Hi all,
I had some issues during the installation of ChirpStack through Docker Compose (the process got stuck).
I worked on a Ubuntu VM (20.04.3 LTS) installed over Virtual Box
Docker version 20.10.12, build e91ed57
Docker Compose version 1.29.2, build 5becea4c
I followed exactly the guidelines on Chirpstack documentation.
First of all I cloned the repository: (git clone GitHub - brocaar/chirpstack-docker: Setup ChirpStack using Docker Compose)
I moved on the proper directory (cd chirpstack-docker)
And I started the installation (docker-compose up)
These are the logs:
root@vmchirpstack-VirtualBox:~/chirpstack-docker# docker-compose up
Recreating chirpstack-docker_mosquitto_1 … done
Starting chirpstack-docker_redis_1 … done
Recreating chirpstack-docker_postgresql_1 … done
Recreating chirpstack-docker_chirpstack-network-server_1 … done
Recreating chirpstack-docker_chirpstack-gateway-bridge_1 … done
Recreating chirpstack-docker_chirpstack-application-server_1 … done
Attaching to chirpstack-docker_redis_1, chirpstack-docker_postgresql_1, chirpstack-docker_mosquitto_1, chirpstack-docker_chirpstack-network-server_1, chirpstack-docker_chirpstack-gateway-bridge_1, chirpstack-docker_chirpstack-application-server_1
chirpstack-gateway-bridge_1 | time=“2022-02-25T15:32:21.349635027Z” level=info msg=“starting ChirpStack Gateway Bridge” docs=“Introduction - ChirpStack open-source LoRaWAN<sup>®</sup> Network Server” version=
chirpstack-gateway-bridge_1 | time=“2022-02-25T15:32:21.349690557Z” level=info msg=“backend/semtechudp: starting gateway udp listener” addr=“0.0.0.0:1700”
chirpstack-gateway-bridge_1 | time=“2022-02-25T15:32:21.377727768Z” level=warning msg="[store] memorystore wiped" module=mqtt
chirpstack-gateway-bridge_1 | time=“2022-02-25T15:32:21.380325677Z” level=info msg=“integration/mqtt: connected to mqtt broker”
chirpstack-network-server_1 | time=“2022-02-25T15:32:20.917339509Z” level=info msg=“starting ChirpStack Network Server” band=EU868 docs=“https://www.chirpstack.io/” net_id=000000 version=
chirpstack-network-server_1 | time=“2022-02-25T15:32:20.917414231Z” level=info msg=“storage: setting up storage module”
chirpstack-network-server_1 | time=“2022-02-25T15:32:20.917430218Z” level=info msg=“storage: setting up Redis client”
chirpstack-network-server_1 | time=“2022-02-25T15:32:20.920233181Z” level=info msg=“storage: connecting to PostgreSQL”
chirpstack-network-server_1 | time=“2022-02-25T15:32:21.047007088Z” level=info msg=“storage: applying PostgreSQL data migrations”
chirpstack-network-server_1 | time=“2022-02-25T15:32:21.089103167Z” level=info msg=“gateway/mqtt: connecting to mqtt broker” server=“tcp://mosquitto:1883”
chirpstack-network-server_1 | time=“2022-02-25T15:32:21.099178538Z” level=info msg=“api: starting network-server api server” bind=“0.0.0.0:8000” ca-cert= tls-cert= tls-key=
mosquitto_1 | 1645803136: mosquitto version 2.0.14 starting
chirpstack-network-server_1 | time=“2022-02-25T15:32:21.103938275Z” level=info msg=“starting downlink device-queue scheduler”
chirpstack-network-server_1 | time=“2022-02-25T15:32:21.103965791Z” level=info msg=“starting multicast scheduler”
chirpstack-network-server_1 | time=“2022-02-25T15:32:21.105308318Z” level=info msg=“backend/gateway: connected to mqtt server”
chirpstack-network-server_1 | time=“2022-02-25T15:32:21.105350125Z” level=info msg=“gateway/mqtt: subscribing to gateway event topic” qos=0 topic=gateway/+/event/+
mosquitto_1 | 1645803136: Config loaded from /mosquitto/config/mosquitto.conf.
mosquitto_1 | 1645803136: Opening ipv4 listen socket on port 1883.
mosquitto_1 | 1645803136: Opening ipv6 listen socket on port 1883.
mosquitto_1 | 1645803136: mosquitto version 2.0.14 running
mosquitto_1 | 1645803141: New connection from 172.19.0.5:58818 on port 1883.
mosquitto_1 | 1645803141: New client connected from 172.19.0.5:58818 as auto-00325730-AFFE-6E9F-623C-459B9987DD65 (p2, c1, k30).
mosquitto_1 | 1645803141: New connection from 172.19.0.6:38084 on port 1883.
mosquitto_1 | 1645803141: New client connected from 172.19.0.6:38084 as auto-B684A52C-DBF4-D484-2626-021F0E28BD0D (p2, c1, k30).
postgresql_1 |
postgresql_1 | PostgreSQL Database directory appears to contain a database; Skipping initialization
postgresql_1 |
postgresql_1 | LOG: database system was shut down at 2022-02-25 14:26:37 UTC
postgresql_1 | LOG: MultiXact member wraparound protections are now enabled
postgresql_1 | LOG: database system is ready to accept connections
postgresql_1 | LOG: autovacuum launcher started
redis_1 | 1:C 25 Feb 2022 15:32:16.435 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1 | 1:C 25 Feb 2022 15:32:16.435 # Redis version=5.0.14, bits=64, commit=00000000, modified=0, pid=1, just started
redis_1 | 1:C 25 Feb 2022 15:32:16.435 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
redis_1 | 1:M 25 Feb 2022 15:32:16.439 * Running mode=standalone, port=6379.
redis_1 | 1:M 25 Feb 2022 15:32:16.439 # Server initialized
redis_1 | 1:M 25 Feb 2022 15:32:16.439 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add ‘vm.overcommit_memory = 1’ to /etc/sysctl.conf and then reboot or run the command ‘sysctl vm.overcommit_memory=1’ for this to take effect.
redis_1 | 1:M 25 Feb 2022 15:32:16.439 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command ‘echo never > /sys/kernel/mm/transparent_hugepage/enabled’ as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
redis_1 | 1:M 25 Feb 2022 15:32:16.442 * DB loaded from disk: 0.002 seconds
redis_1 | 1:M 25 Feb 2022 15:32:16.442 * Ready to accept connections
chirpstack-application-server_1 | time=“2022-02-25T15:32:22.694226639Z” level=info msg=“starting ChirpStack Application Server” docs=“https://www.chirpstack.io/” version=
chirpstack-application-server_1 | time=“2022-02-25T15:32:22.69550009Z” level=info msg=“storage: setting up storage package”
chirpstack-application-server_1 | time=“2022-02-25T15:32:22.695894935Z” level=info msg=“storage: setup metrics”
chirpstack-application-server_1 | time=“2022-02-25T15:32:22.696351453Z” level=info msg=“storage: setting up Redis client”
chirpstack-application-server_1 | time=“2022-02-25T15:32:22.698739664Z” level=info msg=“storage: connecting to PostgreSQL database”
chirpstack-application-server_1 | time=“2022-02-25T15:32:22.785040426Z” level=info msg=“storage: applying PostgreSQL data migrations”
chirpstack-application-server_1 | time=“2022-02-25T15:32:22.851017196Z” level=info msg=“integration: configuring global integrations”
chirpstack-application-server_1 | time=“2022-02-25T15:32:22.851262886Z” level=info msg=“integration/mqtt: TLS config is empty”
chirpstack-application-server_1 | time=“2022-02-25T15:32:22.851282201Z” level=info msg=“integration/mqtt: connecting to mqtt broker” server=“tcp://mosquitto:1883”
mosquitto_1 | 1645803142: New connection from 172.19.0.7:51238 on port 1883.
mosquitto_1 | 1645803142: New client connected from 172.19.0.7:51238 as auto-E27E2C76-C9BA-E037-4128-5DB0C9593C90 (p2, c1, k30).
chirpstack-application-server_1 | time=“2022-02-25T15:32:22.858081228Z” level=info msg=“api/as: starting application-server api” bind=“0.0.0.0:8001” ca_cert= tls_cert= tls_key=
chirpstack-application-server_1 | time=“2022-02-25T15:32:22.860508159Z” level=info msg=“api/external: starting api server” bind=“0.0.0.0:8080” tls-cert= tls-key=
chirpstack-application-server_1 | time=“2022-02-25T15:32:22.861289441Z” level=info msg=“integration/mqtt: connected to mqtt broker”
chirpstack-application-server_1 | time=“2022-02-25T15:32:22.861324042Z” level=info msg=“integration/mqtt: subscribing to tx topic” qos=0 topic=application/+/device/+/command/down
chirpstack-application-server_1 | time=“2022-02-25T15:32:22.96743238Z” level=info msg=“api/external: registering rest api handler and documentation endpoint” path=/api
chirpstack-application-server_1 | time=“2022-02-25T15:32:22.967563484Z” level=info msg=“api/js: starting join-server api” bind=“0.0.0.0:8003” ca_cert= tls_cert= tls_key=
Afterwards the installation got stuck.
Is there something wrong? Do I have to add something in the .yml file or perform other modifications?
Thank you, regards
Alessandro