Re: [Sks-devel] keyserver.nausch.org died once again :( - PTree may be corrupted
Hi Kristian, clocksource tsc solved problem Christian ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] keyserver.nausch.org died once again :( - PTree may be corrupted
Hi Kristian, Am 17.03.2012 18:50, schrieb Kristian Fiskerstrand: You can change the clocksource by setting the clocksource= kernel option in your respective GRUB/LILO* setup, e.g. clocksource=tsc ** . I will give it a try: [0.180033] Switching to clocksource tsc Christian ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] keyserver.nausch.org died once again :( - PTree may be corrupted
Hi Kristian, Clock is still absolutely synchronous, but ptree error already persists. Other clocksources than kvm-clock have significant jitter. Unfortunally sks needs several peerings to get a reproduction of that problem. Christian Am 17.03.2012 18:50, schrieb Kristian Fiskerstrand: On 16.03.2012 18:34, Christian Felsing wrote: Hi, Hi Christian same problem here. ... Anyhow, I'd check /sys/devices/system/clocksource/clocksource0/ where I'd expect to see the files (i) available_clocksource, and (ii) current_clocksource. # cat /sys/devices/system/clocksource/clocksource0/available_clocksource kvm-clock tsc hpet acpi_pm # cat /sys/devices/system/clocksource/clocksource0/current_clocksource kvm-clock Obviously I'm not familiar with the nature of this system, most notably, whether this is a generic production system or an isolated system for sks that you can play around with a bit more. The latter would suggest that you could try changing the clocksource to see if that helps with the stability. You can change the clocksource by setting the clocksource= kernel option in your respective GRUB/LILO* setup, e.g. clocksource=tsc ** . * For grub it'd probably be in /boot/grub/menu.lst ** Please note that tsc in itself can be somewhat unstable e.g. if you have CPU frequency scaling or similar, but it should have a watchdog to monitor for that. I'm using it here as an example, without having any specific recommendation for your individual system. ___ 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] keyserver.nausch.org died once again :( - PTree may be corrupted
I disabled ntp on guest, so kvm-clock is the only clock source. A reference clock (DCF) and systems clock are now absolutely synchronous (1 second resolution) Let's see if problem still persists. Christian Am 17.03.2012 18:50, schrieb Kristian Fiskerstrand: kvm-clock You can change the clocksource by setting the clocksource= kernel option in your respective GRUB/LILO* setup, e.g. clocksource=tsc ** . ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] keyserver.nausch.org died once again :( - PTree may be corrupted
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 16.03.2012 18:34, Christian Felsing wrote: Hi, Hi Christian same problem here. ... Anyhow, I'd check /sys/devices/system/clocksource/clocksource0/ where I'd expect to see the files (i) available_clocksource, and (ii) current_clocksource. # cat /sys/devices/system/clocksource/clocksource0/available_clocksource kvm-clock tsc hpet acpi_pm # cat /sys/devices/system/clocksource/clocksource0/current_clocksource kvm-clock Obviously I'm not familiar with the nature of this system, most notably, whether this is a generic production system or an isolated system for sks that you can play around with a bit more. The latter would suggest that you could try changing the clocksource to see if that helps with the stability. You can change the clocksource by setting the clocksource= kernel option in your respective GRUB/LILO* setup, e.g. clocksource=tsc ** . * For grub it'd probably be in /boot/grub/menu.lst ** Please note that tsc in itself can be somewhat unstable e.g. if you have CPU frequency scaling or similar, but it should have a watchdog to monitor for that. I'm using it here as an example, without having any specific recommendation for your individual system. - -- - Kristian Fiskerstrand http://www.sumptuouscapital.com Twitter: @krifisk - Corruptissima re publica plurimæ leges The greater the degeneration of the republic, the more of its laws - This email was digitally signed using the OpenPGP standard. If you want to read more about this The book: Sending Emails - The Safe Way: An introduction to OpenPGP security is now available in both Amazon Kindle and Paperback format at http://www.amazon.com/dp/B006RSG1S4/ - Public PGP key 0xE3EDFAE3 at http://www.sumptuouscapital.com/pgp/ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPZM7MAAoJEBbgz41rC5UIFGwQAJofYGoREOhuwN7/V8GKgqVP fCuLbrWE1iJZ+1vKlbgh3qz00HgPW6J6nE2MLtYi613gZSFvrVb7QG699LTWT4kD 7TEi+kFq/ZJ97/5u4zL+ZLXV5whiEGPh9uSVJ7G4eAYNDo9GAUxgzp3RfXgB2PMT AJ4hDiB8g9nByeutPwOpQxkvO6VrAtcoPlf+Kz9Iq/oA1rPSiK95ARDSTZp8kLsM ooRYAyTwapgcB/X/n2lo6/rVvKgwX1OOtGG4BG4fIB9Nb+USaXFOg3ld5T9bhkTX PUlRCjDoJ4cD/I4QhNqZtgADX/J7Sxpk/AQOX4ls2IE7WlXTJmXZPj0DhPm/jZ5Z dUQWoGZTjqw+7CXtUfjuGmlxDRE/hl/6GnlqoIqfDIAnNO0TL0OouLjWY2KItVPV G75oF99FNpBXWBOLAIVMTDs4UX3o7DrKE14B3KLM5dAnNvuRIg/zx4vozhMmYUIc dog2Opal3SUVLVICuxAs7lTxg9CoSyaa973pZ7RgxnMxf7BSf3ykY79EXN5WUIMX fHiHDIriQrLukBl/qXJ45nrC/k7TzPzrjmOQXMBVmWMMlaZyVbT1OKpls03Ra9Ge Dy+ZllgSCDsSs3kFziGNFq27UdHqwcMcgjKyEPP5WqmVCePnYHwYdfhKu2Re3SJJ ImTK3dZYciesPGHcU80H =bQNV -END PGP SIGNATURE- ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] keyserver.nausch.org died once again :( - PTree may be corrupted
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 16.03.2012 08:57, Michael Nausch wrote: Ahoi! Hi Michael My keyserver died this morning once again, or in other better words, sks-recon daemon is dead or PTree database is corrupt. First of all, I presume you have tried just rebuilding the ptree, but this is a recurring problem ? Marco Nenciarini wrote some interesting facts in a discission here in our mailinglist (31 Jan 2011) on subject keyserver.linux.it is changing IP: http://lists.gnu.org/archive/html/sks-devel/2011-01/msg00030.html But I can't follow him, waht he has done to solve his problem. May someone tell me, how I can fix this buig/problem? Post is relatively clear on that, I guess; As workaround for a bug in xen the clocksource of the virtual machine was set to jiffies, which isn't accurate enough for sks. id est he switched the clocksource of the kernel to another one (other than jiffies[1] - and perhaps another kernel freq?) You say that the machine is based on a virtual machine, is it still running as one? It might be timing problems related to the hypervisor (wouldn't be the first time I've heard of drifts on that) Anyhow, I'd check /sys/devices/system/clocksource/clocksource0/ where I'd expect to see the files (i) available_clocksource, and (ii) current_clocksource. So if you cat current_clocksource you should see the current source. By default jiffies are used, but that can cause problems within a VM hypervisor in particular (which is why a few provide custom kernels for it). Adding more clocksources will require a bit of kernel (/module) compilations. [1] http://en.wikipedia.org/wiki/Jiffy_(time) - -- - Kristian Fiskerstrand http://www.sumptuouscapital.com Twitter: @krifisk - Corruptissima re publica plurimæ leges The greater the degeneration of the republic, the more of its laws - This email was digitally signed using the OpenPGP standard. If you want to read more about this The book: Sending Emails - The Safe Way: An introduction to OpenPGP security is now available in both Amazon Kindle and Paperback format at http://www.amazon.com/dp/B006RSG1S4/ - Public PGP key 0xE3EDFAE3 at http://www.sumptuouscapital.com/pgp/ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPYyjDAAoJEBbgz41rC5UIeDcP/0TfcG/zuuV7C6AQvXRDhgw3 d7JdT3nRaMCDbCyk3JFTw8NHMkvqmJOqVSDi9MGa3R1AfU5805obKhNgMOtneQzl rpONWns8xdz89AhmDavAlu8Dw5XOrqFrMVpy55Ac3+XyjPyxSWBlYpnOXPACxgaC ZpRwexCxU7MSIUKL4Lfyp8Fc0E0aPdCmYvo5dJJmKhyUAdjRtN1SXnUSWrz5ibtw iJkLK2vMdlTja8pkNWFm0weSYM8JJAzhLPfqgp3vA3QUgm6WRZcyW9FTHe1WQjnk 2fIAEkPZ3R1a4GeRASJmFd2KIZPgQ/1nGh3fR31HBpV75wWFPP9hkxoFm35KQ4HA RUet5B78p8rOq1ZgfGyXrKzZ2uARK7LkMqHnLNprguirvoW8bJcTNZDBEYYyxzEM YzAKtHrfYNBLcb3XU1SJU7q2rE0JwEEIRVbHA0aLJX1FyIpk1fuNyg2QNkkp7A0B xow5y/jpKuq0CdHYoUZ2Tv9bG6u+hBJmGu4sRawUdvKSRxAXnLErT/fSvQufCVmi 7JKPnNQW8D7SNFbwTvY/M68xg8opRjhpqS0dcDdrh9KKl0xGWoTROCX9TfGXlSxL dswosFPluKgc3wCG4v/zfE64SVCjg0jl7ED33qr5qciLlBKTJfvZIPyZXy22eyzE lPxmH6MJ1bk3ZYOdRu/w =xC3e -END PGP SIGNATURE- ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
