beagled dies trying to watch ~/.beagle/config

Bug #1035 reported by Joe Barnett
4
Affects Status Importance Assigned to Milestone
mono (Ubuntu)
Fix Released
Medium
Brandon Hale

Bug Description

after starting beagled, it exits quickly, with this in the logs:

$ beagled --fg
INFO: Starting Beagle Daemon (version 0.0.11)
DEBUG: Command Line: /usr/lib/beagle/BeagleDaemon.exe --fg
DEBUG: Starting main loop
DEBUG: Starting messaging server
DEBUG: Starting QueryDriver
DEBUG: worker added: name=server 'socket' refc...

after starting beagled, it exits quickly, with this in the logs:

$ beagled --fg
INFO: Starting Beagle Daemon (version 0.0.11)
DEBUG: Command Line: /usr/lib/beagle/BeagleDaemon.exe --fg
DEBUG: Starting main loop
DEBUG: Starting messaging server
DEBUG: Starting QueryDriver
DEBUG: worker added: name=server 'socket' refcount=1
DEBUG: Found index helper at /usr/lib/beagle/beagled-index-helper
DEBUG: Starting Inotify Backend
DEBUG: Pre-populated UniqueIdStore cache with 8348 items in .31s
INFO: Loaded 351 records from /home/jbarnett/.beagle/FileSystemIndex/FileAttributesStore.db in 0.008s
INFO: Loaded 141 records from /home/jbarnett/.beagle/LauncherIndex/FileAttributesStore.db in 0.002s
DEBUG: Found 11 types in BeagleDaemonLib, Version=1.4.3.3, Culture=neutral
INFO: FileSystemQueryable start-up thread finished
INFO: Starting Evolution mail backend
INFO: Starting launcher backend
INFO: Scanning Launchers
INFO: Starting Evolution mail backend
INFO: Starting Gaim log backend
DEBUG: Starting mail crawl
INFO: Found 343 Launchers in .00s
INFO: Launcher backend worker thread done in 2.56s
WARN: Could not open Evolution addressbook. Addressbook searching is disabled.
DEBUG: System.DllNotFoundException: libebook-1.2.so.0
in (wrapper managed-to-native) Evolution.Book:e_book_new_system_addressbook (intptr&)
in <0x00016> Evolution.Book:NewSystemAddressbook ()
in <0x00024> Beagle.Daemon.EvolutionDataServerQueryable.EvolutionDataServerQueryable:Start ()
DEBUG: Starting Scheduler thread
INFO: Scanning Tomboy notes...
INFO: Scanned 1 notes in .03s
DEBUG: Starting Inotify threads
This Computer Hostname: leafy
DEBUG: Starting WebBackEnd
DEBUG: Starting task note://tomboy/e6bde763-286c-40b0-b4ed-f994123130fb
DEBUG: Finished task note://tomboy/e6bde763-286c-40b0-b4ed-f994123130fb in .03s
INFO: Starting WebServiceBackEnd
DEBUG: Global WebAccess Disabled
DEBUG: Adding root /home/jbarnett
DEBUG: Caught SocketException -- we probably need to launch a helper: Connection refused
DEBUG: Launching helper process
INFO: Scanning Weblogs
INFO: Found 352 items in 12 weblogs in .08s
INFO: Gaim log backend worker thread done in 3.41s
DEBUG: Mail crawl finished
INFO: Evolution mail driver worker thread done in 5.73s
ERROR: Caught exception in post_hook 'Beagle.Util.Scheduler+Hook'
ERROR: System.Exception: Couldn't launch helper process
in <0x00144> Beagle.Daemon.RemoteIndexer:LaunchHelper ()
in <0x002e4> Beagle.Daemon.RemoteIndexer:SendRequest (Beagle.Daemon.RemoteIndexerRequest request)
in <0x00070> Beagle.Daemon.RemoteIndexer:Flush ()
in <0x00017> Beagle.Daemon.LuceneQueryable+LuceneTaskCollector:PostTaskHook ()
in (wrapper delegate-invoke) System.MulticastDelegate:invoke_void ()
in <0x00b80> Beagle.Util.Scheduler:Worker ()
DEBUG: Starting messaging server
DEBUG: worker added: name=server 'socket-helper' refcount=1
DEBUG: Helper Size: VmRSS=9.7 MB, size=1.00, 0.0%
DEBUG: worker added: name=HandleConnection (1) refcount=1
ioctl: No space left on device
ioctl: No space left on device
ioctl: No space left on device
ioctl: No space left on device
     (repeats a LOT!)
