Open Jars-of-jam-Scheduler opened 2 years ago
I was told to launch a job worker with: APP_ENV=dev make start-job-worker
and make dev
but the command APP_ENV=dev make start-job-worker
shows:
make: *** No rule to make target 'start-job-worker'. Stop.
===> Well I've added it to my Makefile by taking a look at the repo in GitHub. It seems to work now. I don't know why the entry start-job-worker was lacking, I've never edited the Makefile
I am also facing this bug. No event logs are made whenever you create, delete or update a product.
Hi @ZAM-RV, did you well launch the job worker ?
=> APP_ENV=dev make start-job-worker
Hi @ZAM-RV, did you well launch the job worker ? =>
APP_ENV=dev make start-job-worker
Personnaly, I did.
Hi @ZAM-RV @Jars-of-jam-Scheduler and Akeneo Team I am facing the same issue. I have Akeneo running in Docker and have created a new Connection (using a https://beeceptor.com endpoint). The "Test" button on the "EVENT SUBSCRIPTION" tab returns a 200 OK. I have also kicked off the job worker (msg: '[OK] Consuming messages from transports "ui_job, import_export_job, data_maintenance_job".') and am able to run/download a CSV export job.
However, when updating the status of a product - which to my understanding is supposed to trigger an event - nothing happens. I've checked the "ERROR MONITORING" and "EVENT LOGS" tabs but there's no entry. I have also double checked that the "Event subscription activation" is enabled.
Anything else that I am missing to get my event subscription working? Or how can I debug this?
Thank you
So I found that I was missing the webhook
job in my updated Makefile. The added lines are:
.PHONY: start-job-worker start-job-worker: $(PHP_RUN) bin/console -vv messenger:consume webhook ui_job import_export_job data_maintenance_job ${O}
(note the webhook
)
:bug: I'm reporting a Bug :bug:
System > system info
Akeneo Community Edition 6.0.33 here.
You can find the file here: system_infos.txt .
Expected behavior
I create a destination connexion in the admin panel of Akeneo.
I go to the "Event Subscription" menu of this connexion.
I type in the URL field:
http://172.20.0.9/akeneo_events_receiver
, which is the URL I can use to call the Laravel route namedakeneo_events_receiver
, which is POST and currently running/available/callable. NB: Laravel is run with Docker by using Laravel Sailup
CLI command. Akeneo is run with Docker too. I didn't modify their default respective Docker network configuration option. It means that Laravel and Akeneo are on two different Docker networks.Then, after clicking on "SAVE" and "TEST" buttons, Akeneo accepts the URL I provide and shows the credentials (secret, etc.).
When I create a simple product (permissions = "User" and I use the default admin account), Akeneo should 1. log it into the "Event API logs" menu and 2. call my Laravel URL described above with the data.
Encountered behavior
The encountered behavior of Akeneo is: Akeneo doesn't log any event creation and doesn't call my Laravel app.
Steps to reproduce
They are all described in the "Expected behavior" section. However, here are some documentation links:
Question
Could you please tell me why Akeneo doesn't seem to generate an Event (nor log it and send it to my Laravel URL) when I create a simple product?
I thank you in advance and wish you a very good day!
Best regards, Stay safe.
Jars