Message: inetd[1049]: Problem with /var/adm/inetd.sec: cannot start any servers

[Stefan Schulz]

Hi all,

i have several of this messages on my main fileserver:

May 15 11:55:17 keserv inetd[1049]: Problem with /var/adm/inetd.sec: cannot start any servers

Seems that i just can't concentrate today. I feel like a normal Windows user because i (at the moment) don't understand what this message is telling me :-(

My inetd.sec file has nothing special configured. It looks like this:

dtspc allow 127.0.0.1 kitty
spc allow 127.0.0.1 keserv
mserve allow 127.0.0.1 keserv

The Server is a D380/1 running HP-UX 10.20 on 384MB RAM. It is set up as NFS and SAMBA Fileserver. There are 32 (the maximum) nfsd running and 17 smbd.

Any help is greatly appreciated

Regards Stefan

[U.SivaKumar_2]

hi,
hope you checked the permissions of that file.
should be readable and writable only for root.


regards,
U.SivaKumar

[Sridhar Bhaskarla]

Hi Stefan,

inetd.sec reads as below

"Hosts and network names must be official names, not aliases"

See if those names are aliases and fix them and restart inetd.

-Sri

[S.K. Chan]

It means the file /var/adm/inetd.sec contains server names (or hostname) that are not known to the system. Check if all the hostname is a valid one or not. Remove/fix those "bad" hostname and then restart "inetd" ..
# /usr/sbin/inetd -k
# /usr/sbin/inetd

[Steve Steel]

Hi

Indeed bad names

You can also

mv /var/adm/inetd.sec /var/adm/inetd.sec.bad
cp /usr/newconfig/var/adm/inetd.sec /var/adm/inetd.sec
Edit the file appropriately.
/usr/sbin/inetd -k
/usr/sbin/inetd

Then you have got all typos.

Otherwise you must nslookup the server names in the file and see what is missing.

Maybe you lost a dns server

Steve Steel

[Stefan Schulz]

Thanks for your responses.

I think i found tho solution. There was another message in the syslog.log which i didn't recognize the first time (bust have been partially blind):

vmunix: inode: table is full

A quick check with sar -v showed that the inode-table really is full.

Which means that i have to configure and build a new kernel. The inetd message is only a resulting error due to the full inode-table.

The permissions and entries of the inetd.sec file have been unchanged for months. So that disturbed me so much.

Thanks for your fast responses and your provided info. This forced me to have a second look in the syslog.log.

Regards Stefan