[squid-users] squid unable to start on CentOS 6.5

[Amos Jeffries]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 23/12/2014 10:35 a.m., Derek Cole wrote:
> Hello,
> 
> I have a succesful version of squid installed on a CentOS 6.5 box,
> and another Centos65 box where it is not working when I type
> "service squid start" Both boxes have the identical squid
> configuration, and i ensured that they were both running the same
> version, 3.4.8
> 
> From the cache.log file:
> 
> 2014/12/22 16:22:22| Set Current Directory to /var/spool/squid 
> 2014/12/22 16:23:25| Set Current Directory to /var/spool/squid 
> 2014/12/22 16:29:32 kid1| Set Current Directory to
> /var/spool/squid 2014/12/22 16:29:32 kid1| Starting Squid Cache
> version 3.4.8 for x86_64-redhat-linux-gnu... 2014/12/22 16:29:32
> kid1| Process ID 1555 2014/12/22 16:29:32 kid1| Process Roles:
> worker 2014/12/22 16:29:32 kid1| With 1024 file descriptors
> available 2014/12/22 16:29:32 kid1| Initializing IP Cache... 
> 2014/12/22 16:29:32 kid1| DNS Socket created at [::], FD 7 
> 2014/12/22 16:29:32 kid1| DNS Socket created at 0.0.0.0, FD 8 
> 2014/12/22 16:29:32 kid1| Adding nameserver 8.8.8.8 from
> /etc/resolv.conf 2014/12/22 16:29:32 kid1| Logfile: opening log 
> daemon:/var/log/squid/access.log 2014/12/22 16:29:32 kid1| Logfile
> Daemon: opening log /var/log/squid/access.log 2014/12/22 16:29:32
> kid1| Local cache digest enabled; rebuild/rewrite every 3600/3600
> sec 2014/12/22 16:29:32 kid1| Store logging disabled 2014/12/22
> 16:29:32 kid1| Swap maxSize 0 + 262144 KB, estimated 20164 objects 
> 2014/12/22 16:29:32 kid1| Target number of buckets: 1008 2014/12/22
> 16:29:32 kid1| Using 8192 Store buckets 2014/12/22 16:29:32 kid1|
> Max Mem  size: 262144 KB 2014/12/22 16:29:32 kid1| Max Swap size: 0
> KB 2014/12/22 16:29:32 kid1| Using Least Load store dir selection 
> 2014/12/22 16:29:32 kid1| Set Current Directory to
> /var/spool/squid 2014/12/22 16:29:32 kid1| Finished loading MIME
> types and icons. 2014/12/22 16:29:32 kid1| HTCP Disabled. 
> 2014/12/22 16:29:32 kid1| sendto FD 12: (1) Operation not
> permitted 2014/12/22 16:29:32 kid1| ipcCreate: CHILD: hello write
> test failed
> 

Broken helper program or something like apparmor/selinux blocking I/O
sockets use.

> from squid.out:
> 
> squid: ERROR: No running copy 2014/12/22 16:29:32| WARNING:
> Netmasks are deprecated. Please use CIDR masks instead. 2014/12/22
> 16:29:32| WARNING: IPv4 netmasks are particularly nasty when used
> to compare IPv6 to IPv4 ranges. 2014/12/22 16:29:32| WARNING: For
> now we will assume you meant to write /32 2014/12/22 16:29:32|
> WARNING: (A) '0.0.0.0' is a subnetwork of (B) '::/0' 2014/12/22
> 16:29:32| WARNING: because of this '0.0.0.0' is ignored to keep 
> splay tree searching predictable 2014/12/22 16:29:32| WARNING: You
> should probably remove '0.0.0.0' from the ACL named 'all'

Those "WARNING" are about Squid-2 configuration settings being used in
a Squid-3 config file. They are not stopping Squid from starting.

The last few are about your config file containing an "acl all "
definition. In Squid-3 that is a built-in ACL that covers more than
just IPv4. The rest of the warnings may be side effects of that
re-definition.

Please run "squid -k parse", it will show you the config line which is
being processed when the issue(s) are found.


Amos
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJUmKQxAAoJELJo5wb/XPRjH3QH/1Ruur9o4bi2uk1ABhTajQGV
H1ud1lFRYexUHAbAhV2aHQozZuHaXrx73OPObg7wRPltZqwoPSbtQuq/TmM61uDW
oOXlYrcKoFPtmNOn+UJMz/kUoKn9//vdWH3nDBGLtmE1oY++3sfKcHsHYsj6jn22
X/2LctH2Z5+qRJ8pREXfY02VINvDyctaABNDgNr651UpTX//fGaEoMi9ou+whtot
TqhtfFPIywni1XBstxW8bobTRjJqqBRsXBexukHyzXRVBZ/Av2tl+ABgWL+R0ci7
3f3BFCKbaHh5BDThV05VR2FIkDxy3mADm8l87TO1UWxhHFQdOK2d9TXkj13DKv4=
=sEGT
-----END PGP SIGNATURE-----