Seems, all of the cron tasks are stuck (prbably because reboot on doing some task) on

user.hostname.com/admin/hosting/queues

but they are running on

hostname.com/admin/hosting/queues

crontab -e output:

* * * * * bash /var/xdrago/second.sh >/dev/null 2>&1
* * * * * bash /var/xdrago/minute.sh >/dev/null 2>&1
* * * * * bash /var/xdrago/runner.sh >/dev/null 2>&1
*/5 * * * * bash /var/xdrago/manage_ltd_users.sh >/dev/null 2>&1
10 * * * * bash /var/xdrago/clear.sh >/dev/null 2>&1
10 * * * * bash /var/xdrago/purge_binlogs.sh >/dev/null 2>&1
15 3 * * * bash /var/xdrago/graceful.sh >/dev/null 2>&1
15 4 * * * bash /var/xdrago/mysql_backup.sh >/dev/null 2>&1
15 7 * * * bash /var/xdrago/usage.sh >/dev/null 2>&1
15 8 * * * bash /var/xdrago/fetch-remote.sh >/dev/null 2>&1
###EOF2012###

Wnat to try http://community.aegirproject.org/node/14/revisions/841/view#cron :

$ su -s /bin/bash - aegir
$ cd /path/to/hostmaster/sites/domain
$ drush vdel hosting_queue_cron_running -y

but... what is the path to hostmaster in Barracuda?

Will it help?

Comments

playfulwolf’s picture

playfulwolf commented

ok, as aegir user, crontab -e is:

SHELL=/bin/bash
PATH=/opt/local/bin:/bin
*/1 * * * * /var/aegir/drush/drush.php '@hostmaster' hosting-dispatch

and

drush '@hostmaster' hosting-dispatch -d
has those lines:

too early for queue cron [0.27 sec, 23.42 MB]                                                                                              [notice]
too early for queue tasks [0.27 sec, 23.42 MB]

how to delete that semaphore? in https://github.com/omega8cc/nginx-for-drupal/issues/32 it is written, that I should execute drush vdel hosting_queue_cron_running but at which location?

omega8cc’s picture

omega8cc commented

Semaphore is automatically removed if it is more than one hour old. But make sure if the time is set correctly on your server.

For master instance it is standard location, but you can also switch to aegir and run the command using alias:

$ su -s /bin/bash - aegir
$ drush @hostmaster vdel hosting_queue_cron_running
omega8cc’s picture

omega8cc commented

The "too early" suggest that it is your system time issue probably, not sure. Try to sync it with /usr/sbin/ntpdate pool.ntp.org

playfulwolf’s picture

playfulwolf commented

I am on VPS, and it is not allowed to adjust time:

/usr/sbin/ntpdate pool.ntp.org
14 Apr 18:11:26 ntpdate[38220]: Can't adjust the time of day: Operation not permitted

but the clock is ok. There are no indications, thtat something was modified exept some unlucky WSOD bug, during which I rebooted server with some tasks running.
Job queue on hostname.com aegir instance is ok, it is not just on user.hostname.com, looked for all the databases for any mentioned in other issues semaphores - no luck

playfulwolf’s picture

playfulwolf commented

yep, timezone and time is correct, and haven't been modified.

playfulwolf’s picture

playfulwolf commented

seems I have trouble with this :(
is there a way not to wipe server and fix this? create new instance? how?

playfulwolf’s picture

playfulwolf commented
Status: Active » Closed (fixed)

full upgrade with full rebuilds of Barracuda & Octopus finally helped.