starred/planka
1
0
Fork 0
mirror of https://github.com/plankanban/planka.git synced 2026-02-24 19:08:59 +03:00
Code Issues 396 Packages Projects Releases 16 Wiki Activity

Error in pi_planka_1 and therefore unusable #130

New Issue
Closed
opened 2026-02-04 17:22:52 +03:00 by OVERLORD · 22 comments
OVERLORD commented 2026-02-04 17:22:52 +03:00
Owner
Copy Link

Originally created by @LorisTecnology on GitHub (Sep 4, 2021).

I can run the docker but then i got this in pi_planka_1

Error: connect ECONNREFUSED 172.19.0.2:5432

at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1138:16) {

errno: -111,

code: 'ECONNREFUSED',

syscall: 'connect',

address: '172.19.0.2',


port: 5432

}

Tried 7 times. Waiting 5 seconds...

Originally created by @LorisTecnology on GitHub (Sep 4, 2021). I can run the docker but then i got this in pi_planka_1 Error: connect ECONNREFUSED 172.19.0.2:5432 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1138:16) { errno: -111, code: 'ECONNREFUSED', syscall: 'connect', address: '172.19.0.2',  port: 5432 } Tried 7 times. Waiting 5 seconds...
OVERLORD commented 2026-02-04 17:23:11 +03:00
Author
Owner
Copy Link

@nickbe commented on GitHub (Sep 6, 2021):

Please check the other posts about docker - how to install and also the issues covered by other users responses. The docker image works, but as always docker can be tricky.

@nickbe commented on GitHub (Sep 6, 2021): Please check the other posts about docker - how to install and also the issues covered by other users responses. The docker image works, but as always docker can be tricky.
OVERLORD commented 2026-02-04 17:23:21 +03:00
Author
Owner
Copy Link

@dbrennand commented on GitHub (Oct 3, 2021):

Hi @LorisTecnology

Are you using the docker-compose file here?

It looks like Planka tried to connect to the Postgres DB 7 times but failed.

Is the postgres container running?

