Too little memory for the update

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • ChrisSka83
    Senior Member
    • Apr 2023
    • 209

    Too little memory for the update

    Hello everyone,
    I wanted to update to V9 now, but failed because of the memory limit, although this is actually set quite high for me.
    What else could be the problem?


    PHP Code:
     Allowed memory size of 134217728 bytes exhausted (tried to allocate 40443496 bytes) in /var/www/vhosts/EspoURL/application/Espo/Core/Console/Commands/Upgrade.php on line 294 
    
    Attached Files
  • Kharg
    Senior Member
    • Jun 2021
    • 428

    #2
    Are you updating using CLI?

    Usually you also have to set the CLI memory limits

    Comment

    • ChrisSka83
      Senior Member
      • Apr 2023
      • 209

      #3
      Yes, I only ever do this via the CLI.

      Where do I do that? So far I haven't had any problems via CLI.

      Comment

      • Kharg
        Senior Member
        • Jun 2021
        • 428

        #4
        There should be a php.ini related to CLI.

        if you can make a backup of your db and installation I would try to update from the GUI which is easier if you can’t change CLI limits.

        Comment

        • ChrisSka83
          Senior Member
          • Apr 2023
          • 209

          #5
          I already made the backups via CLI before the update attempt.

          I have just tried using the GUI. I got a different error message.

          Attached Files

          Comment

          • ChrisSka83
            Senior Member
            • Apr 2023
            • 209

            #6
            I was able to perform the update with the following command via CLI.

            While attempting to upgrade EspoCRM manually, I encountered an issue. The system prompts me to upgrade it via CLI. However, when I try to perform the upgrade through the CLI, it is showing " Downloading but it's not upgrading at all, it doesn’t proceed as expected. Could you please guide me on resolving this issue? Let me


            Unfortunately, my Espo distance cannot be called up. -> Error 500

            Comment


            • Kharg
              Kharg commented
              Editing a comment
              Remove CopyLeadNotes extension and update FileSharing to the latest version

            • ChrisSka83
              ChrisSka83 commented
              Editing a comment
              I only deactivated the two extensions under Administration, not deleted them. Then the update went through.
              But I can't find the extensions on the server to delete them permanently.
          • yuri
            Member
            • Mar 2014
            • 8540

            #7
            The upgrade package is almost 30 MB.
            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

            • ChrisSka83
              Senior Member
              • Apr 2023
              • 209

              #8
              I'm currently trying to delete these 2 extensions, that could be related to the error 500, at least that's what Kharg suspects.
              Hello everyone, I wanted to update to V9 now, but failed because of the memory limit, although this is actually set quite high for me. What else could be the problem? Allowed memory size of 134217728 bytes exhausted (tried to allocate 40443496 bytes) in /var/www/vhosts/EspoURL/application/Espo/Core/Console/Commands/Upgrade


              I can see them with the command bin/command extensions -l, but I cannot remove them with the command bin/command extension -u --name=“Extension Name”.

              Comment


              • victor
                victor commented
                Editing a comment
                Deleting by ID is more accurate, try it "bin/command extension -u --id="extension-ID"" after the command "bin/command extension -l"

              • ChrisSka83
                ChrisSka83 commented
                Editing a comment
                With Kharg's help, I found the extension that was causing the problems.

                It was the “Ebla PWA Mobile App & Notification” from Eblasoft
            Working...