JetBackup Error
Answered
When I try to look at my backups, I get the following error: "Failed loading panel preload information. Error: Unknown Error"
-
Hey there! Usually it's best to contact JetBackup directly for issues, but I have some ideas on this one.
Usually when this happens this is related to JetBackup's internal version of MongoDB not starting properly. If you check /usr/local/jetapps/var/log/jetbackup5/jetbackupd.log you'll likely find entries similar to this:
[14/Mar/2022 18:00:17 +0000] [PID 2159574] [ERROR] [JetBackupdReady] Failed starting jetbackup5d service as JetMongo is not ready Error: No suitable servers found (`serverSelectionTryOnce` set): [connection refused calling ismaster on 'localhost:27217']Can you try running this to see if that takes care of the issue?
systemctl restart jetmongodI would still recommend checking that log to see if you can track down the root cause of the issue.
0 -
the log file shows as you described and the command fails. I tried to create an account on the JBu forums but am still waiting on the activation email...
journalctl -xe says " Failed starting jetbackup5d service as JetMongo is not ready Error: No suitable servers found (`serverSelectionTryOnce` set): [connection refused calling hello on 'localhost:27217']"
0 -
The restart command fails? Does it give any additional details?
0 -
journalctl -xe says "Failed starting jetbackup5d service as JetMongo is not ready Error: No suitable servers found (`serverSelectionTryOnce` set): [connection refused calling hello on 'localhost:27217']"
0 -
That sounds right to me - and what happens when you try and restart it with that command?
0 -
[root@server ~]# systemctl restart jetmongod
Job for jetmongod.service failed because the control process exited with error code. See "systemctl status jetmongod.service" and "journalctl -xe" for details.0 -
systemctl status jetmongod.service
* jetmongod.service - High-performance, schema-free document-oriented database
Loaded: loaded (/usr/lib/systemd/system/jetmongod.service; enabled; vendor preset: disabled)
Active: activating (auto-restart) (Result: exit-code) since Fri 2024-05-03 10:11:16 EDT; 13s ago
Docs: https://docs.mongodb.org/manual
Process: 29627 ExecStartPre=/usr/local/jetapps/usr/bin/jetmongodready (code=exited, status=1/FAILURE)
Main PID: 564 (code=exited, status=0/SUCCESS)May 03 10:11:16 server.manzwebdesigns.com systemd[1]: jetmongod.service: control process exited, code=exited status=1
May 03 10:11:16 server.manzwebdesigns.com systemd[1]: Failed to start High-performance, schema-free document-oriented database.
May 03 10:11:16 server.manzwebdesigns.com systemd[1]: Unit jetmongod.service entered failed state.
May 03 10:11:16 server.manzwebdesigns.com systemd[1]: jetmongod.service failed.0 -
That's definitely something JetApps will need to look at. Maybe antonJetApps has an idea?
0 -
Thanks for your help!
0 -
Sure thing - I'm sorry I can't offer more directly!
0 -
Hello,
Please try the steps from the following KB article in order to troubleshoot this issue.
https://billing.jetapps.com/index.php?rp=/knowledgebase/127/JetBackup-5.3.9-Update-Failed.html
If the issue persists, please do not hesitate to contact our Support Team by emailing support@jetapps.com
Best Regards,
kevinJetApps0 -
That fixed it, thanks!
0 -
Thanks kevinJetApps!!!
0 -
No problem, I'm glad to hear that JB is up and running again!
1
Please sign in to leave a comment.
Comments
14 comments