search

coollabsio / coolify

An open-source & self-hostable Heroku / Netlify / Vercel alternative.
https://coolify.io
Apache License 2.0
34.36k stars 1.87k forks source link

[Bug]: Umami Analytics service fails on ARM Servers #1306

Closed otekdo closed 3 months ago

otekdo commented 1 year ago

Description

I installed Coolify in a fresh ARM Server image

When i run a new service Umami Analytics image

Web app is not available to reach image

My VPS has the following firewall configuration: sudo ufw status image

Minimal Reproduction (if possible, example repository)

Exception or Error

These are NO error logs, but build logs from the resources:

Umami

2023-10-11T11:50:51.207707387Z yarn run v1.22.19
2023-10-11T11:50:51.323394202Z $ npm-run-all check-db update-tracker start-server
2023-10-11T11:50:52.080547417Z $ node scripts/check-db.js
2023-10-11T11:50:52.296137256Z ✓ DATABASE_URL is defined.
2023-10-11T11:50:52.427150942Z ✓ Database connection successful.
2023-10-11T11:50:52.508032657Z ✓ Database version check successful.
2023-10-11T11:50:54.219311456Z Prisma schema loaded from prisma/schema.prisma
2023-10-11T11:50:54.219349496Z Datasource "db": PostgreSQL database "umami", schema "public" at "postgresql:5432"
2023-10-11T11:50:54.219355696Z 
2023-10-11T11:50:54.219360096Z 3 migrations found in prisma/migrations
2023-10-11T11:50:54.219363696Z 
2023-10-11T11:50:54.219366496Z Applying migration `01_init`
2023-10-11T11:50:54.219369416Z Applying migration `02_report_schema_session_data`
2023-10-11T11:50:54.219372656Z Applying migration `03_metric_performance_index`
2023-10-11T11:50:54.219375696Z 
2023-10-11T11:50:54.219378456Z The following migrations have been applied:
2023-10-11T11:50:54.219381336Z 
2023-10-11T11:50:54.219384256Z migrations/
2023-10-11T11:50:54.219387056Z   └─ 01_init/
2023-10-11T11:50:54.219390816Z     └─ migration.sql
2023-10-11T11:50:54.219393736Z   └─ 02_report_schema_session_data/
2023-10-11T11:50:54.219397056Z     └─ migration.sql
2023-10-11T11:50:54.219399896Z   └─ 03_metric_performance_index/
2023-10-11T11:50:54.219402976Z     └─ migration.sql
2023-10-11T11:50:54.219405976Z       
2023-10-11T11:50:54.219408856Z All migrations have been successfully applied.
2023-10-11T11:50:54.219411856Z 
2023-10-11T11:50:54.219418216Z ✓ Database is up to date.
2023-10-11T11:50:54.628651787Z $ node scripts/update-tracker.js
2023-10-11T11:50:55.113339874Z $ node server.js
2023-10-11T11:50:56.477851829Z   ▲ Next.js 13.5.2
2023-10-11T11:50:56.477887229Z   - Local:        http://localhost:3000
2023-10-11T11:50:56.477891629Z   - Network:      http://0.0.0.0:3000
2023-10-11T11:50:56.477912829Z 
2023-10-11T11:50:56.477917469Z  ✓ Ready in 896ms

PostgreSQL

