Gopher プロトコルでこのサイトにアクセスできるようにしたかったので、Wordpress の投稿内容を表示するpython で書かれたスクリプトを試してみる。gopher://odorikani.net でブラウザが対応していれば画像のようになるはず。

まず、https://github.com/LawnGnome/wp-gopher からソースを入手して展開する。場所は何処でも良いけど、とりあえず/usr/loca/src とかにする。


# pwd
/usr/local/src/wp-gopher/

# apt-get install xinetd
# apt-get install python-mysqldb

# vi /etc/xinetd.conf

service gopher
{
disable = no
id = gopher
socket_type = stream
port = 70
protocol = tcp
user = nobody
wait = no
server = /usr/local/sbin/wp-gopher.py
}

# cp wp-gopher.ini.dist /etc/wp-gopher.ini
# vi /etc/wp-gopher.ini

//適切に自分の環境に合わせて設定

# cp wp-gopher.py /usr/local/sbin/
# service xinetd stop
# service xinetd start
# tail -f /var/log/syslog

xinetd Version started with libwrap loadavg options compiled in.
Started working: 1 available service


で、ルータのport forwarding などを設定すれば動くはず。一応gopher でアクセスできるようになってるんだが、どうもpython のスクリプトが問題なのか解らないがうまく動いてない。エラーログとかapache じゃないし解らんなぁ。もしかするとUTF-8 で日本語だからかも。一応スクリプト書いた人はUTF-8 でいけるはずって書いてあるんだけど、その場合は無理かも。


I wanted the server is able to access via gopher protocol and show wordpress contents, so that I tried a script written in python. If your browser can handle gopher protocol, then you can see as the image above: gopher://odorikani.net.

First, get a source from https://github.com/LawnGnome/wp-gopher and extract it. The location can be anything, but I just put it at /usr/loca/src .


# pwd
/usr/local/src/wp-gopher/

# apt-get install xinetd
# apt-get install python-mysqldb

# vi /etc/xinetd.conf

service gopher
{
disable = no
id = gopher
socket_type = stream
port = 70
protocol = tcp
user = nobody
wait = no
server = /usr/local/sbin/wp-gopher.py
}

# cp wp-gopher.ini.dist /etc/wp-gopher.ini
# vi /etc/wp-gopher.ini

//set your environment

# cp wp-gopher.py /usr/local/sbin/
# service xinetd stop
# service xinetd start
# tail -f /var/log/syslog

xinetd Version started with libwrap loadavg options compiled in.
Started working: 1 available service


Then, check router(s) of port forwarding, and it should work. At least gopher protocol is working, but the script does not show logs somehow, though seemingly the script does not look at the database. I cannot figure out the problem because there is no clue where the logs are. The problem would be UTF-8 Japanese though the author mentioned using UTF-8, so I suppose it should work. Anyway, in that case, there is hopeless.

サーバのHDD が不良セクタ吐いているのでWD20EARX を新しく購入。2TB のもの。mycom.nl で108Euro だった。日本円だと12000円くらいか、現在同じモデルをkakaku.com で調べると9000円くらいなので、3000円ほど高いが仕方ない。

どうもWD20EARX は余り評判が良くないようだ。突然死が少ないながらもあるらしい。



I bought a new HDD, WD20EARX, 2TB SATA because one of the server’s HDD has kept having bad sectors. The cost is 108EUR at mycom.nl, means approximately 12000JPY. Now the same model can be found 9000JPY at kakaku.com, but I have no choice.

I have heard a rumor that WD20EARX would has lost its reputation because of sudden death, the case is rare though.

スクリプトによるバックアップ ( 詳しくはここ) からのリストアはとても簡単。スクリプトは2つのファイル、SQLdata.sql.bz2 とbackupOfWholeSite.tar.bz2 を生成する。Write permission や Owner などの心配など必要なく、そのまま移動させれば良いだけだ。

# bzip2 -d SQLdata.sql.bz2
# mysql -h mysqlhostserver -u mysqlusername
-p databasename < SQLdata.sql

Enter password: (enter your mysql password)

# tar jxvf backupOfWholeSite.tar.bz2
# mv backupOfWholeSite/ /yourWebbyLocation/backupOfWholeSite/



After using scripts ( article here ), restoring WordPress data is very easy. The scripts generate 2 files: SQLdata.sql.bz2 and backupOfWholeSite.tar.bz2. You do't need to worry write permission or owner, means just move the site entirely.

# bzip2 -d SQLdata.sql.bz2
# mysql -h mysqlhostserver -u mysqlusername
-p databasename < SQLdata.sql

Enter password: (enter your mysql password)

# tar jxvf backupOfWholeSite.tar.bz2
# mv backupOfWholeSite/ /yourWebbyLocation/backupOfWholeSite/