From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Description of problem:
The nmbd daemon segfaults when it is set up as a wins proxy..
Version 3.0.9 of samba update rpm for FC3..
I just upgraded our servers from RH9 to FC3 and found out that
the other server that is running as a wins proxy will not answer
to the nmblookup after about 20 second..
The problem seems to be that the nmbd gets signal 11..
The same setup works nicely if I just remove the
wins proxy = on line from the setup..
Before upgrade I had 3.0.9 rpm for RH9 on this machine with
exactly same setup and it has been running for months without
here is the dump from nmbd
INTERNAL ERROR: Signal 11 in pid 17484 (3.0.9-1.fc3)
Please read the appendix Bugs of the Samba HOWTO collection
PANIC: internal error
BACKTRACE: 16 stack frames:
#0 nmbd(smb_panic2+0x8a) [0x1eef3a]
#1 nmbd(smb_panic+0x19) [0x1ef167]
#2 nmbd [0x1da789]
#3 /lib/tls/libc.so.6 [0x49aa48]
#4 /lib/tls/libc.so.6 [0x4d475d]
#5 /lib/tls/libc.so.6(malloc+0x81) [0x4d61e1]
#6 nmbd(Realloc+0x95) [0x1edc1f]
#7 nmbd(convert_string_allocate+0x3d4) [0x1d8023]
#8 nmbd(push_ucs2_allocate+0x52) [0x1d8292]
#9 nmbd(push_ascii_nstring+0x30) [0x1d87e9]
#10 nmbd [0x196676]
#11 nmbd(find_workgroup_on_subnet+0x31) [0x196780]
#12 nmbd(sync_all_dmbs+0x45) [0x180039]
#13 nmbd(main+0x642) [0x17bf4f]
#14 /lib/tls/libc.so.6(__libc_start_main+0xe3) [0x487e33]
#15 nmbd [0x17a5b1]
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. setup one samba server as wins server
2. set another server as a wins proxy and point the wins server
address to the server you have set samba wins server
3. start samba on both servers
Actual Results: nmbd gets signall 11 and dies..
The same for me, on current FC3`s samba-3.0.10-1.fc3 .
Similar "panic" report was produced immediately after fc1->fc3 upgrade.
When I clear /var/cache/samba/* files, the "panic" is go away, but
the problem still exist -- see #144865
IMHO this is a dublicate of bug #144865
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
Actually, it is fixed since 3.0.14a ...
Closing as it is fixed