status.sh Connection refused && Jetty errors

[Cristian Pastramagiu]

Hi Christopher, 

 

Ofc, I missed adding that part in my desc.

 

On http://idp.consulteer.com:8080/idp/ I get a 

HTTP 503:

Problem accessing /idp/. Reason:

 

    Service Unavailable

 

BR
Cristian 

 

From: Christopher Bongaarts [mailto:cab at umn.edu] 
Sent: Friday, December 8, 2017 5:10 PM
To: users at shibboleth.net
Subject: Re: status.sh Connection refused && Jetty errors

 

On 12/8/2017 6:48 AM, Cristian Pastramagiu wrote:



root at idp:/opt/shibboleth-idp/bin# ./status.sh 

(http://localhost/idp/status) Connection refused (Connection refused)


Run "./status.sh --help" to see the options.  Hint: you will need the -u option if jetty is not listening on the default port 80.




 On another side: when looking for idp.my.server:8080 (with a Jetty started in debug mode)  I get 

In browser:

Error 404 - Not Found.

 

No context on this server matched or handled this request.

Contexts known to this server are:

/idp ---> o.e.j.w.WebAppContext at 1ce92674{/idp,[file:///tmp/jetty-0.0.0.0-8080-idp.war-_idp-any-5795040276901592588.dir/webinf/ <mailto:o.e.j.w.WebAppContext at 1ce92674%7b/idp,%5bfile:///tmp/jetty-0.0.0.0-8080-idp.war-_idp-any-5795040276901592588.dir/webinf/> , jar:file:///opt/shibboleth-idp/war/idp.war!/],UNAVAILABLE}{/opt/shibboleth-idp/war/idp.war}

Powered by Jetty:// 9.4.6.v20170531


This is what you'd expect if you just hit http://idp.my.server:8080/ - there isn't any content there normally.  You need to at least add /idp to the URL in order for it to get to the IdP web app.



-- 
%%  Christopher A. Bongaarts   %%  cab at umn.edu <mailto:cab at umn.edu>           %%
%%  OIT - Identity Management  %%  http://umn.edu/~cab  %%
%%  University of Minnesota    %%  +1 (612) 625-1809    %%
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20171208/6b0ec78e/attachment.html>