beagled-helper and beagle run away with CPU and memory

Bug #69752 reported by Rylie Pavlik
34
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Beagle
Fix Released
Medium
beagle (Ubuntu)
Fix Released
Undecided
Kevin Kubasik

Bug Description

Binary package hint: beagle

I recently upgraded from Dapper to Edgy on AMD64. Frequently (once per hour or so, seemingly more common when I step away from the computer for a while), beagle apparently goes wild indexing my hard drive and quickly consumes all 1gb of system memory and 1gb of swap. The beagled-helper process is the one consuming the most memory (when I can get a system monitor open to watch), but if beagled is not also killed, it will spawn a new beagled-helper that does the same thing, nearly immediately. The net result of this is that any time the computer is left alone to turn off the screen by itself, beagle runs away and so it cannot be woken back up. I have tried moving ~/.beagle out of the way in case faulty data from my old dapper install was causing problems, but that does not help. I have uninstalled beagle (and beagle-backend-evolution) temporarily until this problem is resolved, as a workaround, since it makes the system nearly unusable. beagled is listed as a startup program in the session preferences. Thanks for your help!

Revision history for this message
Slogger (slogger) wrote :

https://launchpad.net/distros/ubuntu/+source/beagle/+bug/70426

I have the same problem on a system I upgraded to edgy from dapper.

I have a turion 64, but it is the 32-bit Ubuntu.

Filed I different bug report because I hadn't seen this one.

Revision history for this message
Stephen Chu (standby) wrote :

Same issue for my notebook (Pentium-M).

Revision history for this message
Joe Shaw (joeshaw) wrote :

Can you guys attach your ~/.beagle/Log/current-* files when this happens?

Revision history for this message
Kevin Kubasik (kkubasik) wrote :

This should be fixed (at least in this instance) upstream, but I would like a confirmation.

Changed in beagle:
status: Unconfirmed → Needs Info
Revision history for this message
Justin Hartman (jjhartman) wrote :

I have had the same issue running on iBook G4 PPC, 1.33Ghz, 768MB RAM on Edgy. This was a fresh install on my iBook using the standard 6.10 PPC distro. My CPU get consumed all the time as soon as my machine boots up.

Revision history for this message
Justin Hartman (jjhartman) wrote :

Attached current-beagle log file as per previous post.

Revision history for this message
Ricardo Bánffy (rbanffy) wrote : Anyone using Thunderbird for email?

Seems to be the same problem as in 59615, 64662, 67684, 72047 and 73902

Revision history for this message
Alperen Yusuf Aybar (alperen) wrote :

I can confirm this bug on my edgy installation

Revision history for this message
Thijs N (thijsn) wrote :

I can confirm this bug on my Edgy installation too. There's a heavy load on CPU and RAM.

Revision history for this message
Kevin Kubasik (kkubasik) wrote :

This is one of those benchmark bugs that we will always work on, but can never really make perfect, 0.2.14 was a huge step in the right direction though.

Changed in beagle:
assignee: nobody → kkubasik
status: Needs Info → Confirmed
Revision history for this message
Joe Shaw (joeshaw) wrote :

We need a 0.2.14 build for edgy so that we can track down specific files that are causing the 100% CPU utilization. 0.2.14 also has a *lot* of leak fixes, so memory usage shouldn't get out of hand.

Revision history for this message
Kevin Kubasik (kkubasik) wrote :

I can get on that if I can get word from someone at ubuntu my time will be well spent, I don't wanna package it just to have it not used.

Revision history for this message
Slogger (slogger) wrote : Re: [Bug 69752] Re: beagled-helper and beagle run away with CPU and memory

Hey, I don't know what's been going on with this bug, I haven't been
paying attention 'cause of school (finals and all, then christmas), but
I just wanted to note that it disappears, or seems to, after most
volumes have been indexed, and that its severity seems to be in
proportion to the number of un-indexed drives/partitions. (At least for
me, it seems to wait to show up until I attache an external 250 gig
drive in 4 or 5 partitions.) I don't know if this is how it acts for the
rest of you...

Dustin

