I watched the video and tried to go along with it, hoping that my previous install would not hamper my ability to match the configurations done in the video. Starting with my local box, I checked my deployments with rasactl list:
CURRENT
NAME
STATUS
RASA PRODUCTION
RASA WORKER
ENTERPRISE
VERSION
*
avcsti
Upgrading
0.0.0
0.0.0
After that I tried to remove this deployment: rasactl delete avcsti and created a values.yml to serve as the values file for the new deployment, just as mentioned in the video:
rasactl start avcsti --values-file ~/values.yml
However, it still took several minutes only displaying the “Deploying Rasa X” message and after all I ended up with another error message:
timed out waiting for the condition. Check your deployment status manually with `rasactl status`
Current status is stopped:
Name: avcsti
Status: Stopped
URL: http://avcsti.rasactl.localhost
Version:
Enterprise:
Project path: not defined
Before the video I tried to start using the --debug flag, and I could see several messages indicating that PersistentVolumeClaim is not bound:
2022-03-01T11:16:37.426-0300
INFO
Looks like there are no changes for Ingress rasa-x
2022-03-01T11:16:37.428-0300
INFO
beginning wait for 34 resources with timeout of 15m0s
2022-03-01T11:16:37.433-0300
INFO
PersistentVolumeClaim is not bound: avcsti/rasa-x-rasa-x-claim
…
2022-03-01T11:29:41.439-0300 INFO PersistentVolumeClaim is not bound: avcsti/rasa-x-rasa-x-claim
^CBye
@otmarjr then I am sorry current installation of Rasa X (latest 3. x updated installation) or any other will not be able to install rasa x on the local machine (I guess as per my knowledge) as it’s meant to install only on the server-side. Only, one available installation is there, If you want that I can guide you for the same.
@nik202 sorry for my ignorance, but isn’t Rasa X officially on release 1.x ? Moreover, it seems that REI supports the local or test installation, as it’s the scenario I’m trying to deploy, according to Installation Guide
I’m by no means a Linux expert, but how can REI detect that my local machine isn’t a server?
yes, I’m aware and expecting this question from your side well rasa x documentation needs to be updated, but as per my knowledge rasa 1. x will not be able to install on the local machine.
pinging @Juste for the suggestion and comment on Q: Can we install rasa x latest with the updated installation guide on local machines i.e Mac, Windows, or Ubuntu?
OK @nik202. I’m trying to follow the video, but I’m afraid how can I remediate issues I face when my current setup does not respond accordingly to the video. For now, I’m trying to replicate the command on the server side it seems stuck on another issue:
rasactl start avcsti --values-file ~/values.yml
It’s been around 5 minutes I only see this message on terminal:
∙●∙ Waiting for the health endpoint to be reachable
@nik202 any specific address I should be aware? I cannot see how my server could have any internet connectivity problems, given I have no issues with apt get or pinging external sites.
@nik202 in the video he uses the command only to demonstrate he was on a fresh machine and by the end, to summarize the commands he has shown in the video. However, I haven’t got the same results as in the video.
I’m trying to explain that after running rasactl start avcsti --values-file ~/values.yml, the 7th step on the video, I’m getting an error message, which is not shown in the video. I cannot see how the history command will help me troubleshoot the error I’ve got.
On top of that, I tried to check the server connectivity and explorer rasactl logs, so my history command won’t list the exact same steps on the video. Do you want to make sure I’m running the same commands as shown in the video? Or any other kind of verification ?
Are you using REI? Because I’m trying to run it by using the REI and I have no rasa x command available! Moreover, I’m trying to install Rasa X first, so I still have not installed rasa open source.
well rasa x documentation needs to be updated, but as per my knowledge rasa 1. x will not be able to install on the local machine.