[squid-users] Squid 5 service stops after assertion failure
Vieri
rentorbuy at yahoo.com
Sun Jan 24 21:42:24 UTC 2021
Hi,
My Squid web proxy crashed as shown in this log:
2021/01/24 13:18:13 kid1| helperHandleRead: unexpected reply on channel 0 from bllookup #Hlpr21 '43 ERR message=[...]
current master transaction: master65
2021/01/24 13:18:13 kid1| assertion failed: helper.cc:1066: "skip == 0 && eom == NULL"
current master transaction: master65
2021/01/24 13:18:13 kid1| Set Current Directory to /var/cache/squid
2021/01/24 13:18:13 kid1| Starting Squid Cache version 5.0.4-20201125-r5fadc09ee for x86_64-pc-linux-gnu...
2021/01/24 13:18:13 kid1| Service Name: squid
[...]
REPEATS (assertion failure & squid restart)
[...]
2021/01/24 13:18:27 kid1| helperHandleRead: unexpected reply on channel 0 from bllookup #Hlpr21 '2 ERR message=[...]
current master transaction: master76
2021/01/24 13:18:27 kid1| assertion failed: helper.cc:1066: "skip == 0 && eom == NULL"
current master transaction: master76
2021/01/24 13:18:27| Removing PID file (/run/squid.pid)
2021/01/24 13:18:34| Pinger exiting.
2021/01/24 13:18:37| Pinger exiting.
After the assertion failure Squid tries to restart a few times (assertion failures seen again) and finally exits.
A manual restart works, but I don't know for how long.
The external script "bllookup" is probably responsible for bad output, but maybe Squid could handle it without crashing.
Regards,
Vieri
More information about the squid-users
mailing list