On Wed, 2007-01-03 at 20:15 +0000, Matthew Niks wrote:
> I can confirm this bug on my Edgy installation too. There's a heavy load
> on CPU and RAM.
>

----------------------------------------------------------------------
Online Nursing Programs
Healthcare careers are booming. Education-Advancement offers fast,...
http://tags.bluebottle.com/fc/MhtYWUjAVAA5b0PIkMepjGCziwL6Jbil0KvB6/

Revision history for this message
Justin Hartman (jjhartman) wrote : Re: [Bug 69752] Re: beagled-helper and beagle run away with CPU and memory

On 1/4/07, Joe Shaw <email address hidden> wrote:
> We need a 0.2.14 build for edgy so that we can track down specific files
> that are causing the 100% CPU utilization. 0.2.14 also has a *lot* of
> leak fixes, so memory usage shouldn't get out of hand.

I can tell you that from experience on my system RTF files were
causing the problem. I had about 1,000 rtf files and once I removed
them off my system and rebooted the 100% cpu issue stopped
immediately.
--
Regards
Justin Hartman
PGP Key ID: 102CC123

Revision history for this message
Joe Shaw (joeshaw) wrote :

Justin: you will be happy to know that the RTF filter is fixed now in svn. :)

http://bugzilla.gnome.org/show_bug.cgi?id=393766

Revision history for this message
Justin Hartman (jjhartman) wrote :

Fantastic news Joe. Well done to all involved who helped get this
resolved. I'll be sure to update my system and test it out!

Regards
Justin

On 1/10/07, Joe Shaw <email address hidden> wrote:
> Justin: you will be happy to know that the RTF filter is fixed now in
> svn. :)
>
> http://bugzilla.gnome.org/show_bug.cgi?id=393766
>
> --
> beagled-helper and beagle run away with CPU and memory
> https://launchpad.net/bugs/69752
>

--
Regards
Justin Hartman
PGP Key ID: 102CC123

Revision history for this message
Markus Kienast (elias1884) wrote : Please backport to edgy!

Please backport this to edgy, even if this is now version 0.2.14 instead of 0.2.9! Beagle is unusable in EDGY as is!

There needs to be a backport of some kind unless you want to keep the release broken!

If you don't want to backport, please at least make a .deb available somewhere!

Revision history for this message
Markus Kienast (elias1884) wrote :
Revision history for this message
Joe Shaw (joeshaw) wrote :

Yikes! Those packages are a *prerelease* 0.2.14 version -- the code is buggy and I don't recommend installing them.

Kevin, can you please take those packages down or update them to the official 0.2.14 release?

Revision history for this message
murrayf (murrayf07) wrote : Re: beagled-helper and beagle run away with CPU and memory (SOLVED)

  I have noticed the same problem in beagle 0.2.16.3 running on ubuntu feisty, beagle-helper process loaded a lot of ram. But now I have found the solution:

   First, is necessary to enable extended atributes for your file systems (as beagle wiki says), to do that we add "user_xattr" in the options column of our /etc/fstab and then remount file systems or reboot computer...

  After that, and maybe the "key" of my problem (and hope yours too!) is to exclude the TEMP directory of ed2k files (amule, mldonkey, etc.) in beagle indexing preferences. Then cpu charge is normal.

Alberto.

:)

Revision history for this message
Joe Shaw (joeshaw) wrote :

murrayf: what is "ed2k"? Is this something beagle should be handling more gracefully?

Revision history for this message
murrayf (murrayf07) wrote :

Hello Joe,

Yes, you are right. This kind of files belong to temp directory of edonkey p2p network programs (emule, amule, mldonkey...), they are usually big temporary files of movies that you are downloading... and beagled indexer daemon can't handle easily (I think...)

Best Regards,

Alberto.

:)

Revision history for this message
Joe Shaw (joeshaw) wrote : Re: [Bug 69752] Re: beagled-helper and beagle run away with CPU and memory

Hi,

On 4/30/07, murrayf <email address hidden> wrote:
> Yes, you are right. This kind of files belong to temp directory of
> edonkey p2p network programs (emule, amule, mldonkey...), they are
> usually big temporary files of movies that you are downloading... and
> beagled indexer daemon can't handle easily (I think...)

