Configuring and Managing MPE/iX Internet Services (MPE/iX 6.5)

Chapter 2 41
Internet Daemon
Troubleshooting inetd
Troubleshooting inetd
This section explains the kinds of error messages you may see
regarding the operation of inetd. The messages will appear either on
the console or they will be sent to the $STDLIST for inetd or both,
depending upon the message’s level of importance.
The following diagnostic messages are generated by successful and
failed attempts to establish a connection to the Internet Services.
Message Explanation
An inetd is
already running
You attempted to start inetd when one is already running. You may
invoke inetd a second time if you use the -c, -k, or -l option, but you
cannot run multiple copies of inetd.
There is no
inetd running
You attempted to reconfigure inetd when none was running. The first
time you run inetd, you must stream it as a job or run it interactively
without specifying the -c (reconfiguration) option.
Inetd not found This message occurs if you invoke inetd with the -c option and inetd
cannot reread its configuration file (which is the purpose of -c). This
occurs when the original Internet daemon dies or is killed without
releasing its semaphore. (The Internet daemon locks a global semaphore
to indicate when it is running to prevent users from running more than
one inetd at a time.) To fix the problem, enter the inetd -k command
to remove the semaphore left by the previous Internet daemon, then
restart inetd.
Message Explanation
/etc/inetd.cnf:
Unusable
configuration
file
The Internet daemon cannot access its configuration. The error message
preceding this one specifies the reason for the failure.
/etc/inetd.conf:
line number: nnn
error
There is an error on the line specified by nnn in the inetd configuration
file. The Internet daemon skips this line, continues reading the rest of
the file, and configures itself accordingly. To solve the problem, open the
configuration file, edit the erroneous line, and save the corrected
version. Then, tell inetd to reread the new version of INTEDCNF by
issuing the inetd.net.sys -c command at the CI prompt.
system call:… The system call noted in the error message failed. See the corresponding
entry in the Berkeley Sockets/iX Reference Manual for a description of
the system call. The reason for the failure is explained in the error
message appended to the system call name.
Cannot configure
inetd
Due to errors in the inetd configuration file, none of the services it lists
could be set up properly.