pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedcrash during autovacuum
3+ messages / 3 participants
[nested] [flat]
* crash during autovacuum
@ 2018-12-28 10:13 wambacher@posteo.de
2018-12-28 11:07 ` Re: crash during autovacuum Shreeyansh Dba <shreeyansh2014@gmail.com>
2018-12-28 15:26 ` Re: crash during autovacuum Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 2 replies; 3+ messages in thread
From: wambacher@posteo.de @ 2018-12-28 10:13 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org
Hi,
this morning my database crashed, because of a problem during autovacuum.
this is the second time during the last 2 month and i can't find out why.
logfile:
2018-12-28 10:52:22 CET [23757-59] LOG: Serverprozess (PID 14149) wurde
von Signal 6 beendet: Aborted
2018-12-28 10:52:22 CET [23757-60] DETAIL: Der fehlgeschlagene Prozess
führte aus: autovacuum: VACUUM ANALYZE public.planet_osm_ways
2018-12-28 10:52:22 CET [23757-61] LOG: aktive Serverprozesse werden
abgebrochen
2018-12-28 10:52:23 CET [26335-1] postgres@planet3 FATAL: das
Datenbanksystem ist im Wiederherstellungsmodus
2018-12-28 10:52:23 CET [23757-62] LOG: alle Serverprozesse beendet;
initialisiere neu
2018-12-28 10:52:25 CET [26402-1] postgres@planet3 FATAL: das
Datenbanksystem ist im Wiederherstellungsmodus
2018-12-28 10:52:25 CET [26401-1] LOG: Datenbanksystem wurde
unterbrochen; letzte bekannte Aktion am 2018-12-28 10:50:10 CET
that's all i get :(
it is a really big table (552.669.751 records, 228 GB data + indices)
and the last two autovacuum analyze did well. running for a really long
time (> 2 days) but without any (known) problems.
any idea what's going on and what i can do?
Regards
walter
--
My projects:
Admin Boundaries of the World <https://wambachers-osm.website/boundaries;
Missing Boundaries
<https://wambachers-osm.website/index.php/projekte/internationale-administrative-grenzen/missing-boun...;
Emergency Map <https://wambachers-osm.website/emergency;
Postal Code Map (Germany only) <https://wambachers-osm.website/plz;
Fools (QA for zipcodes in Germany) <https://wambachers-osm.website/fools;
Postcode Boundaries of Germany <https://wambachers-osm.website/pcoundaries;
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: crash during autovacuum
2018-12-28 10:13 crash during autovacuum wambacher@posteo.de
@ 2018-12-28 11:07 ` Shreeyansh Dba <shreeyansh2014@gmail.com>
1 sibling, 0 replies; 3+ messages in thread
From: Shreeyansh Dba @ 2018-12-28 11:07 UTC (permalink / raw)
To: wambacher@posteo.de; +Cc: pgsql-admin@lists.postgresql.org
Hi Walter,
It is very hard to say, but I fear that there may be a disk level issue
(corruption) and this table might be getting participating in the
autovacuum process initial for these 2 crashes.
To reconfirm maybe you can verify by taking a logical dump for this
particular table or whole database once if there any disk level or block
level corruption, and it may be causing that test to be avoided from the
fearing out during the tuning operation.
Thanks & Regards,
*Shreeyansh DBA Team*
www.shreeyansh.com
On Fri, Dec 28, 2018 at 3:43 PM <wambacher@posteo.de> wrote:
> Hi,
>
> this morning my database crashed, because of a problem during autovacuum.
>
> this is the second time during the last 2 month and i can't find out why.
>
> logfile:
>
> 2018-12-28 10:52:22 CET [23757-59] LOG: Serverprozess (PID 14149) wurde
> von Signal 6 beendet: Aborted
> 2018-12-28 10:52:22 CET [23757-60] DETAIL: Der fehlgeschlagene Prozess
> führte aus: autovacuum: VACUUM ANALYZE public.planet_osm_ways
> 2018-12-28 10:52:22 CET [23757-61] LOG: aktive Serverprozesse werden
> abgebrochen
> 2018-12-28 10:52:23 CET [26335-1] postgres@planet3 FATAL: das
> Datenbanksystem ist im Wiederherstellungsmodus
> 2018-12-28 10:52:23 CET [23757-62] LOG: alle Serverprozesse beendet;
> initialisiere neu
> 2018-12-28 10:52:25 CET [26402-1] postgres@planet3 FATAL: das
> Datenbanksystem ist im Wiederherstellungsmodus
> 2018-12-28 10:52:25 CET [26401-1] LOG: Datenbanksystem wurde
> unterbrochen; letzte bekannte Aktion am 2018-12-28 10:50:10 CET
>
> that's all i get :(
>
> it is a really big table (552.669.751 records, 228 GB data + indices) and
> the last two autovacuum analyze did well. running for a really long time (>
> 2 days) but without any (known) problems.
>
> any idea what's going on and what i can do?
>
> Regards
> walter
>
> --
> My projects:
>
> Admin Boundaries of the World <https://wambachers-osm.website/boundaries;
> Missing Boundaries
> <https://wambachers-osm.website/index.php/projekte/internationale-administrative-grenzen/missing-boun...;
> Emergency Map <https://wambachers-osm.website/emergency;
> Postal Code Map (Germany only) <https://wambachers-osm.website/plz;
> Fools (QA for zipcodes in Germany) <https://wambachers-osm.website/fools;
> Postcode Boundaries of Germany
> <https://wambachers-osm.website/pcoundaries;
>
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: crash during autovacuum
2018-12-28 10:13 crash during autovacuum wambacher@posteo.de
@ 2018-12-28 15:26 ` Tom Lane <tgl@sss.pgh.pa.us>
1 sibling, 0 replies; 3+ messages in thread
From: Tom Lane @ 2018-12-28 15:26 UTC (permalink / raw)
To: wambacher@posteo.de; +Cc: pgsql-admin@lists.postgresql.org
wambacher@posteo.de writes:
> this morning my database crashed, because of a problem during autovacuum.
> this is the second time during the last 2 month and i can't find out why.
Can you get a stack trace from the crash?
https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend
The evidence may be gone by now for your current crash, but if so, make
sure you are prepared to capture info from the next one.
The other respondent might be right that this ultimately traces to
data corruption, but it's hard to be sure without more info.
regards, tom lane
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2018-12-28 15:26 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2018-12-28 10:13 crash during autovacuum wambacher@posteo.de
2018-12-28 11:07 ` Shreeyansh Dba <shreeyansh2014@gmail.com>
2018-12-28 15:26 ` Tom Lane <tgl@sss.pgh.pa.us>
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