Yeah, temp directories can be tricky. I'd be interested in seeing the
Beagle logs if you ran beagled with --debug and those directories
enabled, so I can see what the patterns are.

Joe

Revision history for this message
Chris Moore (dooglus) wrote :

I just saw the same crash while downloading an 85Mb .mp3 file using Azureus (bittorrent client):

strace -p on the active /usr/lib/beagle/IndexHelper.exe thread shows:

fstat64(31, {st_mode=S_IFREG|0644, st_size=86537920, ...}) = 0
_llseek(31, 13018790, [13018790], SEEK_SET) = 0
read(31, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 8192) = 8192

fstat64(31, {st_mode=S_IFREG|0644, st_size=86537920, ...}) = 0
_llseek(31, 13018791, [13018791], SEEK_SET) = 0
read(31, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 8192) = 8192

fstat64(31, {st_mode=S_IFREG|0644, st_size=86537920, ...}) = 0
_llseek(31, 13018792, [13018792], SEEK_SET) = 0
read(31, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 8192) = 8192

over and over. I stopped the strace after gathering a million or so lines of output, and nothing had changed. It was still incrementing the offet by one each time, and reading another 8k's worth of zero bytes.

I suppose that each time the torrent client writes to the file, it triggers yet another scan of the incomplete file as well.

Revision history for this message
Chris Moore (dooglus) wrote :

Incidentally, file descriptor 31 in the above is the incomplete .mp3 file itself.

Revision history for this message
Chris Moore (dooglus) wrote :

I raised this upstream and got this response:

  "Beagle switched to taglib-sharp (from entagged-sharp) which handles this case
   without any problem. To test, sync to svn trunk r3706."

Changed in beagle:
status: Unknown → Fix Released
Revision history for this message
Corin Royal Drummond (corinroyal) wrote :
Download full text (4.4 KiB)

It's happening to me, I'm also a constant Azureus user:

Here's my current beagle logfile:

20070824 00:40:17.2234 05784 Beagle INFO: Starting Beagle Daemon (version 0.2.16.3)
20070824 00:40:17.4797 05784 Beagle INFO: Running on Mono 1.2.3.1
20070824 00:40:17.4799 05784 Beagle INFO: Using sqlite version 3
20070824 00:40:17.4803 05784 Beagle INFO: Command Line: /usr/lib/beagle/BeagleDaemon.exe --replace --bg
20070824 00:40:17.4962 05784 Beagle WARN: Extended attributes are not supported on this filesystem. Performance will suffer as a result.
20070824 01:00:40.9765 05784 Beagle ERROR: Maximum inotify watch limit hit adding watch to /home/corin/Desktop/Warez/Linux Warez/install_flash_player_9_linux. Try adjusting /proc/sys/fs/inotify/max_user_watches
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
<email address hidden> has recurrences
kf...

Read more...

Revision history for this message
Joe Shaw (joeshaw) wrote :

Azeureus I believe is just broken in this respect, and as long as it continuously closes and reopens the same file, there's not much we can do about it on the Beagle side in terms of re-indexing the file.

I believe the next major version of Beagle (0.3.0) will solve the problem of excessive memory usage in this situation, though.

I would recommend adding your Azeureus download folder to the list of directories not to crawl from the Beagle UIs preferences (or the beagle-settings tool).

Revision history for this message
Joe Shaw (joeshaw) wrote :

BTW, the "foo has recurrences" is output from evolution-sharp; it's not output from Beagle.

Revision history for this message
Corin Royal Drummond (corinroyal) wrote :

Hey, thanks for the suggestion. I'll do that. I appreciate you taking the time.

----- Original Message ----
From: Joe Shaw <email address hidden>
To: <email address hidden>
Sent: Saturday, August 25, 2007 2:10:56 PM
Subject: [Bug 69752] Re: beagled-helper and beagle run away with CPU and memory

Azeureus I believe is just broken in this respect, and as long as it
continuously closes and reopens the same file, there's not much we can
do about it on the Beagle side in terms of re-indexing the file.

