you've got to find what you love.

bitnami@ip:/opt/bitnami/php/etc$ sudo cat /opt/bitnami/php/var/log/php-fpm.log

[15-May-2020 12:52:48] WARNING: [pool wordpress] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 8 children, there are 3 idle, and 13 total children

[15-May-2020 12:52:56] WARNING: [pool wordpress] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 16 children, there are 0 idle, and 14 total children

[15-May-2020 12:53:00] WARNING: [pool wordpress] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 18 total children

[15-May-2020 12:53:03] WARNING: [pool wordpress] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 22 total children

[15-May-2020 12:53:07] WARNING: [pool wordpress] server reached pm.max_children setting (25), consider raising it

[15-May-2020 12:56:03] WARNING: [pool wordpress] server reached pm.max_children setting (25), consider raising it

[16-May-2020 06:16:58] WARNING: [pool wordpress] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 8 children, there are 3 idle, and 13 total children

[16-May-2020 06:17:07] WARNING: [pool wordpress] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 16 children, there are 3 idle, and 14 total children

[16-May-2020 06:17:08] WARNING: [pool wordpress] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 3 idle, and 15 total children

[16-May-2020 07:52:26] WARNING: [pool wordpress] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 8 children, there are 2 idle, and 21 total children

[16-May-2020 07:52:29] WARNING: [pool wordpress] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 16 children, there are 2 idle, and 23 total children

[16-May-2020 07:52:34] WARNING: [pool wordpress] server reached pm.max_children setting (25), consider raising it

bitnam$ ps aux | grep php-fpm

root      3476  0.0  0.2 146396  9340 ?        Ss   08:20   0:01 php-fpm: master process (/opt/bitnami/php/etc/php-fpm.conf)

daemon    3477  0.6  0.6 153868 25196 ?        S    08:20   4:15 php-fpm: pool wordpress

daemon    3478  0.6  0.6 154064 25380 ?        S    08:20   4:09 php-fpm: pool wordpress

bitnam$ tail /opt/bitnami/php/etc/php-fpm.conf

include=/opt/bitnami/apps/wordpress/conf/php-fpm/pool.conf

include=/opt/bitnami/apps/phpmyadmin/conf/php-fpm/pool.conf

bitnami@ip$ cat /opt/bitnami/apps/wordpress/conf/php-fpm/pool.conf

[wordpress]

listen=/opt/bitnami/php/var/run/wordpress.sock

include=/opt/bitnami/php/etc/common-dynamic.conf

include=/opt/bitnami/apps/wordpress/conf/php-fpm/php-settings.conf

include=/opt/bitnami/php/etc/environment.conf

pm=dynamic

bitnami$ cat /opt/bitnami/php/etc/common-dynamic.conf

include=/opt/bitnami/php/etc/common.conf

pm=dynamic

pm.max_children=5

pm.start_servers=2

pm.min_spare_servers=1

pm.max_spare_servers=3

include=/opt/bitnami/php/etc/bitnami/common.conf

bitnami$ cat /opt/bitnami/php/etc/bitnami/common.conf

;

; Bitnami PHP-FPM Configuration

; Copyright 2019 Bitnami.com All Rights Reserved

;

; Note: This file will be modified on server size changes

;

pm.max_children=25

pm.start_servers=4

pm.min_spare_servers=4

pm.max_spare_servers=10

pm.max_requests=5000

; Choose how the process manager will control the number of child processes.

; Possible Values:

;   static  - a fixed number (pm.max_children) of child processes;

;   dynamic - the number of child processes are set dynamically based on the

;             following directives. With this process management, there will be

;             always at least 1 children.

;             pm.max_children      - the maximum number of children that can

;                                    be alive at the same time.

;             pm.start_servers     - the number of children created on startup.

;             pm.min_spare_servers - the minimum number of children in 'idle'

;                                    state (waiting to process). If the number

;                                    of 'idle' processes is less than this

;                                    number then some children will be created.

;             pm.max_spare_servers - the maximum number of children in 'idle'

;                                    state (waiting to process). If the number

;                                    of 'idle' processes is greater than this

;                                    number then some children will be killed.

;  ondemand - no children are created at startup. Children will be forked when

;             new requests will connect. The following parameter are used:

;             pm.max_children           - the maximum number of children that

;                                         can be alive at the same time.

;             pm.process_idle_timeout   - The number of seconds after which

;                                         an idle process will be killed.

; Note: This value is mandatory.

sudo /opt/bitnami/ctlscript.sh restart php-fpm

bitnami$ tail -f /opt/bitnami/apache2/logs/access_log

173.212.194.14 - - [17/May/2020:00:22:28 +0900] "GET /product-tag/med/?product_orderby=popularity&product_count=24&product_view=grid&product_order=asc HTTP/1.1" 301 -

173.212.194.14 - - [17/May/2020:00:22:47 +0900] "GET /?product_orderby=popularity&product_count=24&product_view=grid&product_order=asc HTTP/1.1" 200 22179

; By default the status page output is formatted as text/plain. Passing either

; 'html', 'xml' or 'json' in the query string will return the corresponding

; output syntax. Example:

;   http://www.foo.bar/status

;   http://www.foo.bar/status?json

;   http://www.foo.bar/status?html

;   http://www.foo.bar/status?xml

;

; By default the status page only outputs short status. Passing 'full' in the

; query string will also return status for each pool process.

; Example:

;   http://www.foo.bar/status?full

;   http://www.foo.bar/status?json&full

;   http://www.foo.bar/status?html&full

;   http://www.foo.bar/status?xml&full

; The Full status returns for each process:

;   pid                  - the PID of the process;

;   state                - the state of the process (Idle, Running, ...);

;   start time           - the date and time the process has started;

;   start since          - the number of seconds since the process has started;

;   requests             - the number of requests the process has served;

;   request duration     - the duration in µs of the requests;

;   request method       - the request method (GET, POST, ...);

;   request URI          - the request URI with the query string;

;   content length       - the content length of the request (only with POST);

;   user                 - the user (PHP_AUTH_USER) (or '-' if not set);

;   script               - the main script called (or '-' if not set);

;   last request cpu     - the %cpu the last request consumed

;                          it's always 0 if the process is not in Idle state

;                          because CPU calculation is done when the request

;                          processing has terminated;

;   last request memory  - the max amount of memory the last request consumed

;                          it's always 0 if the process is not in Idle state

;                          because memory calculation is done when the request

;                          processing has terminated;

; If the process is in Idle state, then informations are related to the

; last request the process has served. Otherwise informations are related to

; the current request being served.

; Example output:

;   ************************

;   pid:                  31330

;   state:                Running

;   start time:           01/Jul/2011:17:53:49 +0200

;   start since:          63087

;   requests:             12808

;   request duration:     1250261

;   request method:       GET

;   request URI:          /test_mem.php?N=10000

;   content length:       0

;   user:                 -

;   script:               /home/fat/web/docs/php/test_mem.php

;   last request cpu:     0.00

;   last request memory:  0

;

; Note: There is a real-time FPM status monitoring sample web page available

;       It's available in: /bitnami/lamp73stack-linux-x64/output/php/share/php/fpm/status.html

;

; Note: The value must start with a leading slash (/). The value can be

;       anything, but it may not be a good idea to use the .php extension or it

;       may conflict with a real PHP file.

; Default Value: not set

;pm.status_path = /status

; The log file for slow requests

; Default Value: not set

; Note: slowlog is mandatory if request_slowlog_timeout is set

;slowlog = log/$pool.log.slow

; The timeout for serving a single request after which a PHP backtrace will be

; dumped to the 'slowlog' file. A value of '0s' means 'off'.

; Available units: s(econds)(default), m(inutes), h(ours), or d(ays)

; Default Value: 0

;request_slowlog_timeout = 0

pm.status_path = /status

slowlog = log/$pool.log.slow

request_slowlog_timeout = 0

$ df -h

Filesystem      Size  Used Avail Use% Mounted on

udev            2.0G     0  2.0G   0% /dev

tmpfs           396M   11M  385M   3% /run

/dev/xvda1       78G   43G   35G  56% /

tmpfs           2.0G     0  2.0G   0% /dev/shm

tmpfs           5.0M     0  5.0M   0% /run/lock

tmpfs           2.0G     0  2.0G   0% /sys/fs/cgroup

/dev/loop0       29M   29M     0 100% /snap/amazon-ssm-agent/2012

/dev/loop2       18M   18M     0 100% /snap/amazon-ssm-agent/1566

/dev/loop1       97M   97M     0 100% /snap/core/9436

/dev/loop3       97M   97M     0 100% /snap/core/9665

tmpfs           396M     0  396M   0% /run/user/1000

lsblk로 mount 정보 확인 

$ lsblk

NAME    MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT

xvda    202:0    0   80G  0 disk

└─xvda1 202:1    0   80G  0 part /

xvdf    202:80   0  256G  0 disk

loop0     7:0    0 28.1M  1 loop /snap/amazon-ssm-agent/2012

loop1     7:1    0 96.5M  1 loop /snap/core/9436

loop2     7:2    0   18M  1 loop /snap/amazon-ssm-agent/1566

loop3     7:3    0   97M  1 loop /snap/core/9665

새로 mount할 디스크 파일 타입 확인 

$ sudo file -s /dev/xvdf

/dev/xvdf: data

기존에 mount되어있는 디스크 파일 타입 확인합니다. ext4를 사용하고 있네요. 

$ sudo file -s /dev/xvda1

/dev/xvda1: Linux rev 1.0 ext4 filesystem data, UUID=9bd74952-5d49-4ac3-8b92-6491cf32a505, volume name "cloudimg-rootfs" (needs journal recovery) (extents) (large files) (huge files)

새로운 디스크도 ext4타입으로 포맷합니다. 이떄 꼭 새로 붙이는 디스크가 비어있는지 확인해야합니다. 

디스크 내용이 들어있으면 포맷하지 마세요!

$ sudo mkfs -t ext4 /dev/xvdf

mke2fs 1.42.13 (17-May-2015)

Creating filesystem with 67108864 4k blocks and 16777216 inodes

