| Subject | Re: [firebird-support] HUGE Log File |
|---|---|
| Author | Helen Borrie |
| Post date | 2015-09-15T00:29:51Z |
At 11:58 a.m. 15/09/2015, chubmasterp@... [firebird-support] wrote:
It won't do any harm to open your new log file in a day or two, and see just what is happening in the environment to cause such a high volume of log messages. It's pretty common to see a lot of network errors in an environment where users just "crash out" of their application programs, instead of following the correct route for a proper client shutdown. On the "good" side, Firebird doesn't corrupt data when these events occur, although it's quite possible that uncommitted new work will just get lost when the server goes about its normal business of clearing up garbage.
On the "bad" side, you'll get zillions of logs from these crashes. Firebird logs unexpected events from its own engine, but these are rare compared to the message it logs from the operating system, the file system and the network. Firebird has no control over these external mechanisms so it can't correct them. It just does its best to report these environmental abnormalities.
Helen
>Actually its a 424 gb log file that increased by 300 gb since sept 10, 2015Yes, sorry, I noticed that after I posted. ;-)
It won't do any harm to open your new log file in a day or two, and see just what is happening in the environment to cause such a high volume of log messages. It's pretty common to see a lot of network errors in an environment where users just "crash out" of their application programs, instead of following the correct route for a proper client shutdown. On the "good" side, Firebird doesn't corrupt data when these events occur, although it's quite possible that uncommitted new work will just get lost when the server goes about its normal business of clearing up garbage.
On the "bad" side, you'll get zillions of logs from these crashes. Firebird logs unexpected events from its own engine, but these are rare compared to the message it logs from the operating system, the file system and the network. Firebird has no control over these external mechanisms so it can't correct them. It just does its best to report these environmental abnormalities.
Helen