Hi,
Hi,
For a few days false notification of nagios reduced. But it has increased
again.
You sure?
Looking at the /configs/system/nagios/services/template.cfg reveals
that it is configured as
max_check_attempt = 4 and retry_check_interval 1 for hosts
and
max_check_attempts = 3 and
So if a service or host is unreachable for 3 or 4 mins, we get a
notification. (However most of the cases it is false positive, due to
congestion or others).
Looking through my email, from what I can recall there are no false
positives. xen6 had to be power-cycled which caused all
So if a service or host is unreachable for 3 or 4 mins, we get a
notification. (However most of the cases it is false positive, due to
congestion or others).
Looking through my email, from what I can recall there are no false
positives. xen6 had to be power-cycled which caused all
On Sat, 2008-04-26 at 16:25 -0500, Mike McGrath wrote:
Welcome Luca, have you any experience with python and turbogears?
I had experience only with python. About web applications I have
experiences with java, but I can learn also TurboGears ;-)
Luca
--
Today is Boomtime, the 44th day of
Nigel Jones wrote:
Looking through my email, from what I can recall there are no false
positives. xen6 had to be power-cycled which caused all the other
collateral notifications.
Collateral notifications can be caught using service dependencies and
parent hosts. Do we currently use any?
On Sun, April 27, 2008 11:01 pm, Jeroen van Meeuwen wrote:
Nigel Jones wrote:
Looking through my email, from what I can recall there are no false
positives. xen6 had to be power-cycled which caused all the other
collateral notifications.
Collateral notifications can be caught using service
On Sat, 2008-04-26 at 10:38 -0700, Toshio Kuratomi wrote:
Hey guys, I'm talking especially to the web app developers here, but I
also hope that other people will chime in with useful thoughts.
As part of python-fedora, I've started documenting some standards for
Fedora Services. These
On Sun, 27 Apr 2008, susmit shannigrahi wrote:
So if a service or host is unreachable for 3 or 4 mins, we get a
notification. (However most of the cases it is false positive, due to
congestion or others).
Looking through my email, from what I can recall there are no false
On Sun, 27 Apr 2008, Jeroen van Meeuwen wrote:
Nigel Jones wrote:
Looking through my email, from what I can recall there are no false
positives. xen6 had to be power-cycled which caused all the other
collateral notifications.
Collateral notifications can be caught using service
On Mon, 28 Apr 2008, Nigel Jones wrote:
On Sun, April 27, 2008 11:01 pm, Jeroen van Meeuwen wrote:
Nigel Jones wrote:
Looking through my email, from what I can recall there are no false
positives. xen6 had to be power-cycled which caused all the other
collateral notifications.
We have a script to restart TG apps on the app servers when their memory
exceeds a customizable limit. We have this run on the app servers on
alternate hours so that we don't take down all the load balanced copies
of an app at the same time. This has proved useful for a few of our
apps which
Jesus M. Rodriguez wrote:
On Sat, Apr 26, 2008 at 10:38:51AM -0700, Toshio Kuratomi wrote:
[snip]
2) JSON data that is deeply nested sucks because objects are turned into
dictionaries so you have to write things like:
package['listings']['F-8']['people']['toshio']['acls']['commit']['status']
Hello everybody,
I'm Pavel Khardikov from the Kursk State University, Russia. I'm 22. I'm
a first year student of postgraduate study.
Graduated from the faculty of computer science and computer engineering.
Speciality: administration software and information systems.
My application have been
13 matches
Mail list logo
