samba - Dec 2018 - Winbindd (tdb_chainlock_with_timeout_internal: alarm (40) timed out for key)

Hi!

Thanks  for answer!

In future my plan is update, but this momento is no possible.. :-|

But, same error, in same time, in 3 server, is very strange....

Regards;


On 24-05-2018 15:38, Rowland Penny via samba wrote:
> On Thu, 24 May 2018 09:32:56 -0300
> Carlos via samba <samba at lists.samba.org> wrote:
>
>> Hi!
>>
>> I have 3 server:
>>
>> S.O. -  Debina 8
>>
>> Winbind Version : 2:4.2.10+dfsg-0+deb8u3
>>
>> Member Domain
>>
>> Samba Server : Ubuntu 14.04 with Samba 4.7.7 , are 18 Dcs
>>
>> ---------------------
>>
>>
>> In day 21/05 , the 3 server have same problema in same time, th
>> problem resolved after 40 minutes....
>>
>> Syslog server 1/2/3:
>>
>> May 21 08:14:12  winbindd[6718]: [2018/05/21 08:14:12.288624,  0]
>> ../source3/winbindd/winbindd_dual.c:105(child_write_response)
>> May 21 08:14:12  winbindd[6718]:   Could not write result
>> May 21 08:15:01  CRON[32667]: (root) CMD (command -v debian-sa1 >
>> /dev/null && debian-sa1 1 1)
>>
>> May 21 08:15:26  winbindd[28719]: [2018/05/21 08:15:26.341870,  0]
>> ../source3/winbindd/winbindd_dual.c:105(child_write_response)
>> May 21 08:15:26  winbindd[28719]:   Could not write result
>> May 21 08:15:30  winbindd[28808]: [2018/05/21 08:15:30.814572,  0]
>> ../source3/winbindd/winbindd_dual.c:105(child_write_response)
>> May 21 08:15:30  winbindd[28808]:   Could not write result
>> May 21 08:15:45  winbindd[32708]: [2018/05/21 08:15:45.545910,  0]
>> ../source3/lib/util_tdb.c:493(tdb_chainlock_with_timeout_internal)
>> May 21 08:15:45  winbindd[32708]:
>> tdb_chainlock_with_timeout_internal: alarm (40) timed out for key
>> DCXXX in tdb /var/run/samba/mutex.tdb May 21 08:15:45
>> winbindd[32708]: [2018/05/21 08:15:45.546208,
>> 0] ../source3/winbindd/winbindd_cm.c:918(cm_prepare_connection) May
>> 21 08:15:45  winbindd[32708]:   cm_prepare_connection: mutex grab
>> failed for DCXXXX
>>
>> May 21 08:16:47  winbindd[29020]: [2018/05/21 08:16:47.246684,  0]
>> ../source3/lib/util_tdb.c:493(tdb_chainlock_with_timeout_internal)
>> May 21 08:16:47  winbindd[29020]:
>> tdb_chainlock_with_timeout_internal: alarm (40) timed out for key
>> DCYYY in tdb /var/run/samba/mutex.tdb May 21 08:16:47
>> winbindd[29020]: [2018/05/21 08:16:47.246803,
>> 0] ../source3/winbindd/winbindd_cm.c:918(cm_prepare_connection) May
>> 21 08:16:47  winbindd[29020]:   cm_prepare_connection: mutex grab
>> failed for DCYYYY May 21 08:16:54  winbindd[29077]: [2018/05/21
>> 08:16:54.834268,
>> 0] ../source3/lib/util_tdb.c:493(tdb_chainlock_with_timeout_internal)
>> May 21 08:16:54  winbindd[29077]:
>> tdb_chainlock_with_timeout_internal: alarm (40) timed out for key
>> DCXXXX in tdb /var/run/samba/mutex.tdb May 21 08:16:54
>> winbindd[29077]: [2018/05/21 08:16:54.834410,
>> 0] ../source3/winbindd/winbindd_cm.c:918(cm_prepare_connection) May
>> 21 08:16:54  winbindd[29077]:   cm_prepare_connection: mutex grab
>> failed for DCYYYY
>>
>> May 21 08:17:01  CRON[1667]: (root) CMD (   cd / && run-parts
>> --report /etc/cron.hourly)
>> May 21 08:17:16  ldminfod[29951]: connect from 192.168.2.157
>> (192.168.2.157) May 21 08:17:41  winbindd[29077]: [2018/05/21
>> 08:17:41.330909,
>> 0] ../source3/lib/util_tdb.c:493(tdb_chainlock_with_timeout_internal)
>>
>> -----------------
>>
>> Ant Idea ?
> Either upgrade your OS, to Debian 9 (stretch) and use Louis Van Belle's
> packages, this will get you a much later version of Samba, or ask
> Debian. Samba 4.2.x is EOL as far as Samba is concerned.
>
> Rowland
>

On Thu, 24 May 2018 20:28:48 -0300
Carlos via samba <samba at lists.samba.org> wrote:
> Hi!
> 
> Thanks  for answer!
> 
> In future my plan is update, but this momento is no possible.. :-|
> 
> But, same error, in same time, in 3 server, is very strange....
> 
> > Either upgrade your OS, to Debian 9 (stretch) and use Louis Van
> > Belle's packages, this will get you a much later version of Samba,
> > or ask Debian. Samba 4.2.x is EOL as far as Samba is concerned.
No, it isn't strange, you seem to have hit an issue and you are getting
the same issue on all three DCs because they are all running the same
version of Samba. This version of Samba is EOL, so either upgrade or
ask Debian.