2023-10-11T11:50:45.075750188Z The files belonging to this database system will be owned by user "postgres".
2023-10-11T11:50:45.075797708Z This user must also own the server process.
2023-10-11T11:50:45.075801668Z 
2023-10-11T11:50:45.075804268Z The database cluster will be initialized with locale "en_US.utf8".
2023-10-11T11:50:45.075807188Z The default database encoding has accordingly been set to "UTF8".
2023-10-11T11:50:45.075809908Z The default text search configuration will be set to "english".
2023-10-11T11:50:45.075812748Z 
2023-10-11T11:50:45.075815348Z Data page checksums are disabled.
2023-10-11T11:50:45.075819548Z 
2023-10-11T11:50:45.075890388Z fixing permissions on existing directory /var/lib/postgresql/data ... ok
2023-10-11T11:50:45.077119108Z creating subdirectories ... ok
2023-10-11T11:50:45.077152668Z selecting dynamic shared memory implementation ... posix
2023-10-11T11:50:45.098506576Z selecting default max_connections ... 100
2023-10-11T11:50:45.119428044Z selecting default shared_buffers ... 128MB
2023-10-11T11:50:45.209471793Z selecting default time zone ... UTC
2023-10-11T11:50:45.212101272Z creating configuration files ... ok
2023-10-11T11:50:45.378050339Z running bootstrap script ... ok
2023-10-11T11:50:46.058360397Z performing post-bootstrap initialization ... ok
2023-10-11T11:50:46.215740189Z syncing data to disk ... ok
2023-10-11T11:50:46.215787029Z 
2023-10-11T11:50:46.215796229Z 
2023-10-11T11:50:46.215869669Z Success. You can now start the database server using:
2023-10-11T11:50:46.215877509Z 
2023-10-11T11:50:46.215883629Z     pg_ctl -D /var/lib/postgresql/data -l logfile start
2023-10-11T11:50:46.215889789Z 
2023-10-11T11:50:46.282821351Z waiting for server to start....2023-10-11 11:50:46.282 UTC [36] LOG:  starting PostgreSQL 15.4 on aarch64-unknown-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924, 64-bit
2023-10-11T11:50:46.284263870Z 2023-10-11 11:50:46.284 UTC [36] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-10-11T11:50:46.289459907Z 2023-10-11 11:50:46.289 UTC [39] LOG:  database system was shut down at 2023-10-11 11:50:46 UTC
2023-10-11T11:50:46.296553183Z 2023-10-11 11:50:46.296 UTC [36] LOG:  database system is ready to accept connections
2023-10-11T11:50:46.352903992Z  done
2023-10-11T11:50:46.352932392Z server started
2023-10-11T11:50:46.421698793Z CREATE DATABASE
2023-10-11T11:50:46.422453233Z 
2023-10-11T11:50:46.422569433Z 
2023-10-11T11:50:46.422578153Z /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
2023-10-11T11:50:46.422582833Z 
2023-10-11T11:50:46.423689312Z waiting for server to shut down....2023-10-11 11:50:46.423 UTC [36] LOG:  received fast shutdown request
2023-10-11T11:50:46.427802670Z 2023-10-11 11:50:46.425 UTC [36] LOG:  aborting any active transactions
2023-10-11T11:50:46.428412229Z 2023-10-11 11:50:46.428 UTC [36] LOG:  background worker "logical replication launcher" (PID 42) exited with exit code 1
2023-10-11T11:50:46.433059827Z 2023-10-11 11:50:46.432 UTC [37] LOG:  shutting down
2023-10-11T11:50:46.437865504Z 2023-10-11 11:50:46.437 UTC [37] LOG:  checkpoint starting: shutdown immediate
2023-10-11T11:50:46.479666760Z 2023-10-11 11:50:46.479 UTC [37] LOG:  checkpoint complete: wrote 918 buffers (5.6%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.021 s, sync=0.017 s, total=0.047 s; sync files=301, longest=0.002 s, average=0.001 s; distance=4222 kB, estimate=4222 kB
2023-10-11T11:50:46.488127036Z 2023-10-11 11:50:46.487 UTC [36] LOG:  database system is shut down
2023-10-11T11:50:46.524293855Z  done
2023-10-11T11:50:46.524327495Z server stopped
2023-10-11T11:50:46.525257495Z 
2023-10-11T11:50:46.525272175Z PostgreSQL init process complete; ready for start up.
2023-10-11T11:50:46.525277895Z 
2023-10-11T11:50:45.594202257Z sh: locale: not found
2023-10-11T11:50:45.594299937Z 2023-10-11 11:50:45.594 UTC [30] WARNING:  no usable system locales were found
2023-10-11T11:50:46.215788949Z initdb: warning: enabling "trust" authentication for local connections
2023-10-11T11:50:46.215846229Z initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb.
2023-10-11T11:50:46.551496640Z 2023-10-11 11:50:46.551 UTC [1] LOG:  starting PostgreSQL 15.4 on aarch64-unknown-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924, 64-bit
2023-10-11T11:50:46.551529480Z 2023-10-11 11:50:46.551 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2023-10-11T11:50:46.551546800Z 2023-10-11 11:50:46.551 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2023-10-11T11:50:46.553591559Z 2023-10-11 11:50:46.553 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-10-11T11:50:46.558499156Z 2023-10-11 11:50:46.558 UTC [52] LOG:  database system was shut down at 2023-10-11 11:50:46 UTC
2023-10-11T11:50:46.566520192Z 2023-10-11 11:50:46.566 UTC [1] LOG:  database system is ready to accept connections
2023-10-11T11:50:52.580343016Z 2023-10-11 11:50:52.580 UTC [65] ERROR:  relation "_prisma_migrations" does not exist at character 15
2023-10-11T11:50:52.580404216Z 2023-10-11 11:50:52.580 UTC [65] STATEMENT:  select * from _prisma_migrations where started_at < '2023-04-17'
2023-10-11T11:50:53.836940031Z 2023-10-11 11:50:53.836 UTC [66] LOG:  could not receive data from client: Connection reset by peer
2023-10-11T11:55:46.655404218Z 2023-10-11 11:55:46.655 UTC [50] LOG:  checkpoint starting: time
2023-10-11T11:56:06.225250057Z 2023-10-11 11:56:06.225 UTC [50] LOG:  checkpoint complete: wrote 198 buffers (1.2%); 0 WAL file(s) added, 0 removed, 0 recycled; write=19.550 s, sync=0.016 s, total=19.570 s; sync files=149, longest=0.001 s, average=0.001 s; distance=1133 kB, estimate=1133 kB

Version

v4.0.0-beta.77

rijavecb commented 1 year ago

Hey! Not sure if this is helpful as I was trying to run Umami through CapRover, also on ARM server through Hetzner. I was also having Umami fail when trying to use PostgreSQL but once I switched it to MySQL it started working fine. I now ran into issues with CapRover and am considering Coolify hence how I found this.

Thank you for making Coolify Andras, and I apologize for possibly off-topic comment.