Perhaps the expanded version of the war was not correctly updated and
it was picking up the old definitions. Weird things happen. Glad to
hear it is not Solr itself.
Regards,
Alex.
Personal: http://www.outerthoughts.com/ and @arafalov
Solr resources and newsletter: http://www.solr-start.com/ an
don't ask, but I've deleted the webapp and re-deployed it in Tomcat and
everything is working now...
Thanks for the input!
Regards,
Stefan
Am 04.12.2014 um 19:53 schrieb Stefan Moises:
Hi,
yeah, that's the strange thing admin UI, /select-URLs etc. are
working fine... just the REST relate
Hi,
yeah, that's the strange thing admin UI, /select-URLs etc. are
working fine... just the REST related URLs give me 404 errors... :(
I'll double check if it's the correct Solr instance, but I'm pretty sure
it is since the requested core is only running on this instance.
Regards,
Stefan
The other options is that you not running your - expected - Solr on
that port but are running a different instance. I found that when I
use the new background scripts, I keep forgetting I have another Solr
running.
Regards,
Alex.
Personal: http://www.outerthoughts.com/ and @arafalov
Solr resour
Does Admin UI works? Because that API end-points is called by the
Admin UI (forgot which screen though).
Regards,
Alex.
Personal: http://www.outerthoughts.com/ and @arafalov
Solr resources and newsletter: http://www.solr-start.com/ and @solrstart
Solr popularizers community: https://www.linkedi
Oh no, now *I* have that same problem again... :(
I have copied my (running) schemaless core to another server, the core
runs schemaless (managed-schema is created etc.), solrconfig.xml and
web.xml are identical besides the paths on the server ...
And yet on one Tomcat (7.0.28) the URL
/solr/s
Perfect - the web.xml configuration was exactly what was missing.
Thanks so much! ;)
--
View this message in context:
http://lucene.472066.n3.nabble.com/Schemaless-configuration-using-4-10-2-API-returning-404-tp4167869p4171932.html
Sent from the Solr - User mailing list archive at Nabble.com.
Hi,
I've had the same problem - double-check your web.xml and make sure, all
the required REST stuff is in there, that is:
...
SolrRestApi
org.restlet.ext.servlet.ServerServlet
org.restlet.application
org.apache.solr.rest.SolrSchemaRestApi
SolrConfigRestApi
org
I have some level of logging in Tomcat, and I can see that SolrDispatchFilter
is being invoked:
2014-11-06 17:23:19,016 [catalina-exec-3] DEBUG SolrDispatchFilter
- Closing out SolrRequest: {}
But that really isn't terribly helpful. Is there more logging that I could
invoke to get more
Ok, I just booted fresh solr 4.10.2, started example-schemaless and
hit http://localhost:8983/solr/collection1/schema/fields - and it
worked.
So, I suspect the problem is not with Solr but with your setup around
it. For example, is your Solr listening on port 9943 directly (and not
8983) or do you
Thanks for the reply!
My Solr has 2 cores(collection1/collection2), I can access them via the Solr
dashboard with no problem.
https://myserver:9943/solr/#/collection1
https://myserver:9943/solr/#/collection2
I can also verify the solrconfig.xml for them contain the schemaless config:
https://myse
Hi,
it might be a silly question, but are you sure that a Solr core
"collection1" exists? Or does it have a different name?
At least you would get a 404 if no such core exists.
Regards,
Andreas
nbosecker wrote on 11/05/2014 09:12 PM:
Hi all,
I'm working on updating legacy Solr to 4.10.2 to
12 matches
Mail list logo
