Question & Answer
Question
Answer
Users of services and daemons managed by inetd
OBJECTIVE:
Provide instructions to troubleshoot basic problems with inetd
OVERVIEW:
The inetd daemon manages a number of services and daemons, such as ftpd, telnetd, tfptd, and rlogind. There are various issues that may cause some or all of these services to fail.
PROCEDURES:
First, confirm if inetd is running. You should see a single process in the process list.
ps -ef | grep inetd | grep -v grepIf inetd is not running, try starting it with
startsrc -s inetdIf this command fails, there is likely a syntax error in /etc/inetd.conf. You can also try starting it with the -d option to see if it logs any errors to syslog.
startsrc -s inetd -a"-d"If inetd is running, list its status along with all of its currently enabled services with this command.
lssrc -l -s inetdYou will see output similar to this.
Subsystem Group PID Status
inetd tcpip 2293892 active
Debug Not active
Signal Purpose
SIGALRM Establishes socket connections for failed services.
SIGHUP Rereads the configuration database and reconfigures services.
SIGCHLD Restarts the service in case the service ends abnormally.
Service Command Description Status
ftp /usr/sbin/ftpd ftpd active
xmquery /usr/bin/xmtopas xmtopas -p3 active
time internal active
time internal active
ntalk /usr/sbin/talkd talkd active
exec /usr/sbin/rexecd rexecd active
login /usr/sbin/rlogind rlogind active
shell /usr/sbin/rshd rshd active
telnet /usr/sbin/telnetd telnetd -a activeIf the service you need isn't listed, check the /etc/inetd.conf file to make sure it exists and is uncommented. If you make changes to the file, you must refresh inetd to get the updates.
refresh -s inetdIf a specific service won't start, see if there's an existing daemon for that service, kill it and then refresh inetd.
ps -ef | grep <daemon_name> | grep -v grep
kill -9 <pid_of_daemon>
refresh -s inetdIn addition, check the permissions of the daemon's file to make sure it's executable. For example,
ls -l /usr/sbin/tftpd
---------- 1 root system 172796 Aug 17 2017 /usr/sbin/tftpdchmod 555 /usr/sbin/tftpdls -l /usr/sbin/tftpd
-r-xr-xr-x 1 root system 172796 Aug 17 2017 /usr/sbin/tftpdREFERENCES:
- inetd
- Configuring inetd
- inetd.conf
SUPPORT:
If additional assistance is required after completing all of the instructions provided in this document, use the following step-by-step instructions to contact IBM to open a case for software with an active and valid support contract. The technical support specialist assigned to your case will confirm that you have completed these steps.
a. Document (or collect screen captures) of all symptoms, errors, and messages that might have occurred
b. Capture any logs or data relevant to the situation
c. Contact IBM to open a support call (PMR):
- For electronic support, please visit the web page:
- https://www-947.ibm.com/support/servicerequest/newServiceRequest.action
- For telephone support, please visit the web page:
- http://www.ibm.com/planetwide
- Please visit the IBM Support Portal web page for additional resources:
- https://www-947.ibm.com/support/entry/myportal/support
d. Provide a good description of your issue and reference this technote
e. Upload all of the details and data to your support call (case):
Please visit this web page for instructions: https://www.secure.ecurep.ibm.com/app/upload
FEEDBACK:
Quality documentation is important to IBM and its customers. If you have feedback specific to this article, please send a detailed message to the email address:
- aix_feedback@wwpdl.vnet.ibm.com
- - This email address is monitored for feedback purposes only.
- No support for any IBM products or services will be provided through this email.
- To receive support, please follow the step-by-step instructions in the above "SUPPORT" section.
Was this topic helpful?
Document Information
Modified date:
15 September 2021
UID
isg3T1027346