Articles in this section

See more

Plesk backup fails: Unable to back up applications packages. Error: ODBC error #28000: [ma-3.1.20]Access denied for user 'apsc'@'127.0.0.1' (using password: YES)

Avatar
Gabriel Aznarez
Updated
Follow
kb: bug Plesk for Linux

Symptoms

  • On a Plesk for Linux server with MariadDB 10.11, creating a backup in Plesk fails:

    Unable to back up applications packages. Error: ODBC error #28000: [ma-3.1.20]Access denied for user 'apsc'@'127.0.0.1' (using password: YES)

  • Using the utility plesk repair db does not help.

  • No corruption of the Plesk database apsc is found using manual methods.

  • Attempt to access domain in Plesk may result into:

    TypeError: Cannot read properties of null (reading 'id')

  • Backup logs returns an error:

    [2024-08-08 08:54:44.306|724517] WARN [panel] Unable to back up applications packages.
    [2024-08-08 08:54:44.307|724517] WARN [panel] Exception: ODBC error #28000: [ma-3.1.20]Access denied for user 'apsc'@'127.0.0.1' (using password: YES)
    file: /usr/local/psa/admin/plib/backup/Agent/Dumper/ApplicationVaultInfo.php
    line: 90
    code: 0
    trace: #0 /usr/local/psa/admin/plib/backup/Agent/Dumper/ApplicationVaultInfo.php(90): APS_Registry_PackageBrowser->browse()
    1 /usr/local/psa/admin/plib/backup/Agent/CallHelper.php(50): Plesk\backup\Agent\Dumper\ApplicationVaultInfo->getPackages()
    2 /usr/local/psa/admin/plib/backup/Agent/Dumper/ApplicationVaultInfo.php(50): Plesk\backup\Agent\Dumper\Base->iterateSafely(object of type Generator, object of type Closure, object of type Closure)
    3 /usr/local/psa/admin/plib/backup/Agent/Dumper/ServerInfo.php(249): Plesk\backup\Agent\Dumper\ApplicationVaultInfo->getPackagesInfo()
    4 /usr/local/psa/admin/plib/backup/Agent/CallHelper.php(20): Plesk\backup\Agent\Dumper\ServerInfo->Plesk\backup\Agent\Dumper{closure}()
    5 /usr/local/psa/admin/plib/backup/Agent/Dumper/ServerInfo.php(246): Plesk\backup\Agent\Dumper\Base->callSafely(object of type Closure, string 'Unable to back up applications packages.')
    6 /usr/local/psa/admin/plib/backup/Agent/Dumper/ServerInfo.php(57): Plesk\backup\Agent\Dumper\ServerInfo->backupApplicationVault(object of type Plesk\backup\Agent\Schema\Backup\Server)
    7 /usr/local/psa/admin/plib/backup/Agent/Dumper/Server.php(42): Plesk\backup\Agent\Dumper\ServerInfo->getServerInfoDump()

  • One of following errors can be found at /var/log/plesk/panel.log:

    ERR [panel] ODBC error #28000: [ma-3.1.20]Plugin caching_sha2_password could not be loaded: /usr/lib/mariadb/plugin/caching_sha2_password.so: cannot open shared object file: No such file or directory 

    ERR [panel] ODBC error #28000: [unixODBC][ma-3.1.20]Access denied for user 'apsc'@'127.0.0.1' (using password: YES)

Cause

Plesk bug PPPM-14535.

Resolution

Until the bug is fixed, use the workaround:

  1. Connect to the Plesk server using SSH.

  2. Open the MariaDB configuration file with an editor:

    • On RHEL/CentOS/AlmaLinux/Rocky Linux/CloudLinux:

      /etc/my.cnf

    • On Ubuntu and Debian:

      /etc/mysql/my.cnf or /etc/mysql/mariadb.conf.d/50-server.cnf

  3. Remove or comment out (by preceding the line with an # ) the parameter skip-name-resolve or skip_name_resolveand save the file.

  4. Restart MariaDB:

    # service mariadb restart

Comments

2 comments

Sort by Date Votes
  • Avatar
    B3 Support (Edited )

    We have skip_name_resolve added to /etc/mysql/mariadb.conf.d/50-server.cnf 

    and restarted mariadb server.

     

    Then we have started an manual Backup only with configuration. The issue still exists.

    Using MariaDB 10.3.x

     

    0
    Comment actions Permalink
  • Avatar
    B3 Support

    The following workaround solved the problem for us:

    show create user `apsc`@`localhost`;

    Create a new user with host 127.0.0.1

    CREATE USER `apsc`@`127.0.0.1` IDENTIFIED BY PASSWORD 'PASSWORD_FROM_CREATE_USER';

    Show the grants of apsc

    show grants for 'apsc'@'localhost';

    Grant the same privileges to new user:

    GRANT USAGE ON *.* TO `apsc`@`127.0.0.1`;
    GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, REFERENCES, INDEX, ALTER, CREATE TEMPORARY TABLES, LOCK TABLES, EXECUTE, CREATE VIEW, SHOW VIEW, CREATE ROUTINE, ALTER ROUTINE, EVENT, TRIGGER ON `apsc`.* TO `apsc`@`127.0.0.1`;
    flush privileges;

    Now the backup is working again.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles