SIGABRT

[Silvan Scherrer]

sometimes SMBD crash with a SIGABRT

[2012/02/27 16:39:29,  1] smbd/service.c:make_connection_snum(1138)
  workstation (192.168.0.112) connect to service D initially as user root (uid=0, gid=513) (pid 735)
[2012/02/27 16:39:31,  1] lib/util_tdb.c:tdb_wrap_log(886)
  tdb(C:\MPTN\ETC\samba\lock/locking.tdb): tdb_lock failed on list 6490 ltype=3 (Invalid argument)
[2012/02/27 16:39:31,  0] smbd/open.c:open_file_ntcreate_internal(1707)
  Could not get share mode lock
[2012/02/27 16:39:34,  1] lib/util_tdb.c:tdb_wrap_log(886)
  tdb(C:\MPTN\ETC\samba\lock/locking.tdb): tdb_lock failed on list -1 ltype=3 (Invalid argument)
[2012/02/27 16:39:34,  0] locking/locking.c:share_mode_lock_destructor(747)
  store returned NT_STATUS_UNSUCCESSFUL
[2012/02/27 16:39:34,  0] lib/util.c:smb_panic(1686)
  PANIC (pid 735): could not store share mode entry
[2012/02/27 16:39:34,  0] lib/util.c:log_stack_trace(1840)
  unable to produce a stack trace on this platform
[2012/02/27 16:39:34,  0] lib/fault.c:dump_core(235)
  dumping core in C:\MPTN\ETC/samba/log/cores/smbd

Killed by SIGABRT
pid=0x02df ppid=0x003b tid=0x0001 slot=0x00b4 pri=0x0400 mc=0x0001
C:\PROGRAMS\SAMBA\SMBD.EXE
Process dumping was disabled, use DUMPPROC / PROCDUMP to enable it.

[Silvan Scherrer]

Dmitriy could you produce a level 10 log with this error? i need the TDB_LOG as well and with level 0 or 1 those are not written.

[Peter Verweij]

I see this behavior also when making a backup. Have to kill the samba server, restart and then it works for a while. Put in the samba.conf log level = 10 but can't findthe tdb_log files. I have the following logs: log.nmbd log.smbd log.smbd..0.0.0.0 log.smbd.ibiza.192.168.1.100 the latest is very big. If you want them let me know. If there is a way to create the tdb_log I don't know how at the moment. Using the samba from april 2013.

[Silvan Scherrer]

on the tdb issues we are working atm. when this is done I believe this ticket is also resolved

[dmik]

this really looks like yet another case of a failed TDB operation. All TDB problems are fixed now with LIBCx so I'm closing this as I'm the reporter.