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 Jack L <jl...@yahoo.ca> on 2007/06/16 00:08:35 UTC
Re[6]: Where are the log files...
Hello Chris,
Yes, I do see the logs printed to the console. Since it's a unix
box, I then close the terminal after starting up solr. When a problem
happens, such as that solr no longer responds, I hope to be able to
to check the log files to see what happened.
It's probably a Java logger setting problem. I just saw Brian's reply.
I'll give that a try.
--
Best regards,
Jack
Friday, June 15, 2007, 1:43:51 PM, you wrote:
> : Also, the jetty log only logs web server activities, not solr
> : activities. Is there a way to configure solr to log to a file?
> Solr logs LogRecords to a Java Logging Logger -- the servlet container
> controls where those LogRecords go.
> I'm really not sure how you are running Jety, but when i go to the stock
> "example" directory that comes with Solr 1.2, and type "java -jar
> start.jar" I see all of the Solr log messages written to my console via
> Jetty's STDERR ... if you leave the jetty.xml file alone, and run jetty in
> the same way (java -jar start.jar), do you see the Solr log messages?
> if not, then i'm not sure what is going on.
> if you do: then how is this differnet from what you've been doing where
> you don't get any messages? (i'm not a jetty expert, i can't give you any
> particular advice on log configuration in jetty, i just know that the
> sample jetty configs we've got log everything to STDERR)
> -Hoss
Re[6]: Where are the log files...
Posted by Chris Hostetter <ho...@fucit.org>.
: Yes, I do see the logs printed to the console. Since it's a unix
: box, I then close the terminal after starting up solr. When a problem
: happens, such as that solr no longer responds, I hope to be able to
: to check the log files to see what happened.
ah ... okay, i understand where you are coming from. at a minimum i would
change your "startup" methodology to include redirecting stderr/stdour to
afile so you don't completley lose the console when closing the terminal
used to start the process. but in general i would look into how to
configure java standard logging of webapps in Jetty .. the settings you
found in the jetty.xml probably only relate to logging from the core Jetty
classes.
: It's probably a Java logger setting problem. I just saw Brian's reply.
: I'll give that a try.
his suggestions looked like they make sense for standalone java apps, but
when running in a servlet container it may not always work -- the servlet
container is totally within it's purview to do things that may prevent
techniques like that from working. breifly skimming this webpage leads me
to believe Jetty won't interfeer with any JDK logging properties you may
choose to set, so it would probably work fine.
http://jetty.mortbay.org/jetty5/tut/logging.html
-Hoss