質問編集履歴
4
補足追記
test
CHANGED
|
File without changes
|
test
CHANGED
|
@@ -3,6 +3,8 @@
|
|
|
3
3
|
しかし、なぜpacemaker+corosyncはtomcat.serviceではなく、tomcat@tomcat.serviceを
|
|
4
4
|
|
|
5
5
|
必要としていたのでしょうか？
|
|
6
|
+
|
|
7
|
+
【追記】tomcat@tomcat.serviceは既存のtomcat.serviceをコピーして作成しました。
|
|
6
8
|
|
|
7
9
|
|
|
8
10
|
|
3
追記情報
test
CHANGED
|
File without changes
|
test
CHANGED
|
@@ -39,3 +39,135 @@
|
|
|
39
39
|
corosync:2.4.0
|
|
40
40
|
|
|
41
41
|
tomcat:8.5.11
|
|
42
|
+
|
|
43
|
+
|
|
44
|
+
|
|
45
|
+
■(追記)pcs config実行結果
|
|
46
|
+
|
|
47
|
+
```pcs
|
|
48
|
+
|
|
49
|
+
[root@osact ~]# pcs config
|
|
50
|
+
|
|
51
|
+
Cluster Name: cluster_os
|
|
52
|
+
|
|
53
|
+
Corosync Nodes:
|
|
54
|
+
|
|
55
|
+
osact ossby
|
|
56
|
+
|
|
57
|
+
Pacemaker Nodes:
|
|
58
|
+
|
|
59
|
+
osact ossby
|
|
60
|
+
|
|
61
|
+
|
|
62
|
+
|
|
63
|
+
Resources:
|
|
64
|
+
|
|
65
|
+
Resource: VIP (class=ocf provider=heartbeat type=IPaddr2)
|
|
66
|
+
|
|
67
|
+
Attributes: ip=192.168.172.9 cidr_netmask=24
|
|
68
|
+
|
|
69
|
+
Operations: start interval=0s timeout=20s (VIP-start-interval-0s)
|
|
70
|
+
|
|
71
|
+
stop interval=0s timeout=20s (VIP-stop-interval-0s)
|
|
72
|
+
|
|
73
|
+
monitor interval=10s (VIP-monitor-interval-10s)
|
|
74
|
+
|
|
75
|
+
Resource: Web_Cluster (class=ocf provider=heartbeat type=apache)
|
|
76
|
+
|
|
77
|
+
Attributes: configfile=/etc/httpd/conf/httpd.conf statusurl=http://127.0.0.1/server-status
|
|
78
|
+
|
|
79
|
+
Operations: start interval=0s timeout=40s (Web_Cluster-start-interval-0s)
|
|
80
|
+
|
|
81
|
+
stop interval=0s timeout=60s (Web_Cluster-stop-interval-0s)
|
|
82
|
+
|
|
83
|
+
monitor interval=1min (Web_Cluster-monitor-interval-1min)
|
|
84
|
+
|
|
85
|
+
Resource: Tomcat_Cluster (class=ocf provider=heartbeat type=tomcat)
|
|
86
|
+
|
|
87
|
+
Attributes: statusurl=http://127.0.0.1:8080/ java_home=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-0.b13.el7_3.x86_64/jre catalina_home=/usr/tomcat8 tomcat_user=tomcat
|
|
88
|
+
|
|
89
|
+
Operations: start interval=0s timeout=60s (Tomcat_Cluster-start-interval-0s)
|
|
90
|
+
|
|
91
|
+
stop interval=0s timeout=120s (Tomcat_Cluster-stop-interval-0s)
|
|
92
|
+
|
|
93
|
+
monitor interval=1min (Tomcat_Cluster-monitor-interval-1min)
|
|
94
|
+
|
|
95
|
+
|
|
96
|
+
|
|
97
|
+
Stonith Devices:
|
|
98
|
+
|
|
99
|
+
Fencing Levels:
|
|
100
|
+
|
|
101
|
+
|
|
102
|
+
|
|
103
|
+
Location Constraints:
|
|
104
|
+
|
|
105
|
+
Resource: VIP
|
|
106
|
+
|
|
107
|
+
Enabled on: osact (score:INFINITY) (role: Started) (id:cli-prefer-VIP)
|
|
108
|
+
|
|
109
|
+
Disabled on: ossby (score:-INFINITY) (role: Started) (id:cli-ban-VIP-on-ossby)
|
|
110
|
+
|
|
111
|
+
Ordering Constraints:
|
|
112
|
+
|
|
113
|
+
start VIP then start Web_Cluster (kind:Mandatory) (id:order-VIP-Web_Cluster-mandatory)
|
|
114
|
+
|
|
115
|
+
start Web_Cluster then start Tomcat_Cluster (kind:Mandatory) (id:order-Web_Cluster-Tomcat_Cluster-mandatory)
|
|
116
|
+
|
|
117
|
+
Colocation Constraints:
|
|
118
|
+
|
|
119
|
+
Web_Cluster with VIP (score:INFINITY) (id:colocation-Web_Cluster-VIP-INFINITY)
|
|
120
|
+
|
|
121
|
+
Tomcat_Cluster with VIP (score:INFINITY) (id:colocation-Tomcat_Cluster-VIP-INFINITY)
|
|
122
|
+
|
|
123
|
+
Resource Sets:
|
|
124
|
+
|
|
125
|
+
set VIP (id:pcs_rsc_set_VIP_Tomcat_Cluster) setoptions score=INFINITY (id:pcs_rsc_colocation_set_VIP_Tomcat_Cluster)
|
|
126
|
+
|
|
127
|
+
set VIP Tomcat_Cluster (id:pcs_rsc_set_VIP_Tomcat_Cluster-1) setoptions score=INFINITY (id:pcs_rsc_colocation_set_VIP_Tomcat_Cluster-1)
|
|
128
|
+
|
|
129
|
+
Ticket Constraints:
|
|
130
|
+
|
|
131
|
+
|
|
132
|
+
|
|
133
|
+
Alerts:
|
|
134
|
+
|
|
135
|
+
No alerts defined
|
|
136
|
+
|
|
137
|
+
|
|
138
|
+
|
|
139
|
+
Resources Defaults:
|
|
140
|
+
|
|
141
|
+
No defaults set
|
|
142
|
+
|
|
143
|
+
Operations Defaults:
|
|
144
|
+
|
|
145
|
+
No defaults set
|
|
146
|
+
|
|
147
|
+
|
|
148
|
+
|
|
149
|
+
Cluster Properties:
|
|
150
|
+
|
|
151
|
+
cluster-infrastructure: corosync
|
|
152
|
+
|
|
153
|
+
cluster-name: cluster_os
|
|
154
|
+
|
|
155
|
+
dc-version: 1.1.15-11.el7_3.2-e174ec8
|
|
156
|
+
|
|
157
|
+
have-watchdog: false
|
|
158
|
+
|
|
159
|
+
last-lrm-refresh: 1485467664
|
|
160
|
+
|
|
161
|
+
no-quorum-policy: ignore
|
|
162
|
+
|
|
163
|
+
stonith-enabled: false
|
|
164
|
+
|
|
165
|
+
|
|
166
|
+
|
|
167
|
+
Quorum:
|
|
168
|
+
|
|
169
|
+
Options:
|
|
170
|
+
|
|
171
|
+
[root@osact ~]#
|
|
172
|
+
|
|
173
|
+
```
|
2
補足追記
test
CHANGED
|
File without changes
|
test
CHANGED
|
@@ -1,3 +1,11 @@
|
|
|
1
|
+
★以下について、tomcat@tomcat.serviceを作成することでtomcat登録が正常に行えました。
|
|
2
|
+
|
|
3
|
+
しかし、なぜpacemaker+corosyncはtomcat.serviceではなく、tomcat@tomcat.serviceを
|
|
4
|
+
|
|
5
|
+
必要としていたのでしょうか？
|
|
6
|
+
|
|
7
|
+
|
|
8
|
+
|
|
1
9
|
pacemaker+corosyncに、リソースとしてtomcatを登録したいのですが、下記エラーが発生し、登録に失敗します。
|
|
2
10
|
|
|
3
11
|
|
1
補足追記
test
CHANGED
|
File without changes
|
test
CHANGED
|
@@ -18,7 +18,7 @@
|
|
|
18
18
|
|
|
19
19
|
存在します。
|
|
20
20
|
|
|
21
|
-
※systemctl start tomcat で正常にtomcat起動でき、http://localhost:8080へも正常アクセスできることは確認済みです。
|
|
21
|
+
※pacemaker+corosyncを介さずに、systemctl start tomcat で正常にtomcat起動でき、http://localhost:8080へも正常アクセスできることは確認済みです。
|
|
22
22
|
|
|
23
23
|
|
|
24
24
|
|