Rasa x does not give response

Version: Rasa X 0.29.1

Hi, I can run the rasa x in local machine, however, when I link to rasa x server, it doesn’t work. After I say hi, only the loading icon showed but no response is given. Can anyone let me know where can I check the error status or how to fix it? I am new to rasa. It may be a very simple question, I did some research but still can’t fix it yet…

Hi @hihalo1212, did you try running Rasa X in debug mode (--debug)? Maybe there the logs will show something useful.

can I know how to run debug mode? is it rasa x --debug ?? Thanks…

Yes! correct

hi, this is the logs rasa-production:

Attaching to rasa_rasa-production_1
rasa-production_1  | /opt/venv/lib/python3.7/site-packages/rasa/core/brokers/pika.py:294: FutureWarning: Your Pika event broker config co
ntains the deprecated `queue` key. Please use the `queues` key instead.
rasa-production_1  |   self.queues = self._get_queues_from_args(queues, kwargs)
rasa-production_1  | 2020-07-30 06:05:31 ERROR    pika.adapters.utils.io_services_utils  - Socket failed to connect: <socket.socket fd=21
, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('172.21.0.7', 47304)>; error=111 (Connection refused)
rasa-production_1  | 2020-07-30 06:05:31 ERROR    pika.adapters.utils.connection_workflow  - TCP Connection attempt failed: ConnectionRef
usedError(111, 'Connection refused'); dest=(<AddressFamily.AF_INET: 2>, <SocketKind.SOCK_STREAM: 1>, 6, '', ('172.21.0.4', 5672))
rasa-production_1  | 2020-07-30 06:05:31 ERROR    pika.adapters.utils.connection_workflow  - AMQPConnector - reporting failure: AMQPConne
ctorSocketConnectError: ConnectionRefusedError(111, 'Connection refused')
rasa-production_1  | 2020-07-30 06:05:36 ERROR    pika.adapters.utils.io_services_utils  - Socket failed to connect: <socket.socket fd=25
, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('172.21.0.7', 47326)>; error=111 (Connection refused)
rasa-production_1  | 2020-07-30 06:05:36 ERROR    pika.adapters.utils.connection_workflow  - TCP Connection attempt failed: ConnectionRef
usedError(111, 'Connection refused'); dest=(<AddressFamily.AF_INET: 2>, <SocketKind.SOCK_STREAM: 1>, 6, '', ('172.21.0.4', 5672))
rasa-production_1  | 2020-07-30 06:05:36 ERROR    pika.adapters.utils.connection_workflow  - AMQPConnector - reporting failure: AMQPConne
ctorSocketConnectError: ConnectionRefusedError(111, 'Connection refused')
rasa-production_1  | 2020-07-30 06:05:48.531612: E tensorflow/stream_executor/cuda/cuda_driver.cc:351] failed call to cuInit: UNKNOWN ERR
OR (303)

logs app:

Attaching to rasa_app_1
app_1              | 2020-07-30 06:10:55 INFO     rasa_sdk.endpoint  - Starting action endpoint server...
app_1              | 2020-07-30 06:10:56 INFO     rasa_sdk.executor  - Registered function for 'action_create_event'
.
app_1              | 2020-07-30 06:10:56 INFO     rasa_sdk.executor  - Registered function for 'action_route_plan'.
app_1              | 2020-07-30 06:10:56 INFO     rasa_sdk.executor  - Registered function for 'action_suggest'.
app_1              | 2020-07-30 06:10:56 INFO     rasa_sdk.executor  - Registered function for 'action_get_weather'.
app_1              | 2020-07-30 06:10:56 INFO     rasa_sdk.executor  - Registered function for 'action_weather_repor
t'.
app_1              | 2020-07-30 06:10:56 INFO     rasa_sdk.executor  - Registered function for 'event_form'.
app_1              | 2020-07-30 06:10:56 INFO     rasa_sdk.endpoint  - Action endpoint is up and running on http://l
ocalhost:5055

may I ask how to run rasa actions run on rasa x ? it seems that the action was not turn on?? the situation now is the form was not executed:

thanks…

@fede

When I typed sudo docker-compose up -d , the bot was not run correctly. Bot recognized the “form” but jumped to utter_slots_value without asked any questions.

I fixed it by typing sudo docker-compose up , then it works now.

However, I am facing another problem, which is DucklingHTTPExtractor cannot identify DateTime correctly on rasa x. when I was using rasa shell or rasa x locally, I typed " tmr at 3pm", it can identify it as {“time”:“2020-7-31T19:00:00…”} but on rasa x server, it identified as {“time”:“tmr at 3pm”}

What can I do to fix it?? Many thanks.