[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Sks-devel] Sks-devel Digest, Vol 184, Issue 26
From: |
Jason John Schwarz |
Subject: |
Re: [Sks-devel] Sks-devel Digest, Vol 184, Issue 26 |
Date: |
Thu, 22 Aug 2019 12:08:51 -0400 |
I am seeing the same issue on the insect.com server. Where is the stack size
setting, because I have not been able to find it for SKS?
Jason John Schwarz
> On Aug 22, 2019, at 12:00 PM, address@hidden wrote:
>
> Send Sks-devel mailing list submissions to
> address@hidden
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.nongnu.org/mailman/listinfo/sks-devel
> or, via email, send a message with subject or body 'help' to
> address@hidden
>
> You can reach the person managing the list at
> address@hidden
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Sks-devel digest..."
>
>
> Today's Topics:
>
> 1. Shutting down keyserver.zap.org.au (John Zaitseff)
> 2. Re: Shutting down keyserver.zap.org.au (Kristian Fiskerstrand)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 22 Aug 2019 05:16:05 +1000
> From: John Zaitseff <address@hidden>
> To: SKS Development and Deployment discussion <address@hidden>
> Subject: [Sks-devel] Shutting down keyserver.zap.org.au
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=us-ascii
>
> It is with feelings of sadness and regret that I will be shutting
> down keyserver.zap.org.au, effective immediately, purging all
> associated database files and logs. I will be sending out
> individual emails to my current peers as well.
>
> I have enjoyed being part of the SKS community since May 2014.
> Thank you for all your help during that time! But good things often
> come to an end... I had hoped to be "last one standing" :-) but
> that is not to be.
>
> For the record, I am not shutting my server down because something
> better has come along -- although keys.openpgp.org is a start. It's
> just that my current installation began core-dumping on a regular
> basis since last week (segfault error 6 -- write to an unmapped
> address). I've been running a cron job every fifteen minutes to
> restart the daemons, but that was only a stop-gap measure.
> Recreating the databases using a fresh key dump did not help. And
> given the current state of the SKS network, it just wasn't worth
> bothering about debugging the root cause.
>
> All the best, everyone!
>
> Yours truly,
>
> John Zaitseff
>
> --
> John Zaitseff ,--_|\ The ZAP Group
> Telephone: +61 2 9643 7737 / \ Sydney, Australia
> Email: address@hidden \_,--._* https://www.zap.org.au/
> v
>
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 22 Aug 2019 02:18:36 +0200
> From: Kristian Fiskerstrand
> <address@hidden>
> To: address@hidden, John Zaitseff <address@hidden>, SKS
> Development and Deployment discussion <address@hidden>
> Subject: Re: [Sks-devel] Shutting down keyserver.zap.org.au
> Message-ID:
> <address@hidden>
> Content-Type: text/plain; charset="utf-8"
>
> Fwiw, that error sounds like too small stack size for the process - in an
> alternative universe it would be interesting to hear your experience running
> with a higher stack limit
>
> On August 21, 2019 9:16:05 PM GMT+02:00, John Zaitseff <address@hidden> wrote:
>> It is with feelings of sadness and regret that I will be shutting
>> down keyserver.zap.org.au, effective immediately, purging all
>> associated database files and logs. I will be sending out
>> individual emails to my current peers as well.
>>
>> I have enjoyed being part of the SKS community since May 2014.
>> Thank you for all your help during that time! But good things often
>> come to an end... I had hoped to be "last one standing" :-) but
>> that is not to be.
>>
>> For the record, I am not shutting my server down because something
>> better has come along -- although keys.openpgp.org is a start. It's
>> just that my current installation began core-dumping on a regular
>> basis since last week (segfault error 6 -- write to an unmapped
>> address). I've been running a cron job every fifteen minutes to
>> restart the daemons, but that was only a stop-gap measure.
>> Recreating the databases using a fresh key dump did not help. And
>> given the current state of the SKS network, it just wasn't worth
>> bothering about debugging the root cause.
>>
>> All the best, everyone!
>>
>> Yours truly,
>>
>> John Zaitseff
>>
>> --
>> John Zaitseff ,--_|\ The ZAP Group
>> Telephone: +61 2 9643 7737 / \ Sydney, Australia
>> Email: address@hidden \_,--._* https://www.zap.org.au/
>> v
>>
>> _______________________________________________
>> Sks-devel mailing list
>> address@hidden
>> https://lists.nongnu.org/mailman/listinfo/sks-devel
>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> <https://lists.nongnu.org/archive/html/sks-devel/attachments/20190822/c41adbd6/attachment.html>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Sks-devel mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/sks-devel
>
>
> ------------------------------
>
> End of Sks-devel Digest, Vol 184, Issue 26
> ******************************************
- Re: [Sks-devel] Sks-devel Digest, Vol 184, Issue 26,
Jason John Schwarz <=