Hello all,
It has been a real fun to develop my chatbot using Rasa platform! Thanks a ton for providing it!!
So, after developing a basic chatbot and testing it on shell, I moved forward to install Rasa X in my system a couple of days back. But somehow I am facing some issues in working with Rasa X.
Following are the issues:
Rasa X interactive training detecting intents correctly but not returning the dialogue or text to be returned along with the intent.
In the attached image it can be seen that the intents are identified but the response text is not returned.
For custom action, I have run command - >rasa run actions -vv in a terminal.
Also, the same conversation works absolutely fine in rasa shell.
Default action - restart doesnât seem to work.
Whenever ârestartâ button is hit in interactive training or conversations, this message is returned - rasa.core.featurizers - Feature âintent_restartâ could not be found in feature map.
Note: I have used âMapping policyâ in the code.
Botâs messages does not appear sometimes in the testerâs pane.
I think this problem is similar to the first issue I mentioned. Bot is skipping a few messages randomly.
In the attached image, it was supposed to return - Did that help you? after telling the symptoms. Since I know the correct path, I responded as âYesâ and it responded as expected. But this skipping messages wonât make sense for the user.
Since, except restart issue, the conversation flow and intent detection is working absolutely fine in shell, I guess it is the problem with the way I installed Rasa X.
I installed it w/o docker by using command - pip install rasa-x --extra-index-url Simple Index
Rasa X version: rasa-x-0.24.1
Rasa version: Rasa 1.6.1
Please help me out in solving this so that I can quickly move it to next stages.
Hi @Saylee . I have also been facing the same problem. It could happen that your custom actions are not returning properly, but since it is running alright in the shell, i have not idea what could be causing this issue.
Most of times I tried reloading the browser page(maybe more than once) and it worked for me, and when it didnât, it was because there was something wrong in my actions.
Hi @Saylee and @varunsapre10! If you look at the Rasa X docs, we recommend that instead of using Rasa X locally, that you should deploy it to a server. You can find out the easiest way to do that here.
The pypi install that lets you run it locally is intended to just show you what Rasa X is quickly before you install it on a server. The reason we recommend deploying on a server is because Rasa X is intended to be capturing and collecting conversations users have with your assistant, so you can use those to improve. I recommend watching this video that goes into more depth about this.
Thanks for your response!
So, I have started deploying Rasa X on windows server using Docker compose Manual installation steps.
But I am getting this error -
sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) could not translate host name âdbâ to address: Name or service not known
I scrolled up in the logs to see the root issue was failure in registering actions.actions
Actually, I have used pandas library in my custom actions. But in docker, is not installed it seems as it is showing no module named pandas.
Ok if all containers are down something must have gone wrong. could you send the logs of the rasa-x and rasa-production containers individually as well?
You can do that with docker ps rasa-production, docker ps rasa-x
As for custom dependencies in custom actions, take a look here.
sorry i meant docker-compose logs rasa-production, rather than docker ps. Ok it looks like the containers are up - do they stay up or are they restarting all the time?
@Saylee could you post the output of sudo docker-compose logs db ? Seems like an issue with the db container since itâs restarting all the time.
If you want, we can also arrange to jump on a call with you to help resolve these issues. Just send us an e-mail at support@rasa.com
Hey @akelad thanks for the support! And @degiz thanks a ton for helping over the call and solving issue!!
I am documenting the solutions you provided for people who might stumble across the same issues.
For Linux server:
Root issue was that actions.actions was not getting registered.
My installation folder was different than /etc/rasa and somehow probably I missed the step to change RASA_HOME variable to the directory I had installation in. (details given in step 2 here)
The actions.py in my project had dependencies which are not present in default rasa-sdk image. So, created Dockerfile as mentioned here and created custom_sdk
And finally actions.actions got registered!! Yay!!
Then there was âFile not found errorâ for which I got a hint from this post.
The problem was, my actions.py was using local files which needed to be included while forming image.
After successfully copying files in the image, then I faced issue with action server not running!
So, I explored a bit more to find that my âendpoints.ymlâ had an issue, it was pointing to localhost i.e. âhttp://localhost:5055/webhookâ. The correct URL should be âhttp://<image_name_as_in_docker-compose.yml>:5055/webhookâ which, in my case was âappâ.
And finallieee Rasa X is up and running flawlessly!!
