After browsing the roller code I found a way to get the search index to completely rebuild on roller startup.
Stop Roller remove the contents of your lucene search directory create the file ".index-inconsistent" in the lucene search directory Start Roller On Fri, Jun 22, 2007 at 09:28:28AM -0500, Glenn Nielsen wrote: > Here are the only lines I found regarding search in my roller log > with DEBUG enabled. > > INFO 2007-06-22 09:24:25,878 IndexManagerImpl:<init> - search enabled: true > INFO 2007-06-22 09:24:30,349 SearchServlet:init - Initializing SearchServlet > > Once again only a 20 byte "segments" file was created in the lucene > search directory. > > Regards, > > Glenn > > On Fri, Jun 22, 2007 at 09:21:28AM -0500, Glenn Nielsen wrote: > > On Fri, Jun 22, 2007 at 09:41:07AM -0400, Dave wrote: > > > Hi Glen, > > > > > > It's hard to diagnose problems without any error messages. Could you > > > try turning up the logging on the search subsystem. You should be able > > > to do that by adding a line to WEB-INF/classes/log4j.properties like > > > so: > > > > > > log4j.category.org.apache.roller.business.search=DEBUG > > > > I have done this with DEBUG logging and saw no messages regarding > > rebuilding the search indexes during startup after having deleted > > everything in the lucene search directory. > > > > I did see log entries when I rebuilt the search index for an individual > > blog using the blog admin online interface. > > > > I will give it another shot just in case I missed something. > > > > > Then stop Roller, delete your logs and restart. You should be able to > > > better see what is happening with search. Any clues there? > > > > Just to be clear. There is no other way to rebuild the search index > > for all blogs than stop roller, delete the contents of the lucene > > search directory, then restart roller? > > > > Thanks, > > > > Glenn Glenn
