Why after upgrade to V4 rejoin is required?

I upgraded Chirpstack to V4 but all of the devices status is “Never Seen” that means I have to reset all the devices by hand for rejoin. Why reajoin is required ?

2 Likes

If the v3 to v4 migration utility runs successful, then the device-sessions are migrated and devices continue to operate.

1 Like

I’ve used the migration tool but even with that it doesn’t seem to keep device-sessions.

Here is the migration log:

./chirpstack-v3-to-v4 \
  --as-config-file /migration/chirpstack-application-server/chirpstack-application-server.toml \
  --ns-config-file /migration/chirpstack-network-server/chirpstack-network-server.toml \
  --cs-config-file /migration/chirpstack/chirpstack.toml 
2022/11/15 16:47:27 Reading ChirpStack configuration file: /migration/chirpstack/chirpstack.toml
2022/11/15 16:47:27 Reading AS configuration file: /migration/chirpstack-application-server/chirpstack-application-server.toml
2022/11/15 16:47:27 Deleting users and tenants from target database
2022/11/15 16:47:27 Migrating users
2022/11/15 16:47:27 Migrating organizations
2022/11/15 16:47:27 Migrating organization users
2022/11/15 16:47:27 Migrating applications
2022/11/15 16:47:27 Migrating application integrations
2022/11/15 16:47:27 Reading NS configuration file: /migration/chirpstack-network-server/chirpstack-network-server.toml
2022/11/15 16:47:27 Migrating gateways
2022/11/15 16:47:31 Migrating device-profiles
2022/11/15 16:47:31 Migrating devices
2022/11/15 16:47:31 Migrating device-keys
2022/11/15 16:47:31 Migrating device-queue
2022/11/15 16:47:31 Migrating device-keys
2022/11/15 16:47:31 Migrating device-queue
2022/11/15 16:47:31 Migrating device-keys
2022/11/15 16:47:31 Migrating device-queue
2022/11/15 16:47:31 Migrating device-keys
2022/11/15 16:47:31 Migrating device-queue
2022/11/15 16:47:31 Migrating device-keys
2022/11/15 16:47:31 Migrating device-queue
2022/11/15 16:47:31 Migrating device-keys
2022/11/15 16:47:31 Migrating device-queue
2022/11/15 16:47:31 Migrating device-keys
2022/11/15 16:47:31 Migrating device-queue
2022/11/15 16:47:31 Migrating device-keys
2022/11/15 16:47:31 Migrating device-queue
2022/11/15 16:47:32 Migrating device-keys
2022/11/15 16:47:32 Migrating device-queue
2022/11/15 16:47:32 Migrating device-keys
2022/11/15 16:47:32 Migrating device-queue
2022/11/15 16:47:32 Migrating device-keys
2022/11/15 16:47:32 Migrating device-queue
2022/11/15 16:47:32 Migrating device-keys
2022/11/15 16:47:32 Migrating device-queue
2022/11/15 16:47:32 Migrating device-keys
2022/11/15 16:47:32 Migrating device-queue
2022/11/15 16:47:32 Migrating device-keys
2022/11/15 16:47:32 Migrating device-queue
2022/11/15 16:47:32 Migrating device-keys
2022/11/15 16:47:32 Migrating device-queue
2022/11/15 16:47:32 Migrating device-keys
2022/11/15 16:47:32 Migrating device-queue
2022/11/15 16:47:32 Migrating device-keys
2022/11/15 16:47:32 Migrating device-queue
2022/11/15 16:47:32 Migrating device-keys
2022/11/15 16:47:32 Migrating device-queue
2022/11/15 16:47:32 Migrating device-keys
2022/11/15 16:47:32 Migrating device-queue
2022/11/15 16:47:32 Migrating device-keys
2022/11/15 16:47:32 Migrating device-queue
2022/11/15 16:47:32 Migrating device-keys
2022/11/15 16:47:32 Migrating device-queue
2022/11/15 16:47:32 Migrating device-keys
2022/11/15 16:47:32 Migrating device-queue
2022/11/15 16:47:32 Migrating device-keys
2022/11/15 16:47:32 Migrating device-queue
2022/11/15 16:47:32 Migrating device-keys
2022/11/15 16:47:32 Migrating device-queue
2022/11/15 16:47:32 Migrating device-keys
2022/11/15 16:47:32 Migrating device-queue
2022/11/15 16:47:32 Migrating device-keys
2022/11/15 16:47:32 Migrating device-queue
2022/11/15 16:47:32 Migrating device-keys
2022/11/15 16:47:32 Migrating device-queue
2022/11/15 16:47:32 Migrating device-keys
2022/11/15 16:47:32 Migrating device-queue
2022/11/15 16:47:32 Migrating device-keys
2022/11/15 16:47:32 Migrating device-queue
2022/11/15 16:47:32 Migrating device-keys
2022/11/15 16:47:32 Migrating device-queue
2022/11/15 16:47:32 Migrating device-keys
2022/11/15 16:47:32 Migrating device-queue
2022/11/15 16:47:32 Migrating device-keys
2022/11/15 16:47:32 Migrating device-queue
2022/11/15 16:47:32 Migrating device-keys
2022/11/15 16:47:32 Migrating device-queue
2022/11/15 16:47:32 Migrating device-keys
2022/11/15 16:47:33 Migrating device-queue
2022/11/15 16:47:33 Migrating device-keys
2022/11/15 16:47:33 Migrating device-queue
2022/11/15 16:47:33 Migrating device-keys
2022/11/15 16:47:33 Migrating device-queue
2022/11/15 16:47:33 Migrating device-keys
2022/11/15 16:47:33 Migrating device-queue
2022/11/15 16:47:33 Migrating device-keys
2022/11/15 16:47:33 Migrating device-queue
2022/11/15 16:47:33 Migrating device-keys
2022/11/15 16:47:33 Migrating device-queue
2022/11/15 16:47:33 Migrating device-keys
2022/11/15 16:47:33 Migrating device-queue
2022/11/15 16:47:33 Migrating device-keys
2022/11/15 16:47:33 Migrating device-queue
2022/11/15 16:47:33 Migrating device-keys
2022/11/15 16:47:33 Migrating device-queue
2022/11/15 16:47:33 Migrating device-keys
2022/11/15 16:47:33 Migrating device-queue
2022/11/15 16:47:33 Migrating device-keys
2022/11/15 16:47:33 Migrating device-queue
2022/11/15 16:47:33 Migrating device-keys
2022/11/15 16:47:33 Migrating device-queue
2022/11/15 16:47:33 Migrating device-keys
2022/11/15 16:47:33 Migrating device-queue
2022/11/15 16:47:33 Migrating device-keys
2022/11/15 16:47:33 Migrating device-queue

If I rejoin the device and restart the server, the device session is correctely persistent.

The old redis DB (redis v5) was 1.8MB ans the one after migration (redis v7) is 1.3MB.

Everything else is migrated fine.

Any idea what is going wrong?