Bug#574144: It used to work on winbind 3.4.2

2010-03-17 Thread Castan Eric
Hello, I need to say that I have held the winbind package on some other lenny nodes. On nodes on which winbind version 2:3.4.2-1~bpo50+3 is running, the above problem does not occur, and for me it is more stable.

Bug#574144: Just created the bug report at samba

2010-03-17 Thread Castan Eric
As per you advice, I reported this bug upstream https://bugzilla.samba.org/show_bug.cgi?id=7259 I let you know what's going on Best regards, Eric

Bug#574144: winbind: Winbind eventually locks forever if one of ActiveDirectory refuses all connections

2010-03-16 Thread Castan Eric
Package: winbind Version: 2:3.4.7~dfsg-1~bpo50+1 Severity: important Due to a misconfiguration, we resulted with the following situation: - 3 active directory servers working perfectly - 1 active directory server up, but all ports being blocked by the firewall It appears that this makes winbind

Bug#556536: winbind segfaults many time per second

2010-01-04 Thread Castan Eric
Hello all, I should also add that I have lenny hosts (2.6.26-2-686) where I use winbind from backports (3.4.3-1~bpo50+2). I have two domains: A - one which is controlled by a windows 2008 r2 english-based server B - one which is controlled by a windows 2003 sp2 french-based server On domain

Bug#553923: winbind: idmap_rid cache becomes corrupted when mixing group and user queries

2009-11-02 Thread Castan Eric
Package: winbind Version: 2:3.2.5-4lenny7 Severity: important I have investigated a strange issue on a system not allowing users to login. It appeared that the winbind cache eventually got corrupt when mixing group queries and user queries. I am using the idmap_rid allocator. If one queries

Bug#553923: Winbind idmap solved by upgrading to 3.4

2009-11-02 Thread Castan Eric
I forgot to add that I tried packages from backports.org ( 2:3.4.2-1~bpo50+3 ) and the problem does not exist any more in samba 3.4

Bug#539882: nagios3: workhours timeperiod schedules check for next year

2009-08-04 Thread Castan Eric
Package: nagios3 Version: 3.0.6-4~lenny2 Severity: normal As reported in http://tracker.nagios.org/view.php?id=31, setting workhours-like timeperiods as check_periods may result in checks being scheduled for the next year instead of the next day. It seems that there is no other workaround but