Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 2 subscribers
  • Views 3469 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Winbind daemon dies, restarts, dies, restarts, die

SalishSwede
I'm getting a continual loop on ASL 6.001

Here are the logs from the self-monitoring logs:

2005:07:23-02:08:27 (none) selfmonng[1021]: DEBUG: NOTIFYEVENT Name=winbindd_running Level=INFO Id=130 suppressed
2005:07:23-02:08:27 (none) selfmonng[1021]: triggerAction: 'cmd'
2005:07:23-02:08:27 (none) selfmonng[1021]: actionCmd(+): '/var/mdw/scripts/ntlm restart'
2005:07:23-02:08:29 (none) selfmonng[1021]: child returned status: exit='0' signal='0'
2005:07:23-02:08:34 (none) selfmonng[1021]: check Failed increment winbindd_running counter 1 - 3
2005:07:23-02:08:39 (none) selfmonng[1021]: check Failed increment winbindd_running counter 2 - 3
2005:07:23-02:08:44 (none) selfmonng[1021]: check Failed increment winbindd_running counter 3 - 3
2005:07:23-02:08:44 (none) selfmonng[1021]: DEBUG: NOTIFYEVENT Name=winbindd_running Level=INFO Id=130 suppressed
2005:07:23-02:08:44 (none) selfmonng[1021]: triggerAction: 'cmd'
2005:07:23-02:08:44 (none) selfmonng[1021]: actionCmd(+): '/var/mdw/scripts/ntlm restart'
2005:07:23-02:08:46 (none) selfmonng[1021]: child returned status: exit='0' signal='0'
2005:07:23-02:08:51 (none) selfmonng[1021]: check Failed increment winbindd_running counter 1 - 3
2005:07:23-02:08:56 (none) selfmonng[1021]: check Failed increment winbindd_running counter 2 - 3
2005:07:23-02:09:01 (none) selfmonng[1021]: check Failed increment winbindd_running counter 3 - 3
2005:07:23-02:09:01 (none) selfmonng[1021]: DEBUG: NOTIFYEVENT Name=winbindd_running Level=INFO Id=130 suppressed
2005:07:23-02:09:01 (none) selfmonng[1021]: triggerAction: 'cmd'
... 
this repeats endlessly 7x24x365

What's this all about?
Thanks.


This thread was automatically locked due to age.
Parents
  • 0
    I have exactly the same thing happening on my box and continually receive messages from the system saying "winbind daemon not running - restarted".
    Can someone enlighten me on why this is happening and how to stop it?
Reply
  • 0
    I have exactly the same thing happening on my box and continually receive messages from the system saying "winbind daemon not running - restarted".
    Can someone enlighten me on why this is happening and how to stop it?
Children
  • 0 in reply to BigO
    Maybe a configuration issue which leads to a not working winbindd?

    Have a look into /var/log.winbindd or maybe /var/log/xinetd.log and /var/log/fallback.log. Also it's possible to increase the logging of winbindd by editing /var/mdw/scrips/ntlm. change "winbindd" to "winbindd -d4".
    The logging will appear in /var/log.winbindd.

    Xeno
  • 0 in reply to Xeno
    The fallback log is huge.
    Every 10-15 seconds the following errors are logged:

    2005:08:10-00:10:26 (none) [daemon:err] winbindd[20108]: [2005/08/10 00:10:26, 0] param/params.c[:$]penConfFile(532)
    2005:08:10-00:10:26 (none) [daemon:err] winbindd[20108]:   params.c[:$]penConfFile() - Unable to open configuration file "/etc/samba/smb.conf":
    2005:08:10-00:10:26 (none) [daemon:err] winbindd[20108]:    No such file or directory
    2005:08:10-00:10:26 (none) [daemon:err] winbindd[20108]: [2005/08/10 00:10:26, 0] nsswitch/winbindd.c:main(846)
    2005:08:10-00:10:26 (none) [daemon:err] winbindd[20108]:   error opening config file

    Babysitting this system is a full time job!
Cookie Information Banner