I have 18.08 single server system. A short while ago I had an unexpected, abrupt shutdown. I'm still mostly up and running but I can't backup my config via GUI. Job status says backup failed. Also when I restart Supervisor (which shows running, sometimes and shut down sometimes), job status says:
Could not read agent results. Write end dead null
and
Error. Error connecting to server (timeout). System error for connect: "Operation now in progress". Unable to connect to server 127.0.0.1. System reports error for connect: "Operation now in progress". No server is responding on this port null
Looking at messages, I see
!! tchdbput: Could not write key to DB "/var/cfengine/state/cf_lock.tcdb": read error
Looking at /var/cfengine/state I see (among other files) these two files: cf_lock.tcdb and cf_lock.tcdb.corrupt.
I'm optimistic that I've found my problem. I believe the abrupt shutdown happened while a lock was in effect and I now have a slightly corrupted system.
Obvious question: how can I repair this?
This link documents the command "mongod --repair" but I hesitate to do such a low-level repair without checking with the experts first. If this command is my best option, should I stop sipxecs first? Any other protection I should do? I do have a VM snapshot since I can't actually back up the config/vmail.
I'm hopeful this is at the heart of the problem but I'm open to any other advice. I was expecting to fix this and see if messages (and backup and Supervisor) come up fine. If it does, thorough testing and I'm happy. If it doesn't, I have one less error to fix and I will find the next one!
I'm also happy to post any other info, but I suspect it isn't yet necessary.
Thanks for any help