Cron Jobs no longer running or disappeared from Schedule (PBXact v16)

I have 2 different PBXact v16 appliances that seem to have stopped running their weekly backup job.

The Backup jobs on BOTH appliances complete successfully if I run them manually via the command-line.


Appliance A - The backup is still scheduled but despite there being entries in the Cron log to show the job being triggered as usual on 30-Mar & 6-Apr, there’s nothing in the Backup log to suggest they even started - Any ideas where else to look for a reason why the job didn’t run ?

Appliance A - Scheduled Cron Jobs (for user ‘asterisk’)

Appliance A - Cron Log (filtered by the word ‘backup’)
image

Appliance A - Backup Log (filtered by Year/Month & the phrase ‘running backup’ - typically used in the 1st log entry for a Backup job)
image

Appliance A - There were the following MODULE UPDATES since the last successful backup on 16-Mar.


Appliance B - Most of the scheduled Cron jobs have simply vanished for some unknown reason - Is there a way to reset the default Cron jobs for a PBXact v16 deployment ?

Appliance B - Scheduled Cron Jobs (for user ‘asterisk’)
image

Appliance B - Cron Log (filtered by the word ‘backup’)
image

Appliance B - Backup Log (filtered by Year/Month & the phrase ‘running backup’ - typically used in the 1st log entry for a Backup job)
image

Appliance B - There has been NO MODULE UPDATES since the last successful backup on 30-Mar.

I have experienced the same situation. The fastest solution in my case is to disable and re-enable the backup schedule so the cron job gets regenerated.

Thanks for your comment.

Rather than remove & re-add the backup schedule, I simply changed the start time & re-saved the backup job & it also re-created the backup related CRON jobs.

As for all the other stuff, a couple of the default PBXact related jobs re-appeared on their own, but I had to manually re-add the rest via the CLI (using another working PBXact deployments as a template/reminder of what was missing).

Sorry for the confusion. What I meant was to toggle the enable button off and on again, I didn’t mean to completely delete the backup job.

Changing any of the parameters of the scheduling would also get the cron job to get regenerated, as you did.

This has been ongoing for a long time, is there anyone at Sangoma aware of this?

I don’t use the ‘distro’ and have never had this problem.

1 Like

Yes, I’ve seen quite a few posts for some time relating to similar things (in particular, Certificates not being updated, possibly because the update job is not running/getting deleted somehow), but I don’t recall seeing any official response/comment recognising this as a potential problem and/or why it might be happening (even a button/utility to verify & re-add any missing default ones would be a start).

I think the best thing for me (& possibly others) to do is keep a copy of the CRON jobs & periodically check they are all present/re-add them if necessary.

I also experienced all cron jobs gone completely.
Found out when my calendar time conditions stopped working because the calendars were not being refreshed.
Looking at the asterisk user’s crontab, I was really shocked to find it completely empty.
Since I didn’t have a backup of the contents, I just reinstalled all modules, hoping all entries would be recreated. Luckily, they were, at least the ones related to functionalities currently in use.