Cron reschedule event error

Hi @jpfssi,

I can’t seem to reproduce the described behavior on any environments yet. And any searches regarding the subject I’ve done so far don’t immediately appear to point towards anything that seems to apply here either.

Consider using the WP Crontrol plugin to check for further information/logs regarding this message, which provides you with more information as to what is happening in the WordPress cron system on this specific environment.

The fact that it doesn’t occur on the staging environment with a very similar set-up might also provide you with further pointers, are there any differences between those environments which could result in this behavior occurring on one of them; but not the other?

Kind regards, Jarno

I’ll take a look at the plugin however, I am now seeing this error on my other sites as well as all the staging sites including the fssi-ca.com one. The frequency at which they occur and the time of day all differ.

Hi @jpfssi,

If the common denominator between the sites where you experience this issue is that they are all hosted with the same Hosting Provider (A2Hosting), then I would suspect that this behavior could be related to what they mention in this article:

https://www.a2hosting.com/kb/developer-corner/linux/cron-jobs-reset-to-15-minute-intervals/

Kind regards, Jarno

It just seems a little inconsistent that the error is mostly showing up on the primary site (fssi-ca.com) and the other sites including the staging sites do not get similar errors and others don’t have it at all. In fact the staging site to fssi-ca.com has this specific cron error 3 times the entire month of April while the live site has gotten at least one on a daily basis. There is significantly less or almost zero traffic on the staging sites so I assume the WP cron would occur more often there.

I did install the WP-Crontrol, however, I’m not sure what to look what to do with it as it is showing me which cron tasks are currently running, edit the task, check how often it runs and if I would like to create a new task to schedule.

Hi @jpfssi,

It seems that the issue is related specifically to saving scheduled tasks on your WordPress installation. Though as we haven’t been able to replicate this behavior, nor have we had other reports about similar issues yet; it does seem to be isolated to this specific environment, rather than it being an issue caused by the plugin itself.

If we know how this issue can be replicated on a fresh WordPress installation with the Really Simple SSL plugin, we would be happy to take a closer look. But at the moment I don’t really have any further pointers as to what causes this to occur in your case.

Kind regards, Jarno

Could these errors occur due to site inactivity? I did read that scheduled WP Cron tasks could produce errors due to site inactivity. I do have other sites that have less traffic that also have cron tasks that give errors.

I also get several of those every single day on a couple of live sites:

Cron reschedule event error for hook: rsssl_every_five_minutes_hook, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {"schedule":"rsssl_five_minutes","args":[],"interval":300}

Is there a way to solve this please?

Hi @dsl225,

These errors are most-likely the result of an issue related to the WordPress cron system, which is responsible for scheduling tasks to occur at specified times; and the “rsssl_every_five_minutes_hook” cannot be rescheduled as the cron event list cannot be saved.

There are a number of potential causes for such issues, e.g. file permissions, low memory limit, or a misconfiguration with the cron settings on your environment,

– Check if your server or hosting provider has limitations or restrictions on cron jobs. If there are restrictions, you may need to adjust your site’s cron schedules or discuss these restrictions with your hosting provider.

– If WordPress doesn’t have sufficient permissions to write to the files and folders it needs to, this type of error could occur as a result. Ensure that WordPress is able to write to the wp-cron.php file and the /wp-content/ directory.

– Try deactivating all of your WordPress plugins temporarily, then reactivating them one by one. This can help to identify whether perhaps one of your plugins is causing this issue.

– If your PHP memory limit is too low, WordPress may not be able to execute cron jobs effectively. You can try increasing the PHP memory limit in your server configuration (https://woocommerce.com/document/increasing-the-wordpress-memory-limit/)

Alternatively, if you could provide us with the steps to replicate this behavior on a fresh WordPress environment with just the Really Simple SSL plugin enabled, that would allow us to try and set this up for ourselves to determine the cause of the issue.

Kind regards, Jarno

Thanks but this sounds quite complicated and don’t well understand why all those checks would be needed on a healthy installation.

Anyhow, I don’t think such checks are really relevant as this cron is for every 5 minutes and I only get 5-6 such errors/day – so, obviously, all others have worked. If there were such issues as those you suggest none of those cron would work.

Hello @dsl225,

The behavior should not be caused by the RSSSL plugin specifically but rather occurs due to some factor outside of the plugin (e.g., server configuration/restrictions). The items that I shared previously are the most common causes of this issue, which I would recommend checking to narrow down the potential causes a bit further.

As I currently only know the error message that was logged on your site, but don’t have any further information or context about the server configuration, potential restrictions etc, it would be somewhat challenging to provide more specific guidance on which steps would be necessary in your case.

Kind regards, Jarno