nginx coredump because of SEGV

[Lentes, Bernd]

----- On Nov 18, 2021, at 10:33 AM, clanlaw clanlaw at gmail.com wrote:

> On Thu, 18 Nov 2021 at 09:29, Lentes, Bernd
> <bernd.lentes at helmholtz-muenchen.de> wrote:
>>
>>
>>
>> ----- On Nov 17, 2021, at 9:15 PM, Bernd Lentes
>> bernd.lentes at helmholtz-muenchen.de wrote:
>>
>> > Hi,
>> >
>> > i had now twice a coredump from nginx. It happened shortly after logrotate.
> 
> Could it be this problem?
> 
> https://stackoverflow.com/questions/36325214/how-does-nginx-restart-after-being-killed-by-log-rotate
> 
> Colin L.

Hi Colin,

i don't think so.
For better understanding: 
Oct 31 00:02:06 documents-oo kernel: [1340433.341063] nginx[433202]: segfault at 10 ip 00007f6a15e08593 sp 00007ffeef04e220 error 4 in libperl.so.5.30.0[7f6a15da0000+166000]

Does that mean that libperl.so is the culprit for the segfault or does anyone else try to access memory which is intended for libperl.so.
Can the coredump provide more information ?

Bernd
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2217 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20211118/9b9d1c26/attachment.bin>