- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- HP Proliant DL 180 G6 Continuously Automatic Resta...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Discussions
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
Community
Resources
Forums
Blogs
- 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
04-30-2017 08:03 AM
04-30-2017 08:03 AM
HP Proliant DL 180 G6 Continuously Automatic Restarting With Event ID 6008 and Event ID 41
Dear Sir;
I have server HP Proliant DL-180 G6 having windows server 2008 r2 Enterprise installed with Exchange 2010. My server is continually crashed and rebooting (Sometimes Halt and we have to manually restart and sometimes automatically restarts) . In Event viewer of Operating System Events ID: 6008 and Event ID: 41.
Event ID 41:
=============
Critical 29/04/2017 2:40:34 AM Kernel-Power 41 (63)
Critical 28/04/2017 4:07:14 PM Kernel-Power 41 (63)
Critical 28/04/2017 10:45:11 AM Kernel-Power 41 (63)
Critical 27/04/2017 4:06:57 PM Kernel-Power 41 (63)
Critical 27/04/2017 10:06:38 AM Kernel-Power 41 (63)
Critical 27/04/2017 5:02:19 AM Kernel-Power 41 (63)
Critical 26/04/2017 9:49:46 AM Kernel-Power 41 (63)
Critical 26/04/2017 6:42:30 AM Kernel-Power 41 (63)
Critical 25/04/2017 10:45:47 PM Kernel-Power 41 (63)
Critical 25/04/2017 11:10:46 AM Kernel-Power 41 (63)
Critical 23/04/2017 6:48:09 AM Kernel-Power 41 (63)
Critical 20/04/2017 1:34:40 PM Kernel-Power 41 (63)
Event ID 6008:
===========
Error 29/04/2017 2:41:25 AM EventLog 6008 None
Error 28/04/2017 10:45:55 AM EventLog 6008 None
Error 27/04/2017 4:07:37 PM EventLog 6008 None
I also checked ILO Logs Or BMC http server logs i found the following system event Log:
Generic
04/26/2017 06:42:36 Gen ID 0x41 C: boot completed Assertion OEM 04/26/2017 06:42:36 000137 00 3e 41 00 59 00 -- Generic 04/26/2017 09:49:50 Gen ID 0x41 C: boot completed Assertion OEM 04/26/2017 09:49:50 000137 00 21 6d 00 59 00 -- Generic 04/27/2017 04:40:09 Gen ID 0x41 Run-time Stop Assertion OEM 04/27/2017 04:40:09 000137 01 d1 00 00 00 01 -- OEM 04/27/2017 04:40:09 000137 02 00 00 7d bf 01 -- OEM 04/27/2017 04:40:09 000137 02 00 00 00 00 01 -- OEM 04/27/2017 04:40:09 000137 03 02 00 00 00 01 -- OEM 04/27/2017 04:40:09 000137 03 00 00 00 00 01 -- OEM 04/27/2017 04:40:09 000137 04 01 00 00 00 01 -- OEM 04/27/2017 04:40:09 000137 04 00 00 00 00 01 -- OEM 04/27/2017 04:40:09 000137 05 3d 7e 16 06 01 -- OEM 04/27/2017 04:40:09 000137 05 80 f8 ff ff 01 -- Generic 04/27/2017 05:02:24 Gen ID 0x41 C: boot completed Assertion OEM 04/27/2017 05:02:24 000137 00 43 7b 01 59 00 -- Generic 04/27/2017 09:44:46 Gen ID 0x41 Run-time Stop Assertion OEM 04/27/2017 09:44:46 000137 01 d1 00 00 00 01 -- OEM 04/27/2017 09:44:46 000137 02 00 00 7d bf 01 -- OEM 04/27/2017 09:44:46 000137 02 00 00 00 00 01 -- OEM 04/27/2017 09:44:46 000137 03 02 00 00 00 01 -- OEM 04/27/2017 09:44:46 000137 03 00 00 00 00 01 -- OEM 04/27/2017 09:44:46 000137 04 01 00 00 00 01 -- OEM 04/27/2017 09:44:46 000137 04 00 00 00 00 01 -- OEM 04/27/2017 09:44:46 000137 05 3d ce 16 06 01 -- OEM 04/27/2017 09:44:46 000137 05 80 f8 ff ff 01 -- Generic 04/27/2017 10:06:45 Gen ID 0x41 C: boot completed Assertion OEM 04/27/2017 10:06:45 000137 00 92 c2 01 59 00 -- Generic 04/27/2017 10:21:04 PS2 Status Power Supply Failure detected Assertion Generic 04/27/2017 10:21:04 PSRed Status Redundancy Lost Assertion Generic 04/27/2017 10:21:16 PSRed Status Full Redundancy Assertion Generic 04/27/2017 15:08:21 Gen ID 0x41 Run-time Stop Assertion OEM 04/27/2017 15:08:21 000137 01 d1 00 00 00 01 -- OEM 04/27/2017 15:08:21 000137 02 00 00 7d bf 01 -- OEM 04/27/2017 15:08:21 000137 02 00 00 00 00 01 -- OEM 04/27/2017 15:08:21 000137 03 02 00 00 00 01 -- OEM 04/27/2017 15:08:21 000137 03 00 00 00 00 01 -- OEM 04/27/2017 15:08:21 000137 04 01 00 00 00 01 -- OEM 04/27/2017 15:08:21 000137 04 00 00 00 00 01 -- OEM 04/27/2017 15:08:21 000137 05 3d ce 0e 06 01 -- OEM 04/27/2017 15:08:21 000137 05 80 f8 ff ff 01 -- Generic 04/27/2017 15:24:33 PS1 Status Power Supply Failure detected Assertion Generic 04/27/2017 15:24:33 PSRed Status Redundancy Lost Assertion Generic 04/27/2017 15:24:48 PS1 Status Power Supply Failure detected Assertion Generic 04/27/2017 15:25:47 PSRed Status Full Redundancy Assertion Generic 04/27/2017 15:26:07 PS1 Status Power Supply Failure detected Assertion Generic 04/27/2017 15:26:07 PSRed Status Redundancy Lost Assertion Generic 04/27/2017 15:26:18 PSRed Status Full Redundancy Assertion Generic 04/27/2017 16:07:03 Gen ID 0x41 C: boot completed Assertion OEM 04/27/2017 16:07:03 000137 00 07 17 02 59 00 -- Generic 04/27/2017 16:14:39 Gen ID 0x41 Unavailable Assertion OEM 04/27/2017 16:14:39 000137 00 ff 00 05 00 00 -- Generic 04/27/2017 17:13:52 Gen ID 0x41 C: boot completed Assertion OEM 04/27/2017 17:13:52 000137 00 b9 26 02 59 00 -- Generic 04/27/2017 18:54:14 Gen ID 0x41 Run-time Stop Assertion OEM 04/27/2017 18:54:14 000137 01 d1 00 00 00 01 -- OEM 04/27/2017 18:54:14 000137 02 00 00 7d bf 01 -- OEM 04/27/2017 18:54:14 000137 02 00 00 00 00 01 -- OEM 04/27/2017 18:54:14 000137 03 02 00 00 00 01 -- OEM 04/27/2017 18:54:14 000137 03 00 00 00 00 01 -- OEM 04/27/2017 18:54:14 000137 04 01 00 00 00 01 -- OEM 04/27/2017 18:54:14 000137 04 00 00 00 00 01 -- OEM 04/27/2017 18:54:14 000137 05 3d 5e 0c 06 01 -- OEM 04/27/2017 18:54:14 000137 05 80 f8 ff ff 01 -- Generic 04/28/2017 10:45:16 Gen ID 0x41 C: boot completed Assertion OEM 04/28/2017 10:45:16 000137 00 82 1c 03 59 00 -- Generic 04/28/2017 15:57:40 Gen ID 0x41 Unavailable Assertion OEM 04/28/2017 15:57:40 000137 00 ff 00 05 00 00 -- Generic 04/28/2017 15:58:42 PS2 Status Power Supply Failure detected Assertion Generic 04/28/2017 15:58:42 PSRed Status Redundancy Lost Assertion Generic 04/28/2017 16:07:20 Gen ID 0x41 C: boot completed Assertion OEM 04/28/2017 16:07:20 000137 00 96 68 03 59 00 -- Generic 04/29/2017 02:10:34 Gen ID 0x41 Run-time Stop Assertion OEM 04/29/2017 02:10:34 000137 01 50 00 00 00 01 -- OEM 04/29/2017 02:10:34 000137 02 00 80 9b 44 01 -- OEM 04/29/2017 02:10:34 000137 02 80 fa ff ff 01 -- OEM 04/29/2017 02:10:34 000137 03 01 00 00 00 01 -- OEM 04/29/2017 02:10:34 000137 03 00 00 00 00 01 -- OEM 04/29/2017 02:10:34 000137 04 45 0c 1c 06 01 -- OEM 04/29/2017 02:10:34 000137 04 80 f8 ff ff 01 -- OEM 04/29/2017 02:10:34 000137 05 00 00 00 00 01 -- OEM 04/29/2017 02:10:34 000137 05 00 00 00 00 01 -- Generic 04/29/2017 02:40:38 Gen ID 0x41 C: boot completed Assertion OEM 04/29/2017 02:40:38 000137 00 02 fd 03 59 00 --
Event due to this problem i can not take the backup because server restart becomes Halt or Restart before completing the windows backup utility. I am afraid that system can crashed anytime. Please help me in this regard.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-01-2017 05:19 AM
05-01-2017 05:19 AM
Re: HP Proliant DL 180 G6 Continuously Automatic Restarting With Event ID 6008 and Event ID 41
You didn't notice these?
>...Kernel-Power
>...PS2 Status Power Supply Failure detected...
>...PSRed Status Redundancy Lost Assertion Generic
Looks like one of your power supplies has failed and the server is running on one power supply only. This remaining power supply does not have enough power to run the server during peak processing times. and the server crashes because it's losing power. Your power supplies are probably too small to run in redundancy mode so that if one failed, the other could run the server by itself. So the server was using both power supplies in normal running mode.