2:42 p.m.
Hi at all,
we cannot access our hosted engine anymore. It started with and overfull
/var due to a growing database. We access the engine via SSH and tried
to fix that - but somehow we seem to have produced another problem on
the SSH server itself. So unfortunately we can not login anymore.
We then tried to access it via its host and a "hosted-engine --console"
but ran into an
internal error: cannot find character device <null>
which I know from KVM. With other VMs I could follow the RedHat's advice
to add a console
(https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/...)
but although I edited the hosted engine's profile those changes weren't
applied - and after an engine restart even deleted again. That kind of
makes sense to me, but limits my options.
So my question is: Is there any idea how can I access the the console
with my current limitations to fix the SSH server's problems and then
hopefully fix everything?
Regards
Daniel
3:11 p.m.
On Fri, Aug 24, 2018 at 2:04 PM Daniel Menzel <
daniel.menzel(a)hhi.fraunhofer.de> wrote:
We then tried to access it via its host and a "hosted-engine
--console"
but ran into an
internal error: cannot find character device <null>
which I know from KVM. With other VMs I could follow the RedHat's advice
to add a console
(
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/...)
but although I edited the hosted engine's profile those changes weren't
applied - and after an engine restart even deleted again. That kind of
makes sense to me, but limits my options.
Please see this: https://bugzilla.redhat.com/show_bug.cgi?id=1590943
with engine 4.2.5-1 you can definitively enable the serial console device
editing the engine VM from the engine itself.
If you are not able to reach the engine VM for the upgrade, you can
copy /var/run/ovirt-hosted-engine-ha/vm.conf somewhere, edit it to add the
console device and restart the hosted-engine VM with a custom vm.conf with
something like:
hosted-engine --vm-shutdown --vm-conf=/root/my_vm.conf
As an alternative, VNC console should work as well; you can set VNC
password with
hosted-engine --add-console-password
4:03 p.m.
Hello Simone,
thanks for your reply.
hosted-engine --vm-shutdown --vm-conf=/root/my_vm.conf
I came across that before but the syntax of this file is nebulous to me
as it looks like some kind of JSON?! How do I add the serial console
there? What's the syntax?
As an alternative, VNC console should work as well; you can set VNC
password with
hosted-engine --add-console-password
I have tried this, too. The result was the following:
Command VM.updateDevice with args {'params': {'existingConnAction':
'keep', 'graphicsType': 'vnc', 'params': {},
'ttl': '120', 'deviceType':
'graphics', 'password': '<mypwd>'}, 'vmID':
'<vmid>'} failed:
(code=56, message=Failed to update device)
4:07 p.m.
On Fri, Aug 24, 2018 at 3:00 PM Daniel Menzel <
daniel.menzel(a)hhi.fraunhofer.de> wrote:
Hello Simone,
thanks for your reply.
> hosted-engine --vm-shutdown --vm-conf=/root/my_vm.conf
I came across that before but the syntax of this file is nebulous to me
as it looks like some kind of JSON?! How do I add the serial console
there? What's the syntax?
something adding like this should be enough:
devices={device:console,type:console,deviceId:816e131e-5718-45e7-b1e3-81a6dfd51e19,address:None}
and please remove xmlBase64= line if there since it contains the XML for
libvirt as generated by the engine and that one, if there, wins over the
dictionary for vdsm.
> As an alternative, VNC console should work as well; you can set VNC
> password with
> hosted-engine --add-console-password
I have tried this, too. The result was the following:
Command VM.updateDevice with args {'params': {'existingConnAction':
'keep', 'graphicsType': 'vnc', 'params': {},
'ttl': '120', 'deviceType':
'graphics', 'password': '<mypwd>'}, 'vmID':
'<vmid>'} failed:
(code=56, message=Failed to update device)
This sounds really weird.
4:36 p.m.
Hi Simone,
it worked - I can access the server via SSH again to solve the original
problem (which is an httpd problem). Concerning the add-console-password
problem: It sounds weird to me, too.
For others: In my case the console device was there, it just did not
have any ID or address:
devices={device:console,type:console}
Regards
Daniel
> something adding like this should be enough:
>
devices={device:console,type:console,deviceId:816e131e-5718-45e7-b1e3-81a6dfd51e19,address:None}
>
> and please remove xmlBase64= line if there since it contains the XML for
> libvirt as generated by the engine and that one, if there, wins over the
> dictionary for vdsm.
>
>
> > As an alternative, VNC console should work as well; you can set VNC
> > password with
> > hosted-engine --add-console-password
>
> I have tried this, too. The result was the following:
>
> Command VM.updateDevice with args {'params':
{'existingConnAction':
> 'keep', 'graphicsType': 'vnc', 'params': {},
'ttl': '120',
> 'deviceType':
> 'graphics', 'password': '<mypwd>'}, 'vmID':
'<vmid>'} failed:
>
>
> (code=56, message=Failed to update device)
>
>
> This sounds really weird.
2282
days inactive
2282
days old
4 comments
2 participants
participants (2)
-
Daniel Menzel -
Simone Tiraboschi