Lock error and conflict on nas AD

Support
,
1

NethServer release 7.6.1810
samba 4.8.3

Hi, I have detected for some time an error that is reported by my nos “xigmanas” regarding the Active Directory domain of neth 7. In the diagnostics a conflict and lock message often appears:

Environment LOGNAME is not defined. Trying anonymous access.
connect_to_domain_password_server: unable to open domain client session to machine nsdc-neth7.ad.internal2.lan. Flags [0x00000000] Error was: NT_STATUS_FILE_LOCK_CONFLICT.
Join to domain ‘INTERNAL2’ is not valid: NT_STATUS_FILE_LOCK_CONFLICT
Winbindd Availability
Ping to winbindd succeeded
Trust Account Status
checking the trust secret for domain INTERNAL2 via RPC calls succeeded
Despite this reporting, the user query and group functions such as “id user” work correctly and return the correct values, and performing the join test to verify that everything is ok the answer is positive.

net ads test join:
reply:
Join is OK
The server name nscd-neth7.ad.internal2.lan is correctly resolved.

I ask everyone for a hint about this error.
Furthermore, restarting the samba service from the nos, everything returns to normal
Thanks :roll_eyes:

55
Schermata 2019-11-28 alle 14.28.55.png994×121 24.1 KB

47
.

2

There seems to be an open bug in your NAS software:

https://sourceforge.net/p/xigmanas/bugs/383/

3

Hi, I had read the same article. I updated the version of the nas and it seems that the error continues to exist. Is it possible to make what changes to the smb4.conf file to contain the error? Anyway thanks .

4

How often does the error occur? What about a “bad workaround” like restarting the samba service outside production time on the NAS regularly with a cron job until they solve the bug?

https://www.xigmanas.com/wiki/doku.php?id=documentation:setup_and_user_guide:system_advanced_cron

5

I figured … let’s say the bug is fixed. At the moment this bug is open as a ticket and unfortunately not solved, so open. Thanks Markuz
:pray:

1 Like