Applying migrations error

Hi again everyone,

Does anyone know what does the below issue means please:

INFO[0000] starting LoRa App Server docs=“https://www.loraserver.io/” version=1.0.1
INFO[0000] connecting to postgresql
INFO[0000] setup redis connection pool
INFO[0000] handler/mqtt: TLS config is empty
INFO[0000] handler/mqtt: connecting to mqtt broker server=“tcp://localhost:1883”
INFO[0000] applying database migrations
INFO[0000] handler/mqtt: connected to mqtt broker
INFO[0000] handler/mqtt: subscribing to tx topic qos=0 topic=application/+/device/+/tx
FATA[0000] applying migrations error: pq: relation “node” does not exist handling 0002_join_accept_params.sql

Thanks

It looks like your migration history is out of sync. This could for example happen when you:

  • Use the same database for LoRa App Server and LoRa Server
  • Make manual modifications (to the code or to the database)
  • Compile your own binaries using non-tagged Git revisions

See also: https://github.com/brocaar/lora-app-server/tree/v1.0.1/migrations. You will see that the node table which does not exist should have been created by 0001_initial.sql.

The migration history is stored in a table called gorp_migrations.

1 Like

Hi Brocaar,

it seems that i was using the same database for both,
However, after creating the loraserver database, it wont start now?

INFO[0000] starting LoRa App Server docs=“https://www.loraserver.io/” version=1.0.1
INFO[0000] connecting to postgresql
INFO[0000] setup redis connection pool
INFO[0000] handler/mqtt: TLS config is empty
INFO[0000] handler/mqtt: connecting to mqtt broker server=“tcp://localhost:1883”
INFO[0000] handler/mqtt: connected to mqtt broker
INFO[0000] handler/mqtt: subscribing to tx topic qos=0 topic=application/+/device/+/tx
INFO[0000] applying database migrations
FATA[0000] applying migrations error: pq: operator class “gin_trgm_ops” does not exist for access method “gin” handling 0027_global_search.sql

Please help…

Thanks

The search is your friend :slight_smile: This has been asked before and already answered how to fix.