Forums

Subscribe via email Subscribe via email
Subscribe via rss
Guest
or Ask a Question
Add a reply View Replies (8) →
achu
achu
Offline

dansguardian: Error connecting to proxy

Resolved
0 votes
I have clearos enterprise 5.2 in non-transparent mode and configured content filter.But it always shows the error
Oct 13 13:59:49 dansguardian[7988]: Error connecting to proxy...
Oct 13 13:59:52 dansguardian[13499]: Error connecting to proxy...
Oct 13 13:59:52 dansguardian[8920]: Error connecting to proxy...
Oct 13 13:59:52 dansguardian[7743]: Error connecting to proxy...
Oct 13 13:59:54 dansguardian[10086]: Error connecting to proxy...
Oct 13 13:59:55 dansguardian[4777]: Error connecting to proxy...
Oct 13 13:59:57 dansguardian[26988]: Error connecting to proxy...
Oct 13 13:59:57 dansguardian[26990]: Error connecting to proxy...
Oct 13 13:59:57 dansguardian[26989]: Error connecting to proxy...
Oct 13 13:59:57 dansguardian[26991]: Error connecting to proxy...
Oct 13 13:59:57 dansguardian[26223]: Error connecting to proxy...
Oct 13 13:59:57 dansguardian[26224]: Error connecting to proxy...
Oct 13 13:59:57 dansguardian[28279]: Error connecting to proxy...
Oct 13 13:59:57 dansguardian[20924]: Error connecting to proxy...
Oct 13 13:59:57 dansguardian[26225]: Error connecting to proxy...
Oct 13 13:59:57 dansguardian[26227]: Error connecting to proxy...
Oct 13 13:59:57 dansguardian[26844]: Error connecting to proxy...
Oct 13 13:59:57 dansguardian[26849]: Error connecting to proxy...

why its happening?
In Proxy and Content Filtering
Thursday, October 14 2010, 06:42 AM
Subscribe via email
Share this post:
Responses (8)

  • Accepted Answer

    Dirk Albring
    Dirk Albring
    Offline
    Thursday, October 14 2010, 03:51 PM - #Permalink
    Resolved
    1 votes
    Verify in /etc/dansguardian-av/dansguardian.conf that your proxy port is set to 3128 and and you content filter port is set to 8080. It should look something like this:

    # the port that DansGuardian listens to.
    
filterport = 8080
    

    
# the ip of the proxy (default is the loopback - i.e. this server)
    
proxyip = 127.0.0.1
    

    
# the port DansGuardian connects to proxy on
    
proxyport = 3128
    The reply is currently minimized Show

  • Accepted Answer

    achu
    achu
    Offline
    Friday, October 15 2010, 07:15 AM - #Permalink
    Resolved
    0 votes
    Verified in /etc/dansguardian-av/dansguardian.conf.No changes same as the Code.
    Any changes require?
    This error occures after ClamAV updates .Please seee the logs

    "freshclam[3012]: ClamAV update process started at Fri Oct 15 12:10:56 2010
    freshclam[3012]: DON'T PANIC! Read http://www.clamav.net/support/faq
    freshclam[3012]: daily.cld is up to date (version: 12138, sigs: 139868, f-level: 53, builder: guitar)
    freshclam[3012]: bytecode.cld is up to date (version: 80, sigs: 10, f-level: 53, builder: edwin)
    freshclam[3012]: --------------------------------------
    dansguardian[25543]: Error connecting to proxy
    clamd[19885]: SelfCheck: Database status OK.
    dansguardian[4718]: Error connecting to proxy
    dansguardian[4715]: Error connecting to proxy
    dansguardian[12561]: Error connecting to prox'


    Any error related to ClamAV?
    The reply is currently minimized Show

  • Accepted Answer

    Dirk Albring
    Dirk Albring
    Offline
    Saturday, October 16 2010, 01:46 AM - #Permalink
    Resolved
    0 votes
    Is the content filter not working or is it just throwing these errors?
    The reply is currently minimized Show

  • Accepted Answer

    achu
    achu
    Offline
    Tuesday, October 19 2010, 04:42 AM - #Permalink
    Resolved
    0 votes
    Content filter is working .But always shows that error.
    The reply is currently minimized Show

  • Accepted Answer

    Jay M
    Jay M
    Offline
    Thursday, July 28 2011, 07:47 AM - #Permalink
    Resolved
    0 votes
    I received complaint from the user that they can't access some websites (the error/ClearOS message on the user screen said Proxy server: DNS failed or something like that).
    I check the log for squid related error but can't find one, but I found several message: dansguardian[XXXX]: Error connecting to proxy
    The other day I do play around with /etc/resolv.conf, and hope gain some performance by adding more DNS servers, but looks like I'm wrong (or the DNS servers that I add are too slow).
    I revert the file and restart squid, and so far everything works normally. No dansguardian[XXXX]: Error connecting to proxy message in the log.
    I hope it help.
    The reply is currently minimized Show

  • Accepted Answer

    Ethan
    Ethan
    Offline
    Friday, October 19 2012, 05:53 AM - #Permalink
    Resolved
    0 votes
    Hi Achu,

    Was the issue resolved by restarting the squid service?

    Regards,
    The reply is currently minimized Show

  • Accepted Answer

    Ty Christensen
    Ty Christensen
    Offline
    Monday, November 05 2012, 05:08 PM - #Permalink
    Resolved
    0 votes
    I'm running into the same problem, and restarting squid got rid of the dansg error messages. We'll see if the users still report intermittent browsing problems.
    The reply is currently minimized Show

  • Accepted Answer

    Ty Christensen
    Ty Christensen
    Offline
    Monday, November 05 2012, 07:35 PM - #Permalink
    Resolved
    0 votes
    2 hours later, I have a bunch of the Dansg errors again. Restarting squid is not the fix.
    The reply is currently minimized Show
Your Reply