cron job wont stop
-
What are you trying to do there? You appear to have it set to run every minute in hour 12. And it looks to be doing that.
You probably want minute 1 of hour 12 like:
1 12 * * * root /usr/local/bin/php -q /root/pkg_check.php
-
@stephenw10 Ok i see the error.
Curious why the other firewall isn't firing off every minute as well. There are packages that need upgrading.
But good catch everyone. Thanks for pointing out the error to me.
-
@jrey said in cron job wont stop:
o run 1 time so pick a minute in the
Thats exactly the problem. Thanks @jrey
-
@michmoor said in cron job wont stop:
Curious why the other firewall isn't firing off every minute as well
It likely is - as the cron settings are the same (so it runs fine, might be an illusion)
Not sure what the script is actually doing, since I don't use it - you want to share the link to it - I'll peek
but it could simply be a case that the 6100 has enough horse power to complete the task in under a minute and the 1100 does not. Lot's of factors and possibilies to consider -- when the jobs on the 1100 start colliding more bad things likely happen thus the "spam"
does the script actually log that it has run somewhere ?
-
The conversation is here. https://forum.netgate.com/topic/137707/auto-update-check-checks-for-updates-to-base-system-packages-and-sends-email-alerts/70
The script is here
https://gist.github.com/luckman212/5e69ecf04e000ace47eb8f760b71e160
-
Yeah I actually just found it
Auto update check, checks for updates to base system + packages and sends email alerts:
look at the sample cron the author has there in the first post
1 18 * * * blah
Minute 1 of the 18th hour ..
Pick a minute and hour of you choice, run it once not 60 times in the hour, you'll be fine ... servers everywhere will be fine ... spam will stop all will be well.
On that post @stephenw10 said in Auto update check, checks for updates to base system + packages and sends email alerts:
Needs more blinkenlight action!
I don't think he meant once a minute for an hour....
-
@jrey lol
-
Blinkenlights. Always.
-
@jrey said in cron job wont stop:
does the script actually log that it has run somewhere ?
If there was a cron log on pfsense, you would see that your 6100 also ran this script every minute.
But on 6100 everything is up to date, so according to the script :No log lines
No message line on the command interface - which is non interactive, so discarded.
No message (mail in my case)so the system log doesn't show anything if up to date.
-
Good point - I never actually looked at the script referenced only the post that it was provided on. but yes that is why it doesn't show as running on his 6100. It is.
Fixing the cron timing so that it does not "Blinkenlights" so many times - should make everything happy on both systems. Only need 1 Blinkenlight in the hour.