Re: [Sks-devel] Sks-devel Digest, Vol 184, Issue 26

2019-08-22 Thread Jason John Schwarz 
Giving unlimited a try, because the results I am seeing are all over the place.

Jason John Schwarz
Chief Technical Officer
MSC Inc

eMail: ja...@insect.com 
Phone: (910) 689.0557
  (800) 284.7872
Fax: (910) 689.0558



> On Aug 22, 2019, at 12:28 PM, Kristian Fiskerstrand 
>  wrote:
> 
> Just use unlimited to test, you can monitor actual size through proc for the 
> pid to determine a proper value, but I haven't done the exercise myself
> 
> On August 22, 2019 6:19:03 PM GMT+02:00, Jason John Schwarz 
>  wrote:
> OK, that is where I was adjusting it on my system, and ulimit -s is showing 
> the increase properly...maybe I just haven't made it large enough.
> I am up to 16384 now.  I was hesitant on going to unlimited.  Any suggestion 
> on value, or are you running it in unlimited mode?
> 
> Jason John Schwarz
> Chief Technical Officer
> MSC Inc
> 
> eMail: ja...@insect.com 
> Phone: (910) 689.0557
>   (800) 284.7872
> Fax: (910) 689.0558
> 
> 
> 
>> On Aug 22, 2019, at 12:14 PM, Kristian Fiskerstrand 
>> > > wrote:
>> 
>> On 22.08.2019 18:08, Jason John Schwarz wrote:
>>> 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?
>> 
>> Depends a bit on init system , so you'd have to check documentation for
>> your system. But traditionally you specify it on a per user basis in
>> /etc/security/limits.conf . See also man ulimit for a one-off, e.g
>> ulimit -s unlimited before starting sks.
>> 
>> -- 
>> 
>> Kristian Fiskerstrand
>> Blog: https://blog.sumptuouscapital.com 
>> Twitter: @krifisk
>> 
>> Public OpenPGP keyblock at hkp://pool.sks-keyservers.net 
>> 
>> fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
>> 
>> Corruptissima re publica plurimæ leges
>> The greater the degeneration of the republic, the more of its laws
>> 
> 
> 
> -- 
> Sent from my Android device with K-9 Mail. Please excuse my brevity.

___
Sks-devel mailing list
Sks-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/sks-devel

Re: [Sks-devel] Sks-devel Digest, Vol 184, Issue 26

2019-08-22 Thread Kristian Fiskerstrand 
Just use unlimited to test, you can monitor actual size through proc for the 
pid to determine a proper value, but I haven't done the exercise myself

On August 22, 2019 6:19:03 PM GMT+02:00, Jason John Schwarz  
wrote:
>OK, that is where I was adjusting it on my system, and ulimit -s is
>showing the increase properly...maybe I just haven't made it large
>enough.
>I am up to 16384 now.  I was hesitant on going to unlimited.  Any
>suggestion on value, or are you running it in unlimited mode?
>
>Jason John Schwarz
>Chief Technical Officer
>MSC Inc
>
>eMail: ja...@insect.com 
>Phone: (910) 689.0557
>  (800) 284.7872
>Fax: (910) 689.0558
>
>
>
>> On Aug 22, 2019, at 12:14 PM, Kristian Fiskerstrand
> wrote:
>> 
>> On 22.08.2019 18:08, Jason John Schwarz wrote:
>>> 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?
>> 
>> Depends a bit on init system , so you'd have to check documentation
>for
>> your system. But traditionally you specify it on a per user basis in
>> /etc/security/limits.conf . See also man ulimit for a one-off, e.g
>> ulimit -s unlimited before starting sks.
>> 
>> --
>> 
>> Kristian Fiskerstrand
>> Blog: https://blog.sumptuouscapital.com
>> Twitter: @krifisk
>> 
>> Public OpenPGP keyblock at hkp://pool.sks-keyservers.net
>> fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
>> 
>> Corruptissima re publica plurimæ leges
>> The greater the degeneration of the republic, the more of its laws
>> 

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.___
Sks-devel mailing list
Sks-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/sks-devel

