Problems with remsh

[Alan Meyer_4]

When connecting to a few of my machines via remsh, I was receiving the following message:

remshd: getservbyname

I then checked the inetd process and configuration and also issued a inetd -c to no avail.

At this point I could still telnet into the machine.

I then issued a /sbin/init.d/inetd stop and then a start and the message changed to this:

rcmd: connect: nodename: Connection refused

and telnet connections were started to be refused by host.


This is only happening on 3 of my machines out or 37 and "to my knowledge", no changes have been made to any of the boxes.

[A. Clay Stephenson]

Well, you didn't bother to identify the OS version(s) but for 11.11, PHNE_33791 may well fix you.

[Alan Meyer_4]

Actually these are all 11.00 boxes. But this is not affecting ALL my 11.00 boxes.

[A. Clay Stephenson]

In that case, check out PHNE_33790.

8. JAGae32691 / SR 8606268453:
remshd fails to execute when the service name database
does not contain an entry for "kshell", and displays the
message: "remshd: getservbyname".

[Robert-Jan Goossens]

Could you check if kshell and ekshell are uncommented in the /etc/services file ?

Robert-Jan

[Robert-Jan Goossens]

Title: remshd(1M) / rlogind(1M) getservbyname error reported in syslog.
Document ID: 8606268453

US
http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000077312589
Europe
http://www4.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000077312589

[Alan Meyer_4]

Is it possible that the services file itself can become corrupt??? The reason I ask is the I am also now getting a bunch of messages in the syslog that state

Nov 2 11:45:44 beryl inetd[940]: telnet/tcp: Unknown service

[Alan Meyer_4]

I have checked the kshell & ekshell services are not commented.

[Sandman!]

Check this out...

http://www2.itrc.hp.com/service/cki/search.do?category=c0&prevQueryString=remshd%3A+getservbyname&mode=id&searchString=2200103257&searchCrit=allwords&docType=Security&docType=Patch&docType=EngineerNotes&docType=BugReports&docType=Hardware&docType=ReferenceMaterials&docType=ThirdParty&dateRange=all&search.x=23&search.y=10

[A. Clay Stephenson · Accepted solution]

Yes, it's possible that you have a corrupt services file and even more possible if you are running NIS, NIS+, or LDAP and have a corrupt services map/table.

[Alan Meyer_4]

It was actually a corrupt NIS slave server. When we ypset these servers to the master server and then ran inetd -c, everything worked great.

So it seems that the slave server in question does not get refreshed whenever the master server gets rebooted. Sounds liek another thread to me....