Hi,
Yesterday I finally found what was wrong, in AbstractIndexer the
IndexWriter, although it is created like this:
IndexWriter writer = new IndexWriter(index.getAbsolutePath(),
new StandardAnalyzer(), create);
With a absolute path to where the index is to be, also needs to write
into where ever java.io.tmpdir is, and in my case it couldn't :(
Well now my searching works and I'm happy! By the way, thanks for a good
thread on searching and to Solprovider for all the help!
//Marc
> -----Oprindelig meddelelse-----
> Fra: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sendt: 22. juni 2005 09:59
> Til: [email protected]
> Emne: Re: Lucene: problem while crawling
>
> On 6/22/05, Marc Steven Pekilidi - TELMORE <[EMAIL PROTECTED]> wrote:
> > I think it might be a problem with the indexing, looking at
> the lucene.log I see a:
> > ERROR index.AbstractIndexer -
> java.io.IOException: Permission denied
>
> And THAT is why I included instructions for log4j.properties.
> Logs are just too useful.
>
> > My question is, where does AbstractIndexer try to write? I
> would think from lucene-live.xconf that it was here:
> > <index-dir src="../../work/search/lucene/index/live/index"/>
> >
> > However, if I remove the index dir I can see this in the lucene.log:
> > WARN index.AbstractIndexer - Directory
> has been created: (absolute
> path)../../work/search/lucene/index/live/index
> > ERROR index.AbstractIndexer -
> java.io.IOException: Permission denied
> >
> > I'm not a FreeBSD expert but I would think that if
> AbstractIndexer is able to create a directory (and it is!) it
> should be able to write to it. Can anyone offer an explanation?
> >
> > Marc
>
> The only places the indexer writes are the index directory
> and lucene.log. Obviously lucene.log is being written, so:
>
> 1. Did you shutdown Lenya before indexing? Even MSWindows
> with its "never heard of security" had problems writing the
> index while Lenya was running.
>
> 2. Check the permissions on the newly created directory. Is
> the user:group set correctly?
>
> 3. The error is generic; it is likely a "read" issue rather
> than a "write" issue. Does the user running the indexer have
> permission to read all of the content files? Or maybe it is
> the configuration files? Check permissions for
> configuration2xslt.xsl, lucene-live.xconf, and lenyadocs.xconf.
>
> solprovider
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED] For
> additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
