Problems with squid
Hi all. Im building a server that has a DansGuardian filter for my job and need help with the configuration.
I followed the instructions from this site and i've been getting errors when trying to restart squid. These are the errors: Code:
squid2009/08/18 13:04:33| parseConfigFile: squid.conf:2 unrecognized: 'http_accel_host' |
Every one of those error messages seem to be saying 'when you set this parameter, there is something I don't like about it'.
There is little chance that anyone else who can't see the appropriate lines from you squid.conf will succeed in guessing what you have for those lines. You might also have need to explain a few things about your network, but will certainly need to say something about what you have set for those parameters, so just cust and paste the lines for people to look at. |
Ok so as i said before im making a filter for the network to weed out certain sites. The conf file i have is pretty much default with default settings. I dont see the need in pasting the entire conf as im sure the mods here wouldnt like that so i'll paste the changes that i have made.
Code:
http_port 127.0.0.1:3128 P.S. Should i use the machines DHCP assigned IP Address or the default 127.0.0.1 IP? Thanx in advance! |
Quote:
Code:
http_port 127.0.0.1:3128 # Usage: port [options] # hostname:port [options] # 1.2.3.4:port [options] # # The socket addresses where Squid will listen for HTTP client # requests. You may specify multiple socket addresses. # There are three forms: port alone, hostname with port, and # IP address with port. If you specify a hostname or IP # address, Squid binds the socket to that specific # address. This replaces the old 'tcp_incoming_address' # option. Most likely, you do not need to bind to a specific # address, so you can use the port number alone. # # If you are running Squid in accelerator mode, you # probably want to listen on port 80 also, or instead. # # The -I command line option will override the *first* port # specified here. # # You may specify multiple socket addresses on multiple lines. ...etc I've always used the 'real' address of the machine (rather than the loopback address of 127.0.0.1, assuming that using the loopback address might end up with the packets traversing firewalls twice and that this might have an efficiency impact, but, I have ot admit, I'm not really that sure. Code:
cache_effective_user squid # If you start Squid as root, it will change its effective/real # UID/GID to the user specified below. The default is to change # to UID to nobody. If you define cache_effective_user, but not # cache_effective_group, Squid sets the GID to the effective # user's default group ID (taken from the password file) and # supplementary group list from the from groups membership of # cache_effective_user. # #Default: # cache_effective_user squid seems reasonable, given that running services as root is a security problem waiting to happen (its still a potential security problem on a home network, just not one that you necessarily have to take seriously)...you might want to set up the squid account manually so that you know the password so that, if you need to debug, you can run squid manually # TAG: cache_effective_group # If you want Squid to run with a specific GID regardless of # the group memberships of the effective user then set this # to the group (or GID) you want Squid to run as. When set # all other group privileges of the effective user is ignored # and only this GID is effective. If Squid is not started as # root the user starting Squid must be member of the specified # group. # #Default: # none also seems reasonable The others I can't currently comment on as this box only has 2.7 available to it and the config directives have changed between the 2.x series and the 3.x series. (So, you should say what your squid version is, because some of those directives clearly won't work on versions that don't recognise them.) |
Hello,
It looks to me that you're putting tags from squid 2.5 in a 3.x version. All references I have point back to 2.5 when in my current version 3.0STABLE16 they don't appear to be there any more, nor are they in the Squid 3.0 Configuration Manual. As salasi pointed out, please post your version. Kind regards, Eric |
Quote:
Code:
squid_2.7.STABLE3-4.1_i386.deb |
Yes, after thinking about it again, I'm pretty sure that you are trying to use config parameter in a version which isn't configured to take it. At first I felt that given the differences between 2.x and 3.x that's what was going one, but I note that the tutorial that you are using is pretty old, so it may be an early 2.x and a late 2.x.
(Note that there are other possibilities, too; some of the config parameters are optional and if whoever built your version didn't build the particular parameter in, then that would cause it too. Their squid.conf should always comply with their build settings, though.) So, if you do this right, there is no danger of getting into this trouble. You open the squid.conf that was installed with your squid and edit the settings according to the comments. A bit tedious, because squid.conf is quite long, but it works. If yopu are confident that the tutorial gives you good info -and with a 2004 tutorial, I don't see how you can be that confident- using the search function in your text editor will get you straight to the bits that you want to edit. If you search and don't find, that is already telling you something. Note that your install ought to have an unmolested .conf file under somewhere like /usr/share/squid/squid.conf.default; if the install has already done any config for you (say networking addresses), the .default version may not have it. OTOH, if you saved a version before you started editing, that would be even better. |
Alright then. I'll either try to get it working with the default config
(/usr/share/doc/squid/examples/squid.conf) And if it still doesnt work the way that i'm looking for i'll just scrap the entire prog and install from src. |
All times are GMT -5. The time now is 09:45 PM. |