Re: [Sks-devel] PTree corrupted
thank you Phil! -- David Horvath Sent from my mobile Phil Pennock sks-devel-p...@spodhuis.org wrote: On 2014-08-22 at 10:10 +0200, Horváth Dávid wrote: PTree often crash in my server. Log: 2014-08-18 14:27:38 Requesting 2 missing keys from ADDR_INET [80.241.60.3]:11371, starting with 1AFFB478E0DC9C6F6A3BEB58E5E6EED4 2014-08-18 14:27:38 2 keys received 2014-08-18 14:27:38 setting synctime to 1408372058.589961 2014-08-18 14:27:38 Added 3 hash-updates. Caught up to 1408372058.589961 2014-08-18 14:27:38 Enabling gossip 2014-08-18 14:27:39 Raising Sys.Break -- PTree may be corrupted: Failure(remove_from_node: attempt to delete non-existant element from prefix tree) Per http://keyserver.dacr.hu:11371/pks/lookup?op=stats you are running SKS 1.1.3. You need to be running at least 1.1.4 to have the fixes for PTree corruption. In short: you're running on a system where gettimeofday() is not returning unique values -- perhaps under a poorly tuned VM hosting environment, perhaps on an OS which just does not offer a high resolution gettimeofday() timer. This was fixed in SKS 1.1.4 by wrapping gettimeofday() to force the value to always go up. That version was released in October 2012. The current release is SKS 1.1.5. Upgrade SKS or fix your OS / VM. Upgrading SKS is going to be simpler. -Phil ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
[Sks-devel] PTree corrupted
Hi, PTree often crash in my server. Log: 2014-08-18 14:27:38 Requesting 2 missing keys from ADDR_INET [80.241.60.3]:11371, starting with 1AFFB478E0DC9C6F6A3BEB58E5E6EED4 2014-08-18 14:27:38 2 keys received 2014-08-18 14:27:38 setting synctime to 1408372058.589961 2014-08-18 14:27:38 Added 3 hash-updates. Caught up to 1408372058.589961 2014-08-18 14:27:38 Enabling gossip 2014-08-18 14:27:39 Raising Sys.Break -- PTree may be corrupted: Failure(remove_from_node: attempt to delete non-existant element from prefix tree) 2014-08-18 14:27:39 further catchup callback interrupted by break. 2014-08-18 14:27:39 DB closed I use a workaround (delete stop sks, delet PTree forled, start sks) but this is not a good solution. My disk is OK, memory healt is OK. Can you help me? Regards, David Horvath ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] PTree corrupted
Sorry, * (stop sks, delete PTree folder, start sks) :) David 2014-08-22 10:10 időpontban Horváth Dávid ezt írta: Hi, PTree often crash in my server. Log: 2014-08-18 14:27:38 Requesting 2 missing keys from ADDR_INET [80.241.60.3]:11371, starting with 1AFFB478E0DC9C6F6A3BEB58E5E6EED4 2014-08-18 14:27:38 2 keys received 2014-08-18 14:27:38 setting synctime to 1408372058.589961 2014-08-18 14:27:38 Added 3 hash-updates. Caught up to 1408372058.589961 2014-08-18 14:27:38 Enabling gossip 2014-08-18 14:27:39 Raising Sys.Break -- PTree may be corrupted: Failure(remove_from_node: attempt to delete non-existant element from prefix tree) 2014-08-18 14:27:39 further catchup callback interrupted by break. 2014-08-18 14:27:39 DB closed I use a workaround (delete stop sks, delet PTree forled, start sks) but this is not a good solution. My disk is OK, memory healt is OK. Can you help me? Regards, David Horvath ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] PTree corrupted
On 2014-08-22 at 10:10 +0200, Horváth Dávid wrote: PTree often crash in my server. Log: 2014-08-18 14:27:38 Requesting 2 missing keys from ADDR_INET [80.241.60.3]:11371, starting with 1AFFB478E0DC9C6F6A3BEB58E5E6EED4 2014-08-18 14:27:38 2 keys received 2014-08-18 14:27:38 setting synctime to 1408372058.589961 2014-08-18 14:27:38 Added 3 hash-updates. Caught up to 1408372058.589961 2014-08-18 14:27:38 Enabling gossip 2014-08-18 14:27:39 Raising Sys.Break -- PTree may be corrupted: Failure(remove_from_node: attempt to delete non-existant element from prefix tree) Per http://keyserver.dacr.hu:11371/pks/lookup?op=stats you are running SKS 1.1.3. You need to be running at least 1.1.4 to have the fixes for PTree corruption. In short: you're running on a system where gettimeofday() is not returning unique values -- perhaps under a poorly tuned VM hosting environment, perhaps on an OS which just does not offer a high resolution gettimeofday() timer. This was fixed in SKS 1.1.4 by wrapping gettimeofday() to force the value to always go up. That version was released in October 2012. The current release is SKS 1.1.5. Upgrade SKS or fix your OS / VM. Upgrading SKS is going to be simpler. -Phil ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
