- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Problem with ServiceGuard Patch aftr doing pat...
Operating System - HP-UX
1753819
Members
9202
Online
108805
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-15-2009 11:03 AM
01-15-2009 11:03 AM
Problem with ServiceGuard Patch aftr doing patching
We recieved the follow erro after doing upgrades to 12/07 on our HP-UX 11.23 clustered
server:
root@dbh1p031-/home/mularps#./update-2008v12.sh
### Cleanup program started at 01/15/09 11:15:17
Cleanup of patch_states on 'dbh1p031'.
Obtaining patch_state information from the Installed Product Database ...done.
The following patch filesets have an incorrect patch_state attribute,
based on the 'superseded_by' attribute in the Installed Product
Database and the contents of the /var/adm/sw/save directory:
Patch Fileset Current patch_state Correct patch_state
=========================== =================== ===================
PHSS_32740.CM-CORE-COM applied committed
Correcting committed patch_states in the IPD ...done.
All information has been logged to /var/adm/cleanup.log.
### Cleanup program completed at 01/15/09 11:15:17
### Cleanup program started at 01/15/09 11:15:22
Commit patches superseded at least 2 time(s) on 'dbh1p031'.
Obtaining superseded patch information...done.
No non-committed patches superseded at least 2 time(s) are present.
All information has been logged to /var/adm/cleanup.log.
### Cleanup program completed at 01/15/09 11:15:22
======= 01/15/09 11:15:25 CST BEGIN swremove SESSION
(non-interactive) (jobid=dbh1p031-0113)
* Session started for user "root@dbh1p031".
* Beginning Selection
* Target connection succeeded for "dbh1p031:/".
* Software selections:
SysFaultMgmt,r=B.01.00.10.02,a=HP-UX_B.11.23_IA/PA,v=HP
SFM-CORE.CTR_PRO_COMM,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=HP-
UX_B.11.23_IA/PA
SFM-CORE.CTR_PRO_COREPA,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=H
P-UX_B.11.23_PA
SFM-CORE.EMT_COMM,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=HP-UX_B
.11.23_IA/PA
SFM-CORE.EMT_COREPA,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=HP-UX
_B.11.23_PA
SFM-CORE.EVWEB_COMM,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=HP-UX
_B.11.23_IA/PA
SFM-CORE.EVWEB_COREPA,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=HP-
UX_B.11.23_PA
SFM-CORE.EVWEB_DOC,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=HP-UX_
B.11.23_IA/PA
SFM-CORE.EVWEB_GUI_COMM,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=H
P-UX_B.11.23_IA/PA
SFM-CORE.EVWEB_GUI_PA,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=HP-
UX_B.11.23_PA
SFM-CORE.EVWEB_MAN,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=HP-UX_
B.11.23_IA/PA
SFM-CORE.FMD_PRO_COMM,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=HP-
UX_B.11.23_IA/PA
SFM-CORE.FMD_PRO_COREPA,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=H
P-UX_B.11.23_PA
SFM-CORE.GS_COMM,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=HP-UX_B.
11.23_IA/PA
SFM-CORE.GS_COREPA,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=HP-UX_
B.11.23_PA
SFM-CORE.HAS-PA,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=HP-UX_B.1
1.23_PA
SFM-CORE.HS_PRO_COREPA,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=HP
-UX_B.11.23_PA
SFM-CORE.MISC_COMM,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=HP-UX_
B.11.23_IA/PA
SFM-CORE.MISC_COREPA,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=HP-U
X_B.11.23_PA
SFM-CORE.SFM_PRO_COMM,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=HP-
UX_B.11.23_IA/PA
SFM-CORE.SFM_PRO_PA,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=HP-UX
_B.11.23_PA
SFMDB.SMPGSQL-DOC,l=/opt/sfmdb/pgsql,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.0
0.10,fa=HP-UX_B.11.23_IA/PA
SFMDB.SMPGSQL-INC,l=/opt/sfmdb/pgsql,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.0
0.10,fa=HP-UX_B.11.23_IA/PA
SFMDB.SMPGSQL-LIB,l=/opt/sfmdb/pgsql,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.0
0.10,fa=HP-UX_B.11.23_PA
SFMDB.SMPGSQL-MAN,l=/opt/sfmdb/pgsql,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.0
0.10,fa=HP-UX_B.11.23_IA/PA
SFMDB.SMPGSQL-RUN,l=/opt/sfmdb/pgsql,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.0
0.10,fa=HP-UX_B.11.23_PA
SFMDB.SMPGSQL-SHA,l=/opt/sfmdb/pgsql,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.0
0.10,fa=HP-UX_B.11.23_IA/PA
SFMDB.SMPGSQL-SRC,l=/opt/sfmdb/pgsql,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.0
0.10,fa=HP-UX_B.11.23_IA/PA
* Selection succeeded.
* Beginning Analysis
* Session selections have been saved in the file
"/home/mularps/.sw/sessions/swremove.last".
* "dbh1p031:/": There will be no attempt to mount filesystems
that appear in the filesystem table.
* Analysis succeeded.
* Beginning Execution
* The execution phase succeeded for "dbh1p031:/".
* Execution succeeded.
NOTE: More information may be found in the agent logfile using the
command "swjob -a log dbh1p031-0113 @ dbh1p031:/".
======= 01/15/09 11:18:15 CST END swremove SESSION (non-interactive)
(jobid=dbh1p031-0113)
**********************************
ERROR: There are filesets which are not in a configured state. Look at the
output of "swlist -l fileset -a state | grep -v -e configured -e ^#"
and fix the issues. Corrupt or transient filesets are especially
difficult to fix, but will really make a mess of the system during
an update. Save yourself some trouble and correct it now.
root@dbh1p031-/home/mularps#swlist -l fileset -a state|grep -v -e configured -e ^#
Cluster-Monitor.CM-CORE-COM corrupt
PHSS_32740.CM-CORE-COM transient
< -l fileset -a install_source Cluster-Monitor.CM-CORE-COM PHSS_32740.CM-CORE-COM
# Initializing...
# Contacting target "dbh1p031"...
#
# Target: dbh1p031:/
#
Cluster-Monitor.CM-CORE-COM
PHSS_32740.CM-CORE-COM
This is from swagent.log
======= 01/15/09 11:15:21 CST BEGIN swmodify SESSION
* Session started for user "root@dbh1p031.wi.gov".
* Source:
* Target: dbh1p031:/
* Software selections:
PHSS_32740.CM-CORE-COM
* Attribute selections:
patch_state=committed
* Beginning Selection Phase.
* Selection Phase succeeded.
* Beginning Analysis Phase.
* Analysis Phase succeeded.
* Beginning Modification Phase.
* Modifying the fileset "PHSS_32740.CM-CORE-COM".
* Modification Phase succeeded.
======= 01/15/09 11:15:22 CST END swmodify SESSION
======= 01/15/09 11:15:25 CST BEGIN remove AGENT SESSION (pid=904)
(jobid=dbh1p031-0113)
* Agent session started for user "root@dbh1p031.wi.gov".
(pid=904)
* Beginning Analysis Phase.
* Target: dbh1p031:/
* Target logfile: dbh1p031:/var/adm/sw/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".
* Summary of Analysis Phase:
* 27 of 27 filesets had no Errors or Warnings.
* The Analysis Phase succeeded.
* Beginning the Unconfigure Execution Phase.
* Filesets: 27
* Files: 1083
* Kbytes: 84498
* Removing bundle "SysFaultMgmt,l=/,r=B.01.00.10.02" .
* Running remove setup command /usr/lbin/sw/remove_setup.
NOTE: Removing Health State Provider module.
NOTE: Removing FMD Provider module.
NOTE: Removing SFM Provider module.
NOTE: EVWEB database Successfully removed on port 10864
* Deconfiguring EMT...
NOTE: Could not remove CER database
* Deconfiguring provider...
* ...successful.
* EMT Provider deconfigured successfully.
* EMT GUI deconfigured successfully.
NOTE: EMT deconfigured successfully.
NOTE: Removing Control Provider module.
* Beginning the Remove Execution Phase.
* Removing fileset "SFM-CORE.HS_PRO_COREPA,l=/,r=B.01.00.10" (1
of 27).
* Removing fileset "SFM-CORE.FMD_PRO_COREPA,l=/,r=B.01.00.10" (2
of 27).
* Removing fileset "SFM-CORE.GS_COMM,l=/,r=B.01.00.10" (3 of
27).
* Removing fileset "SFM-CORE.GS_COREPA,l=/,r=B.01.00.10" (4 of
27).
* Removing fileset "SFM-CORE.HAS-PA,l=/,r=B.01.00.10" (5 of 27).
* Removing fileset "SFM-CORE.MISC_COMM,l=/,r=B.01.00.10" (6 of
27).
* Removing fileset "SFM-CORE.MISC_COREPA,l=/,r=B.01.00.10" (7 of
27).
* Removing fileset "SFM-CORE.SFM_PRO_COMM,l=/,r=B.01.00.10" (8
of 27).
* Removing fileset "SFM-CORE.SFM_PRO_PA,l=/,r=B.01.00.10" (9 of
27).
* Removing fileset "SFM-CORE.FMD_PRO_COMM,l=/,r=B.01.00.10" (10
of 27).
* Removing fileset "SFM-CORE.EVWEB_MAN,l=/,r=B.01.00.10" (11 of
27).
* Removing fileset "SFM-CORE.EVWEB_GUI_PA,l=/,r=B.01.00.10" (12
of 27).
* Removing fileset "SFM-CORE.EVWEB_GUI_COMM,l=/,r=B.01.00.10"
(13 of 27).
* Removing fileset "SFM-CORE.EVWEB_DOC,l=/,r=B.01.00.10" (14 of
27).
* Removing fileset "SFM-CORE.EVWEB_COREPA,l=/,r=B.01.00.10" (15
of 27).
· Removing fileset "SFM-CORE.EVWEB_COMM,l=/,r=B.01.00.10" (16 of
· 27).
· * Removing fileset "SFM-CORE.EMT_COREPA,l=/,r=B.01.00.10" (17 of
· 27).
· * Removing fileset "SFM-CORE.EMT_COMM,l=/,r=B.01.00.10" (18 of
· 27).
· * Removing fileset "SFM-CORE.CTR_PRO_COREPA,l=/,r=B.01.00.10"
· (19 of 27).
· * Removing fileset "SFM-CORE.CTR_PRO_COMM,l=/,r=B.01.00.10" (20
· of 27).
· * Removing fileset
· "SFMDB.SMPGSQL-SRC,l=/opt/sfmdb/pgsql,r=B.01.00.10" (21 of
· 27).
· * Removing fileset
· "SFMDB.SMPGSQL-MAN,l=/opt/sfmdb/pgsql,r=B.01.00.10" (22 of
· 27).
· * Removing fileset
· "SFMDB.SMPGSQL-DOC,l=/opt/sfmdb/pgsql,r=B.01.00.10" (23 of
· 27).
· * Removing fileset
· "SFMDB.SMPGSQL-INC,l=/opt/sfmdb/pgsql,r=B.01.00.10" (24 of
· 27).
· * Removing fileset
· "SFMDB.SMPGSQL-LIB,l=/opt/sfmdb/pgsql,r=B.01.00.10" (25 of
· "SFMDB.SMPGSQL-DOC,l=/opt/sfmdb/pgsql,r=B.01.00.10" (23 of
· 27).
· * Removing fileset
· "SFMDB.SMPGSQL-INC,l=/opt/sfmdb/pgsql,r=B.01.00.10" (24 of
· 27).
· * Removing fileset
· "SFMDB.SMPGSQL-LIB,l=/opt/sfmdb/pgsql,r=B.01.00.10" (25 of
· 27).
· * Removing fileset
· "SFMDB.SMPGSQL-RUN,l=/opt/sfmdb/pgsql,r=B.01.00.10" (26 of
· 27).
· * Removing fileset
· "SFMDB.SMPGSQL-SHA,l=/opt/sfmdb/pgsql,r=B.01.00.10" (27 of
· 27).
·
· * Summary of Execution Phase:
· * 27 of 27 filesets had no Errors or Warnings.
· * The Execution Phase succeeded.
·
·
· ======= 01/15/09 11:18:15 CST END remove AGENT SESSION (pid=904)
· (jobid=dbh1p031-0113)
server:
root@dbh1p031-/home/mularps#./update-2008v12.sh
### Cleanup program started at 01/15/09 11:15:17
Cleanup of patch_states on 'dbh1p031'.
Obtaining patch_state information from the Installed Product Database ...done.
The following patch filesets have an incorrect patch_state attribute,
based on the 'superseded_by' attribute in the Installed Product
Database and the contents of the /var/adm/sw/save directory:
Patch Fileset Current patch_state Correct patch_state
=========================== =================== ===================
PHSS_32740.CM-CORE-COM applied committed
Correcting committed patch_states in the IPD ...done.
All information has been logged to /var/adm/cleanup.log.
### Cleanup program completed at 01/15/09 11:15:17
### Cleanup program started at 01/15/09 11:15:22
Commit patches superseded at least 2 time(s) on 'dbh1p031'.
Obtaining superseded patch information...done.
No non-committed patches superseded at least 2 time(s) are present.
All information has been logged to /var/adm/cleanup.log.
### Cleanup program completed at 01/15/09 11:15:22
======= 01/15/09 11:15:25 CST BEGIN swremove SESSION
(non-interactive) (jobid=dbh1p031-0113)
* Session started for user "root@dbh1p031".
* Beginning Selection
* Target connection succeeded for "dbh1p031:/".
* Software selections:
SysFaultMgmt,r=B.01.00.10.02,a=HP-UX_B.11.23_IA/PA,v=HP
SFM-CORE.CTR_PRO_COMM,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=HP-
UX_B.11.23_IA/PA
SFM-CORE.CTR_PRO_COREPA,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=H
P-UX_B.11.23_PA
SFM-CORE.EMT_COMM,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=HP-UX_B
.11.23_IA/PA
SFM-CORE.EMT_COREPA,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=HP-UX
_B.11.23_PA
SFM-CORE.EVWEB_COMM,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=HP-UX
_B.11.23_IA/PA
SFM-CORE.EVWEB_COREPA,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=HP-
UX_B.11.23_PA
SFM-CORE.EVWEB_DOC,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=HP-UX_
B.11.23_IA/PA
SFM-CORE.EVWEB_GUI_COMM,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=H
P-UX_B.11.23_IA/PA
SFM-CORE.EVWEB_GUI_PA,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=HP-
UX_B.11.23_PA
SFM-CORE.EVWEB_MAN,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=HP-UX_
B.11.23_IA/PA
SFM-CORE.FMD_PRO_COMM,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=HP-
UX_B.11.23_IA/PA
SFM-CORE.FMD_PRO_COREPA,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=H
P-UX_B.11.23_PA
SFM-CORE.GS_COMM,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=HP-UX_B.
11.23_IA/PA
SFM-CORE.GS_COREPA,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=HP-UX_
B.11.23_PA
SFM-CORE.HAS-PA,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=HP-UX_B.1
1.23_PA
SFM-CORE.HS_PRO_COREPA,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=HP
-UX_B.11.23_PA
SFM-CORE.MISC_COMM,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=HP-UX_
B.11.23_IA/PA
SFM-CORE.MISC_COREPA,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=HP-U
X_B.11.23_PA
SFM-CORE.SFM_PRO_COMM,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=HP-
UX_B.11.23_IA/PA
SFM-CORE.SFM_PRO_PA,l=/,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.00.10,fa=HP-UX
_B.11.23_PA
SFMDB.SMPGSQL-DOC,l=/opt/sfmdb/pgsql,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.0
0.10,fa=HP-UX_B.11.23_IA/PA
SFMDB.SMPGSQL-INC,l=/opt/sfmdb/pgsql,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.0
0.10,fa=HP-UX_B.11.23_IA/PA
SFMDB.SMPGSQL-LIB,l=/opt/sfmdb/pgsql,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.0
0.10,fa=HP-UX_B.11.23_PA
SFMDB.SMPGSQL-MAN,l=/opt/sfmdb/pgsql,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.0
0.10,fa=HP-UX_B.11.23_IA/PA
SFMDB.SMPGSQL-RUN,l=/opt/sfmdb/pgsql,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.0
0.10,fa=HP-UX_B.11.23_PA
SFMDB.SMPGSQL-SHA,l=/opt/sfmdb/pgsql,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.0
0.10,fa=HP-UX_B.11.23_IA/PA
SFMDB.SMPGSQL-SRC,l=/opt/sfmdb/pgsql,r=B.01.00.10,a=HP-UX_B.11.23_IA/PA,v=HP,fr=B.01.0
0.10,fa=HP-UX_B.11.23_IA/PA
* Selection succeeded.
* Beginning Analysis
* Session selections have been saved in the file
"/home/mularps/.sw/sessions/swremove.last".
* "dbh1p031:/": There will be no attempt to mount filesystems
that appear in the filesystem table.
* Analysis succeeded.
* Beginning Execution
* The execution phase succeeded for "dbh1p031:/".
* Execution succeeded.
NOTE: More information may be found in the agent logfile using the
command "swjob -a log dbh1p031-0113 @ dbh1p031:/".
======= 01/15/09 11:18:15 CST END swremove SESSION (non-interactive)
(jobid=dbh1p031-0113)
**********************************
ERROR: There are filesets which are not in a configured state. Look at the
output of "swlist -l fileset -a state | grep -v -e configured -e ^#"
and fix the issues. Corrupt or transient filesets are especially
difficult to fix, but will really make a mess of the system during
an update. Save yourself some trouble and correct it now.
root@dbh1p031-/home/mularps#swlist -l fileset -a state|grep -v -e configured -e ^#
Cluster-Monitor.CM-CORE-COM corrupt
PHSS_32740.CM-CORE-COM transient
< -l fileset -a install_source Cluster-Monitor.CM-CORE-COM PHSS_32740.CM-CORE-COM
# Initializing...
# Contacting target "dbh1p031"...
#
# Target: dbh1p031:/
#
Cluster-Monitor.CM-CORE-COM
PHSS_32740.CM-CORE-COM
This is from swagent.log
======= 01/15/09 11:15:21 CST BEGIN swmodify SESSION
* Session started for user "root@dbh1p031.wi.gov".
* Source:
* Target: dbh1p031:/
* Software selections:
PHSS_32740.CM-CORE-COM
* Attribute selections:
patch_state=committed
* Beginning Selection Phase.
* Selection Phase succeeded.
* Beginning Analysis Phase.
* Analysis Phase succeeded.
* Beginning Modification Phase.
* Modifying the fileset "PHSS_32740.CM-CORE-COM".
* Modification Phase succeeded.
======= 01/15/09 11:15:22 CST END swmodify SESSION
======= 01/15/09 11:15:25 CST BEGIN remove AGENT SESSION (pid=904)
(jobid=dbh1p031-0113)
* Agent session started for user "root@dbh1p031.wi.gov".
(pid=904)
* Beginning Analysis Phase.
* Target: dbh1p031:/
* Target logfile: dbh1p031:/var/adm/sw/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".
* Summary of Analysis Phase:
* 27 of 27 filesets had no Errors or Warnings.
* The Analysis Phase succeeded.
* Beginning the Unconfigure Execution Phase.
* Filesets: 27
* Files: 1083
* Kbytes: 84498
* Removing bundle "SysFaultMgmt,l=/,r=B.01.00.10.02" .
* Running remove setup command /usr/lbin/sw/remove_setup.
NOTE: Removing Health State Provider module.
NOTE: Removing FMD Provider module.
NOTE: Removing SFM Provider module.
NOTE: EVWEB database Successfully removed on port 10864
* Deconfiguring EMT...
NOTE: Could not remove CER database
* Deconfiguring provider...
* ...successful.
* EMT Provider deconfigured successfully.
* EMT GUI deconfigured successfully.
NOTE: EMT deconfigured successfully.
NOTE: Removing Control Provider module.
* Beginning the Remove Execution Phase.
* Removing fileset "SFM-CORE.HS_PRO_COREPA,l=/,r=B.01.00.10" (1
of 27).
* Removing fileset "SFM-CORE.FMD_PRO_COREPA,l=/,r=B.01.00.10" (2
of 27).
* Removing fileset "SFM-CORE.GS_COMM,l=/,r=B.01.00.10" (3 of
27).
* Removing fileset "SFM-CORE.GS_COREPA,l=/,r=B.01.00.10" (4 of
27).
* Removing fileset "SFM-CORE.HAS-PA,l=/,r=B.01.00.10" (5 of 27).
* Removing fileset "SFM-CORE.MISC_COMM,l=/,r=B.01.00.10" (6 of
27).
* Removing fileset "SFM-CORE.MISC_COREPA,l=/,r=B.01.00.10" (7 of
27).
* Removing fileset "SFM-CORE.SFM_PRO_COMM,l=/,r=B.01.00.10" (8
of 27).
* Removing fileset "SFM-CORE.SFM_PRO_PA,l=/,r=B.01.00.10" (9 of
27).
* Removing fileset "SFM-CORE.FMD_PRO_COMM,l=/,r=B.01.00.10" (10
of 27).
* Removing fileset "SFM-CORE.EVWEB_MAN,l=/,r=B.01.00.10" (11 of
27).
* Removing fileset "SFM-CORE.EVWEB_GUI_PA,l=/,r=B.01.00.10" (12
of 27).
* Removing fileset "SFM-CORE.EVWEB_GUI_COMM,l=/,r=B.01.00.10"
(13 of 27).
* Removing fileset "SFM-CORE.EVWEB_DOC,l=/,r=B.01.00.10" (14 of
27).
* Removing fileset "SFM-CORE.EVWEB_COREPA,l=/,r=B.01.00.10" (15
of 27).
· Removing fileset "SFM-CORE.EVWEB_COMM,l=/,r=B.01.00.10" (16 of
· 27).
· * Removing fileset "SFM-CORE.EMT_COREPA,l=/,r=B.01.00.10" (17 of
· 27).
· * Removing fileset "SFM-CORE.EMT_COMM,l=/,r=B.01.00.10" (18 of
· 27).
· * Removing fileset "SFM-CORE.CTR_PRO_COREPA,l=/,r=B.01.00.10"
· (19 of 27).
· * Removing fileset "SFM-CORE.CTR_PRO_COMM,l=/,r=B.01.00.10" (20
· of 27).
· * Removing fileset
· "SFMDB.SMPGSQL-SRC,l=/opt/sfmdb/pgsql,r=B.01.00.10" (21 of
· 27).
· * Removing fileset
· "SFMDB.SMPGSQL-MAN,l=/opt/sfmdb/pgsql,r=B.01.00.10" (22 of
· 27).
· * Removing fileset
· "SFMDB.SMPGSQL-DOC,l=/opt/sfmdb/pgsql,r=B.01.00.10" (23 of
· 27).
· * Removing fileset
· "SFMDB.SMPGSQL-INC,l=/opt/sfmdb/pgsql,r=B.01.00.10" (24 of
· 27).
· * Removing fileset
· "SFMDB.SMPGSQL-LIB,l=/opt/sfmdb/pgsql,r=B.01.00.10" (25 of
· "SFMDB.SMPGSQL-DOC,l=/opt/sfmdb/pgsql,r=B.01.00.10" (23 of
· 27).
· * Removing fileset
· "SFMDB.SMPGSQL-INC,l=/opt/sfmdb/pgsql,r=B.01.00.10" (24 of
· 27).
· * Removing fileset
· "SFMDB.SMPGSQL-LIB,l=/opt/sfmdb/pgsql,r=B.01.00.10" (25 of
· 27).
· * Removing fileset
· "SFMDB.SMPGSQL-RUN,l=/opt/sfmdb/pgsql,r=B.01.00.10" (26 of
· 27).
· * Removing fileset
· "SFMDB.SMPGSQL-SHA,l=/opt/sfmdb/pgsql,r=B.01.00.10" (27 of
· 27).
·
· * Summary of Execution Phase:
· * 27 of 27 filesets had no Errors or Warnings.
· * The Execution Phase succeeded.
·
·
· ======= 01/15/09 11:18:15 CST END remove AGENT SESSION (pid=904)
· (jobid=dbh1p031-0113)
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-15-2009 12:12 PM
01-15-2009 12:12 PM
Re: Problem with ServiceGuard Patch aftr doing patching
Shalom,
swconfigure \*
You probably have some corrupt patches installed. The update seems to have failed. You may need to check back swjob logs to see what the issue is.
If the sdux database is not corrupt, you may wish to try a more current bi-annual patch set.
SEP
swconfigure \*
You probably have some corrupt patches installed. The update seems to have failed. You may need to check back swjob logs to see what the issue is.
If the sdux database is not corrupt, you may wish to try a more current bi-annual patch set.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP