1825944 Members
2715 Online
109690 Solutions
New Discussion

swagent error

 
SOLVED
Go to solution
Fabian Briseño
Esteemed Contributor

swagent error

Hello Guys. im getting this error in my rp3440 with an 11.i OS, Isee no error messages in my swagentd.log file

msdicfg:/var/adm/sw> swlist -l product|grep -i jfs


ERROR: Could not contact host "msdicfg". Make sure the hostname is
correct and an absolute pathname is specified (beginning with
"/").
ERROR: More information may be found in the daemon logfile on this
target (default location is msdicfg:/var/adm/sw/swagentd.log)
Knowledge is power.
9 REPLIES 9
Arunvijai_4
Honored Contributor

Re: swagent error

Hi,

Try restarting swagent daemon by,

# swagentd -r

or

# /sbin/init.d/swagentd stop

# /sbin/init.d/swagentd start

Also make sure your /etc/resolv.conf is correct.

-Arun
"A ship in the harbor is safe, but that is not what ships are built for"
Steven E. Protter
Exalted Contributor

Re: swagent error

Shalom,

First steps always:

ps -ef | grep swagent

# See if there is a process. Usually there won't be.

/sbin/init.d/swagentd start

Use the -R command to restart the daemon.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Fabian Briseño
Esteemed Contributor

Re: swagent error

Sorry guys i was looking at the wrong log file, this is the output for the correct one.


======= 11/19/06 22:06:27 PST END swagentd (pid = 1402).

* Registered RPC protocol "ncacn_ip_tcp" with endpoint "2121".
* Registered RPC protocol "ncadg_ip_udp" with endpoint "2121".
WARNING: An attempt to get the network host entry for "msdicfg" failed.
This may result in denial of access to users and agents at
this host. Check the spelling of this name, then your
"/etc/hosts" file, or your "/etc/resolv.conf" file and DNS
resolver configuration. The nslookup program may be helpful
in isolating this problem.
* Checking job queue at 1 minute intervals.

swagentd file is running and I have already reatrted the swagentd deamon.

I compared "/etc/resolv.conf to other servers whe have and modified it to be in the same way as our ther servers.

/etc/hosts file I have also checked and everything seems fine.

What is: DNS resolver configuration ?.
And The nslookup program ?

Knowledge is power.
Arunvijai_4
Honored Contributor

Re: swagent error

Hi,

Did you restart swagent daemon after modifying /etc/resolv.conf and /etc/hosts files ? If not, please do it.

-Arun
"A ship in the harbor is safe, but that is not what ships are built for"
Fabian Briseño
Esteemed Contributor

Re: swagent error

I did restar swagentd deamon after modifying resolv.conf.

Also I defined a new host name in /etc/hosts file and if I ping to it by name. It displays the follwing

ping MEX
ping: unknown host MEX

Knowledge is power.
Fabian Briseño
Esteemed Contributor

Re: swagent error

after doing:
nslookup mex

msdicfg:/etc> nslookup mex
*** Warning - the local domain is not set.
*** Either hostname should be a domain name,
*** the domain should be specified in /etc/resolv.conf,
*** or the shell variable LOCALDOMAIN should be set.

Hope this helps. Thank you in advance
Knowledge is power.
Yang Qin_1
Honored Contributor
Solution

Re: swagent error

Hi, double check /etc/resolv.conf it seems that the "domain" is not properly configured

also compare /etc/nsswitch.conf with the one on the other server.

try to ping mex with full name "ping mex.xxx.xxx"


Yang
Fabian Briseño
Esteemed Contributor

Re: swagent error

/etc/nsswitch.conf file did not exist in the problem server, I created it copying it from another server, but still not it's not working.



Knowledge is power.
Fabian Briseño
Esteemed Contributor

Re: swagent error

Problem solved guys.

I configured via SAM in networking something called:
NAME SERVICE SWITCH->hosts

And that fixed the problem.

Thanks for all your help guys.


Knowledge is power.