"error getting while creating the depot"

[Rahul Rai_1]

Hello Team,

I am getting errors while I am trying to create a depot, please go through with the logs, and sugest us.

Thanks in advance.

[TTr]

Did you go through the logs? Did you happen to notice the following
> ERROR: More information may be found in the agent logfile using the command "swjob -a log devcde01-0251 @ devcde01:/tmp/patch/depot"

The error "execution failed..." does not say much does it.

[Rahul Rai_1]

Dear TTr,

when we are running the swjob* command we are getting below messages,

root@devcde01[/tmp/patch]# swjob -a log devcde01-0254 @devcde01:/tmp/patch/depot
======= 09/21/09 08:18:54 EDT BEGIN verify AGENT SESSION (pid=12555)
(jobid=devcde01-0254)

* Agent session started for user
"root@devcde01.unix.gsm1900.org". (pid=12555)

* Beginning Analysis Phase.
* Target: devcde01:/tmp/patch/depot
* Target logfile: devcde01:/tmp/patch/depot/swagent.log
* Reading source for file information.
NOTE: The filesystems in the filesystem table will not be checked
against those currently mounted because the
"mount_all_filesystems" option is set to "false".
* Available PHSS_32508.ACXX,r=1.0
* Available PHSS_32509.C,r=1.0
* Available PHSS_32510.LANG-AUX,r=1.0

* Summary of Analysis Phase:
Verified BUNDLE,r=B.2009.09.21
Verified PHSS_32508.ACXX,r=1.0
Verified PHSS_32509.C,r=1.0
Verified PHSS_32510.LANG-AUX,r=1.0
* 3 of 3 filesets had no Errors or Warnings.
* The Analysis Phase succeeded.


======= 09/21/09 08:18:55 EDT END verify AGENT SESSION (pid=12555)
(jobid=devcde01-0254)

Regards,
Rahul Rai.

[kobylka]

Hello!

Seams like first swcopy fails for some reason. After script finishes try to get the agent log for the failed swcopy and post again.

Agent log you provided was:

root@devcde01[/tmp/patch]# swjob -a log devcde01-0254 @devcde01:/tmp/patch/depot

which corresponds to verification (devcde01-0254), not to failed swcopy (devcde01-0251):

ERROR: More information may be found in the agent logfile using the
command "swjob -a log devcde01-0251 @
devcde01:/tmp/patch/depot".


Kind regards,

Kobylka

[TTr]

> when we are running the swjob*
There are two patches and two swcopy commands in the crerate_depot script. You gave us the log for the second swcopy which suceeded and had no errors. You need to look in the "01-0251" job not the "01-0254" job.

[gb karki]

Hi TTr,

I'm team member of Rahul.

Please see the below logs, as per your mail.

root@devcde01[/tmp/patch/depot]# swjob -a log devcde01-0251 @devcde01:/tmp/patch/depot
======= 09/21/09 08:18:35 EDT BEGIN copy AGENT SESSION (pid=12515)
(jobid=devcde01-0251)

* Agent session started for user
"root@devcde01.unix.gsm1900.org". (pid=12515)

* Beginning Analysis Phase.
* Source:
devcde01.unix.gsm1900.org:/tmp/patch/PHSS_32508.depot
* Target: devcde01:/tmp/patch/depot
* Target logfile: devcde01:/tmp/patch/depot/swagent.log
* Reading source for product information.
NOTE: The filesystems in the filesystem table will not be checked
against those currently mounted because the
"mount_all_filesystems" option is set to "false".
* Reading source for file information.
NOTE: The used disk space on filesystem "/tmp" is estimated to
increase by 11960 Kbytes.
This will leave 4716957 Kbytes of available user disk space
after the installation.

* Summary of Analysis Phase:
* 1 of 1 filesets had no Errors or Warnings.
* The Analysis Phase succeeded.


* Beginning the Copy Execution Phase.
* Filesets: 1
* Files: 4
* Kbytes: 29521
ERROR: Failed to register "/tmp/patch/depot". You must register it
later using the "swreg" command.
* Copying fileset "PHSS_32508.ACXX,r=1.0" (1 of 1).

* Summary of Execution Phase:
* 1 of 1 filesets had no Errors or Warnings.
ERROR: The Execution Phase had errors. See the above output for
details.


======= 09/21/09 08:18:41 EDT END copy AGENT SESSION (pid=12515)
(jobid=devcde01-0251)
root@devcde01[/tmp/patch/depot]#

Regards
Karki

[Dennis Handly]

>ERROR: Failed to register "/tmp/patch/depot".

This is your problem.

If you can't get this solved, you can simply install PHSS_32508 & PHSS_32509 by themselves, they don't need to reboot.

You might want to check the checksum of PHSS_32508, since only that one was bad.