Tomcat 4.0 access log DIES all the time for no reason

[André de Jesus <an...@tektix.com>]

Hi

Access logs are very important to server maintenance and traffic analysis.

So, a log system needs to be flexible.

In UNIX (Linux), flexibility is obtainable through the filesystem 
interface. For example, logs can be sent to a pipe instead of a regular 
file. Then, a process reads the pipe and inserts the lines in a database.

With Tomcat and its default system of attributing dates to the log files 
(a very good idea), I tried to have a process run by cron that reads the 
logs of the previous day, writes them to a database and then deletes the 
previous file.

But then what happens is that the log DIES when the previous file is 
deleted. There is even an IOException in some other log files. This is 
what happens predictably. But unpredictably, the log also seems to DIE 
for no reason, sometimes.

I haven't seen this problem described anywhere in this mailing list. Is 
it because no one worries about logs, or because there's something wrong 
with my use of Tomcat?

Thanks,

Andre de Jesus

Re: Tomcat 4.0 access log DIES all the time for no reason

["Craig R. McClanahan" <cr...@apache.org>]

Can you please post a stack trace, and describe exactly what you're doing.
I don't know what "the log DIES" means.

Craig

On Tue, 2 Oct 2001, André de Jesus wrote:

> Date: Tue, 02 Oct 2001 13:23:56 +0100
> From: André de Jesus <an...@tektix.com>
> Reply-To: tomcat-user@jakarta.apache.org
> To: tomcat-user@jakarta.apache.org
> Subject: Tomcat 4.0 access log DIES all the time for no reason
>
> Hi
>
> Access logs are very important to server maintenance and traffic analysis.
>
> So, a log system needs to be flexible.
>
> In UNIX (Linux), flexibility is obtainable through the filesystem
> interface. For example, logs can be sent to a pipe instead of a regular
> file. Then, a process reads the pipe and inserts the lines in a database.
>
> With Tomcat and its default system of attributing dates to the log files
> (a very good idea), I tried to have a process run by cron that reads the
> logs of the previous day, writes them to a database and then deletes the
> previous file.
>
> But then what happens is that the log DIES when the previous file is
> deleted. There is even an IOException in some other log files. This is
> what happens predictably. But unpredictably, the log also seems to DIE
> for no reason, sometimes.
>
> I haven't seen this problem described anywhere in this mailing list. Is
> it because no one worries about logs, or because there's something wrong
> with my use of Tomcat?
>
> Thanks,
>
> Andre de Jesus
>
>
>
>