• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue kdump.service failure

Sysop

Basic Pleskian
In the overview of my Plesk Services I have the following error. Any insight on what needs to be done in order to resolve it would be appreciated.

kdump.service : Failed
Crash recovery kernel arming
Execution status has failed with exit code 3, stdout: × kdump.service - Crash recovery kernel arming
Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Thu 2023-11-16 07:31:49 CET; 10h ago
Main PID: 1074 (code=exited, status=1/FAILURE)
CPU: 0

Nov 16 07:31:49 Alma-9-latest-amd64-base systemd[1]: Starting Crash recovery kernel arming...
Nov 16 07:31:49 Alma-9-latest-amd64-base kdumpctl[1083]: kdump: No memory reserved for crash kernel
Nov 16 07:31:49 Alma-9-latest-amd64-base kdumpctl[1083]: kdump: Starting kdump: [FAILED]
Nov 16 07:31:49 Alma-9-latest-amd64-base systemd[1]: kdump.service: Main process exited, code=exited, status=1/FAILURE
Nov 16 07:31:49 Alma-9-latest-amd64-base systemd[1]: kdump.service: Failed with result 'exit-code'.
Nov 16 07:31:49 Alma-9-latest-amd64-base systemd[1]: Failed to start Crash recovery kernel arming.
, stderr:
 
kdump is not a Plesk service. From Plesk's perspective, it is not needed and can be disabled.

Would maybe checking some similar reports on platforms like
help?
 
Back
Top