After a system reboot, you might notice all-status.sh script report that slapd is down even when it is up and running. The exact message would be :
"slapd dead but pid file exists"
When system is rebooted, the init script doesn't get a chance to clean the pid files properly since the stop() isn't invoked. Hence to avoid running in to the issue, run all-stop.sh before rebooting the system.
In such a scenario you may see a lot of errors in Postgres and Zookeeper logs.
This usually means that the slapd process stopped abnormally, and a pid file (or similar) was left in the file system, which is keeping the server from restarting.
Remove /var/run/slapd.pid, and then try to restart the services for Postgres and Zookeeper.
Hey - is this a problem with the init script that someone in the community could fix? It would make on-prem consumers w/ big corporate IT groups happier...
if i had any experience with this sort of thing at all i would do it myself - but i would rather let someone with more experience SHOW us how to resolve this.