You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Michael Glasson <mg...@netspeed.com.au> on 2018/07/17 21:16:40 UTC
File not found error starting Solr 7.4.0 on Windows
Has anyone seen this one?
F:\Users\user\Downloads\solr-7.4.0>bin\solr.cmd start
ERROR StatusLogger Unable to access
file:/F:/Users/user/Downloads/solr-7.4.0/server/file:F:/Users/user/Downloads
/solr-7.4.0/server/resources/log4j2.xml
java.io.FileNotFoundException: F:\Users\user
\Downloads\solr-7.4.0\server\file:F:\Users\user\Downloads\solr-7.4.0\server\
resources\log4j2.xml (The filename, directory name, or volume label syntax
is incorrect)
I have reproduced it on two computers and with Solr in a couple of different
paths. The error does not occur with Solr 6.6.5.
My guess is that there is a doubling up of a file path construction
parameter - maybe in Jetty?
Re: File not found error starting Solr 7.4.0 on Windows
Posted by Erick Erickson <er...@gmail.com>.
I'm pretty sure this was fixed by SOLR-12549. It's a bit confused
though because the JIRA system managed to mess up the original JIRA
SOLR-12008.
We think it's related to switching to Logj2.
There are a copule of options:
1> if you could pull down a current 7x version of Solr (the future
Solr 7.5), compile and try that it'd help us be sure it's really
fixed.
2> change the instances of 'file:%EXAMPLE_DIR%\resources\log4j2.xml" '
to 'file:///%EXAMPLE_DIR%\resources\log4j2.xml" '
Best,
Erick
On Tue, Jul 17, 2018 at 2:16 PM, Michael Glasson <mg...@netspeed.com.au> wrote:
> Has anyone seen this one?
>
>
>
> F:\Users\user\Downloads\solr-7.4.0>bin\solr.cmd start
>
> ERROR StatusLogger Unable to access
> file:/F:/Users/user/Downloads/solr-7.4.0/server/file:F:/Users/user/Downloads
> /solr-7.4.0/server/resources/log4j2.xml
>
> java.io.FileNotFoundException: F:\Users\user
> \Downloads\solr-7.4.0\server\file:F:\Users\user\Downloads\solr-7.4.0\server\
> resources\log4j2.xml (The filename, directory name, or volume label syntax
> is incorrect)
>
>
>
> I have reproduced it on two computers and with Solr in a couple of different
> paths. The error does not occur with Solr 6.6.5.
>
>
>
> My guess is that there is a doubling up of a file path construction
> parameter - maybe in Jetty?
>
>
>
>
>