squid stops due to signal 6 and signal 25
 

Hi,

i'm got this msg when the SQUID stopped automatically.

Infact i have enough space in /usr/local/squid/var/logs drive.
the log file is also under 100 MB.

Any Guess...?
*********************************************************************************************

Nov 22 23:41:17 localhost squid[10016]: Squid Parent: child process
10018 exited due to signal 6
Nov 22 23:41:21 localhost squid[10016]: Squid Parent: child process
11576 started
Nov 22 23:41:21 localhost squid[10016]: Squid Parent: child process
11576 exited due to signal 25
Nov 22 23:41:24 localhost squid[10016]: Squid Parent: child process
11579 started
Nov 22 23:41:25 localhost squid[10016]: Squid Parent: child process
11579 exited due to signal 25
Nov 22 23:41:28 localhost squid[10016]: Squid Parent: child process
11583 started
Nov 22 23:41:28 localhost squid[10016]: Squid Parent: child process
11583 exited due to signal 25
Nov 22 23:41:31 localhost squid[10016]: Squid Parent: child process
11586 started
Nov 22 23:41:32 localhost squid[10016]: Squid Parent: child process
11586 exited due to signal 25
Nov 22 23:41:35 localhost squid[10016]: Squid Parent: child process
11589 started
Nov 22 23:41:35 localhost squid[10016]: Squid Parent: child process
11589 exited due to signal 25
Nov 22 23:41:35 localhost squid[10016]: Exiting due to repeated,
frequent failures
**************************************************************************************************** **
Any help would be appreciated.

Thanks,
Rahul


Hello,

To add to below mentioned problem::

it all stared with squid exiting due to signal 6 :::

Nov 22 23:41:17 localhost (squid): logfileWrite:
/usr/local/squid/var/logs/store.log: (0) Success
Nov 22 23:41:17 localhost squid[10016]: Squid Parent: child process
10018 exited due to signal 6

later i investigated further in cache.log that revels the following::::

FATAL: logfileWrite: /usr/local/squid/var/logs/store.log: (0) Success

Squid Cache (Version 2.5.STABLE6): Terminated abnormally.
CPU Usage: 108696.530 seconds = 23233.910 user + 85462.620 sys
Maximum Resident Size: 0 KB
Page faults with physical i/o: 454770
Memory usage for squid via mallinfo():
total space in arena: 449480 KB
Ordinary blocks: 411592 KB 41705 blks
Small blocks: 0 KB 0 blks
Holding blocks: 192 KB 1 blks
Free Small blocks: 0 KB
Free Ordinary blocks: 37887 KB
Total in use: 411784 KB 92%
Total free: 37887 KB 8%

Any clue.........?

Thanks
Rahul

Hi,

is that because max-file-desciptor is set only to 1024 the problem is arising ?

do increasing max-file-descriptor work if many squid is serving lot of proxy ?

Thanks,
Rahul

It's gonna be due to a logfile getting too large, eg cache.log.. That's error 25..

If the file isn't that big, it may be time for an fsck of that partition or a faster log rotation, or anything that will start a fresh file to write to..

Also try clearing and rebuilding the cache..

check squid.log access.log and cache.log size they maybe over 1GB, delete them and restart squid.

solution to squid failures
 

we were also running into the same issues.
Step 1: No.of File Descriptors
To know the current maximum file descriptors
$ulimit -n
1024
Increase the no.of file descriptors
$vi /etc/security/limits.conf
make following entries
* soft nofile 4096
* hard nofile 65536

Step 2. check whether the size of access.log or cache.log is exceeding 2GB. By default in Redhat Linux 2GB is the maximum size allowed.
Do log rotation based on file size.To check whether this is the right reason for squid failire
$cat /dev/null > /var/log/squid/access.log
$cat /dev/null > /var/log/squid/cache.log
and restart squid and see if the error crops up