Synology Impossible d'installé jellystat via portainer

[bret]

Bonjour ,

je tente depuis ce matin d'installé jellystat sur mon ds916+, mais échec à chaque tentative , voci mon YALM et le message qui apparaît sur portainer

version: '3'
services:
  jellystat-db:
    image: 'postgres:15.2'
    shm_size: 1gb
    container_name: jellystat-db
    restart: unless-stopped
    environment:
      POSTGRES_USER: postgres
      POSTGRES_PASSWORD: masqué
    volumes:
      - 'postgres-data:/var/lib/postgresql/data'
  jellystat:
    image: 'cyfershepard/jellystat:latest'
    container_name: jellystat
    restart: unless-stopped
    environment:
      POSTGRES_USER: postgres
      POSTGRES_PASSWORD: masqué
      POSTGRES_IP: jellystat-db
      POSTGRES_PORT: 5432
      JWT_SECRET: masqué
      TZ: paris
    volumes:
      - 'jellystat-backup-data:/app/backend/backup-data'
    ports:
      - '3000:3000'
    depends_on:
      - jellystat-db
networks:
  default: null
volumes:
  postgres-data: null
  jellystat-backup-data: null
logging:
  driver: json-file
  options:
    max-file: '5'
    max-size: 10m

Voir la pièce jointe 15992

 

[bliz]

essaye d'enlever les `

 

[bret]

j'avais oublié le message d'erreur ! je vais tenter ta solution , on verra bien

Ps: pas mieux !

 

[morgyann]

essaye d'enlever les `

Les ' c'est pour la console en SSH mais sur Portainer y'en a pas (comme vient de l'indiquer @bret)

 

[EVO]

Ce compose est faux. je vois qu'il est corrigé dans la version unstable.

Le voici : https://github.com/CyferShepard/Jellystat/blob/unstable/docker-compose.yml

version: '3'

services:
  jellystat-db:
    image: postgres:15.2
    shm_size: '1gb'
    container_name: jellystat-db
    restart: unless-stopped
    logging:
      driver: "json-file"
      options:
        max-file: "5"
        max-size: "10m"
    environment:
      POSTGRES_USER: postgres
      POSTGRES_PASSWORD: mypassword
    volumes:
      - postgres-data:/var/lib/postgresql/data

  jellystat:
    image: cyfershepard/jellystat:latest
    container_name: jellystat
    restart: unless-stopped
    logging:
      driver: "json-file"
      options:
        max-file: "5"
        max-size: "10m"
    environment:
      POSTGRES_USER: postgres
      POSTGRES_PASSWORD: mypassword
      POSTGRES_IP: jellystat-db
      POSTGRES_PORT: 5432
      JWT_SECRET: "my-secret-jwt-key"
      TZ: mytimezone # timezone (ex: Europe/Paris)
    volumes:
      - jellystat-backup-data:/app/backend/backup-data
    ports:
      - "3000:3000"
    depends_on:
      - jellystat-db
      
networks:
  default:

volumes:
  postgres-data:
  jellystat-backup-data:

 

[bret]

j'ai encore une erreur malgré ta modification @EVO

> jfstat@1.1.6 start
> cd backend && node server.js
env.js file has been saved successfully.
[JELLYSTAT]: Error occurred while executing query: Connection terminated due to connection timeout
[JELLYSTAT]: Error occurred while executing query: Connection terminated due to connection timeout
[JELLYSTAT]: Error occurred while executing query: Connection terminated due to connection timeout
[JELLYSTAT]: Error occurred while executing query: Connection terminated due to connection timeout

Message automatiquement fusionné : 13 Mai 2025

