On 7/25/2013 8:21 AM, Brian Robinson wrote:
The sentence on the admin page just tells me to check the logs, but I
don't appear to have any yet. Those are located in
solr/collection1/data/tlog/, right?
Those are transaction logs - for durability in the face of failure and
for the real-time get handler. If you are using Solr 4.3.0 or later,
especially using the example jetty container (start.jar), the logs
should be in logs/solr.log, relative to the current working directory
where Solr was started. This location is dictated by log4j.properties.
If you have an earlier version or a more custom setup, the log
location could be highly variable.
The admin UI should have a logging section that will show you everything
in the log that's at least WARN severity. Often this isn't enough, and
you need the actual logfile.
The only browser I appear to be able to use in my SSH (my only access to
the server) is Lynx, so this response isn't formatted, unfortunately,
but this is what I get. I tried to find a sample response so I could
compare and parse out the useful information, but no luck. It looks like
there is only the one core, though. I don't see anything that looks like
an init failure.
The lynx browser isn't going to work for the admin UI. The links
(elinks on some systems) browser will display some things, but it
doesn't work either. The UI is pretty much all javascript, and you need
a full graphical browser for that to function properly.
SSH clients (including putty) will let you do port forwarding. Set it
up to forward a local port (like 8983, but you can use what you want) to
the remote port that Solr uses. Then in your local browser, go to
http://localhost:8983/solr (or whatever port you chose) and the UI
should work.
that error indicates that your solr client sent a document to some (valid
and functioning) SolrCore which has a schema.xml that does not contain a
field named "brand".
So it could be that I just updated the wrong schema.xml. But if
/etc/solr/ is my solr home directory, then /etc/solr/collection1/conf/
would be the right location, right?
If you aren't using SolrCloud, and your core is named 'collection1',
then that should be the right schema. You must reload the core, or more
ideally completely restart Solr, after changing the schema.
Thanks,
Shawn
