That appears to have been caused by the following error:
/srv/whimsy/lib/whimsy/asf.rb:14:in `require_relative': cannot load
such file -- /srv/whimsy/lib/whimsy/asf/person (LoadError)
from /srv/whimsy/lib/whimsy/asf.rb:14:in `<top (required)>'
from
/usr/local/rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in
`require'
from
/usr/local/rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in
`require'
from /srv/whimsy/www/roster/public_json_common.rb:11:in `<top (required)>'
from roster/public_ldap_committees.rb:17:in `require_relative'
from roster/public_ldap_committees.rb:17:in `<main>'
I see it is now fixed, however it would be useful to extract at least
the first line of the stack trace to include in the PMB report.
I hope to get round to that soon unless anyone else beats me to it.
On 25 March 2016 at 17:18, Ping My Box <no-re...@pingmybox.com> wrote:
>
> Hello,
> The https service at whimsy.apache.org (whimsy.apache.org (https)) has been
> reported as down by our monitoring system:
>
> Component: response
> Error code: Internal Server Error or equivalent bad message received:
> HTTP/1.1 400 public_json 4 issues: ldap-committees, committee-info,
> icla-info, member-info
> Debug output:
> ----------
> [Fri Mar 25 17:18:09 2016]: Initialising socket
> [Fri Mar 25 17:18:09 2016]: Looking up hostname whimsy.apache.org...
> [Fri Mar 25 17:18:09 2016]: Connecting to 209.188.14.150:443
> [Fri Mar 25 17:18:10 2016]: Connected, sending HTTPS payload.
> [Fri Mar 25 17:18:10 2016]: Reading response header from server
> [Fri Mar 25 17:18:10 2016]: Caught exception: Internal Server Error or
> equivalent bad message received: HTTP/1.1 400 public_json 4 issues:
> ldap-committees, committee-info, icla-info, member-info
>
>
> ----------
>
> With regards,
> Ping My Box - https://www.pingmybox.com/
