Hi,
the log entry is related to a "check filesystem" test.
If sysfs is mounted ("/sys/class/block" is present), Monit retrieves block
device statistics from "/sys/dev/block/<major>:<minor>/stat". The major:minor
numbers correspond to the block device mounted on the monitored filesystem. The
filesystem is mapped to the block device via /proc/self/mounts table.
To trace the monitoring, stop Monit and run it in foreground debug mode:
monit -vI
Each check will be logged, and this should help identify the filesystem
involved.
We've improved the error message in the development version to simplify the
error analysis:
https://bitbucket.org/tildeslash/monit/commits/c9068009c3f54575f799f1a67b10d2b725c928f1
Best regards,
The M/Monit team
> On 17. 8. 2025, at 10:30, lejeczek via This is the general mailing list for
> monit <[email protected]> wrote:
>
> Hi guys.
>
> I get this in logs:
> ...
> filesystem statistic error: cannot read /sys/dev/block/0:0/stat -- No such
> file or directory
> ...
> and I don't know where that comes from.
> Nothing of that path/kind can be found in config files - no explicitly.
> How to trace back ?
> I have a few network mounted paths for monit - could it be there where
> 'monit' misbehaves this way?
>
> many thanks, L.
