David,
If "nothing on port 8983 responds", your servlet container is
certainly the first thing that should be checked, because that is
what's listening on port 8983.
First, let's need to figure out what version of Jetty you're using
and how it is started -- which will lead you to the log files, if it
is producing any. When Jetty/Solr is running correctly, try fetching
any page from that host using "curl -I".
Example: here's what I see on my laptop, with Solr running inside Jetty
shaft:R curl -I http://localhost:8983/
HTTP/1.1 404 Not Found
Content-Type: text/html; charset=iso-8859-1
Content-Length: 1287
Server: Jetty(6.1.3)
From this, I know it's Jetty 6.1.3.
Next, how is Jetty being started? Where is its jetty.xml
configuration file? What does that file specify for RequestLog?
On my laptop, I'm manually starting it via "java -jar start.jar".
On my work hosts, "java -jar start.jar" is being run from daemontools
(unlikely in your case)
Or, Jetty can be invoked without the "start.jar" shortcut. That's
just the default way of starting Solr.
My point is that I can't predict how it's started on your machine.
You need to find out yourself.
On Linux:
- "ps -ef | grep java"
- look at that list, see which java process is the relevant one
- take the parent PID of that process and run "ps -p <value>" to see
what process started it
- repeat until you find the script or program that started Jetty, and
the path to jetty.xml
If the process actually was "java -jar start.jar", then look for an
"etc" subdir in the current working directory for that process.
HTH,
--Matt Kangas
(stepping in to help with what seems to be a panicked-newbie
question...)
On Jul 30, 2007, at 2:35 PM, David Whalen wrote:
Hi Yonik!
I'm glad to finally get to talk to you. We're all very impressed
with solr and when it's running it's really great.
We increased the heap size to 1500M and that didn't seem to help.
In fact, the crashes seem to occur more now than ever. We're
constantly restarting solr just to get a response.
I don't know enough to know where the log files are to answer
your question (again, I'm filling in for the guy that set us
up with all this). Can I ask for your patience so we can figure
this out?
Thanks!
Dave W
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Yonik Seeley
Sent: Monday, July 30, 2007 2:23 PM
To: solr-user@lucene.apache.org
Subject: Re: Please help! Solr 1.1 HTTP server stops responding
It may be related to the out-of-memory errors you were seeing.
severe errors like that should never be ignored.
Do you see any other warning or severe errors in your logs?
-Yonik
On 7/30/07, David Whalen <[EMAIL PROTECTED]> wrote:
Guys:
Can anyone help me? Things are getting serious at my company and
heads are going to roll.
I need to figure out why solr just suddenly stops
responding without
any warning.
DW
-----Original Message-----
From: David Whalen [mailto:[EMAIL PROTECTED]
Sent: Friday, July 27, 2007 10:49 AM
To: solr-user@lucene.apache.org
Subject: RE: Solr 1.1 HTTP server stops responding
We're using Jetty. I don't know what version though. To my
knowledge, Solr is the only thing running inside it.
Yes, we cannot get to the admin pages either. Nothing on port
8983 responds.
So maybe it's actually Jetty that's messing me up? How
can I make
sure of that?
Thanks for the help!
DW
-----Original Message-----
From: Otis Gospodnetic [mailto:[EMAIL PROTECTED]
Sent: Friday, July 27, 2007 10:40 AM
To: solr-user@lucene.apache.org
Subject: Re: Solr 1.1 HTTP server stops responding
Solr runs as a webapp (think .war file) inside a
servlet container
(e.g. Tomcat, Jetty, Resin...). It could be that the
servlet contan
itself has a bug that prevents it from responding
properly after a
while. If you have other webapps in the same container, do
they still
respond? Can you got to
*any* of Solr's "pages" (e.g. admin page)? Anything in
container or
Solr logs?
Otis
--
Lucene Consulting - http://lucene-consulting.com/
----- Original Message ----
From: David Whalen <[EMAIL PROTECTED]>
To: solr-user@lucene.apache.org
Sent: Friday, July 27, 2007 4:21:18 PM
Subject: RE: Solr 1.1 HTTP server stops responding
Hi Otis.
I'm filling-in for the guy that installed the software
for us (now
he's long gone), so I'm just getting familiar with all of
this. Can
you elaborate on what you mean?
DW
-----Original Message-----
From: Otis Gospodnetic [mailto:[EMAIL PROTECTED]
Sent: Friday, July 27, 2007 10:01 AM
To: solr-user@lucene.apache.org
Subject: Re: Solr 1.1 HTTP server stops responding
Hi David,
Have you ruled out your servlet container as the source
of this bug?
Otis
----- Original Message ----
From: David Whalen <[EMAIL PROTECTED]>
To: solr-user@lucene.apache.org
Sent: Friday, July 27, 2007 3:06:42 PM
Subject: Solr 1.1 HTTP server stops responding
Hi All.
We're running Solr 1.1 and we're seeing intermittent cases
where Solr
stops responding to HTTP requests. It seems like the
listener on port
8983 just doesn't respond.
We stop and restart Solr and everything works fine for a
few hours,
and then the problem returns. We can't seem to point to
any single
factor that would lead to this problem, and I'm hoping to
get some
hints on how to diagnose it.
Here's what I can tell you now, and I can provide more info by
request:
1) The query load (via /solr/select) isn't that high.
Maybe 20 or 30
requests per minute tops.
2) The insert load (via /solr/update) is very high. We
commit almost
500,000 documents per day. We also trim out the same
number however,
so the net number of documents should stay around 20 million.
3) We do see Out of Memory errors sometimes, especially
when making
facet queries (which we do most of the time).
We think solr is great, and we want to keep using it, but
the downtime
makes the product (and us) look bad, so we need to solve
this soon.
Thanks in advance for your help!
DW
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.476 / Virus Database: 269.10.22/922 - Release
Date: 7/27/2007 6:08 AM
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.476 / Virus Database: 269.10.22/922 - Release
Date: 7/27/2007 6:08 AM
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.476 / Virus Database: 269.10.22/922 - Release
Date: 7/27/2007 6:08 AM
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.476 / Virus Database: 269.10.25/926 - Release
Date: 7/29/2007 11:14 PM
--
Matt Kangas / [EMAIL PROTECTED]
