After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 417053 - Huge LOG file generated
Huge LOG file generated
Status: RESOLVED DUPLICATE of bug 419389
Product: beagle
Classification: Other
Component: General
0.2.16
Other All
: Normal critical
: ---
Assigned To: Beagle Bugs
Beagle Bugs
Depends on:
Blocks:
 
 
Reported: 2007-03-11 12:18 UTC by Andor J Kiss
Modified: 2007-03-17 18:59 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Andor J Kiss 2007-03-11 12:18:18 UTC
Please describe the problem:
Beagle (running on the Herd 5 Feisty Fawn install) uses 16+ GB of HD space.  It also runs so much that boosts the CPU temps about +20oC.  This did not occur with the Dapper Drake build (0.2.6).  Beagle fills my entire HD with an index and log file such that there is "0 Bytes" left.  I consider this a critical bug and have uninstalled until it is fixed.

Steps to reproduce:
1. Install Feisty Fawn Herd 5
2. Run Beagle for the first time
3. After approximately two days, HD will be full


Actual results:
HD fills to capacity, system becomes unresponsive and unstable

Expected results:


Does this happen every time?
twice so far

Other information:
Comment 1 Debajyoti Bera 2007-03-11 15:25:17 UTC
Argh... you wiped out the directory "~/.beagle/Log" or still have it ?
Comment 2 Andor J Kiss 2007-03-11 19:23:46 UTC
Hi,

Had to wipe it out to use machine, but I can reinstall beagle and try to replicate the problem.  If so, let me know and also let me know which files you'll need to debug (and how to send them on to you).

- CH
Comment 3 Debajyoti Bera 2007-03-11 19:34:17 UTC
Andor, thanks for willing to help. If you can, please reinstall beagle, let it run. If the log file directory grows beyond, say, 50 MB, its a sign of trouble. Tar-gz the entire ~/.beagle/Log directory and attach it to the bug. If it has sensitive data, you can email it to me at dbera.web@gmail.com.

If the size of the tarred directory is too large, I am specifically interested in the files pointed to by ~/.beagle/Log/current-* Besides that, any large file (> 10 MB) in ~/.beagle/Log is of interest.

Thanks.
Comment 4 Andor J Kiss 2007-03-12 14:51:34 UTC
Okay,  bug is back.  Had Beagle installed for 24 hours.  This Dell laptop i8100 is now running +20oC (almost 80% CPU) and is ALWAYS indexing (I suspect).

The LOG file directory is 4.5 GB (GB, not MB) so far.

Cannot mail file.  Too large (45 MB archive)

I've uninstalled beagle again, it's running my machine ragged.

Let me know how you want the file
Comment 5 Joe Shaw 2007-03-12 16:47:28 UTC
The first and last 1000 lines or so of the log would probably be fine.

The problem is not that it's always indexing, but that it's repeatedly looping on some bug.

Thanks.
Comment 6 Debajyoti Bera 2007-03-12 17:32:41 UTC
Andor, just to add what Joe replied, can you attach the first and last 1000 lines of ~/.beagle/current-* files (there will be 2-4 of them) ?
Also I am curious, can you attach the output of
$ ls -l ~/.beagle/Log
Comment 7 Joe Shaw 2007-03-17 16:48:57 UTC
The Feisty herds released so far have a known bug in the SVG filter which will cause this problem.  0.2.16.3 was just pushed into the Feisty tree which will solve this:

https://launchpad.net/ubuntu/+source/beagle

Marking this as a dup of another similar bug.

*** This bug has been marked as a duplicate of 419389 ***
Comment 8 Andor J Kiss 2007-03-17 17:06:13 UTC
Confirmed. Beagle 0.2.16.3 fixed the problem on Feisty.

  Sorry I couldn't post the files, but they were 500MB+ and I couldn't open them to pull the first and last thousand lines.
Comment 9 Joe Shaw 2007-03-17 18:52:09 UTC
Great, glad to hear it.

You can output the first 1000 lines by doing:

   head -n 1000 > head.txt

and the last 1000:

   tail -n 1000 > tail.txt

but that does assume that you have enough disk space to actually write those out. :)
Comment 10 Joe Shaw 2007-03-17 18:59:45 UTC
Ooops, typo.

head -n 1000 huge-log > head.txt

(or tail)