Application it failure
guievas
HOBBYOP

2 years ago

i have this log, and i don't undertand why ? And i not an developeur expert.

PostgreSQL Database directory appears to contain a database; Skipping initialization

2024-02-03 16:59:21.199 UTC [8] LOG: starting PostgreSQL 15.5 (Ubuntu 15.5-1.pgdg22.04+1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, 64-bit

2024-02-03 16:59:21.199 UTC [8] LOG: listening on IPv4 address "0.0.0.0", port 5432

2024-02-03 16:59:21.199 UTC [8] LOG: listening on IPv6 address "::", port 5432

2024-02-03 16:59:21.204 UTC [8] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"

2024-02-03 16:59:21.210 UTC [35] LOG: database system was interrupted; last known up at 2024-02-03 16:46:32 UTC

2024-02-03 16:59:21.250 UTC [35] LOG: database system was not properly shut down; automatic recovery in progress

2024-02-03 16:59:21.253 UTC [35] LOG: redo starts at 0/28EFAD8

2024-02-03 16:59:21.253 UTC [35] LOG: invalid record length at 0/28EFB10: wanted 24, got 0

2024-02-03 16:59:21.253 UTC [35] LOG: redo done at 0/28EFAD8 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s

2024-02-03 16:59:21.259 UTC [33] LOG: checkpoint starting: end-of-recovery immediate wait

2024-02-03 16:59:21.269 UTC [33] LOG: checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.004 s, sync=0.002 s, total=0.012 s; sync files=2, longest=0.001 s, average=0.001 s; distance=0 kB, estimate=0 kB

2024-02-03 16:59:21.276 UTC [8] LOG: database system is ready to accept connections

2024-02-03 16:59:21.277 UTC [38] LOG: TimescaleDB background worker launcher connected to shared catalogs

Solved

4 Replies

ray-chen
EMPLOYEE

2 years ago

Are you facing any issues connecting to it? Those logs can be ignored.


Status changed to Solved Railway almost 2 years ago


guievas
HOBBYOP

2 years ago

Thank you for taking the time to respond. No, I have access to my database, I can see all the fields and the content.


guievas
HOBBYOP

2 years ago

I have olso those log but on my API : (if i undersatand corectly)

npm WARN config production Use --omit=dev instead.
projet-03-evas-back@1.0.0 start
node index.js
Server ready: http://localhost:3000
connect ECONNREFUSED 34.82.192.130:6820


guievas
HOBBYOP

2 years ago

  • npm WARN config production Use --omit=dev instead.

  • projet-03-evas-back@1.0.0 start

  • node index.js

  • Server ready: http://localhost:3000

  • connect ECONNREFUSED 34.82.192.130:6820


Loading...