HELP/QUESTION Research failed start #1816

ldexterldesign · 2022-04-08T16:41:54Z

ldexterldesign
Apr 8, 2022

👋

Thanks for software

My Miniflux service won't start after I a) start macOS and/or b) Docker daemon but it will when I manually start it 😕 - anyone know why this may be?

Log

Before I manually start:

miniflux  | -> Current schema version: 54
miniflux  | -> Latest schema version: 54
miniflux  | [INFO] User "ldexterldesign" already exists, skipping creation
miniflux  | [INFO] Starting Miniflux...
miniflux  | [INFO] Starting scheduler...
miniflux  | [INFO] Listening on "0.0.0.0:8080" without TLS
miniflux  | [ERROR] [UI:AppSession] store: session not found: JAQj591HIv6eamasPavGI_EWcUJQAKDdyUgeFNsj8iU=
miniflux  | [INFO] [UI:CheckLogin] username=ldexterldesign just logged in
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | -> Current schema version: 54
miniflux  | -> Latest schema version: 54
miniflux  | [INFO] User "ldexterldesign" already exists, skipping creation
miniflux  | [INFO] Starting Miniflux...
miniflux  | [INFO] Starting scheduler...
miniflux  | [INFO] Listening on "0.0.0.0:8080" without TLS
miniflux  | [INFO] Shutting down the process...
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
postgres  | The files belonging to this database system will be owned by user "postgres".
postgres  | This user must also own the server process.
postgres  | 
postgres  | The database cluster will be initialized with locale "en_US.utf8".
postgres  | The default database encoding has accordingly been set to "UTF8".
postgres  | The default text search configuration will be set to "english".
postgres  | 
postgres  | Data page checksums are disabled.
postgres  | 
postgres  | fixing permissions on existing directory /var/lib/postgresql/data ... ok
postgres  | creating subdirectories ... ok
postgres  | selecting dynamic shared memory implementation ... posix
postgres  | selecting default max_connections ... 100
postgres  | selecting default shared_buffers ... 128MB
postgres  | selecting default time zone ... Etc/UTC
postgres  | creating configuration files ... ok
postgres  | running bootstrap script ... ok
postgres  | performing post-bootstrap initialization ... ok
postgres  | syncing data to disk ... ok
postgres  | 
postgres  | 
postgres  | Success. You can now start the database server using:
postgres  | 
postgres  |     pg_ctl -D /var/lib/postgresql/data -l logfile start
postgres  | 
postgres  | initdb: warning: enabling "trust" authentication for local connections
postgres  | You can change this by editing pg_hba.conf or using the option -A, or
postgres  | --auth-local and --auth-host, the next time you run initdb.
postgres  | waiting for server to start....2022-04-07 23:47:35.808 UTC [49] LOG:  starting PostgreSQL 14.2 (Debian 14.2-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
postgres  | 2022-04-07 23:47:35.809 UTC [49] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres  | 2022-04-07 23:47:35.813 UTC [50] LOG:  database system was shut down at 2022-04-07 23:47:35 UTC
postgres  | 2022-04-07 23:47:35.817 UTC [49] LOG:  database system is ready to accept connections
postgres  |  done
postgres  | server started
postgres  | CREATE DATABASE
postgres  | 
postgres  | 
postgres  | /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
postgres  | 
postgres  | waiting for server to shut down...2022-04-07 23:47:36.048 UTC [49] LOG:  received fast shutdown request
postgres  | .2022-04-07 23:47:36.049 UTC [49] LOG:  aborting any active transactions
postgres  | 2022-04-07 23:47:36.050 UTC [49] LOG:  background worker "logical replication launcher" (PID 56) exited with exit code 1
postgres  | 2022-04-07 23:47:36.050 UTC [51] LOG:  shutting down
postgres  | 2022-04-07 23:47:36.059 UTC [49] LOG:  database system is shut down
postgres  |  done
postgres  | server stopped
postgres  | 
postgres  | PostgreSQL init process complete; ready for start up.
postgres  | 
postgres  | 2022-04-07 23:47:36.174 UTC [1] LOG:  starting PostgreSQL 14.2 (Debian 14.2-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
postgres  | 2022-04-07 23:47:36.174 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
postgres  | 2022-04-07 23:47:36.174 UTC [1] LOG:  listening on IPv6 address "::", port 5432
postgres  | 2022-04-07 23:47:36.176 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres  | 2022-04-07 23:47:36.180 UTC [63] LOG:  database system was shut down at 2022-04-07 23:47:36 UTC
postgres  | 2022-04-07 23:47:36.184 UTC [1] LOG:  database system is ready to accept connections
postgres  | 2022-04-07 23:47:41.323 UTC [70] ERROR:  relation "schema_version" does not exist at character 21
postgres  | 2022-04-07 23:47:41.323 UTC [70] STATEMENT:  SELECT version FROM schema_version
postgres  | 2022-04-08 00:01:04.452 UTC [1] LOG:  received fast shutdown request
postgres  | 2022-04-08 00:01:04.454 UTC [1] LOG:  aborting any active transactions
postgres  | 2022-04-08 00:01:04.457 UTC [1] LOG:  background worker "logical replication launcher" (PID 69) exited with exit code 1
postgres  | 2022-04-08 00:01:04.458 UTC [64] LOG:  shutting down
postgres  | 2022-04-08 00:01:04.481 UTC [1] LOG:  database system is shut down
postgres  | 
postgres  | PostgreSQL Database directory appears to contain a database; Skipping initialization
postgres  | 
postgres  | 2022-04-08 00:01:06.428 UTC [1] LOG:  starting PostgreSQL 14.2 (Debian 14.2-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
postgres  | 2022-04-08 00:01:06.428 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
postgres  | 2022-04-08 00:01:06.428 UTC [1] LOG:  listening on IPv6 address "::", port 5432
postgres  | 2022-04-08 00:01:06.432 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres  | 2022-04-08 00:01:06.437 UTC [27] LOG:  database system was shut down at 2022-04-08 00:01:04 UTC
postgres  | 2022-04-08 00:01:06.444 UTC [1] LOG:  database system is ready to accept connections
postgres  | 2022-04-08 15:35:58.968 UTC [32] LOG:  stats_timestamp 2022-04-08 15:35:58.988002+00 is later than collector's time 2022-04-08 15:35:58.96364+00 for database 13757
postgres  | 
postgres  | PostgreSQL Database directory appears to contain a database; Skipping initialization
postgres  | 
postgres  | 2022-04-08 16:18:36.440 UTC [1] LOG:  starting PostgreSQL 14.2 (Debian 14.2-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
postgres  | 2022-04-08 16:18:36.440 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
postgres  | 2022-04-08 16:18:36.440 UTC [1] LOG:  listening on IPv6 address "::", port 5432
postgres  | 2022-04-08 16:18:36.442 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres  | 2022-04-08 16:18:36.446 UTC [26] LOG:  database system was shut down at 2022-04-08 16:15:06 UTC
postgres  | 2022-04-08 16:18:36.458 UTC [1] LOG:  database system is ready to accept connections

After I manually start:

miniflux  | -> Current schema version: 54
miniflux  | -> Latest schema version: 54
miniflux  | [INFO] User "ldexterldesign" already exists, skipping creation
miniflux  | [INFO] Starting Miniflux...
miniflux  | [INFO] Starting scheduler...
miniflux  | [INFO] Listening on "0.0.0.0:8080" without TLS
miniflux  | [ERROR] [UI:AppSession] store: session not found: JAQj591HIv6eamasPavGI_EWcUJQAKDdyUgeFNsj8iU=
miniflux  | [INFO] [UI:CheckLogin] username=ldexterldesign just logged in
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | -> Current schema version: 54
miniflux  | -> Latest schema version: 54
miniflux  | [INFO] User "ldexterldesign" already exists, skipping creation
miniflux  | [INFO] Starting Miniflux...
miniflux  | [INFO] Starting scheduler...
miniflux  | [INFO] Listening on "0.0.0.0:8080" without TLS
miniflux  | [INFO] Shutting down the process...
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | [FATAL] Unable to connect to the database: dial tcp: lookup db on 127.0.0.11:53: no such host
miniflux  | -> Current schema version: 54
miniflux  | -> Latest schema version: 54
miniflux  | [INFO] User "ldexterldesign" already exists, skipping creation
miniflux  | [INFO] Starting Miniflux...
miniflux  | [INFO] Starting scheduler...
miniflux  | [INFO] Listening on "0.0.0.0:8080" without TLS
postgres  | The files belonging to this database system will be owned by user "postgres".
postgres  | This user must also own the server process.
postgres  | 
postgres  | The database cluster will be initialized with locale "en_US.utf8".
postgres  | The default database encoding has accordingly been set to "UTF8".
postgres  | The default text search configuration will be set to "english".
postgres  | 
postgres  | Data page checksums are disabled.
postgres  | 
postgres  | fixing permissions on existing directory /var/lib/postgresql/data ... ok
postgres  | creating subdirectories ... ok
postgres  | selecting dynamic shared memory implementation ... posix
postgres  | selecting default max_connections ... 100
postgres  | selecting default shared_buffers ... 128MB
postgres  | selecting default time zone ... Etc/UTC
postgres  | creating configuration files ... ok
postgres  | running bootstrap script ... ok
postgres  | performing post-bootstrap initialization ... ok
postgres  | syncing data to disk ... ok
postgres  | 
postgres  | 
postgres  | Success. You can now start the database server using:
postgres  | 
postgres  |     pg_ctl -D /var/lib/postgresql/data -l logfile start
postgres  | 
postgres  | initdb: warning: enabling "trust" authentication for local connections
postgres  | You can change this by editing pg_hba.conf or using the option -A, or
postgres  | --auth-local and --auth-host, the next time you run initdb.
postgres  | waiting for server to start....2022-04-07 23:47:35.808 UTC [49] LOG:  starting PostgreSQL 14.2 (Debian 14.2-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
postgres  | 2022-04-07 23:47:35.809 UTC [49] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres  | 2022-04-07 23:47:35.813 UTC [50] LOG:  database system was shut down at 2022-04-07 23:47:35 UTC
postgres  | 2022-04-07 23:47:35.817 UTC [49] LOG:  database system is ready to accept connections
postgres  |  done
postgres  | server started
postgres  | CREATE DATABASE
postgres  | 
postgres  | 
postgres  | /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
postgres  | 
postgres  | waiting for server to shut down...2022-04-07 23:47:36.048 UTC [49] LOG:  received fast shutdown request
postgres  | .2022-04-07 23:47:36.049 UTC [49] LOG:  aborting any active transactions
postgres  | 2022-04-07 23:47:36.050 UTC [49] LOG:  background worker "logical replication launcher" (PID 56) exited with exit code 1
postgres  | 2022-04-07 23:47:36.050 UTC [51] LOG:  shutting down
postgres  | 2022-04-07 23:47:36.059 UTC [49] LOG:  database system is shut down
postgres  |  done
postgres  | server stopped
postgres  | 
postgres  | PostgreSQL init process complete; ready for start up.
postgres  | 
postgres  | 2022-04-07 23:47:36.174 UTC [1] LOG:  starting PostgreSQL 14.2 (Debian 14.2-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
postgres  | 2022-04-07 23:47:36.174 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
postgres  | 2022-04-07 23:47:36.174 UTC [1] LOG:  listening on IPv6 address "::", port 5432
postgres  | 2022-04-07 23:47:36.176 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres  | 2022-04-07 23:47:36.180 UTC [63] LOG:  database system was shut down at 2022-04-07 23:47:36 UTC
postgres  | 2022-04-07 23:47:36.184 UTC [1] LOG:  database system is ready to accept connections
postgres  | 2022-04-07 23:47:41.323 UTC [70] ERROR:  relation "schema_version" does not exist at character 21
postgres  | 2022-04-07 23:47:41.323 UTC [70] STATEMENT:  SELECT version FROM schema_version
postgres  | 2022-04-08 00:01:04.452 UTC [1] LOG:  received fast shutdown request
postgres  | 2022-04-08 00:01:04.454 UTC [1] LOG:  aborting any active transactions
postgres  | 2022-04-08 00:01:04.457 UTC [1] LOG:  background worker "logical replication launcher" (PID 69) exited with exit code 1
postgres  | 2022-04-08 00:01:04.458 UTC [64] LOG:  shutting down
postgres  | 2022-04-08 00:01:04.481 UTC [1] LOG:  database system is shut down
postgres  | 
postgres  | PostgreSQL Database directory appears to contain a database; Skipping initialization
postgres  | 
postgres  | 2022-04-08 00:01:06.428 UTC [1] LOG:  starting PostgreSQL 14.2 (Debian 14.2-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
postgres  | 2022-04-08 00:01:06.428 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
postgres  | 2022-04-08 00:01:06.428 UTC [1] LOG:  listening on IPv6 address "::", port 5432
postgres  | 2022-04-08 00:01:06.432 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres  | 2022-04-08 00:01:06.437 UTC [27] LOG:  database system was shut down at 2022-04-08 00:01:04 UTC
postgres  | 2022-04-08 00:01:06.444 UTC [1] LOG:  database system is ready to accept connections
postgres  | 2022-04-08 15:35:58.968 UTC [32] LOG:  stats_timestamp 2022-04-08 15:35:58.988002+00 is later than collector's time 2022-04-08 15:35:58.96364+00 for database 13757
postgres  | 
postgres  | PostgreSQL Database directory appears to contain a database; Skipping initialization
postgres  | 
postgres  | 2022-04-08 16:18:36.440 UTC [1] LOG:  starting PostgreSQL 14.2 (Debian 14.2-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
postgres  | 2022-04-08 16:18:36.440 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
postgres  | 2022-04-08 16:18:36.440 UTC [1] LOG:  listening on IPv6 address "::", port 5432
postgres  | 2022-04-08 16:18:36.442 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres  | 2022-04-08 16:18:36.446 UTC [26] LOG:  database system was shut down at 2022-04-08 16:15:06 UTC
postgres  | 2022-04-08 16:18:36.458 UTC [1] LOG:  database system is ready to accept connections
postgres  | 
postgres  | PostgreSQL Database directory appears to contain a database; Skipping initialization
postgres  | 
postgres  | 2022-04-08 16:41:39.614 UTC [1] LOG:  starting PostgreSQL 14.2 (Debian 14.2-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
postgres  | 2022-04-08 16:41:39.615 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
postgres  | 2022-04-08 16:41:39.615 UTC [1] LOG:  listening on IPv6 address "::", port 5432
postgres  | 2022-04-08 16:41:39.616 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres  | 2022-04-08 16:41:39.620 UTC [27] LOG:  database system was shut down at 2022-04-08 16:38:23 UTC
postgres  | 2022-04-08 16:41:39.631 UTC [1] LOG:  database system is ready to accept connections

I reinstalled macOS last week hoping this problem was an install quirk but it's not

Docker compose:

version: '3.4'
services:
  miniflux:
    image: miniflux/miniflux:latest
    container_name: miniflux
    restart: unless-stopped
    ports:
      - "8080:8080"
    depends_on:
      - db
    environment:
      - DATABASE_URL=postgres://miniflux:secret@db/miniflux?sslmode=disable
      - RUN_MIGRATIONS=1
      - CREATE_ADMIN=1
      - ADMIN_USERNAME=ldexterldesign
      - ADMIN_PASSWORD=IMNGR2l1hr47iBq2bkDX
  db:
    image: postgres:latest
    container_name: postgres
    environment:
      - POSTGRES_USER=miniflux
      - POSTGRES_PASSWORD=secret
    volumes:
      - miniflux-db:/var/lib/postgresql/data
    healthcheck:
      test: ["CMD", "pg_isready", "-U", "miniflux"]
      interval: 10s
      start_period: 30s
volumes:
  miniflux-db:

If you're experiencing this then please vote up (e.g. +1, like)

Welcome feedback/input

Hope this helps and to hear back

Cheers

ldexterldesign · 2022-09-15T01:09:31Z

ldexterldesign
Sep 15, 2022
Author

BUMP

0 replies

Dusky · 2022-10-18T17:12:25Z

Dusky
Oct 18, 2022

I'm also having this issue using docker compose. Though mine does not work properly when I start manually.

0 replies

Dusky · 2022-10-20T15:55:08Z

Dusky
Oct 20, 2022

Changing to posgres 14 from latest fixed this for me

0 replies

ekasprzak · 2023-03-07T23:16:04Z

ekasprzak
Mar 7, 2023

Confirm that.
Freshly installed miniflux via docker (most recent basic.yml), postgres doesn't start automatically after OS or docker service restart, manual start is needed every time.

As @Dusky said, just downgrading postgres to 14 makes it work/autostart correctly.

1 reply

ekasprzak Mar 28, 2023

Confirm that. Freshly installed miniflux via docker (most recent basic.yml), postgres doesn't start automatically after OS or docker service restart, manual start is needed every time.

As @Dusky said, just downgrading postgres to 14 makes it work/autostart correctly.

I need to withdraw from it. I was doing some other changes probably and it just happened to work when I changed postgres version.

ldexterldesign · 2023-03-08T01:37:23Z

ldexterldesign
Mar 8, 2023
Author

It seems to me the next logical step here is to research if this is an upstream Postgres issue..?

I’m not the person to research, even if I had the bandwidth right now 😔

Aside, it would be lovely not to have to babysit this for a minute every time Docker starts 🤞

0 replies

renaldofreire · 2023-03-19T04:17:56Z

renaldofreire
Mar 19, 2023

Hello! I had the same problem using docker compose.

I was able to solve it just by changing the volume to an existing location:

Default

volumes:
      - miniflux-db:/var/lib/postgresql/data

Change to something like

volumes:
      - miniflux-db:/HOME/USER/docker/miniflux/data/

Just make sure the folder structure is correct.

0 replies

ldexterldesign · 2023-03-19T09:21:54Z

ldexterldesign
Mar 19, 2023
Author

@renaldofreire please post your docker-compose.yml

0 replies

renaldofreire · 2023-03-20T01:30:18Z

renaldofreire
Mar 20, 2023

@renaldofreire please post your docker-compose.yml

I hope it helps

See below:

services:
  miniflux:
    image: ${MINIFLUX_IMAGE:-miniflux/miniflux:latest}
    container_name: miniflux
    restart: unless-stopped
    ports:
      - "43000:8080"
    depends_on:
      db:
        condition: service_healthy
    environment:
      - DATABASE_URL=postgres://miniflux:secret@db/miniflux?sslmode=disable
      - RUN_MIGRATIONS=1
      - CREATE_ADMIN=1
      - ADMIN_USERNAME=admin
      - ADMIN_PASSWORD=3*&%djnalJSDa
      - DEBUG=1
    # Optional health check:
    # healthcheck:
    #  test: ["CMD", "/usr/bin/miniflux", "-healthcheck", "auto"]
  db:
    image: postgres:15
    container_name: postgres
    restart: unless-stopped
    environment:
      - POSTGRES_USER=miniflux
      - POSTGRES_PASSWORD=secret
    volumes:
      - miniflux-db:/home/sec-arch/Docker/miniflux/data/
      #- miniflux-db:/var/lib/postgresql/data
    healthcheck:
      test: ["CMD", "pg_isready", "-U", "miniflux"]
      interval: 10s
      start_period: 30s
volumes:
  miniflux-db:

0 replies

renaldofreire · 2023-03-20T01:33:41Z

renaldofreire
Mar 20, 2023

This "miniflux-db" volume seems to never be used (it's empty here), but that's how miniflux started to work correctly.

And I can't explain why. 😅

2 replies

ldexterldesign Mar 28, 2023
Author

Thanks for reply

I deleted this part of the docker file and set a relative path since posting my last code snippet, which didn't fix it for me so unsure why you have better luck 🤷..?:

volumes:
  miniflux-db:

Monirzadeh May 6, 2023

i have same issue try to setup with podman but miniflux give me

[FATAL] Unable to connect to the database: dial tcp: lookup db on 10.0.2.3:53: no such host

set postgresql 14 or set miniflus-db to a relative path not help.
postgresql work complitly fine but some how miniflux send request on port 53 and can't find database.
should i change DATABASE_URL or something like that?

ekasprzak · 2023-03-28T11:44:31Z

ekasprzak
Mar 28, 2023

@renaldofreire are you sure it's the volume PATH that made it work?

In my case, after a lot of testing I found out that adding "restart" property to db container makes it finally work.
That property is there in your YAML, but it's not in the default one provided in git, so maybe it's that which actually made it work?

Is there a reason why restart property is there for a miniflux container but NOT there for a db container?
Maybe it should be just added to default compose yaml?

2 replies

ldexterldesign Mar 28, 2023
Author

🎉 This seems to have fixed it for me

LucaRed Apr 4, 2026

I confirm that adding restart: always under db fixed the problem for me. Thanks!

I opened a PR to fix the basic.yml: #4213

HELP/QUESTION Research failed start #1816

Uh oh!

Uh oh!

Log

Replies: 10 comments · 5 replies

Uh oh!

ldexterldesign Sep 15, 2022 Author

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

ldexterldesign Mar 8, 2023 Author

Uh oh!

Uh oh!

ldexterldesign Mar 19, 2023 Author

Uh oh!

Uh oh!

Uh oh!

ldexterldesign Mar 28, 2023 Author

Uh oh!

Uh oh!

Uh oh!

ldexterldesign Mar 28, 2023 Author

Uh oh!

Replies: 10 comments 5 replies

ldexterldesign
Sep 15, 2022
Author

ldexterldesign
Mar 8, 2023
Author

ldexterldesign
Mar 19, 2023
Author

ldexterldesign Mar 28, 2023
Author

ldexterldesign Mar 28, 2023
Author