Filesystem UUID: 1fba4148-faac-4675-a772-87a67e1b9d6d

Superblock backups stored on blocks:

        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,

        4096000, 7962624, 11239424, 20480000, 23887872

Allocating group tables: done

Writing inode tables: done

Creating journal (32768 blocks): done

Writing superblocks and filesystem accounting information: done

새로 포맷한 디스크의 파일 타입 확인. 

$ sudo file -s /dev/xvdf

/dev/xvdf: Linux rev 1.0 ext4 filesystem data, UUID=1fba4148-faac-4675-a772-87a67e1b9d6d (extents) (large files) (huge files)

마운트할 위치에 디렉토리를 생성하고 

$ sudo mkdir /data

sudo mount device_name mount_point 로 mount를 실행한다. 

$ sudo mount /dev/xvdf /data

df -h로 잘 마운트 되었는지 확인한다. 

$ df -h

Filesystem      Size  Used Avail Use% Mounted on

udev            2.0G     0  2.0G   0% /dev

tmpfs           396M   11M  385M   3% /run

/dev/xvda1       78G   48G   30G  62% /

tmpfs           2.0G     0  2.0G   0% /dev/shm

tmpfs           5.0M     0  5.0M   0% /run/lock

tmpfs           2.0G     0  2.0G   0% /sys/fs/cgroup

/dev/loop0       29M   29M     0 100% /snap/amazon-ssm-agent/2012

/dev/loop2       18M   18M     0 100% /snap/amazon-ssm-agent/1566

/dev/loop1       97M   97M     0 100% /snap/core/9436

/dev/loop3       97M   97M     0 100% /snap/core/9665

tmpfs           396M     0  396M   0% /run/user/1000

/dev/xvdf       252G   60M  239G   1% /data

#sudo apt-get update

패키지 설치정보가 있는 서버 정보를 업데이트 한다.

#sudo apt-get upgrade

기존에 설치되어 있는 패키지들을 업데이트 한다.

#sudo apt-get install apache2 

#sudo apt-get intall php5

#sudo apt-get install php5-mysql

mysql과 php를 연동시키는 패키지도 설치한다.

#sudo apt-get install phpmyadmin

web mysql 관리 툴인 phpmyadmin도 설치한다.

설치중 몇가지 확인 창이 뜨는데 첫번째 웹 서버 자동 설정에서

apache2를 선택하도록 한다.

스페이스를 눌러 제대로 *가 뜨는 것을 확인해야 한다.

 그냥 엔터 누르고 지나갔다가 나중에 http 404 에러가 나와서

 phpmyadmin 다시 설정하지 않으려면 ㅠㅠ

db구성을 dbconfig-common으로 설정하겠냐고도 물어보는데

수동으로 설정하거나 이미 DB가 설치되어 구성되어 있는 경우 아니면

그냥 dbconfig-common으로 설치하면 된다.

중간에  mysql 설정할때 넣었던 root 비밀번호도 입력하면 설치 완료.

아래와 같이 대충 test.php를 만들어서 제대로 출력되나 확인해본다. 

 <?php echo "hello"; ?>

ubuntu@ip-**:/var/www$ ll
total 12
drwxr-xr-x  3 root root 4096 Apr  2 04:56 ./
drwxr-xr-x 13 root root 4096 Apr  2 04:56 ../
drwxr-xr-x  2 root root 4096 Apr  2 05:29 html/

ubuntu@ip-**:/var/www$ sudo chown ubuntu -R /var/www/html
ubuntu@ip-**:/var/www$ ll
total 12
drwxr-xr-x  3 root   root 4096 Apr  2 04:56 ./
drwxr-xr-x 13 root   root 4096 Apr  2 04:56 ../
drwxr-xr-x  2 ubuntu root 4096 Apr  2 05:29 html/

Once phpMyAdmin is installed point your browser to http://localhost/phpmyadmin to start using it. You should be able to login using any users you've setup in MySQL. If no users have been setup, use admin with no password to login.

Should you get a 404 "Not Found" error when you point your browser to the location of phpMyAdmin (such as: http://localhost/phpmyadmin) the issue is likely caused by not checking the 'Apache 2' selection during installation. To redo the installation run the following:

 sudo dpkg-reconfigure -plow phpmyadmin

Then select Apache 2 for the webserver you wish to configure.

참고: https://help.ubuntu.com/community/phpMyAdmin

• For an Amazon Linux AMI, the user name is ec2-user.

• For a RHEL5 AMI, the user name is either root or ec2-user.

• For an Ubuntu AMI, the user name is ubuntu.

• For a Fedora AMI, the user name is either fedora or ec2-user.

• For SUSE Linux, the user name is root.

• Otherwise, if ec2-user and root don't work, check with the AMI provider.

EC2(Elastic Compute Cloud) 

 윈도우/리눅스 t2.micro 인스턴스(1기가 메모리) 를 한 달동안 750시간 사용 

저장공간 - 5기가

관계형 데이터베이스 - DB 인스턴스를 한달동안 750시간 사용 

noSQL - 25기가의 저장공간, 한 달동안 200백만건의 요청 사용