Hi there, I manage a Samba installation which has been operating very well on Debian Wheezy for a number of years. Up until last week I was running 3.6.25, which (as always until now) I compiled myself. Because of the large number of changes in the recent security patches, I opted to try the Debian 'samba' and 'winbind' packages. I was a little horrified to find that Debian is still using 3.6.6 but that's mainly why I opted to compile Samba myself in the first place. Unfortunately the Debian supplied winbindd exits almost immediately after starting. The other daemons start and run without problem, and are serving files as I write. The Debian-supplied winbindd 3.6.6 log contains ... [2016/04/20 20:31:30.244591, 2] Processing section "[Planning]" [2016/04/20 20:31:30.244676, 2] Processing section "[Stores]" [2016/04/20 20:31:30.244762, 2] Processing section "[WIP]" [2016/04/20 20:31:30.244859, 2] Processing section "[printers]" .... [2016/04/20 20:31:30.245448, 2] added interface eth1 ip=fe80::230:48ff:feb1:ecc9%eth1 bcast=fe80::ffff:ffff:ffff:ffff%eth1 netmask=ffff:ffff:ffff:ffff:: [2016/04/20 20:31:30.245540, 2] added interface eth1 ip=192.168.0.250 bcast=192.168.0.255 netmask=255.255.255.0 [2016/04/20 20:31:30.245574, 2] added interface lo ip=::1 bcast=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff [2016/04/20 20:31:30.245608, 2] added interface lo ip=127.0.0.1 bcast=127.255.255.255 netmask=255.0.0.0 [2016/04/20 20:31:30.245698, 2] added interface eth1 ip=fe80::230:48ff:feb1:ecc9%eth1 bcast=fe80::ffff:ffff:ffff:ffff%eth1 netmask=ffff:ffff:ffff:ffff:: [2016/04/20 20:31:30.245744, 2] added interface eth1 ip=192.168.0.250 bcast=192.168.0.255 netmask=255.255.255.0 [2016/04/20 20:31:30.245778, 2] added interface lo ip=::1 bcast=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff [2016/04/20 20:31:30.245811, 2] added interface lo ip=127.0.0.1 bcast=127.255.255.255 netmask=255.0.0.0 [2016/04/20 20:31:30.246735, 0] initialize_winbindd_cache: clearing cache and re-creating with version number 2 [2016/04/20 20:31:30.272347, 2] Added domain BUILTIN S-1-5-32 [2016/04/20 20:31:30.288647, 2] Added domain PALATINE S-1-5-21-2517445876-862569013-3963427703 [2016/04/20 20:31:30.288745, 0] Could not fetch our SID - did we join? [2016/04/20 20:31:30.288774, 0] unable to initialize domain list Of course the join is OK, and winbindd from 3.6.25 has no problem with it. I'm currently running winbindd 3.6.25 with the Debian patched smbd and nmbd. Curiously enough the winbindd from 3.6.6 supplied by samba.org, before the Debian patches but again compiled by myself, also has no problem. If there's any knowledge Out There about this issue I should be very glad to hear it. -- 73, Ged.
On 20/04/16 20:51, G.W. Haywood wrote:> Hi there, > > I manage a Samba installation which has been operating very well on > Debian Wheezy for a number of years. Up until last week I was running > 3.6.25, which (as always until now) I compiled myself. Because of the > large number of changes in the recent security patches, I opted to try > the Debian 'samba' and 'winbind' packages. I was a little horrified > to find that Debian is still using 3.6.6 but that's mainly why I opted > to compile Samba myself in the first place. > > Unfortunately the Debian supplied winbindd exits almost immediately > after starting. The other daemons start and run without problem, and > are serving files as I write. The Debian-supplied winbindd 3.6.6 log > contains > ... > [2016/04/20 20:31:30.244591, 2] Processing section "[Planning]" > [2016/04/20 20:31:30.244676, 2] Processing section "[Stores]" > [2016/04/20 20:31:30.244762, 2] Processing section "[WIP]" > [2016/04/20 20:31:30.244859, 2] Processing section "[printers]" > .... > [2016/04/20 20:31:30.245448, 2] added interface eth1 > ip=fe80::230:48ff:feb1:ecc9%eth1 bcast=fe80::ffff:ffff:ffff:ffff%eth1 > netmask=ffff:ffff:ffff:ffff:: > [2016/04/20 20:31:30.245540, 2] added interface eth1 > ip=192.168.0.250 bcast=192.168.0.255 netmask=255.255.255.0 > [2016/04/20 20:31:30.245574, 2] added interface lo ip=::1 bcast=::1 > netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff > [2016/04/20 20:31:30.245608, 2] added interface lo ip=127.0.0.1 > bcast=127.255.255.255 netmask=255.0.0.0 > [2016/04/20 20:31:30.245698, 2] added interface eth1 > ip=fe80::230:48ff:feb1:ecc9%eth1 bcast=fe80::ffff:ffff:ffff:ffff%eth1 > netmask=ffff:ffff:ffff:ffff:: > [2016/04/20 20:31:30.245744, 2] added interface eth1 > ip=192.168.0.250 bcast=192.168.0.255 netmask=255.255.255.0 > [2016/04/20 20:31:30.245778, 2] added interface lo ip=::1 bcast=::1 > netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff > [2016/04/20 20:31:30.245811, 2] added interface lo ip=127.0.0.1 > bcast=127.255.255.255 netmask=255.0.0.0 > [2016/04/20 20:31:30.246735, 0] initialize_winbindd_cache: clearing > cache and re-creating with version number 2 > [2016/04/20 20:31:30.272347, 2] Added domain BUILTIN S-1-5-32 > [2016/04/20 20:31:30.288647, 2] Added domain PALATINE > S-1-5-21-2517445876-862569013-3963427703 > [2016/04/20 20:31:30.288745, 0] Could not fetch our SID - did we join? > [2016/04/20 20:31:30.288774, 0] unable to initialize domain list > > Of course the join is OK, and winbindd from 3.6.25 has no problem with > it. > I'm currently running winbindd 3.6.25 with the Debian patched smbd and > nmbd. > Curiously enough the winbindd from 3.6.6 supplied by samba.org, before > the > Debian patches but again compiled by myself, also has no problem. > > If there's any knowledge Out There about this issue I should be very > glad to hear it. >Can you post your smb.conf ? Also is there anything in the logs when winbindd dies ? If not, try raising the log level to 3 and try again. Rowland
On Wed, 2016-04-20 at 20:51 +0100, G.W. Haywood wrote:> Hi there, > > I manage a Samba installation which has been operating very well on > Debian Wheezy for a number of years. Up until last week I was > running > 3.6.25, which (as always until now) I compiled myself. Because of > the > large number of changes in the recent security patches, I opted to > try > the Debian 'samba' and 'winbind' packages. I was a little horrified > to find that Debian is still using 3.6.6 but that's mainly why I > opted > to compile Samba myself in the first place. > > Unfortunately the Debian supplied winbindd exits almost immediately > after starting. The other daemons start and run without problem, and > are serving files as I write. The Debian-supplied winbindd 3.6.6 log > contains> [2016/04/20 20:31:30.288745, 0] Could not fetch our SID - did we > join? > [2016/04/20 20:31:30.288774, 0] unable to initialize domain list > > Of course the join is OK, and winbindd from 3.6.25 has no problem > with it.Is that using the same private dir? Typically self-compiled binaries have very different paths than system packages. Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Catalyst IT http://catalyst.net.nz/services/samba