Disk Warning - Exclude
Completed
As a System Administrator or Web Hosting Provider, I would like a way to exclude non-official Mount points from Disk Warning in tweak settings so that if the disk is shared by many users and it starts filling up, the user won't receive a cPanel notice.
====================
Add a way to exclude non official Mount point from Disk Warning in tweak settings.
I need this too... For example, I've installed https://snapcraft.io/ which creates a small partition to run. This partition is always 100% utilized.
I receive continuous critical warning messages about this partition, but this is expected behaviour.
I need this too... For example, I've installed https://snapcraft.io/ which creates a small partition to run. This partition is always 100% utilized.
I receive continuous critical warning messages about this partition, but this is expected behaviour.
For anyone who is interested, you can create a diff patch to work around this issue until there is official support. cPanel would not recommend this, however learning about the gaining popularity of Snapcraft, I think it's appropriate to exclude 'snapd' from _diskcheck
/usr/local/cpanel/Cpanel/TailWatch/ChkServd.pm line 765
For anyone who is interested, you can create a diff patch to work around this issue until there is official support. cPanel would not recommend this, however learning about the gaining popularity of Snapcraft, I think it's appropriate to exclude 'snapd' from _diskcheck
/usr/local/cpanel/Cpanel/TailWatch/ChkServd.pm line 765
In cPanel & WHM version 94, you will be able to configure ChkServd to ignore mount points. ChkServd will look for entries in a new configuration file: /var/cpanel/chkservd_ignored_mounts. Entries in that file are used to ignore disk space checks.
In cPanel & WHM version 94, you will be able to configure ChkServd to ignore mount points. ChkServd will look for entries in a new configuration file: /var/cpanel/chkservd_ignored_mounts. Entries in that file are used to ignore disk space checks.
Thank you. Just installed v94 and am wanting to configure this. Can't find any sample config file supplied to provide syntax. What is config file syntax, please?
Thank you. Just installed v94 and am wanting to configure this. Can't find any sample config file supplied to provide syntax. What is config file syntax, please?
Hi, is there any documentation on the syntax for this feature? I'm looking to disable the multiple snapd drives that trigger on a daily basis.
Hi, is there any documentation on the syntax for this feature? I'm looking to disable the multiple snapd drives that trigger on a daily basis.
Not much to the syntax. Just one number per line:
Not much to the syntax. Just one number per line:
Is there any official documentation regarding the solution? Once we update /var/cpanel/chkservd_ignored_mounts do we need to run /scripts/restartsrv_chkservd ?
Also, the mounts are still showing red in Home » Server Status » Service Status (See attached).
Nice to see a solution, would be nice to see documentation. Unless it's there and I just can't find it...
Is there any official documentation regarding the solution? Once we update /var/cpanel/chkservd_ignored_mounts do we need to run /scripts/restartsrv_chkservd ?
Also, the mounts are still showing red in Home » Server Status » Service Status (See attached).
Nice to see a solution, would be nice to see documentation. Unless it's there and I just can't find it...
I hope a more permanent fix for this issue will be forthcoming. The writearound given is nowhere near permanent.
Every couple of weeks, I get a new message about a filesystem at 100% usage. At the same time, one of the old 100% Snapcraft partition numbers has disappeared. Clearly some background operation is causing an existing partition to be renamed, recreated, or updated under a new name. Then I have to manually edit the exception file every week or two to suppress the messages. This is hardly less work than just ignoring the error messages in the first place.
I hope a more permanent fix for this issue will be forthcoming. The writearound given is nowhere near permanent.
Every couple of weeks, I get a new message about a filesystem at 100% usage. At the same time, one of the old 100% Snapcraft partition numbers has disappeared. Clearly some background operation is causing an existing partition to be renamed, recreated, or updated under a new name. Then I have to manually edit the exception file every week or two to suppress the messages. This is hardly less work than just ignoring the error messages in the first place.
Replies have been locked on this page!