orchest: Error attempting to connect to Gateway server url 'http://jupyter-EG-93c7d122-a3b1-435f-d8f6a2d0-6584-4c1c:8888'. Ensure gateway url is valid and the Gateway instance is running.

Fixed #757 solved by build images . I also got the same problem #757 and run the following solved the problem

git checkout v2022.03.0
scripts/build_container.sh

After that, check the version and I got

Getting versions of all containers...
orchest/jupyter-enterprise-gateway:latest   : v2022.03.0
orchest/jupyter-server:latest               : v2022.03.0
orchest/memory-server:latest                : v2022.03.0
orchest/session-sidecar:latest              : v2022.03.0
orchest/update-server:latest                : v2022.03.0
orchest/orchest-api:latest                  : v2022.03.0
orchest/orchest-webserver:latest            : v2022.03.0
orchest/celery-worker:latest                : v2022.03.0
orchest/auth-server:latest                  : v2022.03.0
orchest/file-manager:latest                 : v2022.03.0
orchest/nginx-proxy:latest                  : v2022.03.0
orchest/base-kernel-py:latest               : v2022.03.0
orchest/base-kernel-r:latest                : v2022.03.0

Yes, follow your steps, the problem is solved! @huangkai31

So it doesn’t look like a network problem. @yannickperrenet

Thanks all. @fruttasecca @yannickperrenet @huangkai31

Fixed #757 solved by build images . I also got the same problem #757 and run the following solved the problem

git checkout v2022.03.0
scripts/build_container.sh

After that, check the version and I got

Getting versions of all containers...
orchest/jupyter-enterprise-gateway:latest   : v2022.03.0
orchest/jupyter-server:latest               : v2022.03.0
orchest/memory-server:latest                : v2022.03.0
orchest/session-sidecar:latest              : v2022.03.0
orchest/update-server:latest                : v2022.03.0
orchest/orchest-api:latest                  : v2022.03.0
orchest/orchest-webserver:latest            : v2022.03.0
orchest/celery-worker:latest                : v2022.03.0
orchest/auth-server:latest                  : v2022.03.0
orchest/file-manager:latest                 : v2022.03.0
orchest/nginx-proxy:latest                  : v2022.03.0
orchest/base-kernel-py:latest               : v2022.03.0
orchest/base-kernel-r:latest                : v2022.03.0

./orchest update --dev

Updating… Pulling images: 14/14|#################################################| Checking whether all containers are running the same version of Orchest. Getting versions of all containers… orchest/jupyter-enterprise-gateway:latest : v2021.06.3 orchest/jupyter-server:latest : v2022.02.9 orchest/memory-server:latest : v2022.02.8 orchest/session-sidecar:latest : v2022.02.8 orchest/update-server:latest : v2021.10.2 orchest/orchest-api:latest : v2021.10.2 orchest/orchest-webserver:latest : v2022.02.9 orchest/celery-worker:latest : v2021.12.0 orchest/auth-server:latest : v2022.02.9 orchest/file-manager:latest : v2021.12.0 orchest/nginx-proxy:latest : v2021.10.2 orchest/base-kernel-py:latest : v2022.02.8 Not all containers are running on the same version of Orchest, which can lead to the application crashing. You can fix this by running: orchest update This should get all containers on the same version again. Update was unsuccessful. Orchest was unable to pull the latest version of its currently pulled images. Please make sure you have enough disk space available. Or if you have plently of disk space available, try updating again later (~30 minutes should work).

The disk still has 86G of remaining space, and after started, the situation is still the same.

ls -aln output: total 760 drwxr-xr-x 30 501 20 960 2 23 10:56 . drwxr-xr-x@ 4 501 20 128 2 21 18:22 … -rw-r–r–@ 1 501 20 8196 2 22 10:16 .DS_Store -rw-r–r-- 1 501 20 214 2 21 18:22 .dockerignore -rw-r–r-- 1 501 20 999 2 21 18:22 .eslintrc.js -rw-r–r-- 1 501 20 469 2 21 18:22 .flake8 drwxr-xr-x 16 501 20 512 2 23 15:20 .git -rw-r–r-- 1 501 20 14 2 21 18:22 .gitattributes drwxr-xr-x 9 501 20 288 2 21 18:23 .github -rw-r–r-- 1 501 20 2375 2 21 18:22 .gitignore -rw-r–r-- 1 501 20 7 2 21 18:22 .nvmrc -rw-r–r-- 1 501 20 1265 2 21 18:22 .pre-commit-config.yaml -rw-r–r-- 1 501 20 65 2 21 18:22 .prettierignore -rw-r–r-- 1 501 20 80 2 21 18:22 .prettierrc.js -rw-r–r-- 1 501 20 255 2 21 18:22 .readthedocs.yaml -rw-r–r–@ 1 501 20 34523 2 21 18:22 LICENSE -rw-r–r–@ 1 501 20 7723 2 21 18:22 README.md drwxr-xr-x@ 7 501 20 224 2 21 18:22 cypress drwxr-xr-x@ 6 501 20 192 2 21 18:22 docs drwxr-xr-x@ 6 501 20 192 2 21 18:23 lib -rwxr-xr-x@ 1 501 20 2480 2 21 18:22 orchest drwxr-xr-x@ 5 501 20 160 2 21 18:22 orchest-sdk -rw-r–r–@ 1 501 20 1266 2 21 18:22 package.json -rw-r–r-- 1 501 20 269838 2 23 10:56 pnpm-lock.yaml -rw-r–r–@ 1 501 20 145 2 21 18:22 pnpm-workspace.yaml -rw-r–r–@ 1 501 20 457 2 21 18:22 pyproject.toml drwxr-xr-x@ 12 501 20 384 2 21 18:22 scripts drwxr-xr-x@ 16 501 20 512 2 21 18:23 services -rw-r–r–@ 1 501 20 407 2 21 18:22 tsconfig.json drwxr-sr-x 9 501 20 288 2 22 10:16 userdir

My guess is that if you stash the changes and run the update again everything should be fixed.

I agree.

And thanks @playinlife for all the outputs 💯

Hi @playinlife, I suspect this might be related to some stale resource or Jupyter EG not being on the same version of the rest of Orchest services. Could you try to do the following and report back?

./orchest status --ext (this is to verify that all Orchest images are on the same version)

Hi @Practcdi, thanks for reporting the issue. Orchest has a CLI command that provides a debug dump (./orchest debug --help), could you do the following?

• stop Orchest
• start Orchest
• reproduce the bug
• run ./orchest debug --compress (if you feel like it, add --ext for more extensive information that might include some project data)
• attach the file, or alternatively, send me a direct message in Slack or via email at jacopo@orchest.io

If possible, could you also go into orchest/userdir and post the result of running ls -la?

Thank you 😃