Opened 6 years ago

Closed 4 years ago

#215 closed defect (wontfix)

Samba 3.5.x smbd and nmbd both trash tdb files after some time

Reported by: herwigb Owned by: diver
Priority: blocker Milestone: Samba Server for eCS (OS/2) 1.3.x
Component: Samba Server Core Version: Server 3.5.x
Keywords: unkillable broken tdb files Cc:

Description (last modified by herwigb)

Symptoms: 3.5.19 nmbd stops working after some arbitrary time. For smbd no mor new connection is accepted, while older one still work.

Looking into log.nmbd I see plenty of these:

[2013/03/15 11:40:54.862000,  0] lib/util_tdb.c:385(tdb_log)
  tdb(D:\MPTN\ETC/samba/lock/wins.tdb): tdb_rec_read bad magic 0xd9fee666 at offset=6392
[2013/03/15 11:40:54.888000,  0] lib/util_tdb.c:385(tdb_log)
  tdb(D:\MPTN\ETC/samba/lock/wins.tdb): tdb_rec_read bad magic 0x42424242 at offset=5384
[2013/03/15 11:40:54.925000,  0] lib/util_tdb.c:385(tdb_log)
  tdb(D:\MPTN\ETC/samba/lock/wins.tdb): tdb_oob len 1113543791 beyond eof at 24576
[2013/03/15 11:40:54.925000,  0] lib/util_tdb.c:385(tdb_log)
  tdb(D:\MPTN\ETC/samba/lock/wins.tdb): tdb_rec_read bad magic 0x0 at offset=6704

for smbd.exe log entries look very similar.

Result is: nmbd.exe process is unkillable and smbd does not accept any new connection.

This problem also affects the client.

Attachments (1)

log_nmbd.zip (3.7 KB) - added by herwigb 6 years ago.
typical log

Download all attachments as: .zip

Change History (8)

Changed 6 years ago by herwigb

typical log

comment:1 Changed 6 years ago by herwigb

It appears this more critical - also smbd.exe is affected.

comment:2 Changed 6 years ago by herwigb

  • Description modified (diff)
  • Keywords broken tdb files added; nmbd removed
  • Priority changed from minor to blocker
  • Status changed from new to assigned
  • Summary changed from nmbd.exe in 3.5.19 stops working to Samba 3.5.x smbd and nmbd both trash tdb files after some time

comment:3 Changed 6 years ago by diver

try latest private build, as it has an important fix

comment:4 Changed 6 years ago by herwigb

http://lists.samba.org/archive/samba-technical/2006-October/049911.html

This thread might shed some light on the problem.

comment:5 Changed 6 years ago by diver

it does not imho, as it does not give the reason and also no solution. imho we still have no clue why it happens and when exactly.

comment:6 Changed 5 years ago by diver

we are still working on that problem.

comment:7 Changed 4 years ago by diver

  • Resolution set to wontfix
  • Status changed from assigned to closed

as samba 3.5 is considered dead, close this ticket in favor of #208.

Note: See TracTickets for help on using tickets.