idp.jks not created

[Walter Forbes Hoehn (wassa)]

Jetty should log its port bindings.  For instance:

jetty.log.20150330.gz:08:59:14.132 - INFO [org.eclipse.jetty.server.ServerConnector:266] - Started ServerConnector at 446a5aa5{SSL-http/1.1}{0.0.0.0:8443}

-WFH


> On Apr 7, 2015, at 1:54 PM, Riz Panjwani <panjwani.riz at gmail.com> wrote:
> 
> 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.
> 
> On Tue, Apr 7, 2015 at 9:59 AM, Cantor, Scott <cantor.2 at osu.edu> wrote:
> On 4/7/15, 12:55 PM, "Riz Panjwani" <panjwani.riz at gmail.com> wrote:
> 
> >Thanks scott, here's what the idp log has:
> 
> 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.
> 
> -- Scott
> 
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
> 
> -- 
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net