Hello!
I have two VM (on XenServer) with same /etc/hast.conf:
Hostname master-a have IP 192.168.0.98, hostname master-b have IP 192.168.0.97. Servers visible over ICMP.
Problem - on master always hast as degradated.
My steps to configure HAST:
1. Create /etc/hast.conf on both servers
2.
3.
4. Run on master-a
5. create ZFS volume on master-a
6. on slave run
On master-a in /var/log/messages i see repeated lines:
I not know why master-a (current primary in hast) search secondary at 192.168.0.98, but hats not start.
I have two VM (on XenServer) with same /etc/hast.conf:
Code:
resource test {
on master-a {
local /dev/ada1
remote 192.168.0.98
}
on master-b {
local /dev/ada1
remote 192.168.0.97
}
}Hostname master-a have IP 192.168.0.98, hostname master-b have IP 192.168.0.97. Servers visible over ICMP.
Problem - on master always hast as degradated.
My steps to configure HAST:
1. Create /etc/hast.conf on both servers
2.
service hastd onestart on both servers3.
hastctl create test on both servers4. Run on master-a
hastctl role primary test, and on master-b hastctl role secondary test5. create ZFS volume on master-a
zpool create test /dev/hast/test6. on slave run
zpool import -F , but not nothing imported. Also run zpool import -f test , but not nothing imported.
Code:
root@master-a:~ # hastctl status
Name Status Role Components
test degraded primary /dev/ada1 192.168.0.98
Code:
root@master-b:~ # hastctl status
Name Status Role Components
test - secondary /dev/ada1 192.168.0.97On master-a in /var/log/messages i see repeated lines:
Code:
Jul 25 08:21:33 master-a hastd[542]: [test] (primary) We act as primary for the resource and not as secondary as requested by tcp://192.168.0.98:33567.
Jul 25 08:21:33 master-a hastd[712]: [test] (primary) Remote node acts as primary for the resource and not as secondary.I not know why master-a (current primary in hast) search secondary at 192.168.0.98, but hats not start.
