monit-general
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [monit] Monit daemon broken


From: Brian Downey
Subject: Re: [monit] Monit daemon broken
Date: Fri, 14 Nov 2008 05:36:45 -0800

Hi Martin!

Here's what we get when running `monit -Iv`

'ql1lwbtdb1' Monit started
Monit instance changed notification is sent to address@hidden
AssertException: systeminfo.mem_kbyte_max > 0 at process.c:200
aborting..
IOT/Abort trap(coredump)

That's it!

We're running the same binary on identical AIX boxes (with different sizes memory, etc) however none of those are experiencing this problem. As I mentioned, it started fairly recently / randomly.


On Nov 13, 2008, at 2:11 PM, Martin Pala wrote:

Hi,

the message is generated because monit was unable to get the physical memory size ... the memory size is fetched by AIX's perfstat_memory_total() interface. The error in monit log will look most probably like this:

 system statistic error -- perfstat_memory_total failed: <some reason>

Please run monit with -v option (verbose mode) and check output.

Is the error seen on certain AIX version and/or machine only? Is the access to the AIX box still available?

Thanks,
Martin



On Nov 13, 2008, at 3:27 PM, Brian Downey wrote:

We just recently started seeing this in the output logs on an AIX 5.x box, when attempting to start the monit daemon:

<snip>
'ibeta' Monit started
AssertException: systeminfo.mem_kbyte_max > 0 at process.c:200
aborting...
</snip>

We're running it under daemontools, so immediately after the 'aborting...' it tries to start over and over to no avail.

We haven't touched the binary at all, this just started semi- randomly. Any ideas?


--
To unsubscribe:
http://lists.nongnu.org/mailman/listinfo/monit-general



--
To unsubscribe:
http://lists.nongnu.org/mailman/listinfo/monit-general





reply via email to

[Prev in Thread] Current Thread [Next in Thread]