Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
cloudappliance/mastermasterdb [2020_04_13 20:31] – [Disclaimer] steven | cloudappliance/mastermasterdb [2021_06_18 09:17] – smeadmin | ||
---|---|---|---|
Line 102: | Line 102: | ||
</ | </ | ||
- | Place a "#" | + | Place a "#" |
+ | |||
+ | ``` | ||
+ | MAILTO='' | ||
+ | #Ansible: | ||
+ | #* * * * * / | ||
+ | #Ansible: #3 | ||
+ | #5 4 * * * / | ||
+ | #Ansible: #2 | ||
+ | #* * * * * / | ||
+ | #Ansible: #5 | ||
+ | #10 2 1 * * / | ||
+ | #Ansible: #4 | ||
+ | #5 * * * * / | ||
+ | #Ansible: #7 | ||
+ | 30 1 * * * / | ||
+ | #Ansible: #6 | ||
+ | #10 * * * * / | ||
+ | * * * * * / | ||
+ | ``` | ||
+ | |||
+ | <WRAP center round info 100%> | ||
+ | Please note this information above was updated with the 2106 release of the File Fabric. Please see this [[cloudappliance/ | ||
+ | </ | ||
- | {{:: | ||
=== iptables for dbservers === | === iptables for dbservers === | ||
Line 110: | Line 132: | ||
On both smesql01 and smesql02, you must update iptables to allow incoming connections to mariadb, do the following. | On both smesql01 and smesql02, you must update iptables to allow incoming connections to mariadb, do the following. | ||
- | As root: | + | As root we will edit the iptables file to add the following lines: |
+ | / | ||
< | < | ||
- | iptables-save > / | + | ... |
- | ipt_line=`iptables | + | -A RH-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 3306 -j ACCEPT |
- | insert_line=`expr $ipt_line | + | -A RH-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 11211 -j ACCEPT |
- | iptables | + | ... |
+ | COMMIT | ||
+ | </ | ||
+ | Then issue a restart: | ||
- | iptables | + | < |
- | + | systemctl restart | |
- | iptables-save > / | + | systemctl restart docker |
</ | </ | ||
Line 350: | Line 376: | ||
We will also need to allow multicast traffic (244.0.0.0) through our iptables firewall, as well as adjust selinux to allow keepalived to operate. Finally, we will add a user (keepalived_script) which keepalived will use. | We will also need to allow multicast traffic (244.0.0.0) through our iptables firewall, as well as adjust selinux to allow keepalived to operate. Finally, we will add a user (keepalived_script) which keepalived will use. | ||
+ | / | ||
< | < | ||
- | iptables -I INPUT -i eth0 -d 224.0.0.0/8 -p vrrp -j ACCEPT | + | ... |
- | iptables-save | + | -A RH-Firewall-1-INPUT |
- | semanage permissive -a keepalived_t | + | ... |
- | groupadd keepalived_script | + | COMMIT |
- | useradd -s / | + | </code> |
+ | Then issue a restart: | ||
+ | |||
+ | < | ||
+ | systemctl restart iptables | ||
+ | systemctl restart docker | ||
</ | </ | ||
Line 611: | Line 643: | ||
== crontab == | == crontab == | ||
- | All of smestorage' | + | The majority |
**As root on smeweb02 only:** | **As root on smeweb02 only:** | ||
< | < | ||
Line 617: | Line 649: | ||
</ | </ | ||
- | Place a # in front of six of the seven jobs listed in the crontab | + | Your crontab |
+ | |||
+ | ``` | ||
+ | MAILTO='' | ||
+ | #Ansible: | ||
+ | #* * * * * / | ||
+ | #Ansible: #3 | ||
+ | #5 4 * * * / | ||
+ | #Ansible: #2 | ||
+ | #* * * * * / | ||
+ | #Ansible: #5 | ||
+ | #10 2 1 * * / | ||
+ | #Ansible: #4 | ||
+ | #5 * * * * / | ||
+ | #Ansible: #7 | ||
+ | 30 1 * * * / | ||
+ | #Ansible: #6 | ||
+ | #10 * * * * / | ||
+ | * * * * * / | ||
+ | ``` | ||
+ | |||
+ | <WRAP center round info 100%> | ||
+ | Please note this information above was updated with the 2106 release of the File Fabric. Please see this [[cloudappliance/ | ||
+ | </ | ||
Restart both servers, so on both smeweb01 and smeweb02, execute a reboot. | Restart both servers, so on both smeweb01 and smeweb02, execute a reboot. |