[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Sks-devel] SKS RAM usage gone haywire
From: |
Ryan Hunt |
Subject: |
Re: [Sks-devel] SKS RAM usage gone haywire |
Date: |
Mon, 16 Feb 2009 10:48:11 -0700 |
User-agent: |
Thunderbird 2.0.0.19 (X11/20090105) |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I don't know what is wrong with my system, I rebuilt the DB from my old
dump.. brought it online and got updated from my peers... and then get
stuck in a new loop trying to get new keys.
I have disabled rcon at the moment to keep from hurting my peers.
Any ideas? I have verified all permissions, created a new database. It
got ~14k keys from my peers when I brought the new db online and all
those keys seem to be in the database.
Here are the last 10mins worth of rcon.log:
2009-02-16 10:28:35 Requesting 3 missing keys from <ADDR_INET
72.190.107.50:11371>, starting with 24930CB60AA1C6C4B1226B120EA8DE56
2009-02-16 10:28:35 3 keys received
2009-02-16 10:29:31 <recon as client> error in callback.:
Sys_error("Connection reset by peer")
2009-02-16 10:30:35 Hashes recovered from <ADDR_INET 114.31.78.196:11371>
2009-02-16 10:30:35 24930CB60AA1C6C4B1226B120EA8DE56
2009-02-16 10:30:35 38DFFFFA1F141DF06D9533038B5AEC83
2009-02-16 10:30:35 4F87D632F4FFC77E1A58593CF9D5C62D
2009-02-16 10:30:35 6B8DBCBF72AFBC8B72ABEB727E941036
2009-02-16 10:30:36 Requesting 4 missing keys from <ADDR_INET
114.31.78.196:11371>, starting with 24930CB60AA1C6C4B1226B120EA8DE56
2009-02-16 10:30:37 4 keys received
2009-02-16 10:30:37 Added 2 hash-updates. Caught up to 1234805437.493819
2009-02-16 10:31:21 Hashes recovered from <ADDR_INET 131.215.176.75:11371>
2009-02-16 10:31:21 24930CB60AA1C6C4B1226B120EA8DE56
2009-02-16 10:31:21 38DFFFFA1F141DF06D9533038B5AEC83
2009-02-16 10:31:21 4F87D632F4FFC77E1A58593CF9D5C62D
2009-02-16 10:31:31 Requesting 3 missing keys from <ADDR_INET
131.215.176.75:11371>, starting with 24930CB60AA1C6C4B1226B120EA8DE56
2009-02-16 10:31:31 3 keys received
2009-02-16 10:32:20 Hashes recovered from <ADDR_INET 84.16.235.61:11371>
2009-02-16 10:32:20 24930CB60AA1C6C4B1226B120EA8DE56
2009-02-16 10:32:20 2B3BC55DD351B9B2381355C16016BC81
2009-02-16 10:32:20 38DFFFFA1F141DF06D9533038B5AEC83
2009-02-16 10:32:20 4F87D632F4FFC77E1A58593CF9D5C62D
2009-02-16 10:32:20 6D12458590911F13DDC6DBAC60E37E1C
2009-02-16 10:32:20 AD6C2B2CE9D7AAC71F1EC5C671D260BC
2009-02-16 10:32:22 Requesting 6 missing keys from <ADDR_INET
84.16.235.61:11371>, starting with 24930CB60AA1C6C4B1226B120EA8DE56
2009-02-16 10:32:23 6 keys received
2009-02-16 10:32:23 Added 3 hash-updates. Caught up to 1234805543.172267
2009-02-16 10:33:16 Hashes recovered from <ADDR_INET 195.111.98.30:11371>
2009-02-16 10:33:16 24930CB60AA1C6C4B1226B120EA8DE56
2009-02-16 10:33:16 38DFFFFA1F141DF06D9533038B5AEC83
2009-02-16 10:33:16 4F87D632F4FFC77E1A58593CF9D5C62D
2009-02-16 10:33:26 Requesting 3 missing keys from <ADDR_INET
195.111.98.30:11371>, starting with 24930CB60AA1C6C4B1226B120EA8DE56
2009-02-16 10:33:26 3 keys received
2009-02-16 10:34:15 Hashes recovered from <ADDR_INET 195.111.98.30:11371>
2009-02-16 10:34:15 24930CB60AA1C6C4B1226B120EA8DE56
2009-02-16 10:34:15 38DFFFFA1F141DF06D9533038B5AEC83
2009-02-16 10:34:15 4F87D632F4FFC77E1A58593CF9D5C62D
2009-02-16 10:34:25 Requesting 3 missing keys from <ADDR_INET
195.111.98.30:11371>, starting with 24930CB60AA1C6C4B1226B120EA8DE56
2009-02-16 10:34:26 3 keys received
2009-02-16 10:35:21 Hashes recovered from <ADDR_INET 72.190.107.50:11371>
2009-02-16 10:35:21 24930CB60AA1C6C4B1226B120EA8DE56
2009-02-16 10:35:21 38DFFFFA1F141DF06D9533038B5AEC83
2009-02-16 10:35:21 4F87D632F4FFC77E1A58593CF9D5C62D
2009-02-16 10:35:21 Requesting 3 missing keys from <ADDR_INET
72.190.107.50:11371>, starting with 24930CB60AA1C6C4B1226B120EA8DE56
2009-02-16 10:35:21 3 keys received
2009-02-16 10:36:20 Hashes recovered from <ADDR_INET 195.111.98.30:11371>
2009-02-16 10:36:20 24930CB60AA1C6C4B1226B120EA8DE56
2009-02-16 10:36:20 38DFFFFA1F141DF06D9533038B5AEC83
2009-02-16 10:36:20 4F87D632F4FFC77E1A58593CF9D5C62D
2009-02-16 10:36:20 944A73D73698FFBFBA74B159838DC9B3
2009-02-16 10:36:21 Requesting 4 missing keys from <ADDR_INET
195.111.98.30:11371>, starting with 24930CB60AA1C6C4B1226B120EA8DE56
2009-02-16 10:36:22 4 keys received
2009-02-16 10:36:22 Added 1 hash-updates. Caught up to 1234805782.306689
2009-02-16 10:37:23 <recon as client> error in callback.:
Sys_error("Connection reset by peer")
2009-02-16 10:38:25 <recon as client> error in callback.: Unix error:
Connection refused - connect()
2009-02-16 10:39:23 <recon as client> error in callback.:
Sys_error("Connection reset by peer")
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkmZptUACgkQIcAiq3SnceEp4ACfXqDsiKAJNaOxCkNJQ0rrIec7
ktEAn0R0v77NoSDWfcEYOvR5qE5sM/wP
=Aw8Q
-----END PGP SIGNATURE-----
- Re: [Sks-devel] SKS RAM usage gone haywire, (continued)
- Re: [Sks-devel] SKS RAM usage gone haywire, Phil Pennock, 2009/02/14
- Re: [Sks-devel] SKS RAM usage gone haywire, Daniel Kahn Gillmor, 2009/02/14
- Re: [Sks-devel] SKS RAM usage gone haywire, Phil Pennock, 2009/02/14
- Re: [Sks-devel] SKS RAM usage gone haywire, Phil Pennock, 2009/02/14
- Re: [Sks-devel] SKS RAM usage gone haywire, Ari Trachtenberg, 2009/02/15
- Re: [Sks-devel] SKS RAM usage gone haywire, Yaron Minsky, 2009/02/15
- Re: [Sks-devel] SKS RAM usage gone haywire, Phil Pennock, 2009/02/15
- Re: [Sks-devel] SKS RAM usage gone haywire, Ryan, 2009/02/15
- Re: [Sks-devel] SKS RAM usage gone haywire, Daniel Kahn Gillmor, 2009/02/15
- Re: [Sks-devel] SKS RAM usage gone haywire, John Marshall, 2009/02/15
- Re: [Sks-devel] SKS RAM usage gone haywire,
Ryan Hunt <=
- Re: [Sks-devel] SKS RAM usage gone haywire, Phil Pennock, 2009/02/16
- Re: [Sks-devel] SKS RAM usage gone haywire, Ryan Hunt, 2009/02/16
- Re: [Sks-devel] SKS RAM usage gone haywire, Phil Pennock, 2009/02/16
- Re: [Sks-devel] SKS RAM usage gone haywire, Ari Trachtenberg, 2009/02/17
- Re: [Sks-devel] SKS RAM usage gone haywire, Azamat S. Kalimoulline, 2009/02/17
- Re: [Sks-devel] SKS RAM usage gone haywire, Azamat S. Kalimoulline, 2009/02/17
- Re: [Sks-devel] SKS RAM usage gone haywire, Alex Roper, 2009/02/17
- Re: [Sks-devel] SKS RAM usage gone haywire, Jonathan Oxer, 2009/02/17
- Re: [Sks-devel] SKS RAM usage gone haywire, John Clizbe, 2009/02/17
- Re: [Sks-devel] SKS RAM usage gone haywire, Azamat S. Kalimoulline, 2009/02/25