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.
Yes -- this is the best solution for now.
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.
192.168.18.2 goes down at 2:30 in the night after backup is complete.
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.
Ok -- I have to switch to newest kernel. Thank you for support and sorry for making so much trouble. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
