Sorry to have bothered you, I got the solution...
Cheers,
Peter

Peter Kühnlein wrote:
Dear Colleagues,

Since yesterday, an unexpected and new error occurs on my machine. I am running an Apache 2 httpd preforked on a RH9 box (quite slow one & old, too). Analog is regularly run as a cronjob four times a day. Up to now, Analog worked really excellently and I've never had any trouble with it. Thanks to the developers! But now it appears to count all the access logs twice, telling me that they overlap with themselves. (See below.) Now, that the logs overlap with themselves is not surprising in itself; it's just a logical fact owing to Leibniz' law that states that identicals share all properties (and vice versa). But can anybody out there explain to me, why Analog all of a sudden starts to count them twice?
And: it's not only *new* logs, but also the *old* ones, which worked fine up to now, that are affected. In fact, I get *all* the requests counted twice, with no odd numbers occuring in the counts. The stats page is http://lubitsch.lili.uni-bielefeld.de/stats.html in case you want to convince yourselves... the recent increase in access frequency is correct & not a byproduct of the double count.

If someone could give me advice, I'd be very grateful.

Cordially, Peter

P.S.: Never mind the FLOOR and SORTBY warnings. I always get them, and don't care.

------- Start of forwarded message -------
Date: Sun, 4 Jan 2004 12:01:01 +0100
From: [EMAIL PROTECTED] (Cron Daemon)
To: [EMAIL PROTECTED]
Subject: Cron <[EMAIL PROTECTED]> analog
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <PATH=/usr/bin:/bin>
X-Cron-Env: <LOGNAME=root>

analog: analog version 5.32/Unix
analog: Warning D: In Domain Report, SORTBY (last date) doesn't match
  SUBSORTBY (bytes)
  (For help on all errors and warnings, see docs/errors.html)
analog: Warning D: In Failure Report, SORTBY (7-day requests) doesn't match
  ARGSSORTBY (requests)
analog: Warning D: In Failure Report, FLOOR (7-day requests) doesn't match
  ARGSFLOOR (requests)
analog: Warning D: In Request Report, SORTBY (7-day requests) doesn't match
  ARGSSORTBY (requests)
analog: Warning D: In Request Report, FLOOR (last date) doesn't match
  ARGSFLOOR (requests)
analog: Warning L: logfiles /var/log/httpd/access_log and
  /var/log/httpd/access_log overlap: possible double counting
analog: Warning L: logfiles /var/log/httpd/access_log.1.gz and
  /var/log/httpd/access_log.1.gz overlap: possible double counting
analog: Warning L: logfiles /var/log/httpd/access_log.10.gz and
  /var/log/httpd/access_log.10.gz overlap: possible double counting
analog: Warning L: logfiles /var/log/httpd/access_log.2.gz and
  /var/log/httpd/access_log.2.gz overlap: possible double counting
analog: Warning L: logfiles /var/log/httpd/access_log.3.gz and
  /var/log/httpd/access_log.3.gz overlap: possible double counting
analog: Warning L: logfiles /var/log/httpd/access_log.4.gz and
  /var/log/httpd/access_log.4.gz overlap: possible double counting
analog: Warning L: logfiles /var/log/httpd/access_log.5.gz and
  /var/log/httpd/access_log.5.gz overlap: possible double counting
analog: Warning L: logfiles /var/log/httpd/access_log.6.gz and
  /var/log/httpd/access_log.6.gz overlap: possible double counting
analog: Warning L: logfiles /var/log/httpd/access_log.7.gz and
  /var/log/httpd/access_log.7.gz overlap: possible double counting
analog: Warning L: logfiles /var/log/httpd/access_log.8.gz and
  /var/log/httpd/access_log.8.gz overlap: possible double counting
analog: Warning L: logfiles /var/log/httpd/access_log.9.gz and
  /var/log/httpd/access_log.9.gz overlap: possible double counting
------- End of forwarded message -------

+------------------------------------------------------------------------
|  TO UNSUBSCRIBE from this list:
|    http://lists.isite.net/listgate/analog-help/unsubscribe.html
|
|  Digest version: http://lists.isite.net/listgate/analog-help-digest/
|  Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
|  List archives:  http://www.analog.cx/docs/mailing.html#listarchives
+------------------------------------------------------------------------

Reply via email to