On Sat, Feb 18, 2006 at 04:22:44PM +0100, Leszek Dubiel wrote: > *************************** > I have upgraded samba. /var/log/aptitude says:
> Aptitude 0.2.15.9: dziennik operacji > Fri Feb 17 17:42:54 2006 > [UAKTUALNIONY] samba 3.0.14a-3 -> 3.0.14a-3sarge1 > [UAKTUALNIONY] samba-common 3.0.14a-3 -> 3.0.14a-3sarge1 > [UAKTUALNIONY] samba-doc 3.0.14a-3 -> 3.0.14a-3sarge1 > [UAKTUALNIONY] smbclient 3.0.14a-3 -> 3.0.14a-3sarge1 > [UAKTUALNIONY] smbfs 3.0.14a-3 -> 3.0.14a-3sarge1 > ********************************* > In the night nmbd got killed with signal 11. Then you are following up to an unrelated bug. Please open a new report for this issue. > Here goes the log: > [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 ^A^B__MSBROWSE__^B<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) Did you get email with a backtrace as a result of this failure? The log messages prior to the fault don't suggest to me any reason for the fault; it's perfectly reasonable and expected for a server to not be the local master browser. Is this segfault reproducible? Again, please send your responses in a new bug report. -- 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
