When network service like telnet connection hangs, then it is possible the inetd subsystem is not working properly.
If the refresh hangs for some time and comes back with 0513-056 time out waiting for command response, then the inetd subsystem may not be working correctly and should then be killed nicely. Run
and do a kill -15 on the process ID on the line that has /usr/sbin/inetd. Once inetd has been killed, type startsrc -s inetd. If inetd starts, try to telnet into the machine. If inetd does not start up successfully, or if telnet still hangs indefinitely, run kill -15 on the PID of inetd again. Back up the original /etc/inetd.conf file to a new file name by typing:
The original template is in /usr/lpp/bos.net/inst_root/etc/. You can copy it by typing:
Run startsrc -s inetd and you should now be able to telnet into the machine
# refresh -s inetd
0513-095 The request for subsystem refresh was completed successfully.
If the refresh hangs for some time and comes back with 0513-056 time out waiting for command response, then the inetd subsystem may not be working correctly and should then be killed nicely. Run
#ps -ef | grep inetd
and do a kill -15 on the process ID on the line that has /usr/sbin/inetd. Once inetd has been killed, type startsrc -s inetd. If inetd starts, try to telnet into the machine. If inetd does not start up successfully, or if telnet still hangs indefinitely, run kill -15 on the PID of inetd again. Back up the original /etc/inetd.conf file to a new file name by typing:
# mv /etc/inetd.conf /etc/inetd.conf.backup
The original template is in /usr/lpp/bos.net/inst_root/etc/. You can copy it by typing:
# cp /usr/lpp/bos.net/inst_root/etc/inetd.conf /etc/inetd.conf
Run startsrc -s inetd and you should now be able to telnet into the machine
Comments
Post a Comment