We didn't test with glusterfs-fuse mount points before. We'll try to reproduce
the problem.
Please can you try to change the test this way?:
check filesystem PEOPLE_SYSDATA path "10.1.1.99:/PEOPLE_SYSDATA"
start program = "/usr/bin/systemctl start PEOPLE_SYSDATA.mount"
stop program = "/usr/bin/systemctl stop PEOPLE_SYSDATA.mount"
Best regards,
Martin
> On 10. 11. 2025, at 11:24, lejeczek via This is the general mailing list for
> monit <[email protected]> wrote:
>
> I tried that, it did not tell me much, I did not get it.
>
> -> $ monit -vI 2>&1 | __grepColorIt '0:0/stat'
> ...
> Reloading mount information for filesystem '/PEOPLE_SYSDATA'
> filesystem statistic error: cannot read /sys/dev/block/0:0/stat -- No such
> file or directory
> 'PEOPLE_SYSDATA' succeeded getting filesystem statistics for '/PEOPLE_SYSDATA'
> ...
> Reloading mount information for filesystem '/PEOPLE_SYSDATA'
> filesystem statistic error: cannot read /sys/dev/block/0:0/stat -- No such
> file or directory
> 'PEOPLE_SYSDATA' succeeded getting filesystem statistics for '/PEOPLE_SYSDATA'
> ...
>
> it shows up in the company of /PEOPLE_SYSDATA but that is - but I have a few
> of those - a glusterfs-fuse mount point:
>
> 10.1.1.99:/PEOPLE_SYSDATA /PEOPLE_SYSDATA fuse.glusterfs
> rw,relatime,user_id=0,group_id=0,allow_other,max_read=131072 0 0
>
> Here is monit for it:
>
> check filesystem PEOPLE_SYSDATA path /PEOPLE_SYSDATA
> start program = "/usr/bin/systemctl start PEOPLE_SYSDATA.mount"
> stop program = "/usr/bin/systemctl stop PEOPLE_SYSDATA.mount"
>
> monit is 5.33.0
> What am I missing?
> thanks, L.
