Hi Guys,
Thanks, I found the problem. I had edited the /etc/vdsm logger
config files to cut down on all the debug logging and the process failed
(silently in any system log I could find) due to a parsing error.
Restored the logger files to defaults and it worked.
For anyone going through the list logs in the future, try running:
sudo -s /bin/bash vdsm
python /usr/share/vdsm/vdsm
to get an error message.
On 16-04-13 09:46 AM, Martin Sivak wrote:
Hi Charles,
can you please make sure you are not in local maintenance mode and the
vdsmd systemd service is enabled?
The line
Apr 13 07:57:09 ovirt-01 ovirt-ha-agent:
ERROR:ovirt_hosted_engine_ha.agent.agent.Agent:Service vdsmd is not running and
the admin is responsible for starting it. Waiting...
seems to indicate that hosted engine agent refused to start vdsm on
its own and that usually happens when the host is in maintenance.
Regards
--
Martin Sivak
SLA / oVirt
On Wed, Apr 13, 2016 at 2:25 PM, Charles Tassell <ctass...@gmail.com> wrote:
Hi Simon,
I tried that, but the same problem: vdsm won't start, so the deploy can't
continue. There is some sort of bug with running VDSMd, but I can't find
any error logging to say what that bug is so I'm at a loss as to how to fix
it.
On 16-04-13 08:47 AM, Simone Tiraboschi wrote:
[snip] You can run hosted-engine --deploy again and choose to redeploy
using the same host-id: it will reconfigure VDSM for you.
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
