Re: [jetty-users] Jetty is failing to start: Unable to reach node goal:

[Shawn Heisey <eclipse@xxxxxxxxxxxx>]

On 3/24/2016 12:20 PM, Steven White wrote:
> This maybe a question I need to ask on the Solr mailing list, but let me
> try here first.
> 
> Every now and then, I see the following error in solr.log file, any idea
> what maybe causing it (this is all that there is in the log):
> 
>     INFO  - 2016-03-24 11:05:30.130; [   ]
> org.eclipse.jetty.util.log.Log; Logging initialized @564ms
> <https://ccm-risk.ottawa.ibm.com:9453/ccm/users/564ms>
>     INFO  - 2016-03-24 11:05:30.382; [   ]
> org.eclipse.jetty.server.Server; jetty-9.2.10.v20150310
>     WARN  - 2016-03-24 11:05:30.406; [   ]
> org.eclipse.jetty.server.handler.RequestLogHandler; !RequestLog
>     INFO  - 2016-03-24 11:05:30.410; [   ]
> org.eclipse.jetty.deploy.providers.ScanningAppProvider; Deployment
> monitor [file:/home/opuser/OP/OpenPages/OPSearch/solr/server/contexts/]
> at interval 0
>     WARN  - 2016-03-24 11:05:30.483; [   ]
> org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration; Config
> error at <Set name="tempDirectory"><Property name="jetty.base"
> default="."/>/solr-webapp</Set>
>     WARN  - 2016-03-24 11:05:30.484; [   ]
> org.eclipse.jetty.deploy.DeploymentManager; Unable to reach node goal:
> started
>     java.lang.NoSuchFieldException: TYPE
>         at java.lang.Class.getFieldImpl(Native Method)
>         at java.lang.Class.getField(Class.java:1101)
>         at
> org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.set(XmlConfiguration.java:490)
>     .... .... ....
>     .... .... ....
>     INFO  - 2016-03-24 11:05:30.521; [   ]
> org.eclipse.jetty.server.AbstractConnector; Started
> ServerConnector@63eccae2{HTTP/1.1}{0.0.0.0:8983 <http://0.0.0.0:8983>}
>     INFO  - 2016-03-24 11:05:30.522; [   ]
> org.eclipse.jetty.server.Server; Started @958ms
> 
> From here on, I cannot access the Jetty server.
> 
> I'm using Jetty that comes with Solr 5.2 and the above error is reported
> when I try to start Solr from the command line using: bin/solr start -p
> 8983 -m 4098m -s ../solr_index.  My environment is Linux.
> 
> To "fix" the issue, I issue Solr's "stop" command followed with the
> "start" again and now everything works.

You may remember me from solr-user.  This question would probably be
more at home on that list than this one.

I looked briefly at the Jetty code that logs these warnings.  I don't
understand the code well enough to tell you what actually went wrong.

I cannot imagine anything *normal* that would cause this problem on one
start but NOT cause it after a stop and another start.  This suggests
that either there's something very weird going on with your setup or
that somebody changed something between the two start attempts.

Checking the entire Solr binary installation (looking at 5.5) for
"jetty.base", I only see it in Jetty configurations, so I am guessing
that Jetty itself will set this property if it is not already set.  As
far as I can tell, the Solr start scripts do not set that property.

Was there more information in the stacktrace?  If so, can you include
the rest of it?

Thanks,
Shawn