Operating System - HP-UX
1753783 Members
6940 Online
108799 Solutions
New Discussion юеВ

swinstall error failed Disk Space Analysis for PHSS_35385 linker patch

 
SOLVED
Go to solution
Johnson Punniyalingam
Honored Contributor

swinstall error failed Disk Space Analysis for PHSS_35385 linker patch

Hi Guys,

Can anyone advice on swinstall Install patch for PHSS_35385 ,

All my file system size looks ok,

please see attachment

Thanks,
Johnson
Problems are common to all, but attitude makes the difference
23 REPLIES 23
likid0
Honored Contributor

Re: swinstall error failed Disk Space Analysis for PHSS_35385 linker patch

when you go to the disk_space tab in the swinstall gui, what filesystem does it complain about?

how much it says it needs ?
Windows?, no thanks
Dennis Handly
Acclaimed Contributor

Re: swinstall error failed Disk Space Analysis for PHSS_35385 linker patch

Why did the Disk Space Analysis fail?
When you "press the "Disk Space..." button." what did you get? Your log file is scrambled.

You need to use command line swinstall to install the patch, not sam, so we don't get unhelpful junk:
swinstall -x mount_all_filesystems=false -s $PWD/PHSS_35385.depot \*

Ganesan R
Honored Contributor

Re: swinstall error failed Disk Space Analysis for PHSS_35385 linker patch

Hi Johnson,

You can always look into /var/adm/sw/swagent.log which will provide the filesystem space issues if any..

Can you provide the tail portion of /var/adm/sw/swagend.log ?
Best wishes,

Ganesh.
Johnson Punniyalingam
Honored Contributor

Re: swinstall error failed Disk Space Analysis for PHSS_35385 linker patch

Hi Dennis, Orange, Ganesan,

Bunch of Thanks, for you Quick reply,

I suspected dependencies issue, so was sucesfull in Installation "PHSS_28871"
but my goel is to Install "PHSS_35385"

>>Why did the Disk Space Analysis fail?
When you "press the "Disk Space..." button." what did you get? Your log file is scrambled.<<

Dennis> please see attachment , Thanks

>>Can you provide the tail portion of /var/adm/sw/swagend.log ?<<

/var/adm/sw > more swinstall.log swagentd.log
* Started install agent on "/" for root@dwhsvr05, pid=12292,
02/03/09 15:36:43 SST
* Started source agent on "/opt/IBM/PHSS_35385.depot" for
root@dwhsvr05, pid=12295, 02/03/09 15:36:44 SST
NOTE: The target "/opt/IBM/PHSS_35385.depot" currently open for
reading is a tape. pid=12295 02/03/09 15:36:44 SST
* Agent pid=12295 completed. 02/03/09 15:37:40 SST
* Agent pid=12292 completed. 02/03/09 15:37:41 SST
* Started install agent on "/" for root@dwhsvr05, pid=13087,
02/03/09 16:02:42 SST
* Started source agent on "/opt/IBM/PHSS_35385.depot" for
root@dwhsvr05, pid=13090, 02/03/09 16:02:43 SST
NOTE: The target "/opt/IBM/PHSS_35385.depot" currently open for
reading is a tape. pid=13090 02/03/09 16:02:43 SST
* Agent pid=13090 completed. 02/03/09 16:03:36 SST
* Agent pid=13087 completed. 02/03/09 16:03:37 SST
* Started install agent on "/" for root@dwhsvr05, pid=17351,
02/11/09 10:26:28 SST
* Started source agent on "/opt/IBM/PHSS_35385.depot" for
root@dwhsvr05, pid=17354, 02/11/09 10:26:29 SST
NOTE: The target "/opt/IBM/PHSS_35385.depot" currently open for
reading is a tape. pid=17354 02/11/09 10:26:30 SST
* Agent pid=17354 completed. 02/11/09 10:27:52 SST
swagentd.log (45%) * Agent pid=17351 completed. 02/11/09 10:27:53 SST
* Started install agent on "/" for root@dwhsvr05, pid=21009,
02/11/09 10:55:39 SST
* Started source agent on "/opt/IBM/PHSS_35385.depot" for
root@dwhsvr05, pid=21012, 02/11/09 10:55:40 SST
NOTE: The target "/opt/IBM/PHSS_35385.depot" currently open for
reading is a tape. pid=21012 02/11/09 10:55:40 SST
* Agent pid=21012 completed. 02/11/09 10:59:27 SST
* Agent pid=21009 completed. 02/11/09 10:59:28 SST
* Started install agent on "/" for root@dwhsvr05, pid=22632,
02/11/09 15:55:22 SST
* Started source agent on "/opt/IBM/PHSS_35385.depot" for
root@dwhsvr05, pid=22635, 02/11/09 15:55:23 SST
NOTE: The target "/opt/IBM/PHSS_35385.depot" currently open for
reading is a tape. pid=22635 02/11/09 15:55:23 SST
* Agent pid=22635 completed. 02/11/09 15:57:18 SST
* Agent pid=22632 completed. 02/11/09 15:57:19 SST
* Started install agent on "/" for root@dwhsvr05, pid=23269,
02/12/09 18:59:30 SST
* Started source agent on "/home/ibmadm1/PHSS_35385.depot" for
root@dwhsvr05, pid=23272, 02/12/09 18:59:31 SST
NOTE: The target "/home/ibmadm1/PHSS_35385.depot" currently open for
reading is a tape. pid=23272 02/12/09 18:59:31 SST
swagentd.log (93%) * Agent pid=23272 completed. 02/12/09 19:01:04 SST
* Agent pid=23269 completed. 02/12/09 19:01:05 SST
swagentd.log: END
Problems are common to all, but attitude makes the difference
sujit kumar singh
Honored Contributor

Re: swinstall error failed Disk Space Analysis for PHSS_35385 linker patch

Hi Johnson,


cant say really as the Disk analysis shows but are there any big open files on /var/ and/or /usr that is not reflecting in here.

as an alternative could you try installing the Superseeding patches for PHSS_35385

that is PHSS_38154 or PHSS_39077.


though nothing seems to be coming in the swagentd logs as being generated speciafically for the Space Analysis.(or might be i Overlooked!!)


as evident from the Logs there is no dependency issue as the dependant patch is already on the system


regards
sujit
TTr
Honored Contributor

Re: swinstall error failed Disk Space Analysis for PHSS_35385 linker patch

What you attached above is the swagentd.log file. This does not show the errors. You need to look in the swinstall.log file and find "failed Disk Space Analysis" text and see what else is mentioned in there.
Ganesan R
Honored Contributor

Re: swinstall error failed Disk Space Analysis for PHSS_35385 linker patch

Hi Johnson,

You need to provide the swagent.log not swagentd.log. It's typo on my previous post.

Provide the portion which descripes the PHSS_35385 installation logs.
Best wishes,

Ganesh.
TTr
Honored Contributor

Re: swinstall error failed Disk Space Analysis for PHSS_35385 linker patch

I wonder why the var filesystem shows up with two slashes " //var " in the swinstal screen. Check the bdf output and /etc/fstab to see if there is a problem. Multiple slashes in a path string are treated as one and you can still navigate the filesystem but if you have two slashes in /etc/fstab, swinstall might get confused.
Dennis Handly
Acclaimed Contributor

Re: swinstall error failed Disk Space Analysis for PHSS_35385 linker patch

Simply tell swinstall to mind its own business:
swinstall -x enforce_dsa=false -x mount_all_filesystems=false -s $PWD/PHSS_35385.depot \*

Unfortunately this isn't something to do lightly. TTr may have the solution?