GNOME Bugzilla – Bug 392675
Uncontrolled Log File Growth
Last modified: 2007-02-11 22:06:53 UTC
Granted, this is a much bigger issue in the older versions, now that debugging is turned off, and at the moment this is more a placeholder should we get more reports from people running the latest and greatest, but I wanted us to be aware.
Just wanted to let you know that I am running 0.2.14 (Edgy Janvitus repo) and I am constantly finding log files taking up over 10GB in size. Yes, that is 10 gigabytes. I believe it only started happening when I stopped using Evolution and installed Thunderbird as my mail app. I tried adding an exclusion for my .mozilla-thunderbird directory but i couldn't via the GUI. However I was able to add it via the command line tools. I'll report back if I see these huge logs files any more.
kirk: We'll need a portion of those log files to know what's going on which would cause them to grow so big. As for the thunderbird backend, you can turn it off by passing in "--backend -thunderbird" or by using the beagle-config tool to disable it permanently. We need to add it to the UI still.
How much of the log would you like? It seems my trick was insufficient and I now have a 5.3 GB logfile I can use.
Presumably there are repeating errors in the files, a 1000 or so lines would probably be good.
Created attachment 81911 [details] Beagle log file (last 1000 lines of 5.3 GB log file) Well, the last 1000 lines of the log aren't all that interesting, actually. I've attached it, but it basically just repeats the following lines around 450 times: 20070130 18:36:36.2783 04784 Beagle DEBUG: Running file crawl task 20070130 18:36:36.2797 04784 Beagle DEBUG: Done crawling '/etc/sgml/docbook-xml/4.0' Can I grep for a particular phrase where things might be more interesting?
Nope, the repeating of that single directory is the bug itself. It was recently fixed in SVN, and might possibly be fixed in 0.2.15.1 depending on what caused it.
This is definitely fixed in 0.2.16. The log file was actually filled due to beagle looping on a directory. That has been fixed in 0.2.16.