Bug 114973

Summary:	Beagle doesn't search
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Bryan Perry <bperry>
Component:	Other	Assignee:	E-mail List <gnome-bugs>
Status:	RESOLVED INVALID	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None
Version:	Beta 4
Target Milestone:	---
Hardware:	x86
OS:	SUSE Other
Whiteboard:
Found By:	System Test	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	Beagle Log folder

Description Bryan Perry 2005-09-02 14:24:27 UTC

When attempting a beagle search for anything at all, I get the message:

The query for resolv failed.
The likely cause is that the beagle daemon isn't running.
Click to start the Beagle daemon...

Clicking the link appears to do nothing. using ps to find and kill the best
process does kill the taskbar icon, and running best from the CLI starts the
taskbar icon back up and gives the message:

# best
Rendering
Done Rendering: .95s
If you're wondering whether Best is working check your notification area (system
tray)

At this point, I can try another search and get the same message as before only
now, since best was started in a terminal window I get a never-ending loop of
delayed query messages that multiply for each additional search I try to
perform. The messages that keep scrolling are:

SetSource:
** (best:20997): WARNING **: _wapi_connect: Need to translate 2 [No such file or
directory] into winsock error
Rendering
Done Rendering: .06s
Delayed query fired

This is a clean install of beta 4, and I have never gotten beagle to run
successfully.

Comment 1 JP Rosevear 2005-09-05 01:39:46 UTC

This is somewhat reminiscent of bug 115186.

Comment 2 JP Rosevear 2005-09-05 17:35:16 UTC

I had problems in beta4 as well, but the update for RC1 seemed to clear them up.
 Comments beagle guys?

Comment 3 Joe Shaw 2005-09-07 15:13:36 UTC

We'd need to see the files in ~/.beagle/Log to know why the beagle daemon didn't
start.

Comment 4 Bryan Perry 2005-09-07 15:24:43 UTC

~/.beagle/Log does not exist. I only have ~/.beagle/config but it is empty.

Comment 5 Joe Shaw 2005-09-07 15:30:46 UTC

If you run "beagled --fg --debug" from the command-line, what do you get?

Comment 6 Bryan Perry 2005-09-07 15:42:11 UTC

Created attachment 49081 [details]
Beagle Log folder

Beagle Log folder

Comment 7 Bryan Perry 2005-09-07 15:43:45 UTC

Looks like the missing Log folder was because I was logged in as root. Switching
to a non-privileged user I have a Log folder and have attached the contents.
When I search as a non-privileged user, I still get no results.

Comment 8 Bryan Perry 2005-09-07 15:45:20 UTC

bryan@linux00c04f2293fa:~> beagled --fg --debug
INFO: Starting Beagle Daemon (version 0.0.13.2)
DEBUG: Command Line: /usr/lib/beagle/BeagleDaemon.exe --fg --debug
DEBUG: Starting main loop
DEBUG: Starting messaging server
FATAL: Could not set up the listener for beagle requests.  There is probably
another beagled instance running.  Use --replace to replace the running service
bryan@linux00c04f2293fa:~> ps -eaf|grep beagled
bryan     4707     1  1 15:37 ?        00:00:06 mono-beagled --debug
/usr/lib/beagle/BeagleDaemon.exe --bg --autostarted
bryan     5229  4707  0 15:44 ?        00:00:01 mono-beagled-helper --debug
/usr/lib/beagle/IndexHelper.exe
bryan     5355  5090  0 15:47 pts/1    00:00:00 grep beagled
bryan@linux00c04f2293fa:~>

Comment 9 Joe Shaw 2005-09-07 15:50:32 UTC

Ok, closing.  Beagle refuses to run as root, and it started up correctly as a
regular user.

The lack of results is because it just started and hasn't crawled your data yet.