HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Why did our "system panic"
Operating System - HP-UX
1834449
Members
2284
Online
110067
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
Forums
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
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
10-29-2002 11:01 AM
10-29-2002 11:01 AM
Why did our "system panic"
On Oct. 24 2002 out system panic'd
root@HENUXAPA(sierra) # model; uname -a
9000/889/K460
HP-UX HENUXAPA B.10.20 A 9000/889 1256854371 two-user license
tail -10 /etc/shutdownlog
08:07 Sun Oct 13, 2002. Reboot:
08:09 Sun Oct 20, 2002. Reboot:
21:20 Thu Oct 24 2002. Reboot after panic: , isr.ior = 0'10240020.0'c0b03138
tail -50 /var/adm/syslog/OLDsyslog.log
Oct 24 21:18:42 HENUXAPA cmcld[1216]: Turning on safety time protection
Oct 24 21:18:42 HENUXAPA cmcld[1216]: 2 nodes have formed a new cluster, sequenc
e #13
Oct 24 21:18:42 HENUXAPA cmcld[1216]: The new active cluster membership is: HENU
XAPB, HENUXAPA
Oct 24 21:18:42 HENUXAPA cmlvmd[1217]: Clvmd initialized successfully.
Oct 24 21:18:45 HENUXAPA tldd[1148]: TLD(8) going to UP state
Oct 24 21:18:46 HENUXAPA cmclconfd[1215]: get_tcp_messages:receive != 0 fd=0
Oct 24 21:19:40 HENUXAPA syslog: /tools/patrol does not exist! Aborting Patrol.
Oct 24 21:20:40 HENUXAPA vmunix: vxfs: mesg 056: vx_dataioerr - /dev/vg00/lvol11
file system file data write error
Oct 24 21:20:40 HENUXAPA vmunix: vxfs: mesg 018: vx_idelxwri_done - /var/adm/cra
sh file system inode 8 had a write error at offset 4602992
Oct 24 21:20:40 HENUXAPA vmunix: vxfs: mesg 033: vx_check_badblock - /dev/vg00/l
vol11 file system had an I/O error, setting VX_FULLFSCK
Oct 24 21:20:40 HENUXAPA syslog: /tools/maestro does not exist! Aborting Maestro
.
Oct 24 21:21:40 HENUXAPA syslog: /tools/ConnectDirect does not exist! Aborting C
:D.
root@HENUXAPA(sierra) # model; uname -a
9000/889/K460
HP-UX HENUXAPA B.10.20 A 9000/889 1256854371 two-user license
tail -10 /etc/shutdownlog
08:07 Sun Oct 13, 2002. Reboot:
08:09 Sun Oct 20, 2002. Reboot:
21:20 Thu Oct 24 2002. Reboot after panic: , isr.ior = 0'10240020.0'c0b03138
tail -50 /var/adm/syslog/OLDsyslog.log
Oct 24 21:18:42 HENUXAPA cmcld[1216]: Turning on safety time protection
Oct 24 21:18:42 HENUXAPA cmcld[1216]: 2 nodes have formed a new cluster, sequenc
e #13
Oct 24 21:18:42 HENUXAPA cmcld[1216]: The new active cluster membership is: HENU
XAPB, HENUXAPA
Oct 24 21:18:42 HENUXAPA cmlvmd[1217]: Clvmd initialized successfully.
Oct 24 21:18:45 HENUXAPA tldd[1148]: TLD(8) going to UP state
Oct 24 21:18:46 HENUXAPA cmclconfd[1215]: get_tcp_messages:receive != 0 fd=0
Oct 24 21:19:40 HENUXAPA syslog: /tools/patrol does not exist! Aborting Patrol.
Oct 24 21:20:40 HENUXAPA vmunix: vxfs: mesg 056: vx_dataioerr - /dev/vg00/lvol11
file system file data write error
Oct 24 21:20:40 HENUXAPA vmunix: vxfs: mesg 018: vx_idelxwri_done - /var/adm/cra
sh file system inode 8 had a write error at offset 4602992
Oct 24 21:20:40 HENUXAPA vmunix: vxfs: mesg 033: vx_check_badblock - /dev/vg00/l
vol11 file system had an I/O error, setting VX_FULLFSCK
Oct 24 21:20:40 HENUXAPA syslog: /tools/maestro does not exist! Aborting Maestro
.
Oct 24 21:21:40 HENUXAPA syslog: /tools/ConnectDirect does not exist! Aborting C
:D.
Learn More
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-29-2002 11:00 AM
10-29-2002 11:00 AM
Re: Why did our "system panic"
Looks like you need to perhaps run fsck on the root lvols.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-29-2002 11:29 AM
10-29-2002 11:29 AM
Re: Why did our "system panic"
Hope this link helps...
http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000062925563
thx
Nag
http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000062925563
thx
Nag
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-29-2002 11:45 AM
10-29-2002 11:45 AM
Re: Why did our "system panic"
If you need to learn, now is the best opportunity
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP