Error "Unable to connect to database: mysql_connect(): No such file or directory (Error code:)" en Plesk 12.5 en Ubuntu 14.04

Created:

2016-11-16 13:05:29 UTC

Modified:

2017-08-16 17:31:30 UTC

2

Was this article helpful?


Have more questions?

Enviar una solicitud

Error "Unable to connect to database: mysql_connect(): No such file or directory (Error code:)" en Plesk 12.5 en Ubuntu 14.04

Applicable to:

  • Plesk 12.5 for Linux

Síntomas

  1. Una vez instalado Plesk y reiniciado el servidor, MySQL no puede iniciarse:

    ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock'(2) exit status 1
  2. En el archivo /var/log/mysql/error.log se aprecia el siguiente error:

    InnoDB: Unable to lock ./ibdata1, error: 11
    InnoDB: Check that you do not already have another mysqld process
    InnoDB: using the same InnoDB data or log files.
    InnoDB: Unable to open the first data file
    InnoDB: Error in opening ./ibdata1
    InnoDB: Operating system error number 11 in a file operation.
    InnoDB: Error number 11 means 'Resource temporarily unavailable'.
    InnoDB: Some operating system error numbers are described at
    InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html
    InnoDB: Could not open or create data files.
    InnoDB: If you tried to add new data files, and it failed here,
    InnoDB: you should now edit innodb_data_file_path in my.cnf back
    InnoDB: to what it was, and remove the new ibdata files InnoDB created
    InnoDB: in this failed attempt. InnoDB only wrote those files full of
    InnoDB: zeros, but did not yet use them in any way. But be careful: do not
    InnoDB: remove old data files which contain your precious data!
    [ERROR] Plugin 'InnoDB' init function returned error.
    [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
    [ERROR] Unknown/unsupported storage engine: InnoDB
    [ERROR] Aborting

Causa

Se trata de un problema de software interno de Plesk con ID #PPPM-3284 . Este se corrigió en Plesk 12.5 MU #5.

Resolución

Aplique las microactualizaciones más recientes:

# plesk installer --select-release-current --reinstall-patch --install-component base
¿Tiene más preguntas? Enviar una solicitud
Inicie sesión para dejar un comentario.