Magento2: Command "queue:consumers:start" is not defined.

[DylanHopman]

Magento (*)

Magento 2.3.3

How to reproduce (*)

bin/magento queue:consumers:start product_action_attribute.update
However, if you look in the bin / magento list and scroll to the queue, you will only see the: list in it. consumer: start is not even listed here. If you do in manually, you get the following error:
`Command "queue:consumers:start" is not defined.

Did you mean one of these?
ce_mq:consumers:start
queue:consumers:list `

Expected result (*)

Updating the attributes, but not working.

Actual result (*)

`Command "queue:consumers:start" is not defined.

Did you mean one of these?
ce_mq:consumers:start
queue:consumers:list `

Extra issue (*)

Also bin/magento cron:run isn't working. Got the following error in it:
`
Command "queue:consumers:start" is not defined.
Did you mean one of these?
ce_mq:consumers:start
queue:consumers:list

Command "queue:consumers:start" is not defined.
Did you mean one of these?
ce_mq:consumers:start
queue:consumers:list

Command "queue:consumers:start" is not defined.
Did you mean one of these?
ce_mq:consumers:start
queue:consumers:list

Command "queue:consumers:start" is not defined.
Did you mean one of these?
ce_mq:consumers:start
queue:consumers:list `

[m2-assistant[bot]]

Hi @DylanHopman. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

  :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

:clock10: You can find the schedule on the Magento Community Calendar page.

:telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

:movie_camera: You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant[bot]]

Hi @engcom-Alfa. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• [ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and _stop verification process here_!

• [ ] 5. Add label Issue: Confirmed once verification is complete.

• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Alfa]

Hi @DylanHopman .
Unfortunately, we are not able to reproduce the issue on fresh 2.4-develop. Everything works as expected.

Manual testing scenario:

1. Configure Rabbit Mq (devdocs);
2. Run in console: bin/magento queue:consumers:start product_action_attribute.update
3. Update any product attribute;

Actual Result: :heavy_check_mark: An attribute was successfully updated

@DylanHopman Are you able to reproduce this issue on fresh 2.4-develop?
Thanks!

[DylanHopman]

@engcom-Alfa, thank you for answering. No we have a couple of websites, also websites on 2.3.3. But this is the first website we have this issue with. Is there an option to fix it, without updating?

[engcom-Alfa]

@DylanHopman Maybe this solution will help you https://github.com/magemojo/m2-ce-cron/issues/89#issuecomment-604938652

[DylanHopman]

Hi,

Thanks for your quick reply. Unfortunately it doesn't solve the problem :(

[hostep]

@DylanHopman: that ce_mq:consumers:start is strange. When I google it I end up on https://github.com/renatocason/magento2-module-mq, I suspect you have that one installed. Maybe that module is removing the default queue:consumers:start command (which is definitely available in a clean Magento 2.3.3 installation).

Anyway, I strongly believe this issue is because of some customisation done to your webshop, hope you can figure it out! 🙂

[DylanHopman]

Thank you @hostep ,

This fixed the issue for me:
bin/magento mod:dis Rcason_Mq Rcason_MqMysql
bin/magento se:di:co
bin/magento s:s:d nl_NL en_US -f
bin/magento c:f
bin/magento cron:run --group default
bin/magento cron:run

You helped me a lot, thanks 👍