From: Peter Seiderer via buildroot <buildroot@buildroot.org>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] postgresql issue
Date: Sun, 16 Feb 2025 15:14:08 +0100 [thread overview]
Message-ID: <20250216151408.710943bf@gmx.net> (raw)
In-Reply-To: <Z7HdD63RHkaM8X8t@waldemar-brodkorb.de>
Hello Waldemar,
On Sun, 16 Feb 2025 13:41:51 +0100, Waldemar Brodkorb <wbx@openadk.org> wrote:
> Hi,
>
> I am using Buildroot master. I try to use Postgresql Server.
> I have locales enabled and building for a raspberry pi5.
>
> wbx@neon:~/buildroot$ grep LOCALE .config
> BR2_NEEDS_HOST_UTF8_LOCALE=y
> BR2_ENABLE_LOCALE=y
> # BR2_ENABLE_LOCALE_PURGE is not set
> BR2_GENERATE_LOCALE="en_US"
> # BR2_PACKAGE_SYSTEMD_LOCALED is not set
>
> Journalctl reports:
> Oct 08 15:42:34 buildroot systemd[1]: Starting PostgreSQL database server...
> Oct 08 15:42:35 buildroot postgres[268]: The files belonging to this database system will be owned by user "postgres".
> Oct 08 15:42:35 buildroot postgres[268]: This user must also own the server process.
> Oct 08 15:42:35 buildroot postgres[268]: initdb: error: invalid locale settings; check LANG and LC_* environment variables
> Oct 08 15:42:35 buildroot postgres[261]: pg_ctl: database system initialization failed
> Oct 08 15:42:35 buildroot systemd[1]: postgresql.service: Control process exited, code=exited, status=1/FAILURE
> Oct 08 15:42:35 buildroot systemd[1]: :5:185m:5:185mpostgresql.service: Failed with result 'exit-code'.
> Oct 08 15:42:35 buildroot systemd[1]: Failed to start PostgreSQL database server.
>
> Any idea? I have set the environment variable LANG to en_US.UTF-8.
Reminds me of an aged patch set
[v1,1/3] package/glibc: install locale cmd independent of NLS (see [1])
[v1,2/3] package/postgresql: needs locale command (see [2])
[v1,3/3] package/postgresql: set locale for initdb to C (see [3])
...not sure if still appropriate...
Regards,
Peter
[1] https://patchwork.ozlabs.org/project/buildroot/patch/20200920150659.7562-1-ps.report@gmx.net/
[2] https://patchwork.ozlabs.org/project/buildroot/patch/20200920150659.7562-2-ps.report@gmx.net/
[3] https://patchwork.ozlabs.org/project/buildroot/patch/20200920150659.7562-3-ps.report@gmx.net/
>
> best regards
> Waldemar
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-02-16 14:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-16 12:41 [Buildroot] postgresql issue Waldemar Brodkorb
2025-02-16 14:14 ` Peter Seiderer via buildroot [this message]
2025-02-19 5:45 ` Waldemar Brodkorb
2025-02-19 6:36 ` Maxim Kochetkov via buildroot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250216151408.710943bf@gmx.net \
--to=buildroot@buildroot.org \
--cc=ps.report@gmx.net \
--cc=wbx@openadk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox