Re: New squid packages 2.4.6-2woody9 restarts very often.
Hi
I had very similar problems with squid_2.4.6-2woody9_i386.deb yesterday
and resolved them, like you, by reinstalling the previous package
(squid_2.4.6-2woody8_i386.deb).
aragon@onlinehome.de wrote:
> Looking in the logfiles shows, that squid 2.4.6-2woody9 restarts very
> often:
>
> upuaut:~# grep "Starting Squid Cache" /var/log/syslog
> Jul 12 12:00:33 upuaut squid[7747]: Starting Squid Cache version 2.4.STABLE6 for i386-debian-linux-gnu...
Same here:
host:/var/log# grep "Starting Squid Cache" squid/cache.log.1 | awk ' {
print $1" "$2 } '
2005/07/12 07:36:45|
2005/07/12 07:45:05|
2005/07/12 07:53:52|
2005/07/12 07:54:03|
2005/07/12 07:54:13|
2005/07/12 07:54:23|
2005/07/12 07:54:33|
2005/07/12 08:46:12|
2005/07/12 08:46:24|
2005/07/12 08:46:34|
2005/07/12 08:46:45|
2005/07/12 08:46:55|
2005/07/12 08:53:04|
2005/07/12 08:53:10|
2005/07/12 08:53:14|
2005/07/12 08:53:21|
2005/07/12 08:53:25|
2005/07/12 08:55:13|
2005/07/12 08:55:17|
2005/07/12 08:55:28|
2005/07/12 08:55:38|
2005/07/12 08:55:48|
2005/07/12 08:59:41|
2005/07/12 08:59:44|
2005/07/12 08:59:47|
2005/07/12 08:59:50|
2005/07/12 08:59:53|
2005/07/12 08:59:54|
2005/07/12 08:59:56|
2005/07/12 08:59:59|
2005/07/12 09:00:13|
2005/07/12 09:03:26|
2005/07/12 09:03:41|
2005/07/12 09:05:29|
2005/07/12 09:06:02|
The last two lines are from the old package, I'd manually restarted it once.
> The only significant error message I found was this one. Everytime 3
> seconds before a new squid process starts:
>
> upuaut:~#grep "Squid Parent: child process.*exited due to signal 6" /var/log/syslog
> Jul 12 12:00:30 upuaut squid[7466]: Squid Parent: child process 7697 exited due to signal 6
> Jul 12 12:00:47 upuaut squid[7466]: Squid Parent: child process 7747 exited due to signal 6
> Jul 12 12:00:53 upuaut squid[7466]: Squid Parent: child process 7775 exited due to signal 6
I see these too, an excerpt follows (excuse the linebreaks):
Jul 12 08:46:12 host squid[9223]: Squid Parent: child process 9226 started
Jul 12 08:46:21 host squid[9223]: Squid Parent: child process 9226
exited due to signal 6
Jul 12 08:46:24 host squid[9223]: Squid Parent: child process 9231 started
Jul 12 08:46:31 host squid[9223]: Squid Parent: child process 9231
exited due to signal 6
Jul 12 08:46:34 host squid[9223]: Squid Parent: child process 9235 started
Jul 12 08:46:42 host squid[9223]: Squid Parent: child process 9235
exited due to signal 6
Jul 12 08:46:45 host squid[9223]: Squid Parent: child process 9240 started
Jul 12 08:46:52 host squid[9223]: Squid Parent: child process 9240
exited due to signal 6
In contrast to Holger, I didn't see any URL in the cache.log file, but I
did see the following when I started squid on the console, telling it
not to detach -- perhaps 99 isn't a valid debug level, though:
host:/var/log/squid# squid -d 99 -z -N
2005/07/12 09:00:08| Creating Swap Directories
host:/var/log/squid# squid -d 99 -N
2005/07/12 09:00:13| Starting Squid Cache version 2.4.STABLE6 for
i386-debian-linux-gnu...
2005/07/12 09:00:13| Process ID 9512
2005/07/12 09:00:13| With 1024 file descriptors available
2005/07/12 09:00:13| Performing DNS Tests...
2005/07/12 09:00:13| Successful DNS name lookup tests...
2005/07/12 09:00:13| DNS Socket created on FD 4
2005/07/12 09:00:13| Adding nameserver 192.168.7.3 from /etc/resolv.conf
2005/07/12 09:00:13| User-Agent logging is disabled.
2005/07/12 09:00:13| Referer logging is disabled.
2005/07/12 09:00:13| Unlinkd pipe opened on FD 9
2005/07/12 09:00:13| Swap maxSize 1048576 KB, estimated 80659 objects
2005/07/12 09:00:13| Target number of buckets: 4032
2005/07/12 09:00:13| Using 8192 Store buckets
2005/07/12 09:00:13| Max Mem size: 81920 KB
2005/07/12 09:00:13| Max Swap size: 1048576 KB
2005/07/12 09:00:13| Local cache digest enabled; rebuild/rewrite every
3600/3600 sec
2005/07/12 09:00:13| Rebuilding storage in /var/spool/squid (DIRTY)
2005/07/12 09:00:13| Using Least Load store dir selection
2005/07/12 09:00:13| Set Current Directory to /var/spool/squid
2005/07/12 09:00:13| Loaded Icons.
2005/07/12 09:00:14| Accepting HTTP connections at 0.0.0.0, port 3600,
FD 10.
2005/07/12 09:00:14| HTCP Disabled.
2005/07/12 09:00:14| WCCP Disabled.
2005/07/12 09:00:14| Ready to serve requests.
2005/07/12 09:00:14| temporary disabling (Bad Request) digest from localhost
2005/07/12 09:00:14| Done scanning /var/spool/squid swaplog (0 entries)
2005/07/12 09:00:14| Finished rebuilding storage from disk.
2005/07/12 09:00:14| 0 Entries scanned
2005/07/12 09:00:14| 0 Invalid entries.
2005/07/12 09:00:14| 0 With invalid flags.
2005/07/12 09:00:14| 0 Objects loaded.
2005/07/12 09:00:14| 0 Objects expired.
2005/07/12 09:00:14| 0 Objects cancelled.
2005/07/12 09:00:14| 0 Duplicate URLs purged.
2005/07/12 09:00:14| 0 Swapfile clashes avoided.
2005/07/12 09:00:14| Took 0.9 seconds ( 0.0 objects/sec).
2005/07/12 09:00:14| Beginning Validation Procedure
2005/07/12 09:00:14| Completed Validation Procedure
2005/07/12 09:00:14| Validated 0 Entries
2005/07/12 09:00:14| store_swap_size = 84k
2005/07/12 09:00:14| storeLateRelease: released 0 objects
squid: rfc1035.c:410: rfc1035RRUnpack: Assertion `(*off) <= sz' failed.
Aborted
Since RFC 1035 deals with DNS and the Squid patch ist meant to
specifically fix a DNS issue, I suspect there's a bug in the patch. Not
knowing what better to do, I'm sending this message to the security team
per CC.
Cheers,
Tobias
Reply to: