I would really like to hear from anybody else who has AWS machines, and
alerting/monitoring of those systems (by a system other than Amazon's own
monitoring system).
The number of alerts I'm receiving about systems being unreachable and then
becoming reachable again is ... Crazy to say the
On Sun, Sep 28, 2014 at 01:56:07PM +, Edward Ned Harvey (blu) wrote:
I would really like to hear from anybody else who has AWS machines, and
alerting/monitoring of those systems (by a system other than Amazon's own
monitoring system).
The number of alerts I'm receiving about systems
None of our systems are scheduled for reboot, *and* the machines triggering our
alerts have not been rebooting - they just become unavailable on the network
for a few minutes and then reappear, without any sort of crash or reboot or
anything affecting uptime. *And* this has been a general
From: discuss-bounces+blu=nedharvey@blu.org [mailto:discuss-
bounces+blu=nedharvey@blu.org] On Behalf Of Chuck Anderson
Maybe this?
https://aws.amazon.com/blogs/aws/ec2-maintenance-update/
I am aware of that - but they say less than 10% of their systems will be
affected, and
Did you get an email telling you about reboots begin scheduled? I know I
have a number of systems being rebooted today around 2pm. If you log into
the console, and go to EC2 then click on Events on the left side it will
show you any ones that are scheduled in the future. If you change one of
We use Nagios and nrpe with a pretty standard monitoring setup. We also
pull in cloudwatch data via python goto scripts.
As for the uptick I would avoid making any changes until after the AWS
maintenance. We have also noticed an uptick in alerts,though not to that
level.
However just because
Hi all,
So I'm brining up apache on my new server and I'm trying to do right by
selinux this time. My default mode is to ignore selinux, put it in
permissive mode, and watch all the error messages get logged but pretty
much ignore what's going on under the selinux hood. Well, I figure this
On Sun, Sep 28, 2014 at 04:25:06PM -0400, Stephen Adler wrote:
P.S. this is the kind of stuff I'm confronting
[root@mipdata0 ~]# sealert -l dd884c85-199f-49c5-b44c-a595ce3cec43
SELinux is preventing /usr/bin/python2.7 from read access on the lnk_file .
First, I recommend reading Dan
Chuck is spot on. Dan is the center of wisdom, and other advise looked good.
___
Discuss mailing list
Discuss@blu.org
http://lists.blu.org/mailman/listinfo/discuss
On 09/28/2014 06:55 PM, Chuck Anderson wrote:
On Sun, Sep 28, 2014 at 04:25:06PM -0400, Stephen Adler wrote:
P.S. this is the kind of stuff I'm confronting
[root@mipdata0 ~]# sealert -l dd884c85-199f-49c5-b44c-a595ce3cec43
SELinux is preventing /usr/bin/python2.7 from read access on the
10 matches
Mail list logo
