next message in archive
no next message in thread
previous message in archive
Index of Subjects
CCN-TECH readers - A week or so ago I set DEBUG_global to 0 (no
debugging). I've set it back to 1 to see if we can figure out where/why
some of this extra output comes from that is turning up in the:
$CS_ROOT/cronbin/httpd-logsum "Other Error Output" report
-----
from... $CS_ROOT/etc/conf/debug
# This file determines the level of debugging output to be logged by csuite
# scripts. The three debugging levels are 0 (no debugging), 1 (overwrite
# debug file on every execution) and 2 (append to the debug file).
#
# The variable DEBUG_global defines the default debugging level. The
# debugging level for a particular script can be set with DEBUG_scriptname.
#
DEBUG_global=1
========================================================================
csuite-dev readers might want to:
1) check that your version of this report which goes to $STATS_ALIAS is
going to the right people
2) add some additional filtering to the specification for Other Error
Output... in our case we added three filters to reduce the output to a
manageable level...
(from $CS_ROOT/cronbin/httpd-logsum - and reformatted... for clarity...)
egrep -v "access to $CS_USERHOME/"'|
lqword: warning: No index information for:|
++ contained no recognised words|
++ lingering close|
++ lost connection to client|
send aborted|
No file match|
could not get local address|
does not exist|
timed out' error_log.$today |
sort | uniq -c | sort -nr |
mail_output $STATS_ALIAS "$SHORT_NAME: Other Error Output"
cheers
david potter
next message in archive
no next message in thread
previous message in archive
Index of Subjects