*** ASF Nagios ***
Notification Type: PROBLEM
Host: blogs.zones.apache.org
Address: 140.211.11.102
Service: HTTP - ASF Blogs
State: CRITICAL
Info: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway
Date/Time: Mon Jul 8 20:00:18 UTC 2013
*** ASF Nagios ***
Notification Type: PROBLEM
Host: blogs.zones.apache.org
Address: 140.211.11.102
Service: HTTP - ASF Blogs
State: CRITICAL
Info: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway
Date/Time: Mon Jul 8 18:00:18 UTC 2013
+1
At Mon, 08 Jul 2013 12:44:18 -0400,
Glen Mazza wrote:
>
> Yes, I see you're trying. They're always welcome to send us a
> human-made email message here if we can help them, it's just that
> probably 90%+ of these messages are automated duplicates of the same
> problem, problems that resol
Yes, I see you're trying. They're always welcome to send us a
human-made email message here if we can help them, it's just that
probably 90%+ of these messages are automated duplicates of the same
problem, problems that resolve themselves, and/or are a
server-and-not-Roller related Infra matte
*** ASF Nagios ***
Notification Type: PROBLEM
Host: blogs.zones.apache.org
Address: 140.211.11.102
Service: HTTP - ASF Blogs
State: CRITICAL
Info: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway
Date/Time: Mon Jul 8 16:00:18 UTC 2013
*** ASF Nagios ***
Notification Type: PROBLEM
Host: blogs.zones.apache.org
Address: 140.211.11.102
Service: HTTP - ASF Blogs
State: CRITICAL
Info: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway
Date/Time: Mon Jul 8 14:00:20 UTC 2013
Overall, I think these are very good ideas. Thanks for the proposals. More
comments below.
On Thu, Jul 4, 2013 at 9:18 PM, Glen Mazza wrote:
> Hi All, here are the next round of improvements I'd like us to consider
> for Roller:
>
> 1.) Update Spring framework from 2.0.7 & 2.5.6 & 1.2 to the la
*** ASF Nagios ***
Notification Type: RECOVERY
Host: blogs.zones.apache.org
Address: 140.211.11.102
Service: HTTP - ASF Blogs
State: OK
Info: HTTP OK HTTP/1.1 200 OK - 41922 bytes in 3.662 seconds
Date/Time: Mon Jul 8 07:26:28 UTC 2013
