[Top][All Lists]

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

Re: Unable to stop monit

From: Martin Pala
Subject: Re: Unable to stop monit
Date: Fri, 12 Feb 2016 10:28:47 +0100

As mentioned it is almost certainly linux driver issue ... monit just triggers 
the problem, but the root cause is 3rd party.

Based on the stacktrace which is logged in
 it seems that the blocked read() may probably come from collecting the system 
and process statistics via a /proc filesystem.

It  seems that in case of LXC it goes via a FUSE filesystem and gets stuck 

I think it should be possible to trigger the problem without involving monit, 
the following script collects the data from the /proc filesystem each 5 seconds 
similarly to monit, can you try to run it and see if it'll stuck as well?

        while (true); do cat /proc/meminfo /proc/stat /proc/[1-9]*/stat 
/proc/[1-9]*/status > /dev/null; sleep 5; done


> On 10 Feb 2016, at 01:37, deranjer <address@hidden> wrote:
> It actually is an LXC container it is running in, so I will assume that is
> the issue.  I'm running 5.9, so I will either manually update to 5.16 then
> test it to see if anything has changed (since apparently 5.15 fixed some
> signal handling issues) or just deal with the issue until the new version
> hits the repos.
> --
> View this message in context: 
> Sent from the monit-general mailing list archive at
> --
> To unsubscribe:

reply via email to

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