• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue plesk-ext-monitoring-hcd.service & systemd-quotacheck.service failed

Polli

Basic Pleskian
Server operating system version
Debian 12
Plesk version and microupdate number
18.0.58#2
I have found the following errors in the protocol.
At first I thought it wasn't that bad, as the errors only appeared once.
But now I realize that the quota seems to be disabled because all websites have unlimited quotas.

Starting the services failed with "permission denied".
How can I fix these errors? Plesk repair did not found any issues.

Execution status has failed with exit code 3, stdout: × plesk-ext-monitoring-hcd.service - Hardware changes detector for the Plesk Monitoring
Loaded: loaded (/lib/systemd/system/plesk-ext-monitoring-hcd.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Wed 2024-01-24 03:25:18 CET; 5 days ago
Main PID: 4434 (code=exited, status=1/FAILURE)
CPU: 1.795s

Jan 24 03:25:18 loft24204 php[4434]: PleskExt\Monitoring\Helper\Grafana::updateState()
Jan 24 03:25:18 loft24204 php[4434]: 4: /opt/psa/admin/plib/modules/monitoring/library/Helper/HardwareInfoUpdater.php:50
Jan 24 03:25:18 loft24204 php[4434]: PleskExt\Monitoring\Helper\HardwareInfoUpdater->update()
Jan 24 03:25:18 loft24204 php[4434]: 5: /opt/psa/admin/plib/modules/monitoring/scripts/detect-hardware-changes.php:22
Jan 24 03:25:18 loft24204 php[4434]: ERROR: pm_Exception_ResultException: Execution extension has failed with exit code 3, stdout: , stderr: Unable to Connect to tcp://127.0.0.1:3030. Error #111: Connection refused
Jan 24 03:25:18 loft24204 php[4434]: (ApiCli.php:331)
Jan 24 03:25:18 loft24204 systemd[1]: plesk-ext-monitoring-hcd.service: Main process exited, code=exited, status=1/FAILURE
Jan 24 03:25:18 loft24204 systemd[1]: plesk-ext-monitoring-hcd.service: Failed with result 'exit-code'.
Jan 24 03:25:18 loft24204 systemd[1]: Failed to start plesk-ext-monitoring-hcd.service - Hardware changes detector for the Plesk Monitoring.
Jan 24 03:25:18 loft24204 systemd[1]: plesk-ext-monitoring-hcd.service: Consumed 1.795s CPU time.
, stderr:

Execution status has failed with exit code 3, stdout: × systemd-quotacheck.service - File System Quota Check
Loaded: loaded (/lib/systemd/system/systemd-quotacheck.service; static)
Active: failed (Result: exit-code) since Wed 2024-01-24 03:24:21 CET; 5 days ago
Docs: man:systemd-quotacheck.service(8)
Main PID: 655 (code=exited, status=1/FAILURE)
CPU: 11ms

Jan 24 03:24:21 loft24204 systemd[1]: Starting systemd-quotacheck.service - File System Quota Check...
Jan 24 03:24:21 loft24204 systemd-quotacheck[657]: quotacheck: Kann das Dateisystem auf / nicht als nur-lesbar ummounten. Gezählte Werte könnten falsch sein.
Jan 24 03:24:21 loft24204 systemd-quotacheck[657]: Bitte beenden Sie alle Programme, die auf das Dateisystem schreiben oder verwenden Sie -m, um die Prüfung zu erzwingen.
Jan 24 03:24:21 loft24204 systemd-quotacheck[655]: (quotacheck) failed with exit status 1.
Jan 24 03:24:21 loft24204 systemd[1]: systemd-quotacheck.service: Main process exited, code=exited, status=1/FAILURE
Jan 24 03:24:21 loft24204 systemd[1]: systemd-quotacheck.service: Failed with result 'exit-code'.
Jan 24 03:24:21 loft24204 systemd[1]: Failed to start systemd-quotacheck.service - File System Quota Check.
, stderr:

Thanks for help and best regards
 
plesk-ext-monitoring-hcd.service is running now. This issue is solved.

systemd-quotacheck.service is still dead and I´m not able to get it started.
 
Sorry for posting again. Quota service is now running but the quota is still unlimited for all websites. I also tried to set all quota again on all websites. No changes. How can I fix this?
 
Could you please provide an example what quota setting you mean in a subscription?
I set a limit for using diskspace on every Website. But the diskspace is still shown as unlimited. See attached Screenshots. (If you need translation, let me know.)
By the way: The field for entering the number is too small to read longer values correctly.
 

Attachments

  • Screenshot_20240130_120335_Brave.jpg
    Screenshot_20240130_120335_Brave.jpg
    196.1 KB · Views: 7
  • Screenshot_20240130_120456_Brave.jpg
    Screenshot_20240130_120456_Brave.jpg
    247 KB · Views: 8
You'll need to set the disk space quota in the subscription's hosting plan and also make sure that the plan is synced with the subscription. The hardware quota is something different.
 
My Plesk version has no subscriptions. I use the Web-Admin version. It worked before. I'm not really sure at witch point this happened. I just checked everything after the upgrade from Debian 11 to Debian 12 and recognised that the limits did not work any longer. All services are up and running. Plesk repair did not find any issues.
 
Disk space usage is running and is viewable.
 

Attachments

  • Screenshot_20240130_180638_Brave.jpg
    Screenshot_20240130_180638_Brave.jpg
    247.1 KB · Views: 5
I have several websites on my server. These share the space. However, they should not be unlimited so that they do not take up too much space. The limit worked until recently. But now it no longer does. What is the reason for this?
 
Operating System - Debian 10.13
Plesk Obsidian Version 18.0.58 Update #2


I have the same problem with plesk-ext-monitoring-hcd.service:

Execution status has failed with exit code 3, stdout: ● plesk-ext-monitoring-hcd.service - Hardware changes detector for the Plesk Monitoring
Loaded: loaded (/lib/systemd/system/plesk-ext-monitoring-hcd.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2024-01-30 11:17:19 CET; 1 weeks 1 days ago
Main PID: 1163 (code=exited, status=1/FAILURE)

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
, stderr:


How was this solved?

Thanks and best regards
 
Operating System - Debian 10.13
Plesk Obsidian Version 18.0.58 Update #2


I have the same problem with plesk-ext-monitoring-hcd.service:

Execution status has failed with exit code 3, stdout: ● plesk-ext-monitoring-hcd.service - Hardware changes detector for the Plesk Monitoring
Loaded: loaded (/lib/systemd/system/plesk-ext-monitoring-hcd.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2024-01-30 11:17:19 CET; 1 weeks 1 days ago

Main PID: 1163 (code=exited, status=1/FAILURE)

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
, stderr:


How was this solved?

Thanks and best regards
Have you restarted your server? That solved my problem that the service wont start. But the quota is still not working. But this is ok for me cause I have the Web Admin Edition. Still no answer why they changed it, but I can deal with it.
With limit active it was easy to see how much space every website eats up. Now I just can guess how much space they take compared to the total storage space. The Web Admin Edition supports up to ten Domains. So it makes sense to see who is taken how much space on my server.
 
Have you restarted your server? That solved my problem that the service wont start. But the quota is still not working. But this is ok for me cause I have the Web Admin Edition. Still no answer why they changed it, but I can deal with it.
With limit active it was easy to see how much space every website eats up. Now I just can guess how much space they take compared to the total storage space. The Web Admin Edition supports up to ten Domains. So it makes sense to see who is taken how much space on my server.
After a restart, the service still does not start. I get no notification about the systemd-quotacheck.service failing, so it must be ok. I honestly don't understand what this plesk-ext-monitoring-hcd.service is supposed to do. As far as I can see, monitoring (grafana) does work.
 
I have the same issue!!. I have Ubuntu 22.04. Did you guides resolve this issue? My grafana monitor is working good!

Also I restarted the server.

Thanks

Jose
 

Attachments

  • Screenshot 2024-02-12 123301.png
    Screenshot 2024-02-12 123301.png
    54.2 KB · Views: 7
Did any of you open a support ticket on it? Normally support will find the root cause, and it would be great if you then shared it here.
 
I try to report to support but the system show answer and don't let me go click forward. I will try later again
 
Hello Peter:

I tried and now support told me this:

We identified that the Plesk license was purchased not directly from Plesk but through one of the Plesk Resellers.
Ionos dont have support for Plesk.

There is another way to report this issue?

Thanks☺

Jose
 
Back
Top