Re: [Sks-devel] SKS RAM usage gone haywire

[Phil Pennock]

On 2009-02-14 at 15:14 -0800, Phil Pennock wrote:
> I saw recon size go to 3GB again, but the RSS was only 11MB, so not so

1.6GB used for recon, switch MRTG graphs show no increased traffic.

Got to love those clean shutdown semantics which mean that the process
has to page in so that it can quit cleanly.  (Had SIGSTOP'd it for
investigation, letting it page partly out).

Since I had rotated the logs, it's interesting to see this:

2009-02-14 23:12:21 Opening log
2009-02-14 23:12:21 sks_recon, SKS version 1.1.0
2009-02-14 23:12:21 Copyright Yaron Minsky 2002-2003
2009-02-14 23:12:21 Licensed under GPL.  See COPYING file for details
2009-02-14 23:12:21 Opening PTree database
2009-02-14 23:12:21 Setting up PTree data structure
2009-02-14 23:12:21 PTree setup complete
2009-02-14 23:12:52 Malformed entry 
2009-02-14 23:12:52 Malformed entry 
2009-02-14 23:12:52 Malformed entry 
2009-02-14 23:12:52 Malformed entry 
2009-02-14 23:12:52 Malformed entry 

but not spectacularly useful.

I see missing keys fetched, hashes successfully recovered; I see
timeouts connecting to remote hosts and connection refused -- I wonder
how many of the former are the remote side thrashing memory so that
userland is unresponsive?

I see also quite a number of these scattered through the recon.log:
2009-02-14 23:26:00 Reconciliation failed.  Returning elements returned so far: 
End_of_file

but nothing identifying which peer it is.

What I do have is information on which peers I have successfully
received keys from, which will help eliminate some.

Hrm, I have quite a few of these:
2009-02-15 00:25:46 Requesting 19 missing keys from <ADDR_INET 
208.72.157.55:11371>, starting with 1825B0B0A4E23B7551F06DF13F72C597
2009-02-15 00:25:46 Error getting missing keys: End_of_file

and I know Ryan just rebuilt keys.nayr.net and it's the latest change to
my configs, so out it goes temporarily for purposes of debugging.

The closest I can come to a confirmation is to wait a day and see if it
goes screwy again.  :/

-Phil

pgpd3ziB93Mdv.pgp
Description: PGP signature