Operating System - HP-UX
1832757 Members
3186 Online
110045 Solutions
New Discussion

OB-II Client Installation problem

 
SOLVED
Go to solution
vselvaraj
Advisor

OB-II Client Installation problem

Dear All

I am having Ob-11 3.10 installed on HPUX 11.00 L-1000 server. I have installed the clients on R,B,L,A class servers with 10.20 ,11.00 and intel based NT Servers also.

I was tring to install one more new client
on A class HPUX 10.20, I am getting the followiung error, Installation failed.

Error files attached.
Can anyone help me to solve this.

Thanks in advance
V.Selvaraj




4 REPLIES 4
Andy Monks
Honored Contributor

Re: OB-II Client Installation problem

It looks like OBII is trying to use OV-SD (the full software-distributor product), and doing remote swinstalls. I'm no OBII expert, but I didn't think it worked that way. I thought it just remsh'ed to copy the depot across.

However, as SD is involved, I would check that both machines, know each others hostname, ip address and can correctly ping/telnet etc. SD is the most fussy s/w when it comes to hostname resolution.
Alex Glennie
Honored Contributor
Solution

Re: OB-II Client Installation problem

Try a kill/restart of swagentd and retry, sounds like the ACL's are a bit hosed.
Stefan Farrelly
Honored Contributor

Re: OB-II Client Installation problem


One of your logs lists;
Target succeeded for chefwm:/
and the swagent.log lists;
root@chefwm.bplnet.com
Looks like a hostname/domain/dns lookup problem.
On your host chefwm, whats the hostname set to ? can you do an nslookup on it, does it return chefwm or chefwm.bplnet.com. Can you nslookup chefwm.bplnet.com ?
Both nslookups need to work, your hostname should be set to chefwm and in the hosts file you should have its IP and hostname of chefwm, but dns should return its domain, chefwm.bplnet.com
Im from Palmerston North, New Zealand, but somehow ended up in London...
John Palmer
Honored Contributor

Re: OB-II Client Installation problem

You could also try the following:-

/sbin/init.d/swagentd stop
/sbin/init.d/swagentd start
rm /var/adm/sw/products/swlock
swacl -l host -M user:root@:crwit

A point of interest for anyone on HP-UX 11.00 is that HP have changed the /sbin/init.d/swagentd script so that it will not work if you just run it as '/sbin/init.d/swagentd'. It must be run as '/sbin/rc2.d/S100swagentd start' and '/sbin/rc1.d/K900swagentd stop'

It took me a little while examining the script a couple of weeks ago when I wanted to restart swagentd.