I believe the next major version of Beagle (0.3.0) will solve the
problem of excessive memory usage in this situation, though.

I would recommend adding your Azeureus download folder to the list of
directories not to crawl from the Beagle UIs preferences (or the beagle-
settings tool).

--
beagled-helper and beagle run away with CPU and memory
https://bugs.launchpad.net/bugs/69752
You received this bug notification because you are a direct subscriber
of the bug.

      ____________________________________________________________________________________
Fussy? Opinionated? Impossible to please? Perfect. Join Yahoo!'s user panel and lay it on us. http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7

Revision history for this message
Alessandro Tanasi (jekil) wrote :

i can confirm this bug with gutsy, 2 cpu at 100% and 2 giga of ram needed

Revision history for this message
Joe Shaw (joeshaw) wrote :

Alessandro: Can you send SIGUSR1 to the beagled process, SIGUSR2 to the beagled-helper process, and attach the last 100 lines of each of the ~/.beagle/Log/current-* files? The output from "ps ax | grep -i beagle" would also be helpful.

Revision history for this message
Jared Luxenberg (jluxenbe) wrote :

Joe:

I can also confirm this bug with Gutsy. One core of my dual core cpu is at 100%, and beagled is using over 1GB of virtual memory. It appears to be reindexing my thunderbird mail often...

I've attached the last 100 lines of the log files after sending SIGUSR1 to the beagled process (I don't have a beagled-helper process). The output from "ps ax | grep -i beagle" follows:

 7440 ? SNl 646:43 beagled /usr/lib/beagle/BeagleDaemon.exe --replace --bg

Revision history for this message
dBera (dbera-web) wrote :

Jared, Thunderbird Indexing is disabled in the beagle-0.2.18 release due to memory and CPU usage problems. Looks like it is enabled on your computer; maybe the ubuntu packager enables it. I suggest turning it off by doing this as user from the command line
$ beagle-config daemon DenyBackend Thunderbird

Revision history for this message
Panagiotis Issaris (t4k1s) wrote :

I can confirm this bug with Gutsy. It's using 850M (VIRT) or 600M (RES) RAM, while my machine only has 1G physical memory...
And it's heavily using the cpu, fluctuating between 60 and 100% usage...

top - 15:35:16 up 16 days, 4:07, 2 users, load average: 3.16, 2.75, 1.69
Tasks: 153 total, 3 running, 150 sleeping, 0 stopped, 0 zombie
Cpu(s): 1.0%us, 22.5%sy, 72.5%ni, 0.0%id, 3.7%wa, 0.0%hi, 0.3%si, 0.0%st
Mem: 1034480k total, 1021148k used, 13332k free, 113496k buffers
Swap: 3145720k total, 674168k used, 2471552k free, 50188k cached

  PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
24478 takis 24 7 854m 602m 3152 R 94.5 59.7 90:33.94 beagled
14408 takis 15 0 188m 50m 21m S 0.7 5.0 0:11.98 firefox-bin
  125 root 12 -5 0 0 0 D 0.3 0.0 2:08.59 kswapd0
    1 root 19 0 2948 232 180 S 0.0 0.0 0:01.83 init
    2 root 11 -5 0 0 0 S 0.0 0.0 0:00.00 kthreadd
    3 root 34 19 0 0 0 S 0.0 0.0 0:11.96 ksoftirqd/0
    4 root RT -5 0 0 0 S 0.0 0.0 0:00.00 watchdog/0
    5 root 18 -5 0 0 0 S 0.0 0.0 0:02.49 events/0

Revision history for this message
Panagiotis Issaris (t4k1s) wrote :

