Latest version freezes when trying to run actions server

Rasa version: 1.5.3

Rasa SDK version (if used & relevant): 1.5.2

Python version: 3.6.9 (Anaconda)

Operating system (windows, osx, …): RHEL 7 (CentOs) - Running on a Dell XPS i7 with 16Gb RAM

Issue: When I issue “rasa run actions”, I get a list of functions, but no line stating that the action server is runner on port 5055. If I try and access the action endpoint, it timeouts. The last version I tested where it ran correctly was 1.4.6 (Python 3.6.9)

Error (including full traceback): No error message… The computer just freezes. Ctrl-C interrupts the script.

$ rasa run actions --debug
2019-12-13 09:22:37 INFO     rasa_sdk.endpoint  - Starting action endpoint server...
2019-12-13 09:22:37 INFO     rasa_sdk.executor  - Registered function for 'action_get_valor_registro'.
2019-12-13 09:22:37 INFO     rasa_sdk.executor  - Registered function for 'action_get_valor_averbacao'.
2019-12-13 09:22:37 INFO     rasa_sdk.executor  - Registered function for 'action_get_cartorio_registral'.
2019-12-13 09:22:37 INFO     rasa_sdk.executor  - Registered function for 'action_saudacao'.
2019-12-13 09:22:37 INFO     rasa_sdk.executor  - Registered function for 'registro_form'.
2019-12-13 09:22:37 INFO     rasa_sdk.executor  - Registered function for 'averbacao_form'.
2019-12-13 09:22:37 INFO     rasa_sdk.executor  - Registered function for 'cartorio_form'.
2019-12-13 09:22:37 DEBUG    rasa_sdk.utils  - Using the default number of Sanic workers (1).

This is the last message that appears until Ctrl-C is entered. When I press Ctrl-C, I just get a ^C and prompt. No traceback.

Here’s the output from top, ordered by PID descending:

top - 09:37:11 up 2 days, 31 min,  3 users,  load average: 0,00, 0,01, 0,12
Tasks: 286 total,   1 running, 285 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0,0 us,  0,1 sy,  0,0 ni, 99,8 id,  0,1 wa,  0,0 hi,  0,0 si,  0,0 st
KiB Mem : 16214800 total,  4038896 free,  1476516 used, 10699388 buff/cache
KiB Swap:  8191996 total,  8191996 free,        0 used. 13883652 avail Mem

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
32004 root      20   0       0      0      0 S   0,0  0,0   0:00.17 kworker/u16:1
30612 root      20   0       0      0      0 S   0,0  0,0   0:00.00 kworker/7:2
30490 root      20   0       0      0      0 S   0,0  0,0   0:01.60 kworker/3:2
25633 root      20   0       0      0      0 S   0,0  0,0   0:00.71 kworker/5:0
25622 root      20   0       0      0      0 S   0,0  0,0   0:00.65 kworker/1:1
23666 root      20   0       0      0      0 S   0,0  0,0   0:02.81 kworker/7:0
23648 root      20   0       0      0      0 S   0,0  0,0   0:00.00 kworker/2:2
21771 root      20   0       0      0      0 S   0,0  0,0   0:00.00 kworker/2:0
21770 root      20   0       0      0      0 S   0,0  0,0   0:00.00 kworker/4:0
21769 root      20   0  107956    348    280 S   0,0  0,0   0:00.00 sleep
21752 root      20   0       0      0      0 S   0,0  0,0   0:00.00 kworker/7:1
21735 root      20   0       0      0      0 S   0,0  0,0   0:00.00 kworker/3:3
21718 root      20   0       0      0      0 S   0,0  0,0   0:00.00 kworker/0:1
21717 root      20   0       0      0      0 S   0,0  0,0   0:00.00 kworker/2:1
21711 root      20   0       0      0      0 S   0,0  0,0   0:00.00 kworker/4:2
21698 xxxxxx    20   0 1992720 257996  79124 S   0,0  1,6   0:02.07 rasa
21406 root      20   0       0      0      0 S   0,0  0,0   0:00.00 kworker/5:1
20325 xxxxxx    20   0  162316   2568   1612 R   0,7  0,0   0:01.86 top

Command or request that led to error:

rasa run actions --debug

Content of configuration file (config.yml) (if relevant):

Content of domain file (domain.yml) (if relevant):

[YunLovesCode]

It was just a log message that was removed in Rasa 1.5. The action server was runnning and responding correctly. Okay, thanks!

[erohmensing]

It seems like that log was removed: https://github.com/RasaHQ/rasa-sdk/commit/755ef54bf60b74061f5ae7d7e36a76cbf3de219d

which is why you’re not seeing it. If you like, you can create a PR to bring it back. Have you tried to check whether the action server is actually running? if you run it on debug mode do you see it receiving calls to the actions?