swinstall

[Noble Sebastian]

Hi experts

I unable to install anything (patch , s/w) in my server , the flowing error is showing .



A Remote Procedure Call to a daemon has failed. Could not start a
management session for "servername :". Make sure the host is accessible
from the network, and that its daemon, swagentd, is running.


can you help me

Os -HP UX 11.11

thanks

Noble

[Torsten.]

- restart the swagentd (/sbin/init.d/swagentd stop/start)

- check name resolution

[Ivan Krastev]

Can you post the exact command, used in installation. Possible problem is missconfigured networks/hosts.



Regards,
ivan

[V. Nyga]

Hi,

check the log-file:
/var/adm/sw/swagentd.log

Maybe it's enough to start the agent 'swagentd' or restart with 'swagentd -r'.

HTH
Volkmar

[V. Nyga]

Also check if it's running:
'ps -ef|grep swagentd'

->root 2313 1 0 Mar 18 ? 1:24 /usr/sbin/swagentd -r

V.

[whiteknight]

Noble,

make sure your network link is up too.

WK

[Noble Sebastian]

Thanks to all

I restart demon swagentd , but still problem not solved .
The flowing error showing

Remote Procedure Call to a daemon has failed. Could not start a
management session for "server2/tmp/patch/1 :". Make sure the host is accessible
from the network, and that its daemon, swagentd, is running.

Why host is not accessible from the network..?

I attaching /var/adm/sw/swagentd.log and swinstall.log

Thanks

Noble

[Robert-Jan Goossens]

what does uname -n give you for name?

[Ivan Krastev]

Check following things:
1. resolv of ajith (depot server) - nslookup ajith

2. Connections between your and depot servers:

telnet ajith 2121
swlist -l depot @ajith

regards,
ivan

[James George_1]

Check your hostname defenitions in /etc/hosts file and see if you need the fully qualified name. And also check the nslook on your server name.

your swagentd is not able to resolve / lookup up the hostname correctly and it is reporting , unable to access the host.

Rgds /James

[Bob E Campbell]

The error refers to the target "server2/tmp/patch/1 :". Assuming that this is not a "cut-n-paste" error there are a number of potential problems.

1. No relative paths to a depot

Any depot must include a full path. This means the first character of the path must be "/".

2. Remote depots specified via system:/path

If the depot "/tmp/patch/1" on system "server2" was intended, you need to add a colon:

-s server2:/tmp/patch/1

3. Remote serial depots not supported

If /tmp/patch/1 on server2 is a depot packaged as a single file (known as a serial depot, tape-style depot, or ".depot" file) then it can only be installed on the local system.

If this info is not enough consider using the swinstall GUI and have it guide you to the depot. If that fails, post an "ls -l" of the depot.