After Update from today no users

Support
, , ,
11

Also had a huge update today, but I can create users and groups.
I think same updates as yours, but no problems so far. :thinking:

12

so i am happy for you :slight_smile:

1 Like
13

Wait some minutes. I will install a fresh machine and test it.

2 Likes
14

FTR, that’s CentOS 7.3

1 Like
15

thats pretty nice but would love to have my system back :smiley:

and at my server is written:

1 Like
16

3 posts were split to a new topic: Problem installing the LDAP account provider

18

Thanks a lot for testing that Uwe

20

We are investigating the issue.

Please check that SSSD is up and running.

2 Likes
21

if i check it by systemctl start sssd.service i got no error, so seems to work, right?

22

Aren’t there any missing updates? (samba-*4.4.4)

yum clean all && yum update --assumeno
23

no packages for update

24

after a restart the mysql is started, but the rest dont work.

25

Could you paste the output of?

systemctl status nsdc

Also search for any error message in

journalctl -M nsdc
1 Like
26

the output of systemctl status is:
â nsdc.service - NethServer Domain Controller container
Loaded: loaded (/usr/lib/systemd/system/nsdc.service; enabled; vendor preset: disabled)
Active: active (running) since Tue 2016-12-13 08:32:04 CET; 6min ago
Docs: man:systemd-nspawn(1)
Main PID: 27144 (systemd-nspawn)
Status: "Container running."
Memory: 149.4M
CGroup: /machine.slice/nsdc.service
ââ27144 /usr/bin/systemd-nspawn --quiet --keep-unit --boot --network-bridge=br0 --machine=nsdc
ââ27146 /usr/lib/systemd/systemd
ââsystem.slice
ââdbus.service
â ââ27253 /bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
ââsystemd-journald.service
â ââ27232 /usr/lib/systemd/systemd-journald
ââsystemd-logind.service
â ââ27252 /usr/lib/systemd/systemd-logind
ââsamba.service
â ââ27260 /usr/sbin/samba -i --debug-stderr
â ââ27263 /usr/sbin/samba -i --debug-stderr
â ââ27264 /usr/sbin/samba -i --debug-stderr
â ââ27265 /usr/sbin/smbd -D --option=server role check:inhibit=yes --foreground
â ââ27266 /usr/sbin/samba -i --debug-stderr
â ââ27267 /usr/sbin/samba -i --debug-stderr
â ââ27268 /usr/sbin/samba -i --debug-stderr
â ââ27269 /usr/sbin/samba -i --debug-stderr
â ââ27270 /usr/sbin/samba -i --debug-stderr
â ââ27271 /usr/sbin/samba -i --debug-stderr
â ââ27272 /usr/sbin/samba -i --debug-stderr
â ââ27273 /usr/sbin/samba -i --debug-stderr
â ââ27274 /usr/sbin/samba -i --debug-stderr
â ââ27275 /usr/sbin/samba -i --debug-stderr
â ââ27276 /usr/sbin/winbindd -D --option=server role check:inhibit=yes --foreground
â ââ27277 /usr/sbin/samba -i --debug-stderr
â ââ27280 /usr/sbin/smbd -D --option=server role check:inhibit=yes --foreground
â ââ27281 /usr/sbin/smbd -D --option=server role check:inhibit=yes --foreground
â ââ27283 /usr/sbin/smbd -D --option=server role check:inhibit=yes --foreground
â ââ27284 /usr/sbin/winbindd -D --option=server role check:inhibit=yes --foreground
â ââ27393 /usr/sbin/smbd -D --option=server role check:inhibit=yes --foreground
ââconsole-getty.service
ââ27257 /sbin/agetty --noclear --keep-baud console 115200 38400 9600 vt220

