Kinkie wrote:
On Mon, Mar 30, 2009 at 1:31 AM, Nagios
<[email protected]> wrote:
***** Nagios *****
Notification Type: PROBLEM
Service: HTTP
Host: wiki.squid-cache.org
Address: wiki.squid-cache.org
State: CRITICAL
Date/Time: Sun Mar 29 16:31:55 PDT 2009
Additional Info:
Connection refused
Sorry guys.
Root cause of this was eu getting a RAM upgrade (4 gigs now). Upon
reboot, the squid acting as a rproxy failed starting up with this
error:
2009/03/29 19:20:19| Configuring Parent squid-cache.org/80/0
2009/03/29 19:20:19| WARNING: Disk space over limit: 275488 KB > 102400 KB
2009/03/29 19:20:19| assertion failed: ../../lib/Profiler.c:213:
"cstack[cstack_head].timer == type"
Squid Cache: Version 3.1.0.6-BZR
configure options: '--enable-debug-cbdata'
'--enable-xmalloc-statistics' '--disable-wccp' '--disable-wccpv2'
'--disable-htcp' '--enable-ssl' '--enable-stacktraces'
'--enable-cpu-profiling' '--enable-storeio=ufs,aufs'
'--enable-disk-io=AIO,Blocking,DiskThreads'
'--enable-removal-policies=heap' '--prefix=/usr/local/squid'
'--enable-ltdl-convenience' '--disable-optimizations'
'--with-default-user=squid' '--cache-file=/tmp/config.cache'
'--with-filedescriptors=1024' '--with-valgrind-debug'
--with-squid=/home/kinkie/squid/squid-3.1-bzr
Try killing the cpu-profiling for now. It's known to have problems
sometimes. This seems to be one.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE6 or 3.0.STABLE13
Current Beta Squid 3.1.0.6
