From: Leonid Mamchenkov <f.l.linux-admin@news.francoudi.com>
To: linux-admin@vger.kernel.org
Subject: Re: problem with cron job of Webalizer
Date: Fri, 13 Jun 2003 11:22:22 +0000 (UTC) [thread overview]
Message-ID: <20030613112222.GA1257@francoudi.com> (raw)
In-Reply-To: <3EE5C981.A04C083F@tid.es>
Dear Miguel Gonz?lez Casta?os,
Once you wrote about "problem with cron job of Webalizer":
MGlCo> I have a script for executing webalizer for the different virtual
MGlCo> hosts. That script works in the command prompt.
MGlCo>
MGlCo> I have been testing if it was dued to the environment variables, that
MGlCo> werent loaded, but I put on the script a ". /root/.bash_profile "
MGlCo> instruction to avoid that.
MGlCo>
MGlCo> I got a mail when the job is supposed to be done by cron.
MGlCo>
MGlCo> In the access log files of apache, I use rotate logs. The rotate logs
MGlCo> of apache is done daily and before the webalizer cron job is donde.
MGlCo>
MGlCo> What I have seen so far, its that sometimes it works and sometimes it
MGlCo> doesnt. Sometimes the system doesnt log all the accesses in all virtual
MGlCo> hosts (some do work and others dont) and normally if the webalizer
MGlCo> scripts updates fine the stats html files then apache stops logging the
MGlCo> access files and the other way round...
MGlCo>
MGlCo> Anyone could give any ideas of how I could trace the behaviour of the
MGlCo> system?
Did you try to run webalizer _before_ you rotate the logs? It's also a
good idea to measure how much time does it take for your webalizer jobs
to finish. This will help you to make sure webalizer has enough time
before the logs are taken from it. :)
--
Best regards,
Leonid Mamtchenkov, RHCE
System Administrator
Francoudi & Stephanou Ltd.
next prev parent reply other threads:[~2003-06-13 11:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-10 12:05 problem with cron job of Webalizer Miguel González Castaños
2003-06-13 11:22 ` Leonid Mamchenkov [this message]
2003-06-18 8:13 ` Miguel González Castaños
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030613112222.GA1257@francoudi.com \
--to=f.l.linux-admin@news.francoudi.com \
--cc=leonid@francoudi.com \
--cc=linux-admin@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).