• 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.

Recent content by Maximillian Schmidt

  1. M

    Resolved Internal error: Lock Manager error: 'No locks available'.

    Ended up contacting my VPS host who raised my numflock value. Now everything works fine for me - thanks for the help!
  2. M

    Resolved Internal error: Lock Manager error: 'No locks available'.

    CentOS 6.8 (Final)‬ on a Virtuozzo VPS. Checking the user_beancounters ("cat proc/user_beancounters") shows me the numflock value clipped a few times (200+ times). Rebooting the VPS and trying to update (Plesk Onyx 17.0.17 Update Nr. 7 to Update Nr. 11) again ends with the same error message and...
  3. M

    Resolved Internal error: Lock Manager error: 'No locks available'.

    Hey Plesk Community, just updated to Onyx and after two weeks I ran the first update (#9). After finishing the update I've tried to login but this error message keeps showing up: Message No locks available File Hierarchical.php Line 201 Type UnknownError Any ideas on how to fix this? Thanks...
See more
Back
Top