swagentd

[Dario_4]

Hello admins,
I wuold like to solve this problem:

Reinizializate software distribution agent deamon ....FAILS.

This is related to swagentd.

The output of /etc/rc.log show this:

Reinitialize Software Distributor agent daemon
Output from "/sbin/rc2.d/S870swagentd start":
----------------------------
ERROR: swagentd exiting due to initialization error in background
process. Check the logfile "/var/adm/sw/swagentd.log" for
more information.
ERROR: Unable to restart swagentd after initializing networking.
"/sbin/rc2.d/S870swagentd start" FAILED


This is the var/adm/sw/swagentd.log

======= 12/10/01 14:26:00 EST BEGIN swagentd (pid = 1924).

WARNING: Failure registering as Remote Procedure Call server using
protocol sequence "ncacn_ip_tcp" with endpoint "2121". No
addresses (dce / rpc)
* Started configure agent on "/" for root@localhost, pid=2294,
12/10/01 14:26:32 EST
* Agent pid=2294 completed. 12/10/01 14:28:44 EST
* Started configure agent on "/" for root@localhost, pid=2707,
12/10/01 14:28:46 EST
* Agent pid=2707 completed. 12/10/01 14:28:51 EST
* Started configure agent on "/" for root@localhost, pid=2715,
12/10/01 14:28:53 EST
* Agent pid=2715 completed. 12/10/01 14:28:57 EST
* Started configure agent on "/" for root@localhost, pid=2723,
12/10/01 14:29:00 EST


But if i lunch swagentd by command line, it works fine.

Some suggestions?

Thanks

[harry d brown jr]

I believe you need to patch your system. Go to the "custom patch manager" and get the patches for your system.

live free or die
harry

[Sachin Patel]

Hi Harry, How is he going to install patch if his swagentd is not running?

I think it is to do with his hostname resolv or some rpc service is not running.

Sachin

[Technical Support_2]

Hi Fabrizio,
Here is what I found on itrc

Problem:
swagentd hanging at bootup, system can't resolve its own name

Current Path Home
Score : 0
Document Type : EN
Date : 2001 Jul 31
Description : swagentd hanging at bootup, system can't resolve its own name
Document Id : KBRC00007604
Search String :

You may provide feedback on this document

View the printer friendly version of this document



--------------------------------------------------------------------------------
swagentd hanging at bootup, system can't resolve its own name DocId: KBRC00007604 Updated: 7/31/01 4:15:00 PM

PROBLEM
I'm having problems when booting my system, S100swagentd startup
script is hanging. When starting swagentd from the command line,
I receive the error:

failure registering as remote procedure call, ncacn_ip_tcp 2121

I can ping other systems via the IP address, but not by name.
I'm using resolv.conf and I'm unable to get to my name server. CONFIGURATION

Operating System -HP-UX
Version -10.20
RESOLUTION
If the system cannot resolve its own hostname, then swagentd will not be able
to start.

To fix this problem:

1) If your are not using DNS, then move resolv.conf out of the way,
and verify that the hostname is in /etc/hosts. swagentd should now
start without any problems.

2) If your are using DNS, it is recommended that you set files
as the first place to try and lookup a hostname on each
machine. Do this by editng the 'hosts" line in
/etc/nsswitch.conf file to look similar to:

hosts: files [NOTFOUND=continue] dns

This way when the systems boot up, if the nameserver is down, each machine will
be able to start swagentd without a problem since it is resolving its own name
locally.

[Dario_4]

Now it's ok...
I don't make nothing....
Strange problem...

[harry d brown jr]

Sachin, he said he could start it from the command line without any problems....?? And now its ok?

live free or die
harry

[Sanjay_6]

Hi Fabrizio,

Try these links,

http://us-support3.external.hp.com/cki/bin/doc.pl/sid=b751f10412dd68b75d/screen=ckiDisplayDocument?docId=200000055759519

http://us-support3.external.hp.com/cki/bin/doc.pl/sid=b751f10412dd68b75d/screen=ckiDisplayDocument?docId=200000014667815

Hope this helps.

Regds

[Wodisch]

Hello Fabrizio,

could you check your "/etc/rc.config.d/*", please?
If there are some environment variables set (which do not exist in your shell's environment), that could be the reason...

Just my $0.02,
Wodisch