はじめてのにき

_ Starcraft 2 - Epic Moments Of All Time

epic

http://www.youtube.com/watch?v=NiDGTprVJu4

amazing 1, 2

http://www.youtube.com/watch?v=pXXf5kkp5F4

http://www.youtube.com/watch?v=Z-2gYARv58g

あたりを見て面白かった。

8割くらいは見たことあるからこんなのあったなーて感じだけど、でも見たことないのも結構あった。

見たことなかった huk naniwa はこれぽい。

http://www.youtube.com/watch?v=hctUYFMdv5Y

huk naniwa というと home story cup のこれもすごい感じだった…

http://www.youtube.com/watch?v=agY1d1eij_4

(09:52)

_ 謎電源断

昔もたまにあったんだけど、なんか最近謎の電源断が多いな、と思ってた。まぁなんかハードウェアの問題なのかなとか思ってたけど、見てみるとなんかヘンだ。

> ls -l /var/log/messages-*
-rw-------. 1 root root 1612674  9月 16 03:15 /var/log/messages-20120916
-rw-------. 1 root root 2484338  9月 23 03:30 /var/log/messages-20120923
-rw-------. 1 root root 1407985  9月 30 03:34 /var/log/messages-20120930
-rw-------. 1 root root 1379566 10月  7 03:17 /var/log/messages-20121007

週に一度、深夜3時から3時30分くらいに死ぬらしい。

中身を見てみると、ログの最後はだいたいこれが出る。

Oct  7 03:17:03 u6 httpd[29716]: httpd: Could not reliably determine the server's fully qualified domain name, using 192.168.11.17 for ServerName
Oct  7 03:17:03 u6 httpd[29716]: Syntax OK

これって起動時には出てないんだけど、他でもたまーに出てて、謎電源断が起きる直前に必ず起きてるっぽい。

sudo sh -c "grep 'Could not reliably' /var/log/messages-*"
/var/log/messages-20120916:Sep 13 14:44:34 u6 httpd[3054]: httpd: Could not reliably determine the server's fully qualified domain name, using 192.168.11.17 for ServerName
/var/log/messages-20120916:Sep 16 03:15:02 u6 httpd[10241]: httpd: Could not reliably determine the server's fully qualified domain name, using 192.168.11.17 for ServerName
/var/log/messages-20120923:Sep 20 02:09:53 u6 httpd[3184]: httpd: Could not reliably determine the server's fully qualified domain name, using 192.168.11.17 for ServerName
/var/log/messages-20120923:Sep 22 04:22:32 u6 httpd[1961]: httpd: Could not reliably determine the server's fully qualified domain name, using 192.168.11.17 for ServerName
/var/log/messages-20120923:Sep 23 03:30:05 u6 httpd[25342]: httpd: Could not reliably determine the server's fully qualified domain name, using 192.168.11.17 for ServerName
/var/log/messages-20120930:Sep 25 03:27:03 u6 httpd[3741]: httpd: Could not reliably determine the server's fully qualified domain name, using 192.168.11.17 for ServerName
/var/log/messages-20120930:Sep 30 03:34:03 u6 httpd[23230]: httpd: Could not reliably determine the server's fully qualified domain name, using 192.168.11.17 for ServerName
/var/log/messages-20121007:Oct  5 09:18:49 u6 httpd[2327]: httpd: Could not reliably determine the server's fully qualified domain name, using 192.168.11.17 for ServerName
/var/log/messages-20121007:Oct  7 03:17:03 u6 httpd[29716]: httpd: Could not reliably determine the server's fully qualified domain name, using 192.168.11.17 for ServerName

Apache のエラーログを見ると

sudo sh -c "grep 'SIGHUP\|Could not reliably' /var/log/httpd/error*"
/var/log/httpd/error_log-20120916:[Sun Sep 16 03:15:03 2012] [notice] SIGHUP received.  Attempting to restart
/var/log/httpd/error_log-20120916:httpd: Could not reliably determine the server's fully qualified domain name, using 192.168.11.17 for ServerName
/var/log/httpd/error_log-20120923:[Sun Sep 23 03:30:07 2012] [notice] SIGHUP received.  Attempting to restart
/var/log/httpd/error_log-20120923:httpd: Could not reliably determine the server's fully qualified domain name, using 192.168.11.17 for ServerName
/var/log/httpd/error_log-20120930:      [Tue Sep 25 03:27:04 2012] [notice] SIGHUP received.  Attempting to restart
/var/log/httpd/error_log-20120930:      httpd: Could not reliably determine theserver's fully qualified domain name, using 192.168.11.17 for ServerName
/var/log/httpd/error_log-20120930:      [Sun Sep 30 03:34:04 2012] [notice] SIGHUP received.  Attempting to restart
/var/log/httpd/error_log-20120930:      httpd: Could not reliably determine the server's fully qualified domain name, using 192.168.11.17 for ServerName
/var/log/httpd/error_log-20121007:[Sun Oct 07 03:17:03 2012] [notice] SIGHUP received.  Attempting to restart
/var/log/httpd/error_log-20121007:httpd: Could not reliably determine the server's fully qualified domain name, using 192.168.11.17 for ServerName

なにやら SIGHUP を受けたと主張している。ただ死亡直前以外で /var/log/messages に書いてあるケースの方はこっちのログには残ってなくてふしぎ (sep 25 のやつはたぶん自分で再起動した時だと思う)。実際のログは

[Fri Oct 05 09:18:49 2012] [notice] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0
[Fri Oct 05 09:18:49 2012] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Oct 05 09:18:49 2012] [notice] Digest: generating secret for digest authentication ...
[Fri Oct 05 09:18:49 2012] [notice] Digest: done
[Fri Oct 05 09:18:49 2012] [notice] mod_python: Creating 4 session mutexes based on 256 max processes and 0 max threads.
[Fri Oct 05 09:18:49 2012] [notice] mod_python: using mutex_directory /tmp
[Fri Oct 05 09:18:49 2012] [notice] Apache/2.2.21 (Unix) DAV/2 PHP/5.3.10 mod_python/3.3.1 Python/2.7.2 configured -- resuming normal operations
[Sun Oct 07 03:17:03 2012] [notice] SIGHUP received.  Attempting to restart

httpd: Could not reliably determine the server's fully qualified domain name, using 192.168.11.17 for ServerName

という感じで、 message.log に残ってる電源断と関係ないタイミングのエラーと対応する時間に SELinux の notice が出ている。他のログを見てみると、電源断のタイミングでも SELinux の notice が出てることもある。

ためしに httpd に手動で SIGHUP 撃ってみたけどマシンは死なない。つーか誰が SIGHUP 撃ってるのかなぁ、と思って、 crontab とか見てみたけどそれっぽいエントリは見つからず。 signal もそうだけど、ファイルを最後に書いたプロセスが誰かとか知りたくなること多いので、そういうの残せるモードとかあると良いよなーとか思いつつ。

あと普段から SELinux が httpd についてよく文句言ってるなよく見ると。 enforcing mode じゃないぽいから特に問題になってないみたいだけど。

とりあえずよくわからんので、例のごとくという感じだけど、 SELinux 無効化してみて様子を見てみよう。

(17:25)