New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rasa-production_1 | Could not fetch runtime config from server at 'http://rasa-x:5002/api/config?token=token_string'. Exiting. #5582
Comments
@mandaarp Mhm, that seems some tokens weren't set correctly. Did you specify |
I think so. Please see .env file above. Below is my environments.yml file (per the posted documentation)... rasa:
production:
url: http://rasa-production:5005
token: ${RASA_TOKEN}
worker:
url: http://rasa-worker:5005
token: ${RASA_TOKEN} |
Are |
Here is the output of rasa x installation directory:
|
That actually looks 🤔 Can you please also share the |
Hi, am also facing the same issue. is there any solution for this? rasa-production_1 | Starting Rasa X in production mode... 🚀 |
the same issue |
Weird, Rasa X keeps on restarting 🤔 Could you please set an environment variable |
Hi, also facing the same problem here. Using the newest docker compose file of rasa-x version 0.28.5 after a while I get the same error messages:
Also when i click on "train" in the rasa-x UI I get the following error:
then in the UI it says "Nothing has changed" with a button "See latest model". When i click on that I get the following error:
|
I think i know what the problem is... I am using spacy and this needs to be run on the docker images on build:
To do this I replaced the following in the
TO:
Then make a dockerfile containing this:
Here I used the dutch spacy model. |
This issue has been automatically closed because there has been no response to our request for more information from the original author. Without this, we don't have enough information to help you. Please comment below with the requested information if you still need help. |
I have the same problem with identical output. I use the latest images and had the same setup as described by the author. |
Do you mean with the |
I'm facing the same issue with identical output. I use the latest images and had the same setup as described by the author. |
I'm having the same issue. Any updates on how to fix it? |
I'm having the same issue. :( |
Same issue... |
I don't understand why this issue is closed. |
Which Rasa X / Rasa Open Source versions are you using and how did you deploy? How much disk space does your machine have (should be at least 50 GiB)? @RasaHQ/practice-cdd Could you please have a look at this? 🙌🏻 |
Ho @wochinge , I am using the latetest of both Free space yes. Aroud 150GB, 16GB RAM (32 in the server, around 16 free) PS: I have a 404 by clicking your link. Something wrong? PPS: @wochinge maybe it's a bit off topic this question but I don't know if it may help. |
This issue has been automatically closed because there has been no response to our request for more information from the original author. Without this, we don't have enough information to help you. Please comment below with the requested information if you still need help. |
I finally solved the issue: |
I tried to reproduce with the following
And I'm getting the same initial logs from Judging from @cianiandreadev's comment, it might have been that then Can somebody who's currently experiencing this issue post the output of |
Rasa version: 1.9.5
Rasa SDK version (if used & relevant):
Rasa X version (if used & relevant): 0.27.4
Python version: 3.7
Operating system (windows, osx, ...): osx
Issue:
Error (including full traceback):
Command or request that led to error:
Content of configuration file (config.yml) (if relevant):
Content of domain file (domain.yml) (if relevant):
**Content of .env file
The text was updated successfully, but these errors were encountered: