Netdata Community

How can I exclude rclone fuse mount from disk space monitoring?

Environment

Linux box 4.15.0-159-generic #167-Ubuntu SMP Tue Sep 21 08:55:05 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Problem/Question

How can i exclude rclone fuse mount from disk space monitoring?
So far I have tried adding this

exclude space metrics on filesystems = *gvfs gluster *s3fs *ipfs *davfs2 *httpfs *sshfs *gdfs moosefs fusectl autofs fuse

This is the line from cat /proc/self/mountinfo

6371 159 0:1882 / /home/user/storage/media/MyMounts/ODriveMusic rw,nosuid,nodev,relatime shared:1217 - fuse.rclone OneDrive:Music rw,user_id=0,group_id=0,allow_other

I’ve also tried fuse.rclone instead of fuse, but that does not work as well.

Any Ideas what I’m doing wrong? (Obviously I’m rebooting netdata after each change)

It should work. Please check if the configuration is applied - open http://<your host>:19999/netdata.conf and check if exclude space metrics on filesystems is correct and uncommented.

You also can try using fuse*.

Okay, The problem was that old netdata instance was running even after executing systemctl restart netdata. same problem with systemctl stop netdata.
I had to force kill all netdata instance.
Now I can see that the netdata service does not kill the nginx instances it is running. Is that normal?

Hmm, maybe you executed one instance manually by mistake? Does the issue happen repeatedly when you restart the service?

Nope, It was running after the installation, probably triggered by the installation script.

Right now, the Netdata instance properly stops and starts with systemd, but It is leaving behind lots of nginx worker process without their master process (zomie process most likely). And these can’t be killed.

Netdata doesn’t spawn nginx processes. There might be a problem with nginx itself. You could try to restart the nginx service.

Thanks for the clarification but It’s quite strange. These processes do not exist after a system reboot and only start after running netdata. Also these are running as netdata user, while my main nginx process runs as nginx user.
I’ve stopped main nginx instance but that does not kill these processes.

Also, I’ve installed netdata on a different machine and same behavior. Any idea, what is happening?

Hm, unfortunately, I’m not familiar with nginx. @ilyam8, @Austin_Hemmelgarn, could you help here?

nginx: worker process are processes spawned by the master Nginx process. You can see the hierarchy by executing:

[ilyam@pc ~]$ ps faxu | grep "[n]ginx"
root        1823  0.4  0.0  10656  5816 ?        Ss   14:42   0:00  \_ nginx: master process nginx -g daemon off;
101         1877  0.0  0.0  11060  2656 ?        S    14:42   0:00      \_ nginx: worker process
101         1878  0.0  0.0  11060  2656 ?        S    14:42   0:00      \_ nginx: worker process
101         1879  0.0  0.0  11060  2656 ?        S    14:42   0:00      \_ nginx: worker process
101         1880  0.0  0.0  11060  2656 ?        S    14:42   0:00      \_ nginx: worker process
101         1881  0.0  0.0  11060  2656 ?        S    14:42   0:00      \_ nginx: worker process
101         1882  0.0  0.0  11060  2656 ?        S    14:42   0:00      \_ nginx: worker process