Rowland

Hey,

But What's the reason of this error?


On 05/25/2018 04:58 AM, Carlos via samba wrote:
> Hi!
>
> Thanks  for answer!
>
> In future my plan is update, but this momento is no possible.. :-|
>
> But, same error, in same time, in 3 server, is very strange....
>
> Regards;
>
>
> On 24-05-2018 15:38, Rowland Penny via samba wrote:
>> On Thu, 24 May 2018 09:32:56 -0300
>> Carlos via samba <samba at lists.samba.org> wrote:
>>
>>> Hi!
>>>
>>> I have 3 server:
>>>
>>> S.O. -  Debina 8
>>>
>>> Winbind Version : 2:4.2.10+dfsg-0+deb8u3
>>>
>>> Member Domain
>>>
>>> Samba Server : Ubuntu 14.04 with Samba 4.7.7 , are 18 Dcs
>>>
>>> ---------------------
>>>
>>>
>>> In day 21/05 , the 3 server have same problema in same time, th
>>> problem resolved after 40 minutes....
>>>
>>> Syslog server 1/2/3:
>>>
>>> May 21 08:14:12  winbindd[6718]: [2018/05/21 08:14:12.288624,  0]
>>> ../source3/winbindd/winbindd_dual.c:105(child_write_response)
>>> May 21 08:14:12  winbindd[6718]:   Could not write result
>>> May 21 08:15:01  CRON[32667]: (root) CMD (command -v debian-sa1
>
>>> /dev/null && debian-sa1 1 1)
>>>
>>> May 21 08:15:26  winbindd[28719]: [2018/05/21 08:15:26.341870,  0]
>>> ../source3/winbindd/winbindd_dual.c:105(child_write_response)
>>> May 21 08:15:26  winbindd[28719]:   Could not write result
>>> May 21 08:15:30  winbindd[28808]: [2018/05/21 08:15:30.814572,  0]
>>> ../source3/winbindd/winbindd_dual.c:105(child_write_response)
>>> May 21 08:15:30  winbindd[28808]:   Could not write result
>>> May 21 08:15:45  winbindd[32708]: [2018/05/21 08:15:45.545910,  0]
>>> ../source3/lib/util_tdb.c:493(tdb_chainlock_with_timeout_internal)
>>> May 21 08:15:45  winbindd[32708]:
>>> tdb_chainlock_with_timeout_internal: alarm (40) timed out for key
>>> DCXXX in tdb /var/run/samba/mutex.tdb May 21 08:15:45
>>> winbindd[32708]: [2018/05/21 08:15:45.546208,
>>> 0] ../source3/winbindd/winbindd_cm.c:918(cm_prepare_connection) May
>>> 21 08:15:45  winbindd[32708]:   cm_prepare_connection: mutex grab
>>> failed for DCXXXX
>>>
>>> May 21 08:16:47  winbindd[29020]: [2018/05/21 08:16:47.246684,  0]
>>> ../source3/lib/util_tdb.c:493(tdb_chainlock_with_timeout_internal)
>>> May 21 08:16:47  winbindd[29020]:
>>> tdb_chainlock_with_timeout_internal: alarm (40) timed out for key
>>> DCYYY in tdb /var/run/samba/mutex.tdb May 21 08:16:47
>>> winbindd[29020]: [2018/05/21 08:16:47.246803,
>>> 0] ../source3/winbindd/winbindd_cm.c:918(cm_prepare_connection) May
>>> 21 08:16:47  winbindd[29020]:   cm_prepare_connection: mutex grab
>>> failed for DCYYYY May 21 08:16:54  winbindd[29077]: [2018/05/21
>>> 08:16:54.834268,
>>> 0]
../source3/lib/util_tdb.c:493(tdb_chainlock_with_timeout_internal)
>>> May 21 08:16:54  winbindd[29077]:
>>> tdb_chainlock_with_timeout_internal: alarm (40) timed out for key
>>> DCXXXX in tdb /var/run/samba/mutex.tdb May 21 08:16:54
>>> winbindd[29077]: [2018/05/21 08:16:54.834410,
>>> 0] ../source3/winbindd/winbindd_cm.c:918(cm_prepare_connection) May
>>> 21 08:16:54  winbindd[29077]:   cm_prepare_connection: mutex grab
>>> failed for DCYYYY
>>>
>>> May 21 08:17:01  CRON[1667]: (root) CMD (   cd / &&
run-parts
>>> --report /etc/cron.hourly)
>>> May 21 08:17:16  ldminfod[29951]: connect from 192.168.2.157
>>> (192.168.2.157) May 21 08:17:41  winbindd[29077]: [2018/05/21
>>> 08:17:41.330909,
>>> 0]
../source3/lib/util_tdb.c:493(tdb_chainlock_with_timeout_internal)
>>>
>>> -----------------
>>>
>>> Ant Idea ?
>> Either upgrade your OS, to Debian 9 (stretch) and use Louis Van
Belle's
>> packages, this will get you a much later version of Samba, or ask
>> Debian. Samba 4.2.x is EOL as far as Samba is concerned.
>>
>> Rowland
>>
>
>

On Wed, 19 Dec 2018 12:32:45 +0530
Amit Kumar via samba <samba at lists.samba.org> wrote:
> Hey,
> 
> But What's the reason of this error?
> 
I do not know, but what I do know is that, if it is a bug, you will
never get it fixed in Samba 4.2.x, this version is EOL. It might also
have been fixed in a later version.

Sorry if this isn't what you want to hear.

Rowland