Page 1 of 1
Search appears to be broken [Resolved]

Posted:
Sun Jan 01, 2012 4:14 am
by Mr. Odd
Setup: Ubuntu 11.10, plenty of CPU and memory. Installation works fine - I can find everything from the library directly. Search, however, doesn't return anything for any entry. I've got into the control panel and forced an index rebuild but still nothing. Any suggestions?
Re: Search appears to be broken

Posted:
Sun Jan 01, 2012 5:07 am
by BKKKPewsey
Mr. Odd wrote:I've got into the control panel and forced an index rebuild but still nothing.
I thought search update was done via settings/search - update search index
So what control panel are you referring to?
Does the log show any errors?
Re: Search appears to be broken

Posted:
Sun Jan 01, 2012 8:47 am
by Mr. Odd
I'm referring to the Subsonic settings page (just habit calling it the 'control panel').
No errors in the log.
Re: Search appears to be broken

Posted:
Sun Jan 01, 2012 5:09 pm
by BKKKPewsey
Mr. Odd wrote:No errors in the log.
Is there anything in log to show search index being created?
Last few lines should look like
- Code: Select all
[01/01/12 06:17:23 GMT] INFO SearchService Created search index with 80000 entries.
[01/01/12 06:17:34 GMT] INFO SearchService Created search index with 81000 entries.
[01/01/12 06:17:50 GMT] INFO SearchService Updating Lucene search index.
[01/01/12 06:18:12 GMT] INFO SearchService Created search index with 81521 entries.

Re: Search appears to be broken

Posted:
Sun Jan 01, 2012 6:06 pm
by Mr. Odd
No, actually. The last line is:
[1/1/12 3:43:53 AM EST] INFO SearchService Created search index with 62000 entries
With no further entries. Any ideas why?
Re: Search appears to be broken

Posted:
Sun Jan 01, 2012 6:48 pm
by BKKKPewsey
It looks like the search indexer is stopping before updating the Lucene database.
Check your java memory allocation and possibly up it.
You could also try deleting the sub-directories in the subsonic\lucene directories and re-building index (may have a corrupt db there)
Re: Search appears to be broken

Posted:
Sun Jan 01, 2012 8:14 pm
by Mr. Odd
Yup, it was the java memory allocation. I doubled it and all's well. Thanks!