# Cron and Wordpress action scheduler

**URL:** <https://forum.virtualmin.com/t/cron-and-wordpress-action-scheduler/113528>\
**Category:** Help! (Home for newbies)\
**Created:** [January 6, 2022, 4:54pm UTC](https://forum.virtualmin.com/t/cron-and-wordpress-action-scheduler/113528 "2022-01-06T16:54:15Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![sean.latitude](https://cdn.forum.virtualmin.com/letter_avatar_proxy/v4/letter/s/7ba0ec/32.png) [@sean.latitude](https://forum.virtualmin.com/u/sean.latitude)\
**Post date:** [January 6, 2022, 4:54pm UTC](https://forum.virtualmin.com/t/cron-and-wordpress-action-scheduler/113528/1 "2022-01-06T16:54:15Z")

</div>

**Operating system** CentOS Linux 7.9.2009  
**Webmin version** 1.984 **Usermin version** 1.834  
**Virtualmin version** 6.17

Hello all,  
I have been using Virtualmin happily for a number of years but have run into an issue I don’t know how to get past and am asking for help!

I run some Wordpress sites which have auto updates and other scheduled actions running from time to time (at least they used to run smoothly). For a couple of months I have had to run items manually. I have now added a cron job to force action-scheduler to run once an hour but ideally I’d like it to work as it did before.

Can anyone help give me some tips on what to look for and how to go about finding out why things just stopped.

It might be worth noting I went as far as setting up a new server and moved one of the sites onto the new server and it made no difference.

---

<div class="post-metadata">

**Author:** ![suther](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/suther/32/2163_2.png) [@suther](https://forum.virtualmin.com/u/suther)\
**Post date:** [January 7, 2022, 12:43pm UTC](https://forum.virtualmin.com/t/cron-and-wordpress-action-scheduler/113528/2 "2022-01-07T12:43:44Z")

</div>

You might start at your wordpress installation… check the logs and see if there are any error’s while trying to run those upgrade-commands.  
Don’t know how WP it currently do… if it’s some kind of “pseudo-cron” generated via website-traffic, or if wordpress use real-cron-jobs.

---

<div class="post-metadata">

**Author:** ![Gomez\_Adams](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/gomez_adams/32/3221_2.png) [@Gomez\_Adams](https://forum.virtualmin.com/u/Gomez_Adams)\
**Post date:** [January 7, 2022, 2:05pm UTC](https://forum.virtualmin.com/t/cron-and-wordpress-action-scheduler/113528/3 "2022-01-07T14:05:33Z")

</div>

Is your Virtualmin version actually 6.17 or 6.17-3?

If it’s 6.17 you really should update it.

---

<div class="post-metadata">

**Author:** ![sean.latitude](https://cdn.forum.virtualmin.com/letter_avatar_proxy/v4/letter/s/7ba0ec/32.png) [@sean.latitude](https://forum.virtualmin.com/u/sean.latitude)\
**Post date:** [January 7, 2022, 2:32pm UTC](https://forum.virtualmin.com/t/cron-and-wordpress-action-scheduler/113528/4 "2022-01-07T14:32:30Z")

</div>

Thanks Gomez, yum update tells me it is all up to date but I see other results when I google suggesting users have had to manually try to update? virtualmin info responds with virtualmin version: 6.17.gpl so I assume its not up to date?

---

<div class="post-metadata">

**Author:** ![Gomez\_Adams](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/gomez_adams/32/3221_2.png) [@Gomez\_Adams](https://forum.virtualmin.com/u/Gomez_Adams)\
**Post date:** [January 7, 2022, 6:02pm UTC](https://forum.virtualmin.com/t/cron-and-wordpress-action-scheduler/113528/5 "2022-01-07T18:02:51Z")

</div>

I think there were several issues with some older OS’s not seeing the available updates. I’m not sure if OS7.9 was one of them.

Maybe @Joe can help out with this.

---

<div class="post-metadata">

**Author:** ![Joe](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/joe/32/9_2.png) [@Joe](https://forum.virtualmin.com/u/Joe)\
**Post date:** [January 7, 2022, 10:09pm UTC](https://forum.virtualmin.com/t/cron-and-wordpress-action-scheduler/113528/6 "2022-01-07T22:09:45Z")

</div>

The package version is authoritative, not the displayed version (I know this is annoying, it doesn’t happen often that we have the extra field and our build process doesn’t update the displayed version).

Check the version of the wbm-virtual-server or webmin-virtual-server package to confirm whether you have the -3 release.

---

<div class="post-metadata">

**Author:** ![Joe](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/joe/32/9_2.png) [@Joe](https://forum.virtualmin.com/u/Joe)\
**Post date:** [January 7, 2022, 10:10pm UTC](https://forum.virtualmin.com/t/cron-and-wordpress-action-scheduler/113528/7 "2022-01-07T22:10:47Z")

</div>

> [@Gomez\_Adams](#):
>
> I think there were several issues with some older OS’s not seeing the available updates.

Some people have broken their own updates by removing/disabling Virtualmin repos. That’s not our issue. 😉

---

<div class="post-metadata">

**Author:** ![sean.latitude](https://cdn.forum.virtualmin.com/letter_avatar_proxy/v4/letter/s/7ba0ec/32.png) [@sean.latitude](https://forum.virtualmin.com/u/sean.latitude)\
**Post date:** [February 3, 2022, 8:30am UTC](https://forum.virtualmin.com/t/cron-and-wordpress-action-scheduler/113528/8 "2022-02-03T08:30:37Z")

</div>

Seems I finally resolved this. Bind DNS was stopped on both servers - strange this happened on both existing and new server. In any case it seems the wordpress plugins are relying on local dns resolution related to the SSL letsencrypt certificate somehow. Started BIND DNS and all my problems went away!

---

<div class="post-metadata">

**Author:** ![system](https://cdn.forum.virtualmin.com/uploads/default/original/2X/c/cd96d761e326db4b2bef94886a639109bd7a8e76.svg) [@system](https://forum.virtualmin.com/u/system)\
**Post date:** [March 21, 2022, 5:14am UTC](https://forum.virtualmin.com/t/cron-and-wordpress-action-scheduler/113528/9 "2022-03-21T05:14:10Z")

</div>

Closed on March 21, 2022, 5:14am UTC

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.
