swagentd problem

[RAJESH GANGADHARAN]

Hi

we got a HP-UX 11 system runningo n an L Class server. When ever I tried to install any software after the system reboot it is giving some error unable to connect to system . Following is the error in the /var/adm/sw/swagentd.log

WARNING: Failure registering as Remote Procedure Call server using
protocol sequence "ncacn_ip_tcp" with endpoint "2121". No
addresses (dce / rpc)
* Checking job queue at 1 minute intervals.

If I am restarting swagentd daemon. This problem will get resolved till the next reboot.
Can any one suggest what could be the problem.

Thanks in adv
Rajesh

[Tim D Fulford]

You may know this already, but port 2121 is being flagged as used. Why?

what do you get if you do
netstat -na | egrep 1212

Tim

[Massimo Bianchi]

Try restarting the swagentd with
swagentd -r

before the reboot. It's cheap and easy...
Massimo

[Steven E. Protter]

What is the hostname of the machine?

If you've recently changed it in /etc/rc.config.d/netconf make sure it does not exceed 8 characters.

This thread elaborates:
http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xad751cc6003bd6118fff0090279cd0f9,00.html

HP-UX will have trouble with the agent if you use the form hpweb.investmenttool.com as the hostname because investmenttool is too logn. prod.juf.net will work just fine.

If my guess is right to correct you'll neec to change the hostname back and reboot.

SEP

[RAJESH GANGADHARAN]

Hi,
There were no changes in the hostname. Hostname got only 6 charactors.

-Rajesh

[Ben Salamon]

I've got exactly the same problem with swagentd.

======= 12/22/03 16:51:06 GMT BEGIN swagentd (pid = 8920).

WARNING: Failure registering as Remote Procedure Call server using
protocol sequence "ncacn_ip_tcp" with endpoint "2121". status
0xfffffffe (??? / )
ERROR: Terminating prematurely - cannot inquire RPC bindings. status
0xfffffffe (??? / )

======= 12/22/03 16:51:06 GMT END swagentd (pid = 8920, startup
error).

Did you manage to find out the issue. I've tried swagent -r but no luck.

[Andreas D. Skjervold]

Late answer; but I ran into same problem.

Found that this was due to the name resolution. The server name was not registered in the DNS. Apparently the swagent uses only the primary lookup (which was the dns) and not the working NIS service or the lokal files.

Removed /etc/resolv.conf and restarted the swagentd and it worked.

rgds
Andreas

[Uyttersprot]

I have same problem and tried all above options but the problem persists.
What can I do ?

Our customer's system is a J6000 with HPUX 10.20.

[F Verschuren]

Make sure
ping `hostname`
if this is not working you got this error.

if you do nt have a network put it on IP 127.0.0.1

[F Verschuren]

Make sure that you can ping your hostname
ping `hostname`
if this is not working you got this error.

if you do nt have a network put it on IP 127.0.0.1