Re: [Sks-devel] Sks-devel Digest, Vol 184, Issue 26

2019-08-22 Thread Jason John Schwarz 
OK, that is where I was adjusting it on my system, and ulimit -s is showing the 
increase properly...maybe I just haven't made it large enough.
I am up to 16384 now.  I was hesitant on going to unlimited.  Any suggestion on 
value, or are you running it in unlimited mode?

Jason John Schwarz
Chief Technical Officer
MSC Inc

eMail: ja...@insect.com 
Phone: (910) 689.0557
  (800) 284.7872
Fax: (910) 689.0558



> On Aug 22, 2019, at 12:14 PM, Kristian Fiskerstrand 
>  wrote:
> 
> On 22.08.2019 18:08, Jason John Schwarz wrote:
>> 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?
> 
> Depends a bit on init system , so you'd have to check documentation for
> your system. But traditionally you specify it on a per user basis in
> /etc/security/limits.conf . See also man ulimit for a one-off, e.g
> ulimit -s unlimited before starting sks.
> 
> --
> 
> Kristian Fiskerstrand
> Blog: https://blog.sumptuouscapital.com
> Twitter: @krifisk
> 
> Public OpenPGP keyblock at hkp://pool.sks-keyservers.net
> fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
> 
> Corruptissima re publica plurimæ leges
> The greater the degeneration of the republic, the more of its laws
> 



signature.asc
Description: Message signed with OpenPGP
___
Sks-devel mailing list
Sks-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/sks-devel

Re: [Sks-devel] Sks-devel Digest, Vol 184, Issue 26

2019-08-22 Thread Kristian Fiskerstrand 
On 22.08.2019 18:08, Jason John Schwarz wrote:
> 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?

Depends a bit on init system , so you'd have to check documentation for
your system. But traditionally you specify it on a per user basis in
/etc/security/limits.conf . See also man ulimit for a one-off, e.g
ulimit -s unlimited before starting sks.

-- 

Kristian Fiskerstrand
Blog: https://blog.sumptuouscapital.com
Twitter: @krifisk

Public OpenPGP keyblock at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3

Corruptissima re publica plurimæ leges
The greater the degeneration of the republic, the more of its laws



signature.asc
Description: OpenPGP digital signature
___
Sks-devel mailing list
Sks-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/sks-devel

Re: [Sks-devel] Sks-devel Digest, Vol 184, Issue 26

2019-08-22 Thread Jason John Schwarz 
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, sks-devel-requ...@nongnu.org wrote:
> 
> Send Sks-devel mailing list submissions to
>   sks-devel@nongnu.org
> 
> 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
>   sks-devel-requ...@nongnu.org
> 
> You can reach the person managing the list at
>   sks-devel-ow...@nongnu.org
> 
> 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 
> To: SKS Development and Deployment discussion 
> Subject: [Sks-devel] Shutting down keyserver.zap.org.au
> Message-ID: <20190821191605.ga36...@zap.org.au>
> 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: j.zaits...@zap.org.au   \_,--._*   https://www.zap.org.au/
> v
> 
> 
> 
> --
> 
> Message: 2
> Date: Thu, 22 Aug 2019 02:18:36 +0200
> From: Kristian Fiskerstrand
>   
> To: sks-devel@nongnu.org, John Zaitseff , SKS
>   Development and Deployment discussion 
> Subject: Re: [Sks-devel] Shutting down keyserver.zap.org.au
> Message-ID:
>   <6f493bd5-8f44-4b68-a199-56f1ac09f...@sumptuouscapital.com>
> 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 
>  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: j.zaits...@zap.org.au   \_,--._*   https://www.zap.org.au/
>>v
>> 
>> ___
>> Sks-devel mailing list
>> Sks-devel@nongnu.org
>> 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...
> UR