#MONIT DOCKER INSTALL#
#MONIT DOCKER FULL#

Serverd : ok=6 changed=4 unreachable=0 failed=0 skipped=0 rescued=0 ansible]$ curl Welcome to on ansible]$ curl Welcome to on 172.25.250.13 Serverc : ok=6 changed=4 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0 该playbook在webservers主机组中的主机上运行 ansible]$ cd roles]$ ansible-galaxy init apacheĪpache requirements.yml selinux roles]$ cd apache]$ lsĭefaults files handlers meta README.md tasks templates tests apache]$ cd tasks]$ tasks]$ vim main.ymlĭefaults files handlers meta README.md tasks templates tests apache]$ cd templates]$ vim 2 phpinfo is already installed, skipping. balancer is already installed, skipping. home/student/ansible/roles/requirements.yml -p /home/student/ansible/roles/ 此角色的名称应当为 phpinfo ansible]$ vim roles/requirements.yml 使用 Ansible Galaxy 和要求文件 /home/student/ansible/roles/requirements.yml，从以下 URL 下载角色并安装到 /home/student/ansible/roles： ansible]$ ansible-playbook ansible]$ cp -r /usr/share/ansible/roles/linux /home/student/ansible/roles/selinux ansible]$ cp -r /usr/share/ansible/roles/linux /home/student/ansible/roles/selinuxīecome: ansible]$ ansible-playbook selinux.yml

#MONIT DOCKER INSTALL#

配置该角色，以启用 iburst 参数 ansible]$ sudo yum -y install ansible]$ mkdir ansible]$ cp -r /usr/share/ansible/roles/rhel-system-roles.timesync/ ansible]$ vim timesync.yml In my case, because I start docker services on boot it wasn't an issue.安装 RHEL 系统角色软件包，并创建符合以下条件的playbook /home/student/ansible/timesync.yml：

The only downside to this method is that Monit will log about the service not running repeatedly until it is started. Here you see I'm also using the MATCHING syntax because the entrypoint for Docker containers may change in the future (I don't maintain this one myself). In my case, 13% is about 65% CPU on a single core which (over 3 minutes) I deemed enough to recognize when the bug had occurred.

#MONIT DOCKER FULL#

Monit considers 100% CPU usage to be full utilization on all cores, which is why you see 13% (you can also verify current service CPU usage checking the output of monit status). If cpu usage > 13% for 3 cycles then restart Stop program = '/usr/bin/docker stop home-assistant'

Start program = '/usr/bin/docker start home-assistant' Monit doesn't have a good answer for this built-in, so the key is to override the start action by executing a no-op when the service isn't running: only check process home-assistant MATCHING ^python.+homeassistant 'if already running' turned out to be a little more complicated than I expected. Otherwise, Monit would proceed to start the container on boot prior to the mounted drive being present, resulting in a bunch of headaches. I wanted Monit to automatically restart the service when it was eating CPU (which ordinarily is trivial to do), but due to the mapped volume, I only wanted it to stop & start the service if it was already running. I recently ran into an issue where a bug in one of my Docker containers would intermittently chew through CPU until restarted.

Monit docker