nerdyator / dataparksearch

Automatically exported from code.google.com/p/dataparksearch
GNU General Public License v2.0
0 stars 0 forks source link

SearchD gives internal server error #21

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Trying to get searchd to run we have performed the following.
1. searchd.conf is configured with defaults from dist file
2. In search.htm we have the following two dbaddr lines.
   a. DBaddr
mysql://user:pass@localhost/dpesarch/?socket=/var/lib/mysql/mysql.sock&dbmode=mu
lti&trackquery&stored=localhost
   b. DBaddr searchd://localhost/

All processes, including searchd, are running on the same machine. 

When we navigate to to the search homepage it is displayed, but when a
search is performed we receive an Internal Server Error (500).

We are using v4.51 (can't successfully run .52 or 53)

Any ideas or additional configuration necessary?

Original issue reported on code.google.com by Imlbr...@gmail.com on 1 Oct 2009 at 5:57

GoogleCodeExporter commented 9 years ago
Also, searchd.conf has the following line
DBAddr
mysql://user:pass@localhost/dpsearch/?socket=/var/lib/mysql/mysql.sock?dbmode=mu
lti&stored=localhost

Original comment by Imlbr...@gmail.com on 1 Oct 2009 at 6:00

GoogleCodeExporter commented 9 years ago
try to reconfigure with --enable-multidbaddr option to configure and rebuild
dataparksearch.

Why you can't run 4.52 and 4.53 ? Do you encounter any error with these 
versions ?

Original comment by dp.max...@gmail.com on 1 Oct 2009 at 6:53

GoogleCodeExporter commented 9 years ago
Thanks for the suggestion, I will try it and post the results. 

I submitted issue 20 for version 4.53. I don't fully recall why 4.52 didn't 
work, but
I vaguely remember that with a clean db 4.52 would not index any files, then we 
would
replace the w/4.51 and everything worked, no config changes just executables.

Original comment by Imlbr...@gmail.com on 1 Oct 2009 at 10:02

GoogleCodeExporter commented 9 years ago
Maxime, Upgrading from MySQL 5.0 to 5.3 solved this issue for us. Thanks for 
your help.

Original comment by Imlbr...@gmail.com on 28 Oct 2009 at 6:01

GoogleCodeExporter commented 9 years ago
Thank you for reporting.

Original comment by dp.max...@gmail.com on 28 Oct 2009 at 6:17