random problems with remsh

[Ing Meloni]

I recently patched a N4000 (HPUX 11.0) with all recent critical patches, and now I noticed that when I make a remsh from another HPUX 11.0 machine I obtain a strange random behaviour:

chirone 28: remsh vic23 uname -a
sed: Command not found.
sed: Command not found.
sed: Command not found.
sed: Command not found.
sed: Command not found.
uname: Command not found.

Immediately after:
chirone 29: remsh vic23 uname -a
sed: Command not found.
HP-UX vic23 B.11.00 U 9000/800 619309312 unlimited-user license

Sometimes I don't obtain the line "sed: Command not found." at all.

With another N4000 identical to the other one, but last patched 6 months ago, I have no problems at all.
I am prone to exclude network problem, the answer to the command is immediate, like any other attempt of connection between the two machines.

[Dietmar Konermann]

Check the search path of your remote shell... /usr/bin seems to be missing:

remsh vic23 'echo $PATH'

Best regards...
Dietmar.

[Robert-Jan Goossens]

Hi,

Just a wildshot, but check with remsh on both servers the env

# remsh server env | grep PATH

Hope it helps,

Robert-Jan.

[Ing Meloni]

No, /usr/bin IS in the path. The proof is:

chirone 30: remsh vic23 which sed
sed: Command not found.
sed: Command not found.
/usr/bin/sed
sed: Command not found.

BTW, the problem seems to arise only with non-user accounts.

I tried with "tusc", but it didn't help me much...

[Darren Prior]

Hi,

A couple of questions:

1) Have you checked the permissions on /usr/bin/sed?

2) What happens if you try a remsh vic23 ll /usr/bin/sed?

3) Do you see the sed error regardless of the command you remsh?

regards,

Darren.

[Ing Meloni]

1) correct, I think: 555
2) soon or later I get the correct answer
3) I tried e.g. "remsh vic23 date" (or the ll at point 2) with same result.

BTW: when and at what purpose remsh use sed?

[Darren Prior]

Hmmm - the "sooner or later" bit concerns me!

If this has only started happening since the patches were applied then you should ensure you have the latest check_patches patch, then run check_patches to confirm that your system's patching is correct.

regards,

Darren.

[Adam J Markiewicz]

Hi

Just few thoughts:

If the problem shows up with nonuser accounts, so mayby its because of homedir?Mayby shell?

If its set for / for this accounts mayby the problem is because of permissions to /?


Good luck
Adam

[Frank Slootweg]

I think there may be a problem with aliases, or a remsh trojan somewhere, or ...

So first start with *full* pathnames and to the *local* system, i.e.

/usr/bin/remsh `/usr/bin/hostname` /usr/bin/date

When this works, change things, *one by one*, until it fails again.