first step of the shallow sysadmin: turn on the logs! have you already ? if yes, post them here, if not, enable them (optionally tuning logging.config) and run the scheduler with -D 0 to enable logging at DEBUG level.
Il giorno martedì 23 luglio 2013 15:44:06 UTC+2, Tyrone ha scritto: > > I am using the scheduler to run our email queue on our website. We have > two duplicate sites in different countries on different servers. The one > uses a newer /init/ service management and the other uses an older > /etc/init.d/ setup. Otherwise the code is the same. (I can't remember the > exact terms for the different setups, I just remember the folders, but say > if I must clarify) > > After a boot, both work without issues, however at some point, after a day > or two, the scheduler on the /etc/init.d/ service stops. I have been trying > all sorts of different things but without any success. These are the > relavant points: > > 1 - When the scheduler stops, no errors are recorded or occur > 2 - On the worker, the heartbeat is still going and it is still listed as > ACTIVE, but tasks aren't running > 3 - recreating the tasks does not resolve the problem > 4 - restarting the service does not resolve the problem > 5 - deleting the worker and restarting the service resolves the problem > > Why is the worker still going but the tasks stop happening? Is there any > way I can debug this? The other server has no problems at all. > -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
