8.3 mysql error

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • fernando.giacomino
    Junior Member
    • Jul 2022
    • 23

    8.3 mysql error

    Hi! I´ve update EspoCRM from 8.2.5 to 8.3 version with command.sh upgrade, in docker installation. All fine, but mysql container stay restarting. Log error seems like upgrade don't add new feature column into my custom entity "Pedido":

    CRITICAL: (42S22) SQLSTATE[42S22]: Column not found: 1054 Unknown column 'user.avatar_color' in 'field list' :: GET /Pedido :: /var/www/html/application/Espo/ORM/Executor/DefaultSqlExecutor.php(77)

    Also another error that don't know where to fix is:

    WARNING: Cron is not run because it's disabled with 'cronDisabled' param.

    Runing Ubuntu Server
  • victor
    Active Community Member
    • Aug 2022
    • 727

    #2
    Regarding the first error:
    Please tell me if you tried make Hard Rebuild: https://docs.espocrm.com/administration/commands/#hard-rebuild?

    Regarding the second error:
    In /data/config.php check cronDisabled. Must be​ 'cronDisabled' => false

    Comment

    • fernando.giacomino
      Junior Member
      • Jul 2022
      • 23

      #3
      Thanks Victor! Actually cronDisabled is set to "false" in config.php, and trying "hard rebuild" falls in another error, while espo-mysql container keep restarting:

      SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo for espocrm-mysql failed: Temporary failure in name resolution

      I think will restore to backup and try clean before upgrade?

      Comment

      • esforim
        Active Community Member
        • Jan 2020
        • 2204

        #4
        Try disabling some of your extension, previously I got a similar error due to an 'outdated' extension.

        Comment

        • fernando.giacomino
          Junior Member
          • Jul 2022
          • 23

          #5
          Don't have extensions, just some customization. Is second time I run on this error, my fault for no make database dump. I've made regular upgrades succesfully and just "trust" (yes, I know...) that no error will appears. Maybe adding dump function to command.sh script or (better) in auto-backup process that runs before upgrade in the future will avoid dumbs like me lose his data.
          Last edited by fernando.giacomino; 06-22-2024, 01:52 PM.

          Comment

          Working...