RE: [squid-users] Squid won't restart

From: Linux <linux@dont-contact.us>
Date: Wed, 12 Jun 2002 21:21:32 +1200

Many thanks

I will try this out tomorrow

Mike

-----Original Message-----
From: Rost, Werner [mailto:Werner.Rost@zfboge.com]
Sent: Wednesday, 12 June 2002 21:17
To: 'Linux'; squid-users@squid-cache.org
Subject: AW: [squid-users] Squid won't restart

Hi,

below is a description how to get squid starting. This works fine for me
(SQUID 2.4 Stable 3 running on TRU64 5.1A). Maybe it would be helpful to
insert this procedure in the FAQ.

Logon as root

1. get the name of the "squid user"

   # grep cache_effective_user squid.conf | grep -v "#"
   cache_effective_user squid
   #
   ---> username = squid

2. get the name of the cache directory

   # grep cache_dir squid.conf | grep -v "#"
   cache_dir ufs /data1/squid_cache 5000 32 512
   #
   ---> directory = /data1/squid_cache

3. does the "squid user" exist?

   # grep squid /etc/passwd
   squid:Nologin:200:15:SQUID-User:/usr/users/squid:/bin/sh
   #

   If not: create this user.

4. ensure that squid user may write into the logs directory

   # cd <squd-root-directory>
   cd /usr/local/squid
   chown squid:users logs

5. create the cache directory as squid user

   # logon as squid user
   su - squid
   # create the main directory
   cd /data1
   mkdir squid_cache
   # run squid creating the cache
   # this may take some time - be patient...
   /usr/local/squid/bin/squid -z

6. Now you can start squid.

> Mit freundlichen Grüßen / regards
> Werner Rost
>
> ---------------------------------------------------------------------
> ZF Boge GmbH
> Werner Rost
> IT
> Friesdorfer Str. 175
> D-53175 Bonn
>
>
> phone: +49/228/3825 420
> fax: +49/228/3825 398
> werner.rost@zfboge.com
>
> www.boge-vibrationcontrol.com
> ---------------------------------------------------------------------
>

