winbind looses connection to DC in 3.0.30

[Jens Nissen]

I have successfully joined a domain with Samba 3.0.30
But after approx. one or two hours, winbind looses
connection to the domain controller and users are not allowed
to connect shares.
After a 'killall winbindd' and restarting of winbind, the users
can connect to the shares again.

How can I work around this bug?

Configuration looks like this:

[global]
         dos charset = ISO-8859-1
         unix charset = ISO-8859-1
         display charset = ISO-8859-1
         workgroup = DOMAIN
         realm = DOMAIN.TEST
         server string = myserver
         interfaces = ixp0
         security = ADS
         allow trusted domains = No
         password server = sbs2000.domain.test
         private dir = /var/lib/adsamba/private
         passdb backend = tdbsam
         guest account = samba
         log level = 6
         log file = /var/log/adsamba/smblog.ad
         max log size = 0
         name resolve order = wins bcast host
         socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE
SO_RCVBUF=8192 SO_SNDBUF=8192
         load printers = No
         show add printer wizard = No
         preferred master = No
         local master = No
         domain master = No
         wins server = 192.168.1.4
         idmap uid = 1000-60000
         idmap gid = 1000-60000
         winbind enum users = Yes
         winbind enum groups = Yes
         winbind offline logon = Yes
         admin users = DOMAIN\\Administrator
         ea support = Yes
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

[Volker Lendecke]

On Fri, Jul 18, 2008 at 03:20:35PM +0200, Jens Nissen wrote:
> I have successfully joined a domain with Samba 3.0.30
> But after approx. one or two hours, winbind looses
> connection to the domain controller and users are not allowed
> to connect shares.
> After a 'killall winbindd' and restarting of winbind, the users
> can connect to the shares again.
>
> How can I work around this bug?

Can you please provide debug level 10 log files of winbindd
(log.winbindd and log.wb-DOMAIN)?

Thanks,

Volker


--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

[Jeremy Allison]

On Fri, Jul 18, 2008 at 03:20:35PM +0200, Jens Nissen wrote:
> I have successfully joined a domain with Samba 3.0.30
> But after approx. one or two hours, winbind looses
> connection to the domain controller and users are not allowed
> to connect shares.
> After a 'killall winbindd' and restarting of winbind, the users
> can connect to the shares again.
>
> How can I work around this bug?

Known bug. This is why we released 3.0.31 (sorry).

Jeremy.
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

[Jens Nissen]

Thanks Volker,

I think, we can close at least this thread for version 3.0.30 as I could
not reproduce the effect on 3.0.31. I will continue with testing on
3.0.31 and post the issues found on a new thread.

Kind regards,

Jens

Volker Lendecke wrote:

> On Fri, Jul 18, 2008 at 04:39:27PM +0200, Jens Nissen wrote:
>> Hello Volker,
>>
>> please find attached the log file for the whole session.
>>
>> As 300K compressed is a bit large, I am not posting to the group.
>> I didn't cut anything from the files, as I am not sure, what the the
>> important moment is.
>>
>> What I did to reproduce:
>> 1) I started Samba close to 16:00 with fresh log files, so you can see
>> the complete startup.
>>
>> 2) The Samba-Server is attached to my virtual Windows SBS Server 2000,
>> so to accelerate the issue, after testing some access to shares
>> from the CANDEO\\Administrator account (which was ok), I
>> simply stopped the virtual server.
>>
>> 3) At 16:27, I restarted the virtual server and tried to access my
>> shares several times - without success. I then logged out and back into
>>  the Windows account (as this sometimes solves problems), but to no  avail.
>>
>> 4) I then stopped Samba and got the whole bunch of log files!
>
> This is a bug that winbind tries to connect to itself.
> Jeremy Allison has done some work that went into 3.0.31
> which attempts to resolve this. The history of this is
> visible in https://bugzilla.samba.org/show_bug.cgi?id=5551.
> Before I try to solve a potentially already solved problem
> within 3.0.30, I would appreciate if you could try to
> reproduce it with 3.0.31.
>
> Thanks,
>
> Volker

--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba