Forums

Jenz
Jenz
Offline
Resolved
0 votes
I have some big issues with my ClearOS installation. It all began with an update crashing the OS so it was unable to boot. Well, I fixed that by using Google, due to my limited linux knowledge. However, after that the Samba service will not start, so I got the idea to install the FTP service to be able to access the flexshares where I have some important files.
The FTP service installed fine, but I can not connect with any user on port 21. It keeps complaining about the wrong password.

Again using google, I managed to find this error message:
May  8 22:08:56 nas proftpd[32413]: 127.0.0.1 (192.168.10.200[192.168.10.200]) - FTP session opened.
May 8 22:08:56 nas nslcd[4650]: [05e3d8] <passwd="somepass"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
May 8 22:08:56 nas nslcd[4650]: [05e3d8] <passwd="somepass"> no available LDAP server found: Can't contact LDAP server


Tried with restarting LDAP service:

[root@nas log]# service slapd stop
Redirecting to /bin/systemctl stop slapd.service
[root@nas log]# service slapd start
Redirecting to /bin/systemctl start slapd.service
[root@nas log]# service slapd status -l
Redirecting to /bin/systemctl status -l slapd.service
● slapd.service - OpenLDAP Server Daemon
Loaded: loaded (/usr/lib/systemd/system/slapd.service; enabled; vendor preset: disabled)
Active: active (running) since Wed 2019-05-08 22:13:55 CEST; 11s ago
Docs: man:slapd
man:slapd-config
man:slapd-hdb
man:slapd-mdb
file:///usr/share/doc/openldap-servers/guide.html
Process: 32713 ExecStart=/usr/sbin/slapd -u ldap -h ${SLAPD_URLS} $SLAPD_OPTIONS (code=exited, status=0/SUCCESS)
Process: 32695 ExecStartPre=/usr/libexec/openldap/prestart.sh (code=exited, status=0/SUCCESS)
Main PID: 32716 (slapd)
CGroup: /system.slice/slapd.service
└─32716 /usr/sbin/slapd -u ldap -h ldap://127.0.0.1/

