Opened 12 years ago
Last modified 10 years ago
#215 closed defect
Samba 3.5.x smbd and nmbd both trash tdb files after some time — at Version 2
Reported by: | Herwig Bauernfeind | Owned by: | Silvan Scherrer |
---|---|---|---|
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 )
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.
Change History (3)
by , 12 years ago
Attachment: | log_nmbd.zip added |
---|
comment:2 by , 12 years ago
Description: | modified (diff) |
---|---|
Keywords: | broken tdb files added; nmbd removed |
Priority: | minor → blocker |
Status: | new → assigned |
Summary: | nmbd.exe in 3.5.19 stops working → Samba 3.5.x smbd and nmbd both trash tdb files after some time |
Note:
See TracTickets
for help on using tickets.
typical log