Make sure you're up to date. the ini file no longer has a log entry,
the log output location is in the log4j.xml file. If you unzip a newly
built zip file ('mvn' will build one for you) it should log to a file
in the logs/ folder.I've verified that c-l does not start over when restarted with the current code. It's possible there was a regression in the past that no one else noticed (including me). Can you retry with the latest code please? B. On Wed, Apr 14, 2010 at 12:00 PM, Manokaran K <[email protected]> wrote: > On Wed, Apr 14, 2010 at 4:15 PM, Manokaran K <[email protected]> wrote: > >> >> On Wed, Apr 14, 2010 at 3:58 PM, Sebastian Cohnen < >> [email protected]> wrote: >> >>> Hi, >>> >>> this is (of course) not to be expected. c-l uses the _chages API and >>> checkpointing (using the update sequence number) to figure out, if there is >>> something new to index - at least as far as I understood this. But since 0.5 >>> is not yet released, maybe you've found a bug :) Could you provide some more >>> information on your setup, used design document, c-l logs? >>> >>> >>> >> My setup consists of about 150K docs to demo a web app. I'll prune it to a >> much smaller number and give you the information. Any specific action you >> would want me to try? >> >> > Where's the c-l log file located? My c-l.ini file says couchdb-lucene.log > but there's no such file in my system! > > thanks, > mano >
