Agent install fails with ssh access

Rmumford — Tue, 10 Jul 2007 10:08:11 GMT

I’m trying to install the agent on a remote host, and having a problem getting the server to log into the remote. The server is a Solaris box and the remote is a linux 2.6 box. Here’s the versions:

[root@mgt02] /tmp>opcagt -version
A.08.10.160

[root@mx231] ~> uname -a
Linux mx231 2.6.9-42.ELsmp #1 SMP Wed Jul 12 23:27:17 EDT 2006 i686 i686 i386 GNU/Linux

Here’s the error I get: (I get the same using the gui)

[root@mgt02] />/opt/OV/bin/OpC/agtinstall/inst.sh
--------------------------------------------------
Script /opt/OV/bin/OpC/agtinstall/inst.sh invoked by root at 07/10/07 10:28:29.
OVO Software Maintenance on Managed Node(s).
Enter system(s) for which software maintenance should be done.
More than one system can be specified, if separated by blank: (empty = stop processing)
========> mx231
========> Preferred IP address of node mx231 (Return=mx231)?
Managed Nodes platforms supported by this Management Server:
dec/alpha/unix
dec/alpha/unix51A+
hp/ia64/hp-ux11_32
hp/ipf32/hpux1122
hp/pa-risc/hp-ux11
hp/pa-risc/hpux1100
ibm/rs6000/aix
ip/other/other
linux/intel/linux24
linux/x86/linux24
linux/x86/linux26
ms/intel/nt
ms/x86/winnt
non_ip/other/other
novell/intel/nw
sgi/mips/irix
sun/sparc/solaris
sun/sparc/solaris7
========> Enter platform name for mx231 :linux/x86/linux26
========> Automatic update of system resource files (y|n=default)?y
========> Automatic (re-)start of OVO services on (y|n=default)?y
========> OVO version (V.UU.FF) which should be installed on system mx231 (Return=latest version)?
========> Enter distribution method for Agent package (1 = Management Server based, 2 = Satellite Agent Depot with SD, 3 = Windows NT
installation server 4 = Secure Shell installation (default=1)?
========> Login name of superuser for system mx231 (Return=root)?unisys12345

PHASE I: reading missing passwords for Managed Nodes.
=============================================================
Checking for OV Config and Deploy component running on system mx231.mc2.embarqnow.net.
There is no OV Deployment component running on system mx231.mc2.embarqnow.net.
========> Please enter the root password for system mx231.mc2.embarqnow.net?
Encountered problem obtaining information from system mx231.mc2.embarqnow.net. Possible causes: Specified password might be wrong or name of
management server is not known on managed node.
========> Do you want to re-enter the login information for system mx231.mc2.embarqnow.net (y|n=default)?n
ERROR: Skipping node mx231.mc2.embarqnow.net for initial password check; maybe you know the password later when applying the OVO software maintenance
on that system.

Please press RETURN for error confirmation:

[root@mgt02] /tmp>cat /var/opt/OV/log/OpC/mgmt_sv/inst_err.log
Script /opt/OV/bin/OpC/agtinstall/inst.sh invoked by root at 07/10/07 10:28:29.
ERROR: Skipping node mx231.mc2.embarqnow.net for initial password check; maybe you know the password later when applying the OVO software maintenance
on that system.

I found another string on this site that suggested adding the server to the .rhosts file, I did so with no change. I also have tried entering the server in the /etc/hosts file.

I can log in via ssh, and the password is correct and works.

Thanks for any help.

R Mumford

Re: Agent install fails with ssh access

Rmumford — Tue, 10 Jul 2007 10:13:14 GMT

Apologies to all, this was meant for the OVO forum. I will attempt to close. Moderator, please remove from linux forum.....

R Mumford

Re: Agent install fails with ssh access

Rmumford — Tue, 10 Jul 2007 10:13:45 GMT

Wrong forum

Re: Agent install fails with ssh access

Mkwasn — Mon, 06 Aug 2007 16:12:40 GMT

We found that in order to install the OVO agent we had to temporarily re-enable some of the r commands.

1. Add "mgmntsvr_name root" to /.rhosts on the new node. For us our mgmtsvr_name is opscena, so the entry would look like "opscena root".
2. Enable rlogin if it is disabled. In /etc/inetd.conf the new node, uncomment login, shell, exec. Then, run "inetd -c"
3. Try distributing agent to new node.
4. Reverse steps 1 and 2.

topic Re: Agent install fails with ssh access in Operating System - Linux

Agent install fails with ssh access

Re: Agent install fails with ssh access

Re: Agent install fails with ssh access

Re: Agent install fails with ssh access