pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedDocker images from Jan 22 forward failing to start on raspberry pi 4
4+ messages / 2 participants
[nested] [flat]
* Docker images from Jan 22 forward failing to start on raspberry pi 4
@ 2021-02-08 23:53 William Hingston <will.hingston@gmail.com>
0 siblings, 1 reply; 4+ messages in thread
From: William Hingston @ 2021-02-08 23:53 UTC (permalink / raw)
To: pgsql-bugs@lists.postgresql.org
Hello,
https://hub.docker.com/r/arm32v7/postgres/tags?page=1&ordering=last_updated
The dockers images after Jan 22 fail to start on arm64 (tested on my
raspberry pi 4).
https://stackoverflow.com/questions/65877033/postgressql-terminates-with-signal-11-when-run-with-doc...
https://stackoverflow.com/questions/65938577/why-is-my-postgres-database-working-for-a-while-and-the...
db_1 | Success. You can now start the database server using:
db_1 |
db_1 | pg_ctl -D /var/lib/postgresql/data -l logfile start
db_1 |
db_1 | waiting for server to start....[36] LOG: starting PostgreSQL
13.1 on arm-unknown-linux-musleabihf, compiled by gcc (Alpine
10.2.1_pre1) 10.2.1 20201203, 32-bit
db_1 | [36] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
db_1 | ......[36] LOG: startup process (PID 37) was terminated by
signal 11: Segmentation fault
db_1 | [36] LOG: aborting startup due to startup process failure
db_1 | [36] LOG: database system is shut down
db_1 | pg_ctl: could not start server
db_1 | Examine the log output.
db_1 | stopped waiting
To replicate:
docker-compose.yml:
version: '3.8'
services:
db:
image: postgres:13.1-alpine
volumes:
- postgres_data:/var/lib/postgresql/data/
volumes:
postgres_data:
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Docker images from Jan 22 forward failing to start on raspberry pi 4
@ 2021-02-09 14:14 Dmitry Dolgov <9erthalion6@gmail.com>
parent: William Hingston <will.hingston@gmail.com>
0 siblings, 1 reply; 4+ messages in thread
From: Dmitry Dolgov @ 2021-02-09 14:14 UTC (permalink / raw)
To: William Hingston <will.hingston@gmail.com>; +Cc: pgsql-bugs@lists.postgresql.org
> On Tue, Feb 09, 2021 at 09:53:23AM +1000, William Hingston wrote:
>
> The dockers images after Jan 22 fail to start on arm64 (tested on my
> raspberry pi 4).
>
> https://stackoverflow.com/questions/65877033/postgressql-terminates-with-signal-11-when-run-with-doc...
> https://stackoverflow.com/questions/65938577/why-is-my-postgres-database-working-for-a-while-and-the...
>
> db_1 | Success. You can now start the database server using:
> db_1 |
> db_1 | pg_ctl -D /var/lib/postgresql/data -l logfile start
> db_1 |
> db_1 | waiting for server to start....[36] LOG: starting PostgreSQL
> 13.1 on arm-unknown-linux-musleabihf, compiled by gcc (Alpine
> 10.2.1_pre1) 10.2.1 20201203, 32-bit
> db_1 | [36] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
> db_1 | ......[36] LOG: startup process (PID 37) was terminated by
> signal 11: Segmentation fault
> db_1 | [36] LOG: aborting startup due to startup process failure
> db_1 | [36] LOG: database system is shut down
> db_1 | pg_ctl: could not start server
> db_1 | Examine the log output.
> db_1 | stopped waiting
Interesting. There are build farm members with arm64 architechture, and
they're not complaining as far as I see, but they're also not compiled
with musl. Can you maybe provide a core dump or at least a stack trace?
[1]: https://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Docker images from Jan 22 forward failing to start on raspberry pi 4
@ 2021-02-13 09:27 William Hingston <will.hingston@gmail.com>
parent: Dmitry Dolgov <9erthalion6@gmail.com>
0 siblings, 1 reply; 4+ messages in thread
From: William Hingston @ 2021-02-13 09:27 UTC (permalink / raw)
To: Dmitry Dolgov <9erthalion6@gmail.com>; +Cc: pgsql-bugs@lists.postgresql.org
Hello Dmitry,
I was about to follow the guide you posted but in the process of deploying
the image, I noticed that 13.2 was released 11 hours ago
<https://hub.docker.com/layers/postgres/library/postgres/13.2/images/sha256-ef7278c4fb90d44bc6495114c...;.
This release has solved the issue. Was the problem already found and fixed?
If not would it still be useful to provide a stack trace running 13.1?
Regards,
Will
On Tue, 9 Feb 2021 at 14:12, Dmitry Dolgov <9erthalion6@gmail.com> wrote:
> > On Tue, Feb 09, 2021 at 09:53:23AM +1000, William Hingston wrote:
> >
> > The dockers images after Jan 22 fail to start on arm64 (tested on my
> > raspberry pi 4).
> >
> >
> https://stackoverflow.com/questions/65877033/postgressql-terminates-with-signal-11-when-run-with-doc...
> >
> https://stackoverflow.com/questions/65938577/why-is-my-postgres-database-working-for-a-while-and-the...
> >
> > db_1 | Success. You can now start the database server using:
> > db_1 |
> > db_1 | pg_ctl -D /var/lib/postgresql/data -l logfile start
> > db_1 |
> > db_1 | waiting for server to start....[36] LOG: starting PostgreSQL
> > 13.1 on arm-unknown-linux-musleabihf, compiled by gcc (Alpine
> > 10.2.1_pre1) 10.2.1 20201203, 32-bit
> > db_1 | [36] LOG: listening on Unix socket
> "/var/run/postgresql/.s.PGSQL.5432"
> > db_1 | ......[36] LOG: startup process (PID 37) was terminated by
> > signal 11: Segmentation fault
> > db_1 | [36] LOG: aborting startup due to startup process failure
> > db_1 | [36] LOG: database system is shut down
> > db_1 | pg_ctl: could not start server
> > db_1 | Examine the log output.
> > db_1 | stopped waiting
>
> Interesting. There are build farm members with arm64 architechture, and
> they're not complaining as far as I see, but they're also not compiled
> with musl. Can you maybe provide a core dump or at least a stack trace?
>
> [1]:
> https://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD
>
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Docker images from Jan 22 forward failing to start on raspberry pi 4
@ 2021-02-13 10:26 Dmitry Dolgov <9erthalion6@gmail.com>
parent: William Hingston <will.hingston@gmail.com>
0 siblings, 0 replies; 4+ messages in thread
From: Dmitry Dolgov @ 2021-02-13 10:26 UTC (permalink / raw)
To: William Hingston <will.hingston@gmail.com>; +Cc: pgsql-bugs@lists.postgresql.org
> On Sat, Feb 13, 2021 at 09:27:58AM +0000, William Hingston wrote:
>
> I was about to follow the guide you posted but in the process of deploying
> the image, I noticed that 13.2 was released 11 hours ago
> <https://hub.docker.com/layers/postgres/library/postgres/13.2/images/sha256-ef7278c4fb90d44bc6495114c...;.
> This release has solved the issue. Was the problem already found and fixed?
> If not would it still be useful to provide a stack trace running 13.1?
There is some number of bugfixes between 13.1 and 13.2, but I don't see
any directly related to the problem you've described. If you san
reliably reproduce it on 13.1, I would still suggest to provide a stack
trace to make sure the issue was addressed.
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2021-02-13 10:26 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2021-02-08 23:53 Docker images from Jan 22 forward failing to start on raspberry pi 4 William Hingston <will.hingston@gmail.com>
2021-02-09 14:14 ` Dmitry Dolgov <9erthalion6@gmail.com>
2021-02-13 09:27 ` William Hingston <will.hingston@gmail.com>
2021-02-13 10:26 ` Dmitry Dolgov <9erthalion6@gmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox