On 5/8/19 12:25 PM, Konstantin Belousov wrote:

Signal 6 is SIGABRT, which means most likely that some assert was triggered.
You should look into your logs.

samba.log shows nothing at level 1 (default); at level 3 gives gobs of information and I don't look what to look for.

In all.log, however, I have something like this:

May  8 12:48:11 xxxx winbindd[83147]: [2019/05/08 12:48:11.493769,  0] 
../source3/libsmb/trusts_util.c:334(trust_pw_change)
May  8 12:48:11 xxxx kernel: May  8 12:48:09 xxxx last message repeated 4 times
May  8 12:48:11 xxxx kernel: May  8 12:48:11 xxxx winbindd[83147]: [2019/05/08 
12:48:11.493769,  0] ../source3/libsmb/trusts_util.c:334(trust_pw_change)
May  8 12:48:11 xxxx winbindd[83147]:   2019/05/08 12:48:11 : 
trust_pw_change(XX): A password change was already started against 
'dc1.ad.xxxxxxxxxxxxx.it' at Mon Apr 29 12:22:51 2019 CEST. Trying to recover...
May  8 12:48:11 xxxx kernel: May  8 12:48:11 xxxx winbindd[83147]:   2019/05/08 
12:48:11 : trust_pw_change(XX): A password change was already started against 
'dc1.ad.xxxxxxxxxxxxx.it' at Mon Apr 29 12:22:51 2019 CEST. Trying to recover...
May  8 12:48:11 xxxx winbindd[83147]: [2019/05/08 12:48:11.493910,  0] 
../source3/libsmb/trusts_util.c:343(trust_pw_change)
May  8 12:48:11 xxxx kernel: May  8 12:48:11 xxxx winbindd[83147]: [2019/05/08 
12:48:11.493910,  0] ../source3/libsmb/trusts_util.c:343(trust_pw_change)
May  8 12:48:11 xxxx winbindd[83147]:   2019/05/08 12:48:11 : 
trust_pw_change(XX): Last failure local[NT_STATUS_NOT_COMMITTED] 
remote[NT_STATUS_CONNECTION_DISCONNECTED] against 'dc1.ad.xxxxxxxxxxxxx.it' at 
Wed May  8 12:47:11 2019 CEST.
May  8 12:48:11 xxxx kernel: May  8 12:48:11 xxxx winbindd[83147]:   2019/05/08 
12:48:11 : trust_pw_change(XX): Last failure local[NT_STATUS_NOT_COMMITTED] 
remote[NT_STATUS_CONNECTION_DISCONNECTED] against 'dc1.ad.xxxxxxxxxxxxx.it' at 
Wed
 May  8 12:47:11 2019 CEST.
