Problem with nsdc: socket.error

activedirectory
(Wijnand Mijnders) #1

NethServer Version: 7.5.1804 (final)

Dear Nethservians,

I have stumbled upon a problem with nsdc which i probably created myself :frowning: I cannot add new users in Nethserver and also the hotsync configuration-backup encounters a problem. I think it is python related because some time ago I tried to install Odoo (following to the instructions in a forum-post), which requires python version 3.5 while Nethserver has 2.7 on board. Around that time the above problems started. I didn’t get Odoo to work so in the mean time I erased python 3.

This is an extract of the messages log for the config-backup:

Sep 6 16:30:48 server1 esmith::event[30626]: Action: /etc/e-smith/events/actions/generic_template_expand SUCCESS [0.229643]
Sep 6 16:30:48 server1 esmith::event[30626]: Traceback (most recent call last):
Sep 6 16:30:48 server1 esmith::event[30626]: File “/usr/bin/nsdc-run”, line 38, in
Sep 6 16:30:48 server1 esmith::event[30626]: so.connect(’/var/lib/machines/nsdc/var/lib/misc/nsdc-run.sock’)
Sep 6 16:30:48 server1 esmith::event[30626]: File “/usr/lib64/python2.7/socket.py”, line 224, in meth
Sep 6 16:30:48 server1 esmith::event[30626]: return getattr(self._sock,name)(*args)
Sep 6 16:30:48 server1 esmith::event[30626]: socket.error: [Errno 2] No such file or directory
Sep 6 16:30:48 server1 esmith::event[30626]: Action: /etc/e-smith/events/pre-backup-config/S40nethserver-dc-pre-backup FAILED: 1 [0.032025]
Sep 6 16:30:48 server1 esmith::event[30626]: Action: /etc/e-smith/events/pre-backup-config/S40nethserver-mail-shrmbx-cfgbackup SUCCESS [0.004908]
Sep 6 16:30:48 server1 esmith::event[30626]: Action: /etc/e-smith/events/pre-backup-config/S40nethserver-sssd-backup-tdb SUCCESS [0.249436]
Sep 6 16:30:50 server1 esmith::event[30626]: Action: /etc/e-smith/events/pre-backup-config/S50nethserver-backup-config-list-packages SUCCESS [2.023349]
Sep 6 16:30:50 server1 esmith::event[30626]: Event: pre-backup-config FAILED

The errorlines for adding a user are similar in respect to the socket.error. What could I try to resolve this problem? All help is much appreciated!

Regards, Wijnand.

(Markus Neuberger) #2

I tried to reproduce but got no error, I installed AD and odoo 11 which uses python 3.5. Even after reboot I can still create users or do a config backup.

[root@testvm2 ~]# backup-config
===== Report for configuration backup =====

Backup started at 2018-09-06 18:41:10
Event pre-backup-config: SUCCESS
Action backup-config-execute: SUCCESS
Event post-backup-config: SUCCESS
Backup status: SUCCESS
Backup ended at 2018-09-06 18:41:17
Time elapsed: 0 hours, 0 minutes, 7 seconds

Is the nsdc running?

systemctl status nsdc -l

(Wijnand Mijnders) #3

Hi Markus,

nsdc seems to be running:

