pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedSegmentation fault postgres 9.6
6+ messages / 5 participants
[nested] [flat]
* Segmentation fault postgres 9.6
@ 2018-09-17 12:15 Mariel Cherkassky <mariel.cherkassky@gmail.com>
2018-09-17 14:04 ` Re: Segmentation fault postgres 9.6 Tom Lane <tgl@sss.pgh.pa.us>
2018-09-17 14:04 ` Re: Segmentation fault postgres 9.6 Shreeyansh Dba <shreeyansh2014@gmail.com>
2018-09-17 21:28 ` Re: Segmentation fault postgres 9.6 066ce286@free.fr
0 siblings, 3 replies; 6+ messages in thread
From: Mariel Cherkassky @ 2018-09-17 12:15 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org
Hi,
I'm trying to insert a few values into a foreign table via sqllite_fdw and
my postgresql database crushes :
2018-09-17 12:09:54 UTC 43444 LOG: server process (PID 43831) was
terminated by signal 11: Segmentation fault
2018-09-17 12:09:54 UTC 43444 DETAIL: Failed process was running: insert
into vip_foreign values (2,2,2);
2018-09-17 12:09:54 UTC 43444 LOG: terminating any other active server
processes
2018-09-17 12:09:54 UTC 43451 WARNING: terminating connection because of
crash of another server process
2018-09-17 12:09:54 UTC 43451 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.
2018-09-17 12:09:54 UTC 43451 HINT: In a moment you should be able to
reconnect to the database and repeat your command.
2018-09-17 12:09:54 UTC 43444 LOG: archiver process (PID 43452) exited
with exit code 1
2018-09-17 12:09:54 UTC 43444 LOG: all server processes terminated;
reinitializing
2018-09-17 12:09:54 UTC 43840 LOG: database system was interrupted; last
known up at 2018-09-17 12:08:35 UTC
2018-09-17 12:09:56 UTC 43840 LOG: database system was not properly shut
down; automatic recovery in progress
2018-09-17 12:09:56 UTC 43840 LOG: redo starts at 0/6000098
2018-09-17 12:09:56 UTC 43840 LOG: invalid record length at 0/60000D0:
wanted 24, got 0
2018-09-17 12:09:56 UTC 43840 LOG: redo done at 0/6000098
2018-09-17 12:09:56 UTC 43840 LOG: checkpoint starting: end-of-recovery
immediate
2018-09-17 12:09:56 UTC 43840 LOG: checkpoint complete: wrote 0 buffers
(0.0%); 0 transaction log file(s) added, 0 removed, 0 recycled; write=0.006
s, sync=0.000 s, total=0.030 s; sync files=0, longest=0.000 s,
average=0.000 s; distance=0 kB, estimate=0 kB
2018-09-17 12:09:56 UTC 43840 LOG: MultiXact member wraparound
protections are now enabled
2018-09-17 12:09:56 UTC 43444 LOG: database system is ready to accept
connections
2018-09-17 12:09:56 UTC 43844 LOG: autovacuum launcher started
any idea how can I investigate if the problem in the wrapper or in the
database ?
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Segmentation fault postgres 9.6
2018-09-17 12:15 Segmentation fault postgres 9.6 Mariel Cherkassky <mariel.cherkassky@gmail.com>
@ 2018-09-17 14:04 ` Tom Lane <tgl@sss.pgh.pa.us>
2018-09-18 07:47 ` Re: Segmentation fault postgres 9.6 Mariel Cherkassky <mariel.cherkassky@gmail.com>
2 siblings, 1 reply; 6+ messages in thread
From: Tom Lane @ 2018-09-17 14:04 UTC (permalink / raw)
To: Mariel Cherkassky <mariel.cherkassky@gmail.com>; +Cc: pgsql-admin@lists.postgresql.org
Mariel Cherkassky <mariel.cherkassky@gmail.com> writes:
> I'm trying to insert a few values into a foreign table via sqllite_fdw and
> my postgresql database crushes :
> ...
> any idea how can I investigate if the problem in the wrapper or in the
> database ?
Get a stack trace:
https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend
If the trace shows that the failure occurred in code of the wrapper,
I'd definitely blame the wrapper. If sqllite_fdw is nowhere to be seen
anywhere in the trace, then it's more debatable.
regards, tom lane
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Segmentation fault postgres 9.6
2018-09-17 12:15 Segmentation fault postgres 9.6 Mariel Cherkassky <mariel.cherkassky@gmail.com>
2018-09-17 14:04 ` Re: Segmentation fault postgres 9.6 Tom Lane <tgl@sss.pgh.pa.us>
@ 2018-09-18 07:47 ` Mariel Cherkassky <mariel.cherkassky@gmail.com>
0 siblings, 0 replies; 6+ messages in thread
From: Mariel Cherkassky @ 2018-09-18 07:47 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-admin@lists.postgresql.org
The output of the core :
[root@node1_priviledged data]# gdb -q -c core
BFD: Warning: /data/pgsql/data/core is truncated: expected core file size
>= 3268321280, found: 100470784.
[New Thread 861]
Failed to read a valid object file image from memory.
Core was generated by `postgres: postgres db1 [local] INSERT '.
Program terminated with signal 11, Segmentation fault.
#0 0x00007fda258499df in ?? ()
Doesnt give me any details that can help me investigate further. What else
can I check ?
בתאריך יום ב׳, 17 בספט׳ 2018 ב-17:04 מאת Tom Lane <tgl@sss.pgh.pa.us
>:
> Mariel Cherkassky <mariel.cherkassky@gmail.com> writes:
> > I'm trying to insert a few values into a foreign table via sqllite_fdw
> and
> > my postgresql database crushes :
> > ...
> > any idea how can I investigate if the problem in the wrapper or in the
> > database ?
>
> Get a stack trace:
>
>
> https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend
>
> If the trace shows that the failure occurred in code of the wrapper,
> I'd definitely blame the wrapper. If sqllite_fdw is nowhere to be seen
> anywhere in the trace, then it's more debatable.
>
> regards, tom lane
>
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Segmentation fault postgres 9.6
2018-09-17 12:15 Segmentation fault postgres 9.6 Mariel Cherkassky <mariel.cherkassky@gmail.com>
@ 2018-09-17 14:04 ` Shreeyansh Dba <shreeyansh2014@gmail.com>
2018-09-17 16:15 ` Re: Segmentation fault postgres 9.6 Ron <ronljohnsonjr@gmail.com>
2 siblings, 1 reply; 6+ messages in thread
From: Shreeyansh Dba @ 2018-09-17 14:04 UTC (permalink / raw)
To: mariel.cherkassky@gmail.com; +Cc: pgsql-admin@lists.postgresql.org
Hi Mariel,
it seems kernel shared memory parameter issue which blocking or creating a
new process, which requires for data purpose.
Check your kernel shared memory parameters.
<http://www.shreeyansh.com;
On Mon, Sep 17, 2018 at 5:46 PM Mariel Cherkassky <
mariel.cherkassky@gmail.com> wrote:
> Hi,
> I'm trying to insert a few values into a foreign table via sqllite_fdw and
> my postgresql database crushes :
> 2018-09-17 12:09:54 UTC 43444 LOG: server process (PID 43831) was
> terminated by signal 11: Segmentation fault
> 2018-09-17 12:09:54 UTC 43444 DETAIL: Failed process was running:
> insert into vip_foreign values (2,2,2);
> 2018-09-17 12:09:54 UTC 43444 LOG: terminating any other active server
> processes
> 2018-09-17 12:09:54 UTC 43451 WARNING: terminating connection because
> of crash of another server process
> 2018-09-17 12:09:54 UTC 43451 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.
> 2018-09-17 12:09:54 UTC 43451 HINT: In a moment you should be able to
> reconnect to the database and repeat your command.
> 2018-09-17 12:09:54 UTC 43444 LOG: archiver process (PID 43452) exited
> with exit code 1
> 2018-09-17 12:09:54 UTC 43444 LOG: all server processes terminated;
> reinitializing
> 2018-09-17 12:09:54 UTC 43840 LOG: database system was interrupted;
> last known up at 2018-09-17 12:08:35 UTC
> 2018-09-17 12:09:56 UTC 43840 LOG: database system was not properly
> shut down; automatic recovery in progress
> 2018-09-17 12:09:56 UTC 43840 LOG: redo starts at 0/6000098
> 2018-09-17 12:09:56 UTC 43840 LOG: invalid record length at 0/60000D0:
> wanted 24, got 0
> 2018-09-17 12:09:56 UTC 43840 LOG: redo done at 0/6000098
> 2018-09-17 12:09:56 UTC 43840 LOG: checkpoint starting: end-of-recovery
> immediate
> 2018-09-17 12:09:56 UTC 43840 LOG: checkpoint complete: wrote 0 buffers
> (0.0%); 0 transaction log file(s) added, 0 removed, 0 recycled; write=0.006
> s, sync=0.000 s, total=0.030 s; sync files=0, longest=0.000 s,
> average=0.000 s; distance=0 kB, estimate=0 kB
> 2018-09-17 12:09:56 UTC 43840 LOG: MultiXact member wraparound
> protections are now enabled
> 2018-09-17 12:09:56 UTC 43444 LOG: database system is ready to accept
> connections
> 2018-09-17 12:09:56 UTC 43844 LOG: autovacuum launcher started
>
> any idea how can I investigate if the problem in the wrapper or in the
> database ?
>
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Segmentation fault postgres 9.6
2018-09-17 12:15 Segmentation fault postgres 9.6 Mariel Cherkassky <mariel.cherkassky@gmail.com>
2018-09-17 14:04 ` Re: Segmentation fault postgres 9.6 Shreeyansh Dba <shreeyansh2014@gmail.com>
@ 2018-09-17 16:15 ` Ron <ronljohnsonjr@gmail.com>
0 siblings, 0 replies; 6+ messages in thread
From: Ron @ 2018-09-17 16:15 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org
How did you determine that? (What line of the log file says it?)
On 09/17/2018 09:04 AM, Shreeyansh Dba wrote:
>
> Hi Mariel,
>
> it seems kernel shared memory parameter issue which blocking or creating a
> new process, which requires for data purpose.
>
> Check your kernel shared memory parameters.
>
> <http://www.shreeyansh.com;
> On Mon, Sep 17, 2018 at 5:46 PM Mariel Cherkassky
> <mariel.cherkassky@gmail.com <mailto:mariel.cherkassky@gmail.com>> wrote:
>
> Hi,
> I'm trying to insert a few values into a foreign table via sqllite_fdw
> and my postgresql database crushes :
> 2018-09-17 12:09:54 UTC 43444 LOG: server process (PID 43831) was
> terminated by signal 11: Segmentation fault
> 2018-09-17 12:09:54 UTC 43444 DETAIL: Failed process was running:
> insert into vip_foreign values (2,2,2);
> 2018-09-17 12:09:54 UTC 43444 LOG: terminating any other active
> server processes
> 2018-09-17 12:09:54 UTC 43451 WARNING: terminating connection
> because of crash of another server process
> 2018-09-17 12:09:54 UTC 43451 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.
> 2018-09-17 12:09:54 UTC 43451 HINT: In a moment you should be able
> to reconnect to the database and repeat your command.
> 2018-09-17 12:09:54 UTC 43444 LOG: archiver process (PID 43452)
> exited with exit code 1
> 2018-09-17 12:09:54 UTC 43444 LOG: all server processes terminated;
> reinitializing
> 2018-09-17 12:09:54 UTC 43840 LOG: database system was interrupted;
> last known up at 2018-09-17 12:08:35 UTC
> 2018-09-17 12:09:56 UTC 43840 LOG: database system was not properly
> shut down; automatic recovery in progress
> 2018-09-17 12:09:56 UTC 43840 LOG: redo starts at 0/6000098
> 2018-09-17 12:09:56 UTC 43840 LOG: invalid record length at
> 0/60000D0: wanted 24, got 0
> 2018-09-17 12:09:56 UTC 43840 LOG: redo done at 0/6000098
> 2018-09-17 12:09:56 UTC 43840 LOG: checkpoint starting:
> end-of-recovery immediate
> 2018-09-17 12:09:56 UTC 43840 LOG: checkpoint complete: wrote 0
> buffers (0.0%); 0 transaction log file(s) added, 0 removed, 0
> recycled; write=0.006 s, sync=0.000 s, total=0.030 s; sync files=0,
> longest=0.000 s, average=0.000 s; distance=0 kB, estimate=0 kB
> 2018-09-17 12:09:56 UTC 43840 LOG: MultiXact member wraparound
> protections are now enabled
> 2018-09-17 12:09:56 UTC 43444 LOG: database system is ready to
> accept connections
> 2018-09-17 12:09:56 UTC 43844 LOG: autovacuum launcher started
>
> any idea how can I investigate if the problem in the wrapper or in the
> database ?
>
--
Angular momentum makes the world go 'round.
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Segmentation fault postgres 9.6
2018-09-17 12:15 Segmentation fault postgres 9.6 Mariel Cherkassky <mariel.cherkassky@gmail.com>
@ 2018-09-17 21:28 ` 066ce286@free.fr
2 siblings, 0 replies; 6+ messages in thread
From: 066ce286@free.fr @ 2018-09-17 21:28 UTC (permalink / raw)
To: Mariel Cherkassky <mariel.cherkassky@gmail.com>; +Cc: pgsql-admin@lists.postgresql.org
I do have the same problem with a simple select max() from foreign_table where...
Syslog said the the mysql fdw lib segfaulted.
I've tried to compile the mysql_fdw sources ; but still same problem.
----- Mail original -----
De: "Mariel Cherkassky" <mariel.cherkassky@gmail.com>
À: pgsql-admin@lists.postgresql.org
Envoyé: Lundi 17 Septembre 2018 14:15:44
Objet: Segmentation fault postgres 9.6
Hi,
I'm trying to insert a few values into a foreign table via sqllite_fdw and my postgresql database crushes :
2018-09-17 12:09:54 UTC 43444 LOG: server process (PID 43831) was terminated by signal 11: Segmentation fault
2018-09-17 12:09:54 UTC 43444 DETAIL: Failed process was running: insert into vip_foreign values (2,2,2);
2018-09-17 12:09:54 UTC 43444 LOG: terminating any other active server processes
2018-09-17 12:09:54 UTC 43451 WARNING: terminating connection because of crash of another server process
2018-09-17 12:09:54 UTC 43451 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.
2018-09-17 12:09:54 UTC 43451 HINT: In a moment you should be able to reconnect to the database and repeat your command.
2018-09-17 12:09:54 UTC 43444 LOG: archiver process (PID 43452) exited with exit code 1
2018-09-17 12:09:54 UTC 43444 LOG: all server processes terminated; reinitializing
2018-09-17 12:09:54 UTC 43840 LOG: database system was interrupted; last known up at 2018-09-17 12:08:35 UTC
2018-09-17 12:09:56 UTC 43840 LOG: database system was not properly shut down; automatic recovery in progress
2018-09-17 12:09:56 UTC 43840 LOG: redo starts at 0/6000098
2018-09-17 12:09:56 UTC 43840 LOG: invalid record length at 0/60000D0: wanted 24, got 0
2018-09-17 12:09:56 UTC 43840 LOG: redo done at 0/6000098
2018-09-17 12:09:56 UTC 43840 LOG: checkpoint starting: end-of-recovery immediate
2018-09-17 12:09:56 UTC 43840 LOG: checkpoint complete: wrote 0 buffers (0.0%); 0 transaction log file(s) added, 0 removed, 0 recycled; write=0.006 s, sync=0.000 s, total=0.030 s; sync files=0, longest=0.000 s, average=0.000 s; distance=0 kB, estimate=0 kB
2018-09-17 12:09:56 UTC 43840 LOG: MultiXact member wraparound protections are now enabled
2018-09-17 12:09:56 UTC 43444 LOG: database system is ready to accept connections
2018-09-17 12:09:56 UTC 43844 LOG: autovacuum launcher started
any idea how can I investigate if the problem in the wrapper or in the database ?
^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2018-09-18 07:47 UTC | newest]
Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2018-09-17 12:15 Segmentation fault postgres 9.6 Mariel Cherkassky <mariel.cherkassky@gmail.com>
2018-09-17 14:04 ` Tom Lane <tgl@sss.pgh.pa.us>
2018-09-18 07:47 ` Mariel Cherkassky <mariel.cherkassky@gmail.com>
2018-09-17 14:04 ` Shreeyansh Dba <shreeyansh2014@gmail.com>
2018-09-17 16:15 ` Ron <ronljohnsonjr@gmail.com>
2018-09-17 21:28 ` 066ce286@free.fr
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