jellystat_user 'FATAL: database "jellystat_user" does not exist

[Jurrer]

Describe the bug
Hello, parsing of env variables for DB has some bug, because it tries to find a DB named like db user
I happens on container startup.

jellystat_user 'FATAL: database "jellystat_user" does not exist <- this is a log from Postgres

Here's my current env var config

    environment:
      TZ: ${TZ}
      JWT_SECRET: ${JELLYSTAT_JWT_KEY}
      POSTGRES_USER: jellystat_user
      POSTGRES_PASSWORD: ${JELLYSTAT_PG_PASS}
      POSTGRES_IP: postgresql
      POSTGRES_PORT: 5432
      POSTGRES_DB: jellystat
      MINIMUM_SECONDS_TO_INCLUDE_PLAYBACK: 60

Environment Details (please complete the following information):

• OS: Docker
• Jellystat Version 1.1.10

To Reproduce
Steps to reproduce the behavior:

1. Set up Jellystat with Postgres DB
2. Launch the container
3. See first logs

Expected behavior
No error

Container Logs

    at Parser.parseErrorMessage (/app/node_modules/pg-protocol/dist/parser.js:285:98)
    at Parser.handlePacket (/app/node_modules/pg-protocol/dist/parser.js:122:29)
    at Parser.parse (/app/node_modules/pg-protocol/dist/parser.js:35:38)
    at Socket.<anonymous> (/app/node_modules/pg-protocol/dist/index.js:11:42)
    at Socket.emit (node:events:519:28)
    at addChunk (node:internal/streams/readable:561:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
    at Readable.push (node:internal/streams/readable:392:5)
    at TCP.onStreamRead (node:internal/stream_base_commons:189:23)
[JELLYSTAT] Database exists. Skipping creation
FS-related option specified for migration configuration. This resets migrationSource to default FsMigrations
FS-related option specified for migration configuration. This resets migrationSource to default FsMigrations```

[EVOTk]

Hello,
It's new install ? pls share compose and .env to test

[hiSandog]

The log suggests the client is connecting without POSTGRES_DB being applied, so PostgreSQL falls back to using the username as the database name. It would help to see the full compose service for both Jellystat and Postgres, including whether the app expects POSTGRES_DB, POSTGRES_DATABASE, or a connection URL. Also worth checking whether the database container was initialized before POSTGRES_DB: jellystat was added, since Postgres only creates the initial DB on first volume initialization.

[Jurrer]

Hi!
So my compose is pretty convoluted and I want to only share stuff that is relevant, that's why I shared only the environment: part.
I don't have .env file. Not a new install, this error was from the beginning.
The postgres database is shared across multiple services and it functions properly. It is already running when jellystat starts up.

To clarify, jellystat works and uses the postgres database.

I created this issue because of this error. I think indicates a logic issue as previous comment suggests.
Not sure why the rest of the compose is relevant. I'm running postgres 17 but it's not the official image.

  jellystat:
    image: cyfershepard/jellystat:latest
    container_name: jellystat
    environment:
      TZ: ${TZ}
      JWT_SECRET: ${JELLYSTAT_JWT_KEY}
      POSTGRES_USER: jellystat_user
      POSTGRES_PASSWORD: ${JELLYSTAT_PG_PASS}
      POSTGRES_IP: postgresql
      POSTGRES_PORT: 5432
      POSTGRES_DB: jellystat
      MINIMUM_SECONDS_TO_INCLUDE_PLAYBACK: 60
    labels:
[redacted]
    volumes:
      - backup_data:/app/backend/backup-data
    networks:
      some_network:
    restart: unless-stopped

  postgresql:
    image: postgres_vector:17
    container_name: postgresql
    networks:
      some_network:
    restart: unless-stopped

Here's the container logs once again. It's all the logs since container starts.

env.js file has been saved successfully.
error: database "jellystat_user" does not exist
    at parseErrorMessage (/app/node_modules/pg-protocol/dist/parser.js:305:11)
    at Parser.handlePacket (/app/node_modules/pg-protocol/dist/parser.js:143:27)
    at Parser.parse (/app/node_modules/pg-protocol/dist/parser.js:37:38)
    at Socket.<anonymous> (/app/node_modules/pg-protocol/dist/index.js:11:42)
    at Socket.emit (node:events:509:20)
    at addChunk (node:internal/streams/readable:568:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:519:3)
    at Readable.push (node:internal/streams/readable:399:5)
    at TCP.onStreamRead (node:internal/stream_base_commons:189:23)
[JELLYSTAT] Database exists. Skipping creation
FS-related option specified for migration configuration. This resets migrationSource to default FsMigrations
FS-related option specified for migration configuration. This resets migrationSource to default FsMigrations
[JELLYSTAT] Server listening on http://0.0.0.0:3000/
Task Manager Singleton created
Task Scheduler Singleton created
[ActivityMonitor] Starting adaptive polling with idle interval: 5000ms
[ActivityMonitor] Loaded settings: { activeSessionsInterval: 1000, idleInterval: 5000 }

[Jurrer]

I noticed someone else reported similar issue in the past. #327
One thing we have in common - we use non default environment variables to connect to postgres.
Maybe it's hardcoded somewhere and it causes this issue.

[Jurrer]

hi @hiSandog @EVOTk
I've investigated it myself and prepared a PR with a fix. Could you take a look and review? #541