Register for the iXsystems Community to get an ad-free experience and exclusive discounts in our eBay Store.

SMBD INTERNAL ERROR/PANIC - TrueNAS-12.0-U1

merrellb

Newbie
Joined
Dec 14, 2020
Messages
1
I recently upgraded from FreeNAS 11 to TrueNAS 12.0 and have noticed that SMBD keeps crashing every few minutes under very minimal load. Possibly relevant logs:

/var/log/samba4/log.smbd

[2020/12/14 11:05:37.345113, 0] ../../lib/util/fault.c:79(fault_report)
===============================================================
[2020/12/14 11:05:37.345206, 0] ../../lib/util/fault.c:80(fault_report)
INTERNAL ERROR: Signal 11 in pid 39227 (4.12.9)
If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting
[2020/12/14 11:05:37.345290, 0] ../../lib/util/fault.c:86(fault_report)
===============================================================
[2020/12/14 11:05:37.345345, 0] ../../source3/lib/util.c:830(smb_panic_s3)
PANIC (pid 39227): internal error
[2020/12/14 11:05:37.347410, 0] ../../lib/util/fault.c:265(log_stack_trace)
BACKTRACE: 6 stack frames:
#0 0x801296217 <log_stack_trace+0x37> at /usr/local/lib/samba4/libsamba-util.so.0
#1 0x802f9b656 <smb_panic_s3+0x56> at /usr/local/lib/samba4/libsmbconf.so.0
#2 0x801296007 <smb_panic+0x17> at /usr/local/lib/samba4/libsamba-util.so.0
#3 0x8012963ee <log_stack_trace+0x20e> at /usr/local/lib/samba4/libsamba-util.so.0
#4 0x801295fe9 <fault_setup+0x59> at /usr/local/lib/samba4/libsamba-util.so.0
#5 0x8099dbc20 <_pthread_sigmask+0x530> at /lib/libthr.so.3
[2020/12/14 11:05:37.347698, 0] ../../source3/lib/dumpcore.c:315(dump_core)
dumping core in /var/db/system/cores


/var/log/messages

Dec 14 10:42:54 threenas kernel: pid 38893 (smbd), jid 0, uid 0: exited on signal 6
Dec 14 10:42:59 threenas kernel: pid 38894 (smbd), jid 0, uid 0: exited on signal 6
Dec 14 10:43:07 threenas kernel: pid 38895 (smbd), jid 0, uid 0: exited on signal 6
Dec 14 10:47:27 threenas kernel: pid 38906 (smbd), jid 0, uid 0: exited on signal 6
Dec 14 10:47:37 threenas kernel: pid 38974 (smbd), jid 0, uid 0: exited on signal 6
Dec 14 10:47:49 threenas kernel: pid 38975 (smbd), jid 0, uid 0: exited on signal 6
Dec 14 11:04:45 threenas kernel: pid 39193 (smbd), jid 0, uid 0: exited on signal 6
Dec 14 11:05:37 threenas kernel: pid 39227 (smbd), jid 0, uid 0: exited on signal 6
 

anodos

Sambassador
iXsystems
Joined
Mar 6, 2014
Messages
7,222
I recently upgraded from FreeNAS 11 to TrueNAS 12.0 and have noticed that SMBD keeps crashing every few minutes under very minimal load. Possibly relevant logs:

/var/log/samba4/log.smbd

[2020/12/14 11:05:37.345113, 0] ../../lib/util/fault.c:79(fault_report)
===============================================================
[2020/12/14 11:05:37.345206, 0] ../../lib/util/fault.c:80(fault_report)
INTERNAL ERROR: Signal 11 in pid 39227 (4.12.9)
If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting
[2020/12/14 11:05:37.345290, 0] ../../lib/util/fault.c:86(fault_report)
===============================================================
[2020/12/14 11:05:37.345345, 0] ../../source3/lib/util.c:830(smb_panic_s3)
PANIC (pid 39227): internal error
[2020/12/14 11:05:37.347410, 0] ../../lib/util/fault.c:265(log_stack_trace)
BACKTRACE: 6 stack frames:
#0 0x801296217 <log_stack_trace+0x37> at /usr/local/lib/samba4/libsamba-util.so.0
#1 0x802f9b656 <smb_panic_s3+0x56> at /usr/local/lib/samba4/libsmbconf.so.0
#2 0x801296007 <smb_panic+0x17> at /usr/local/lib/samba4/libsamba-util.so.0
#3 0x8012963ee <log_stack_trace+0x20e> at /usr/local/lib/samba4/libsamba-util.so.0
#4 0x801295fe9 <fault_setup+0x59> at /usr/local/lib/samba4/libsamba-util.so.0
#5 0x8099dbc20 <_pthread_sigmask+0x530> at /lib/libthr.so.3
[2020/12/14 11:05:37.347698, 0] ../../source3/lib/dumpcore.c:315(dump_core)
dumping core in /var/db/system/cores


/var/log/messages