@dbrennand commented on GitHub (Oct 3, 2021): Hi @LorisTecnology Are you using the [docker-compose file](https://github.com/plankanban/planka/blob/master/docker-compose.yml) here? It looks like Planka tried to connect to the Postgres DB 7 times but failed. Is the postgres container running?
OVERLORD commented 2026-02-04 17:23:24 +03:00
Author
Owner
Copy Link

@LorisTecnology commented on GitHub (Oct 4, 2021):

1970-05-08 17:23:04.010 GMT [1] LOG:  starting PostgreSQL 14.0 on arm-unknown-linux-musleabihf, compiled by gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424, 32-bit


1970-05-08 17:23:04.010 GMT [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432


1970-05-08 17:23:04.010 GMT [1] LOG:  listening on IPv6 address "::", port 5432


1970-05-08 17:23:04.010 GMT [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"


1970-05-08 17:23:04.010 GMT [22] FATAL:  the database system is starting up


1970-05-08 17:23:04.010 GMT [23] FATAL:  the database system is starting up


1970-05-08 17:23:04.010 GMT [24] FATAL:  the database system is starting up


1970-05-08 17:23:04.010 GMT [1] LOG:  startup process (PID 21) was terminated by signal 11: Segmentation fault


1970-05-08 17:23:04.010 GMT [1] LOG:  aborting startup due to startup process failure


1970-05-08 17:23:04.010 GMT [1] LOG:  database system is shut down




PostgreSQL Database directory appears to contain a database; Skipping initialization




1970-05-09 11:35:20.011 GMT [1] LOG:  starting PostgreSQL 14.0 on arm-unknown-linux-musleabihf, compiled by gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424, 32-bit


1970-05-09 11:35:20.011 GMT [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432


1970-05-09 11:35:20.011 GMT [1] LOG:  listening on IPv6 address "::", port 5432


1970-05-09 11:35:20.011 GMT [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"


1970-05-09 11:35:20.011 GMT [22] FATAL:  the database system is starting up


1970-05-09 11:35:20.011 GMT [1] LOG:  startup process (PID 21) was terminated by signal 11: Segmentation fault


1970-05-09 11:35:20.011 GMT [1] LOG:  aborting startup due to startup process failure


1970-05-09 11:35:20.011 GMT [1] LOG:  database system is shut down




PostgreSQL Database directory appears to contain a database; Skipping initialization




1970-05-02 15:44:56.010 GMT [1] LOG:  starting PostgreSQL 14.0 on arm-unknown-linux-musleabihf, compiled by gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424, 32-bit


1970-05-02 15:44:56.010 GMT [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432


1970-05-02 15:44:56.010 GMT [1] LOG:  listening on IPv6 address "::", port 5432


1970-05-02 15:44:56.010 GMT [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"


1970-05-02 15:44:56.010 GMT [22] FATAL:  the database system is starting up


1970-05-02 15:44:56.010 GMT [23] FATAL:  the database system is starting up


1970-05-02 15:44:56.010 GMT [1] LOG:  startup process (PID 21) was terminated by signal 11: Segmentation fault


1970-05-02 15:44:56.010 GMT [1] LOG:  aborting startup due to startup process failure


1970-05-02 15:44:56.010 GMT [1] LOG:  database system is shut down




PostgreSQL Database directory appears to contain a database; Skipping initialization




1970-04-30 09:08:08.010 GMT [1] LOG:  starting PostgreSQL 14.0 on arm-unknown-linux-musleabihf, compiled by gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424, 32-bit


1970-04-30 09:08:08.010 GMT [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432


1970-04-30 09:08:08.010 GMT [1] LOG:  listening on IPv6 address "::", port 5432


1970-04-30 09:08:08.010 GMT [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"


1970-04-30 09:08:08.010 GMT [24] FATAL:  the database system is starting up


1970-04-30 09:08:08.010 GMT [1] LOG:  startup process (PID 23) was terminated by signal 11: Segmentation fault


1970-04-30 09:08:08.010 GMT [1] LOG:  aborting startup due to startup process failure


1970-04-30 09:08:08.010 GMT [1] LOG:  database system is shut down




PostgreSQL Database directory appears to contain a database; Skipping initialization




1970-05-05 16:34:00.010 GMT [1] LOG:  starting PostgreSQL 14.0 on arm-unknown-linux-musleabihf, compiled by gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424, 32-bit


1970-05-05 16:34:00.010 GMT [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432


1970-05-05 16:34:00.010 GMT [1] LOG:  listening on IPv6 address "::", port 5432


1970-05-05 16:34:00.010 GMT [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"


1970-05-05 16:34:00.010 GMT [22] FATAL:  the database system is starting up


1970-05-05 16:34:00.010 GMT [1] LOG:  startup process (PID 21) was terminated by signal 11: Segmentation fault


1970-05-05 16:34:00.010 GMT [1] LOG:  aborting startup due to startup process failure


1970-05-05 16:34:00.010 GMT [1] LOG:  database system is shut down




PostgreSQL Database directory appears to contain a database; Skipping initialization




1970-05-04 04:09:28.010 GMT [1] LOG:  starting PostgreSQL 14.0 on arm-unknown-linux-musleabihf, compiled by gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424, 32-bit


1970-05-04 04:09:28.010 GMT [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432


1970-05-04 04:09:28.010 GMT [1] LOG:  listening on IPv6 address "::", port 5432


1970-05-04 04:09:28.010 GMT [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"


1970-05-04 04:09:28.010 GMT [23] FATAL:  the database system is starting up


1970-05-04 04:09:28.010 GMT [24] FATAL:  the database system is starting up


1970-05-04 04:09:28.010 GMT [1] LOG:  startup process (PID 22) was terminated by signal 11: Segmentation fault


1970-05-04 04:09:28.010 GMT [1] LOG:  aborting startup due to startup process failure


1970-05-04 04:09:28.010 GMT [1] LOG:  database system is shut down




PostgreSQL Database directory appears to contain a database; Skipping initialization




1970-05-06 10:46:16.010 GMT [1] LOG:  starting PostgreSQL 14.0 on arm-unknown-linux-musleabihf, compiled by gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424, 32-bit


1970-05-06 10:46:16.010 GMT [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432


1970-05-06 10:46:16.010 GMT [1] LOG:  listening on IPv6 address "::", port 5432


1970-05-06 10:46:16.010 GMT [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"


1970-05-06 10:46:16.010 GMT [23] FATAL:  the database system is starting up


1970-05-06 10:46:16.010 GMT [1] LOG:  startup process (PID 22) was terminated by signal 11: Segmentation fault


1970-05-06 10:46:16.010 GMT [1] LOG:  aborting startup due to startup process failure


1970-05-06 10:46:16.010 GMT [1] LOG:  database system is shut down




PostgreSQL Database directory appears to contain a database; Skipping initialization




1970-05-04 22:21:44.010 GMT [1] LOG:  starting PostgreSQL 14.0 on arm-unknown-linux-musleabihf, compiled by gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424, 32-bit


1970-05-04 22:21:44.010 GMT [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432


1970-05-04 22:21:44.010 GMT [1] LOG:  listening on IPv6 address "::", port 5432


1970-05-04 22:21:44.010 GMT [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"


1970-05-04 22:21:44.010 GMT [22] FATAL:  the database system is starting up


1970-05-04 22:21:44.010 GMT [23] FATAL:  the database system is starting up


1970-05-04 22:21:44.010 GMT [24] FATAL:  the database system is starting up


1970-05-04 22:21:44.010 GMT [1] LOG:  startup process (PID 21) was terminated by signal 11: Segmentation fault


1970-05-04 22:21:44.010 GMT [1] LOG:  aborting startup due to startup process failure


1970-05-04 22:21:44.010 GMT [1] LOG:  database system is shut down




PostgreSQL Database directory appears to contain a database; Skipping initialization




1970-05-03 09:57:12.010 GMT [1] LOG:  starting PostgreSQL 14.0 on arm-unknown-linux-musleabihf, compiled by gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424, 32-bit


1970-05-03 09:57:12.010 GMT [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432


1970-05-03 09:57:12.010 GMT [1] LOG:  listening on IPv6 address "::", port 5432


1970-05-03 09:57:12.010 GMT [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"


1970-05-03 09:57:12.010 GMT [23] FATAL:  the database system is starting up

This is what i have now on the database

@LorisTecnology commented on GitHub (Oct 4, 2021): ``` 1970-05-08 17:23:04.010 GMT [1] LOG: starting PostgreSQL 14.0 on arm-unknown-linux-musleabihf, compiled by gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424, 32-bit 1970-05-08 17:23:04.010 GMT [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 1970-05-08 17:23:04.010 GMT [1] LOG: listening on IPv6 address "::", port 5432 1970-05-08 17:23:04.010 GMT [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" 1970-05-08 17:23:04.010 GMT [22] FATAL: the database system is starting up 1970-05-08 17:23:04.010 GMT [23] FATAL: the database system is starting up 1970-05-08 17:23:04.010 GMT [24] FATAL: the database system is starting up 1970-05-08 17:23:04.010 GMT [1] LOG: startup process (PID 21) was terminated by signal 11: Segmentation fault 1970-05-08 17:23:04.010 GMT [1] LOG: aborting startup due to startup process failure 1970-05-08 17:23:04.010 GMT [1] LOG: database system is shut down PostgreSQL Database directory appears to contain a database; Skipping initialization 1970-05-09 11:35:20.011 GMT [1] LOG: starting PostgreSQL 14.0 on arm-unknown-linux-musleabihf, compiled by gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424, 32-bit 1970-05-09 11:35:20.011 GMT [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 1970-05-09 11:35:20.011 GMT [1] LOG: listening on IPv6 address "::", port 5432 1970-05-09 11:35:20.011 GMT [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" 1970-05-09 11:35:20.011 GMT [22] FATAL: the database system is starting up 1970-05-09 11:35:20.011 GMT [1] LOG: startup process (PID 21) was terminated by signal 11: Segmentation fault 1970-05-09 11:35:20.011 GMT [1] LOG: aborting startup due to startup process failure 1970-05-09 11:35:20.011 GMT [1] LOG: database system is shut down PostgreSQL Database directory appears to contain a database; Skipping initialization 1970-05-02 15:44:56.010 GMT [1] LOG: starting PostgreSQL 14.0 on arm-unknown-linux-musleabihf, compiled by gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424, 32-bit 1970-05-02 15:44:56.010 GMT [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 1970-05-02 15:44:56.010 GMT [1] LOG: listening on IPv6 address "::", port 5432 1970-05-02 15:44:56.010 GMT [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" 1970-05-02 15:44:56.010 GMT [22] FATAL: the database system is starting up 1970-05-02 15:44:56.010 GMT [23] FATAL: the database system is starting up 1970-05-02 15:44:56.010 GMT [1] LOG: startup process (PID 21) was terminated by signal 11: Segmentation fault 1970-05-02 15:44:56.010 GMT [1] LOG: aborting startup due to startup process failure 1970-05-02 15:44:56.010 GMT [1] LOG: database system is shut down PostgreSQL Database directory appears to contain a database; Skipping initialization 1970-04-30 09:08:08.010 GMT [1] LOG: starting PostgreSQL 14.0 on arm-unknown-linux-musleabihf, compiled by gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424, 32-bit 1970-04-30 09:08:08.010 GMT [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 1970-04-30 09:08:08.010 GMT [1] LOG: listening on IPv6 address "::", port 5432 1970-04-30 09:08:08.010 GMT [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" 1970-04-30 09:08:08.010 GMT [24] FATAL: the database system is starting up 1970-04-30 09:08:08.010 GMT [1] LOG: startup process (PID 23) was terminated by signal 11: Segmentation fault 1970-04-30 09:08:08.010 GMT [1] LOG: aborting startup due to startup process failure 1970-04-30 09:08:08.010 GMT [1] LOG: database system is shut down PostgreSQL Database directory appears to contain a database; Skipping initialization 1970-05-05 16:34:00.010 GMT [1] LOG: starting PostgreSQL 14.0 on arm-unknown-linux-musleabihf, compiled by gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424, 32-bit 1970-05-05 16:34:00.010 GMT [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 1970-05-05 16:34:00.010 GMT [1] LOG: listening on IPv6 address "::", port 5432 1970-05-05 16:34:00.010 GMT [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" 1970-05-05 16:34:00.010 GMT [22] FATAL: the database system is starting up 1970-05-05 16:34:00.010 GMT [1] LOG: startup process (PID 21) was terminated by signal 11: Segmentation fault 1970-05-05 16:34:00.010 GMT [1] LOG: aborting startup due to startup process failure 1970-05-05 16:34:00.010 GMT [1] LOG: database system is shut down PostgreSQL Database directory appears to contain a database; Skipping initialization 1970-05-04 04:09:28.010 GMT [1] LOG: starting PostgreSQL 14.0 on arm-unknown-linux-musleabihf, compiled by gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424, 32-bit 1970-05-04 04:09:28.010 GMT [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 1970-05-04 04:09:28.010 GMT [1] LOG: listening on IPv6 address "::", port 5432 1970-05-04 04:09:28.010 GMT [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" 1970-05-04 04:09:28.010 GMT [23] FATAL: the database system is starting up 1970-05-04 04:09:28.010 GMT [24] FATAL: the database system is starting up 1970-05-04 04:09:28.010 GMT [1] LOG: startup process (PID 22) was terminated by signal 11: Segmentation fault 1970-05-04 04:09:28.010 GMT [1] LOG: aborting startup due to startup process failure 1970-05-04 04:09:28.010 GMT [1] LOG: database system is shut down PostgreSQL Database directory appears to contain a database; Skipping initialization 1970-05-06 10:46:16.010 GMT [1] LOG: starting PostgreSQL 14.0 on arm-unknown-linux-musleabihf, compiled by gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424, 32-bit 1970-05-06 10:46:16.010 GMT [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 1970-05-06 10:46:16.010 GMT [1] LOG: listening on IPv6 address "::", port 5432 1970-05-06 10:46:16.010 GMT [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" 1970-05-06 10:46:16.010 GMT [23] FATAL: the database system is starting up 1970-05-06 10:46:16.010 GMT [1] LOG: startup process (PID 22) was terminated by signal 11: Segmentation fault 1970-05-06 10:46:16.010 GMT [1] LOG: aborting startup due to startup process failure 1970-05-06 10:46:16.010 GMT [1] LOG: database system is shut down PostgreSQL Database directory appears to contain a database; Skipping initialization 1970-05-04 22:21:44.010 GMT [1] LOG: starting PostgreSQL 14.0 on arm-unknown-linux-musleabihf, compiled by gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424, 32-bit 1970-05-04 22:21:44.010 GMT [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 1970-05-04 22:21:44.010 GMT [1] LOG: listening on IPv6 address "::", port 5432 1970-05-04 22:21:44.010 GMT [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" 1970-05-04 22:21:44.010 GMT [22] FATAL: the database system is starting up 1970-05-04 22:21:44.010 GMT [23] FATAL: the database system is starting up 1970-05-04 22:21:44.010 GMT [24] FATAL: the database system is starting up 1970-05-04 22:21:44.010 GMT [1] LOG: startup process (PID 21) was terminated by signal 11: Segmentation fault 1970-05-04 22:21:44.010 GMT [1] LOG: aborting startup due to startup process failure 1970-05-04 22:21:44.010 GMT [1] LOG: database system is shut down PostgreSQL Database directory appears to contain a database; Skipping initialization 1970-05-03 09:57:12.010 GMT [1] LOG: starting PostgreSQL 14.0 on arm-unknown-linux-musleabihf, compiled by gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424, 32-bit 1970-05-03 09:57:12.010 GMT [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 1970-05-03 09:57:12.010 GMT [1] LOG: listening on IPv6 address "::", port 5432 1970-05-03 09:57:12.010 GMT [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" 1970-05-03 09:57:12.010 GMT [23] FATAL: the database system is starting up ``` This is what i have now on the database
OVERLORD commented 2026-02-04 17:23:38 +03:00
Author
Owner
Copy Link

@LorisTecnology commented on GitHub (Oct 4, 2021):

Tried 28 times. Waiting 5 seconds...


/app/node_modules/pg-protocol/dist/parser.js:278


            : new messages_1.DatabaseError(messageValue, length, name);


              ^


Tried 29 times. Waiting 5 seconds...




error: the database system is starting up


    at Parser.parseErrorMessage (/app/node_modules/pg-protocol/dist/parser.js:278:15)


    at Parser.handlePacket (/app/node_modules/pg-protocol/dist/parser.js:126:29)


    at Parser.parse (/app/node_modules/pg-protocol/dist/parser.js:39:38)


    at Socket.<anonymous> (/app/node_modules/pg-protocol/dist/index.js:10:42)


    at Socket.emit (node:events:369:20)


    at addChunk (node:internal/streams/readable:313:12)


    at readableAddChunk (node:internal/streams/readable:288:9)


    at Socket.Readable.push (node:internal/streams/readable:227:10)


    at TCP.onStreamRead (node:internal/stream_base_commons:190:23) {


  length: 104,


  severity: 'FATAL',


  code: '57P03',


  detail: undefined,


  hint: undefined,


  position: undefined,


  internalPosition: undefined,


  internalQuery: undefined,


  where: undefined,


  schema: undefined,


  table: undefined,


  column: undefined,


  dataType: undefined,


  constraint: undefined,


  file: 'postmaster.c',


  line: '2301',


  routine: 'ProcessStartupPacket'


}


/app/node_modules/pg-protocol/dist/parser.js:278


            : new messages_1.DatabaseError(messageValue, length, name);


              ^




error: the database system is starting up


    at Parser.parseErrorMessage (/app/node_modules/pg-protocol/dist/parser.js:278:15)


    at Parser.handlePacket (/app/node_modules/pg-protocol/dist/parser.js:126:29)


    at Parser.parse (/app/node_modules/pg-protocol/dist/parser.js:39:38)


    at Socket.<anonymous> (/app/node_modules/pg-protocol/dist/index.js:10:42)


    at Socket.emit (node:events:369:20)


    at addChunk (node:internal/streams/readable:313:12)


    at readableAddChunk (node:internal/streams/readable:288:9)


    at Socket.Readable.push (node:internal/streams/readable:227:10)


    at TCP.onStreamRead (node:internal/stream_base_commons:190:23) {


  length: 104,


  severity: 'FATAL',


  code: '57P03',


  detail: undefined,


  hint: undefined,


  position: undefined,


  internalPosition: undefined,


  internalQuery: undefined,


  where: undefined,


  schema: undefined,


  table: undefined,


  column: undefined,


  dataType: undefined,


  constraint: undefined,


  file: 'postmaster.c',


  line: '2301',


  routine: 'ProcessStartupPacket'


}


Tried 30 times. Waiting 5 seconds...


/app/node_modules/pg-protocol/dist/parser.js:278


            : new messages_1.DatabaseError(messageValue, length, name);


              ^




error: the database system is starting up


    at Parser.parseErrorMessage (/app/node_modules/pg-protocol/dist/parser.js:278:15)


    at Parser.handlePacket (/app/node_modules/pg-protocol/dist/parser.js:126:29)


    at Parser.parse (/app/node_modules/pg-protocol/dist/parser.js:39:38)


    at Socket.<anonymous> (/app/node_modules/pg-protocol/dist/index.js:10:42)


    at Socket.emit (node:events:369:20)


    at addChunk (node:internal/streams/readable:313:12)


    at readableAddChunk (node:internal/streams/readable:288:9)


    at Socket.Readable.push (node:internal/streams/readable:227:10)


    at TCP.onStreamRead (node:internal/stream_base_commons:190:23) {


  length: 104,


  severity: 'FATAL',


  code: '57P03',


  detail: undefined,


  hint: undefined,


  position: undefined,


  internalPosition: undefined,


  internalQuery: undefined,


  where: undefined,


  schema: undefined,


  table: undefined,


  column: undefined,


  dataType: undefined,


  constraint: undefined,


  file: 'postmaster.c',


  line: '2301',


  routine: 'ProcessStartupPacket'


}


Tried 1 times. Waiting 5 seconds...

this is what i have on the other container

@LorisTecnology commented on GitHub (Oct 4, 2021): ``` Tried 28 times. Waiting 5 seconds... /app/node_modules/pg-protocol/dist/parser.js:278 : new messages_1.DatabaseError(messageValue, length, name); ^ Tried 29 times. Waiting 5 seconds... error: the database system is starting up at Parser.parseErrorMessage (/app/node_modules/pg-protocol/dist/parser.js:278:15) at Parser.handlePacket (/app/node_modules/pg-protocol/dist/parser.js:126:29) at Parser.parse (/app/node_modules/pg-protocol/dist/parser.js:39:38) at Socket.<anonymous> (/app/node_modules/pg-protocol/dist/index.js:10:42) at Socket.emit (node:events:369:20) at addChunk (node:internal/streams/readable:313:12) at readableAddChunk (node:internal/streams/readable:288:9) at Socket.Readable.push (node:internal/streams/readable:227:10) at TCP.onStreamRead (node:internal/stream_base_commons:190:23) { length: 104, severity: 'FATAL', code: '57P03', detail: undefined, hint: undefined, position: undefined, internalPosition: undefined, internalQuery: undefined, where: undefined, schema: undefined, table: undefined, column: undefined, dataType: undefined, constraint: undefined, file: 'postmaster.c', line: '2301', routine: 'ProcessStartupPacket' } /app/node_modules/pg-protocol/dist/parser.js:278 : new messages_1.DatabaseError(messageValue, length, name); ^ error: the database system is starting up at Parser.parseErrorMessage (/app/node_modules/pg-protocol/dist/parser.js:278:15) at Parser.handlePacket (/app/node_modules/pg-protocol/dist/parser.js:126:29) at Parser.parse (/app/node_modules/pg-protocol/dist/parser.js:39:38) at Socket.<anonymous> (/app/node_modules/pg-protocol/dist/index.js:10:42) at Socket.emit (node:events:369:20) at addChunk (node:internal/streams/readable:313:12) at readableAddChunk (node:internal/streams/readable:288:9) at Socket.Readable.push (node:internal/streams/readable:227:10) at TCP.onStreamRead (node:internal/stream_base_commons:190:23) { length: 104, severity: 'FATAL', code: '57P03', detail: undefined, hint: undefined, position: undefined, internalPosition: undefined, internalQuery: undefined, where: undefined, schema: undefined, table: undefined, column: undefined, dataType: undefined, constraint: undefined, file: 'postmaster.c', line: '2301', routine: 'ProcessStartupPacket' } Tried 30 times. Waiting 5 seconds... /app/node_modules/pg-protocol/dist/parser.js:278 : new messages_1.DatabaseError(messageValue, length, name); ^ error: the database system is starting up at Parser.parseErrorMessage (/app/node_modules/pg-protocol/dist/parser.js:278:15) at Parser.handlePacket (/app/node_modules/pg-protocol/dist/parser.js:126:29) at Parser.parse (/app/node_modules/pg-protocol/dist/parser.js:39:38) at Socket.<anonymous> (/app/node_modules/pg-protocol/dist/index.js:10:42) at Socket.emit (node:events:369:20) at addChunk (node:internal/streams/readable:313:12) at readableAddChunk (node:internal/streams/readable:288:9) at Socket.Readable.push (node:internal/streams/readable:227:10) at TCP.onStreamRead (node:internal/stream_base_commons:190:23) { length: 104, severity: 'FATAL', code: '57P03', detail: undefined, hint: undefined, position: undefined, internalPosition: undefined, internalQuery: undefined, where: undefined, schema: undefined, table: undefined, column: undefined, dataType: undefined, constraint: undefined, file: 'postmaster.c', line: '2301', routine: 'ProcessStartupPacket' } Tried 1 times. Waiting 5 seconds... ``` this is what i have on the other container
OVERLORD commented 2026-02-04 17:23:44 +03:00
Author
Owner
Copy Link

@dbrennand commented on GitHub (Oct 4, 2021):

Hi @LorisTecnology

The log line here:

startup process (PID 22) was terminated by signal 11: Segmentation fault

In the Postgres SQL logs looks like the container is failing to start. Looking at this issue it looks like this could be due to a bug in the libseccomp2 library.

Please could you try option 1 from LinuxServer.io documentation and see if this fixes your issue :-)

@dbrennand commented on GitHub (Oct 4, 2021): Hi @LorisTecnology The log line here: `startup process (PID 22) was terminated by signal 11: Segmentation fault` In the Postgres SQL logs looks like the container is failing to start. Looking at [this](https://github.com/timescale/timescaledb-docker/issues/136) issue it looks like this could be due to a bug in the `libseccomp2` library. Please could you try [option 1](https://docs.linuxserver.io/faq#option-1) from LinuxServer.io documentation and see if this fixes your issue :-)
OVERLORD commented 2026-02-04 17:23:47 +03:00
Author
Owner
Copy Link

@LorisTecnology commented on GitHub (Oct 4, 2021):

thanks
but i don't really get what should i do

@LorisTecnology commented on GitHub (Oct 4, 2021): thanks but i don't really get what should i do
OVERLORD commented 2026-02-04 17:23:51 +03:00
Author
Owner
Copy Link

@LorisTecnology commented on GitHub (Oct 4, 2021):

error stil persist

@LorisTecnology commented on GitHub (Oct 4, 2021): error stil persist
OVERLORD commented 2026-02-04 17:23:52 +03:00
Author
Owner
Copy Link

@dbrennand commented on GitHub (Oct 4, 2021):

To clarify, you're trying this on a Raspberry Pi 4?

thanks but i don't really get what should i do

Run the following command:

wget http://ftp.us.debian.org/debian/pool/main/libs/libseccomp/libseccomp2_2.4.4-1~bpo10+1_armhf.deb && sudo dpkg -i libseccomp2_2.4.4-1~bpo10+1_armhf.deb

Once installed, I would reboot the Pi and try again.

You're using the docker-compose.yml file here correct?

@dbrennand commented on GitHub (Oct 4, 2021): To clarify, you're trying this on a Raspberry Pi 4? > > > thanks but i don't really get what should i do Run the following command: ` wget http://ftp.us.debian.org/debian/pool/main/libs/libseccomp/libseccomp2_2.4.4-1~bpo10+1_armhf.deb && sudo dpkg -i libseccomp2_2.4.4-1~bpo10+1_armhf.deb` Once installed, I would reboot the Pi and try again. You're using the [docker-compose.yml](https://github.com/plankanban/planka/blob/master/docker-compose.yml) file here correct?
OVERLORD commented 2026-02-04 17:23:55 +03:00
Author
Owner
Copy Link

@LorisTecnology commented on GitHub (Oct 4, 2021):

yes is a pi
yes i'm using docker compose

@LorisTecnology commented on GitHub (Oct 4, 2021): yes is a pi yes i'm using docker compose
OVERLORD commented 2026-02-04 17:24:01 +03:00
Author
Owner
Copy Link

@dbrennand commented on GitHub (Oct 4, 2021):

Hmm interesting. I actually deployed Planka myself on a Raspberry Pi 4 yesterday.

Another possible fix is to alter the postgres container image tag to 9.6.23-stretch instead of alpine.

So modify image: postgres:alpine in the docker-compose.yml file to image: postgres:9.6.23-stretch

@dbrennand commented on GitHub (Oct 4, 2021): Hmm interesting. I actually deployed Planka myself on a Raspberry Pi 4 yesterday. Another possible fix is to alter the postgres container image tag to `9.6.23-stretch` instead of `alpine`. So modify `image: postgres:alpine` in the docker-compose.yml file to `image: postgres:9.6.23-stretch`
OVERLORD commented 2026-02-04 17:24:11 +03:00
Author
Owner
Copy Link

@dbrennand commented on GitHub (Oct 4, 2021):

Did it work then? @LorisTecnology 😄

@dbrennand commented on GitHub (Oct 4, 2021): Did it work then? @LorisTecnology 😄
OVERLORD commented 2026-02-04 17:24:14 +03:00
Author
Owner
Copy Link

@LorisTecnology commented on GitHub (Oct 4, 2021):

still trying
is pulling now
i'll let you know

thanks a lot for helping

@LorisTecnology commented on GitHub (Oct 4, 2021): still trying is pulling now i'll let you know thanks a lot for helping
OVERLORD commented 2026-02-04 17:24:24 +03:00
Author
Owner
Copy Link

@LorisTecnology commented on GitHub (Oct 4, 2021):

Error: getaddrinfo ENOTFOUND postgres


    at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:69:26) {


  errno: -3008,


  code: 'ENOTFOUND',


  syscall: 'getaddrinfo',


  hostname: 'postgres'


}

got this error on planka

@LorisTecnology commented on GitHub (Oct 4, 2021): ``` Error: getaddrinfo ENOTFOUND postgres at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:69:26) { errno: -3008, code: 'ENOTFOUND', syscall: 'getaddrinfo', hostname: 'postgres' } ``` got this error on planka
OVERLORD commented 2026-02-04 17:24:31 +03:00
Author
Owner
Copy Link

@LorisTecnology commented on GitHub (Oct 4, 2021):

PostgreSQL Database directory appears to contain a database; Skipping initialization




FATAL:  "/var/lib/postgresql/data" is not a valid data directory


DETAIL:  File "/var/lib/postgresql/data/PG_VERSION" does not contain valid data.


HINT:  You might need to initdb.
@LorisTecnology commented on GitHub (Oct 4, 2021): ``` PostgreSQL Database directory appears to contain a database; Skipping initialization FATAL: "/var/lib/postgresql/data" is not a valid data directory DETAIL: File "/var/lib/postgresql/data/PG_VERSION" does not contain valid data. HINT: You might need to initdb. ```
OVERLORD commented 2026-02-04 17:24:40 +03:00
Author
Owner
Copy Link

@dbrennand commented on GitHub (Oct 4, 2021):

Hmm ok. Could you try deleting the existing volumes and starting up the containers again.

docker-compose down --volumes && docker-compose up -d

@dbrennand commented on GitHub (Oct 4, 2021): Hmm ok. Could you try deleting the existing volumes and starting up the containers again. `docker-compose down --volumes && docker-compose up -d`
OVERLORD commented 2026-02-04 17:24:50 +03:00
Author
Owner
Copy Link

@LorisTecnology commented on GitHub (Oct 4, 2021):

sure

@LorisTecnology commented on GitHub (Oct 4, 2021): sure
OVERLORD commented 2026-02-04 17:24:57 +03:00
Author
Owner
Copy Link

@LorisTecnology commented on GitHub (Oct 4, 2021):

yes
at least i have a page now

@LorisTecnology commented on GitHub (Oct 4, 2021): yes at least i have a page now
OVERLORD commented 2026-02-04 17:25:06 +03:00
Author
Owner
Copy Link

@LorisTecnology commented on GitHub (Oct 4, 2021):

now i have another issue tho

page is loading forever

image

@LorisTecnology commented on GitHub (Oct 4, 2021): now i have another issue tho page is loading forever ![image](https://user-images.githubusercontent.com/63395247/135872837-31bc038e-ec68-4344-9029-3ba5f9aaf090.png)
OVERLORD commented 2026-02-04 17:25:16 +03:00
Author
Owner
Copy Link

@dbrennand commented on GitHub (Oct 4, 2021):

Nice!

Ha, yeah this looks like https://github.com/plankanban/planka/issues/135 and https://github.com/plankanban/planka/issues/111. I actually had this issue yesterday myself.

I assume you're trying to access Planka using the IP address of your Raspberry Pi on your home network or something similar?

If so, you'll need to modify: - BASE_URL=http://localhost:3000 in the docker-compose.yml to - BASE_URL=http://external-IP-of-pi:3000

E.g: - BASE_URL=http://192.168.1.3:3000

@dbrennand commented on GitHub (Oct 4, 2021): Nice! Ha, yeah this looks like https://github.com/plankanban/planka/issues/135 and https://github.com/plankanban/planka/issues/111. I actually had this issue yesterday myself. I assume you're trying to access Planka using the IP address of your Raspberry Pi on your home network or something similar? If so, you'll need to modify: `- BASE_URL=http://localhost:3000` in the docker-compose.yml to `- BASE_URL=http://external-IP-of-pi:3000` E.g: `- BASE_URL=http://192.168.1.3:3000`
OVERLORD commented 2026-02-04 17:25:22 +03:00
Author
Owner
Copy Link

@LorisTecnology commented on GitHub (Oct 4, 2021):

so the Ip of the ip i have as static?

@LorisTecnology commented on GitHub (Oct 4, 2021): so the Ip of the ip i have as static?
OVERLORD commented 2026-02-04 17:25:29 +03:00
Author
Owner
Copy Link

@LorisTecnology commented on GitHub (Oct 4, 2021):

yes
everything works

thanks a lot

@LorisTecnology commented on GitHub (Oct 4, 2021): yes everything works thanks a lot
OVERLORD commented 2026-02-04 17:25:42 +03:00
Author
Owner
Copy Link

@dbrennand commented on GitHub (Oct 4, 2021):

Hi @LorisTecnology

Great! You're most welcome. Glad you got it all working. 👍🏻

@dbrennand commented on GitHub (Oct 4, 2021): Hi @LorisTecnology Great! You're most welcome. Glad you got it all working. 👍🏻
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
documentation
documentation
duplicate
enhancement
good first issue
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/planka#130
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?