Furthermore, beagle-shutdown does not shut it down :-(

Is there an easy way to permanently disable beagle without uninstalling it?

Revision history for this message
Chris Moore (dooglus) wrote :

> Furthermore, beagle-shutdown does not shut it down :-(
>
> Is there an easy way to permanently disable beagle without uninstalling
> it?
>

You can set the search preferences to not index anything - that should help.

From the search window:
  Search > Preferences > Indexing
then uncheck 'index my home directory' and add folder path / to the list of
resources to exlude from indexing.

It's a shame this bug isn't getting any attention. Running the CPU flat out
leads to overheating and crashes on my laptop, causing data loss and
potentially hardware damage.

Revision history for this message
Joe Shaw (joeshaw) wrote :

> It's a shame this bug isn't getting any attention. Running the CPU flat out
> leads to overheating and crashes on my laptop, causing data loss and
> potentially hardware damage.

I don't think this is accurate. I say pretty clearly in an earlier comment [1] the info that we need to be able to diagnose the problem. Without log data, there's nothing we can do. I believe you when you say it uses 100% CPU -- but top output isn't helpful. We need help from bug reporters.

This has been ongoing work, and isn't as simple as fixing a one-liner and having the problem go away forever. Beagle is software which effectively has to be able to read and comprehend every piece of data on your system -- a difficult task and one with a lot of "surface area" and potential for failures. I'm not sure what version is in Gutsy, but 0.2.18 is better than ever with these and 0.3.0, which will be released soon, improves further.

Joe

[1] https://bugs.launchpad.net/ubuntu/+source/beagle/+bug/69752/comments/32

Revision history for this message
dBera (dbera-web) wrote :

Panagiotis, just in case if beagled is still running or if you happen to find this again, could you send the output of

$ beagle-index-info
$ beagle-status
$ ls -l ~/.beagle/Log/

In two terminals, do
$ tail -f ~/.beagle/Log/current-Beagle
$ tail -f ~/.beagle/Log/current-IndexHelper
(it will keep printing the debug messages, press ctrl-c to stop)
Then from another terminal,
$ kill -USR2 `pidof beagled`
(if pidof program is not installed, find the pid of beagled and use it)
This command will print something in the current-Beagle and current-IndexHelper log files. Paste the outputs of both.

Thanks. Chris, this bug _is_ getting attention. Read the previous responses from Joe - there has been several different causes for the same problem; many are fixed and for the rest, we need some diagnostic feedback to trace where the problem is. You should realize that these problems are not easy to reproduce.

Revision history for this message
Osmo Laitinen (osmo-laitinen) wrote :
Download full text (4.4 KiB)

I have this same problems with almost 100% CPU usage.

Last lines of current-Beagle file
20080106 12:05:17.8039 06414 Beagle WARN EX: Caught exception in DoTaskReal
20080106 12:05:17.8039 06414 Beagle WARN EX: Tag: /home/username/.mozilla-thunderbird/fyn4mgwx.default/ImapMail/mail.somedomain.com/INBOX.sbd/varasto.msf
20080106 12:05:17.8039 06414 Beagle WARN EX: Creator: /home/username/.mozilla-thunderbird/fyn4mgwx.default/ImapMail/mail.somedomain.com/INBOX.sbd/varasto.msf
20080106 12:05:17.8039 06414 Beagle WARN EX: Description: /home/username/.mozilla-thunderbird/fyn4mgwx.default/ImapMail/mail.somedomain.com/INBOX.sbd/varasto.msf
20080106 12:05:17.8039 06414 Beagle WARN EX: Priority: /home/username/.mozilla-thunderbird/fyn4mgwx.default/ImapMail/mail.somedomain.com/INBOX.sbd/varasto.msf ()
20080106 12:05:17.8039 06414 Beagle WARN EX: System.UriFormatException: Invalid URI: The hostname could not be parsed.
20080106 12:05:17.8039 06414 Beagle WARN EX: at System.Uri.Parse (System.String uriString) [0x00000]
20080106 12:05:17.8039 06414 Beagle WARN EX: at System.Uri.ParseUri () [0x00000]
20080106 12:05:17.8039 06414 Beagle WARN EX: at System.Uri..ctor (System.String uriString, Boolean dontEscape) [0x00000]
20080106 12:05:17.8039 06414 Beagle WARN EX: at System.Uri..ctor (System.String uriString) [0x00000]
20080106 12:05:17.8039 06414 Beagle WARN EX: at Beagle.Util.Thunderbird.NewUri (Beagle.Util.Account account, System.String mailbox, System.String id) [0x00000]
20080106 12:05:17.8039 06414 Beagle WARN EX: at Beagle.Util.Thunderbird+Mail..ctor (Beagle.Util.Account account, System.Collections.Hashtable data, System.String workfile) [0x00000]
20080106 12:05:17.8039 06414 Beagle WARN EX: at Beagle.Util.Thunderbird+Database+DatabaseEnumerator.get_Current () [0x00000]
20080106 12:05:17.8039 06414 Beagle WARN EX: at Beagle.Daemon.ThunderbirdQueryable.MailIndexableGenerator.HasNextIndexable () [0x00000]
20080106 12:05:17.8039 06414 Beagle WARN EX: at Beagle.Daemon.LuceneQueryable+AddGeneratorTask.DoTaskReal () [0x00000]
20080106 12:05:17.8039 06414 Beagle WARN EX: at Beagle.Util.Scheduler+Task.DoTask () [0x00000]

And last lines of current-IndexHelper file:

20080106 12:05:18.8091 06611 IndexH DEBUG: Generated 30 child indexables from file:///home/username/Desktop/Alice-2.0.0.tar.gz#Alice/Required/mp3/lib/ext/mp3plugin.jar (filtered with Beagle.Filters.FilterArchive)
20080106 12:05:18.8116 06611 IndexH DEBUG: +file:///home/username/Desktop/Alice-2.0.0.tar.gz#Alice/Required/tutorialWorlds/IceSkaterWorld.a2w
20080106 12:05:18.8181 06611 IndexH ERROR EX: Caught exception extracting data from archive /tmp/tmp4b3eb6dc.a2w
20080106 12:05:18.8181 06611 IndexH ERROR EX: ICSharpCode.SharpZipLib.Zip.ZipException: Data descriptor signature not found
20080106 12:05:18.8181 06611 IndexH ERROR EX: at ICSharpCode.SharpZipLib.Zip.ZipInputStream.ReadDataDescriptor () [0x00000]
20080106 12:05:18.8181 06611 IndexH ERROR EX: at ICSharpCode.SharpZipLib.Zip.ZipInputStream.BodyRead (System.Byte[] b, Int32 off, Int32 len) [0x00000]
20080106 12:05:18.8181 06611 IndexH ERROR EX: at (wrapper delegate-invoke) Sy...

Read more...

Revision history for this message
Osmo Laitinen (osmo-laitinen) wrote :

And while I was writing above post and configured beagle to ignore /tmp and tried to shut it down (with no success), these errors were logged:

20080106 12:05:17.8039 06414 Beagle WARN EX: at Beagle.Util.Scheduler+Task.DoTask () [0x00000]
20080106 13:22:06.7187 06414 Beagle DEBUG: Loading Beagle.Util.Conf+DaemonConfig from daemon.xml
20080106 13:22:06.7413 06414 Beagle ERROR EX: Could not load configuration from daemon.xml:
20080106 13:22:06.7413 06414 Beagle ERROR EX: System.IO.IOException: Sharing violation on path /home/username/.beagle/config/daemon.xml
20080106 13:22:06.7413 06414 Beagle ERROR EX: at System.IO.FileStream..ctor (System.String name, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, Boolean anonymous, FileOptions options) [0x00000]
20080106 13:22:06.7413 06414 Beagle ERROR EX: at System.IO.FileStream..ctor (System.String name, FileMode mode, FileAccess access, FileShare share) [0x00000]
20080106 13:22:06.7413 06414 Beagle ERROR EX: at (wrapper remoting-invoke-with-check) System.IO.FileStream:.ctor (string,System.IO.FileMode,System.IO.FileAccess,System.IO.FileShare)
20080106 13:22:06.7413 06414 Beagle ERROR EX: at System.IO.File.Open (System.String path, FileMode mode, FileAccess access, FileShare share) [0x00000]
20080106 13:22:06.7413 06414 Beagle ERROR EX: at Beagle.Util.Conf.LoadFile (System.Type type, Beagle.Util.Section current, Beagle.Util.Section& section, Boolean force) [0x00000]
20080106 13:22:07.3673 06414 Beagle DEBUG: Loading Beagle.Util.Conf+IndexingConfig from indexing.xml
20080106 13:22:07.3774 06414 Beagle DEBUG: Loading Beagle.Util.Conf+DaemonConfig from daemon.xml
20080106 13:22:07.3805 06414 Beagle DEBUG: Loading Beagle.Util.Conf+SearchingConfig from searching.xml
20080106 13:22:42.7952 06414 Beagle DEBUG: Caught ResponseMessageException: Socket was closed before any data could be read
20080106 13:22:42.7960 06414 Beagle DEBUG EX: Exception was unexpected.
20080106 13:22:42.7960 06414 Beagle DEBUG EX: Beagle.ResponseMessageException: Socket was closed before any data could be read
20080106 13:22:42.7975 06414 Beagle DEBUG: Launching helper process
20080106 13:22:42.8320 06414 Beagle DEBUG: IndexHelper PID is 6884
20080106 13:22:44.3332 06414 Beagle DEBUG: Found IndexHelper (6884) in 1.50s
20080106 13:25:19.6863 06414 Beagle INFO: Shutdown requested
20080106 13:25:19.6890 06414 Beagle DEBUG: CancelIfBlocking Beagle.Daemon.ConnectionHandler
20080106 13:25:19.6917 06414 Beagle DEBUG: Bailing out of HandleConnection -- shutdown requested
20080106 13:25:19.6941 06414 Beagle DEBUG: Stopping inotify threads
20080106 13:25:19.6978 06414 Beagle DEBUG: Server '/home/username/.beagle/socket' shut down
20080106 13:25:19.7011 06414 Beagle DEBUG: All workers have finished. Exiting main loop.
20080106 13:25:19.7066 06414 Beagle DEBUG: Joining thread 1 of 1: EHT 06570 [06414 BeagleDaemon] Beagle.Util.Scheduler:Worker

Revision history for this message
Osmo Laitinen (osmo-laitinen) wrote :

Ah, almost forgot: I use Ubuntu 7.10.

Revision history for this message
dBera (dbera-web) wrote :

Osmo, the mozilla-thunderbird errors were due to a faulty Thunderbird
backend which was actually disable upstream but strangely enabled in
ubuntu. That and the other errors were fixed in 0.3.0 which was
released a month ago. The ICSharpCode.SharpZipLib.Zip.ZipException is
not fatal, it just indicated a failure in indexing of a certain file,
probably due to a corrupt archive.

--
-----------------------------------------------------
Debajyoti Bera @ http://dtecht.blogspot.com
beagle / KDE fan
Mandriva / Inspiron-1100 user

Revision history for this message
Osmo Laitinen (osmo-laitinen) wrote :
Download full text (4.9 KiB)

:~/.beagle/Log$ beagle-index-info
Index information:
Name: Thunderbird
Count: 0
Crawling: False

Name: KMail
Count: 0
Crawling: False

Name: Files
Count: 1998
Crawling: True

Name: GaimLog
Count: 166
Crawling: False

Name: IndexingService
Count: 0
Crawling: False

Name: Tomboy
Count: 0
Crawling: False

Name: Labyrinth
Count: 0
Crawling: False

Name: Blam
Count: 0
Crawling: False

Name: Liferea
Count: 0
Crawling: False

Name: Akregator
Count: 0
Crawling: False

Name: KonquerorHistory
Count: 0
Crawling: False

Name: KonqBookmark
Count: 0
Crawling: False

Name: KNotes
Count: 0
Crawling: False

Name: KOrganizer
Count: 0
Crawling: False

Name: KAddressBook
Count: 0
Crawling: False

Name: Kopete
Count: 0
Crawling: False

Name: Konversation
Count: 0
Crawling: False

Name: applications
Count: 286
Crawling: False

Name: documentation
Count: 33962
Crawling: False

Every 5.0s: beagle-info --status Sun Jan 20 12:37:05 2008

Scheduler:
Count: 153
Status: Executing task
Delayed 0 (20/01/2008 11:46:41 AM)
Indexing files inside /home/username/bin/cee

Pending Tasks:
1 Maintenance 100 (20/01/2008 11:46:43 AM)
Final Flush for FileSystemIndex

2 Maintenance 0 (20/01/2008 11:43:18 AM)
Optimize ThunderbirdIndex

3 Maintenance 0 (20/01/2008 11:43:18 AM)
Optimize KMailIndex

4 Maintenance 0 (20/01/2008 11:43:26 AM)
Optimize GaimLogIndex

5 Maintenance 0 (20/01/2008 11:43:26 AM)
Optimize IndexingServiceIndex

6 Maintenance 0 (20/01/2008 11:43:26 AM)
Optimize TomboyIndex

7 Maintenance 0 (20/01/2008 11:43:26 AM)
Optimize LabyrinthIndex

8 Maintenance 0 (20/01/2008 11:43:26 AM)
Optimize BlamIndex

9 Maintenance 0 (20/01/2008 11:43:26 AM)
Optimize LifereaIndex

10 Maintenance 0 (20/01/2008 11:43:26 AM)
Optimize AkregatorIndex

11 Maintenance 0 (20/01/2008 11:43:26 AM)

Then I did
kill -USR2 6682

here is the logs:
 ~/.beagle/Log/current-IndexHelper:
20080120 12:35:19.0711 06682 IndexH WARN: Handling signal 12 (SIGUSR2)
20080120 12:35:19.1126 06682 IndexH WARN: Filtering status (48m35s ago): determining filter for file:///home/username/Desktop/Alice-2.0.0.tar.gz#Alice/Required/tutorialWorlds/IceSkaterWorld.a2w

~/.beagle/Log/current-Beagle
20080120 12:34:39.1548 06491 Beagle DEBUG: Handling signal 12 (SIGUSR2)
20080120 12:34:44.6505 06491 Beagle WARN: extra WorkerFinished called for System.Byte[]
20080120 12:34:51.0833 06491 Beagle WARN: extra WorkerFinished called for System.Byte[]
20080120 12:34:58.0137 06491 Beagle WARN: extra WorkerFinished called for System.Byte[]
20080120 12:35:04.3970 06491 Beagle WARN: extra WorkerFinished called for System.Byte[]
20080120 12:35:11.4224 06491 Beagle WARN: extra WorkerFinished called for System.Byte[]
20080120 12:35:17.4850 06491 Beagle WARN: extra WorkerFinished called for System.Byte[]
20080120 12:35:24.2323 06491 Beagle WARN: extra WorkerFinished called for System.Byte[]
20080120 12:35:30.2849 06491 Beagle WARN: extra WorkerFinished called for System.Byte[]
20080120 12:35:37.4669 06491 Beagle WARN: extra WorkerFinished called for System.Byte[]
20080120 12:35:44.3655 06491 Beagle WARN: extra WorkerFinished calle...

Read more...

Revision history for this message
dBera (dbera-web) wrote :

There seems to be some problem in indexing
20080120 12:35:19.1126 06682 IndexH WARN: Filtering status (48m35s ago): determining filter for file:///home/username/Desktop/Alice-2.0.0.tar.gz#Alice/Required/tutorialWorlds/IceSkaterWorld.a2w
(the process started 48m ago and not yet finished).
I downloaded the Alice tutorial files but could not reproduce this (in 0.2.18 which is in Kubuntu I believe nor in 0.3.x which is in hardy). Anyhow, the indexing of archives was redone in 0.3.0 and such problems would not happen in the 0.3.x series I believe.

Changed in beagle:
importance: Unknown → Medium
Revision history for this message
murrayf (murrayf07) wrote : Re: [Bug 69752] Re: beagled-helper and beagle run away with CPU and memory

Hi,

This bug was reported long time ago, maybe it is fixed now.

Thx.
On 16/09/10 14:23, Bug Watch Updater wrote:
> ** Changed in: beagle
> Importance: Unknown => Medium
>

Revision history for this message
Thomas Hotz (thotz-deactivatedaccount) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. As far as i now beagle development was stopped 2010. I will close this bug report.

Changed in beagle (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.