Sorry if this doesn’t have all required information, I am not an experienced Linux user.
I tried the migration tool to upgrade from v3 to v4, but run into problems.
Chirpstack is running on a Ubuntu 20.04.4 LTS installation running on a VPS. v3 works without any problems.
Old versions:
chirpstack-network-server is already the newest version (3.16.3).
chirpstack-gateway-bridge is already the newest version (3.14.2).
chirpstack-application-server is already the newest version (3.17.7).
After installation of Chirpstack v4 and running the migration tool, I can see all devices and gateways in the console. But no packet from my gateways is reaching the server. The migration guide is a little bit vague what to do with the existing installations of the Network Server v3 and Application Server v3.
Should they be uninstalled?
Are there any manual changes in the .toml files required? I checked the ip addresses and ports in the chirpstack.toml and it seems to be all ok.
Running journalctl doesn’t show any critical errors on any of chirpstack, network or application server.
Chirpstack V4 is now running. I have direct installation, no Docker.
But I do not understand how to run multiple instances of of the Chirpstack Gateway Bridge on the same machine.
It doesn’t matter, as long as it can connect to the databases using the configuration files. In case your chirpstack-application-server.toml (and network-server.toml) contain localhost, you might want to make a copy of these files and update the hostnames.
Again, the important thing is that the migration utility has access to the databases as listed in the config files. This might need some updates if you need to change the hostnames.
Hostname or IP doesn’t matter, for config options, as long as it is resolvable.
If you have ChirpStack Network Server, ChirpStack Application Server and ChirpStack v4 already up-and-running, then you already have these config files Please see the above usage-example link.
Please see the above usage-example link.
Will open a new topic for it.