ioctl: No space left on device
ioctl: No space left on device
DEBUG: Helper Size: VmRSS=9.8 MB, size=1.01, 0.3%
DEBUG: Scanned 8348 subdirs in 8.96s
ioctl: No space left on device

Unhandled Exception: System.IO.IOException: Attempt to watch /home/jbarnett/.beagle/config failed!
in <0x0026c> Beagle.Util.Inotify:Subscribe (string,Beagle.Util.Inotify/InotifyCallback,Beagle.Util.Inotify/EventType,Beagle.Util.Inotify/EventType)
in <0x00012> Beagle.Util.Inotify:Subscribe (string,Beagle.Util.Inotify/InotifyCallback,Beagle.Util.Inotify/EventType)
in <0x00057> Beagle.Util.Conf:WatchForUpdates ()
in <0x00182> Beagle.Daemon.BeagleDaemon:StartupProcess ()
in <0x00048> (wrapper delegate-invoke) System.MulticastDelegate:invoke_bool ()
in <0x0002a> IdleProxy:Handler ()
in <0x00036> (wrapper native-to-managed) IdleProxy:Handler ()
in (unmanaged) 0xb7f5c7ef
in <0x00004> (wrapper managed-to-native) Gtk.Application:gtk_main ()
in <0x00007> Gtk.Application:Run ()
in <0x0052e> Beagle.Daemon.BeagleDaemon:Main (string[])

DEBUG: The daemon appears to have gone away.
DEBUG: Shutting down helper.
DEBUG: Calling BeginShutdown
DEBUG: Beginning shutdown event
DEBUG: Done with shutdown event
DEBUG: (1) Waiting for 1 worker...
DEBUG: waiting for server 'socket-helper'
DEBUG: worker removed: name=server 'socket-helper'
INFO: Exiting
DEBUG: Server 'socket-helper' shut down

I did not get this problem with beagle 0.10

Brandon Hale (brandon)
Changed in mono:
assignee: nobody → brandon
Revision history for this message
Brandon Hale (brandon) wrote :

Is this bug still valid?

Revision history for this message
Joe Barnett (thejoe) wrote :

seems to get past this point with 0.12

Brandon Hale (brandon)
Changed in mono:
status: New → Fixed
Revision history for this message
Jean-Christophe Baptiste (jc-baptiste) wrote :

I am having this problem under dapper :

- whether I install Beagle from the package repository or from the source ;
- whether I use Mono in the package repository or in the latest version (CVS)
- gtk-sharp is present and from the repository

I get this kind of message when I try to start beagle-search (it seems that the daemon "beagled" is correctly up) or when I try to compile the beagle CVS.

<<<
stenka@ubuntu:~$ beagle-search

** (/usr/lib/beagle/Search.exe:18000): WARNING **: The following assembly referenced from /usr/lib/beagle/Search.exe could not be loaded:
Assembly: gtk-sharp (assemblyref_index=0)
Version: 2.8.0.0
Public Key: 35e10195dab3c99f
The assembly was not found in the Global Assembly Cache, a path listed in the MONO_PATH environment variable, or in the location of the executing assembly (/usr/lib/beagle).

================================================== ===============
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
================================================== ===============

Stacktrace:

Native stacktrace:

beagle-search(mono_handle_native_sigsegv+0xbb) [0x8153d0b]
beagle-search [0x813e66f]
[0xffffe440]
beagle-search(mono_assembly_load_reference+0x11e) [0x809fd6e]
beagle-search(mono_class_from_typeref+0x164) [0x8089c44]
beagle-search(mono_class_get+0xef) [0x809139f]
beagle-search(mono_class_get_full+0x21) [0x8091411]
beagle-search [0x808fca5]
beagle-search(mono_class_get+0x11c) [0x80913cc]
beagle-search [0x80bfb0a]
beagle-search(mono_get_method_full+0x60) [0x80bfbd0]
beagle-search(mono_get_method+0x27) [0x80bfb67]
beagle-search(mono_jit_exec+0x42) [0x805c552]
beagle-search(strftime+0x1ba2) [0x805c602]
beagle-search(mono_main+0x857) [0x805cfe7]
beagle-search(__fxstat64+0x12b) [0x805b9bb]
/lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xd2) [0xb7cfcea2]
beagle-search(sinh+0x41) [0x805b911]
Abandon
>>>

Please help me, I really enjoyed Beagle and want to use it again !

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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