1847201 Members
3050 Online
110263 Solutions
New Discussion

Re: patch installation

 
amipankaj
Frequent Advisor

patch installation

Hello Experts,


i got some error while installing a depot on my server.

the depot is on server1 and i want to install it on server2.

the analysis phase giving follwing error.

ERROR: The expected depot or root does not exist at │
│ │ "/depots/11.23/depot". │
│ │ * Retry number 1 of 1 for product information. │
│ │ ERROR: The expected depot or root does not exist at │
│ │ "/depots/11.23/depot". ││
│ │ ERROR: Cannot open source. Check above for errors, as well as the ││
│ │ daemon logfile on the source host (default location: /var/adm/sw/swagentd.log). │
│ │ ERROR: Cannot continue the Analysis Phase until the previous errors │
│ │ are corrected.


i have checked on the the source server also and didn't get any error.

please suggest, what to do?


thanks ....Roy
16 REPLIES 16
Asif Sharif
Honored Contributor

Re: patch installation

Hi Roy,

Just copy the depot into machine where you want to install on this path. /tmp/11_23/depot

#swinstall -s /tmp/11_23/depot

Regards,
Asif Sharif
Regards,
Asif Sharif
OFC_EDM
Respected Contributor

Re: patch installation

Did you want to install the software from the depot or simply register the depot on the server?
The Devil is in the detail.
OFC_EDM
Respected Contributor

Re: patch installation

If you have the depot files on server2 too then I think its

swreg -l depot /path/to/depot

This will register the depot on server 2


If the depot is on server1 then from server1 I think its

swreg -l depot /path/to/depot @ server1

Check out the man pages at http://docs.hp.com/en/B2355-92069/B2355-92069.pdf (page 511)
The Devil is in the detail.
amipankaj
Frequent Advisor

Re: patch installation

Hi folks,


the depot is already registered on server server1, i am able to see it using swlist -l depot on server1....i think it may be the access problem, but the permission is also pooking good..its 750.
Ivan Krastev
Honored Contributor

Re: patch installation

What is the exact command used for this installation? Maybe you didn't specify -s parameter?

regards,
ivan
Dennis Handly
Acclaimed Contributor

Re: patch installation

>the depot is on server1 and I want to install it on server2.
ERROR: The expected depot or root does not exist at "/depots/11.23/depot".

Hmm, the message doesn't seem to have server1 anywhere. Did you use:
swinstall -s server1:/depots/11.23/depot

>I am able to see it using swlist -l depot on server1

Can you see it from server2?
swlist -l depot -s server1
Trng
Super Advisor

Re: patch installation

Hi,

you need to make sure that both nodes are pinging one from another and put entries in /etc/hosts accordingly.

regards
skr
administrator
David Markus
Advisor

Re: patch installation

Hi all,

David here, a colleague of Pankaj... I've also been investigating the issue, as I'm the creator of the custom bundles.

I've built them on systemA and swcopied it to systemB, which is within the customer's network.

From there it's can be installed with swinstall.

I've done this many times with multiple bundles without any problems. The current 11.11 bundle works like a charm. It is the 11.23 bundle that is giving problems. It was built the same way as the 11.11 bundle (except other patches of course) and is registered on both systemA and B.

Whenever we try to install it from either system, we get the message that "the target agent cannot access the source".

I've already rebuilt the entire bundle, suspecting that something might be wrong there. I've also unregistered and registered the bundle many times. Also stopped and started swagent, but still no go.

@Ivan Kastrev: Yes, we did specify the -s option. The command I used was: swinstall -s systemA:/depots/11.23/depot

@Dennis Handly: Yes, we did specify the server. Also when we do 'swlist' remotely, the bundle shows up in the list.

@Trng: the reason why the systems should be able to ping eachother isn't clear to me. SDUX needs ports 2121, 2200-2209 to be open, which they are. Also, the customer uses DNS, and all hostnames can be resolved in both ways.





Dennis Handly
Acclaimed Contributor

Re: patch installation

>The command I used was: swinstall -s systemA:/depots/11.23/depot
>Also when we do 'swlist' remotely, the bundle shows up in the list.

Can you list the depot remotely:
swlist -l fileset -s systemA:/depots/11.23/depot
amipankaj
Frequent Advisor

Re: patch installation

Yes Dennis, we are able to list it remotely withe command swlist -l depot @serverB and the depot is visilbe there. No issues in that also.
Dennis Handly
Acclaimed Contributor

Re: patch installation

>we are able to list it remotely with command swlist -l depot

I didn't ask about "-l depot", I asked about "-l fileset". The latter has to actually look inside the depot.
David Markus
Advisor

Re: patch installation

Hi Dennis,

also swlist -l fileset works, it gives a nice cool list of patches.

cheers,

david
Dennis Handly
Acclaimed Contributor

Re: patch installation

>also swlist -l fileset works, it gives a nice cool list of patches.

Hmm, if it can read inside the depot, it seems like it should be able to install it.
David Markus
Advisor

Re: patch installation

Hence the question :)
Dennis Handly
Acclaimed Contributor

Re: patch installation

>David: Hence the question :)

If you don't get any solutions here, it may be time to talk to the Response Center.
Are you up to date on your SD patches?
David Markus
Advisor

Re: patch installation

I've placed a software call yesterday and we're working on the case. If the problem is found, I'll post it here.

Nevertheless thanks for all your help.

cheers,

David