[root@server1 ~]# systemctl status nsdc -l
● nsdc.service - NethServer Domain Controller container
   Loaded: loaded (/usr/lib/systemd/system/nsdc.service; enabled; vendor preset: disabled)
   Active: active (running) since Wed 2018-08-29 23:06:32 CEST; 1 weeks 0 days ago
     Docs: man:systemd-nspawn(1)
 Main PID: 4721 (systemd-nspawn)
   Status: "Container running."
   CGroup: /machine.slice/nsdc.service
           ├─4721 /usr/bin/systemd-nspawn --quiet --keep-unit --boot --network-bridge=br0 --machine=nsdc --capability=CAP_SYS_TIME
           ├─4725 /usr/lib/systemd/systemd
           └─system.slice
             ├─samba.service
             │ ├─ 4824 /usr/sbin/samba -i --debug-stderr
             │ ├─ 4827 /usr/sbin/samba -i --debug-stderr
             │ ├─ 4828 /usr/sbin/samba -i --debug-stderr
             │ ├─ 4829 /usr/sbin/smbd -D --option=server role check:inhibit=yes --foreground
             │ ├─ 4830 /usr/sbin/samba -i --debug-stderr
             │ ├─ 4831 /usr/sbin/samba -i --debug-stderr
             │ ├─ 4832 /usr/sbin/samba -i --debug-stderr
             │ ├─ 4833 /usr/sbin/samba -i --debug-stderr
             │ ├─ 4834 /usr/sbin/samba -i --debug-stderr
             │ ├─ 4835 /usr/sbin/samba -i --debug-stderr
             │ ├─ 4836 /usr/sbin/samba -i --debug-stderr
             │ ├─ 4837 /usr/sbin/samba -i --debug-stderr
             │ ├─ 4838 /usr/sbin/samba -i --debug-stderr
             │ ├─ 4839 /usr/sbin/winbindd -D --option=server role check:inhibit=yes --foreground
             │ ├─ 4840 /usr/sbin/samba -i --debug-stderr
             │ ├─ 4841 /usr/sbin/samba -i --debug-stderr
             │ ├─ 4844 /usr/sbin/smbd -D --option=server role check:inhibit=yes --foreground
             │ ├─ 4845 /usr/sbin/smbd -D --option=server role check:inhibit=yes --foreground
             │ ├─ 4847 /usr/sbin/smbd -D --option=server role check:inhibit=yes --foreground
             │ ├─ 4848 /usr/sbin/winbindd -D --option=server role check:inhibit=yes --foreground
             │ └─27530 /usr/sbin/winbindd -D --option=server role check:inhibit=yes --foreground
             ├─console-getty.service
             │ └─4821 /sbin/agetty --noclear --keep-baud console 115200 38400 9600 vt220
             ├─systemd-logind.service
             │ └─4819 /usr/lib/systemd/systemd-logind
             ├─ntpd.service
             │ └─4822 /usr/sbin/ntpd -u ntp:ntp -g
             ├─dbus.service
             │ └─4816 /bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
             └─systemd-journald.service
               └─4772 /usr/lib/systemd/systemd-journald

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

One of the error-lines refers to so.connect(’/var/lib/machines/nsdc/var/lib/misc/nsdc-run.sock’) but the nsdc-run.sock file is not present in that directory.

(Davide Principi) #4

Try the following commands:

systemctl stop nsdc
systemctl start nsdc
(Wijnand Mijnders) #5

Hello Davide,

Unfortunately restarting nsdc doesn’t lead to success. nsdc is running but the socket.error still exists.

systemctl stop nsdc:

