HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Panic Reboot without any record in shutdownlog
Operating System - HP-UX
1832343
Members
2266
Online
110041
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
Go to solution
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
07-30-2008 10:24 PM
07-30-2008 10:24 PM
Dear All,
We are using Oralce RAC10g on HP Integrity servers (HP-UX 11.23)
Sometimes Oracle CRS reboot the server in panic mode.
syslog before reboot :
Jul 29 17:04:07 servername syslog: Oracle CSSD failure 134.
Jul 29 17:04:07 servername syslog: Oracle CRS failure. Rebooting for cluster integrity.
Jul 29 17:04:12 servername syslog: Oracle clsomon failed with fatal status 12.
After rebooting there is no log in /etc/shutdownlog
But sometimes after Panic Reboots, shutdownlog is also indicating the reboot.
Actually we can not always refer to shutdownlog file to check the reboots.
Any idea?
We are using Oralce RAC10g on HP Integrity servers (HP-UX 11.23)
Sometimes Oracle CRS reboot the server in panic mode.
syslog before reboot :
Jul 29 17:04:07 servername syslog: Oracle CSSD failure 134.
Jul 29 17:04:07 servername syslog: Oracle CRS failure. Rebooting for cluster integrity.
Jul 29 17:04:12 servername syslog: Oracle clsomon failed with fatal status 12.
After rebooting there is no log in /etc/shutdownlog
But sometimes after Panic Reboots, shutdownlog is also indicating the reboot.
Actually we can not always refer to shutdownlog file to check the reboots.
Any idea?
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-30-2008 11:27 PM
07-30-2008 11:27 PM
Solution
Well if Oracle is rebnooting the box, it has been known to call reboot with a -q (or quiet) option. This reboots the server without leaving an entry in the shutdown log.
You should check with Oracle regarding this.
You should check with Oracle regarding this.
My house is the bank's, my money the wife's, But my opinions belong to me, not HP!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-31-2008 12:28 AM
07-31-2008 12:28 AM
Re: Panic Reboot without any record in shutdownlog
Shalom,
This is the equivalent of a serviceguard TOC.
Oracle is doing it. Oracle is responsible to log the cause.
Some criteria of the cluster configuration is leading Oracle to believe a split brain problem is coming up and that risks data corruption. So the node gets booted.
SEP
This is the equivalent of a serviceguard TOC.
Oracle is doing it. Oracle is responsible to log the cause.
Some criteria of the cluster configuration is leading Oracle to believe a split brain problem is coming up and that risks data corruption. So the node gets booted.
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP