johnw <[email protected]> writes: > Hi, my samba server crash a lot, after upgrade from 4.1.x to 4.3/4.x > > (no problem before, running 4.1.x version) > > (my system is running amd64/current with samba package 4.4.3p0) > > I found some error message in "/var/log/samba/log.smbd" like this: > > [2016/05/28 09:37:30.217939, 0] ../source3/lib/util.c:791(smb_panic_s3) > PANIC (pid 27088): internal error > [2016/05/28 09:37:30.218145, 0] ../source3/lib/util.c:902(log_stack_trace) > BACKTRACE: 1 stack frames: > #0 0x18b8b840d51e <log_stack_trace+62> at > /usr/local/lib/libsmbconf.so.0.0 > > And "dmesg |grep signal" message like this: > > crash of smbd(69427) signal 6 > crash of smbd(47833) signal 6 > crash of smbd(79506) signal 6 > crash of smbd(18370) signal 6 > > I can not find any core dump file in /var/log/samba/cores/ and else where.
Yeah I don't think this part of the code works on OpenBSD, but we have a generic framework to achieve the same goal. For the setup see the last example in sysctl(8). > Attached testparm and /var/log/samba/log.smbd file here. > > Any idea, how to solve / debug? A gdb backtrace would help. doas gdb smbd /var/crash/smbd/something.core, type 'bt' BTW testparm is nice but it contains lots of extra data, it is a good thing to have its output plus the original smb.conf. -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
signature.asc
Description: PGP signature
