From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Problem with squid 5.7 and '/usr/bin/asnbl-helper.py' - exception => traceback => helper exits
Date: Fri, 30 Dec 2022 12:22:02 +0100 [thread overview]
Message-ID: <61ab5362-81fe-0c07-068e-449a18e7bc80@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2372 bytes --]
Hi,
sorry, but...
With Core 171 I ran 'squid 5.7' with the options "Deny access to
destinations hosted on fast flux setup" and "Deny access to destinations
hosted on selectively announced networks" both ticked (activated). No
problems.
With Core 172, I found that the 'squid-asnbl-helper.py'-script is having
problems with specific urls - it logs a 'traceback' and the helper exits.
Below is an excerpt from '/var/log/squid/cache.log':
***SNIP***
2022/12/30 11:56:01 kid1| helperOpenServers: Starting 1/10
'asnbl-helper.py' processes
current master transaction: master64
Dec 30 11:56:01 squid-asnbl-helper[776] WARN: No ASNBL configured. This
is acceptable as long as this script is configured to do anything, you
just have been warned...
Dec 30 11:56:01 squid-asnbl-helper[776] INFO: ASN database operational -
excellent. Waiting for input...
Dec 30 11:56:01 squid-asnbl-helper[778] WARN: No ASNBL configured. This
is acceptable as long as this script is configured to do anything, you
just have been warned...
Dec 30 11:56:01 squid-asnbl-helper[778] INFO: ASN database operational -
excellent. Waiting for input...
Traceback (most recent call last):
File "/usr/bin/asnbl-helper.py", line 488, in <module>
resolvedasn = resolve_asn(singleip, ASNDB)
File "/usr/bin/asnbl-helper.py", line 184, in resolve_asn
result = asndb.lookup(str(ipaddr))
BlockingIOError: [Errno 11] Resource temporarily unavailable
Traceback (most recent call last):
File "/usr/bin/asnbl-helper.py", line 488, in <module>
resolvedasn = resolve_asn(singleip, ASNDB)
File "/usr/bin/asnbl-helper.py", line 184, in resolve_asn
result = asndb.lookup(str(ipaddr))
BlockingIOError: [Errno 11] Resource temporarily unavailable
2022/12/30 11:56:01 kid1| WARNING: external_acl_type #Hlpr5 exited
current master transaction: master63
2022/12/30 11:56:01 kid1| Too few external_acl_type processes are
running (need 1/10)
current master transaction: master63
2022/12/30 11:56:01 kid1| Starting new helpers
current master transaction: master63
2022/12/30 11:56:01 kid1| helperOpenServers: Starting 1/10
'asnbl-helper.py' processes
current master transaction: master63
2022/12/30 11:56:01 kid1| WARNING: external_acl_type #Hlpr7 exited
current master transaction: master67
***SNAP***
Can anyone confirm? And if yes - should I open a bug report?
Best,
Matthias
next reply other threads:[~2022-12-30 11:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 11:22 Matthias Fischer [this message]
2022-12-30 11:24 Matthias Fischer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=61ab5362-81fe-0c07-068e-449a18e7bc80@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox