Cron Job Once/Day
-
Not worth discussing further,
the maintainers recommendation is pretty obvious, when it says "Default: Every hour" in bold letters even.
You seem unwilling to try the change and report back the observation, simply because "it has always worked"
You seem unwilling "to install another package just to see." (not even something I'm recommending)
No it is not "difficult to tell if it's actually running" but again you are at a road block of "it has always worked"Again if you are unwilling to try the suggestions just because "I have had it configured that way for years without issue." then it will be very difficult for people who are just trying to help you..
I'm not the one experiencing the issue, you are.
Good luck -
@jrey said in Cron Job Once/Day:
the maintainers recommendation is pretty obvious, when it says "Default: Every hour" in bold letters even.
Can you share a link to that? I will comply upon seeing...in the meanwhile I look through the doc.
-
you have already shared it with us in your screen capture with the big red arrow, pointing at your current setting.
"Default: Every Hour" by implication the provided default is the recommendation. The developer didn't just picked it out of the sky. (you are certainly welcome to change it, as you have) but that doesn't imply what you are setting it too isn't broken for some yet unknown reason.
As I stated I use 2 hours so I don't use the "default" recommended value either.
have you looked in the log file? I don't see anything to suggest you have. The cron starts should be recorded in there.
As mentioned I have my cron set to start on the 30 minute mark rather than the top of the hour, and the frequency of each list set per my screen shot above. The lowest interval being 2 hours. this means that based on my schedule it would check for something to do at 00:30, 2:30...6:30, 8:30, 10:30 .. etc
so I temporarily changed it to 1 hour and by doing so 9:30 then becomes possible time things could run (if their frequency says so). I have nothing on my system that says so. However it took no time to tell me it had nothing to do at 9:30 in the log file.
CRON PROCESS START [ v3.2.0_6 ] [ 10/30/23 09:30:00 ] No Updates required. CRON PROCESS ENDED UPDATE PROCESS ENDEDagain what frequency do you have set on your individual lists ?
It's not a case of you being forced to "comply", just basic troubleshooting.
Again, you are firm on "Once a day" it's always worked. You have a suggestion to try something, you don't answer the questions, please propose then how we can help? -
@jrey So, after your last response, I went checking the doc on Netgate and could not find anything specific to cron job yet, then went back to look at the interface without making any changes and now it's say as below despite it should be about 23h and a few minutes...
-
@NollipfSense said in Cron Job Once/Day:
then went back to look at the interface without making any changes and now it's say as below despite it should be about 23h and a few minutes
and that implies that
a) it is not running now,
b) that it is going to run again at midnight, and that is 14:49:54 away from that time. Is that correct based on your timezone? are your 14:49 away from midnight (00:00)why are you thinking 23h be the correct display here?
will run at 00:00 with 14:49:54 time remaining
your system clock isn't fluctuating wildly is it ?
-
-
@jrey said in Cron Job Once/Day:
why are you thinking 23h be the correct display here?
will run at 00:00 with 14:49:54 time remaining
Okay, I messed up on the 23hr...thinking it's from the time I rebooted; so, now the crob job is showing the correct time to the next run, since it's 9:40am approximately. Thank you for pointing that out.
-
So looks like the problem is resolved and "time" will tell at this point.
Let us know tomorrow if the run is successful overnight and the time remaining until next run when you view in the morning appears correct.
(did you happen save or re-save any of the configuration screens along the way?)
-
@jrey said in Cron Job Once/Day:
So looks like the problem is resolved and "time" will tell at this point.
Let us know tomorrow if the run is successful overnight and the time remaining until next run when you view in the morning appears correct.
(did you happen save or re-save any of the configuration screens along the way?)
No change other than reboot and yes will follow up as you're correct that only time will tell.
-
Well, this morning Cron job was stuck again and it seems that it occurs when list constantly fail to download , such as [ DNSBL_Malicious - MDL ] Download Fail [ 09/3/23 00:00:32 ]. It had failed every day and was removed this morning. Also removed/disabled was the shellalist...I had advertising and tracking only and those failed.
[ DNSBL_Shallalist - Shallalist_adv ] Download Fail [ 10/31/23 00:00:33 ]
[ DNSBL_Shallalist - Shallalist_tracker ] Download Fail [ 10/31/23 00:00:33 ]The same was enabled in the UT-list. I'll continue to monitor
-
-
@jrey said in Cron Job Once/Day:
I'm not really surprised by that.
That's because the bug is still present...see here: https://forum.netgate.com/topic/178357/active-pfblockerng-cron-job-never-ends/4
-
@BBcan177 It appears that the cron job bug or a bug that causes cron job to constantly run which was supposedly fixed in v3.2.0_3 is still present in v3.2.0_6. Yes, I have wildcard blocking TLD enabled; however, that's one of the main features to run pfBlockerNG. Is there another work around other than disabling that feature? My feeds and cron job are set to update/run once per day.
-
Not really where I was going with my comment, but ok
@NollipfSense said in Cron Job Once/Day:
That's because the bug is still present.
You must realize, of course, this is new information to your problem description, as it is the first time you have mentioned that
@NollipfSense said in Cron Job Once/Day:
I have wildcard blocking TLD enabled
Good to know.
are you seeing the TLD processing mentioned in the log file ?
"Assembling DNSBL database...... completed [ 05/22/23 22:47:03 ]
TLD:
TLD analysis..xx completed [ 05/22/23 22:47:21 ]are you
Unbound mode or;
Unbound python mode
?Edit: on the dashboard widget does it show the DNSBL_* -- what is the value in the Count column ?
-
@jrey said in Cron Job Once/Day:
this is new information to your problem description,
That's because I discovered it doing a search of the problem I am facing...the same exact issue, cron job constantly running...
@jrey said in Cron Job Once/Day:
are you seeing the TLD processing
It's working remember I had added snapshots.netgate.com and was able to download v2.8dev.
@jrey said in Cron Job Once/Day:
Unbound python mode
yes
@jrey said in Cron Job Once/Day:
on the dashboard widget does it show the DNSBL
pfBlockerNG is functioning normally except for the cron job...just notice the yellow dot with ! when it should be green...
-
@NollipfSense said in Cron Job Once/Day:
are you seeing the TLD processing
sorry, I meant can you show the log file output (part) that shows TLD being processed. I don't see an image of that.
is there an error in the error.log ?
-
@jrey said in Cron Job Once/Day:
@NollipfSense said in Cron Job Once/Day:
are you seeing the TLD processing
sorry, I meant can you show the log file output (part) that shows TLD being processed. I don't see an image of that.
is there an error in the error.log ?
That's why I had said that pfBlockerNG is functioning normally except for the cron job...I feel we are moving away from the cron job issue that's continuously running...Here is a small capture of DNSBL log and error log...note there is an error earlier when I rebooted then update...but I could not reload because cron job had already started it continuous run. Not sure what couldn't open ports...
DNSBL-python,Nov 2 13:11:30,incoming-telemetry.thunderbird.net,192.168.1.100,Python,DNSBL_A,DNSBL_ADs,incoming-telemetry.thunderbird.net,Yoyo,+
DNSBL-python,Nov 2 13:15:00,incoming-telemetry.thunderbird.net,192.168.1.100,Python,DNSBL_A,DNSBL_ADs,incoming-telemetry.thunderbird.net,Yoyo,-
DNSBL-python,Nov 2 13:16:30,incoming-telemetry.thunderbird.net,192.168.1.100,Python,DNSBL_A,DNSBL_ADs,incoming-telemetry.thunderbird.net,Yoyo,-
DNSBL-python,Nov 2 13:20:30,incoming-telemetry.thunderbird.net,192.168.1.100,Python,DNSBL_A,DNSBL_ADs,incoming-telemetry.thunderbird.net,Yoyo,-
DNSBL-python,Nov 2 13:22:00,incoming-telemetry.thunderbird.net,192.168.1.100,Python,DNSBL_A,DNSBL_ADs,incoming-telemetry.thunderbird.net,Yoyo,-
DNSBL-python,Nov 2 15:43:58,metrics.icloud.com,192.168.1.100,HSTS,DNSBL_HTTPS,DNSBL_EasyList,metrics.icloud.com,EasyPrivacy,+
DNSBL-python,Nov 2 16:57:36,metrics.icloud.com,192.168.1.100,HSTS,DNSBL_HTTPS,DNSBL_EasyList,metrics.icloud.com,EasyPrivacy,-
DNSBL-python,Nov 2 18:11:19,metrics.icloud.com,192.168.1.100,HSTS,DNSBL_HTTPS,DNSBL_EasyList,metrics.icloud.com,EasyPrivacy,-[ DNSBL_Shallalist - Shallalist_adv ] Download Fail [ 10/31/23 00:00:33 ]
Local File Failure [ 10/31/23 00:00:33 ]
[ DNSBL_Shallalist - Shallalist_tracker ] Download Fail [ 10/31/23 00:00:33 ]
Local File Failure [ 10/31/23 00:00:33 ]
DNSBL disabled - Unbound conf update FAIL *** Fix error(s) and a Force Reload required! *** [ 11/2/23 14:06:19 ][1698951979] unbound[73183:0] error: bind: address already in use [1698951979] unbound[73183:0] fatal error: could not open ports
[ 11/2/23 14:06:19 ]
DNSBL enabled FAIL *** Fix error(s) and a Force Reload required! *** [ 11/2/23 14:07:55 ][1698952075] unbound[80987:0] error: bind: address already in use [1698952075] unbound[80987:0] fatal error: could not open ports
[ 11/2/23 14:07:55 ]
-
Found this thread and will read in the morning: https://forum.netgate.com/topic/176362/pfblockerng-devel-v3-1-0_7-update-unbound-issue
-
Interesting post just a few minutes ago. ( I'll ask obvious the question there )
https://forum.netgate.com/topic/183821/shallalist-failed-to-open-stream-no-such-file-or-directory
-
J jrey referenced this topic on
-
@jrey said in Cron Job Once/Day:
Interesting post just a few minutes ago. ( I'll ask obvious the question there )
https://forum.netgate.com/topic/183821/shallalist-failed-to-open-stream-no-such-file-or-directory
Yes, I just responded...in my case, it seems that an issue with Unbound python mode...right now, cron job has been running since the last update at midnight...no sure what to do, maybe enable every hour despite running for nothing. Hope BBcan177 will respond for clarification...
