[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Debian sks.service: Main process exited, code=killed, status=11/SEGV
|
From: |
Skip Carter |
|
Subject: |
Re: Debian sks.service: Main process exited, code=killed, status=11/SEGV |
|
Date: |
Wed, 26 Feb 2020 08:13:12 -0800 |
I see this during the DB build process, increase the stack limit:
ulimit -s unlimited
Crashes that wont restart after deployment seem to be DB corruptions.
Depending upon where the problem is, it might work to just remove the
PTree and just rebuild that. Otherwise you will need to do a fresh
build of both KDB and PTree
On Wed, 2020-02-26 at 13:40 +0100, Kristian Fiskerstrand wrote:
> On 26.02.2020 13:10, Azamat S. Kalimoulline wrote:
> > Hi. After recon started with peer sks crashed with message in logs
> > "sks.service: Main process exited, code=killed, status=11/SEGV". No
> > other
> > messages in logs. SKS version 1.1.6 Debian Buster. Is anyone get
> > that?
> >
> >
> >
>
> I'd guess it hitting a stack limit during merge of a large key.
>
--
Dr Everett (Skip) Carter 0xF29BF36844FB7922
address@hidden
Taygeta Scientific Inc
607 Charles Ave
Seaside CA 93955
831-641-0645 x103
signature.asc
Description: This is a digitally signed message part