cannot connect to parent proxy error at startup

hi guys!

what should run first? Squid or Dansguardian? correct if im wrong, i think the problem is with the sequence of who should run first. if i am correct how could i make the squid run first before the dansguardian?

any suggestions or comments

tnx

squid is a high performance proxy caching server for web clients. squids handles all requests in a non blocking process and maintains i/o buffers. so having a filter is a preferreable or (i'll say essential).

dansguardian does security like a filtering and passes the data for the squid
and squid does the fetching (cacheing proxy).

yes, its better for the dans-guard to be outside of squid, as it saves the memory by only fetching the required data and result in better performance and secure.


First you need to make your Squid configuration. The Squid configuration can be found in

/usr/local/squid/etc/squid.conf

go for QUICKSTART guide and try this The sample squid.conf file contains comments explaining each option.

thank you cisman,

i can run both squid and dansguardian, the problem is during start up, the dansguardian always failed. but after the initiallization or after the startup routine completed and i run the command /sbin/service dansguardian start, there is no problem at all. i checked the /var/log/messages log, there is an error that says "dansguardian: Error connecting to parent proxy". that's why i suspecting that the parent proxy here is the squid. but since the squid has not started yet, the connecting to parent proxy error occurs. AM I RIGHT WITH MY OBSERVATION? is this with the INIT?

is there anybody to correct me?

Yes monsky, you are getting the problem because DansGuardian is starting up before Squid. It is not a stand-alone proxy but a web content filtering application.

You will need to find the startup script that calls Squid and DansGuardian. The you will need to ensure that Squid is called before DansGuardian. The location of the script will vary depending on your distro. My startup scripts are in /etc/rc.d/. If you're not sure, go to the startup directory and type in "grep -i 'squid' *"

yes, you are right monsky and also the da light like always
if you have squid-2, the system restart is buitin. so you need to run the path name to the squid executables.

for that you have to run ex:
/usr/local/squid/sbin/squid


To make DansGuardian start up when the server reboots. For linux this means use your favourite SysV editor to stick DansGuardian in run level 5 and 3 at about 92, if chkconfig/rpm has not already done this for you.

Also you need to rotate the logs once a week. As root, crontab -e and set the log rotation script up as follows:
59 23 * * sun /etc/dansguardian/logrotation
I.e 23:59 every sunday. Or as pleases you. Note, the path may be different. You don't have to use my splendid script and could use any method you want so long as it stops DansGuardian first, rotates then starts it again.

if that doesnt work then you should look at these
>squid startup
>the dans-guard not configured properly to the squid(or not able to catch the squid)
The port it listens on by default is 8080. It uses port 3128 on Squid.


hope its helpful for you
cisman

thank you Dalight and Cisman, im now doing what you had suggested. ill keep you posted.

cheers