Sep  6 21:24:51 server1 systemd: Stopping NethServer Domain Controller container...
Sep  6 21:24:51 server1 systemd-nspawn: nsdc-server1 login: Trying to halt container. Send SIGTERM again to trigger immediate termination.
Sep  6 21:24:51 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Stopped target Graphical Interface.
Sep  6 21:24:51 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Removed slice system-getty.slice.
Sep  6 21:24:51 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Stopped target Timers.
Sep  6 21:24:51 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Stopped target Multi-User System.
Sep  6 21:24:51 server1 systemd-nspawn: Stopping Samba domain controller daemon...
Sep  6 21:24:51 server1 systemd-nspawn: Stopping D-Bus System Message Bus...
Sep  6 21:24:51 server1 systemd-nspawn: Stopping Network Time Service...
Sep  6 21:24:51 server1 systemd-nspawn: Stopping Login Service...
Sep  6 21:24:51 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Stopped target Login Prompts.
Sep  6 21:24:51 server1 systemd-nspawn: Stopping Console Getty...
Sep  6 21:24:51 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Stopped Login Service.
Sep  6 21:24:51 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Stopped Console Getty.
Sep  6 21:24:51 server1 systemd-nspawn: Stopping Permit User Sessions...
Sep  6 21:24:51 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Stopped Permit User Sessions.
Sep  6 21:24:51 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Stopped target Remote File Systems.
Sep  6 21:24:51 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Stopped D-Bus System Message Bus.
Sep  6 21:24:52 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Stopped Network Time Service.
Sep  6 21:24:56 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Stopped Samba domain controller daemon.
Sep  6 21:24:56 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Stopped target Network.
Sep  6 21:24:56 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Stopped target Basic System.
Sep  6 21:24:56 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Stopped target Paths.
Sep  6 21:24:56 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Stopped target Slices.
Sep  6 21:24:56 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Removed slice User and Session Slice.
Sep  6 21:24:56 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Stopped target Sockets.
Sep  6 21:24:56 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Closed D-Bus System Message Bus Socket.
Sep  6 21:24:56 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Stopped target System Initialization.
Sep  6 21:24:56 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Stopped target Encrypted Volumes.
Sep  6 21:24:56 server1 systemd-nspawn: Stopping Load/Save Random Seed...
Sep  6 21:24:56 server1 systemd-nspawn: Stopping Update UTMP about System Boot/Shutdown...
Sep  6 21:24:56 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Stopped Load/Save Random Seed.
Sep  6 21:24:56 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Stopped Update UTMP about System Boot/Shutdown.
Sep  6 21:24:56 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Stopped Create Volatile Files and Directories.
Sep  6 21:24:56 server1 systemd-nspawn: Stopping Create Volatile Files and Directories...
Sep  6 21:24:56 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Reached target Shutdown.
Sep  6 21:24:56 server1 systemd-nspawn: Sending SIGTERM to remaining processes...
Sep  6 21:24:57 server1 systemd-nspawn: Sending SIGKILL to remaining processes...
Sep  6 21:24:57 server1 systemd-nspawn: Halting system.
Sep  6 21:24:57 server1 kernel: br0: port 2(vb-nsdc) entered disabled state
Sep  6 21:24:57 server1 kernel: device vb-nsdc left promiscuous mode
Sep  6 21:24:57 server1 kernel: br0: port 2(vb-nsdc) entered disabled state
Sep  6 21:24:57 server1 systemd-machined: Machine nsdc terminated.
Sep  6 21:24:57 server1 avahi-daemon[965]: Withdrawing address record for fe80::b0d6:faff:fecf:783f on vb-nsdc.
Sep  6 21:24:57 server1 systemd: Stopped NethServer Domain Controller container.
Sep  6 21:24:57 server1 avahi-daemon[965]: Withdrawing workstation service for vb-nsdc.

systemctl start nsdc:

