Rebuild fail upon upgrade to 7.2

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • tobias
    Senior Member
    • May 2016
    • 229

    Rebuild fail upon upgrade to 7.2

    I'm afraid I cannot install the upgrade, tried three times now:

    Code:
    # php upgrade.php EspoCRM-upgrade-5.6.14-to-5.7.2.zip
    Current version is 5.6.14
    Starting upgrade process...
    Error: Error occurred while EspoCRM rebuild.
    #:/home/site/wwwroot#
    Any ideas and/or suggestions?
  • yuri
    Member
    • Mar 2014
    • 8521

    #2
    Try to figure out why rebuild is not working. Try just running rebuild, check logs.
    If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.

    Comment

    • tobias
      Senior Member
      • May 2016
      • 229

      #3
      The rebuild was completed just fine, i.e. no errors in the log. Will try to upgrade again now and circle back.

      Comment

      • tobias
        Senior Member
        • May 2016
        • 229

        #4
        Couldn't pm you, hence need to post the log here, sorry. Any ideas what's going on during upgrade?
        Attached Files

        Comment

        • Maximus
          Senior Member
          • Nov 2018
          • 2731

          #5
          Hello Tobias,
          Could you tell us the next information:
          1. Is it a full error log file?
          2. When have you tried to upgrade for the first time? We need a log file of the first day of upgrade attempts
          3. Which is the current EspoCRM version shown in Administration -> Upgrade?
          4. Is the main Stream logs still shows you the notification?
          5. Which user is owner of all directories and files?
          6. Under which user you had run the upgrade command?

          Comment

          • tobias
            Senior Member
            • May 2016
            • 229

            #6
            1. No, just the part that includes the time frame of the upgrade attempt.
            2. Today, after two other successful upgrades: 5.6.12 to 5.6.13 and 5.6.13 to 5.6.14 - both went fine.
            3. That said, it's obviously version 5.6.14 showing in Administration > Upgrade.
            4. Not sure what you mean by that.
            5. User is nobody (we're on Linux in Docker) and since prior upgrades + rebuild works just fine, I think the user is not the issue.
            6. root

            UPDATE:
            An error that is added to the log on a regular basis now is the following:
            Code:
            [2019-10-15 10:00:24] Espo.ERROR: Hook class '\Espo\Hooks\Common\Webhook' does not exist. [] []
            Last edited by tobias; 10-15-2019, 10:01 AM.

            Comment

            • Maximus
              Senior Member
              • Nov 2018
              • 2731

              #7
              Thank you for your fast reply.
              > 4. Not sure what you mean by that.
              We need to know whether you are receiving some errors message in the log file upon you are viewing the Stream dashlet?
              The same thing we need to now whether you are receiving some errors message in the log file upon you are viewing the Opportunity list view?

              Comment

              • tobias
                Senior Member
                • May 2016
                • 229

                #8
                No errors on any of these pages:



                The only error we see every ~5 seconds in the log now is this one:
                [2019-10-15 10:08:17] Espo.ERROR: Hook class '\Espo\Hooks\Common\Webhook' does not exist. [] []

                Comment

                • tobias
                  Senior Member
                  • May 2016
                  • 229

                  #9
                  And every now and then, the following error appears in the log file:
                  [2019-10-15 10:22:37] Espo.WARNING: E_WARNING: get_class() expects parameter 1 to be object, null given {"code":2,"message":"get_class() expects parameter 1 to be object, null given","file":"/home
                  /site/wwwroot/application/Espo/ORM/Repositories/RDB.php","line":68,"context":{"entityType":"Dashbo ardTemplate","entityManager":"[object] (Espo\\Core\\ORM\\EntityManager: {})","entityFactory":"[obj
                  ect] (Espo\\ORM\\EntityFactory: {})"}} []

                  Comment

                  • Maximus
                    Senior Member
                    • Nov 2018
                    • 2731

                    #10
                    Please try to make these steps:
                    1. In a terminal under the root user run the command
                    Code:
                    php rebuild.php
                    2. In a terminal under the root user run the command
                    Code:
                    php upgrade.php <path-to-upgrade-pack
                    3. Change the owner of the all directories and files to the web server user.

                    Comment

                    • tobias
                      Senior Member
                      • May 2016
                      • 229

                      #11
                      This is exactly what I did - except for point 3, which I don't really see a reason for, since all other upgrades worked just fine. Can you explain the reason for point 3?

                      Comment

                      • Maximus
                        Senior Member
                        • Nov 2018
                        • 2731

                        #12
                        For the proper work of the EspoCRM functionality, the owner of the directories and files should be correct.

                        Comment

                        • tobias
                          Senior Member
                          • May 2016
                          • 229

                          #13
                          With docker, you will always have the owner of the directories and files set to nobody, which is ok and wasn't a problem with Espo ever since we're having this environment. It has to be something else.

                          Comment

                          • tobias
                            Senior Member
                            • May 2016
                            • 229

                            #14
                            As expected, it wasn't related to the user, yet to a faulty installation of an extension. Here's what I did:

                            Code:
                            db1abe1118b2:/home/site/wwwroot# php rebuild.php
                            db1abe1118b2:/home/site/wwwroot# php extension.php advanced-pack-2.4.0.zip
                            Starting installation process...
                            Extension installation is complete.
                            db1abe1118b2:/home/site/wwwroot# php extension.php sales-pack-1.0.6.zip
                            Starting installation process...
                            Extension installation is complete.
                            db1abe1118b2:/home/site/wwwroot# php upgrade.php EspoCRM-upgrade-5.6.14-to-5.7.2.zip
                            Current version is 5.6.14
                            Starting upgrade process...
                            Upgrade is complete. Current version is 5.7.2.
                            db1abe1118b2:/home/site/wwwroot#
                            Maximus All good now, thanks still for taking the time.

                            Comment

                            Working...