-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: There are no commands defined in the "cache" namespace. #22
Comments
@fabiorleal The composer installation sometimes ends up with a messed up auto loader which requires another |
@phoenix-bjoern, thanks for the response. ❯ kl -f cronjob-f78599b78-56wt7 -c cronjob
2024-08-13 12:19:03,176 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message.
2024-08-13 12:19:03,193 INFO supervisord started with pid 1
2024-08-13 12:19:04,217 INFO spawned: 'deploy' with pid 7
2024-08-13 12:19:04,253 INFO spawned: 'cronjob' with pid 8
******************************
2024-08-13 12:19:04,310 INFO success: deploy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
** nginx server_name SETUP ***
******************************
******************************
******* POSTFIX SETUP ********
******************************
Forwarding all emails to smtp.office365.com
without any authentication. Make sure your server is configured to accept emails coming from this IP.
******************************
******* PHP SETUP ************
******************************
2024-08-13 12:19:05,735 INFO success: cronjob entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
postfix/postlog: starting the Postfix mail system
[2024-08-13T12:19:08.848212+00:00] INFO: Starting scenario(s): scenario/deploy.xml, vendor/phoenix-media/magento2-ece-tools/scenario/deploy/custom-mode-config.xml (magento/ece-tools version: 2002.1.17, magento/magento2-base version: 2.4.6-p4)
[2024-08-13T12:19:09.599346+00:00] NOTICE: Starting pre-deploy.
[2024-08-13T12:19:09.601511+00:00] INFO: Set "env_file_absence" flag
[2024-08-13T12:19:09.614656+00:00] INFO: Set flag: var/.env_file_absence
[2024-08-13T12:19:09.738946+00:00] INFO: Updating cache configuration.
[2024-08-13T12:19:09.739911+00:00] INFO: Skip copying directory ./var/view_preprocessed.
[2024-08-13T12:19:09.740025+00:00] INFO: Clearing ./var/view_preprocessed
[2024-08-13T12:19:09.821049+00:00] WARNING: [2026] Cannot copy directory /var/www/html/init/app/etc. Directory does not exist.
[2024-08-13T12:19:09.852610+00:00] WARNING: [2026] Cannot copy directory /var/www/html/init/pub/media. Directory does not exist.
2024-08-13 12:19:09,853 INFO reaped unknown pid 99 (exit status 0)
[2024-08-13T12:19:09.857432+00:00] WARNING: [2026] Cannot copy directory "". Directory does not exist.
[2024-08-13T12:19:09.859095+00:00] NOTICE: Recoverable directories were copied back.
[2024-08-13T12:19:09.859783+00:00] INFO: Set Magento application mode to 'production'
[2024-08-13T12:19:09.860498+00:00] INFO: Step "clean-redis-cache" was skipped
[2024-08-13T12:19:09.860632+00:00] NOTICE: End of pre-deploy.
[2024-08-13T12:19:09.860843+00:00] INFO: Step "enable-maintenance-mode" was skipped
[2024-08-13T12:19:09.861038+00:00] INFO: Disable cron
[2024-08-13T12:19:09.861664+00:00] INFO: Trying to kill running cron jobs and consumers processes
[2024-08-13T12:19:09.876888+00:00] INFO: Running Magento cron and consumers processes were not found.
[2024-08-13T12:19:09.877279+00:00] NOTICE: Validating configuration
[2024-08-13T12:19:09.880593+00:00] INFO: Checking if db exists and has tables
[2024-08-13T12:19:10.075988+00:00] NOTICE: Fix configuration with given suggestions:
[2024-08-13T12:19:10.076236+00:00] NOTICE: Can't validate version of some services: The command "redis-cli -p 6379 -h redis-master info | grep redis_version" failed. sh: redis-cli: not found
[2024-08-13T12:19:10.076425+00:00] WARNING: [2005] The following admin data is required to create an admin user during initial installation only and is ignored during upgrade process: admin email, admin login, admin first name, admin last name, admin password
[2024-08-13T12:19:10.078552+00:00] WARNING: Can't validate version of some services: The command "dpkg -s rabbitmq-server | grep Version" failed. sh: dpkg: not found
[2024-08-13T12:19:10.078718+00:00] WARNING: Can't validate version of some services: The command "redis-cli -p 6379 -h redis-master info | grep redis_version" failed. sh: redis-cli: not found
[2024-08-13T12:19:10.078831+00:00] NOTICE: End of validation
[2024-08-13T12:19:10.079344+00:00] INFO: Checking existence of encryption key
[2024-08-13T12:19:10.079763+00:00] INFO: Setting encryption key from CRYPT_KEY
[2024-08-13T12:19:10.080600+00:00] INFO: Checking if db exists and has tables
[2024-08-13T12:19:10.085725+00:00] INFO: Magento was installed on Tue, 13 Aug 2024 12:19:09 +0000
[2024-08-13T12:19:10.085993+00:00] WARNING: [2020] Magento state indicated as installed but configuration file app/etc/env.php was empty or did not exist. Required data will be restored from environment configurations and from .magento.env.yaml file.
[2024-08-13T12:19:10.088572+00:00] NOTICE: Starting update.
[2024-08-13T12:19:10.088715+00:00] INFO: Updating env.php.
[2024-08-13T12:19:10.089394+00:00] INFO: Updating env.php cron consumers runner configuration.
[2024-08-13T12:19:10.090526+00:00] INFO: Updating env.php DB connection configuration.
[2024-08-13T12:19:10.091707+00:00] INFO: Updating env.php AMQP configuration.
[2024-08-13T12:19:10.092543+00:00] INFO: redis will be used for session if it was not override by SESSION_CONFIGURATION
[2024-08-13T12:19:10.092771+00:00] INFO: Updating session configuration.
[2024-08-13T12:19:10.093135+00:00] INFO: Updating search engine configuration.
[2024-08-13T12:19:10.093250+00:00] INFO: Set search engine to: elasticsearch7
[2024-08-13T12:19:10.094359+00:00] INFO: Skipping URL updates because the URL_UPDATES variable is set to false.
[2024-08-13T12:19:10.094556+00:00] INFO: The value of the property 'directories/document_root_is_pub' set as 'true'
[2024-08-13T12:19:10.095874+00:00] INFO: The lock provider "db" was set.
[2024-08-13T12:19:10.096745+00:00] INFO: Updating env.php backend front name.
[2024-08-13T12:19:10.097401+00:00] INFO: Flushing cache.
[2024-08-13T12:19:13.591800+00:00] INFO: Set flag: var/.deploy_is_failed
[2024-08-13T12:19:13.592078+00:00] ERROR: [127] The command "php ./bin/magento cache:flush --ansi --no-interaction" failed.
There are no commands defined in the "cache" namespace.
In Processor.php line 129:
The command "php ./bin/magento cache:flush --ansi --no-interaction" failed.
There are no commands defined in the "cache" namespace.
In InstallUpdate.php line 100:
The command "php ./bin/magento cache:flush --ansi --no-interaction" failed.
There are no commands defined in the "cache" namespace.
In CleanCache.php line 75:
The command "php ./bin/magento cache:flush --ansi --no-interaction" failed.
There are no commands defined in the "cache" namespace.
In Shell.php line 86:
The command "php ./bin/magento cache:flush --ansi --no-interaction" failed.
There are no commands defined in the "cache" namespace.
run <scenario>...
Deployment failed. Exiting.
2024-08-13 12:19:13,766 INFO exited: deploy (exit status 0; expected)
failed to create fsnotify watcher: too many open files I also tried to install it using the command |
Hey Phoenix-Media Team(@phoenix-bjoern or @phoenix-henri), very nice work creating the tutorial and these repos, but...
Summary:
I have been trying to install Magento2 for a few weeks now and have had no success so far.
I am trying to deploy magento2 on premise K8s clsuter, following Running Magento2 in Kubernetes - part 2 and Running Magento2 in Kubernetes - part 3 articles.
Some changes I had to make were:
Error:
Cronjob Pod is not coming up on deploying using this magento2-helm chart, getting error in pod logs:
Steps followed:
1 - Followed Running Magento2 in Kubernetes — Part 2: Building the Docker Image and Magento2 container build pipeline for building the docker image.
2 - Configured the values.yaml file with with bellow values and passed the env variables values in base64.
Significant changes:
3 - Deployed the helm chart with the values.yaml
The text was updated successfully, but these errors were encountered: