perl-modperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joachim Zobel <>
Subject Re: No error log, no database
Date Fri, 02 Aug 2002 15:36:59 GMT
At 09:03 02.08.2002 +0800, you wrote:
>Joachim Zobel wrote:
>>Yesterday it happened that our error log reached 2Gb. Since ours is a 
>>linux box writing to it stopped. At the same time all database driven 
>>functionality stopped working (Plain DBI on Mysql, no Apache::DBI). The 
>>database was still usable through the PHP admin interface. The filesystem 
>>was not full. When the log was rotated, everything returned to normal.
>>This was on a virtual Apache 1.3.26, mod_perl 1.25.
>>Does  anybody have an idea what happened?
>You've hit the 2GB limit.

Yes, I know. I should have stated my question more clearly. But normally it 
should not be a critical error if the error log can no longer be written. 
In our case the database was not accessible (except for one handler that 
does a very simple SELECT). My question is: How did reaching the error logs 
2Gb limit affect the database driver?

[adding large file support]

Thanks. This is not an option. We will simply increase the rotation frequency.


"... ein Geschlecht erfinderischer Zwerge, die fuer alles gemietet werden
koennen."                            - Bertolt Brecht - Leben des Galilei

View raw message