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
b
В письме от среда, 26 февраля 2020 г. 15:40:37 MSK Вы написали:
> 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
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 hitti
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?
