Operating System - HP-UX
1834449 Members
2284 Online
110067 Solutions
New Discussion

Why did our "system panic"

 
Jerry Sims
Advisor

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.
Learn More
3 REPLIES 3
Ken Hubnik_2
Honored Contributor

Re: Why did our "system panic"

Looks like you need to perhaps run fsck on the root lvols.
Nag Varma
Advisor

Re: Why did our "system panic"

Anil C. Sedha
Trusted Contributor

Re: Why did our "system panic"

 
If you need to learn, now is the best opportunity