systemctl stop nsdc
systemctl start nsdc
systemctl -M nsdc status samba
1 Like
[root@s-lsfc an.sistemas]# systemctl -M nsdc status samba
● samba.service - Samba domain controller daemon
Loaded: loaded (/usr/lib/systemd/system/samba.service; enabled; vendor preset: disabled)
Active: active (running) since Sun 2022-11-27 18:07:10 -05; 266ms ago
Main PID: 26 (kworker/3:0H)
CGroup: /machine.slice/nsdc.service/system.slice/samba.service
├─17898 /usr/sbin/samba -i --debug-stderr
├─17902 /usr/sbin/samba -i --debug-stderr
├─17903 /usr/sbin/samba -i --debug-stderr
├─17904 /usr/sbin/samba -i --debug-stderr
├─17905 /usr/sbin/samba -i --debug-stderr
├─17906 /usr/sbin/smbd -D --option=server role check:inhibit=yes --foreground
├─17907 /usr/sbin/samba -i --debug-stderr
├─17908 /usr/sbin/samba -i --debug-stderr
├─17909 /usr/sbin/samba -i --debug-stderr
├─17910 /usr/sbin/samba -i --debug-stderr
├─17911 /usr/sbin/samba -i --debug-stderr
├─17912 /usr/sbin/samba -i --debug-stderr
├─17913 /usr/sbin/samba -i --debug-stderr
├─17914 /usr/sbin/samba -i --debug-stderr
├─17915 /usr/sbin/samba -i --debug-stderr
├─17916 /usr/sbin/winbindd -D --option=server role check:inhibit=yes --foreground
├─17917 /usr/sbin/samba -i --debug-stderr
├─17918 /usr/sbin/samba -i --debug-stderr
├─17919 /usr/sbin/samba -i --debug-stderr
├─17920 python /usr/sbin/samba_dnsupdate
├─17921 /usr/sbin/samba -i --debug-stderr
└─17922 python /usr/sbin/samba_spnupdate
‣ 26 [kworker/3:0H]
[root@s-lsfc an.sistemas]# nsdc-run -e – samba -V
Traceback (most recent call last):
File “/bin/nsdc-run”, line 55, in
buf = so.recv(buf_sz)
socket.error: [Errno 104] Connection reset by peer
It is a production server!!
Can´t make that acrobacy this time, I will try to update a new server, then backup config, then reload the server it self.
60 machines are configured to the NSDC, it is coming vacations time maybe in 20 days I can make it work.
systemctl -M nsdc status -l nsdc-run.socket
systemctl -M nsdc restart nsdc-run.socket
1 Like
[quote=“dnutan, post:24, topic:20950”]
systemctl -M nsdc status -l nsdc-run.socket
systemctl -M nsdc restart nsdc-run.socket
[root@s-XX an.sistemas]# systemctl -M nsdc restart nsdc-run.socket
[root@s-XX an.sistemas]# systemctl -M nsdc status -l nsdc-run.socket
● nsdc-run.socket - NSDC container remote command server
Loaded: loaded (/etc/systemd/system/nsdc-run.socket; enabled; vendor preset: disabled)
Active: active (listening) since Sun 2022-11-27 18:22:35 -05; 5s ago
Docs: nethserver-dc/README.rst at master · NethServer/nethserver-dc · GitHub
Listen: /var/lib/misc/nsdc-run.sock (Stream)
Accepted: 1; Connected: 0
[root@s-XX an.sistemas]# nsdc-run -e – samba -V
Traceback (most recent call last):
File “/bin/nsdc-run”, line 55, in
buf = so.recv(buf_sz)
socket.error: [Errno 104] Connection reset by peer
If you have a good and recent configuration backup with the DC user database you could evaluate the restore-config procedure in a separate testing environment:
Disaster recovery — NethServer 7 Final
If that works you can run it on the broken server too:
- remove the account provider
- restore the configuration backup
I’m going to do it in the virtualbox server, if it works I’ll try it in the main server, can’t do it now, but in weekend for sure,
I’ll keep you updated.
1 Like
Hi there Aligators!!!
Making the steps above (remove the account provider, then restore the config backup) the system uploaded the config (feels like You are making damages like sid ejejeje).
Keep this in mind the backup config didn’t work in all the week during the nethserver-dc-1.9.0. failure After the new package nethserver-dc-1.9.1 the backup config it worked again.
The windows 11 is joining the domain, and it works with the RSAT GPO editor.
Thank’s for the help You gave me!!
3 Likes
This topic was automatically closed after 22 hours. New replies are no longer allowed.