Unix client agent 1

[mleggatt]

I have a Windows NT server with the ARCSERVE manager installed backing up a Solaris 5.7 Unix box. Until recently this worked o.k. The power supply to the box failed and the machine had to be rebooted. On rebooting it appears that I now cannot get past the USERNAME and PASSWORD screen when trying to browse down the tree on the Backup manager screen. I have tried re-installing the agent and applying the latest service pack (SP1 Build 884) but when I browse down the tree in the Backup manager window to the Unix box in question (under Unix agents) the logon dialogue comes up and I enter the root user name and password but get a "Login to agent" failed message. I know that this password and username is correct as I can Telnet to the box using it. I found a log file within /USR/CYEagent/logs which seems to show what the error is but I have no idea what is means (see below).

6/04 17:38:04(1515) - (getRequest) enter ...
06/04 17:38:04(1515) - (getRequest) blkOffset=680
06/04 17:38:04(1515) - (getRequest) objType=0, opMode=14
06/04 17:38:04(1515) - (agentLogin) loginID=[], paswd=[*]
06/04 17:38:04(1515) - (hostequiv) peerAddr=[192.168.xxx.xxx]
06/04 17:38:04(1515) - (ckpasswd) Failed in getpwnam(), Socket operation on non-socket
06/04 17:38:04(1515) - -- Object [0] [/opt/uagent] ------------------
06/04 17:38:04(1515) - agent info: [Uagent] 5.0.0.2 0x0

I have looked on Google e.t.c for this but found nothing. Has anyone else experienced this or resolved the issue?? any pointers would be appreciated.

Thanks
Martin

 

[mleggatt]

I have since noticed that on an identical server that the agent works on the log file looks like this:

> 06/04 17:38:04(1515) - (agentLogin) loginID=[], paswd=[*]

whereas on the one that does work the line reads:

> 06/04 16:35:04(1515) - (agentLogin) loginID=[root], paswd=[*]

So it seems the ARCSERVE manager is not passing the userid to the unix agent. Question is how do I correct this?

any hints would be appreciated.

 

[TudorP]

Maybe the problem is much simpler than that. In order for the UNIX agent to work you need to specify the machine name and IP address and/or you can add the IP address to the etc\hosts file. My guess is either the name or IP has changed following the reboot, and you can easily verify that by pinging the UNIX box from the NT machine by name and IP. I would be surprised if that is not the problem...
hope this helps
TP

 

[mleggatt]

TP,

Ahhh this may well be the cause of the issue, after the rebooted I noticed that on the Solaris welcome screen it said "Welcome to -a" instead of "welcome to %HOST%" where host is the hostname. After some investigation I found the nodename to be set to "-a" in the file \etc\nodename. I am not sure why this was set like this (I have just inherited the network from a previous sys admin). I changed it to the correct hostname. I have tried deleting the server from the ARCSERVE manager and re-adding it by using auto-discovery but it still refuses the server. Your post has given me a different angle on the issue and has given me another avenue to investigate. I will look into this and post back here once I resolve the issue.

Thanks again
Martin

 

[TudorP]

Dont bother with autodiscovery. Add the unix machine name and IP address to the etc\hosts file on the Windows server and make sure that same info is entered when you add the UNIX agent in the backup manager. bottom line is you should be able to ping the unix box by name and ping -a by IP address from a command line. If that works, AS will work too
glad I could help
TP

 

[mleggatt]

TP,

I have only just got time to add the entry to the hosts file on the Solaris and NT boxes. Guess what I added them this morning and checked I could ping both machines from each other (by name) and now can browse the Solaris box in the backup manager. I will double check the backup runs on this box this evening but I think it will. I think this is a classic case of me overcomplicating things (Wood for trees springs to mind).

Thanks for your assistance this was starting to drive me nuts, it's very much appreciated.