sks-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: seeking peers for keyserver.hyperboria.net.pl


From: Adam Wojcieszonek
Subject: Re: seeking peers for keyserver.hyperboria.net.pl
Date: Sun, 18 Oct 2020 08:42:38 +0000

Hi Dan
I observed Segmentation Fault only yesterday. This event happenings lasted 
about 8 hrs and then. I could not determine what was the cause of malfunction. 
My TEMPORARY fix was added automatic restart after failure to Systemd. Added 
commands:

Restart=on-failure
RestartSec=5sec

... but last night problem with restarting/SEGV went away spontaneously. This 
is very strange.

My OS is Debian 9. Sks installed from packages.
Today is first day when SKS looks like working stable without breaks ,errors 
and restarts. If no any troubles next 2-3 days then i'll post my configuration 
here .

br

Adam





‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
niedziela, 18 października 2020 06:26, Dan Egli <dan@newideatest.site> 
napisał(a):

> On 10/17/2020 9:00 AM, Adam Wojcieszonek wrote:
>
> > Hi Todd,
> > Last 4 days I'm reading all threads with sks tunning, suggestions /
> > troubles / errors etc.. It's really large dose of valuable informations.
> > SKS gives me different surprises every day. Final tunning its one of
> > most important thing but it's very difficult to prevent malfunctions
> > with unknown reasons. Today new one again - SKS shutting down every
> > few hours. When restarting manually, situation repeats itself after
> > few hours.
> > sks.service - SKS database service
> >    Loaded: loaded (/lib/systemd/system/sks.service; enabled; vendor
> > preset: disabled)
> >    Active: failed (Result: signal) since Sat 2020-10-17 15:55:14 CEST;
> > 22min ago
> >      Docs: man:sks(8)
> >   Process: 3474 ExecStart=/usr/sbin/sks -stdoutlog db (code=killed,
> > signal=SEGV)
> > Main PID: 3474 (code=killed, signal=SEGV)
> > Oct 17 15:55:14 Khaos systemd[1]: sks.service: Main process exited,
> > code=killed, status=11/SEGV
> > Oct 17 15:55:14 Khaos systemd[1]: sks.service: Failed with result
> > 'signal'.
> > Keeping keys on servers like sks is a very important goal for a
> > positive idea but costs much work and attention.
> > br
> > Adam
>
> Are you always getting status=11/SEGV? Because if you are you have a
> major problem with your sks binary. SEGV = Segmentation Fault, what was
> also known as an Access Violation or an Invalid Page Request in the old
> Windows 9x days. Sorry for coming in late on this one, but what OS are
> you using SKS on? And if Linux, what Distro? Custom compiled or Distro
> package?
>
>
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Dan Egli
> On my Test server





reply via email to

[Prev in Thread] Current Thread [Next in Thread]