[pgpool-general: 9146] Re: Another segmentation fault

[Tatsuo Ishii]

>> On my Linux (Ubuntu 20) there's a file which controls the core dump
>> file name.
>>
>> cat /proc/sys/kernel/core_pattern
>> |/usr/share/apport/apport -p%p -s%s -c%c -d%d -P%P -u%u -g%g -- %E
>>
>> Is it possible for you to include pid in core file name?
>>
> 
> I think it already does. Almalinux uses systemd-coredump for this, and from
> what I can find, the number before the timestamp is the PID.

Which part of the file name is the timestamp?

core.pgpool.208.d678e2ac33af434981c93683b6c42020.102976.1718650919000000

> However, this
> is the PID as seen by the kernel, not the PID as seen by the process
> itself, as pgpool runs inside a docker container. This is why the main
> pgpool process always reports PID 1 for us.

Correct.

> I don't think there is a way to
> get the PID from inside the container in the name of the dump. If we get
> another crash with multiple segmentation faults, I'll use the timestamps to
> get the first, so you can be pretty sure which PID it was the coredump
> belongs to.

What about adding a global variable to pgpool which holds the PID of
the pgpool child process?

> BTW, I have pushed fix_segfault2.patch and fix_main_node_id.patch.
>>
> 
> Great to hear! I'm glad to be of help in fixing these issues. Thank you for
> the great support!

My pleasure. Your reports are excellent!

Best reagards,
--
Tatsuo Ishii
SRA OSS LLC
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp