On Sun, Feb 19, 2006 at 11:40:25AM +0100, Leszek Dubiel wrote: > In the night nmbd got killed with signal 11. Here goes the log -- it > contains all lines starting from uprade-restart till restart next day > morning when workers told something is wrong. Orion is hostname of my > server, while Serwery is network group it stays in.
<snip> > [2006/02/18 00:30:05, 0] > nmbd/nmbd_nameregister.c:register_name_response(130) > register_name_response: server at IP 192.168.18.2 rejected our name > registration of SERWERY<1d> IP 192.168.18.1 with error code 6. > [2006/02/18 00:30:05, 0] > nmbd/nmbd_become_lmb.c:become_local_master_fail2(417) > become_local_master_fail2: failed to register name SERWERY<1d> on > subnet 192.168.18.1. Failed to become a local master browser. > [2006/02/18 00:30:05, 0] > nmbd/nmbd_become_lmb.c:become_local_master_fail2(417) > become_local_master_fail2: failed to register name SERWERY<1d> on > subnet 192.168.18.1. Failed to become a local master browser. > [2006/02/18 00:30:05, 0] > nmbd/nmbd_namelistdb.c:standard_success_release(384) > standard_success_release: Name release for name __MSBROWSE__<01> > IP 192.168.18.1 on subnet 192.168.18.1. Name was not found on subnet. > [2006/02/18 00:30:05, 0] > nmbd/nmbd_namelistdb.c:standard_fail_register(283) > standard_fail_register: Failed to register/refresh name SERWERY<1d> > on subnet 192.168.18.1 > [2006/02/18 00:30:05, 0] lib/fault.c:fault_report(36) > =============================================================== > [2006/02/18 00:30:05, 0] lib/fault.c:fault_report(37) > INTERNAL ERROR: Signal 11 in pid 28986 (3.0.14a-Debian) > Please read the appendix Bugs of the Samba HOWTO collection > [2006/02/18 00:30:05, 0] lib/fault.c:fault_report(39) > =============================================================== > [2006/02/18 00:30:05, 0] lib/util.c:smb_panic2(1485) <snip> > I think this error is not reproducible. I didn't get any email as defined > in panic_action. In the night I run backup procedure -- this is > "find | cpio | ssh" , and it started 2006/02/17 22:30, and it stopped > 2006/02/18 02:03. Serwer Delta (192.168.18.2) is the name of serwer which > is saving backup data. Orion has Ip 192.168.18.1. Since this bug seems to not be reproducible, it is likely that we won't be able to debug it based on this information. We can still hold the bug open for a while, in case the problem happens for you again. It's interesting to note that, once nmbd *was* restarted in the morning, this machine came up as the LMB; even though the server on 192.168.18.2 had been the LMB the night before. That seems a little unusual. Based on the logs, I guess you're also not likely to reproduce this error while ORION is the LMB, since the fault coincided with a failure to become LMB. > -- System Information: > Debian Release: 3.1 > Architecture: i386 (i686) > Kernel: Linux 2.4.18-686 > Locale: LANG=pl_PL, LC_CTYPE=pl_PL (charmap=ISO-8859-2) Incidentally, I don't think this is the cause of your problems, but please note that 2.4.18 is not a supported kernel version for sarge. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/
signature.asc
Description: Digital signature
