I have freeipa with ad-trust installed on centos 8 . It was working perfectly fine. Today after I updated the OS via dnf, the IPA server fails to start via "ipactl start" command because "smb" service fails to start . All other services start successfully. I have also run "ad-trust-install" again but it didnt work.
$ rpm -q freeipa-server freeipa-client ipa-server ipa-client 389-ds-base pki-ca krb5-server package freeipa-server is not installed package freeipa-client is not installed ipa-server-4.8.0-13.module_el8.1.0+265+e1e65be4.x86_64 ipa-client-4.8.0-13.module_el8.1.0+265+e1e65be4.x86_64 389-ds-base-1.4.1.3-7.module_el8.1.0+234+96aec258.x86_64 pki-ca-10.7.3-1.module_el8.1.0+238+005506d1.noarch krb5-server-1.17-9.el8.x86_64
$ ipactl start Existing service file detected! Assuming stale, cleaning and proceeding Starting Directory Service Starting krb5kdc Service Starting kadmin Service Starting named Service Starting httpd Service Starting ipa-custodia Service Starting pki-tomcatd Service Starting smb Service Failed to start smb Service Shutting down Hint: You can use --ignore-service-failure option for forced start in case that a non-critical service failed Aborting ipactl
$cat /var/log/messages
smb.service: Failed with result 'exit-code'. id1 winbindd[10102]: exit_daemon: daemon failed to start: Failed to initialize passdb backend! Check the 'passdb backend' variable in your smb.conf file., error code 22 id1 smbd[10364]: [2020/02/16 01:59:23.483659, 0] ../../source3/passdb/pdb_interface.c:171(make_pdb_method_name) id1 smbd[10364]: No builtin nor plugin backend for ipasam found
$ pdbedit -s /dev/null -b ipasam -d5 |grep Error Can't initialize passdb backend. Error loading module '/usr/lib64/samba/pdb/ipasam.so': /usr/lib64/samba/pdb/ipasam.so: undefined symbol: DEBUGLEVEL_CLASS
This is CentOS-specific issue, introduced by unorderly rebuilt samba and ipa packages.
It is tracked at https://bugs.centos.org/view.php?id=16929. FreeIPA upstream has nothing to do with CentOS packages -- we asked already for a rebuild a month ago.
Metadata Update from @abbra: - Issue close_status updated to: invalid - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.