I am also having this exact same problem. The only diff is that it does not take a long period of time for us to fix. We can simply service winbind restart and the problem is fixed with in seconds. This has happened twice just this week, and has been happening about once per week since we started using Ubuntu. We were previously on a FreeBSD system that was not using AD for authentication. I have looked in the log.winbind and in the winbind.log nothing of much help is found there.
The following message is repeated over and over in winbind.log: [2010/10/29 05:37:07, 1] winbindd/winbindd_util.c:303(trustdom_recv) Could not receive trustdoms This message begins at the same time the service becomes unavailable. I know this because we have Nagios setup to monitor and we get alerts from Nagios that correlate with the logs. The only messages found in log.winbind are the messages that show we started the service: => zcat log.winbindd.1.gz [2010/10/25 08:01:07, 0] winbindd/winbindd.c:1252(main) winbindd version 3.4.7 started. Copyright Andrew Tridgell and the Samba Team 1992-2009 => cat log.winbindd [2010/10/29 07:46:28, 0] winbindd/winbindd.c:1252(main) winbindd version 3.4.7 started. Copyright Andrew Tridgell and the Samba Team 1992-2009 I am not seeing any core files in /var/log/samba/cores/* -- winbind crashes https://bugs.launchpad.net/bugs/667269 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
