Page 1 of 1

Crash

PostPosted: Thu Nov 14, 2013 4:51 am
by phil_discount
Hello,

sometimes one of my servers a suddenly down, no ping, no picture on the monitor possible.
I only can reboot the server.

in messages i found the last log before crash
Code: Select all
Nov 14 03:00:02 gabcom2 kernel: [85733.813833] CIFS VFS: cifs_mount failed w/return code = -112
Nov 14 03:00:12 gabcom2 kernel: [85743.800078] CIFS VFS: Unexpected lookup error -112
Nov 14 03:00:22 gabcom2 kernel: [85753.992159] CIFS VFS: Unexpected lookup error -112
Nov 14 03:00:36 gabcom2 kernel: [85768.052024] BUG: soft lockup - CPU#0 stuck for 22s! [sh:28078]
Nov 14 03:00:36 gabcom2 kernel: [85768.052030] Modules linked in: dahdi crc_ccitt des_generic ecb md4 md5 nls_utf8 cifs cpufreq_conservative cpufreq_userspace cpufreq_powersave powernow_k8 mperf edd sr_mod cdrom ata_generic joydev pcspkr k10temp fam15h_power pata_atiixp sp5100_tco i2c_piix4 sg igb dca button autofs4 usbhid ohci_hcd ehci_hcd ssb usbcore mmc_core pcmcia pcmcia_core processor thermal_sys


some people in other forums told that i have to make a kernel update to fix the problem

ViciBox Redux v.4.0.3
I'm using Opensuse 12.1: Linux gabcom2 3.1.10-1.16-pae #1 SMP Wed Jun 27 05:21:40 UTC 2012 (d016078) i686 athlon i386 GNU/Linux

What do u mean, should i try a kernel update? or is it a problem.

regards
philip

Re: Crash

PostPosted: Fri Nov 15, 2013 4:41 am
by DomeDan
Don't mount windows shares on the server, try NFS instead if you have that option.

other than that.. a kernel upgrade hopefully will fix that bug,
take backup and do a "zypper refresh && zypper up" I guess you will get a new kernel after that

Re: Crash

PostPosted: Thu Nov 21, 2013 4:20 am
by phil_discount
i think that cannot be the problem, because i mount on every server a windows and linux share using cifs.
if i do a kernel update using zypper up - must asterisk/dahdi/vicidial be reinstalled?

Re: Crash

PostPosted: Wed Dec 04, 2013 11:20 am
by phil_discount
i will wait for the next crash and and read the logs .. i've got about 10 server with shares like this

Re: Crash

PostPosted: Wed Dec 04, 2013 3:16 pm
by williamconley
CPU#0 stuck for 22s
usually a bad cpu. swap it out into another machine and see if the problem follows it (or goes away .. ).