Binary package hint: samba
Occasionally on various Ubuntu 64-bit LucidLynx systems (10.04.1), winbind goes into a state such that logging in fails.
(we use ActiveDirectory for logging in. We do not use the Likewise-open product.)
Although, it appears that there are 1 or more winbindd processes running, they are all dead/not_working/hung, etc.
The only recourse to fix the problem, is that I log in with a local account that has sudo privilege, find and kill all the
winbindd processes, and restart, nmbd, winbindd and samba. (not sure if I need to restart nmbd and samba, but
I do it anyways.)
This problem seems to happen more often on systems that are shared with other users.
Some of those other users are connected from across the Wan via ssh.
The problem seems to occur more often over the weekend. Meaning, Monday morning,
is when we discover the machines are un-loginable with Active Directory account names.
This problem does not happen with all 80+ machines. All machines are built out the same,
and are on approximately the same type of hardware.
This problem has existed since the onset of LucidLynx from what I can remember.
The problem occurs frequently enough, that I had to set up a self-help web page for users with the
problem. From there I have a script that will log into the machine in question,
with a local sudo privileged account, kills all the winbind processes and restarts
nmbd, winbindd and samba.
Even with using the local account, each command takes about 2 1/2 minutes to complete.
It takes about 12 minutes to accomplish the "fixing" of the machine due to the # of commands that
need to be run.
I am assuming the core file under /var/log/samba/cores/winbindd/core
will be relevant to the problem I am having.
$ lsb_release -rd
Description: Ubuntu 10.04.1 LTS
Release: 10.04
$ apt-cache policy winbind
winbind:
Installed: 2:3.4.7~dfsg-1ubuntu3.2
Candidate: 2:3.4.7~dfsg-1ubuntu3.2
Version table:
*** 2:3.4.7~dfsg-1ubuntu3.2 0
500 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
500 http://security.ubuntu.com/ubuntu/ lucid-security/main Packages
100 /var/lib/dpkg/status
2:3.4.7~dfsg-1ubuntu3 0
500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages
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/
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 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 version 3.4.7 started.
Copyright Andrew Tridgell and the Samba Team 1992-2009
I am not seeing any core files in /var/log/