search

plankanban / planka

The realtime kanban board for workgroups built with React and Redux.
https://planka.app
GNU Affero General Public License v3.0
7.69k stars 714 forks source link

Error in pi_planka_1 and therefore unusable #158

Open LorisTecnology opened 3 years ago

LorisTecnology commented 3 years ago

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...

nickbe commented 3 years ago

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.

dbrennand commented 2 years ago

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?

LorisTecnology commented 2 years ago 
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 2 years ago 
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

dbrennand commented 2 years ago

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 :-)

LorisTecnology commented 2 years ago

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

LorisTecnology commented 2 years ago

error stil persist

dbrennand commented 2 years ago

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?

LorisTecnology commented 2 years ago

yes is a pi yes i'm using docker compose

dbrennand commented 2 years ago

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 2 years ago

Did it work then? @LorisTecnology 😄

LorisTecnology commented 2 years ago

still trying is pulling now i'll let you know

thanks a lot for helping

LorisTecnology commented 2 years ago 
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 2 years ago 
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.
dbrennand commented 2 years ago

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

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

LorisTecnology commented 2 years ago

sure

LorisTecnology commented 2 years ago

yes at least i have a page now

LorisTecnology commented 2 years ago

now i have another issue tho

page is loading forever

image

dbrennand commented 2 years ago

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

LorisTecnology commented 2 years ago

so the Ip of the ip i have as static?

LorisTecnology commented 2 years ago

yes everything works

thanks a lot

dbrennand commented 2 years ago

Hi @LorisTecnology

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