Hi All, thanks in advance for the help. I’m deploying my rasa chatbot using rasa x, i update to the latest version of rasa x 0.26.3. When i write to the bot, in rest channel or rasa interface, the tracker db is update and works well, but rasa x not save the conversation, that is, on conversation_event table nothing is inserted, other things on rasa x seem to works correctly, so what can be a solution?
Are you using the
docker-compose based deployment? The tracker information is passed from Rasa to Rasa X via a rabbit message queue. A
docker-compose ps should show a rabbit container is running.
You should also look at the Rasa X log for errors,
docker-compose logs rasa-x. If you don’t see anything there, view all logs with
Thanks for the reply Greg,
Yes, i use the docker-compose based deployment, the enviroment was created using “Docker-Compose Manual Install” guide. Before i run Rasa (1.6.2) and Rasa X (0.25.2) and everything works well, then i update with the latest version and the issue was presented (Rasa 1.9.0, Rasa X 0.26.3).
The container named rabbit_1 is up, so rabbit should be ok.
I try the restchannel and not useful logs is presented on rasa-x container, also for the chat integrated on Rasa X (The section: “Talk to your bot”). The chat integrated restart for each message i sent, i think it is related to the conversation_event table that it isn’t populated.
Watching the full logs on docker-compose logs i see the initial error in rasa production and worker to connect to rabbit, after i while the rabbit start to accept connection and the log rasa_x connected to rabbit appears, but i don’t see any similar log for the production and worker.
I noticed this log:
[2020-03-26 08:48:12 +0000]  [INFO] Starting worker  rasa-x_1 | [2020-03-26 08:48:14 +0000]  [DEBUG] KeepAlive Timeout. Closing connection. rasa-x_1 | [2020-03-26 08:48:15 +0000]  [DEBUG] KeepAlive Timeout. Closing connection.
What kind of connection are closed on rasa-x, maybe to the production and worker?
Thanks for the help.
At the end the connection is accepted by rabbit, and no more log are presented by rabbit container.
2020-03-26 08:51:06.552 [info] <0.598.0> accepting AMQP connection <0.598.0> (172.18.0.6:41392 -> 172.18.0.5:5672) 2020-03-26 08:51:06.557 [info] <0.598.0> connection <0.598.0> (172.18.0.6:41392 -> 172.18.0.5:5672): user 'user' authenticated and granted access to vhost '/' 2020-03-26 08:51:06.602 [info] <0.616.0> accepting AMQP connection <0.616.0> (172.18.0.7:59496 -> 172.18.0.5:5672) 2020-03-26 08:51:06.605 [info] <0.616.0> connection <0.616.0> (172.18.0.7:59496 -> 172.18.0.5:5672): user 'user' authenticated and granted access to vhost '/' 2020-03-26 08:51:08.294 [info] <0.628.0> accepting AMQP connection <0.628.0> (172.18.0.2:39388 -> 172.18.0.5:5672) 2020-03-26 08:51:08.297 [info] <0.628.0> connection <0.628.0> (172.18.0.2:39388 -> 172.18.0.5:5672): user 'user' authenticated and granted access to vhost '/'
I think Rasa X is not cosuming the queue.
I have no name!@3688fb3148ac:/$ rabbitmq-diagnostics list_queues Timeout: 60.0 seconds ... Listing queues for vhost / ... name messages rasa_production_events 0 rasa_core_events 166
Those versions of Rasa & Rasa X aren’t compatible. Try Rasa
1.9.2 and Rasa X
i just updated to the version suggested by you and everythings work well.
Thank you very much.