Re: Segmentation fault on startup
От | Helmut Bender |
---|---|
Тема | Re: Segmentation fault on startup |
Дата | |
Msg-id | 63af4202-d0b0-bb54-32a4-ca5705620dc0@helmut-bender.de обсуждение исходный текст |
Ответ на | Re: Segmentation fault on startup (Helmut Bender <hab@helmut-bender.de>) |
Список | 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
В списке pgsql-general по дате отправления: