286cbf9e9...45.jpeg, 41.19 KB, 640x360, exif ggl iq id3 |
> ручное обновление по крону
66e153990...736.gif, 5664.13 KB, 600x338, exif ggl iq id3 |
> Навыки работы с системами багтренинга (Redmine)
9b9214a2e...1c.jpeg, 98.77 KB, 1000x562, exif ggl iq id3 |
# only second header will be present in response
# not really bug, just how it works
location /only-one-if {
set $true 1;
if ($true) {
add_header X-First 1;
}
if ($true) {
add_header X-Second 2;
}
return 204;
}
> not really bug
> not bug
> really
56c71a6ee...f6.jpeg, 76.59 KB, 1280x720, exif ggl iq id3 |
As this is the top post if you google for MySQL high CPU usage or load, I'll add an additional answer:
On the 1st of July 2012, a leap second was added to the current UTC-time to compensate for the slowing rotation of the earth due to the tides. When running ntp (or ntpd) this second was added to your computer's/server's clock. MySQLd does not seem to like this extra second on some OS'es, and yields a high CPU load. The quick fix is (as root):
$ /etc/init.d/ntpd stop
$ date -s "`date`"
$ /etc/init.d/ntpd start
https://stackoverflow.com/questions/1282232/mysql-high-cpu-usage