<div dir="ltr">ok so I set $JETTY_HOME to /opt/jetty/ and started jetty. So now it's listening on 8085 and 8443, but it's funny because when I started the service it said "Failed to start service" after a few seconds.<div><br></div><div>Here's the output when i verbose curl the port:</div><div><br></div><div><div> curl --verbose localhost:8085</div><div>* Rebuilt URL to: localhost:8085/</div><div>* Hostname was NOT found in DNS cache</div><div>* Trying 127.0.0.1...</div><div>* Connected to localhost (127.0.0.1) port 8085 (#0)</div><div>> GET / HTTP/1.1</div><div>> User-Agent: curl/7.35.0</div><div>> Host: localhost:8085</div><div>> Accept: */*</div><div>></div><div>* Empty reply from server</div><div>* Connection #0 to host localhost left intact</div><div>curl: (52) Empty reply from server</div></div><div><br></div><div>Not sure if at this point it's supposed to return something else, or just respond with an empty reply like this. Not really sure where to go from here. I ran the shibboleth status command and it just responded with "<a href="http://localhost/idp/status">http://localhost/idp/status</a>" so I curled that and I got an empty response again...</div><div><br></div><div><div>ubuntu@riz-test:/opt/shibboleth-idp$ ./bin/status.sh</div><div>(<a href="http://localhost/idp/status">http://localhost/idp/status</a>) <a href="http://localhost/idp/status">http://localhost/idp/status</a></div><div>ubuntu@riz-test:/opt/shibboleth-idp$ curl --verbose localhost:8085/idp/status</div><div>* Hostname was NOT found in DNS cache</div><div>* Trying 127.0.0.1...</div><div>* Connected to localhost (127.0.0.1) port 8085 (#0)</div><div>> GET /idp/status HTTP/1.1</div><div>> User-Agent: curl/7.35.0</div><div>> Host: localhost:8085</div><div>> Accept: */*</div></div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Apr 7, 2015 at 3:06 PM, 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">Jetty should log its port bindings. For instance:<br>
<br>
jetty.log.20150330.gz:08:59:14.132 - INFO [org.eclipse.jetty.server.ServerConnector:266] - Started ServerConnector@446a5aa5{SSL-http/1.1}{<a href="http://0.0.0.0:8443" target="_blank">0.0.0.0:8443</a>}<br>
<span class="HOEnZb"><font color="#888888"><br>
-WFH<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
> On Apr 7, 2015, at 1:54 PM, Riz Panjwani <<a href="mailto:panjwani.riz@gmail.com">panjwani.riz@gmail.com</a>> wrote:<br>
><br>
> I was mistaken, the service doesn't actually even listen to the ports. Might have been some stale service. I just can't get this service going. Not sure where else to look. Doesn't seem like a networking issue as I have apache running on port 80 and I can curl to it on localhost no problems.<br>
><br>
> On Tue, Apr 7, 2015 at 9:59 AM, Cantor, Scott <<a href="mailto:cantor.2@osu.edu">cantor.2@osu.edu</a>> wrote:<br>
> On 4/7/15, 12:55 PM, "Riz Panjwani" <<a href="mailto:panjwani.riz@gmail.com">panjwani.riz@gmail.com</a>> wrote:<br>
><br>
> >Thanks scott, here's what the idp log has:<br>
><br>
> Then there's nothing wrong. Whatever ports you think it's using, whatever path into the web server you think is open, it's not. It's a networking issue.<br>
><br>
> -- Scott<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><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>
</div></div></blockquote></div><br></div>