Duplicate Cron removed from xf_job, and never gets requeued

[Jake B.]

Not sure specifically what led to it being removed, but a customer of ours contacted us about their XF crons no longer running, and I found that the job wasn't in the xf_job table, and it looks like XenForo only queues the cron job when either the existing one finishes, or when a cron is saved. It's possible the behavior of this is different in 2.2, but I haven't been able to check yet as the person who had this issue is still running 2.1

 

[Chris D]

It's just a case of re-queueing the job either by triggering a cron save or adding it manually as you noted.

There's generally no expectation for it to ever be removed so the focus needs to be on identifying and preventing that root cause.

 

[Jake B.]

Did some searching on whether this has come up before, and this was all I came across: https://xenforo.com/community/threa...sts-running-ajax-job-php.147830/#post-1262272

Currently the recommended workaround is to duplicate your xf_job table (and its contents e.g. xf_job_bak) and then empty/truncate the original table.

Things should start moving normally.

has something changed since then, or did I misinterpret your response?

 

[Chris D]

That advice was for a very specific issue that is no longer relevant.

For the general issue of the cron entry being missing from the job table, see here for a similar bug report:

Not planned - Rebuild corrupted or missing cron job via admin ui

If something happens to the "cron" job in xf_job (eg it becomes corrupted or missing), then cron entries will not run. The only way to re-create the cron job is to create or save a cron entry - however, for a server running in production, you cannot edit any existing cron entries without...

xenforo.com