Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

PostgreSQL 14.11 is not able to identify the postmaster daemon.#1209

vigneshkumar2016 started this conversation inGeneral
Discussion options

PostgreSQL 14.11 runs out on error.
Image: Official Image
Version: 14.11
OS: Debian
OS version: bullseye
Container: yes

PostgreSQL errors out on 14.11
Segmentation fault (core dumped). this is quite strange.

PostgreSQL 14.5, 14.6, 14.0 works just fine.

Seems like the compiler is overshooting on the address space to load postgres.

any help here is much appreciated.

You must be logged in to vote

Replies: 3 comments 1 reply

Comment options

Hi@vigneshkumar2016 ,

It's possible that the issue you're encountering is related tolibseccomp.
If that's the case, you might consider updating bothlibseccomp and docker on the host that's running the containers.
( or just usepostgres:14.11-bullseye )

For detailed information, including the root cause and potential workarounds, please visit:
#1100 (comment)

You must be logged in to vote
0 replies
Comment options

libseccomp

Thanks, this works for me. However the traceback results and coredump looks similar with that of the one which is working and failing. pretty strange to debug. But clearly getting libraries are not getting loaded to the container memory.

You must be logged in to vote
0 replies
Comment options

Yeah, the seccomp blocks happen at the kernel level, so strace is one of the few tools that shows what's happening and even then it's usually an obscureEPERM in places it shouldn't be and no real indicator that it's actually seccomp blocking it. 😭

You must be logged in to vote
1 reply
@vigneshkumar2016
Comment options

Yeah seems like it has to read the XFR register call. but failing to do so.. its not able to identify what to load to kernel. either fails with Segmentation fault. possibly expecting a fix in generic.

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Category
General
Labels
None yet
3 participants
@vigneshkumar2016@tianon@ImreSamu
Converted from issue

This discussion was converted from issue #1208 on March 06, 2024 20:52.


[8]ページ先頭

©2009-2025 Movatter.jp