remshd: Login incorrect

[Frank de Vries]

We have a script that runs once every hour on weekdays and nights.

And since we have ported it to a new host in the last 4 months we had 2 or 3 incidents , that the script failed and in the log was simply a message:
resmshd: Login incorrect

However at the next hour it run okay again, and
nothing was changed in the script.
And we loads of othter scripts which do remsh,
no incidents to date there.
So we are a bit puzzled, maybe one of you
came accross this as well?

This is an exerpt from the script.

#second incident: 15.06.2005
# added an explicit -l username due to rare remshd: 'Login incorrect ' errors that
# appeared unexplicably, however it could be due to DNS resolve problem of vwbr46 so we do nslookup checkup.

print "Starting remsh as id = `id` on date = `date ` \n"

nslookup vwbr46
remsh vwbr46 -l infas -n $REMSCR

Anyone ever had the error in this erratic way.

NB: We run the script via the agent of Autosys (a product from CA ) so it is not a cronjob!.
NB: The $REMSCR command that we run on the remote accesses a datafile on a NFS-share.

[Amit Agarwal_1 · Accepted solution]

You need to check the .rhosts file on vwbr46 under infas' home directory. It must contain the entry specifying the hostname and username from where you are running this script.

So, if you are on host HHHH and logged in as user UUUU, there should be an entry in
/.rhosts, which matches any one of the below.

HHHH UUUU
or
+ UUUU
or
HHHH +

[Frank de Vries]

the .rhosts file in $HOME of user infas
only has mention of hostnames.

The fact we omitted the user could
give rise to the erratic behaviour ?
That is, 20*24 times it is successfully authenticated and once it is denied ?

Can anyone explain ?

[Muthukumar_5]

Some times working and some time not?

what is your system information? uname -a
remshd version? what /usr/lbin/remshd

hth.

[Frank de Vries]

Hmm, good questions.

Yes, it works basically every hour on weekdays, so roughly 20 days * 24, and it fails once out of that since we migrated to
the new node.( In the last 4 months, it
failed 3 times, so roughly once a month)
------
host which runs remsh and uname -a
[root@orasrv1:]/picnew/apps/infas/execute/sh<>>> what /usr/lbin/remshd
/usr/lbin/remshd:
Copyright (c) 1983, 1988 The Regents of the University of California.
rshd.c 5.17.1.2 (Berkeley) 2/7/89
remshd.c $Revision: 1.36.214.15 $
patch id : PHNE_23003
You have mail in /var/mail/root
[orasrv1:/picnew/apps/infas/execute/sh]# uname -a
HP-UX orasrv1 B.11.00 U 9000/800 654359382 unlimited-user license
----
host which receives remsh and uname -a
[vwbsrv3:/root]# what /usr/lbin/remshd
/usr/lbin/remshd:
$Revision: vw: -RW selectors: 'ic27d' -proj integ -- ph_ic27d_i80 'cupi80_ic27dbase_pb(08-Nov-00.
16:48:14)' 'BE11.11_IC27A'
Wed Nov 8 18:32:19 PST 2000 $
Copyright (c) 1983, 1988 The Regents of the University of California.
[vwbsrv3:/root]# uname -a
HP-UX vwbsrv3 B.11.11 U 9000/871 2000573132 unlimited-user license
[vwbsrv3:/root]#

[Amit Agarwal_1]

Hi Frank,

I believe that you need to mention the user name or '+'. I haven't encountered rhost entry without username.

The other issue that you have mentioned about remsh script not working once in a while. Based on the information that you have provided, and moreover you say that there is no change in any script or rhost file, I would see it as a one-off case. However, would suggest you to have a deeper look next time it fails. Try to capture the .rhosts file of infas user whenever it fails.

-amit

[Eknath]

Hi Frank,

Is it possible to replace the hostname with the IP address, just to resolve the issue.

Cheers !!!
eknath

[Amit Agarwal_1]

By any chance, the DNS server were down when you noticed the remsh script failure?

It is possible that access was denied because host name could not be resolved successfully.

-amit

[Frank de Vries]

sorry for the late reply, and allocating
some points.

In fact is is fully working now without incident for months , and it seems that a explicit username seemed to have solved it.
(Still don't get it why, but heck)

The dns was definitely available.
So thanks for all your input

Regards,