Dec 14 10:42:54 threenas kernel: pid 38893 (smbd), jid 0, uid 0: exited on signal 6
Dec 14 10:42:59 threenas kernel: pid 38894 (smbd), jid 0, uid 0: exited on signal 6
Dec 14 10:43:07 threenas kernel: pid 38895 (smbd), jid 0, uid 0: exited on signal 6
Dec 14 10:47:27 threenas kernel: pid 38906 (smbd), jid 0, uid 0: exited on signal 6
Dec 14 10:47:37 threenas kernel: pid 38974 (smbd), jid 0, uid 0: exited on signal 6
Dec 14 10:47:49 threenas kernel: pid 38975 (smbd), jid 0, uid 0: exited on signal 6
Dec 14 11:04:45 threenas kernel: pid 39193 (smbd), jid 0, uid 0: exited on signal 6
Dec 14 11:05:37 threenas kernel: pid 39227 (smbd), jid 0, uid 0: exited on signal 6
Please PM me a debug. I believe this is fixed in 12.0-STABLE, I'll send you an updated ISO to test.
 

anodos

Sambassador
iXsystems
Joined
Mar 6, 2014
Messages
7,222
It appears I have the same problem, also in TrueNAS-12.0-U1.

Has this been fixed yet?
U1 is affected by the bug. It's been fixed in our stable branch, but version with fix has not been released. If you are stuck on U1 and can't roll back to release, feel free to PM me and I'll provide a dev snapshot with the fix in it.
 
Joined
Mar 10, 2017
Messages
5
Thanks for your prompt response!

I rolled back to 11.3-U5 without any issue, and will stay there till 12.0-U2 arrives. It's so great we have such effortless and reliable rollbacks!
 

Breit

Junior Member
Joined
Oct 4, 2016
Messages
12
Do you have "server multi channel support = yes" under auxiliary parameters in Services/SMB by any chance?
I have exactly the same problem if I switch multi channel support on under 12.0/12.0-U1. However under 11.3-U5 this runs smooth without any issues. Must be a bug in whatever version of Samba is used on 12.
 
Joined
Mar 10, 2017
Messages
5
Nope, I don't. I do however have quite a complex ACL structure, maybe it's related to that. Either way: I'll await 12.0-U2. Thanks for the suggestion!
 

hakayova

Junior Member
Joined
Jan 16, 2021
Messages
13
Hi all,

I recently installed TrueNAS core on a server I built and I am having the same issue. The first version of TrueNAS I installed was TrueNAS-12.0-U1. I upgraded it today to TrueNAS-12.0-U1.1 and then noticed recurrent smbd crashes. Therefore, I assume that I can only rollback to U1 but nothing else, which may not solve the problem according to @anodos's post above. I do not have any auxillary parameters set for smb service. Any guidance will be greatly appreciated.
 

TechOps

Neophyte
Joined
Dec 21, 2020
Messages
4
Hi all,

I recently installed TrueNAS core on a server I built and I am having the same issue. The first version of TrueNAS I installed was TrueNAS-12.0-U1. I upgraded it today to TrueNAS-12.0-U1.1 and then noticed recurrent smbd crashes. Therefore, I assume that I can only rollback to U1 but nothing else, which may not solve the problem according to @anodos's post above. I do not have any auxillary parameters set for smb service. Any guidance will be greatly appreciated.
Same here; I think we are just in a waiting game for U2..
 

flotpg

Junior Member
Joined
Dec 21, 2017
Messages
15
My temporary fix until U2 is release > disable smb multichannel (server multi channel support = no) on TrueNAS SMB service.
 
Last edited:

CubicSphere

Neophyte
Joined
Sep 7, 2020
Messages
6
I also have the same issue. 12.0-RELEASE was working fine until I upgraded to U1.1. The only parameter I have for the SMB service is smb encrypt = mandatory.

Is it safe to rollback from U1.1 to 12.0-RELEASE?
 

CubicSphere

Neophyte
Joined
Sep 7, 2020
Messages
6
I've tried it following your previous post and that didn't fix the issue. Perhaps it's due to the smb encrypt = mandatory parameter in some of the shares... I rolled back to 12.0-RELEASE and the problem is fixed. Since the bug that U1.1 fixes appears only for block storage and I have all the data backed up elsewhere, I'm thinking about waiting for U2.
 

anodos

Sambassador
iXsystems
Joined
Mar 6, 2014
Messages
7,222
U1.1 became an OS fix for the ZFS bug mentioned in the release notes. The SMB fix was not present in the release. I can provide a custom update file for the SMB fixes for testing purposes. If you are interested in doing this, feel free to send me a PM.
 

Breit

Junior Member
Joined
Oct 4, 2016
Messages
12
It seems this problem is not directly related to server multi channel support being enabled. Allthough, I first noticed smbd crashes while having it enabled.
However, a few others here are having similiar problems with complex ACLs. After testing a few things, I noticed, that at least on my install I have similiar crashes of smbd with signal 6 when I try to access/list snapshots via VSS/Previous Versions on a SMB share in Windows 10.
I'm hoping all of this gets resolved with U2.
 

Borja Marcos

Member
Joined
Nov 24, 2014
Messages
108
Interesting. Yet I get the same errors at home, with no Windows clients and just several Macs doing Time Machine backups.

Maybe I should try to obtain a coredump as well.
 
Top