Cron Job Once/Day
-
@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...
-
@NollipfSense said in Shallalist: Failed to open stream: No such file or directory:
That's why I removed it, but the hanging continues...
but from what you have provided on this post
and looking at the code, it's not cron that is the issue.Cron is only reacting to not seeing the requested job finish as expected, so it appears to be waiting (and it likely is).
you might simply have a bad file in one of the directories
when cron runs the job it tries to do "normal" things with it.
it fails (or does it really) but the result is garbage in the file that is going to be used by unbound, as it in part or perhaps even all of it gets parsed into the unbound list.
then pfB code gets into a loop trying to start/stop unbound (and it can't) but it keeps trying or never gets an expected response.Don't really have all the details about what your various settings were and / or are now, just suggesting, you might need to clean up left over "stuff" manually to get it going again.
I can't say for certain with shallalist, and obviously can't even test anymore, but can with 100% certainty, demonstrate similar bad things with an ASN feed goes bad
If I had to venture a further guess, I'd suspect you are getting an "unbound" issue cause cron to say "i'm running"
are you seeing unbound start and stop rapidly ?
more than one copy running?what kind of messaging are you seeing in the DNS Resolver log for unbound.
so again just suggesting, you might need to clean up left over "stuff" manually to get it going again.
-
@jrey said in Cron Job Once/Day:
Cron is only reacting to not seeing the requested job finish as expected,
I had rebooted after that and it has not presented anything else.
@jrey said in Cron Job Once/Day:
what kind of messaging are you seeing in the DNS Resolver log for unbound.
Nothing unusual...
Nov 2 19:10:57 unbound 99157 [99157:0] notice: init module 0: python
Nov 2 19:10:57 unbound 99157 [99157:0] info: [pfBlockerNG]: pfb_unbound.py script loaded
Nov 2 19:10:57 unbound 99157 [99157:0] info: [pfBlockerNG]: init_standard script loaded
Nov 2 19:10:57 unbound 99157 [99157:0] notice: init module 1: validator
Nov 2 19:10:57 unbound 99157 [99157:0] notice: init module 2: iterator
Nov 2 19:10:57 unbound 99157 [99157:0] info: start of service (unbound 1.17.1).
Nov 2 19:14:21 unbound 91640 [91640:0] notice: init module 0: python
Nov 2 19:14:21 unbound 91640 [91640:0] info: [pfBlockerNG]: pfb_unbound.py script loaded
Nov 2 19:14:22 unbound 91640 [91640:0] info: [pfBlockerNG]: init_standard script loaded
Nov 2 19:14:22 unbound 91640 [91640:0] notice: init module 1: validator
Nov 2 19:14:22 unbound 91640 [91640:0] notice: init module 2: iterator
Nov 2 19:14:22 unbound 91640 [91640:0] info: start of service (unbound 1.17.1).
Nov 2 19:14:30 unbound 91640 [91640:6] info: generate keytag query _ta-4f66. NULL IN
Nov 3 00:00:58 unbound 93173 [93173:0] notice: init module 0: python
Nov 3 00:00:58 unbound 93173 [93173:0] info: [pfBlockerNG]: pfb_unbound.py script loaded
Nov 3 00:00:58 unbound 93173 [93173:0] info: [pfBlockerNG]: init_standard script loaded
Nov 3 00:00:58 unbound 93173 [93173:0] notice: init module 1: validator
Nov 3 00:00:58 unbound 93173 [93173:0] notice: init module 2: iterator
Nov 3 00:00:58 unbound 93173 [93173:0] info: start of service (unbound 1.17.1).
Nov 3 00:01:04 unbound 93173 [93173:2] info: generate keytag query _ta-4f66. NULL IN -
Looks like v23.09RC may have fixed the issue and DNSBL now has the green check mark...will continue to monitor...
-
So, under v23.09RC which has the same exact version of pfBlockerNG, Cron job is behaving as configured. That begs the question was the Shellalist causing the Cron job to stuck in constant running mode trying to update the list? It seems so since I completely removed it.
-
@NollipfSense said in Cron Job Once/Day:
was the Shellalist causing the Cron job to stuck in constant running mode
There you go.
@jrey said in Cron Job Once/Day:
when cron runs the job it tries to do "normal" things with it.
it fails (or does it really) but the result is garbage in the file that is going to be used by unbound, as it in part or perhaps even all of it gets parsed into the unbound list.
then pfB code gets into a loop trying to start/stop unbound (and it can't) but it keeps trying or never gets an expected response.It would have been nice to learn a little more about the specific failure point, however
@jrey said in Cron Job Once/Day:
just suggesting, you might need to clean up left over "stuff" manually to get it going again.
Installing the 23.09RC likely also contributed to that clean up..
-
@jrey said in Cron Job Once/Day:
Installing the 23.09RC likely also contributed to that clean up..
Agree...
