Announcement

Collapse
No announcement yet.

(500) Cannot save settings after upgrading from 5.8 to 5.9.2

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

  • (500) Cannot save settings after upgrading from 5.8 to 5.9.2

    Hello,
    was running 5.8.x since a while and wanted to run the last version 5.9.2
    _from the GUI disable "cron" and set on the maintenance mode
    _ran the CLI php upgrade command (no error)
    _can access flawlessly to espocrm but ... unable to switch back the maintenance mode and cron !
    Espo log shown:
    [2020-06-12 19:48:17] Espo.ERROR: (500) Cannot save settings; PUT /espocrm/api/v1/Settings; line: 209, file: /var/www/html/espocrm/application/Espo/Services/Settings.php [] []

    cleared cache by cli command
    rebuitd database by cli command
    check index.php access right
    did not found anything, any help will be grandly appreciated

    have a goot week end
    Christophe

  • #2
    I forgot to mention that:
    _I installed also the last ubuntu 18 updates (so perhaps this has nothing to do with espocrm)
    _Machine was rebooted but this did not improve anything
    _all settings in the administration section are concerned (changes cannot be saved)
    Last edited by chr1st0ph9; 06-12-2020, 08:29 PM.

    Comment


    • #3
      Reading the log deeper, gave this information
      [2020-06-12 19:32:03] Espo.WARNING: E_WARNING: rename(data/config.php): failed to open stream: Permission denied {"code":2,"message":"rename(data/config.php): failed to open stream: Permission denied"

      looking into the data directory
      drwxrwxr-x 3 www-data www-data 4096 Jun 12 22:08 cache
      -rw-rw-r-- 1 root root 7487 Jun 12 21:52 config.php <<< ????????

      Changing the access right for config.php like following
      -rw-rw-r-- 1 www-data www-data 7489 Jun 12 22:42 config.php
      solved the problem :-)

      if anybody has an idea why/how a permission problem appeared with the config.php file, I would be glad to have it ...
      Best Regards,
      Christophe



      Comment


      • #4
        It seems that during upgrade, an owner for config.php was changed to root. It should not happen, Espo should change owner to www-data if everything is configured right. Not sure why it didn't work for you.

        As a workaround, for the next time, you can run upgrade under www-data user.

        Comment


        • #5
          Merci Yuri for your answer!
          I had a look into the last backup before upgrade, the data/config.php was already owned by root but with 666 permissions.
          Meilleures salutations,
          Christophe

          Comment

          Working...
          X