Fate of sks.undergrid.net

Regrettably, at this time sks.undergrid.net will be going offline indefinitely. My wife and I are in the process of selling our house in Georgia and moving to Florida. In preparation, I've been moving most of my services I need to keep available into the cloud. Unfortunately due to the usage/abuse

membership peer request.

Sending request for peering. sks.kingsview.org:11371 Antonio Airoso aair...@kingsview.org 0x002CB48FD723AE47 Antonio Airoso Senior Network Administrator/Architect Kings View Information Technology Services openpgp-digital-signature.asc Description:

Re: Debian sks.service: Main process exited, code=killed, status=11/SEGV

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

Re: Debian sks.service: Main process exited, code=killed, status=11/SEGV

В письме от среда, 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

Re: Debian sks.service: Main process exited, code=killed, status=11/SEGV

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

Debian sks.service: Main process exited, code=killed, status=11/SEGV

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?