Dec 13 08:32:05 xxx.xx.xx. systemd-nspawn[27144]: [ OK ] Started Network Service.
Dec 13 08:32:05 xxx.xx.xx systemd-nspawn[27144]: [ OK ] Reached target Network.
Dec 13 08:32:05 xxx.xx.xx systemd-nspawn[27144]: [ OK ] Started Samba domain controller daemon.
Dec 13 08:32:05 xxx.xx.xx systemd-nspawn[27144]: Starting Samba domain controller daemon…
Dec 13 08:32:05xxx.xx.xx systemd-nspawn[27144]: [ OK ] Reached target Multi-User System.
Dec 13 08:32:05 xxx.xx.xx systemd-nspawn[27144]: [ OK ] Reached target Graphical Interface.
Dec 13 08:32:05 xxx.xx.xx systemd-nspawn[27144]: Starting Update UTMP about System Runlevel Changes…
Dec 13 08:32:05xxx.xx.xx systemd-nspawn[27144]: [ OK ] Started Update UTMP about System Runlevel Changes.
Dec 13 08:32:05 xxx.xx.xx systemd-nspawn[27144]: CentOS Linux 7 (Core)
Dec 13 08:32:05 xxx.xx.xx systemd-nspawn[27144]: Kernel 4.4.22-1.el7.elrepo.x86_64 on an x86_64

27

So the nsdc container is up and samba4 is running. Can you ping its IP address? You can obtain it with

config show nsdc
28

yes ping is responding

29

if i view at the domain account is written this now

NetBIOS domain name: xxx
ads_connect: No logon servers
ads_connect: No logon servers
Didn’t find the ldap server!

ads_connect: No logon servers
Join to domain is not valid: No logon servers
ads_connect: No logon servers
ads_connect: No logon servers

1 Like
30

The container seems good, let’s see the “client” side… What does the Server Manager report at page “Status > Domain accounts”?

/cc @support_team

31

Let’s see dnsmasq:

 systemctl status dnsmasq
32

â dnsmasq.service - DNS caching server.
Loaded: loaded (/usr/lib/systemd/system/dnsmasq.service; enabled; vendor preset: disabled)
Active: active (running) since Mon 2016-12-12 20:06:06 CET; 12h ago
Main PID: 1190 (dnsmasq)
CGroup: /system.slice/dnsmasq.service
ââ1190 /usr/sbin/dnsmasq -k

Dec 13 06:08:32 xxx.xxx.xxx dnsmasq-dhcp[1190]: DHCPREQUEST(br0) 192.168.100.150 00:04:20:2a:50:91
Dec 13 06:08:32 xxx.xxx.xxx dnsmasq-dhcp[1190]: DHCPACK(br0) 192.168.100.150 00:04:20:2a:50:91 SqueezeboxRadio
Dec 13 07:45:01 xxx.xxx.xxx dnsmasq-dhcp[1190]: DHCPREQUEST(br0) 192.168.100.109 e8:50:8b:0a:b8:6a
Dec 13 07:45:01 sxxx.xxx.xxx dnsmasq-dhcp[1190]: DHCPACK(br0) 192.168.100.109 e8:50:8b:0a:b8:6a android-2dec71c06455d059
Dec 13 08:17:35 xxx.xxx.xxx dnsmasq-dhcp[1190]: DHCPDISCOVER(br0) b8:ee:65:ac:37:0b
Dec 13 08:17:35 xxx.xxx.xxx dnsmasq-dhcp[1190]: DHCPOFFER(br0) 192.168.100.112 b8:ee:65:ac:37:0b
Dec 13 08:17:35 xxx.xxx.xxx dnsmasq-dhcp[1190]: DHCPREQUEST(br0) 192.168.100.112 b8:ee:65:ac:37:0b
Dec 13 08:17:35 xxx.xxx.xxx dnsmasq-dhcp[1190]: DHCPACK(br0) 192.168.100.112 b8:ee:65:ac:37:0b Rainer-Notebook
Dec 13 08:18:29 xxx.xxx.xxx dnsmasq-dhcp[1190]: DHCPREQUEST(br0) 192.168.100.112 b8:ee:65:ac:37:0b
Dec 13 08:18:29 xxx.xxx.xxx dnsmasq-dhcp[1190]: DHCPACK(br0) 192.168.100.112 b8:ee:65:ac:37:0b Rainer-Notebook