<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[High CPU usage after 1/7/2012]]></title><description><![CDATA[<p dir="auto">Hello.</p>
<p dir="auto">As you might know, on July 1th, 2012 time was changed to 1 seconds back, which affected some NTP-enabled systems.<br />
Symptoms are server lockup and high cpu usage for some processes.<br />
We've got reports about Debian6 and Ubuntu12 servers running nxagentd.</p>
<p dir="auto">Fix:<br />
<s>* Upgrade tzdata packages<br />
* Either reboot server or stop ntpd then set date manually and then restart ntp and affected applications</s></p>
<p dir="auto">UPDATE: looks like it's enough to just jump time a couple of seconds ahead using "date" command, no need to restart anything. Ntpd then will resolve this jump.</p>
<p dir="auto">Also please check Marco's blog for more details.</p>
<p dir="auto">More info:<br />
<a href="http://my.opera.com/marcomarongiu/blog/2012/06/01/an-humble-attempt-to-work-around-the-leap-second" rel="nofollow ugc">http://my.opera.com/marcomarongiu/blog/2012/06/01/an-humble-attempt-to-work-around-the-leap-second</a><br />
<a href="https://lkml.org/lkml/2012/7/1/203" rel="nofollow ugc">https://lkml.org/lkml/2012/7/1/203</a></p>
]]></description><link>https://forum.netxms.org/topic/1797/high-cpu-usage-after-1-7-2012</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 11:25:19 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/1797.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 02 Jul 2012 10:19:15 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to High CPU usage after 1/7/2012 on Thu, 12 Jul 2012 14:28:00 GMT]]></title><description><![CDATA[<p dir="auto">For those affected, jumping with the date command can be accomplished with:</p>
<p dir="auto">     date; sudo date `date +"%m%d%H%M%C%y.%S"`; date;</p>
<p dir="auto">One additional note, if this is a virtualized machine make sure to check the host server it is running on as well for the issue, it was the cause for us.</p>
]]></description><link>https://forum.netxms.org/post/7874</link><guid isPermaLink="true">https://forum.netxms.org/post/7874</guid><dc:creator><![CDATA[lweidig]]></dc:creator><pubDate>Thu, 12 Jul 2012 14:28:00 GMT</pubDate></item></channel></rss>