Announcement

Collapse
No announcement yet.

Espo.ERROR: Uncaught Exception PDOException - on fresh installation

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Espo.ERROR: Uncaught Exception PDOException - on fresh installation

    Environment:
    OS: CENTOS7 (LEMP stack)
    NGINX: config attached
    Mariadb: 10.3
    PHP: 7.3
    ESPOCRM: 5.8.2 (current)
    Ownership and permissions are fine.

    FPM type: Unix socket (using default pool www with modified to nginx settings): config attached (delta from default)
    DB: created DB and user; granted priveleges; config is tested at the
    EspoCRM configuration: Followed espocrm server and nginx configurations
    Problem: Cannot pass the Install process. Test verification is fine (See attached file); Once INSTALL button is pushed I am gettting the error (See attached file).

    Please help

    tailf /opt/espocrm/data/logs/espo-2020-02-10.log:
    [2020-02-10 16:36:20] Espo.ERROR: Uncaught Exception PDOException: "SQLSTATE[HY000] [2002] No such file or directory" at /opt/espocrm/application/Espo/ORM/EntityManager.php line 158 {"exception":"[object] (PDOException(code: 2002): SQLSTATE[HY000] [2002] No such file or directory at /opt/espocrm/application/Espo/ORM/EntityManager.php:158)"} []
    [2020-02-10 16:36:20] Espo.ERROR: Uncaught Exception PDOException: "SQLSTATE[HY000] [2002] No such file or directory" at /opt/espocrm/application/Espo/ORM/EntityManager.php line 158 {"exception":"[object] (PDOException(code: 2002): SQLSTATE[HY000] [2002] No such file or directory at /opt/espocrm/application/Espo/ORM/EntityManager.php:158)"} []
    [2020-02-10 16:36:42] Espo.ERROR: Uncaught Exception PDOException: "SQLSTATE[HY000] [2002] No such file or directory" at /opt/espocrm/application/Espo/ORM/EntityManager.php line 158 {"exception":"[object] (PDOException(code: 2002): SQLSTATE[HY000] [2002] No such file or directory at /opt/espocrm/application/Espo/ORM/EntityManager.php:158)"} []

    Click image for larger version

Name:	wizard.gif
Views:	23
Size:	55.8 KB
ID:	55864
    Attached Files

  • #2
    Hello,
    I have tested EspoCRM v.5.8.2 installation on NGINX + MariaDB + PHP-FPM 7.3. It works good. It seems that MariaDB throws this error upon creating DB. Check please MariaDB error log file to get more info about the error. Also, check whether your DB user has proper permissions.

    Comment


    • #3
      Hello Maximus,

      thank you for your reply!
      This is very straight forward procedure:

      CREATE DATABASE espocrmdb ;
      CREATE USER 'crmuser'@'localhost' IDENTIFIED BY '********************' ;
      GRANT USAGE ON espocrmdb.* TO 'crmuser'@localhost IDENTIFIED BY '**********************';
      GRANT ALL privileges ON espocrmdb.* TO 'crmuser'@localhost;
      FLUSH PRIVILEGES;

      MariaDB [(none)]> SHOW GRANTS FOR 'crmuser'@localhost;
      +----------------------------------------------------------------------------------------------------------------+
      | Grants for crmuser@localhost |
      +----------------------------------------------------------------------------------------------------------------+
      | GRANT USAGE ON *.* TO 'crmuser'@'localhost' IDENTIFIED BY PASSWORD '********************************************' |
      | GRANT ALL PRIVILEGES ON `espocrmdb`.* TO 'crmuser'@'localhost' |
      +----------------------------------------------------------------------------------------------------------------+
      -----------------------------------

      Mariadb do not reveal any errors in the logs. Did you install it on CENTOS7.x ?
      Last edited by abaravia; 02-11-2020, 03:55 PM.

      Comment


      • #4
        I also set the logging mode in ESPO/data/config.php to "DEBUG". I got some errors (see attached). I would appreciate your help.
        Attached Files

        Comment


        • #5
          I have investigated a way of how the other EspoCRM users installed EspoCRM on CentOS 7 and noticed that there is no big difference with a way described in our manual. Try to test to install EspoCRM with root database user to make sure that this issue is 100% is not a DB user permission issue.

          Comment

          Working...
          X