I have been trying to install open-balena in my server and have stumbled upon a problem that I can’t surprass. I have followed the guide Openbalena Getting Started Guide | Open Balena and everything seems to work perfectly until I input this command “./scripts/compose up -d” because it does everything as normal but doesn’t start correctly, when I do the “./scripts/compose up” It gives me this
api_1 | Systemd init system enabled.
balena-mdns-publisher_1 | Systemd init system enabled.
cert-provider_1 | [Info] VALIDATION not set. Using default: http-01
cert-provider_1 | [Info] Waiting for api.openbalena.local to be available via HTTP…
cert-provider_1 | [Info] (1/3) Connecting…
db_1 |
db_1 | PostgreSQL Database directory appears to contain a database; Skipping initialization
db_1 |
openbalena_api_1 exited with code 255
haproxy_1 | Building certificate from environment variables…
db_1 | 2024-04-17 10:50:07.298 UTC [1] LOG: starting PostgreSQL 14.3 (Debian 14.3-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
db_1 | 2024-04-17 10:50:07.314 UTC [1] LOG: listening on IPv4 address “0.0.0.0”, port 5432
db_1 | 2024-04-17 10:50:07.314 UTC [1] LOG: listening on IPv6 address “::”, port 5432
haproxy_1 | Setting up watches. Beware: since -r was given, this may take a while!
haproxy_1 | Watches established.
db_1 | 2024-04-17 10:50:07.392 UTC [1] LOG: listening on Unix socket “/var/run/postgresql/.s.PGSQL.5432”
cert-provider_1 | [Info] (1/3) Failed. Retrying in 5 seconds…
db_1 | 2024-04-17 10:50:07.593 UTC [30] LOG: database system was shut down at 2024-04-17 10:46:54 UTC
db_1 | 2024-04-17 10:50:07.735 UTC [1] LOG: database system is ready to accept connections
registry_1 | Systemd init system enabled.
vpn_1 | Systemd init system enabled.
s3_1 | Systemd init system enabled.
openbalena_s3_1 exited with code 255
openbalena_balena-mdns-publisher_1 exited with code 255
redis_1 | 1:C 17 Apr 2024 10:50:07.303 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see vm.max_map_count growing steadily when vm.overcommit_memory is 2 · Issue #1328 · jemalloc/jemalloc · GitHub. 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:C 17 Apr 2024 10:50:07.303 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1 | 1:C 17 Apr 2024 10:50:07.303 * Redis version=7.2.4, bits=64, commit=00000000, modified=0, pid=1, just started
redis_1 | 1:C 17 Apr 2024 10:50:07.303 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
openbalena_vpn_1 exited with code 255
openbalena_registry_1 exited with code 255
redis_1 | 1:M 17 Apr 2024 10:50:07.304 * monotonic clock: POSIX clock_gettime
redis_1 | 1:M 17 Apr 2024 10:50:07.304 * Running mode=standalone, port=6379.
redis_1 | 1:M 17 Apr 2024 10:50:07.305 * Server initialized
redis_1 | 1:M 17 Apr 2024 10:50:07.305 * Loading RDB produced by version 7.2.4
redis_1 | 1:M 17 Apr 2024 10:50:07.305 * RDB age 193 seconds
redis_1 | 1:M 17 Apr 2024 10:50:07.305 * RDB memory usage when created 0.83 Mb
redis_1 | 1:M 17 Apr 2024 10:50:07.305 * Done loading RDB, keys loaded: 0, keys expired: 0.
redis_1 | 1:M 17 Apr 2024 10:50:07.305 * DB loaded from disk: 0.000 seconds
redis_1 | 1:M 17 Apr 2024 10:50:07.305 * Ready to accept connections tcp
cert-provider_1 | [Info] (2/3) Connecting…
cert-provider_1 | [Info] (2/3) Failed. Retrying in 5 seconds…
cert-provider_1 | [Info] (3/3) Connecting…
cert-provider_1 | [Info] (3/3) Failed!
cert-provider_1 | [Info] Unable to access api.openbalena.local on port 80. This is needed for certificate validation. Retrying in 30 seconds…
haproxy_1 | [WARNING] 107/105011 (16) : parsing [/usr/local/etc/haproxy/haproxy.cfg:77] : ‘server balena_api_1’ : could not resolve address ‘api’, disabling server.
haproxy_1 | [WARNING] 107/105011 (16) : parsing [/usr/local/etc/haproxy/haproxy.cfg:83] : ‘server balena_registry_1’ : could not resolve address ‘registry’, disabling server.
haproxy_1 | [WARNING] 107/105011 (16) : parsing [/usr/local/etc/haproxy/haproxy.cfg:89] : ‘server balena_vpn_1’ : could not resolve address ‘vpn’, disabling server.
cert-provider_1 | [Info] Waiting for api.openbalena.local to be available via HTTP…
cert-provider_1 | [Info] (1/3) Connecting…
cert-provider_1 | [Info] (1/3) Failed. Retrying in 5 seconds…
haproxy_1 | [WARNING] 107/105011 (16) : parsing [/usr/local/etc/haproxy/haproxy.cfg:95] : ‘server balena_s3_1’ : could not resolve address ‘s3’, disabling server.
cert-provider_1 | [Info] (2/3) Connecting…
cert-provider_1 | [Info] (2/3) Failed. Retrying in 5 seconds…
cert-provider_1 | [Info] (3/3) Connecting…
cert-provider_1 | [Info] (3/3) Failed!
cert-provider_1 | [Info] Unable to access api.openbalena.local on port 80. This is needed for certificate validation. Retrying in 30 seconds…
haproxy_1 | [WARNING] 107/105011 (16) : parsing [/usr/local/etc/haproxy/haproxy.cfg:105] : ‘server balena_vpn_1’ : could not resolve address ‘vpn’, disabling server.
haproxy_1 | [WARNING] 107/105011 (16) : parsing [/usr/local/etc/haproxy/haproxy.cfg:130] : ‘server balena_vpn’ : could not resolve address ‘vpn’, disabling server.
haproxy_1 | [WARNING] 107/105011 (16) : parsing [/usr/local/etc/haproxy/haproxy.cfg:135] : ‘server balena_vpn’ : could not resolve address ‘vpn’, disabling server.
haproxy_1 | [NOTICE] 107/105011 (16) : New worker #1 (18) forked
cert-provider_1 | [Info] Waiting for api.openbalena.local to be available via HTTP…
cert-provider_1 | [Info] (1/3) Connecting…
cert-provider_1 | [Info] (1/3) Failed. Retrying in 5 seconds…
cert-provider_1 | [Info] (2/3) Connecting…
cert-provider_1 | [Info] (2/3) Failed. Retrying in 5 seconds…
cert-provider_1 | [Info] (3/3) Connecting…
cert-provider_1 | [Info] (3/3) Failed!
cert-provider_1 | [Info] Unable to access api.openbalena.local on port 80. This is needed for certificate validation. Retrying in 30 seconds…
I have been trying this past weeks to see if it’s a problem with the server configuration or with the actual open-balena instalation, I have reinstalled it and all but I can’t seem to fix it. The dockers itself work because I can use sdkmanager with it.