Forums

Resolved
0 votes
I'm using ClearOS 5.2 as an Internet gateway for my network, and also using DansGuardian. Everything was working fine, until it stopped working. :)

The hardware I was using was too slow for the load, so I built a new box and (looking at some suggestions here) pulled the hard drive from the old server and put it into the new one as a way of preserving my configuration. Everything started fine, just had to reassign the NICs. Except that now the proxy server won't start. And without that, DansGuardian won't run.

I've shutdown and restarted several times. It's set to start automatically on a reboot, but no luck. Clicking start doesn't start the service. Tried clearing the proxy cache, changing the settings, etc. No go.

I can access the internet fine with the proxy server off and transparent mode off, but long-term I want the content filter running.

I checked the logs from the ClearOS GUI, but don't find any references to some kind of error that is preventing the service from starting up. I might try restoring the settings from my backup, but that seems unlikely to work since the gateway is basically working properly, except for this one thing.

Any ideas would be appreciated.

Charlie
Saturday, July 02 2011, 02:42 AM
Share this post:
Responses (4)
  • Accepted Answer

    Wednesday, November 20 2019, 03:44 PM - #Permalink
    Resolved
    0 votes
    Bumping an 8 year old thread is not a good idea. It certainly would not have been running ClearOS 7 pan probably not 6.

    Have you looked in the squid and dansguardian logs? one common error is specifying a domain and a sub-domain of the same domain in the "Authentication Exception Sites". If you have a domain as an exception, it includes all sub-domains but default and squid can refuse to start.
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, November 20 2019, 01:43 PM - #Permalink
    Resolved
    0 votes
    I have the Same issue.
    I am trying to restart the service in both GUI & Command list its won't.


    Thank You
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, July 02 2011, 05:26 AM - #Permalink
    Resolved
    0 votes
    You, sir, win the cigar.

    Squid.out was reporting a "bungled squid.conf line..." which turned out to be the remnants of an ACL rule that I had only partially deleted. Deleted the thing entirely and web proxy started right up.

    I greatly appreciate your help.
    Like
    1
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, July 02 2011, 04:46 AM - #Permalink
    Resolved
    0 votes
    Did you check the contents of "/var/log/squid/squid.out" for clues?
    Like
    1
    The reply is currently minimized Show
Your Reply