@Bert, @Haioken, and @doenietzomoeilijk
The update in question that seems to have upset things here would appear to be the system wide shift from upstream that moved our base from CentOS 7.3 to 7.4 around the time that Rockstor 184.108.40.206 was released.
I.e, having just updated a system from Rockstor 3.9.1-10 to 3.9.1-13, samba and co were updated from 4.4.4 to 4.6.2 and initially that caused a failure of the newly upgraded samba to start due to a nmbd failure:
dell1 systemd: Stopping Samba NMB Daemon...
dell1 systemd: Starting Samba NMB Daemon...
dell1 nmbd: /usr/sbin/nmbd: /usr/lib64/samba/libreplace-samba4.so: version `SAMBA_4.4.4' not found (required by /lib64
dell1 nmbd: /usr/sbin/nmbd: /usr/lib64/samba/libwinbind-client-samba4.so: version `SAMBA_4.4.4' not found (required by
dell1 systemd: nmb.service: main process exited, code=exited, status=1/FAILURE
dell1 systemd: Failed to start Samba NMB Daemon.
dell1 systemd: Unit nmb.service entered failed state.
dell1 systemd: nmb.service failed.
However in the above case an:
systemctl restart nmb.service
resulted in nmbd starting successfully and consequently samba also. A reboot would have done the same and a subsequent reboot seems to be functioning as expected, ie prior working samba share still working.
So ‘so far’ I’ve only seen a momentary samba issue related to this system wide update.
@doenietzomoeilijk your log appears to indicate a failure of your system to update, ie you don’t appear to be on the new samba version:
yum list installed samba
Loaded plugins: changelog, fastestmirror
Loading mirror speeds from cached hostfile
* base: centos.mirroring.pulsant.co.uk
* epel: www.mirrorservice.org
* extras: centos.mirroring.pulsant.co.uk
* updates: centos.mirroring.pulsant.co.uk
samba.x86_64 4.6.2-10.el7_4 @updates
the failure of the update is also indicated by the lower version in your links:
ls -la /usr/lib64/libwbclient.so*
lrwxrwxrwx 1 root root 19 Sep 20 14:06 /usr/lib64/libwbclient.so.0 -> libwbclient.so.0.13
lrwxrwxrwx 1 root root 40 Sep 20 14:06 /usr/lib64/libwbclient.so.0.13 -> /etc/alternatives/libwbclient.so.0.13-64
ie this successfully updated machine shows the 0.13 version like @Haioken’s example and @Bert’s successful re-install example.
Which updates release are you subscribed to: testing or stable? I suggest you try and run a system wide update and see what error messages, if any, you see in the logs.
@Haioken Thanks for doing a bunch of the diagnosis here. And yes this is “Strange”. I’m trying a few more systems here that are old enough to be affected and see if anything else sheds light on this.