I fixed this in public_ldap_people.json.
But perhaps the fix belongs in monitor.rb; if title and data are both
present, should it use data?
On 7 March 2016 at 12:17, sebb <seb...@gmail.com> wrote:
> There is an issue with interpreting logs which have both a warning and
> an output file update.
>
> In this case the output title replaced the data field in the PMB message.
> This is confusing, and loses useful information.
>
> The source log for this report was:
>
> -------------- cut here --------------
> _INFO Connecting to LDAP server: ldaps://ldap2-us-west.apache.org:636
> _INFO [ldap2-us-west.apache.org:636] ldapsearch -x -LLL -b
> ou=people,dc=apache,dc=org -s one
> (|(cn=*)(loginShell=*)(asf-personalURL=*)(createTimestamp=*)(modifyTimestamp=*))
> cn loginShell asf-personalURL createTimestamp modifyTimestamp uid
> _WARN [ldap2-us-west.apache.org:636] => #<LDAP::ResultError: Time
> limit exceeded> for ldapsearch -x -LLL -b ou=people,dc=apache,dc=org
> -s one
> (|(cn=*)(loginShell=*)(asf-personalURL=*)(createTimestamp=*)(modifyTimestamp=*))
> cn loginShell asf-personalURL createTimestamp modifyTimestamp uid,
> retrying ...
> _INFO Connecting to LDAP server: ldaps://ldap3-us-west.apache.org:636
> _INFO [ldap3-us-west.apache.org:636] ldapsearch -x -LLL -b
> ou=people,dc=apache,dc=org -s one
> (|(cn=*)(loginShell=*)(asf-personalURL=*)(createTimestamp=*)(modifyTimestamp=*))
> cn loginShell asf-personalURL createTimestamp modifyTimestamp uid
> _INFO git_info: fba690b 2016-03-07 11:08:36 +0000 - creating/updating
> public/public_ldap_people.json
>
> --- public/public_ldap_people.json 2016-03-07 11:19:03.244867528 +0000
> +++ - 2016-03-07 11:34:11.586237700 +0000
> @@ -1,6 +1,6 @@
> {
> "lastCreateTimestamp": "20160304172642Z",
> - "lastTimestamp": "20160307111844Z",
> + "lastTimestamp": "20160307112147Z",
> "people": {
> "a_horuzhenko": {
> "name": "Artyom Horuzhenko"
> @@ -8523,7 +8523,7 @@
> "lars": {
> "name": "Lars Eilebrecht",
> "urls": [
> - "http://www.apache.org/~lars/icbm.html";
> + "http://www.eilebrecht.net";
> ]
> },
> "larsfrancke": {
>
> -------------- cut here --------------
>
> The public_json.rb script generates the following output for this:
>
> -------------- cut here --------------
> "ldap-people": {
> "href": "../logs/public-ldap-people",
> "mtime": "2016-03-07 11:48:26 +0000",
> "level": "warning",
> "title": "updated",
> "data": "[ldap2-us-west.apache.org:636] => #<LDAP::ResultError:
> Time limit exceeded> for ldapsearch -x -LLL -b
> ou=people,dc=apache,dc=org -s one
> (|(cn=*)(loginShell=*)(asf-personalURL=*)(createTimestamp=*)(modifyTimestamp=*))
> cn loginShell asf-personalURL createTimestamp modifyTimestamp uid,
> retrying ..."
> },
> -------------- cut here --------------
>
> The "title" has come from the diff output.
> However normally a warning does not include a title.
>
> I'm not sure whether the bug is that public_json.rb should suppress
> the title in this case or whether monitor.rb should handle title
> differently where there is also a data entry.
>
> Original PMB message:
> On 7 March 2016 at 11:36, 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 ldap-people updated
>> Debug output:
>> ----------
>> [Mon Mar 7 11:35:45 2016]: Initialising socket
>> [Mon Mar 7 11:35:45 2016]: Looking up hostname whimsy.apache.org...
>> [Mon Mar 7 11:35:45 2016]: Connecting to 209.188.14.150:443
>> [Mon Mar 7 11:35:46 2016]: Connected, sending HTTPS payload.
>> [Mon Mar 7 11:35:46 2016]: Reading response header from server
>> [Mon Mar 7 11:35:46 2016]: Caught exception: Internal Server Error or
>> equivalent bad message received: HTTP/1.1 400 public_json ldap-people updated
>>
>>
>> ----------
>>
>> With regards,
>> Ping My Box - https://www.pingmybox.com/
