weird remsh problem

[Alex Lavrov]

hi,

all throughout my network, and inconsistently, remsh commands sometime don't work and exit, after a long time with: "rcmd: command timeout".

The weird thing about it is that if i run remsh *without any command*, it works just fine. only when I 'remsh host ls' or something like that the problem occurs.

does anyone has an idea?

[Mark Grant]

Are you sure it's not when you run interactive commands such as "vi" as these won't work and won't exit and therefore the remsh will time out.

If not and it really happens when you run "ls" then I would guess that you have network errors. You normally get the error you mention when the command you run hasn't exited.

[Todd McDaniel_1]

What if any does your syslog say?

also, I would look for any hardware issues on your system. Check the psconfig or the cstm output for messages...

Intermittent problems usu point to H/W issues, if not your network card, then the cabling b/t your box and the destination systems...

I would check the remote hosts as well... remsh to a few other differnet hosts so you can try to narrow down the box or h/w or cabling with the problem...

I would bet a donut that one of the boxes involved, either has a bad network card or a cable is going out.

If you have Hardware support in your company, have them check the stability of your network.

[Stuart Abramson_2]

I have a set of scripts that go out and status all of the servers on my LAN each morning when I come in. It does a rcp/remsh and status check on each server.

Sometiimes it times out on one of our servers.

The problem is that the server is set up incorrectly. Buffer cache is too high (50% problem) and memory is often overloaded on this machine.

Real users never complain.

So, I just chalk my problem up to response time issues on the client.

One of these days (next outage window), I'll fix it.

Stuart

[Elmar P. Kolkman]

remsh works through 2 ways, depending on your arguments. If you don't give a command to remsh, it uses the remote-shell port, but if you omit the command, it uses the remote-login port. So what you should do is check your inetd.conf file on the remote machine and see if both are available (login and shell).

Good luck.