please check if 1) ur dir to store indexes (indexes dir ) is properly set in the local.ini config file 2) ownership of that indexes dir set to couchdb user recursively eg: chown -R couchdb:couchdb <indexesdir> 3) permissions of that indexes dir set appropriately eg: chmod -R 0770 <indexesdir> restart couchdb and check now.
HTH Krishna ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ On Thu, Mar 4, 2010 at 9:14 AM, Michael McCaffrey <[email protected]>wrote: > Something's happened with my couchdb lucene implementation and I can't > get couch to start unless I comment out the indexer in the ini file. > > I'm getting java heap errors. > > I've tried cleaning out my indices folder but to no avail. > > Don't know what happened, it was working fine, I made a change to a > database record to test a lucene query and it hung up. Had to kill the > couch session and now it won't restart. > > Any ideas? > > Thanks > > > 1> 2010-03-03 17:07:52,027 [couchdb-lucene] WARN Forcibly unlocking > locked index at startup. > [info] [<0.62.0>] 127.0.0.1 - - 'GET' /_all_dbs 200 > 1> [info] [<0.62.0>] 127.0.0.1 - - 'GET' > /test/_all_docs?startkey=%22_design%22&endkey=%22_desig > 1> [info] [<0.62.0>] 127.0.0.1 - - 'GET' /test 200 > 1> [info] [<0.62.0>] 127.0.0.1 - - 'GET' > /test/_all_docs_by_seq?startkey=0&limit=250&include_doc > 1> Exception in thread "main" java.lang.OutOfMemoryError: Java heap > space > [error] [<0.52.0>] OS Process died with status: 0 > >
