• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Search results

  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...
Back
Top