Domain Controller Repeatedly Down Every Single Monday

activedirectory
v7

(Jeremy) #1

System version
NethServer release 7.6.1810 (final)
Kernel release
3.10.0-957.1.3.el7.x86_64

I don’t see any helpful past posts and I have not had good luck finding any help on these forums. I really need help on this issue. My Domain Controller is not available to authenticate against at least once a week on Monday every single week for the last few weeks. There is never any change on my end and everything just stops working on Mondays. The fix is never the same and the error messages are not the same week to week.

This week I cannot get the domain controller up and running after working at all.

ads_connect: No logon servers are currently available to service the logon request.
Didn’t find the ldap server!
Join is OK
ads_connect: No logon servers are currently available to service the logon request.

nmap $(config getprop nsdc IpAddress)

Starting Nmap 6.40 ( http://nmap.org ) at 2018-12-27 12:17 CST
Nmap scan report for ad.calumetfab.com (10.1.10.75)
Host is up (0.000019s latency).
All 1000 scanned ports on ad.calumetfab.com (10.1.10.75) are closed
MAC Address: 9A:82:66:8B:97:91 (Unknown)

Nmap done: 1 IP address (1 host up) scanned in 0.15 seconds

systemctl -l status nsdc
● nsdc.service - NethServer Domain Controller container
Loaded: loaded (/usr/lib/systemd/system/nsdc.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2018-12-27 12:05:16 CST; 12min ago
Docs: man:systemd-nspawn(1)
Main PID: 4430 (systemd-nspawn)
Status: “Container running.”
Tasks: 7
Memory: 23.6M
CGroup: /machine.slice/nsdc.service
├─4430 /usr/bin/systemd-nspawn --quiet --keep-unit --boot --network-bridge=br0 --machine=nsdc --capability=CAP_SYS_TIME
├─4442 /usr/lib/systemd/systemd
└─system.slice
├─console-getty.service
│ └─4874 /sbin/agetty --noclear --keep-baud console 115200 38400 9600 vt220
├─ntpd.service
│ └─4938 /usr/sbin/ntpd -u ntp:ntp -g
├─systemd-logind.service
│ └─4846 /usr/lib/systemd/systemd-logind
├─dbus.service
│ └─4731 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
└─systemd-journald.service
└─4551 /usr/lib/systemd/systemd-journald

Dec 27 12:05:16 calfab01.calumetfab.com systemd-nspawn[4430]: [ OK ] Started Login Service.
Dec 27 12:05:16 calfab01.calumetfab.com systemd-nspawn[4430]: [ OK ] Started Network Time Service.
Dec 27 12:05:16 calfab01.calumetfab.com systemd-nspawn[4430]: [ OK ] Started Network Service.
Dec 27 12:05:16 calfab01.calumetfab.com systemd-nspawn[4430]: [ OK ] Reached target Network.
Dec 27 12:05:16 calfab01.calumetfab.com systemd-nspawn[4430]: [ OK ] Reached target Multi-User System.
Dec 27 12:05:16 calfab01.calumetfab.com systemd-nspawn[4430]: [ OK ] Reached target Graphical Interface.
Dec 27 12:05:16 calfab01.calumetfab.com systemd-nspawn[4430]: Starting Update UTMP about System Runlevel Changes…
Dec 27 12:05:16 calfab01.calumetfab.com systemd-nspawn[4430]: [ OK ] Started Update UTMP about System Runlevel Changes.
Dec 27 12:05:17 calfab01.calumetfab.com systemd-nspawn[4430]: CentOS Linux 7 (Core)
Dec 27 12:05:17 calfab01.calumetfab.com systemd-nspawn[4430]: Kernel 3.10.0-957.1.3.el7.x86_64 on an x86_64

systemctl -l -M nsdc status samba
● samba.service - Samba domain controller daemon
Loaded: loaded (/usr/lib/systemd/system/samba.service; enabled; vendor preset: disabled)
Active: inactive (dead)
Condition: start condition failed at Thu 2018-12-27 12:05:16 CST; 5min ago
ConditionPathExists=/var/lib/samba/private/krb5.conf was not met


(Oliver Johnston) #2

Sounds obvious but have you checked your hard disks or memory? when I have had issues like this in the past it usually turns out to be hardware related.
Worth a look. At least you can rule it out.


(Michael) #3

Try lowering the kernel on 3.10.0-862.14.4.el7.x86_64