Two days since systemboard replaced, and all is well.
Of course, I probably just jinxed it :-)
Best Regards,
*Dave Windsor*
Robert Bosch LLC
Team Leader, MES Database Infrastructure Group (AdP/TEF7.1)
4421 Highway 81 North
Anderson, SC 29621 USA
On 4/1/2011 1:44 PM, Windsor Dave L. (AdP/TEF7) wrote:
On 3/24/2011 11:03 AM, Windsor Dave L. (AdP/TEF7.1) wrote:
Hello Everyone,
I recently installed CentOS 5.5 x86_64 on a brand new ProLiant DL380 G7. I
have identical OS software running reock-solid on two other DL380 ProLiant
servers,
On 3/24/2011 11:03 AM, Windsor Dave L. (AdP/TEF7.1) wrote:
Hello Everyone,
I recently installed CentOS 5.5 x86_64 on a brand new ProLiant DL380 G7. I
have identical OS software running reock-solid on two other DL380 ProLiant
servers, but they are G6 models, not G7. On the G7, the
From: Dave Windsor dave.wind...@us.bosch.com
Today, there are not high I/O loads. This server was intended to
replace two older HP-UX servers. I had just begun to migrate the
workload to the new server when the crashes began to occur. There are
some minor, sporadic I/O loads but
On 03/24/2011 10:05 PM, Dr. Ed Morbius wrote:
You can create a timestamp cron job. Just a
*/10 * * * * root Logger --- TIMESTAMP ---
syslogd already has this buildin. It's normally disabled
by the -m 0 in /etc/sysconfig/syslog. Change the zero
to 10, restart syslogd and you get the same
On 3/25/2011 7:51 AM, John Doe wrote:
From: Dave Windsordave.wind...@us.bosch.com
Today, there are not high I/O loads. This server was intended to
replace two older HP-UX servers. I had just begun to migrate the
workload to the new server when the crashes began to occur. There are
Windsor Dave L. (AdP/TEF7) wrote:
On 3/25/2011 7:51 AM, John Doe wrote:
From: Dave Windsordave.wind...@us.bosch.com
Today, there are not high I/O loads. This server was intended to
replace two older HP-UX servers. I had just begun to migrate the
workload to the new server when the
on 13:18 Fri 25 Mar, Mogens Kjaer (m...@lemo.dk) wrote:
On 03/24/2011 10:05 PM, Dr. Ed Morbius wrote:
You can create a timestamp cron job. Just a
*/10 * * * * root Logger --- TIMESTAMP ---
syslogd already has this buildin. It's normally disabled
by the -m 0 in
Hello Everyone,
I recently installed CentOS 5.5 x86_64 on a brand new ProLiant DL380 G7. I
have identical OS software running reock-solid on two other DL380 ProLiant
servers, but they are G6 models, not G7. On the G7, the installation went
perfectly and the machine ran great for about 2
Windsor Dave L. (AdP/TEF7.1) wrote:
Hello Everyone,
I recently installed CentOS 5.5 x86_64 on a brand new ProLiant DL380 G7. I have
identical OS software running reock-solid on two other DL380 ProLiant servers, but they
are G6 models, not G7. On the G7, the installation went perfectly and
Le 24/03/2011 16:03, Windsor Dave L. (AdP/TEF7.1) a écrit :
Hello Everyone,
I recently installed CentOS 5.5 x86_64 on a brand new ProLiant DL380 G7. I have
identical OS software running reock-solid on two other DL380 ProLiant servers, but they
are G6 models, not G7. On the G7, the
On 3/24/2011 12:37 PM, Alain Péan wrote:
Le 24/03/2011 16:03, Windsor Dave L. (AdP/TEF7.1) a écrit :
snipped
Code: 00 00 00 00 00 00 00 00 70 4d 4f 9d 00 81 ff ff 98 e4 4b dc
RIP [8100dc435cf0]
RSP81001529fd18
CR2: 8100dc435cf0
0Kernel panic - not syncing: Fatal exception
Le 24/03/2011 18:30, Dave Windsor a écrit :
On 3/24/2011 12:37 PM, Alain Péan wrote:
Le 24/03/2011 16:03, Windsor Dave L. (AdP/TEF7.1) a écrit :
snipped
Code: 00 00 00 00 00 00 00 00 70 4d 4f 9d 00 81 ff ff 98 e4 4b dc
RIP [8100dc435cf0]
RSP81001529fd18
CR2: 8100dc435cf0
On 3/24/2011 1:44 PM, Alain Péan wrote:
Le 24/03/2011 18:30, Dave Windsor a écrit :
On 3/24/2011 12:37 PM, Alain Péan wrote:
Le 24/03/2011 16:03, Windsor Dave L. (AdP/TEF7.1) a écrit :
snipped
Code: 00 00 00 00 00 00 00 00 70 4d 4f 9d 00 81 ff ff 98 e4 4b dc
RIP [8100dc435cf0]
Windsor Dave L. (AdP/TEF7) wrote:
On 3/24/2011 1:44 PM, Alain Péan wrote:
Le 24/03/2011 18:30, Dave Windsor a écrit :
On 3/24/2011 12:37 PM, Alain Péan wrote:
Le 24/03/2011 16:03, Windsor Dave L. (AdP/TEF7.1) a écrit :
snipped
Code: 00 00 00 00 00 00 00 00 70 4d 4f 9d 00 81 ff ff 98 e4 4b dc
There are no error messages in any logs. For example, in
/var/log/messages, everything looks normal until you see the kernel
restart messages after the reboot, although there seems to be a long gap
in time between the last entry and the time when the systems actually
stopped and was
Greetings,
On 3/24/11, Windsor Dave L. (AdP/TEF7.1) dave.wind...@us.bosch.com wrote:
[80028905] vfs_stat_fd+0x1b/0x4a
My gut feeling would is that its hardware (i/o channel) .
imho
Regards,
Rajagopal
___
CentOS mailing list
Dave:
on 16:03 Thu 24 Mar, Windsor Dave L. (AdP/TEF7.1) (dave.wind...@us.bosch.com)
wrote:
Hello Everyone,
I recently installed CentOS 5.5 x86_64 on a brand new ProLiant DL380
G7. I have identical OS software running reock-solid on two other
DL380 ProLiant servers, but they are G6 models,
On 3/24/2011 2:27 PM, m.r...@5-cent.us wrote:
Windsor Dave L. (AdP/TEF7) wrote:
On 3/24/2011 1:44 PM, Alain Péan wrote:
Le 24/03/2011 18:30, Dave Windsor a écrit :
On 3/24/2011 12:37 PM, Alain Péan wrote:
Le 24/03/2011 16:03, Windsor Dave L. (AdP/TEF7.1) a écrit :
snipped
Code: 00 00 00
On 3/24/2011 4:38 PM, Dr. Ed Morbius wrote:
Dave:
on 16:03 Thu 24 Mar, Windsor Dave L. (AdP/TEF7.1) (dave.wind...@us.bosch.com)
wrote:
Hello Everyone,
Code: 00 00 00 00 00 00 00 00 70 4d 4f 9d 00 81 ff ff 98 e4 4b dc
RIP [8100dc435cf0]
RSP81001529fd18
CR2: 8100dc435cf0
on 16:56 Thu 24 Mar, Windsor Dave L. (AdP/TEF7) (dave.wind...@us.bosch.com)
wrote:
On 3/24/2011 4:38 PM, Dr. Ed Morbius wrote:
Dave:
on 16:03 Thu 24 Mar, Windsor Dave L. (AdP/TEF7.1)
(dave.wind...@us.bosch.com) wrote:
Hello Everyone,
Code: 00 00 00 00 00 00 00 00 70 4d 4f 9d 00 81
Dave,
Here's a thought: have you tried ipmitool?
mark
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
22 matches
Mail list logo