Sep  6 21:25:26 server1 systemd: Starting NethServer Domain Controller container...
Sep  6 21:25:26 server1 kernel: nf_conntrack: falling back to vmalloc.
Sep  6 21:25:26 server1 systemd-nspawn: Failed to create directory /var/lib/machines/nsdc//sys/fs/selinux: Read-only file system
Sep  6 21:25:26 server1 systemd-nspawn: Failed to create directory /var/lib/machines/nsdc//sys/fs/selinux: Read-only file system
Sep  6 21:25:26 server1 kernel: IPv6: ADDRCONF(NETDEV_UP): vb-nsdc: link is not ready
Sep  6 21:25:26 server1 kernel: br0: port 2(vb-nsdc) entered blocking state
Sep  6 21:25:26 server1 kernel: br0: port 2(vb-nsdc) entered disabled state
Sep  6 21:25:26 server1 kernel: device vb-nsdc entered promiscuous mode
Sep  6 21:25:26 server1 systemd-machined: New machine nsdc.
Sep  6 21:25:26 server1 systemd: Started NethServer Domain Controller container.
Sep  6 21:25:26 server1 systemd-nspawn: systemd 219 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
Sep  6 21:25:26 server1 systemd-nspawn: Detected virtualization systemd-nspawn.
Sep  6 21:25:26 server1 systemd-nspawn: Detected architecture x86-64.
Sep  6 21:25:26 server1 systemd-nspawn: Welcome to #033[0;31mCentOS Linux 7 (Core)#033[0m!
Sep  6 21:25:26 server1 systemd-nspawn: Set hostname to <nsdc-server1.ad1.pa3hfj.nl>.
Sep  6 21:25:26 server1 systemd-nspawn: Cannot add dependency job for unit display-manager.service, ignoring: Unit not found.
Sep  6 21:25:26 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Reached target Remote File Systems.
Sep  6 21:25:26 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Reached target Swap.
Sep  6 21:25:26 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Created slice Root Slice.
Sep  6 21:25:26 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Listening on networkd rtnetlink socket.
Sep  6 21:25:26 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Created slice User and Session Slice.
Sep  6 21:25:26 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Created slice System Slice.
Sep  6 21:25:26 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Reached target Slices.
Sep  6 21:25:26 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Listening on Delayed Shutdown Socket.
Sep  6 21:25:26 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Listening on Journal Socket.
Sep  6 21:25:26 server1 systemd-nspawn: Mounting FUSE Control File System...
Sep  6 21:25:26 server1 systemd-nspawn: Mounting Huge Pages File System...
Sep  6 21:25:26 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Reached target Paths.
Sep  6 21:25:26 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Reached target Local File Systems (Pre).
Sep  6 21:25:26 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Reached target Local File Systems.
Sep  6 21:25:26 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Listening on /dev/initctl Compatibility Named Pipe.
Sep  6 21:25:26 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Reached target Encrypted Volumes.
Sep  6 21:25:26 server1 systemd-nspawn: Starting Load/Save Random Seed...
Sep  6 21:25:26 server1 systemd-nspawn: Mounting POSIX Message Queue File System...
Sep  6 21:25:26 server1 systemd-nspawn: Starting Journal Service...
Sep  6 21:25:26 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Created slice system-getty.slice.
Sep  6 21:25:26 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Started Load/Save Random Seed.
Sep  6 21:25:26 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Mounted Huge Pages File System.
Sep  6 21:25:26 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Mounted FUSE Control File System.
Sep  6 21:25:26 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Mounted POSIX Message Queue File System.
Sep  6 21:25:26 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Started Journal Service.
Sep  6 21:25:26 server1 systemd-nspawn: Starting Flush Journal to Persistent Storage...
Sep  6 21:25:26 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Started Flush Journal to Persistent Storage.
Sep  6 21:25:26 server1 systemd-nspawn: Starting Create Volatile Files and Directories...
Sep  6 21:25:27 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Started Create Volatile Files and Directories.
Sep  6 21:25:27 server1 systemd-nspawn: Starting Update UTMP about System Boot/Shutdown...
Sep  6 21:25:27 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Started Update UTMP about System Boot/Shutdown.
Sep  6 21:25:27 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Reached target System Initialization.
Sep  6 21:25:27 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Reached target Timers.
Sep  6 21:25:27 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Listening on D-Bus System Message Bus Socket.
Sep  6 21:25:27 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Reached target Sockets.
Sep  6 21:25:27 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Reached target Basic System.
Sep  6 21:25:27 server1 systemd-nspawn: Starting Permit User Sessions...
Sep  6 21:25:27 server1 systemd-nspawn: Starting Login Service...
Sep  6 21:25:27 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Started D-Bus System Message Bus.
Sep  6 21:25:27 server1 systemd-nspawn: Starting D-Bus System Message Bus...
Sep  6 21:25:27 server1 systemd-nspawn: Starting Network Service...
Sep  6 21:25:27 server1 systemd-nspawn: Starting Network Time Service...
Sep  6 21:25:27 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Started Permit User Sessions.
Sep  6 21:25:27 server1 systemd-nspawn: Starting Cleanup of Temporary Directories...
Sep  6 21:25:27 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Started Console Getty.
Sep  6 21:25:27 server1 systemd-nspawn: Starting Console Getty...
Sep  6 21:25:27 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Reached target Login Prompts.
Sep  6 21:25:27 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Started Login Service.
Sep  6 21:25:27 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Started Cleanup of Temporary Directories.
Sep  6 21:25:27 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Started Network Time Service.
Sep  6 21:25:27 server1 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vb-nsdc: link becomes ready
Sep  6 21:25:27 server1 kernel: br0: port 2(vb-nsdc) entered blocking state
Sep  6 21:25:27 server1 kernel: br0: port 2(vb-nsdc) entered forwarding state
Sep  6 21:25:27 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Started Network Service.
Sep  6 21:25:27 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Reached target Network.
Sep  6 21:25:27 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Started Samba domain controller daemon.
Sep  6 21:25:27 server1 systemd-nspawn: Starting Samba domain controller daemon...
Sep  6 21:25:27 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Reached target Multi-User System.
Sep  6 21:25:27 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Reached target Graphical Interface.
Sep  6 21:25:27 server1 systemd-nspawn: Starting Update UTMP about System Runlevel Changes...
Sep  6 21:25:27 server1 systemd-nspawn: [#033[32m  OK  #033[0m] Started Update UTMP about System Runlevel Changes.
Sep  6 21:25:28 server1 systemd-nspawn: CentOS Linux 7 (Core)
Sep  6 21:25:28 server1 systemd-nspawn: Kernel 3.10.0-862.11.6.el7.x86_64 on an x86_64
Sep  6 21:25:29 server1 avahi-daemon[965]: Registering new address record for fe80::b0d6:faff:fecf:783f on vb-nsdc.*.
(Davide Principi) #6

Compare RPMs versions:

# rpm -q nethserver-dc
nethserver-dc-1.5.4-1.ns7.x86_64

Please attach the output of

systemctl status -M nsdc nsdc-run.socket

Mine is

● nsdc-run.socket - NSDC container remote command server
   Loaded: loaded (/etc/systemd/system/nsdc-run.socket; enabled; vendor preset: disabled)
   Active: active (listening) since Mon 2018-07-23 18:23:46 CEST; 1 months 15 days ago
     Docs: https://github.com/NethServer/nethserver-dc/blob/master/README.rst
   Listen: /var/lib/misc/nsdc-run.sock (Stream)
 Accepted: 111; Connected: 0

That socket path exists here.

You could try also

 systemctl stop -M nsdc nsdc-run.socket
 systemctl start -M nsdc nsdc-run.socket

(Re-)Executing this action might help too

/etc/e-smith/events/nethserver-dc-upgrade/S30nethserver-dc-upgrade
(Wijnand Mijnders) #7

First of all, thanks for your effort in helping me out!

Still no luck i’m afraid. The compete output of the commands is in a file because of the size (seems too large to include in a forum message). How can i get it to you? There is a lot of activity going on after issuing the S30nethserver-dc-upgrade command. I did a reboot after the dc-upgrade to be sure but that didn’t help either.

For completeness I’ve added the logoutput after adding a user in Nethserver, same problems concerning the missing nsdc-run.sock and the user adding fails.

Sep  7 14:38:52 server1 esmith::event[7930]: Event: user-create cursus Cursus /usr/libexec/openssh/sftp-server
Sep  7 14:38:52 server1 esmith::event[7930]: Traceback (most recent call last):
Sep  7 14:38:52 server1 esmith::event[7930]:  File "/bin/nsdc-run", line 38, in <module>
Sep  7 14:38:52 server1 esmith::event[7930]:    so.connect('/var/lib/machines/nsdc/var/lib/misc/nsdc-run.sock')
Sep  7 14:38:52 server1 esmith::event[7930]:  File "/usr/lib64/python2.7/socket.py", line 224, in meth
Sep  7 14:38:52 server1 esmith::event[7930]:    return getattr(self._sock,name)(*args)
Sep  7 14:38:52 server1 esmith::event[7930]: socket.error: [Errno 2] No such file or directory
Sep  7 14:38:52 server1 esmith::event[7930]: [ERROR] User cursus creation failed
Sep  7 14:38:52 server1 esmith::event[7930]: Action: /etc/e-smith/events/user-create/S40nethserver-dc-user-create FAILED: 1 [0.143501]
Sep  7 14:38:53 server1 esmith::event[7930]: Traceback (most recent call last):
Sep  7 14:38:53 server1 esmith::event[7930]:  File "/bin/nsdc-run", line 38, in <module>
Sep  7 14:38:53 server1 esmith::event[7930]:    so.connect('/var/lib/machines/nsdc/var/lib/misc/nsdc-run.sock')
Sep  7 14:38:53 server1 esmith::event[7930]:  File "/usr/lib64/python2.7/socket.py", line 224, in meth
Sep  7 14:38:53 server1 esmith::event[7930]:    return getattr(self._sock,name)(*args)
Sep  7 14:38:53 server1 esmith::event[7930]: socket.error: [Errno 2] No such file or directory
Sep  7 14:38:53 server1 esmith::event[7930]: [ERROR] failed to modify UPN suffixes
Sep  7 14:38:53 server1 esmith::event[7930]: Action: /etc/e-smith/events/user-create/S50nethserver-dc-sync-upn FAILED: 1 [0.323891]
Sep  7 14:38:53 server1 esmith::event[7930]: [NOTICE] clearing sssd cache for user cursus@pa3hfj.nl
Sep  7 14:38:53 server1 esmith::event[7930]: No cache object matched the specified search
Sep  7 14:38:53 server1 esmith::event[7930]: No cache object matched the specified search
Sep  7 14:38:53 server1 esmith::event[7930]: Action: /etc/e-smith/events/user-create/S90nethserver-sssd-clear-cache SUCCESS [0.055937]
Sep  7 14:38:53 server1 esmith::event[7930]: Event: user-create FAILED
Sep  7 14:38:53 server1 esmith::event[7948]: Event: password-policy-update cursus no
Sep  7 14:38:53 server1 esmith::event[7948]: [NOTICE] clearing sssd cache for user cursus@pa3hfj.nl
Sep  7 14:38:53 server1 esmith::event[7948]: No cache object matched the specified search
Sep  7 14:38:53 server1 esmith::event[7948]: No cache object matched the specified search
Sep  7 14:38:53 server1 esmith::event[7948]: Action: /etc/e-smith/events/password-policy-update/S10nethserver-sssd-clear-cache SUCCESS [0.019247]
Sep  7 14:38:53 server1 esmith::event[7948]: Traceback (most recent call last):
Sep  7 14:38:53 server1 esmith::event[7948]:  File "/bin/nsdc-run", line 38, in <module>
Sep  7 14:38:53 server1 esmith::event[7948]:    so.connect('/var/lib/machines/nsdc/var/lib/misc/nsdc-run.sock')
Sep  7 14:38:53 server1 esmith::event[7948]:  File "/usr/lib64/python2.7/socket.py", line 224, in meth
Sep  7 14:38:53 server1 esmith::event[7948]:    return getattr(self._sock,name)(*args)
Sep  7 14:38:53 server1 esmith::event[7948]: socket.error: [Errno 2] No such file or directory
Sep  7 14:38:53 server1 esmith::event[7948]: [ERROR] Faild to set expiry on user cursus
Sep  7 14:38:53 server1 esmith::event[7948]: Action: /etc/e-smith/events/password-policy-update/S30nethserver-dc-password-policy FAILED: 1 [0.141984]
Sep  7 14:38:53 server1 esmith::event[7948]: Event: password-policy-update FAILED
Sep  7 14:38:53 server1 esmith::event[7957]: Event: password-modify cursus@pa3hfj.nl /tmp/ng-EHbzx6
Sep  7 14:38:53 server1 esmith::event[7957]: Action: /etc/e-smith/events/password-modify/S25password-set SUCCESS [0.003236]
Sep  7 14:38:53 server1 esmith::event[7957]: Traceback (most recent call last):
Sep  7 14:38:53 server1 esmith::event[7957]:  File "/bin/nsdc-run", line 38, in <module>
Sep  7 14:38:53 server1 esmith::event[7957]:    so.connect('/var/lib/machines/nsdc/var/lib/misc/nsdc-run.sock')
Sep  7 14:38:53 server1 esmith::event[7957]:  File "/usr/lib64/python2.7/socket.py", line 224, in meth
Sep  7 14:38:53 server1 esmith::event[7957]:    return getattr(self._sock,name)(*args)
Sep  7 14:38:53 server1 esmith::event[7957]: socket.error: [Errno 2] No such file or directory
Sep  7 14:38:53 server1 esmith::event[7957]: Action: /etc/e-smith/events/password-modify/S30nethserver-dc-password-set FAILED: 1 [0.03395]
Sep  7 14:38:53 server1 esmith::event[7957]: Traceback (most recent call last):
Sep  7 14:38:53 server1 esmith::event[7957]:  File "/bin/nsdc-run", line 38, in <module>
Sep  7 14:38:53 server1 esmith::event[7957]:    so.connect('/var/lib/machines/nsdc/var/lib/misc/nsdc-run.sock')
Sep  7 14:38:53 server1 esmith::event[7957]:  File "/usr/lib64/python2.7/socket.py", line 224, in meth
Sep  7 14:38:53 server1 esmith::event[7957]:    return getattr(self._sock,name)(*args)
Sep  7 14:38:53 server1 esmith::event[7957]: socket.error: [Errno 2] No such file or directory
Sep  7 14:38:53 server1 esmith::event[7957]: Action: /etc/e-smith/events/password-modify/S40nethserver-dc-user-unlock FAILED: 1 [0.030531]
Sep  7 14:38:54 server1 esmith::event[7957]: Action: /etc/e-smith/events/password-modify/S90password-cleanup SUCCESS [0.627883]
Sep  7 14:38:54 server1 esmith::event[7957]: Event: password-modify FAILED
(Davide Principi) #8

Please upload it to https://gist.github.com/ (can choose both public/private). You can PM me if you like!

(Wijnand Mijnders) #9

Hopefully this works, I am new to this :grinning:

(Davide Principi) #10

I noticed that you updated from an old ns-samba version (4.6.11)

https://gist.github.com/pa3hfj/83a08dff3a2a910b81168cdc4d61323e#file-gistfile1-txt-L157

The update seems ok, however…

https://gist.github.com/pa3hfj/83a08dff3a2a910b81168cdc4d61323e#file-gistfile1-txt-L729

Failed to execute operation: No such file or directory

Try to execute again

systemctl -M nsdc enable --now nsdc-run.socket

…just to see if the error is the same.

(Wijnand Mijnders) #11

The results:

[root@server1 log]# systemctl -M nsdc enable --now nsdc-run.socket
Failed to execute operation: No such file or directory

I must add that according to the Software Centre updates-tab the system was up-to-date before nethserver-dc-upgrade command, apart from two entries that are there for a long time (far before this problem arose)

Naam 	Versie 	Release
libmspack	0.7	0.1.alpha.el7
python-markdown	2.4.1	2.el7
Updates CHANGELOG

Loaded plugins: changelog, fastestmirror, priorities
Loading mirror speeds from cached hostfile
 * base: centos.mirror.triple-it.nl
 * epel: mirror.i3d.net
 * extras: mirror.nforce.com
 * nethforge: mirror2.nethserver.org
 * nethserver-base: mirror2.nethserver.org
 * nethserver-updates: mirror2.nethserver.org
 * remi-safe: remi.mirror.ate.info
 * updates: mirror.nforce.com
188 packages excluded due to repository priority protections
changelog stats. 0 pkgs, 0 source pkgs, 0 changelogs
(Davide Principi) #12

The update transaction was acting on the NSDC container chroot, not the host system

Please try this command

signal-event nethserver-dc-upgrade

It also expands some templates I might forget in the commands above…

Check how it goes in /var/log/messages

(Wijnand Mijnders) #13

Hello Davide,

Well, i’m very glad to inform you that this command did the trick! :fireworks:

This solved it, there seemed to be a missing symlink:

server1 esmith::event[20584]: Created symlink from /etc/systemd/system/sockets.target.wants/nsdc-run.socket to /etc/systemd/system/nsdc-run.socket.

Davide, thank you very much for your perseverance!