> -----Ursprüngliche Nachricht-----
> Von: Linux [mailto:linux@dounsix.co.nz]
> Gesendet am: Mittwoch, 12. Juni 2002 10:53
> An: squid-users@squid-cache.org
> Betreff: RE: [squid-users] Squid won't restart
>
> Hi back again
>
> I have set the permissions on /var/spool/squid now so many times it is
> getting worn out
>
> I am out of ideas.. Help???
> Immediately below is the message I get while initialising the
> cache. The
> permissions are set to squid:squid recursively
>
> Initialising the Squid cache with the command squid -f
> /etc/squid/squid.conf
> -z ..
>
>
> 2002/06/12 15:24:41| Creating Swap Directories
> FATAL: Failed to make swap directory /var/spool/squid: (13) Permission
> denied
> Squid Cache (Version 2.4.STABLE3): Terminated abnormally.
>
>
>
> CPU Usage: 0.000 seconds = 0.000 user + 0.000 sys
> Maximum Resident Size: 0 KB
> Page faults with physical i/o: 14
>
>
> -----Original Message-----
> From: Linux [mailto:linux@dounsix.co.nz]
> Sent: Monday, 27 May 2002 22:27
> To: squid-users@squid-cache.org
> Subject: RE: [squid-users] Squid won't restart
>
>
> Many thanks Joe I checked and set the cache directory but I
> have not checked
> the log directory.
>
> Many thanks
>
> Mike
>
> -----Original Message-----
> From: Joe Cooper [mailto:joe@swelltech.com]
> Sent: Monday, 27 May 2002 22:17
> To: Linux
> Cc: squid-users@squid-cache.org
> Subject: Re: [squid-users] Squid won't restart
>
>
> Ok, in that case...
>
> Check permissions again. Make sure the cache_dir and log
> directory are
> writable by Squid (for example, on a Red Hat machine with Squid
> installed from RPM, Squid will run as user squid, group
> squid...so the
> ownership of all cache_dirs and /var/log/squid should be
> squid:squid).
> This is the only thing it can be if Squid is telling you it
> doesn't have
> permission to write to the directory.
>
> By default Squid listens on port 3128 for client connections.
> Outgoing
> connections will usually be on port 80. If using Squid to
> proxy for FTP
> and HTTPS you will also have outgoing requests on 20 and 21 and 443.
> Some other ports come up as well, like 8080 and 8000, for
> standard http
> traffic.
>
> Return traffic back to Squid from origin servers will be on
> ephemeral or
> user ports, above port 1024.
>
> I think that covers it...Henrik, am I missing anything?
>
> Linux wrote:
> > The ports is not a problem it is an off topic side issue
> for my knowledge.
> > The main issue is that squid won't restart
> >
> > Many thanks
> >
> > Mike
> >
> > -----Original Message-----
> > From: Joe Cooper [mailto:joe@swelltech.com]
> > Sent: Monday, 27 May 2002 22:03
> > To: Linux
> > Cc: squid-users@squid-cache.org
> > Subject: Re: [squid-users] Squid won't restart
> >
> >
> > I'm confused...Is the problem still "permission denied"?
> If so, why ask
> > about ports...or is this a new problem?
> >
> > Linux wrote:
> >
> >>Hi
> >>
> >>I have done what you suggested below but it has made no
> difference. I am
> >>still unable to start Squid on this server.
> >>
> >>What port(s) does squid use when web traffic leaves it for
> the Internet.
> >>i.e. users come in on port xx and requests leave squid for
> the Internet on
> >>port ??
> >>
> >>Many thanks
> >>
> >>Mike
> >>
> >>-----Original Message-----
> >>From: Squid Support (Henrik Nordstrom) [mailto:hno@marasystems.com]
> >>Sent: Tuesday, 14 May 2002 21:43
> >>To: Linux; squid-users@squid-cache.org
> >>Subject: Re: [squid-users] Squid won't restart
> >>
> >>
> >>On Tuesday 14 May 2002 11:22, Linux wrote:
> >>
> >>
> >>
> >>>FATAL: Failed to make swap directory /var/spool/squid: (13)
> >>>Permission denied
> >>
> >>
> >>You need to make sure the user who Squid runs as
> >>(cache_effective_user) has permission to write to your cache_dir
> >>directories (/var/spool/squid above) and to the directory where you
> >>have told Squid to keep it's log files and pid file (usually
> >>/var/log/squid)
>
>
> This mail was processed by Mail essentials for Exchange/SMTP,
> the email security & management gateway. Mail essentials adds
> content checking, email encryption, anti spam, anti virus,
> attachment compression, personalised auto responders, archiving
> and more to your Microsoft Exchange Server or SMTP mail server.
> For more information visit http://www.mailessentials.com
>
>
> ---------------------------------------------------------
> This Mail has been checked for Viruses
> Attention: Encrypted mails can NOT be checked!
>
> **
>
> Diese Mail wurde auf Viren geprueft
> Hinweis: Verschluesselte mails koennen NICHT auf Viren
> geprueft werden!
> ---------------------------------------------------------
>

---------------------------------------------------------
This Mail has been checked for Viruses
Attention: Encrypted mails can NOT be checked!

**

Diese Mail wurde auf Viren geprueft
Hinweis: Verschluesselte mails koennen NICHT auf Viren geprueft werden!
---------------------------------------------------------

This mail was processed by Mail essentials for Exchange/SMTP,
the email security & management gateway. Mail essentials adds
content checking, email encryption, anti spam, anti virus,
attachment compression, personalised auto responders, archiving
and more to your Microsoft Exchange Server or SMTP mail server.
For more information visit http://www.mailessentials.com
Received on Wed Jun 12 2002 - 03:22:04 MDT

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:08:39 MST