https://console.aws.amazon.com/s3/buckets/<バケット名>/<prefix>?showdeleted=true
$ aws cloudwatch get-metric-statistics \ --region us-east-1 --metric-name Requests \ --namespace AWS/CloudFront \ --statistics Sum \ --dimensions Name=DistributionId,Value=xxxxxxxxxxxxxx \ Name=Region,Value=Global \ --start-time `date --iso-8601=seconds -d '3 minute ago'` \ --end-time `date --iso-8601=seconds` \ --period 60 \ --output text|sort -k3 Requests DATAPOINTS 4231.0 2016-04-15T06:54:00Z None DATAPOINTS 4389.0 2016-04-15T06:55:00Z None DATAPOINTS 1205.0 2016-04-15T06:56:00Z None $ aws cloudwatch get-metric-statistics \ --region us-east-1 --metric-name Requests \ --namespace AWS/CloudFront \ --statistics Sum \ --dimensions Name=DistributionId,Value=xxxxxxxxxxxxxx \ Name=Region,Value=Global \ --start-time `date --iso-8601=seconds -d '3 minute ago'` \ --end-time `date --iso-8601=seconds` \ --period 60 \ --output text|sort -k3 Requests DATAPOINTS 4231.0 2016-04-15T06:54:00Z None DATAPOINTS 4389.0 2016-04-15T06:55:00Z None DATAPOINTS 4380.0 2016-04-15T06:56:00Z None
[06/Apr/2016:10:39:40 +0000] "GET /test?escape HTTP/1.1" 200 95 35008269 [06/Apr/2016:10:41:00 +0000] "GET /test?timeout HTTP/1.1" 200 95 35008254 [06/Apr/2016:10:43:47 +0000] "GET /hoge HTTP/1.1" 403 213 92 [06/Apr/2016:10:43:52 +0000] "GET /piyo HTTP/1.1" 403 213 95 [06/Apr/2016:11:06:39 +0000] "GET /test?linkdown HTTP/1.1" 200 95 35009322 [06/Apr/2016:11:07:30 +0000] "GET /ok HTTP/1.1" 403 211 86
2016-04-06T10:41:00.811664Z 504 0 0 0 "GET https://xxx:443/test?timeout HTTP/1.1" 2016-04-06T10:43:47.905126Z 403 403 0 213 "GET https://xxx:443/hoge HTTP/1.1" 2016-04-06T10:43:51.996916Z 403 403 0 213 "GET https://xxx:443/piyo HTTP/1.1" 2016-04-06T11:07:30.187571Z 403 403 0 211 "GET https://xxx:443/ok HTTP/1.1"
# yum install clamav
# vi /etc/freshclam.conf Example 表記をコメントアウト
freshclam
clamscan --exclude-dir="/sys/" -r -i /
LibClamAV Warning: fmap_readpage: pread fail: asked for 4085 bytes @ offset 11, got 0
<html lang="ja"> <head>S3 File List </head> <body onload="loadXML();"> <div id="result"style="white-space:nowrap;" > </div> </body> </html>
{
"Version": "2008-10-17",
"Statement": [
{
"Sid": "AllowUser",
"Effect": "Allow",
"Principal": {
"AWS": "*"
},
"Action": [
"s3:List*",
"s3:Get*"
],
"Resource": [
"arn:aws:s3:::s3-bucket-name",
"arn:aws:s3:::s3-bucket-name/*"
],
"Condition": {
"IpAddress": {
"aws:SourceIp": ["xxx.xxx.xxx.xxx/32"]
}
}
}
]
}
autocommit=0 innodb_flush_log_at_trx_commit=0 innodb_support_xa=0 character-set-client-handshake=0 character_set_client=utf8 character_set_connection=utf8 character_set_database=utf8 character_set_filesystem=utf8 character_set_results=utf8 character_set_server=utf8・レプリケーション向けRDS Parameter Group
innodb_flush_log_at_trx_commit=0 character-set-client-handshake=0 character_set_client=utf8 character_set_connection=utf8 character_set_database=utf8 character_set_filesystem=utf8 character_set_results=utf8 character_set_server=utf8・本番運用向けRDS Parameter Group
innodb_flush_log_at_trx_commit=2 character-set-client-handshake=0 character_set_client=utf8 character_set_connection=utf8 character_set_database=utf8 character_set_filesystem=utf8 character_set_results=utf8 character_set_server=utf8
[mysqld] log-bin=mysql-bin expire_logs_days=7
mysql> grant all on *.* to replicator identified by 'password'; Query OK, 0 rows affected (0.09 sec) mysql> flush privileges; Query OK, 0 rows affected (0.04 sec)
$ (echo "SET unique_checks=0;SET foreign_key_checks=0;"; mysqldump --order-by-primary --add-drop-table --add-locks --master-data=2 --quick --all-databases -udbuser -p) | tee /mnt/storage/dump.sql | mysql -f -urdbuser -p -h xxx.yyy.ap-northeast-1.rds.amazonaws.com database_name
$ grep -m 1 MASTER_LOG /mnt/storage/dump.sql -- CHANGE MASTER TO MASTER_LOG_FILE='mysql-bin.000242', MASTER_LOG_POS=24812749;
CALL mysql.rds_set_external_master('10.xxx.xxx.xxx',3306,'replicator','password','mysql-bin.000242',24812749,0);
Query OK, 0 rows affected (0.11 sec)
CALL mysql.rds_start_replication;
+-------------------------+
| Message |
+-------------------------+
| Slave running normally. |
+-------------------------+
1 row in set (1.05 sec)
Query OK, 0 rows affected (1.05 sec)
mysql> show slave status \G Slave_IO_Running: Yes Slave_SQL_Running: Yes Seconds_Behind_Master: 11069
mysql> show processlist; | 123 | replicator | ip-10-xxx-xxx-xxx.ap-northeast-1.compute.internal:57028 | NULL | Binlog Dump | 77 | Master has sent all binlog to slave; waiting for binlog to be updated | NULLRDSから接続が来ていますね
mysql> CALL mysql.rds_skip_repl_error; +-------------------------------------+ | Message | +-------------------------------------+ | Statement in error has been skipped | +-------------------------------------+ 1 row in set (0.04 sec) +---------------------------+ | Message | +---------------------------+ | Slave is running normally | +---------------------------+ 1 row in set (2.05 sec) Query OK, 0 rows affected (2.05 sec)
Modifyして1日以上に設定
mysql> CALL mysql.rds_stop_replication; +---------------------------+ | Message | +---------------------------+ | Slave is down or disabled | +---------------------------+ 1 row in set (1.08 sec) Query OK, 0 rows affected (1.08 sec) mysql> CALL mysql.rds_reset_external_master; +----------------------+ | message | +----------------------+ | Slave has been reset | +----------------------+ 1 row in set (0.18 sec) Query OK, 0 rows affected (0.18 sec)
Concurrency Level: 10
Time taken for tests: 33.292 seconds
Complete requests: 10000
Failed requests: 0
Write errors: 0
Total transferred: 3780000 bytes
HTML transferred: 100000 bytes
Requests per second: 300.37 [#/sec] (mean)
Time per request: 33.292 [ms] (mean)
Time per request: 3.329 [ms] (mean, across all concurrent requests)
Transfer rate: 110.88 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 3 12 31.1 5 3017
Processing: 8 21 90.4 22 3024
Waiting: 8 21 90.4 22 3024
Total: 11 33 96.2 38 3044
Percentage of the requests served within a certain time (ms)
50% 38
66% 44
75% 45
80% 47
90% 49
95% 52
98% 55
99% 60
100% 3044 (longest request)
2回目Concurrency Level: 10
Time taken for tests: 19.364 seconds
Complete requests: 10000
Failed requests: 0
Write errors: 0
Total transferred: 3780000 bytes
HTML transferred: 100000 bytes
Requests per second: 516.41 [#/sec] (mean)
Time per request: 19.364 [ms] (mean)
Time per request: 1.936 [ms] (mean, across all concurrent requests)
Transfer rate: 190.63 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 3 6 3.4 9 40
Processing: 5 13 79.5 12 3012
Waiting: 5 13 79.5 12 3011
Total: 8 19 79.7 21 3021
Percentage of the requests served within a certain time (ms)
50% 21
66% 23
75% 23
80% 23
90% 24
95% 25
98% 30
99% 37
100% 3021 (longest request)
Concurrency Level: 10
Time taken for tests: 36.137 seconds
Complete requests: 10000
Failed requests: 0
Write errors: 0
Total transferred: 3560000 bytes
HTML transferred: 100000 bytes
Requests per second: 276.73 [#/sec] (mean)
Time per request: 36.137 [ms] (mean)
Time per request: 3.614 [ms] (mean, across all concurrent requests)
Transfer rate: 96.21 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 4 9 52.1 11 3009
Processing: 10 27 156.2 19 3062
Waiting: 10 27 156.2 19 3061
Total: 14 36 164.7 30 3074
Percentage of the requests served within a certain time (ms)
50% 30
66% 32
75% 33
80% 33
90% 35
95% 40
98% 58
99% 73
100% 3074 (longest request)
Concurrency Level: 10
Time taken for tests: 31.559 seconds
Complete requests: 10000
Failed requests: 0
Write errors: 0
Total transferred: 3560000 bytes
HTML transferred: 100000 bytes
Requests per second: 316.86 [#/sec] (mean)
Time per request: 31.559 [ms] (mean)
Time per request: 3.156 [ms] (mean, across all concurrent requests)
Transfer rate: 110.16 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 3 8 42.6 4 3007
Processing: 10 23 116.4 19 3021
Waiting: 10 23 116.4 19 3021
Total: 14 31 124.0 30 3033
Percentage of the requests served within a certain time (ms)
50% 30
66% 32
75% 32
80% 33
90% 34
95% 37
98% 49
99% 66
100% 3033 (longest request)
Concurrency Level: 10
Time taken for tests: 7.469 seconds
Complete requests: 10000
Failed requests: 0
Write errors: 0
Total transferred: 4161358 bytes
HTML transferred: 100000 bytes
Requests per second: 1338.85 [#/sec] (mean)
Time per request: 7.469 [ms] (mean)
Time per request: 0.747 [ms] (mean, across all concurrent requests)
Transfer rate: 544.09 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 2 3 0.5 3 12
Processing: 3 4 3.2 4 137
Waiting: 3 4 3.2 4 137
Total: 5 7 3.3 7 140
Percentage of the requests served within a certain time (ms)
50% 7
66% 8
75% 8
80% 8
90% 9
95% 10
98% 11
99% 14
100% 140 (longest request)
2回目Concurrency Level: 10
Time taken for tests: 8.182 seconds
Complete requests: 10000
Failed requests: 0
Write errors: 0
Total transferred: 4190808 bytes
HTML transferred: 100000 bytes
Requests per second: 1222.17 [#/sec] (mean)
Time per request: 8.182 [ms] (mean)
Time per request: 0.818 [ms] (mean, across all concurrent requests)
Transfer rate: 500.18 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 2 3 0.7 3 23
Processing: 3 5 2.0 5 41
Waiting: 3 5 2.0 5 41
Total: 5 8 2.2 8 44
Percentage of the requests served within a certain time (ms)
50% 8
66% 8
75% 9
80% 9
90% 10
95% 11
98% 13
99% 16
100% 44 (longest request)
Concurrency Level: 10
Time taken for tests: 7.836 seconds
Complete requests: 10000
Failed requests: 0
Write errors: 0
Total transferred: 4190014 bytes
HTML transferred: 100000 bytes
Requests per second: 1276.15 [#/sec] (mean)
Time per request: 7.836 [ms] (mean)
Time per request: 0.784 [ms] (mean, across all concurrent requests)
Transfer rate: 522.18 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 2 3 1.8 3 27
Processing: 3 5 2.5 4 39
Waiting: 3 4 2.4 4 39
Total: 5 8 3.2 7 53
Percentage of the requests served within a certain time (ms)
50% 7
66% 8
75% 8
80% 8
90% 9
95% 12
98% 20
99% 21
100% 53 (longest request)
2回目Concurrency Level: 10
Time taken for tests: 8.473 seconds
Complete requests: 10000
Failed requests: 0
Write errors: 0
Total transferred: 4191311 bytes
HTML transferred: 100000 bytes
Requests per second: 1180.20 [#/sec] (mean)
Time per request: 8.473 [ms] (mean)
Time per request: 0.847 [ms] (mean, across all concurrent requests)
Transfer rate: 483.07 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 2 3 0.6 3 17
Processing: 3 5 5.7 4 198
Waiting: 3 5 5.7 4 198
Total: 5 8 5.7 8 201
Percentage of the requests served within a certain time (ms)
50% 8
66% 8
75% 9
80% 9
90% 11
95% 13
98% 17
99% 23
100% 201 (longest request)
{
"Version": "2008-10-17",
"Id": "2c08cdf1-ddfc-4765-ac19-26b03a8e8b5e",
"Statement": [
{
"Sid": "AllowUser",
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::<12桁の数字からなるAWSのユーザID>:root"
},
"Action": "s3:*",
"Resource": [
"arn:aws:s3:::[S3 bucket name]/*",
"arn:aws:s3:::[S3 bucket name]"
]
}
]
}
今回は、コピー先のS3バケットとその中のオブジェクトに対する全権限を付与しました
gluster volume replace-brick vol1 x.x.x.x:/gfs x.x.x.x/gfs2 startで、置換開始
gluster volume replace-brick vol1 x.x.x.x:/gfs x.x.x.x/gfs2 statusで、completeになったことを確認
gluster volume replace-brick vol1 x.x.x.x:/gfs x.x.x.x/gfs2 commitで、コミット の手順でうまくいったので、実際の環境に試してみました 10GBのVolumeには1.5GBぐらいのデータが書き込まれている状態です
gluster volume replace-brick vol1 x.x.x.x:/gfs x.x.x.x/gfs2 startコマンドは通ったのですが、みるみるcpu使用率が上昇しコンソール操作もままならない程になってしまいました。 このとき利用していたインスタンスタイプはc1.mediumです。
gluster volume replace-brick vol1 x.x.x.x:/gfs x.x.x.x/gfs2 pauseこれでとりあえず負荷は下がったのですが、1GB程の一時領域に書き込みつつreplaceが行えるように待機をしている状態のようでした。
gluster volume replace-brick vol1 x.x.x.x:/gfs x.x.x.x/gfs2 abortそれはそれで、マシンリソースを喰いまくり、コマンドライン操作を受け付けないほどになってしまったのでデーモン停止(´・ω・`)
service gluster stop[失敗] だそうな。。。 なので仕方なくpkillしました
pkill glusterこのあと、安定状態に戻すまでかなりの奮闘をしたのでこの方法は避けた方が良さそうです。 次は、上手くいった方法 Volumeに容量の大きなBrick(/gfs2)を追加し、既存のBrick(/gfs)を削除するという方法
gluster volume add-brick vol1 x.x.x.x:/gfs2 y.y.y.y./gfs2すんなり追加されました つづいて、既存のBrickを削除
gluster volume remove-brick vol1 x.x.x.x:/gfs y.y.y.y./gfs startstartをつけることで、安全にBrickを削除できるように削除対象ではないところにデータを移動してくれるようです。 cpu使用率が上昇しましたが、replaceのようにコンソール操作を受け付けなくなる程ではありませんでした。
gluster volume remove-brick vol1 x.x.x.x:/gfs y.y.y.y./gfs statusで、状態を確認しながらcompleteになるまで待機 8GB程データがある状態で40分程で終了しました あとはコミットするだけ
gluster volume remove-brick vol1 x.x.x.x:/gfs y.y.y.y./gfs commitこれで無事にオンサービスのまま容量を追加することができましたよヾ(*･ω･)ｼ
yum -y erase apr yum -y install db4-devel expat-devel postgresql-devel sqlite-devel freetds-devel unixODBC-devel nss-devel mysql-devel distcache-devel libuuid-devel lksctp-tools-devel doxygen openldap-devel openssl-devel pcre-devel lua-develyumでは入らない依存モジュールのダウンロード＆ビルド＆インストール
wget http://ftp.jaist.ac.jp/pub/apache/apr/apr-1.4.6.tar.bz2 rpmbuild -tb apr-1.4.6.tar.bz2 yum install --nogpgcheck /usr/src/redhat/RPMS/x86_64/apr-* wget http://ftp.jaist.ac.jp/pub/apache/apr/apr-util-1.4.1.tar.bz2 rpmbuild -tp --nodeps apr-util-1.4.1.tar.bz2 sed -i "s/libuuid-devel/e2fsprogs-devel/" /usr/src/redhat/BUILD/apr-util-1.4.1/apr-util.spec mv apr-util-1.4.1.tar.bz2 /usr/src/redhat/SOURCES rpmbuild -bb /usr/src/redhat/BUILD/apr-util-1.4.1/apr-util.specとやったところ、テストでエラー(´・ω・`)
teststrmatch : SUCCESS testuri : SUCCESS testuuid : SUCCESS testbuckets : SUCCESS testpass : SUCCESS testmd4 : SUCCESS testmd5 : SUCCESS testcrypto : passphrase: KEY_3DES_192/MODE_CBC nss native error -8128: (SEC_ERROR_NO_MODULE) passphrase: KEY_3DES_192/MODE_CBC nss native error -8128: (SEC_ERROR_NO_MODULE) passphrase: KEY_AES_256/MODE_CBC nss native error -8128: (SEC_ERROR_NO_MODULE) passphrase: KEY_AES_256/MODE_CBC nss native error -8128: (SEC_ERROR_NO_MODULE) passphrase: KEY_AES_256/MODE_ECB nss native error -8128: (SEC_ERROR_NO_MODULE) passphrase: KEY_AES_256/MODE_ECB nss native error -8128: (SEC_ERROR_NO_MODULE) passphrase: KEY_AES_192/MODE_CBC nss native error -8128: (SEC_ERROR_NO_MODULE) passphrase: KEY_AES_192/MODE_CBC nss native error -8128: (SEC_ERROR_NO_MODULE) passphrase: KEY_AES_192/MODE_ECB nss native error -8128: (SEC_ERROR_NO_MODULE) passphrase: KEY_AES_192/MODE_ECB nss native error -8128: (SEC_ERROR_NO_MODULE) passphrase: KEY_AES_128/MODE_CBC nss native error -8128: (SEC_ERROR_NO_MODULE) passphrase: KEY_AES_128/MODE_CBC nss native error -8128: (SEC_ERROR_NO_MODULE) passphrase: KEY_AES_128/MODE_ECB nss native error -8128: (SEC_ERROR_NO_MODULE) passphrase: KEY_AES_128/MODE_ECB nss native error -8128: (SEC_ERROR_NO_MODULE) passphrase: KEY_3DES_192/MODE_CBC nss native error -8128: (SEC_ERROR_NO_MODULE) passphrase: KEY_3DES_192/MODE_CBC nss native error -8128: (SEC_ERROR_NO_MODULE) passphrase: KEY_AES_256/MODE_CBC nss native error -8128: (SEC_ERROR_NO_MODULE) passphrase: KEY_AES_256/MODE_CBC nss native error -8128: (SEC_ERROR_NO_MODULE) passphrase: KEY_AES_192/MODE_CBC nss native error -8128: (SEC_ERROR_NO_MODULE) passphrase: KEY_AES_192/MODE_CBC nss native error -8128: (SEC_ERROR_NO_MODULE) passphrase: KEY_AES_128/MODE_CBC nss native error -8128: (SEC_ERROR_NO_MODULE) passphrase: KEY_AES_128/MODE_CBC nss native error -8128: (SEC_ERROR_NO_MODULE) passphrase: KEY_3DES_192/MODE_CBC nss native error -8128: (SEC_ERROR_NO_MODULE) passphrase: KEY_AES_256/MODE_CBC nss native error -8128: (SEC_ERROR_NO_MODULE) passphrase: KEY_AES_256/MODE_ECB nss native error -8128: (SEC_ERROR_NO_MODULE) passphrase: KEY_3DES_192/MODE_CBC nss native error -8128: (SEC_ERROR_NO_MODULE) passphrase: KEY_AES_256/MODE_CBC nss native error -8128: (SEC_ERROR_NO_MODULE) passphrase: KEY_3DES_192/MODE_CBC nss native error -8128: (SEC_ERROR_NO_MODULE) passphrase: KEY_AES_256/MODE_CBC nss native error -8128: (SEC_ERROR_NO_MODULE) passphrase: KEY_AES_256/MODE_ECB nss native error -8128: (SEC_ERROR_NO_MODULE) passphrase: KEY_3DES_192/MODE_CBC nss native error -8128: (SEC_ERROR_NO_MODULE) passphrase: KEY_AES_256/MODE_CBC nss native error -8128: (SEC_ERROR_NO_MODULE) FAILED 6 of 13 testldap : SUCCESS testdbd : SUCCESS testdate : SUCCESS testmemcache : SUCCESS testxml : SUCCESS testxlate : SUCCESS testrmm : SUCCESS testdbm : SUCCESS testqueue : SUCCESS testreslist : SUCCESS Failed Tests Total Fail Failed % =================================================== testcrypto 13 6 46.15% Programs failed: testall make: *** [check] エラー 1 + exit 1 エラー: /var/tmp/rpm-tmp.35396 の不正な終了ステータス (%check)調べてみた感じだとこのあたりにバグ報告されてて解決されてない？？
sed -i "s/libuuid-devel/e2fsprogs-devel/" /usr/src/redhat/BUILD/apr-util-1.4.1/apr-util.spec sed -i "s/make check || exit 1/make check || \"continue\"/" /usr/src/redhat/BUILD/apr-util-1.4.1/apr-util.spec rpmbuild -bb /usr/src/redhat/BUILD/apr-util-1.4.1/apr-util.spec yum install --nogpgcheck /usr/src/redhat/RPMS/x86_64/apr-util-*
wget http://ftp.kddilabs.jp/infosystems/apache/httpd/httpd-2.4.3.tar.bz2
rpmbuild -tp httpd-2.4.3.tar.bz2
mv httpd-2.4.3.tar.bz2 /usr/src/redhat/SOURCES
sed -i "s/%{epoch}://g" /usr/src/redhat/BUILD/httpd-2.4.3/httpd.spec
rpmbuild -bb /usr/src/redhat/BUILD/httpd-2.4.3/httpd.spec
yum install --nogpgcheck /usr/src/redhat/RPMS/x86_64/httpd-*
で、出来上がりヾ(*･ω･)ｼ
yum -y install libselinux-devel pcre-devel openldap-devel lua-devel openssl-devel libuuid-devel lksctp-tools-devel db4-devel expat-devel postgresql-devel sqlite-devel freetds-devel unixODBC-devel nss-devel mysql-develyumで入らない依存モジュールのダウンロード＆ビルド＆インストール
wget ftp://ftp.riken.jp/Linux/fedora/development/18/source/SRPMS/d/distcache-1.4.5-23.src.rpm rpmbuild --rebuild distcache-1.4.5-23.src.rpm rpm -i ~/rpmbuild/RPMS/x86_64/distcache-* wget ftp://ftp.riken.jp/Linux/fedora/development/18/source/SRPMS/a/apr-1.4.6-3.fc18.src.rpm rpmbuild --rebuild apr-1.4.6-3.fc18.src.rpm rpm -i ~/rpmbuild/RPMS/x86_64/apr-* wget ftp://ftp.riken.jp/Linux/fedora/development/18/source/SRPMS/a/apr-util-1.4.1-5.fc18.src.rpm rpmbuild --rebuild apr-util-1.4.1-5.fc18.src.rpm rpm -i ~/rpmbuild/RPMS/x86_64/apr-util-*そしていよいよhttpd-2.4.3のダウンロード＆ビルド＆インストール
wget http://ftp.kddilabs.jp/infosystems/apache/httpd/httpd-2.4.3.tar.bz2
rpmbuild -tp httpd-2.4.3.tar.bz2
mv httpd-2.4.3.tar.bz2 ~/rpmbuild/SOURCES/
sed -i "s/%{epoch}://g" ~/rpmbuild/BUILD/httpd-2.4.3/httpd.spec
rpmbuild -bb ~/rpmbuild/BUILD/httpd-2.4.3/httpd.spec
rpm -i ~/rpmbuild/RPMS/x86_64/httpd-*
start=`date "+%s"`;i=1;while true; do echo aaaaaaaa,$i >> /gfs/test.log ;now=`date "+%s"`;if [ `expr $now - $start` -gt 60 ];then break;fi;i=`expr $i + 1`;doneaaaaaaaaの部分はクライアント1ではa,2ではb,3ではcと置き換えて実行しました
$ wc -l /gfs/test.log 15841 /gfs/test.log $ tac /gfs/test.log | grep aaa -m 1 aaaaaaaa,7639 $ tac /gfs/test.log | grep bbb -m 1 bbbbbbbb,4171 $ tac /gfs/test.log | grep ccc -m 1 cccccccc,4031となり、15841=7639+4171+4031と整合性が保たれているようです
$ wc -l /nfs/test.log 5461 /nfs/test.log $ tac /nfs/test.log | grep aaa -m 1 aaaaaaaa,2504 $ tac /nfs/test.log | grep bbb -m 1 bbbbbbbb,1678 $ tac /nfs/test.log | grep ccc -m 1 cccccccc,2484となり、5461≠2504+1678+2484=6666となりファイルに不整合がでています
#! /usr/bin/ruby
require 'rubygems'
require 'aws-sdk'
my_access_key_id = 'xxxxxxxxxxxxxxxxxxxx'
my_secret_key = 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
AWS.config({
:access_key_id => my_access_key_id,
:secret_access_key => my_secret_key
})
sts = AWS::STS.new()
session = sts.new_session()
#puts "Session expires at: #{session.expires_at.to_s}"
#s3 = AWS::S3.new(session.credentials)
for bucket in s3.buckets
puts bucket.url
end
てな具合で見慣れたCredentials周りのコードを書く訳ですがIAM roles for EC2 instances版だとここを省くことができます#! /usr/bin/ruby require 'rubygems' require 'aws-sdk' s3 = AWS::S3.new() for bucket in s3.buckets puts bucket.url endと、こんな単純に。
./list_s3_urls.rb http://bucket1.s3.amazonaws.com/ http://bucket2.s3.amazonaws.com/ http://bucket3.s3.amazonaws.com/みたいな感じで表示してくれます
curl http://169.254.169.254/latest/meta-data/iam/security-credentials/role1
{
"Code" : "Success",
"LastUpdated" : "2012-07-25T04:43:21Z",
"Type" : "AWS-HMAC",
"AccessKeyId" : "xxxxxxxxxx",
"SecretAccessKey" : "xxxxxxxxxx",
"Token" : "xxx",
"Expiration" : "2012-07-25T11:15:42Z"
}
みたいに最後の/の後にEC2インスタンスに割り当てられたroleの名前を入れてあげれば、一時的に利用できるAccessKeyIdとSecretAccessKeyを含むレスポンスが得られるのでこれを利用すれば良いみたいです。
$ openssl genrsa -des3 -out hoge.key 2048 openssl genrsa -out ozawa.key 2048 Generating RSA private key, 2048 bit long modulus ......................................................+++ .........................................................................+++ e is 65537 (0x10001) Enter pass phrase for ozawa.key: Verifying - Enter pass phrase for ozawa.key:パスフレーズなしにしたい場合は-des3を抜けばOK 2.Certificate Signing Request (CSR)の作成
openssl req -new -key hoge.key -out hoge.csr You are about to be asked to enter information that will be incorporated into your certificate request. What you are about to enter is what is called a Distinguished Name or a DN. There are quite a few fields but you can leave some blank For some fields there will be a default value, If you enter '.', the field will be left blank. ----- Country Name (2 letter code) [GB]:JP State or Province Name (full name) [Berkshire]:Tokyo Locality Name (eg, city) [Newbury]:Tokyo Organization Name (eg, company) [My Company Ltd]:company Organizational Unit Name (eg, section) []: Common Name (eg, your name or your server's hostname) []:hoge Email Address []: Please enter the following 'extra' attributes to be sent with your certificate request A challenge password []: An optional company name []:住所やら所属やら聞かれるけれど適当に入力 3.Self-Signed SSL Certificatの作成 アップロードするのはこのファイルです。
openssl x509 -req -days 3650 -in hoge.csr -signkey hoge.key -out hoge.crt Signature ok subject=/C=JP/ST=Tokyo/L=Tokyo/O=company/CN=hoge Getting Private key
[ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 1.08 GBytes 929 Mbits/sec
[ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 1.09 GBytes 935 Mbits/sec
[ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 462 MBytes 388 Mbits/sec
[ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 176 MBytes 147 Mbits/sec
[ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 461 MBytes 387 Mbits/sec
./super_pi 21
------ Started super_pi run : 2011年 8月 24日 水曜日 13:19:24 JST Start of PI calculation up to 2097152 decimal digits End of initialization. Time= 0.543 Sec. I= 1 L= 0 Time= 1.599 Sec. I= 2 L= 0 Time= 1.859 Sec. I= 3 L= 1 Time= 1.846 Sec. I= 4 L= 2 Time= 1.870 Sec. I= 5 L= 5 Time= 1.855 Sec. I= 6 L= 10 Time= 1.846 Sec. I= 7 L= 21 Time= 1.867 Sec. I= 8 L= 43 Time= 1.998 Sec. I= 9 L= 87 Time= 1.857 Sec. I=10 L= 174 Time= 1.863 Sec. I=11 L= 349 Time= 1.867 Sec. I=12 L= 698 Time= 1.863 Sec. I=13 L= 1396 Time= 1.851 Sec. I=14 L= 2794 Time= 1.895 Sec. I=15 L= 5588 Time= 1.973 Sec. I=16 L= 11176 Time= 1.839 Sec. I=17 L= 22353 Time= 1.820 Sec. I=18 L= 44707 Time= 1.806 Sec. I=19 L= 89415 Time= 1.761 Sec. I=20 L= 178831 Time= 1.800 Sec. End of main loop End of calculation. Time= 39.002 Sec. End of data output. Time= 0.171 Sec. Total calculation(I/O) time= 39.173( 4.013) Sec. ------ Ended super_pi run : 2011年 8月 24日 水曜日 13:24:03 JST
------ Started super_pi run : 2011年 8月 24日 水曜日 13:24:30 JST Start of PI calculation up to 2097152 decimal digits End of initialization. Time= 0.587 Sec. I= 1 L= 0 Time= 1.706 Sec. I= 2 L= 0 Time= 2.113 Sec. I= 3 L= 1 Time= 2.018 Sec. I= 4 L= 2 Time= 1.840 Sec. I= 5 L= 5 Time= 1.844 Sec. I= 6 L= 10 Time= 1.891 Sec. I= 7 L= 21 Time= 1.954 Sec. I= 8 L= 43 Time= 1.957 Sec. I= 9 L= 87 Time= 1.878 Sec. I=10 L= 174 Time= 1.857 Sec. I=11 L= 349 Time= 1.871 Sec. I=12 L= 698 Time= 1.944 Sec. I=13 L= 1396 Time= 2.012 Sec. I=14 L= 2794 Time= 2.037 Sec. I=15 L= 5588 Time= 1.841 Sec. I=16 L= 11176 Time= 1.852 Sec. I=17 L= 22353 Time= 1.815 Sec. I=18 L= 44707 Time= 1.793 Sec. I=19 L= 89415 Time= 1.739 Sec. I=20 L= 178831 Time= 1.616 Sec. End of main loop End of calculation. Time= 39.638 Sec. End of data output. Time= 0.181 Sec. Total calculation(I/O) time= 39.819( 4.014) Sec. ------ Ended super_pi run : 2011年 8月 24日 水曜日 13:32:02 JST
cpulimit -e pi -l 18
------ Started super_pi run : 2011年 8月 24日 水曜日 13:44:04 JST Start of PI calculation up to 2097152 decimal digits End of initialization. Time= 0.546 Sec. I= 1 L= 0 Time= 1.637 Sec. I= 2 L= 0 Time= 1.873 Sec. I= 3 L= 1 Time= 1.865 Sec. I= 4 L= 2 Time= 1.861 Sec. I= 5 L= 5 Time= 1.878 Sec. I= 6 L= 10 Time= 1.869 Sec. I= 7 L= 21 Time= 1.879 Sec. I= 8 L= 43 Time= 1.877 Sec. I= 9 L= 87 Time= 1.864 Sec. I=10 L= 174 Time= 1.873 Sec. I=11 L= 349 Time= 1.877 Sec. I=12 L= 698 Time= 1.882 Sec. I=13 L= 1396 Time= 1.843 Sec. I=14 L= 2794 Time= 1.858 Sec. I=15 L= 5588 Time= 1.849 Sec. I=16 L= 11176 Time= 1.860 Sec. I=17 L= 22353 Time= 1.829 Sec. I=18 L= 44707 Time= 1.829 Sec. I=19 L= 89415 Time= 1.751 Sec. I=20 L= 178831 Time= 1.654 Sec. End of main loop End of calculation. Time= 38.643 Sec. End of data output. Time= 0.170 Sec. Total calculation(I/O) time= 38.813( 3.936) Sec. ------ Ended super_pi run : 2011年 8月 24日 水曜日 13:47:32 JST
------ Started super_pi run : 2011年 8月 24日 水曜日 13:47:34 JST Start of PI calculation up to 2097152 decimal digits End of initialization. Time= 0.570 Sec. I= 1 L= 0 Time= 1.660 Sec. I= 2 L= 0 Time= 1.862 Sec. I= 3 L= 1 Time= 1.888 Sec. I= 4 L= 2 Time= 1.892 Sec. I= 5 L= 5 Time= 1.890 Sec. I= 6 L= 10 Time= 1.862 Sec. I= 7 L= 21 Time= 1.858 Sec. I= 8 L= 43 Time= 1.905 Sec. I= 9 L= 87 Time= 1.877 Sec. I=10 L= 174 Time= 1.882 Sec. I=11 L= 349 Time= 1.883 Sec. I=12 L= 698 Time= 1.862 Sec. I=13 L= 1396 Time= 1.873 Sec. I=14 L= 2794 Time= 1.865 Sec. I=15 L= 5588 Time= 1.870 Sec. I=16 L= 11176 Time= 1.864 Sec. I=17 L= 22353 Time= 1.842 Sec. I=18 L= 44707 Time= 1.830 Sec. I=19 L= 89415 Time= 1.756 Sec. I=20 L= 178831 Time= 1.645 Sec. End of main loop End of calculation. Time= 38.825 Sec. End of data output. Time= 0.170 Sec. Total calculation(I/O) time= 38.995( 3.964) Sec. ------ Ended super_pi run : 2011年 8月 24日 水曜日 13:51:10 JST
DEPRECATION WARNING: Object#returning has been deprecated in favor of Object#tap.
gem 'aws-s3', :git => 'git://github.com/emk/aws-s3.git', :require => 'aws/s3' gem 'xml-simple'
{
"Statement": [
{
"Action": "s3:*",
"Effect": "Allow",
"Resource": "arn:aws:s3:::*"
}
]
}
とかしちゃえば、s3に関してはなんでもOKになります。{
"Version": "2008-10-17",
"Id": "2c08cdf1-ddfc-4765-ac19-26b03a8e8b5e",
"Statement": [
{
"Sid": "AllowMyUser",
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::012345678901:user/iam-user-name"
},
"Action": "s3:*",
"Resource": [
"arn:aws:s3:::bucket-name/*",
"arn:aws:s3:::bucket-name"
]
}
]
}