Your message dated Mon, 8 Dec 2008 18:41:19 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#436959: Moreinfo needed for this samba/winbind bug
has caused the Debian Bug report #436959,
regarding winbind hang & startup problem
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
436959: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=436959
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: winbind
Version: 3.0.24-6

I have a 2 very strange problems with winbind, and I think they are related that's why file only one bug report. The first issue is that when my machine boots, right after boot 'wbinfo -D {mydomain}' shows:

Name              : PHYSICS
Alt_Name          : Physics.xxxxxxxxxxxx
SID               : S-1-5-21-1818682373-3371831198-3922779086
Active Directory  : No
Native            : No
Primary           : Yes
Sequence          : -1

Although winbind works, it doesn't make sense as the machine is connected to a Windows2003 ADS Server. But the strange thing is that when I ie. issue '/etc/init.d/winbind restart' it shows:

Name              : PHYSICS
Alt_Name          : Physics.xxxxxxxxxxxx
SID               : S-1-5-21-1818682373-3371831198-3922779086
Active Directory  : Yes
Native            : Yes
Primary           : Yes
Sequence          : -1

Note that both "Active Directory" and "Native" now say Yes (as expected).

Another problem I experience (and I think it's related to the above issue) is that once in a while winbind stops responding, obviously causing users/groups not be resolved from the Windows2003 domain. 'wbinfo -p' then shows:

Ping to winbindd failed on fd -1
could not ping winbindd!

Although winbind is still running (ps -ef |grep winbind):

root      3730     1  0 19:50 ?        00:00:00 /usr/sbin/winbindd
root      3731  3730  0 19:50 ?        00:00:00 /usr/sbin/winbindd

Note that I haven't found a way (yet) to reproduce this problem, so it's quite hard to debug. The latter issue is (of course) the real show stopper as at that point my users are no longer able to access the machine until I issue another /etc/init.d/winbind restart.




--
Ing. A.C.J. van Amersfoort (Arno)
Department Of Electronics (ELD, k1007)
Huygens Laboratory
Leiden University
P.O. Box 9504
Niels Bohrweg 2
2333 CA Leiden
The Netherlands
----------------------------------------------------------------
Phone : +31-(0)71-527.1894   Fax: +31-(0)71-527.5819
E-mail: [EMAIL PROTECTED]
----------------------------------------------------------------
Arno's (Linux firewall) homepage: http://rocky.eld.leidenuniv.nl











--- End Message ---
--- Begin Message ---
Version: 2:3.2.5-1

Quoting Arno van Amersfoort ([EMAIL PROTECTED]):
> Dear Christian,
>
> Sorry that I didn't respond any time sooner. I've been really tied up at  
> work for a while and these emails tend to move to the bottom of my  
> mailbox. AFAIK the problem has been fixed upstream/with a newer Samba  
> version. I am now running Debian-Lenny on the same machine and the  
> problem seems solved.


Thanks for your answer. I'm therefore closing this bug report with
version tagging (conservative: I tag the bug as fixed in 3.2.5-1,
which is the version in lenny...:-))

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to