@D_Jones Hello.
Just chipping in on the NUT bit:
I think this is a red herring with regard to your other report details as Rockstor’s NUT version and/or CentOS 7 systemd versions currently has a bug concerning the systemd-tmpfiles, I believe a fix for this is released in later versions however I don’t think it affects basic NUT operation and seem to remember coming across this way back when doing the NUT stuff.
Although our 2.7.2-3.el7 version is meant to have addressed it:
https://bugzilla.redhat.com/show_bug.cgi?id=1187286
I.e. I have the same report here:
Mar 7 19:07:13 cube systemd-tmpfiles[2500]: Failed to open '/etc/tmpfiles.d/nut-run.conf', ignoring: No such file or directory
Mar 7 19:07:13 cube sm-notify[2503]: Version 1.3.0 starting
Mar 7 19:07:13 cube postgresql-check-db-dir: Executing: /usr/bin/postgresql-check-db-dir /var/lib/pgsql/data
Mar 7 19:07:13 cube upsmon: fopen /var/run/nut/upsmon.pid: No such file or directory
Mar 7 19:07:13 cube upsmon: Using power down flag file /etc/ups/killpower
Mar 7 19:07:13 cube upsmon: UPS: ups@OpenWrt (slave) (power value 1)
And it is also present in @alexey’s NUT report here on the forum:
[SOLVED] Failed to start NUT-UPS service due to a system error
and @AngeleToR’s NUT report here:
[SOLVED] UPS service fails to start
Though in both cases and mine I believe, it was due to other issues blocking the NUT startup, ie incorrect configuration or in my case my system was on another network so couldn’t reach its’s UPS.
So hence no direct connection between NUT and LDAP.
I see from your post update that you have made some progress re finding network configuration changes. This may also point to why the openVPN rockon wouldn’t start and possibly the NUT and LDAP if your nut config is network related.
Sorry not more help here.