<div dir="ltr">Thanks Walter. I ran the process manually from jetty base inside a tmux session and using netstat I can now see that a java process is listening on ports 8085 and 8443. However, when I issue a curl command to those ports, it just hangs and nothing happens. I still see the following messages in my stderrorout log, but I see nothing in my request.log:<div><br></div><div><div>2015-04-07 15:40:32.272:INFO:oejs.Server:main: jetty-9.2.10.v20150310</div><div>2015-04-07 15:40:32.292:INFO:oejs.AbstractNCSARequestLog:main: Opened /opt/jetty/logs/2015_04_07.request.log</div><div>2015-04-07 15:40:32.297:INFO:oejdp.ScanningAppProvider:main: Deployment monitor [file:/opt/jetty/webapps/] at interval 1</div><div>2015-04-07 15:40:43.751:INFO:/idp:main: No Spring WebApplicationInitializer types detected on classpath</div><div>2015-04-07 15:40:44.281:INFO:/idp:main: Initializing Spring root WebApplicationContext</div></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Apr 7, 2015 at 6:42 AM, Walter Forbes Hoehn (wassa) <span dir="ltr"><<a href="mailto:wassa@memphis.edu" target="_blank">wassa@memphis.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">That log seems to indicate that Jetty starts up fine, but doesn’t find a “Jetty Deployable Descriptor” file. It’s looking for this file under $JETTY_HOME/webapps/, which could be valid, depending on your configuration. If you are following the instructions listed on the wiki, however, you would have placed your idp.xml file under $JETTY_BASE/webapps/. To point at the correct configuration, you need to bootstrap Jetty from $JETTY_BASE, not $JETTY_HOME. If you are starting jetty manually, simply change to the $JETTY_BASE directory and execute something like “java -jar ../star.jar”.<br>
<span class="HOEnZb"><font color="#888888"><br>
-Walter<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
> On Apr 6, 2015, at 10:39 PM, Riz Panjwani <<a href="mailto:panjwani.riz@gmail.com">panjwani.riz@gmail.com</a>> wrote:<br>
><br>
> Hi,<br>
><br>
> I'm following the instructions here: <a href="https://wiki.shibboleth.net/confluence/display/IDP30/Jetty9" target="_blank">https://wiki.shibboleth.net/confluence/display/IDP30/Jetty9</a> to install jetty 9. When I try to start the service, it fails. But I'm not seeing any errors in the stderrout.log or any other log in the /logs folder. Any idea where I should check? Below is my stderrout.log content:<br>
><br>
> 2015-04-07 03:28:23.136:INFO:oejs.Server:main: jetty-9.2.10.v20150310<br>
> 2015-04-07 03:28:23.156:INFO:oejs.AbstractNCSARequestLog:main: Opened /opt/jetty/logs/2015_04_07.request.log<br>
> 2015-04-07 03:28:23.160:INFO:oejdp.ScanningAppProvider:main: Deployment monitor [file:/opt/jetty/webapps/] at interval 1<br>
> 2015-04-07 03:28:34.575:INFO:/idp:main: No Spring WebApplicationInitializer types detected on classpath<br>
> 2015-04-07 03:28:35.116:INFO:/idp:main: Initializing Spring root WebApplicationContext<br>
><br>
> On Mon, Apr 6, 2015 at 8:35 PM, Riz Panjwani <<a href="mailto:panjwani.riz@gmail.com">panjwani.riz@gmail.com</a>> wrote:<br>
> I'm following the instructions here: <a href="https://wiki.shibboleth.net/confluence/display/IDP30/Jetty9" target="_blank">https://wiki.shibboleth.net/confluence/display/IDP30/Jetty9</a> to install jetty 9. When I try to start the service, it fails. But I'm not seeing any errors in the stderrout.log or any other log in the /logs folder. Any idea where I should check?:<br>
><br>
> 2015-04-07 03:28:23.136:INFO:oejs.Server:main: jetty-9.2.10.v20150310<br>
> 2015-04-07 03:28:23.156:INFO:oejs.AbstractNCSARequestLog:main: Opened /opt/jetty/logs/2015_04_07.request.log<br>
> 2015-04-07 03:28:23.160:INFO:oejdp.ScanningAppProvider:main: Deployment monitor [file:/opt/jetty/webapps/] at interval 1<br>
> 2015-04-07 03:28:34.575:INFO:/idp:main: No Spring WebApplicationInitializer types detected on classpath<br>
> 2015-04-07 03:28:35.116:INFO:/idp:main: Initializing Spring root WebApplicationContext<br>
><br>
><br>
> On Tue, Mar 31, 2015 at 7:42 PM, Scott Koranda <<a href="mailto:skoranda@gmail.com">skoranda@gmail.com</a>> wrote:<br>
> On Tue, Mar 31, 2015 at 9:36 PM, Riz Panjwani <<a href="mailto:panjwani.riz@gmail.com">panjwani.riz@gmail.com</a>> wrote:<br>
> > Hi, I'm trying to install Shibboleth on ubuntu14.04 and according to the<br>
> > guide here<br>
> > (<a href="https://wiki.shibboleth.net/confluence/display/SHIB2/IdPApacheTomcatPrepare" target="_blank">https://wiki.shibboleth.net/confluence/display/SHIB2/IdPApacheTomcatPrepare</a>),<br>
> > after running install.sh, I should see idp.jks in IDP_HOME/credentials/.<br>
> > However, all I see are the following files:<br>
> ><br>
> > -rw------- 1 root root 1675 Mar 31 21:22 idp-signing.key<br>
> > -rw-r--r-- 1 root root 1204 Mar 31 21:22 idp-signing.crt<br>
> > -rw------- 1 root root 1679 Mar 31 21:22 idp-encryption.key<br>
> > -rw-r--r-- 1 root root 1204 Mar 31 21:22 idp-encryption.crt<br>
> > -rw-r--r-- 1 root root 1204 Mar 31 21:22 idp-backchannel.crt<br>
> > -rw-r--r-- 1 root root 2608 Mar 31 21:22 idp-backchannel.p12<br>
> > -rw-r--r-- 1 root root 500 Mar 31 21:22 sealer.jks<br>
> > -rw-r--r-- 1 root root 47 Mar 31 21:22 sealer.kver<br>
> ><br>
> > I don't have the idp.jks. What am I doing wrong?<br>
> ><br>
><br>
> You have deployed the version 3.1.x of the IdP but are reading<br>
> instructions for the older version 2.x.<br>
><br>
> The documentation for version 3.1.x is at<br>
><br>
> <a href="https://wiki.shibboleth.net/confluence/display/IDP30/Home" target="_blank">https://wiki.shibboleth.net/confluence/display/IDP30/Home</a><br>
><br>
> Scott K<br>
> --<br>
> To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net">users-unsubscribe@shibboleth.net</a><br>
><br>
><br>
> --<br>
> To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net">users-unsubscribe@shibboleth.net</a><br>
<br>
--<br>
To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net">users-unsubscribe@shibboleth.net</a></div></div></blockquote></div><br></div>