What type of hardware are you using: Raspberry Pi 3, 4+ What YunoHost version are you running: 12.0.16 How are you able to access your server: Direct access via physical keyboard/screen Are you in a special context or did you perform specific tweaking on your YunoHost instance ?: NO
Describe your issue
I switched off my raspberry to move it (sudo shutdown, I’m always careful to switch it off before unplugging it).
I plugged it back in a few minutes later, and it turned on correctly, but I realised that some services were no longer working, including Nextcloud. I try to connect to the YunoHost admin interface, but it’s impossible, no user is recognised. I try to do the same thing via SSH, same thing, impossible, even with SSH keys. No user recognised.
So I connected the raspberry to a screen and realised that the slapd service wasn’t running at start-up.
[FAILED] Failed to start slapd.service (Lightweight Directory Access Protocol).
See ‘systemctl status slapd.service’ for details.
Starting nslcd.service – LSB: LDAP connection daemon...
I’ve tried several different ways of connecting so that I can regenerate the LDAP config and see if I can resolve the problem, but it’s impossible. I don’t know what else to do.
Services that don’t require YunoHost LDAP work without a hitch.
Share relevant logs or error messages
root@(none):/# yunohost tools regen-conf sldap --force
Warning: The LDAP service is down, attempt to restart it
System has not been booted with systemd as init system (PID 1). Can’t operate.
Failed to connect to bus: Host is down
Info: The operation ‘Regenerate system configurations ‘sldap’’ could not be completed. Please share the full log of this operation using the command ‘yunohost log share 19700101-004751-regen_conf-sldap’ to get help
Error: Service slapd is not running but is required to perform this action
You can try to investigate what’s happening with ‘systemctl status slapd’
Well actually this sounds like you’ve been running this command from a rescue shell somehow so it’s expected (i think?) that systemd is not running .. Or was this from a chroot ? How did you enter that shell ?
Yes that sounds consistent with what the prompt looks like … But why not just do a regular boot and check the slapd system logs ? With systemctl slapd status ? Or the issue that you can’t even login on direct screen+keyboard after a regular boot ? What about using the root account ? (The password should be something like the very first password you chose during postinstall, or if you don’t remember it, you can indeed change it booting with init=/bin/bash and then running passwd to change it)