May 08 22:13:55 nas.local systemd[1]: Starting OpenLDAP Server Daemon...
May 08 22:13:55 nas.local prestart.sh[32695]: Configuration directory '/etc/openldap/slapd.d' does not exist.
May 08 22:13:55 nas.local prestart.sh[32695]: Warning: Usage of a configuration file is obsolete!
May 08 22:13:55 nas.local runuser[32699]: pam_unix(runuser:session): session opened for user ldap by (uid=0)
May 08 22:13:55 nas.local runuser[32699]: pam_unix(runuser:session): session closed for user ldap
May 08 22:13:55 nas.local slapd[32713]: @(#) $OpenLDAP: slapd 2.4.44 (Dec 4 2018 13:31:39) $
mockbuild@build64-1.clearsdn.local:/builddir/build/BUILD/openldap-2.4.44/openldap-2.4.44/servers/slapd
May 08 22:13:55 nas.local slapd[32716]: slapd starting
May 08 22:13:55 nas.local systemd[1]: Started OpenLDAP Server Daemon.


I'm so frustrated! What should I do?
Wednesday, May 08 2019, 08:47 PM
Share this post:
Responses (9)
  • Accepted Answer

    Thursday, May 09 2019, 03:24 PM - #Permalink
    Resolved
    0 votes
    LDAP will often restart after an update such as occurred. One thing that it does is a sanity check to avoid data corruption. Because it can fail at restarting when it does this sanity check, it can cause a myriad of problems since so many services depend on it. And we do depend on this package to perform well from upstream. That being said, openldap has some great recovery tools and we also include tools to back it up daily. So what are some reasons why it may fail?

    The biggest one I've seen has been power failure. If you can guarantee that the system has ALWAYS been properly shut down and the service properly stopped and no power failures then perhaps we do deserve some of the push back. But if your directory is corrupt because you downed your user database in the middle of a write and the system obliged by not letting you mount it without a proper repair, then it did its job.

    Of all the systems to go through this upgrade process, yours is the only one that (so far) has experienced this issue. So is this an issue with the distribution or something local?

    Your comments don't seem to match the claim that the system didn't boot ('crashes the boot system'). Is there another issue that you didn't report? There was one issue with booting (again, on the community version) that was fixed previously. I know that the new kernel causes a boot issue with a certain 'experimental hardware' board in my possession. But other than that, booting doesn't seem to be a problem with this update.

    The guest account is a bit immutable to the update/upgrade process. It is created initially when LDAP is initialized. So if it is missing, chances are it was corrupted somehow locally or your system did not initialize the LDAP database initially. Outside of that nothing really touches the guest account so if it is knackered, the probable cause is local LDAP database corruption (ie. not the fault of an updated but rather a problem waiting to show itself on the next reboot or update).
    The reply is currently minimized Show
  • Accepted Answer

    Jenz
    Jenz
    Offline
    Thursday, May 09 2019, 02:39 PM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    Jenz wrote:

    Thanks for the tip regarding WinSCP! I can now access the data. That's fine for now. ClearOS is now going to be replaced by Windows :)
    That is a bit of a kick in the teeth. I trust you'll be happy paying the $$$.


    Well, I don't have confidence in an OS that crashes the boot system after an automatic update. I need a reliable OS that does not cost me a lot of $$$ in support and maintenance and time. As for now I have put a lot of hours trying to resolve this issue. If you have the time to sit and fiddle around with this OS that's fine, it will be suitable for a lot of people, but I don't have that luxury. I don't pay much for Windows licenses, so for me the $ is not an issue (I have a MSDN subscription).
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, May 09 2019, 02:02 PM - #Permalink
    Resolved
    0 votes
    Jenz wrote:

    Thanks for the tip regarding WinSCP! I can now access the data. That's fine for now. ClearOS is now going to be replaced by Windows :)
    That is a bit of a kick in the teeth. I trust you'll be happy paying the $$$.
    The reply is currently minimized Show
  • Accepted Answer

    Jenz
    Jenz
    Offline
    Thursday, May 09 2019, 01:24 PM - #Permalink
    Resolved
    0 votes
    AS for the samba service, it failed due to not locating the guest-account. nmb and winbind is fine.
    The reply is currently minimized Show
  • Accepted Answer

    Jenz
    Jenz
    Offline
    Thursday, May 09 2019, 01:17 PM - #Permalink
    Resolved
    0 votes
    Thanks for the tip regarding WinSCP! I can now access the data. That's fine for now. ClearOS is now going to be replaced by Windows :)
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, May 09 2019, 01:01 PM - #Permalink
    Resolved
    0 votes
    Reinstalling generally wipes your disk so you will lose your flexshares. The only exception to this **may** be if you have your flexshares on a separate partition and you then have to install with custom partitioning.

    If it was in the last 10 days, then ClearOS keeps a daily config backup can you try restoring from there using the system config backup and restore menu?

    If not, how about troubleshooting samba? From the command line see which bits are working:
    systemclt status smb
    systemclt status nmb
    systemclt status winbind
    I am never sure when you do an don't need winbind. For any not running, try starting them - replace "status" with "start" in the above command. If anyfail, get the status with the -l switch. Also check the logs in /var/log/samba.

    If you need to recover flexshare data, you should be able to ger to it with WinSCP in the /var/flexshare/shares folder, but if you use that method to put them back you will have to fix up te permissions afterwards.
    The reply is currently minimized Show
  • Accepted Answer

    Jenz
    Jenz
    Offline
    Thursday, May 09 2019, 12:20 PM - #Permalink
    Resolved
    0 votes
    If I reinstall the ClearOS, will the data on the flexdrives be preserved?
    The reply is currently minimized Show
  • Accepted Answer

    Jenz
    Jenz
    Offline
    Thursday, May 09 2019, 12:19 PM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    Is the user set up as an FTP Server User in the User's menu or, from another view, in the FTP webconfig, click on the App Policies button (the methods are interchangeable)


    Yes, it's a ftp user.
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, May 08 2019, 09:26 PM - #Permalink
    Resolved
    0 votes
    Is the user set up as an FTP Server User in the User's menu or, from another view, in the FTP webconfig, click on the App Policies button (the methods are interchangeable)
    The reply is currently minimized Show
Your Reply