CRON configuration

johnny

yeah there is little hacks to make things work but its not a supported thing. Your welcome to try some of them but we highly do not recommend it, plus if we run the cron that quickly it can possibly cause adverse affects with possibly duplicate emails being processed etc

Bigbug

do you know of anything you'd recommend?

johnny

we just have it set to every min for cron ticket parser, so I prefer that

Bigbug

But if I want it should run on seconds?

johnny

Im not really sure. I don't recommend it.

johnny

Maybe in the future we'll tweak it into system daemon so it can run in realtime

Bigbug

johnny Maybe in the future we'll tweak it into system daemon so it can run in realtime

That would be GREAT!

chris_ha

In my recent ITFlow installation (completed using the recommended script), I can view all the cron tasks via the terminal command sudo crontab -l, and I can observe them seemingly running every minute by using sudo tail -f /var/log/syslog | grep CRON.

However, I've encountered an issue where the cron tasks do not appear to be executing as expected. Specifically, I've configured everything for email ticketing, but no emails are being sent. When I check the email queue, I can see the emails listed with a status of "Queued."

I'm wondering if there might be something I've overlooked in my setup or if this issue could potentially be related to a bug?

johnny

check for itflow_XXX.lock files in /tmp and delete them

We recently introduced lock files so the cron scripts would not overrun each other and cause possible dupe emails and such.

We plan on adding a delete lock files to the main cron.php script and in the maintenance section give the option to remove the locks.

rm /tmp/itflow*.local

chris_ha

^ Fixed. Thanks!

« Previous Page