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

  1. D

    Question Failed to start MariaDB 10 database server

    I followed the steps in the link, the mariadb service was fixed, but it gives the following error. 500 Plesk\Exception\Database DB query failed: SQLSTATE[HY000] [1049] Unknown database 'psa'
  2. D

    Question Failed to start MariaDB 10 database server

    I do not have this directory. /var/log/mysql/error.log /var/log/mysql/mysql.log /usr/sbin/mysqld, Version: 10.1.48-MariaDB-0+deb9u2 (Debian 9.13). started with: Tcp port: 3306 Unix socket: /var/run/mysqld/mysqld.sock Time Id Command Argument /usr/sbin/mysqld, Version...
  3. D

    Question Failed to start MariaDB 10 database server

    -- Logs begin at Mon 2023-05-01 10:05:13 +03, end at Mon 2023-05-01 10:33:38 +03. -- May 01 10:05:14 server.abc.com systemd[1]: Starting MariaDB 10.1.48 database server... May 01 10:05:15 server.abc.com mysqld[1796]: 2023-05-01 10:05:15 140621889342848 [Note] /usr/sbin/mysqld (mysqld...
  4. D

    Question Failed to start MariaDB 10 database server

    Server Error 500 Plesk\Exception\Database DB query failed: SQLSTATE[HY000] [2002] No such file or directory
  5. D

    Question Failed to start MariaDB 10 database server

    Unable to start mariadb service. when i tried to repair the result did not change. The first cause of the problem was that mariadb could not be started because the server disk capacity was full. After deleting the logs, disk space was freed, but mysqld.sock continued to give an error because...
Back
Top