Kernel panic for unknown reason

Status
Not open for further replies.

nccsa186

Cadet
Joined
Feb 22, 2013
Messages
9
I'm getting kernel panics and I don't understand why. In /var/log/messages they always occur in three's, as below:

Aug 27 13:29:37 freenas smbd[37669]: [2014/08/27 13:29:37.455656, 0] ../source3/lib/util.c:785(smb_panic_s3)
Aug 27 13:29:37 freenas smbd[37669]: PANIC (pid 37669): num_bytes too large: 4294966797
Aug 27 13:29:37 freenas kernel: pid 37669 (smbd), uid 1001: exited on signal 10

I'm running linux freenas 9.2.1.5, with 8gb of ram:
[root@freenas] ~# sysctl hw.physmem
hw.physmem: 7937671168

In the /var/log/samba4/log.smbd the error is present there too, of course, always preceded by the null passwords warning.
[2014/08/19 17:29:00.236654, 1] ../source3/param/loadparm.c:3178(lp_do_parameter)
WARNING: The "null passwords" option is deprecated
[2014/08/19 17:29:00.241515, 0] ../source3/lib/util.c:785(smb_panic_s3)
PANIC (pid 46016): num_bytes too large: 4294966797
BUT the null passwords warning occurs elsewhere with no panic following, so that might be irrelevant.

Fortunately, my server does not have a lot of files on it yet; I looked through all the directories and I could not find a file of size 4294966797

I also searched these forums and could find no posts containing "num_bytes"--which might make my case special, which is never a good thing...

Any thoughts?
 

nccsa186

Cadet
Joined
Feb 22, 2013
Messages
9
I kept researching. I found someone on an ubuntu forum with the same problem:
http://ubuntuforums.org/showthread.php?t=2237583
He reports getting the error:
[2014/08/01 08:04:48.868528, 0] ../source3/lib/util.c:785(smb_panic_s3)
PANIC (pid 19119): num_bytes too large: 4294966797
What are the odds of the num_bytes being exactly the same?? I'm going to try to install a new samba and see if his solution works for me. I'll keep this post updated in case someone else has this problem in the future.
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
First I'd upgrade to 9.2.1.7. Anyone on 9.2.1.x should be on 9.2.1.7 because of a possible root exploit. This probably won't solve your problem, but it might.

Second, can you post the rest of the info on your system?
 
Status
Not open for further replies.
Top