May  8 12:48:11 xxxx winbindd[83147]: [2019/05/08 12:48:11.493986,  0] 
../source3/libsmb/trusts_util.c:380(trust_pw_change)
May  8 12:48:11 xxxx kernel: May  8 12:48:11 xxxx winbindd[83147]: [2019/05/08 
12:48:11.493986,  0] ../source3/libsmb/trusts_util.c:380(trust_pw_change)
May  8 12:48:11 xxxx winbindd[83147]:   2019/05/08 12:48:11 : 
trust_pw_change(XX): Verifying passwords remotely 
netlogon_creds_cli:CLI[FS/FS$]/SRV[DC1/XX].
May  8 12:48:11 xxxx kernel: May  8 12:48:11 xxxx winbindd[83147]:   2019/05/08 
12:48:11 : trust_pw_change(XX): Verifying passwords remotely 
netlogon_creds_cli:CLI[FS/FS$]/SRV[DC1/XX].
May  8 12:48:11 xxxx samba[54713]: stack overflow detected; terminated
May  8 12:48:11 xxxx winbindd[83147]: [2019/05/08 12:48:11.496724,  0] 
../source3/libsmb/trusts_util.c:452(trust_pw_change)
May  8 12:48:11 xxxx kernel: May  8 12:48:11 xxxx samba[54713]: stack overflow 
detected; terminated
May  8 12:48:11 xxxx kernel: May  8 12:48:11 xxxx winbindd[83147]: [2019/05/08 
12:48:11.496724,  0] ../source3/libsmb/trusts_util.c:452(trust_pw_change)
May  8 12:48:11 xxxx winbindd[83147]:   2019/05/08 12:48:11 : 
trust_pw_change(XX): Verified old password remotely using 
netlogon_creds_cli:CLI[FS/FS$]/SRV[DC1/XX]
May  8 12:48:11 xxxx kernel: May  8 12:48:11 xxxx winbindd[83147]:   2019/05/08 
12:48:11 : trust_pw_change(XX): Verified old password remotely using 
netlogon_creds_cli:CLI[FS/FS$]/SRV[DC1/XX]
May  8 12:48:11 xxxx winbindd[83147]: [2019/05/08 12:48:11.496828,  0] 
../source3/libsmb/trusts_util.c:491(trust_pw_change)
May  8 12:48:11 xxxx kernel: May  8 12:48:11 xxxx winbindd[83147]: [2019/05/08 
12:48:11.496828,  0] ../source3/libsmb/trusts_util.c:491(trust_pw_change)
May  8 12:48:11 xxxx winbindd[83147]:   2019/05/08 12:48:11 : 
trust_pw_change(XX): Changed password locally
May  8 12:48:11 xxxx kernel: May  8 12:48:11 xxxx winbindd[83147]:   2019/05/08 
12:48:11 : trust_pw_change(XX): Changed password locally
May  8 12:48:11 xxxx winbindd[83147]: [2019/05/08 12:48:11.636003,  0] 
../source3/libsmb/trusts_util.c:507(trust_pw_change)
May  8 12:48:11 xxxx kernel: pid 54713 (samba), uid 0: exited on signal 6 (core 
dumped)
May  8 12:48:11 xxxx kernel: May  8 12:48:11 xxxx winbindd[83147]: [2019/05/08 
12:48:11.636003,  0] ../source3/libsmb/trusts_util.c:507(trust_pw_change)
May  8 12:48:11 xxxx winbindd[83147]:   2019/05/08 12:48:11 : 
trust_pw_change(XX) remote password change with 
netlogon_creds_cli:CLI[FS/FS$]/SRV[DC1/XX] failed - 
NT_STATUS_CONNECTION_DISCONNECTED (disconnected)
May  8 12:48:11 xxxx kernel: May  8 12:48:11 xxxx winbindd[83147]:   2019/05/08 
12:48:11 : trust_pw_change(XX) remote password change with 
netlogon_creds_cli:CLI[FS/FS$]/SRV[DC1/XX] failed - 
NT_STATUS_CONNECTION_DISCONNECTED (disconnected
)
May  8 12:48:11 xxxx samba[80265]: [2019/05/08 12:48:11.639630,  0] 
../source4/smbd/process_standard.c:158(standard_child_pipe_handler)
May  8 12:48:11 xxxx kernel: May  8 12:48:11 xxxx samba[80265]: [2019/05/08 
12:48:11.639630,  0] 
../source4/smbd/process_standard.c:158(standard_child_pipe_handler)
May  8 12:48:11 xxxx samba[80265]:   standard_child_pipe_handler: Child 54713 
() terminated with signal 6
May  8 12:48:11 xxxx kernel: May  8 12:48:11 xxxx samba[80265]:   
standard_child_pipe_handler: Child 54713 () terminated with signal 6

While this sheds some light (seems the whole thing has to do with trust password change), it shows a stack overflow, not an assert.
So the question is two-fold:

a) how do I get out of this? Remove the other member from the domain and rejoin? Try and fix the DB (how)? Other? (I understand this would be a question better answere on Samba list, but we are already here).

b) if there's a stack overflow, isn't that a bug? How can I check it and report it (to FreeBSD or Samba, once the details can let me decide) if I cannot get a proper core? I guess I'd have to look into a way to generate debug info with Poudriere... what's the proper way to do this?


 bye & Thanks
        av.
_______________________________________________
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Reply via email to