Re: Segmentation fault on startup

From: Helmut Bender <pgsql(at)helmut-bender(dot)de>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Segmentation fault on startup
Date: 2021-02-13 09:16:30
Message-ID: 63af4202-d0b0-bb54-32a4-ca5705620dc0@helmut-bender.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,

a little follow-up to this case...

since redis didn't work correctly, too, I looked around for a solution
for that, too.

It seems that the alpine image 3.13 for arm7 is broken at the moment...
see the answer here:
https://stackoverflow.com/questions/66091978/corrupt-date-with-redis6-alpine-on-raspi

And since I used the :10-alpine image for postgres, it apparently was
also affected by this bug.

So - not the reboot crashed postgres, but alpine.

Am 02.02.21 um 19:22 schrieb Helmut Bender:
>>> Today I had to restart the RasPi. Now the container fails to start with
>>> a segmentation violation.
>>
>> Not good --- sounds like you have data corruption.  After an OS crash
>> this is something that's quite possible if you haven't taken the time
>> to qualify the storage subsystem's honoring of fsync.
>
> Well, it was a regular reboot... don't know what happend.
>
> Thank you for your tips, it's running again. :-D
>

--
Gruß Helmut

In response to

Browse pgsql-general by date

  From Date Subject
Next Message João Gaspar 2021-02-13 10:36:52 [LDAPS] Test connection user with ldaps server
Previous Message Thomas Guyot 2021-02-13 00:58:08 Re: AW: ldap connection parameter lookup