| From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
|---|---|
| To: | Hugo Osvaldo Barrera <hugo(at)barrera(dot)io> |
| Cc: | <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: postgresql-server exiting abnormally after an OS upgrade |
| Date: | 2015-02-13 13:29:23 |
| Message-ID: | 54DDFC33.6090703@vmware.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 02/13/2015 12:42 AM, Hugo Osvaldo Barrera wrote:
> Here's the error which repeats ad infinitum:
>
> LOG: database system was shut down at 2015-02-12 14:41:29 GMT
> LOG: database system is ready to accept connections
> LOG: autovacuum launcher started
> LOG: server process (PID 21205) was terminated by signal 6: Abort trap
> LOG: terminating any other active server processes
> WARNING: terminating connection because of crash of another server process
> DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
> HINT: In a moment you should be able to reconnect to the database and repeat your command.
Can you get a core dump and a stack trace from it?
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hugo Osvaldo Barrera | 2015-02-13 14:03:32 | Re: server exiting abnormally after an OS upgrade |
| Previous Message | Michael Paquier | 2015-02-13 02:59:49 | Re: gettimeofday cause crash on Windows |