Can you check if there are any errors in the engine volume's mount logs (/var/logs/glusterfs/rrhev-data-center-mnt-glusterSD-<engine volume>.log) On Tue, Apr 16, 2019 at 2:33 PM Stefan Wolf <shb256@gmail.com> wrote:
Sorry i forgot to wrote,
This is everything I got.
No keyboard input
I ve read to mount the harddrive with losetup and use fsck
[root@kvm360 /]# fdisk -lu /mnt/36663740-576a-4498-b28e-0a402628c6a7/images/50d59094-7f24-4fed-9c4e-d3bb6b42eb6a/38252d8a-49fd-474e-a449-d40b3ef4b7dc
Disk /mnt/36663740-576a-4498-b28e-0a402628c6a7/images/50d59094-7f24-4fed-9c4e-d3bb6b42eb6a/38252d8a-49fd-474e-a449-d40b3ef4b7dc: 53.7 GB, 53687091200 bytes, 104857600 sectors
Units = Sektoren of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x000aff89
Gerät boot. Anfang Ende Blöcke Id System
/mnt/36663740-576a-4498-b28e-0a402628c6a7/images/50d59094-7f24-4fed-9c4e-d3bb6b42eb6a/38252d8a-49fd-474e-a449-d40b3ef4b7dc1 * 2048 2099199 1048576 83 Linux
/mnt/36663740-576a-4498-b28e-0a402628c6a7/images/50d59094-7f24-4fed-9c4e-d3bb6b42eb6a/38252d8a-49fd-474e-a449-d40b3ef4b7dc2 2099200 92012543 44956672 8e Linux LVM
/mnt/36663740-576a-4498-b28e-0a402628c6a7/images/50d59094-7f24-4fed-9c4e-d3bb6b42eb6a/38252d8a-49fd-474e-a449-d40b3ef4b7dc3 92012544 104855551 6421504 83 Linux
[root@kvm360 /]# losetup -o 2099200 /dev/loop0 /mnt/36663740-576a-4498-b28e-0a402628c6a7/images/50d59094-7f24-4fed-9c4e-d3bb6b42eb6a/38252d8a-49fd-474e-a449-d40b3ef4b7dc
[root@kvm360 /]# mount /dev/loop0 /test/
mount: /dev/loop0 is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
[root@kvm360 /]#
But I suck on mounting partition
-----Ursprüngliche Nachricht----- Von: Sahina Bose <sabose@redhat.com> Gesendet: Dienstag, 16. April 2019 10:57 An: Stefan Wolf <shb256@gmail.com> Cc: users <users@ovirt.org> Betreff: Re: [ovirt-users] hosted engine does not start
On Tue, Apr 16, 2019 at 1:07 AM Stefan Wolf <shb256@gmail.com> wrote:
Hello all,
after a powerloss the hosted engine won’t start up anymore.
I ‘ve the current ovirt installed.
Storage is glusterfs und it is up and running
It is trying to start up hosted engine but it does not work, but I can’t see where the problem is.
[root@kvm320 ~]# hosted-engine --vm-status
--== Host 1 status ==--
conf_on_shared_storage : True
Status up-to-date : True
Hostname : kvm380.durchhalten.intern
Host ID : 1
Engine status : {"reason": "bad vm status", "health": "bad", "vm": "down", "detail": "Down"}
Score : 1800
stopped : False
Local maintenance : False
crc32 : 3ad6d0bd
local_conf_timestamp : 14594
Host timestamp : 14594
Extra metadata (valid at timestamp):
metadata_parse_version=1
metadata_feature_version=1
timestamp=14594 (Mon Apr 15 21:25:12 2019)
host-id=1
score=1800
vm_conf_refresh_time=14594 (Mon Apr 15 21:25:12 2019)
conf_on_shared_storage=True
maintenance=False
state=GlobalMaintenance
stopped=False
--== Host 2 status ==--
conf_on_shared_storage : True
Status up-to-date : True
Hostname : kvm320.durchhalten.intern
Host ID : 2
Engine status : {"reason": "failed liveliness check", "health": "bad", "vm": "up", "detail": "Up"}
Score : 0
stopped : False
Local maintenance : False
crc32 : e7d4840d
local_conf_timestamp : 21500
Host timestamp : 21500
Extra metadata (valid at timestamp):
metadata_parse_version=1
metadata_feature_version=1
timestamp=21500 (Mon Apr 15 21:25:22 2019)
host-id=2
score=0
vm_conf_refresh_time=21500 (Mon Apr 15 21:25:22 2019)
conf_on_shared_storage=True
maintenance=False
state=ReinitializeFSM
stopped=False
--== Host 3 status ==--
conf_on_shared_storage : True
Status up-to-date : True
Hostname : kvm360.durchhalten.intern
Host ID : 3
Engine status : {"reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"}
Score : 1800
stopped : False
Local maintenance : False
crc32 : cf9221cb
local_conf_timestamp : 22121
Host timestamp : 22120
Extra metadata (valid at timestamp):
metadata_parse_version=1
metadata_feature_version=1
timestamp=22120 (Mon Apr 15 21:25:18 2019)
host-id=3
score=1800
vm_conf_refresh_time=22121 (Mon Apr 15 21:25:18 2019)
conf_on_shared_storage=True
maintenance=False
state=GlobalMaintenance
stopped=False
[root@kvm320 ~]# virsh -r list
Id Name Status
----------------------------------------------------
6 HostedEngine laufend
[root@kvm320 ~]# hosted-engine --console
The engine VM is running on this host
Verbunden mit der Domain: HostedEngine
Escape-Zeichen ist ^]
Fehler: Interner Fehler: Zeichengerät <null> kann nicht gefunden
warden
In engish it should be this
[root@mgmt~]# hosted-engine --console
The engine VM is running on this host
Connected to domain HostedEngine
Escape character is ^]
error: internal error: cannot find character device
This is in the log
[root@kvm320 ~]# tail -f /var/log/ovirt-hosted-engine-ha/agent.log
MainThread::INFO::2019-04-15
21:28:33,032::hosted_engine::491::ovirt_hosted_engine_ha.agent.hosted_
engine.HostedEngine::(_monitoring_loop) Current state EngineStarting
(score: 1800)
MainThread::INFO::2019-04-15 21:28:43,050::states::779::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(consume) VM is powering up..
MainThread::INFO::2019-04-15
21:28:43,165::hosted_engine::491::ovirt_hosted_engine_ha.agent.hosted_
engine.HostedEngine::(_monitoring_loop) Current state EngineStarting
(score: 1800)
MainThread::INFO::2019-04-15 21:28:53,183::states::779::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(consume) VM is powering up..
MainThread::INFO::2019-04-15
21:28:53,300::hosted_engine::491::ovirt_hosted_engine_ha.agent.hosted_
engine.HostedEngine::(_monitoring_loop) Current state EngineStarting
(score: 1800)
MainThread::INFO::2019-04-15 21:29:03,317::states::779::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(consume) VM is powering up..
MainThread::INFO::2019-04-15
21:29:03,434::hosted_engine::491::ovirt_hosted_engine_ha.agent.hosted_
engine.HostedEngine::(_monitoring_loop) Current state EngineStarting
(score: 1800)
MainThread::INFO::2019-04-15 21:29:13,453::states::779::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(consume) VM is powering up..
MainThread::INFO::2019-04-15
21:29:13,571::states::136::ovirt_hosted_engine_ha.agent.hosted_engine.
HostedEngine::(score) Penalizing score by 1600 due to gateway status
MainThread::INFO::2019-04-15
21:29:13,571::hosted_engine::491::ovirt_hosted_engine_ha.agent.hosted_
engine.HostedEngine::(_monitoring_loop) Current state EngineStarting
(score: 1800)
MainThread::INFO::2019-04-15 21:29:22,589::states::779::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(consume) VM is powering up..
MainThread::INFO::2019-04-15
21:29:22,712::hosted_engine::491::ovirt_hosted_engine_ha.agent.hosted_
engine.HostedEngine::(_monitoring_loop) Current state EngineStarting
(score: 1800)
But it is not reachable over the network
[root@kvm320 ~]# ping 192.168.200.211
PING 192.168.200.211 (192.168.200.211) 56(84) bytes of data.
From 192.168.200.231 icmp_seq=1 Destination Host Unreachable
From 192.168.200.231 icmp_seq=2 Destination Host Unreachable
From 192.168.200.231 icmp_seq=3 Destination Host Unreachable
From 192.168.200.231 icmp_seq=4 Destination Host Unreachable
I tried to stop and start the vm again, but it didn’t helped
Maybe someone can give me some advice how to get the hosted engine
running again
Can you access the VNC console of the Hosted Engine VM and check?
Thx by stefan
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org Privacy
Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/7PNLN5C4
X6GRVZZ22KJYBHTLOBLUWS27/
participants (1)
-
Sahina Bose