Welcome to wis2box Discussions! #2
Replies: 9 comments 9 replies
-
|
I am trying to run python3 wis2box-ctl.py start . |
Beta Was this translation helpful? Give feedback.
-
|
After re-installing, I am trying to run python3 wis2box-ctl.py start again During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): |
Beta Was this translation helpful? Give feedback.
-
|
Hi Maixentkambi, Thank you for trying out wis2box ! Can you confirm docker is running using the following command: Could you let us know the version of docker and docker-compose you are running ? |
Beta Was this translation helpful? Give feedback.
-
|
Hi maaikelimper thanks for your answer . Here is the output root@localhost wis2box]# systemctl status docker.service Apr 30 14:35:00 localhost.localdomain dockerd-current[10065]: time="2022-04-30T14:35:00.208846600+01:00" level=error msg="Error setting up exec command in container wis2box: No such co...r: wis2box" |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. The docker version looks to be old. Could you please install the latest version of docker: https://docs.docker.com/engine/install/ My output for docker --version |
Beta Was this translation helpful? Give feedback.
-
|
Hi all thanks for your answer . Here is the output [root@localhost wis2box]# python3 wis2box-ctl.py start |
Beta Was this translation helpful? Give feedback.
-
|
I think this was addressed by #148 |
Beta Was this translation helpful? Give feedback.
-
|
Hello, |
Beta Was this translation helpful? Give feedback.
-
|
As an update I have modified the port numbers in the docker-compose.override.yml file and modified the dev.env file to use the new ports to set the WIS2BOX_API_URL and WIS2BOX_URL I haven't changed the docker-compose.yml file yet. I followed the quickstart instructions including the ingest data and cache/publish stations steps to load the tests data. I can see WIS2BOX running in a browser, but I can't see any data. Should I be able to see data on these pages?
Any assistance would be gratefully received. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, By default the WIS2BOX_URL=http://localhost:8999 It sounds like that's exactly what you did, but to double-check, could you repeat these steps: For example, Update WIS2BOX_URL and WIS2BOX_API_URL in dev.env : Restart the wis2box-stack And WIS2BOX_UI is available on http://localhost:1234 If your wis2box shows no datasets, it might mean you have not added the collections. To add collections, login to the wis2box-container: and, assuming your using the test-data from the quickstart, run the following commands: add-collection publish metadata |
Beta Was this translation helpful? Give feedback.
-
|
We are working on improving documentation for WIS2-in-a-box users with a new guide available here: |
Beta Was this translation helpful? Give feedback.
-
|
The current docs are available at: https://docs.wis2box.wis.wmo.int/ |
Beta Was this translation helpful? Give feedback.
-
|
Hi I've been working to get wis2box running but once I'm set up and applied some preliminary config from the guide, the containers don't seem to deploy. The output is listed below. When setting up the host, I had to remove docker-compose-plugin (yum remove ...) as the version was > v2 and get docker-compose 1.29.2 manually and then ln -s /usr/bin/docker-compose according to the troubleshooting guide. I've tested docker-compose using the example at https://docs.docker.com/compose/gettingstarted/ and that example worked normally with docker, so I think docker and docker-compose are working fine. docker version is 23.0.5 After attempting to start wis2box (output below) "docker info" reports no containers running but I'm left with three docker-proxy processes for ports 8884. 1883 and 3000. Those persist across docker stop and starts and I have to remove them from /var/lib/docker/network/files/local-kv.db, otherwise they interfere with following wis2box start attempts. I've switched SELinux to permissive and stopped firewalld. I tried removing all the containers and images with docker rm(i) but once everything was retrieved again the same as below occurred. I tried various entries for DOCKER_HOST env but that didn't seem to help. Do you have any tips or can see what I've got wrong here? Thank you for any help you can give |
Beta Was this translation helpful? Give feedback.
-
|
From what you described the problem seems related to your Docker-installation. Here are a few things you could try. You can test Docker works OK by running the hello-world example:
Clean up your Docker system before attempting to start wis2box, you can use You could try to start without the monitoring-stack (no cAdvisor/grafana/loki/prometheus):
|
Beta Was this translation helpful? Give feedback.
-
|
Hi Thank you for getting back so quickly. The hello world example worked fine and I had tried clearing docker but unfortunately didn't help. Starting without the monitoring as you describe though has got me further along with the following and I see containers running, (where as before there was never anything listed despite starting wis2box-ctl.py) http://localhost/oapi/collections doesn't return anything yet (not listening on port 80) but may be that's expected starting things like this? Does that reveal anything about what might be wrong with my installation and what I can try from here? Stopping everything, clearing docker and trying to start with "python3 wis2box-ctl.py start" still results in the problems listed earlier. I'm not sure the started services are stable though; nginx is always restarting and wis2box-api and ui report Exit 1 as their status. Running the same command with 'down' instead of 'up' stops everything cleanly. Thank you again for your help, very appreciated. |
Beta Was this translation helpful? Give feedback.
-
|
From the information your provided it looks like the nginx-container is restarting. You could check the logs for this container with |
Beta Was this translation helpful? Give feedback.
-
|
Hi Sorry for late reply. We found that ipv6 was shut down on the host and some other features were disabled for instance hardening which stopped wis2bix running normally. Creating a standard ec2 instance and wis2box ran first time and without issues. We have our test instance running now for 2 or 3 months. Thank you again for your help earlier. |
Beta Was this translation helpful? Give feedback.
-
|
Typing to get v1.0b6 running (same problem with git-main) Cleared out all the docker container.
docker inspect --format "{{json .State.Health }}" elasticsearch | jq So it seems that elasticsearch is not accepting connections. I have no idea why and need help to get this running |
Beta Was this translation helpful? Give feedback.
-
👋 Welcome!
We’re using Discussions as a place to connect with other members of our community. We hope that you:
build together 💪.
To get started, comment below with an introduction of yourself and tell us about what you do with this community.
Beta Was this translation helpful? Give feedback.
All reactions