<div class="gmail_quote">On 1 July 2012 19:30, Robert M. Riches Jr. <span dir="ltr"><<a href="mailto:rm.riches@jacob21819.net" target="_blank">rm.riches@jacob21819.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Sun, 01 Jul 2012 11:07:54 +0200, Jan Ceuleers wrote:<br>
> Seems to be caused by the leap second insertion which happened overnight<br>
> (UTC).<br>
<br>
</div>At least on my system (backend and frontend on same system), it<br>
seemed connected to mysqld. Before I had seen any news about<br>
the leap second issue, I stopped mythbackend, but mysqld still<br>
consumed a steady 85% of a LCPU. After stopping and restarting<br>
mysqld, it immediately returned to using 85% of a LCPU. After<br>
several rounds of stopping and starting mysqld and mythbackend,<br>
a reboot made everything happy. Oh, and I didn't think to try<br>
restarting ntpd with the date set command in between.<br></blockquote><div><br>Exactly this happened to me, too. Though Firefox showed the same behavior as mysqld.<br><br>Also, while I could start mythfrontend, it responded to one key event in total over 1-2 minutes but was otherwise frozen.<br>
<br>A reboot solved the problem.<br><br>Versions:<br>distro Fedora 16<br>mysql Ver 14.14 Distrib 5.5.24, for Linux (x86_64) using readline 5.1<br>mythbackend 0.25, Library API : 0.25.20120408-1<br>kernel 3.3.5-2.fc16.x86_64 #1 SMP Tue May 8 11:24:50 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux<br>
<br>/ Niklas<br><br></div></div>