Hello,
I have set up 3 hosts for engine, 2 of them are working correct. There is no other host even having broker/agent installed. Is it possible that the error occurs because the hosts are multihomed (Management IP, IP for storage) and can communicate with different IP's ?
hosted-engine --vm-status on both working hosts seems correct: (3 is out of order...)
[root@microcloud21 ~]# hosted-engine --vm-status
--== Host 1 status ==--
conf_on_shared_storage: True
Status up-to-date : True
Hostname: microcloud21.sub.mydomain.de
Host ID : 1
Engine status : {"health": "good", "vm": "up", "detail": "up"}
Score: 3400
stopped: False
Local maintenance : False
crc32: 5941227d
local_conf_timestamp: 152316
Host timestamp : 152302
Extra metadata (valid at timestamp):
metadata_parse_version=1
metadata_feature_version=1
timestamp=152302 (Sat Feb 4 11:49:29 2017)
host-id=1
score=3400
vm_conf_refresh_time=152316 (Sat Feb 4 11:49:43 2017)
conf_on_shared_storage=True
maintenance=False
state=EngineUp
stopped=False
--== Host 2 status ==--
conf_on_shared_storage: True
Status up-to-date : True
Hostname: microcloud24.sub.mydomain.de
Host ID : 2
Engine status : {"reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"}
Score: 3400
stopped: False
Local maintenance : False
crc32: 77e25433
local_conf_timestamp: 157637
Host timestamp : 157623
Extra metadata (valid at timestamp):
metadata_parse_version=1
metadata_feature_version=1
timestamp=157623 (Sat Feb 4 11:49:34 2017)
host-id=2
score=3400
vm_conf_refresh_time=157637 (Sat Feb 4 11:49:48 2017)
conf_on_shared_storage=True
maintenance=False
state=EngineDown
stopped=False
--== Host 3 status ==--
conf_on_shared_storage: True
Status up-to-date : False
Hostname: microcloud27.sub.mydomain.de
Host ID : 3
Engine status : unknown stale-data
Score: 0
stopped: True
Local maintenance : False
crc32: 74798986
local_conf_timestamp: 77946
Host timestamp : 77932
Extra metadata (valid at timestamp):
metadata_parse_version=1
metadata_feature_version=1
timestamp=77932 (Fri Feb 3 15:19:25 2017)
host-id=3
score=0
vm_conf_refresh_time=77946 (Fri Feb 3 15:19:39 2017)
conf_on_shared_storage=True
maintenance=False
state=AgentStopped
stopped=True
Am 03.02.2017 um 19:20 schrieb Simone Tiraboschi:
On Fri, Feb 3, 2017 at 5:22 PM, Ralf Schenk <rs@databay.de> wrote:
Thanks, the issue is here:Hello,
of course:
[root@microcloud27 mnt]# sanlock client status
daemon 8a93c9ea-e242-408c-a63d-a9356bb22df5.microcloud
p -1 helper
p -1 listener
p -1 status
sanlock.log attached. (Beginning 2017-01-27 where everything was fine)
2017-02-02 19:01:22+0100 4848 [1048]: s36 lockspace 7c8deaa8-be02-4aaf-b9b4-ddc8da99ad96:3:/rhev/data- center/mnt/glusterSD/ glusterfs.sub.mydomain.de:_ engine/7c8deaa8-be02-4aaf- b9b4-ddc8da99ad96/dom_md/ids:0 2017-02-02 19:03:42+0100 4988 [12983]: s36 delta_acquire host_id 3 busy1 3 15 13129 7ad427b1-fbb6-4cee-b9ee- 01f596fddfbb.microcloud 2017-02-02 19:03:43+0100 4989 [1048]: s36 add_lockspace fail result -262 Could you please check if you have other hosts contending for the same ID (id=3 in this case).
--
Ralf Schenk
fon +49 (0) 24 05 / 40 83 70
fax +49 (0) 24 05 / 40 83 759
mail rs@databay.de
Databay AG
Jens-Otto-Krag-Straße 11
D-52146 Würselen
www.databay.de
Sitz/Amtsgericht Aachen • HRB:8437 • USt-IdNr.: DE 210844202
Vorstand: Ralf Schenk, Dipl.-Ing. Jens Conze, Aresch Yavari, Dipl.-Kfm. Philipp Hermanns
Aufsichtsratsvorsitzender: Klaus Scholzen (RA)