Symptoms
You may find that you are unable to use JetBackup through the WHM interface. When you view the '/var/log/messages' log file, you see errors like this happening every thirty seconds or so.
Sep 7 11:55:42 ns2 systemd: jetmongod.service: main process exited, code=killed, status=6/ABRT
Sep 7 11:55:42 ns2 systemd: Unit jetmongod.service entered failed state.
Sep 7 11:55:42 ns2 systemd: jetmongod.service failed.
...
Sep 7 11:55:57 ns2 systemd: jetmongod.service holdoff time over, scheduling restart.
Sep 7 11:57:03 ns2 systemd: jetmongod.service: main process exited, code=killed, status=6/ABRT
Sep 7 11:57:03 ns2 systemd: Unit jetmongod.service entered failed state.
Sep 7 11:57:03 ns2 systemd: jetmongod.service failed.
Description
When you find JetBackup is not responding, and the 'jetmongodb' service is constantly restarting, there may be an issue with jetmongodb database corruption. Viewing the JetBackup MongoDB log may show errors like this:
{"t":{"$date":"2021-09-07T11:03:32.317-04:00"},"s":"E", "c":"STORAGE", "id":22435, "ctx":"TTLMonitor","msg":"WiredTiger error","attr":{"error":0,"message":"[1631027012:317466][313287:0x7f93529d9700], file:index-6--6973543040496432733.wt, WT_SESSION.open_cursor: __wt_block_read_off, 283: index-6--6973543040496432733.wt: read checksum error for 4096B block at offset 8192: block header checksum of 0xb850a298 doesn't match expected checksum of 0x2b3d433f"}}
{"t":{"$date":"2021-09-07T11:03:32.320-04:00"},"s":"F", "c":"-", "id":23089, "ctx":"TTLMonitor","msg":"Fatal assertion","attr":{"msgid":50853,"file":"src/mongo/db/storage/wiredtiger/wiredtiger_util.cpp","line":446}}
{"t":{"$date":"2021-09-07T11:03:32.321-04:00"},"s":"F", "c":"-", "id":23090, "ctx":"TTLMonitor","msg":"\n\n***aborting after fassert() failure\n\n"}
{"t":{"$date":"2021-09-07T11:03:32.321-04:00"},"s":"F", "c":"CONTROL", "id":4757800, "ctx":"TTLMonitor","msg":"Writing fatal message","attr":{"message":"Got signal: 6 (Aborted).\n"}}
This particular error shows a bad checksum on the 'WiredTiger' component. We've opened an upstream case with Imunify's team to investigate this further. For reference, the case number is UPS-395. Follow this article to receive an email notification when a solution is published in the product.
Workaround
Use the JetBackup Disaster Recovery page at "Home / Plugins / JetBackup". If possible, use the 'Recover from Disaster' setting to regain access.
Comments
0 comments
Article is closed for comments.