> jfstat@1.1.6 start
> cd backend && node server.js
env.js file has been saved successfully.
[JELLYSTAT]: Error occurred while executing query: Connection terminated due to connection timeout
[JELLYSTAT]: Error occurred while executing query: Connection terminated due to connection timeout
[JELLYSTAT]: Error occurred while executing query: Connection terminated due to connection timeout
[JELLYSTAT]: Error occurred while executing query: Connection terminated due to connection timeout
[JELLYSTAT]: Error occurred while executing query: Connection terminated due to connection timeout
[JELLYSTAT]: Error occurred while executing query: Connection terminated due to connection timeout
[JELLYSTAT]: Error occurred while executing query: Connection terminated due to connection timeout
[JELLYSTAT]: Error occurred while executing query: Connection terminated due to connection timeout
[JELLYSTAT]: Error occurred while executing query: Connection terminated due to connection timeout
[JELLYSTAT]: Error occurred while executing query: Connection terminated due to connection timeout
[JELLYSTAT]: Error occurred while executing query: Connection terminated due to connection timeout
[JELLYSTAT]: Error occurred while executing query: Connection terminated due to connection timeout
[JELLYSTAT]: Error occurred while executing query: Connection terminated due to connection timeout
[JELLYSTAT]: Error occurred while executing query: Connection terminated due to connection timeout
[JELLYSTAT]: Error occurred while executing query: Connection terminated due to connection timeout
[JELLYSTAT]: Error occurred while executing query: Connection terminated due to connection timeout
[JELLYSTAT]: Error occurred while executing query: Connection terminated due to connection timeout
[JELLYSTAT]: Error occurred while executing query: Connection terminated due to connection timeout
[JELLYSTAT]: Error occurred while executing query: Connection terminated due to connection timeout
[JELLYSTAT]: Error occurred while executing query: Connection terminated due to connection timeout
[JELLYSTAT]: Error occurred while executing query: Connection terminated due to connection timeout
[JELLYSTAT]: Error occurred while executing query: Connection terminated due to connection timeout
[JELLYSTAT]: Error occurred while executing query: Connection terminated due to connection timeout
[JELLYSTAT]: Error occurred while executing query: Connection terminated due to connection timeout
[JELLYSTAT]: Error occurred while executing query: Connection terminated due to connection timeout
Error: connect ETIMEDOUT 172.23.0.2:5432
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1636:16)
[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]: Error occurred while executing query: Connection terminated due to connection timeout
[JELLYSTAT]: Error occurred while executing query: Connection terminated due to connection timeout
[JELLYSTAT]: Error occurred while executing query: Connection terminated due to connection timeout
[JELLYSTAT]: Error occurred while executing query: Connection terminated due to connection timeout
[JELLYSTAT]: Error occurred while executing query: Connection terminated due to connection timeout
[JELLYSTAT]: Error occurred while executing query: Connection terminated due to connection timeout
/app/node_modules/knex/lib/client.js:332
        convertedError = new KnexTimeoutError(
                         ^
KnexTimeoutError: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?
    at Client_PG.acquireConnection (/app/node_modules/knex/lib/client.js:332:26)
    at async Runner.ensureConnection (/app/node_modules/knex/lib/execution/runner.js:305:28)
    at async Runner.run (/app/node_modules/knex/lib/execution/runner.js:30:19)
    at async listCompleted (/app/node_modules/knex/lib/migrations/migrate/migration-list-resolver.js:12:3)
    at async Promise.all (index 1)
    at async Migrator.latest (/app/node_modules/knex/lib/migrations/migrate/Migrator.js:63:29) {
  sql: undefined,
  bindings: undefined
}
Node.js v23.11.0
npm notice
npm notice New major version of npm available! 10.9.2 -> 11.3.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.3.0
npm notice To update run: npm install -g npm@11.3.0
npm notice
> jfstat@1.1.6 start
> cd backend && node server.js
env.js file has been saved successfully.
[JELLYSTAT]: Error occurred while executing query: Connection terminated due to connection timeout
[JELLYSTAT]: Error occurred while executing query: Connection terminated due to connection timeout

 

[EVO]

on dirai que la DB n'a pas répondu assez vite. Tu a essayé de relancer la stack ?

 

[bret]

oui, plusieurs fois ! que ce soit Synology ou Qnap ... c'est un dur combat pour les installations sous portainer

Message automatiquement fusionné : 13 Mai 2025

faut il créer des dossiers dans docker ?

 

[bret]

Hourra, j'ai enfin réussi , au moins 50 tentatives .... , par contre ces IP c'est normal ?