Server reboot

Hi,

The server got rebooted and below messages can be seen in /var/log/messages

Sep  7 10:49:12 minersville kernel: Call Trace: <IRQ> <ffffffff80167420>{__alloc_pages+796}
Sep  7 10:49:12 minersville kernel:        <ffffffff80182814>{kmem_getpages+106} <ffffffff80183c16>{fallback_alloc+304}
Sep  7 10:49:12 minersville kernel:        <ffffffff8018411b>{__kmalloc+179} <ffffffff8028d4b7>{__alloc_skb+93}
Sep  7 10:49:12 minersville kernel:        <ffffffff880e3595>{:bnx2x:bnx2x_rx_int+4951} <ffffffff88294db6>{:bonding:bond_xmit_activebackup+86}
Sep  7 10:49:12 minersville kernel:        <ffffffff802c3496>{tcp_rcv_established+355} <ffffffff802c8f51>{tcp_v4_do_rcv+42}
Sep  7 10:49:12 minersville kernel:        <ffffffff880f4fcb>{:bnx2x:bnx2x_poll+180} <ffffffff802c76f2>{tcp_delack_timer+0}
Sep  7 10:49:12 minersville kernel:        <ffffffff802c77e9>{tcp_delack_timer+247} <ffffffff80293298>{net_rx_action+165}
Sep  7 10:49:12 minersville kernel:        <ffffffff8013a048>{__do_softirq+85} <ffffffff8010c1f6>{call_softirq+30}
Sep  7 10:49:12 minersville kernel:        <ffffffff8010d184>{do_softirq+44} <ffffffff8010d54e>{do_IRQ+64}
Sep  7 10:49:12 minersville kernel:        <ffffffff8010b332>{ret_from_intr+0} <EOI> <ffffffff80169a34>{__pagevec_release+0}
Sep  7 10:49:12 minersville kernel:        <ffffffff8016ad24>{shrink_zone+1379} <ffffffff802a1fa4>{__qdisc_run+54}
Sep  7 10:49:12 minersville kernel:        <ffffffff801fff25>{find_next_bit+96} <ffffffff8016c713>{try_to_free_pages+379}
Sep  7 10:49:12 minersville kernel:        <ffffffff801672d9>{__alloc_pages+469} <ffffffff8028d4d5>{__alloc_skb+123}
Sep  7 10:49:12 minersville kernel:        <ffffffff802bb33b>{tcp_sendmsg+1437} <ffffffff8028706e>{do_sock_write+201}
Sep  7 10:49:12 minersville kernel:        <ffffffff80287fc8>{sock_aio_write+72} <ffffffff80186985>{do_sync_write+199}
Sep  7 10:49:12 minersville kernel:        <ffffffff802f31b8>{do_page_fault+1018} <ffffffff801489d6>{autoremove_wake_function+0}
Sep  7 10:49:12 minersville kernel:        <ffffffff801872d1>{vfs_write+234} <ffffffff80187887>{sys_write+69}
Sep  7 10:49:12 minersville kernel:        <ffffffff8010ae16>{system_call+126}
Sep  7 10:49:12 minersville kernel: Mem-info:
Sep  7 10:49:12 minersville kernel: Node 0 DMA per-cpu:

Regards,
Vishal

Very interesting, but is there a question?

Was this an unexpected boot perhaps?

Robin

Hi Robin,

There were plenty of these messages which I copied in the last post and ultimately Oracle clusterware caused the node to evict

Sep  7 10:52:56 minersville logger: Oracle clsomon failed with fatal status 13.
Sep  7 10:52:57 minersville logger: Oracle CRS failure.  Rebooting for cluster integrity.

Regards

---------- Post updated at 12:42 PM ---------- Previous update was at 10:14 AM ----------

Anything on this please.

Regards,

Well, your cluster software has decided that something is so bad that the best option is to boot. I regret that there is not enough here to diagnose why. Have you reviewed the cluster software logs?