[X] I have inspeced the status of docker containers.
[X] I have run the sanity check described in after-installation.md.
[X] I have inspected all error messages.
[X] I have inspected the log files in the /var/log/fiware directory.
[X] I have run the make collect command.
Describe the bug
I want to update the platform from version 0.17 to 0.27 while preserving the existing information. Additionally, I want to migrate to a new domain first in a test environment to ensure everything functions correctly before migrating in my primary domain.
My intended steps are as follows:
Change the domain in version 0.17 while keeping the existing container information for the primary domain.
Once completed, update the version in the test domain, verify that everything works correctly, and then replicate the steps in my primary domain.
I have identified that the draco service is not working, it gives a 502 Bad Gateway from Nginx.
I'm not entirely sure if anything else has gone wrong. I would like to know if there is an established procedure for updating the platform and if my steps are correct.
Your system environment
Run make collect in a directory where you ran the lets-fiware.sh script and paste the results here.
./config/script/collect.sh
Date: Tue May 16 09:15:21 UTC 2023
Version: 0.17.0
Hash: d2317c9e5f49f2def5663ad7de2d79f63f49c7563b27b4101746af498327b382 lets-fiware.sh
git-hash:
8151bea89502b48e4f2c1142d5c600e13c0df11c
App list: KEYROCK ORION COMET WIRECLOUD NGSIPROXY NODE_RED GRAFANA QUANTUMLEAP IOTAGENT_UL IOTAGENT_JSON IOTAGENT_HTTP MOSQUITTO
Install: completed
Docker containers:
make[1]: Entering directory '/home/ubuntu/FIWARE-Big-Bang'
sudo /usr/local/bin/docker-compose ps
Name Command State Ports
------------------------------------------------------------------------------------------------------------
fiware-big-bang- npm --no-update-notifier - Up (healthy) 1880/tcp
agrinodered001-1 ...
fiware-big-bang- npm --no-update-notifier - Up (healthy) 1880/tcp
agrinodered002-1 ...
fiware-big-bang- npm --no-update-notifier - Up (healthy) 1880/tcp
agrinodered003-1 ...
fiware-big-bang-comet-1 docker/entrypoint.sh -- c Up (healthy) 127.0.0.1:8666->8666/tcp
...
fiware-big-bang-crate-1 /docker-entrypoint.sh crat Up 127.0.0.1:4200->4200/tcp,
... 4300/tcp, 5432/tcp
fiware-big-bang-draco-1 ../scripts/start.sh Up (health: starting) 10000/tcp,
127.0.0.1:5050->5050/tcp,
8000/tcp, 8080/tcp,
8443/tcp
fiware-big-bang- /docker-entrypoint.sh elas Up 9200/tcp, 9300/tcp
elasticsearch-1 ...
fiware-big-bang-grafana-1 /run.sh Up 3000/tcp
fiware-big-bang-iotagent- docker-entrypoint.sh node Up (healthy) 4041/tcp, 7896/tcp
json-1 ...
fiware-big-bang-iotagent- docker-entrypoint.sh node Up (healthy) 4061/tcp, 7896/tcp
ul-1 ...
fiware-big-bang-keyrock-1 docker-entrypoint.sh npm Up (healthy) 3000/tcp
start
fiware-big-bang- docker-entrypoint.sh memca Up 11211/tcp
memcached-1 ...
fiware-big-bang-mongo-1 docker-entrypoint.sh --noj Up 127.0.0.1:27017->27017/tcp
...
fiware-big-bang- /docker-entrypoint.sh /usr Up 1883/tcp
mosquitto-1 ...
fiware-big-bang-mysql-1 docker-entrypoint.sh Up 127.0.0.1:3306->3306/tcp,
mysqld 33060/tcp
fiware-big-bang-nginx-1 /docker-entrypoint.sh ngin Up 0.0.0.0:443->443/tcp,:::44
... 3->443/tcp, 0.0.0.0:80->80
/tcp,:::80->80/tcp, 0.0.0.
0:8883->8883/tcp,:::8883->
8883/tcp
fiware-big-bang- docker/entrypoint.sh Up
ngsiproxy-1
fiware-big-bang-orion-1 sh -c rm /tmp/contextBroke Up (healthy) 127.0.0.1:1026->1026/tcp
...
fiware-big-bang-perseo- /code/perseo_core-entrypoi Up (healthy) 8080/tcp
core-1 ...
fiware-big-bang-perseo- docker-entrypoint.sh node Up (healthy) 9090/tcp
fe-1 ...
fiware-big-bang-postgres-1 docker-entrypoint.sh Up 127.0.0.1:5432->5432/tcp
postgres
fiware-big-bang- python app.py Up (healthy) 127.0.0.1:8668->8668/tcp
quantumleap-1
fiware-big-bang- docker-entrypoint.sh Up 1030/tcp
queryproxy-1
fiware-big-bang-redis-1 docker-entrypoint.sh redis Up 6379/tcp
...
fiware-big-bang-regproxy-1 docker-entrypoint.sh Restarting
fiware-big-bang- docker-entrypoint.sh Up 1029/tcp
tokenproxy-1
fiware-big-bang-wilma-1 docker-entrypoint.sh npm Up (health: starting) 1027/tcp
start
fiware-big-bang- /docker-entrypoint.sh Up (healthy) 8000/tcp
wirecloud-1
fiware-big-bang-zeppelin-1 /usr/bin/tini -- bin/zeppe Up 8080/tcp
...
make[1]: Leaving directory '/home/ubuntu/FIWARE-Big-Bang'
Keyrock:
{"keyrock":{"version":"8.1.0","release_date":"2021-07-22","uptime":"00:13:25.7","git_hash":"https://github.com/ging/fiware-idm/releases/tag/8.1.0","doc":"https://fiware-idm.readthedocs.io/en/8.1.0/","api":{"version":"v1","link":"https://keyrock.xxxxx.com/v1"}}}
To Reproduce
My steps so far have been:
Backed up the "data" folder.
Saved the configuration of the .env file.
Ran make clean.
Modified the config.sh file by replacing the variables referring to the old domain with those of the test domain.
Executed ./lets-fiware.sh for installation.
Replaced the .env file and the "data" folder with those from the primary domain.
Expected behavior
Change the domain and keep the information of the installation with the old domain.
Screenshots
Server (please complete the following information):
OS and OS version: 20.04.5
Docker version: 20.10.22
Docker compose version: 2.6.1
Additional context
Running sanity checks:
make get-token
./config/script/get_token.sh
jq: error (at <stdin>:0): Cannot index string with string "access_token"
make: *** [Makefile:30: get-token] Error 5
ngsi version --host orion.xxxx.com
Run001 error 401 Unauthorized "Invalid client: client is invalid
Checklist Put an
x
in the boxes that applymake collect
command.Describe the bug I want to update the platform from version 0.17 to 0.27 while preserving the existing information. Additionally, I want to migrate to a new domain first in a test environment to ensure everything functions correctly before migrating in my primary domain.
My intended steps are as follows:
I have identified that the draco service is not working, it gives a 502 Bad Gateway from Nginx. I'm not entirely sure if anything else has gone wrong. I would like to know if there is an established procedure for updating the platform and if my steps are correct.
Your system environment Run
make collect
in a directory where you ran the lets-fiware.sh script and paste the results here. ./config/script/collect.shTo Reproduce My steps so far have been:
Expected behavior Change the domain and keep the information of the installation with the old domain.
Screenshots
Server (please complete the following information):
Additional context Running sanity checks:
I am able to access the Keyrock interface.
Accessing the draco interface gives a 502 Bad Gateway from Nginx.
Node-red is also not working properly as shown in the screenshot.
The other services seem to be working as they should.
I send also the errors of the containers in case it can help: