G’day,
We’ve been monitoring full backups in particular over the weekend, and are happy with their execution.
Please let us know if you notice any other issues in this interim period before JetApps fix it - again. :-)
Cheers,
LEOPARD.host
JetApps have responded confirming the “return of the bug” - much like they had to demolish v4 and build v5 from scratch due to foundational issues in v4, it seems they struggle with on-boot events, timings and dependencies for successful service starting.
"Although we successfully fixed this problem in version 5.2.8, it seems that the error still occurs in version 5.2.11 because the jetbackup5d.service initiates before the cPanel services after a reboot. This issue has been resolved in our v5.3 update which is expected to be released to STABLE at the end of Q4 2023."
They also checked over FTP Accounts backing up when an account is suspended, and this other unrelated error comes down to a glitch in cPanel API behaviour, which is slowly being fixed too:
"So, in the case that the account is suspended, the FTP accounts are not being backed up, and there is a GIT issue #JBB1136 to ensure this is resolved in a future version. This issue has been resolved in JetBackup v5.3.3 and was released to public EDGE already, but not yet to STABLE."
With the issue we contacted them about, it seems the actual fix is a month or two away, however restarting the JetBackup service once the machine is active for a while gets the jobs functional again. The reason we encountered this re-emerging bug is because of the hypervisor updating requiring VM shut-downs.
This issue is being marked as monitoring. If we are happy with job executions into next week, we will close it pending the STABLE release of the fixes mentioned. Thank you for your patience as we investigate.
G’day,
We’ve raised a ticket with JetApps (212478) due to noticing the error rate for backup jobs increasing in an out-of-the-ordinary fashion. It is reporting “no accounts found for backup” when the jobs fail to run properly, but then will work fine the following day for example - no rhyme or reason to it, no system impacts when this happens.
Backups are still operational however not to the normal frequencies until this is resolved with the developer.
Please let us know if you’ve any questions or concerns.
Cheers,
LEOPARD.host
Network: AS138521