NethServer Version: 7.6.1810 (final)
the last 2 days were hard. My proxmox had som filesystem failures. After repairing the fs, the proxmox was o.k. again, but the nethserver-vms then showed xfs-failures. So I decided to do a desaster recovery with my hotsync slave. But this wasn’t the best idea, because if you have a production machine with subscription and a slave without subscription some repos seem to be mixed up. Also the mysql-database wasn’t synced, which was bad, because we’re using sogo-calender for event-managing in my company. Fortunaltely I was able to export the old databases from the crahed machine and no data were lost.
Otherwise I had a backup from the last night before, so desaster recorery from back was also an option. Always good to have 2 options.
But after recovery I’ve now a problem which I can’t solve.
Allmost everything now works fine again on the now masterrole ex-slave, except the nsdc-service doesn’t start automatically at boot. When I start it manually from (old) server-manager it works.
The service is enabled in config, but provisiontype is “ns6upgrade”.
I looked at
journalctl -M-nsdc --since"xxxx" but found no hint.
Also in messages.log I can’t find a hint why.
I also did
signal-event nethserver-sssd-save and
So please @davidep can you give me some advice?