Forums

Resolved
0 votes
I have a few ClearOS systems, all running ClearOS7, latest update. One system (SAN2) is just a basic back-up system for the entire network. It networks happily with all othe systems using rsync, filezilla, etc. It used to work with Windows systems in the network, as I set it up without an Account Manager system, just a basic filesharing system. Suddenly, my SAN2 system has an Account Manager, and it is offline. I assume it was entered into the system via yum update, as I cannot remember having done that myself. Obviously I cannot use Samba now.
I have seen the different posts on this forum, so I know it will not be easy to remove slapd. I can rebuild the system from scratch which would be a bit of an embarrasment. Before doing that and before I spend too much time on this common issue, I would be interested to know whether there currently is an easy fix so that I can re-use Samba for simple filesharing. Status of slapd:
[root@san2 ~]# service slapd status
Redirecting to /bin/systemctl status slapd.service
● slapd.service - OpenLDAP Server Daemon
Loaded: loaded (/usr/lib/systemd/system/slapd.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since ma 2022-05-16 19:05:33 CEST; 4min 4s ago
Docs: man:slapd
man:slapd-config
man:slapd-hdb
man:slapd-mdb
file:///usr/share/doc/openldap-servers/guide.html
Process: 3426 ExecStart=/usr/sbin/slapd -u ldap -h ${SLAPD_URLS} $SLAPD_OPTIONS (code=exited, status=1/FAILURE)
Process: 3386 ExecStartPre=/usr/libexec/openldap/prestart.sh (code=exited, status=0/SUCCESS)

mei 16 19:05:33 san2.calluna-ventures.com prestart.sh[3386]: Configuration directory '/etc/openldap/slapd.d' does not exist.
mei 16 19:05:33 san2.calluna-ventures.com prestart.sh[3386]: Warning: Usage of a configuration file is obsolete!
mei 16 19:05:33 san2.calluna-ventures.com runuser[3390]: pam_unix(runuser:session): session opened for user ldap by (uid=0)
mei 16 19:05:33 san2.calluna-ventures.com runuser[3390]: pam_unix(runuser:session): session closed for user ldap
mei 16 19:05:33 san2.calluna-ventures.com slapd[3426]: @(#) $OpenLDAP: slapd 2.4.44 (May 4 2022 10:32:43) $
root@build-x86_64-1.orem.clearos.com:/builddir/build/BUILD/openldap-2.4.44/openldap-2.4.44/servers/slapd
mei 16 19:05:33 san2.calluna-ventures.com systemd[1]: slapd.service: control process exited, code=exited status=1
mei 16 19:05:33 san2.calluna-ventures.com systemd[1]: Failed to start OpenLDAP Server Daemon.
mei 16 19:05:33 san2.calluna-ventures.com systemd[1]: Unit slapd.service entered failed state.
mei 16 19:05:33 san2.calluna-ventures.com systemd[1]: slapd.service failed.
[root@san2 ~]#
Monday, May 16 2022, 06:26 PM
Share this post:
Responses (4)
  • Accepted Answer

    Tuesday, May 17 2022, 04:11 PM - #Permalink
    Resolved
    0 votes
    Thanks again. I will rebuild my server and stick to webconfig as much as possible, certainly for using Samba. Hopefully this problem doesn't come back.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, May 17 2022, 03:20 PM - #Permalink
    Resolved
    0 votes
    If you use Webmin for Samba, it will break the ClearOS implementation of Windows Networking/Flexshares and I don't know how to make work again. Other functions may be OK in Webmin but I can't say which are and which aren't. I have no idea what Webmin tries to do for users.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, May 17 2022, 02:52 PM - #Permalink
    Resolved
    0 votes
    Thank you, Nick. Where would we be without you? I only blame myself, but I am not really aware what went wrong. Next to the webconfig I use webmin for things webconfig doesn't handle well like LVM, RAID or iSCSI configs and of course the file manager. Sometimes, while working in webmin, I would get a notification of new sofware which I normally blindly accept. That's probably the cause and, yes, I have probably also used webmin for making Samba changes. While I will not blame anybody besides myself I find it peculiar that this problem can still arise so easily and it is so difficult to deal with. Rebuilding my very simple server wouldn't be difficult. I am just a bit embarrassed this would still be necessary as this seems to have been a common problem for years. But your help is greatly appreciated!
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, May 17 2022, 09:11 AM - #Permalink
    Resolved
    0 votes
    The accounts system would not have initialised itself, or at least should not. There was an update to openldap recently but that is just a basic update, but to update, you must have already had it installed. IIRC ClearOS Samba insists on having LDAP initialised before you initialise Samba, so have you been doing some command-line work and adding users manually with something like useradd? Also setting up Samba manually rather than through the Webconfig, Windows Networking and Flexshares?
    The reply is currently minimized Show
Your Reply