Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-24025

Error when installing ezpublish from ezpublish_platform

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Blocker Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: QA tracked issues
    • Component/s: Install
    • Labels:
      None
    • Environment:

      Operating System: CentOS 7.0 x64
      PHP Version: 5.4.16
      Database and version: Mariadb 5.5
      Browser (and version): Firefox 35

    • Sprint:
      Pollux Platform S6

      Description

      Hi,
      Currently, it's not possible to install ezpublish from ezpublish_platform repository due errors explain below in "Steps to reproduce"

      Steps to reproduce

      Fetch ezpublish from ezpublish_platform repository
      Get composer.phar and do composer install

      – $ git clone git@github.com:ezsystems/ezpublish-platform.git ezpublish5
      – $ cd ezpublish5
      – $ curl -sS https://getcomposer.org/installer | php
      – $ php -d memory_limit=-1 composer.phar install --prefer-dist --no-dev

      In the end, execute the permissions and assetics
      – $ sudo setfacl -R -m u:apache:rwx -m u:apache:rwx ezpublish/

      {cache,logs,config,sessions} ezpublish_legacy/{design,extension,settings,var} web
      – $ sudo setfacl -dR -m u:apache:rwx -m u:`whoami`:rwx ezpublish/{cache,logs,config,sessions}

      ezpublish_legacy/

      {design,extension,settings,var} web

      In the two previous commands,i have had the error

      setfacl: ezpublish_legacy/design: No such file or directory
      setfacl: ezpublish_legacy/settings: No such file or directory
      setfacl: ezpublish_legacy/var: No such file or directory
      



      So, to move on, I adapted, removing the "ezpublish_legacy/{design,extension,settings,var}

      " of the previous commands:

      Then I continued:
      – $ php ezpublish/console assets:install --symlink web
      – $ php ezpublish/console ezpublish:legacy:assets_install --symlink web
      Here, i have the following error

        [InvalidArgumentException]
        There are no commands defined in the "ezpublish:legacy" namespace.
        Did you mean one of these?
            ezpublish:test
            ezpublish
      

      So i proceed without this last one and executed the following one:
      – $ php ezpublish/console assetic:dump --env=prod web

      Then i tried to execute the setup wizard and i have in prod.log

      [2015-02-13 19:25:29] app.NOTICE: Siteaccess not matched against configuration, returning default siteaccess. [] []
      [2015-02-13 19:25:29] app.DEBUG: Router eZ\Bundle\EzPublishCoreBundle\Routing\DefaultRouter was not able to match, message "" [] []
      [2015-02-13 19:25:29] request.CRITICAL: Uncaught PHP Exception eZ\Bundle\EzPublishCoreBundle\ApiLoader\Exception\InvalidRepositoryException: "Undefined repository ''. Did you forget to configure it in ezpublish_*.yml?" at /var/www/html/ezpublish5/vendor/ezsystems/ezpublish-kernel/eZ/Bundle/EzPublishCoreBundle/ApiLoader/StorageRepositoryProvider.php line 54 {"exception":"[object] (eZ\\Bundle\\EzPublishCoreBundle\\ApiLoader\\Exception\\InvalidRepositoryException(code: 0): Undefined repository ''. Did you forget to configure it in ezpublish_*.yml? at /var/www/html/ezpublish5/vendor/ezsystems/ezpublish-kernel/eZ/Bundle/EzPublishCoreBundle/ApiLoader/StorageRepositoryProvider.php:54)"} []
      

        Issue Links

          Activity

          Hide
          André Rømcke added a comment -
          Show
          André Rømcke added a comment - (Same) Commit back in, with additional fix: https://github.com/ezsystems/ezpublish-kernel/commit/f7db9f7cb2d122f8a0947128e8b456cf2ad11060
          Hide
          Paulo Nunes (Inactive) added a comment -

          Retried the process again and the previous error message no longer appear, but others do:
          during the composer command to create the project, i have had the following info that didn't appear yesterday:

          Package guzzle/common is abandoned, you should avoid using it. Use guzzle/guzzle instead.
          Package guzzle/stream is abandoned, you should avoid using it. Use guzzle/guzzle instead.
          Package guzzle/parser is abandoned, you should avoid using it. Use guzzle/guzzle instead.
          Package guzzle/http is abandoned, you should avoid using it. Use guzzle/guzzle instead.
          

          And in the end, after all instructions done, when i try to access my local installation, i have a "500 Internal Server Error" and in prod.log i have:

          [2015-02-25 09:53:21] app.NOTICE: Siteaccess not matched against configuration, returning default siteaccess. [] []
          [2015-02-25 09:53:22] app.DEBUG: Router eZ\Bundle\EzPublishCoreBundle\Routing\DefaultRouter was not able to match, message "" [] []
          [2015-02-25 09:53:23] request.CRITICAL: Uncaught PHP Exception eZ\Bundle\EzPublishCoreBundle\ApiLoader\Exception\InvalidRepositoryException: "Undefined repository ''. Did you forget to configure it in ezpublish_*.yml?" at /var/www/html/ezpublish5/vendor/ezsystems/ezpublish-kernel/eZ/Bundle/EzPublishCoreBundle/ApiLoader/StorageRepositoryProvider.php line 54 {"exception":"[object] (eZ\\Bundle\\EzPublishCoreBundle\\ApiLoader\\Exception\\InvalidRepositoryException(code: 0): Undefined repository ''. Did you forget to configure it in ezpublish_*.yml? at /var/www/html/ezpublish5/vendor/ezsystems/ezpublish-kernel/eZ/Bundle/EzPublishCoreBundle/ApiLoader/StorageRepositoryProvider.php:54)"} []
          

          Manually clearing the caches, i no longer have the previous error in prod.log and already can access the frontend

          Show
          Paulo Nunes (Inactive) added a comment - Retried the process again and the previous error message no longer appear, but others do: during the composer command to create the project, i have had the following info that didn't appear yesterday: Package guzzle/common is abandoned, you should avoid using it. Use guzzle/guzzle instead. Package guzzle/stream is abandoned, you should avoid using it. Use guzzle/guzzle instead. Package guzzle/parser is abandoned, you should avoid using it. Use guzzle/guzzle instead. Package guzzle/http is abandoned, you should avoid using it. Use guzzle/guzzle instead. And in the end, after all instructions done, when i try to access my local installation, i have a "500 Internal Server Error" and in prod.log i have: [2015-02-25 09:53:21] app.NOTICE: Siteaccess not matched against configuration, returning default siteaccess. [] [] [2015-02-25 09:53:22] app.DEBUG: Router eZ\Bundle\EzPublishCoreBundle\Routing\DefaultRouter was not able to match, message "" [] [] [2015-02-25 09:53:23] request.CRITICAL: Uncaught PHP Exception eZ\Bundle\EzPublishCoreBundle\ApiLoader\Exception\InvalidRepositoryException: "Undefined repository ''. Did you forget to configure it in ezpublish_*.yml?" at /var/www/html/ezpublish5/vendor/ezsystems/ezpublish-kernel/eZ/Bundle/EzPublishCoreBundle/ApiLoader/StorageRepositoryProvider.php line 54 {"exception":"[object] (eZ\\Bundle\\EzPublishCoreBundle\\ApiLoader\\Exception\\InvalidRepositoryException(code: 0): Undefined repository ''. Did you forget to configure it in ezpublish_*.yml? at /var/www/html/ezpublish5/vendor/ezsystems/ezpublish-kernel/eZ/Bundle/EzPublishCoreBundle/ApiLoader/StorageRepositoryProvider.php:54)"} [] Manually clearing the caches, i no longer have the previous error in prod.log and already can access the frontend
          Hide
          André Rømcke added a comment - - edited

          Returning to this subject, what workaround do you currently need to use to install master?
          Anything besides clearing cache? And if so did you perform the install command using --env=prod ?

          Side note: "guzzle/" warnings can be ignored.

          Show
          André Rømcke added a comment - - edited Returning to this subject, what workaround do you currently need to use to install master? Anything besides clearing cache? And if so did you perform the install command using --env=prod ? Side note: "guzzle/" warnings can be ignored.
          Hide
          Paulo Nunes (Inactive) added a comment -

          The installation is done using the updated readme.md instructions. The only workaround is to manually clearing caches in the end.

          Show
          Paulo Nunes (Inactive) added a comment - The installation is done using the updated readme.md instructions. The only workaround is to manually clearing caches in the end.
          Hide
          André Rømcke added a comment -

          Closing as fixed, the remaining issue regarding clearing caches is QA system specific and needs to be reported separately with details on which cache is causing the issue.

          Show
          André Rømcke added a comment - Closing as fixed, the remaining issue regarding clearing caches is QA system specific and needs to be reported separately with details on which cache is causing the issue.

            People

            • Assignee:
              Unassigned
              Reporter:
              Paulo Nunes (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Agile