swinstall and RPC exception: "connection closed (dce/rpc)"

[Ahmed ABDOU_1]

Hi

We have N-4000 system with hp-ux 11.00 .

We were trying to install patches on it but we faced the following error after the analysis phase ended successfully. and starting the actual loading :

The Controller has lost communication with the agent on the target "drcanb:/" probably because of networking problem or the target agent timing out due to extended inactivity. The task can not be completed and the target has been automatically excluded. you can not obtain "product summary" or "Logfile" information on this target.

Best regards,

Note: this is the part of the swinstall.log file that has the problem, and please know that we do not have DNS or NFS.
======= swinstall ========

* Beginning Analysis
* The analysis phase succeeded for "drcanb:/".
* Ending Analysis
* Before starting Installation, you should be aware of the
following:

Kernel filesets will be installed on the local system. The
Installation process will include building a new kernel.

The system will be rebooted as soon as Installation is
complete.

Do you still wish to start Installation?
* Beginning Task Execution
* Proceeding with Task Execution on the following targets:
* drcanb:/
ERROR: RPC exception: "Connection closed (dce / rpc)" 11/10/01
13:40:03 WAT
ERROR: RPC exception: "Connection closed (dce / rpc)" 11/10/01
13:40:03 WAT
* The controller has lost communication with the agent on the
target "drcanb:/", probably because of a networking problem or
the target agent timing out due to extended inactivity. The
task cannot be completed and the target has been automatically
excluded. You cannot obtain "Product Summary" or "Logfile"
information on this target.
* A communication failure occurred on drcanb:/.
* Ending Task Execution
* Returning to Selection

======= 11/10/01 13:40:44 WAT END swinstall SESSION (interactive)

[Bill McNAMARA_1]

Is your local host the server name mentioned?

Try restarting swagent on your target (local system)

/sbin/init.d/swagentd stop
/sbin/init.d/swagentd start

You should also have a look in your /var/adm/syslog/*.log
for networking errors..

ensure you can ping the source server, verify the /etc/hosts

Later,
Bill

[Sanjay_6]

Hi,

Take a look at the threads below,

http://us-support.external.hp.com/cki/bin/doc.pl/sid=18112eb41d5c4236c2/screen=ckiDisplayDocument?docId=200000045467725

http://us-support.external.hp.com/cki/bin/doc.pl/sid=18112eb41d5c4236c2/screen=ckiDisplayDocument?docId=200000057272506

Hope this helps.

Regds

[T G Manikandan]

Hello,
Also check this link

http://us-support.external.hp.com/cki/bin/doc.pl/sid=2560dc2d084deb22ba/screen=ckiDisplayDocument?docId=200000024631715

[Ahmed ABDOU_1]

Hi

Thanks for every one for his replay but the problem I can not accuses these links because it in US-ITRC and my account is in Europe.

So could you please attached these pages to the replay message

Thanks in advance

[Darrell Allen]

Very curious, I just got the same error. I'm installing from a local depot, have made no networking changes (including name resolution), and have the referenced SD patch. I've rebooted to no avail.

Unlike the other links, I get thru the analysis phase okay. I even get some of the patches installed. Then I get the Communication Failure.

I'll let you know what I find.

Darrell

[Bill McNAMARA_1]

with those links, just copy the url, replace the us with europe and it'll work fine.

Later,
Bill

[Sanjay_6]

Hi,

The Doc ID's are
A5909796
USDUXKBRC00008295
W3555671

Do a search with the DOC ID and you should be able to locate the document.

Hope this helps.

Regds

[Darrell Allen]

Hello again,

I believe if you simply change us-support to europe-support in the links shown you'll be able to get to them.

Now for the good news: my swinstall worked. I have been testing and created a new volume group with a logical volume and a filesystem. It was activated but the filesystem was not mounted nor was there a reference to it in /etc/fstab. From reading the links suggested and realizing this testing was the only changes I've made, I decided to de-activate the VG and export it. The install then worked as expected.

Good luck with your install. Hope you'll be posting your solution soon!

Darrell

[Darrell Allen]

Hi again,

Well, I just had the same error on another server while installing a patch bundle. I had not been testing with VGs on this system so I can only assume that last time I was lucky and there is another problem.

Darrell

[Wodisch]

Hello,
you could simply kill "swagentd" and restart it with the "-r" option...

Just my ???0.02,
Wodisch

[Anoop P_2]

If the source path points to a tar file, extract it to a suitable location, register it as a depot and create the swlock file in the catalog folder. I solved my problem this way