Sssd, nmb, smb and winbind not starting after upgrade from 7.8

[graeleah (Ken Laurie)]

NethServer Version: 7.9.2009
Hi All

First time I have had some issues with nethserver that I couldn’t solve from reading the forum.

After upgrading from 7.8, sssd, nmb, smb and winbind will not start. sssd gets the status=1/FAILURE. While upgrading I had an issue that meant I had to restart the box. Ran the yum-complete-transaction and then ran the update. All via the command line. Seemed to work.

Couldn’t sign into email and realised that sssd was not running, so no email received by the server or sent. Sending from external I get user unknown. Cannot connect to the mail server from any clients include SOGo.
Tried a few of the suggestions in the forum with no success.
Any help would be appreciated. Any information required can be provided.

regards
Ken

[dnutan (Marc)]

@graeleah

While upgrading I had an issue that meant I had to restart the box.

Don’t know for sure if this applies to your case but looks similar:

SSSD start failed after update

You could try to reinstall only the corrupted packages, if any. First you need to update everything, I do not know why you have problems, probably some broken transaction. Blind shot: yum --disablerepo=* --enablerepo=nethserver-updates,nethserver-base,base,updates update I just fixed a machine with the same problem: rm -f /usr/lib64/ldb/modules/ldb/paged_results.so systemctl restart sssd

Another recent case you can follow is this one:

Can't access all my shared folder

@swit_ayhan03 Hi Ayhan If you have Backups, you also have “Config-Backups”… Reload the last Config-Backup, then reboot. You need to use Cockpit for this (Port 9090). The old Dashboard can not restore Backups anymore. This worked for me and a few Users with the same Issue… My 2 cents Andy

Things that might help diagnose the problem:

@davidep

account-provider-test dump
journalctl  -M nsdc

@davidep

 systemctl status -M nsdc samba
 systemctl status nsdc

Another useful test sometimes is

yum install -y nmap
nmap $(config getprop nsdc IpAddress)

Samba is not working (SSSD accountsprovider error)

Ok, the nmap command output says if all samba sub-processes are running correctly. Here’s the expected output: $ nmap nsdc Starting Nmap 7.60 ( https://nmap.org ) at 2018-06-07 09:19 CEST Nmap scan report for nsdc (XXXXXXXXXXXXXX) Host is up (0.00015s latency). rDNS record for XXXXXXXXXXXXXX Not shown: 987 closed ports PORT STATE SERVICE 53/tcp open domain 88/tcp open kerberos-sec 135/tcp open msrpc 139/tcp open netbios-ssn 389/tcp open ldap 445/tcp open microsoft-ds 4…

After Update from today no users

What is the nethserver-sssd version? rpm -q nethserver-sssd What does this command say? realm list Please check also: host -t SRV _ldap._tcp.$(hostname -d) $(config getprop nsdc IpAddress) host -t SRV _ldap._tcp.$(hostname -d) 127.0.0.1

[graeleah (Ken Laurie)]

Thanks Dnutan.

Tried SSSD start failed after update - yum command. No luck

Did a config restore and no luck. Now I have more services not running, however the extra services did start manually. SSSD still fails.

Account-provider-test dump appears fine.
journalctl -M nsdc seems fine. both winbindd and smbd finished and ready to server connections

systemctl status -M nsdc samba - active
systemctl status nsdc - active

Nmap
PORT      STATE SERVICE
53/tcp    open  domain
88/tcp    open  kerberos-sec
135/tcp   open  msrpc
139/tcp   open  netbios-ssn
389/tcp   open  ldap
445/tcp   open  microsoft-ds
464/tcp   open  kpasswd5
636/tcp   open  ldapssl
3268/tcp  open  globalcatLDAP
3269/tcp  open  globalcatLDAPssl
49152/tcp open  unknown
49153/tcp open  unknown
49154/tcp open  unknown

Nethsever-sssd version nethserver-sssd-1.7.0-1.ns7.noarch

host
Using domain server:
Name: 192.168.1.2
Address: 192.168.1.2#53
Aliases: 

_ldap._tcp.graeleah.com has no SRV record

[graeleah (Ken Laurie)]

Just tried /usr/sbin/sssd -l and received the following

[dp_module_open_lib] (0x0010): Unable to load module [ad] with path [/usr/lib64/sssd/libsss_ad.so]: libwbclient.so.0: cannot open shared object file: No such file or directory
[dp_target_init] (0x0010): Unable to load module ad
[be_process_init] (0x0010): Unable to setup data provider [1432158209]: Internal Error
[main] (0x0010): Could not initialize backend [1432158209]
[dp_module_open_lib] (0x0010): Unable to load module [ad] with path [/usr/lib64/sssd/libsss_ad.so]: libwbclient.so.0: cannot open shared object file: No such file or directory

The above was repeated 3 times then
dp_target_init] (0x0010): Unable to load module ad
[be_process_init] (0x0010): Unable to setup data provider [1432158209]: Internal Error
[main] (0x0010): Could not initialize backend [1432158209]
[sssd] [monitor_restart_service] (0x0010): Process [domain.com], definitely stopped!
[sssd] [monitor_cleanup] (0x0010): Error removing pidfile! (2 [No such file or directory])

[giacomo (Giacomo Sanchietti)]

You probably have a broken link inside this dir /usr/lib64/samba/wbclient/.
I can’t say what is the correct fix without inspecting the machine, but you could try to:

• delete the broken link
• reinstall the package: yum reinstall libwbclient

[graeleah (Ken Laurie)]

Thanks Giacomo. That worked. Very much appreciated.

regards
Ken