Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 1 subscriber
  • Views 1498 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

7.011 Squid error

Snova
Anybody else hardly able to surf the web with 7.011? Since the update I´m getting lots of these in the Content Filter Log:

web request could not be delivered due to an error" action="block" reason="error" server_error="ERR_READ_ERROR 104" action="block" reason="squiderror"


This thread was automatically locked due to age.
Parents
  • 0
    I had the same problem.  But in my case the CPU was pegged at 100% and the log partition had filled up.  I had to login to the box and delete the squid log file.  After I rebooted it all is well.
  • 0 in reply to jimd
    Hi!

    I removed the use-provider-dns-tick to use manually entered nameservers. That didn't help.  So I removed all of my DNS-servers, that did help.

    Funny enough that all those problems occured after installing 7.011 and all of my manually entered DNS servers resolved names to wrong IPs. Nevertheless, using root servers now...
Reply
  • 0 in reply to jimd
    Hi!

    I removed the use-provider-dns-tick to use manually entered nameservers. That didn't help.  So I removed all of my DNS-servers, that did help.

    Funny enough that all those problems occured after installing 7.011 and all of my manually entered DNS servers resolved names to wrong IPs. Nevertheless, using root servers now...
Children
  • 0 in reply to Snova
    Hi there, 

    this was just a timely coincidence. About a day later after the update has released, the german providier had this DNS issue. We received 10-20 reports from customers all with the same issues, all pointing to the not working dns servers.

    I haven't checked, but i think by now the issue should be resolved.

    regards
    Gert