On Tue, Sep 15, 2015 at 2:31 PM, noc <noc(a)nieuwland.nl> wrote:
On 15-9-2015 9:31, Simone Tiraboschi wrote:
Yes, can you please attach the logs from /var/log/ovirt-hosted-engine-ha/
?
Attached.
Now the agent correctly reads the VM configuration file from the shared
domain so no issue there but then it exits cause VDSM is not up:
MainThread::INFO::2015-09-14
20:48:58,007::hosted_engine::667::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_initialize_storage_images)
Reloading vm.conf from the shared storage domain
MainThread::INFO::2015-09-14
20:48:58,163::hosted_engine::460::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(start_monitoring)
Current state EngineUp (score: 3400)
MainThread::INFO::2015-09-14
20:49:08,201::hosted_engine::610::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_initialize_vdsm)
Initializing VDSM
MainThread::INFO::2015-09-14
20:49:08,317::hosted_engine::655::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_initialize_storage_images)
Connecting the storage
MainThread::INFO::2015-09-14
20:49:08,318::storage_server::110::ovirt_hosted_engine_ha.lib.storage_server.StorageServer::(connect_storage_server)
Connecting storage server
MainThread::INFO::2015-09-14
20:49:08,318::storage_server::135::ovirt_hosted_engine_ha.lib.storage_server.StorageServer::(connect_storage_server)
Connecting storage server
MainThread::INFO::2015-09-14
20:49:08,349::hosted_engine::659::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_initialize_storage_images)
Preparing images
MainThread::INFO::2015-09-14
20:49:08,349::image::61::ovirt_hosted_engine_ha.lib.image.Image::(prepare_images)
Preparing images
MainThread::INFO::2015-09-14
20:49:08,787::hosted_engine::667::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_initialize_storage_images)
Reloading vm.conf from the shared storage domain
MainThread::INFO::2015-09-14
20:49:08,941::hosted_engine::460::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(start_monitoring)
Current state EngineUp (score: 3400)
MainThread::INFO::2015-09-14
20:49:15,104::agent::143::ovirt_hosted_engine_ha.agent.agent.Agent::(run)
Agent shutting down
MainThread::INFO::2015-09-14
21:06:07,601::agent::78::ovirt_hosted_engine_ha.agent.agent.Agent::(run)
ovirt-hosted-engine-ha agent 1.3.0-0.0.master.20150909150500 started
MainThread::INFO::2015-09-14
21:06:07,632::hosted_engine::246::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_get_hostname)
Found certificate common name: lichthuis.puzzle-it.nu
MainThread::INFO::2015-09-14
21:06:07,633::hosted_engine::610::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_initialize_vdsm)
Initializing VDSM
MainThread::ERROR::2015-09-14
21:06:18,209::hosted_engine::418::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(start_monitoring)
Service vdsmd is not running and the admin is responsible for starting it.
Shutting down.
MainThread::INFO::2015-09-14
21:06:18,210::agent::143::ovirt_hosted_engine_ha.agent.agent.Agent::(run)
Agent shutting down
Martin, any hint there?
Previously you had an issue there:
MainThread::ERROR::2015-09-14
17:34:19,972::agent::201::ovirt_hosted_engine_ha.agent.agent.Agent::(_run_agent)
Error: '[Errno 13] Permission denied:
'/var/run/ovirt-hosted-engine-ha/vm.conf'' - trying to restart agent
Did you manually created /var/run/ovirt-hosted-engine-ha/vm.conf being
readable only by root or something similar? ovirt-ha-agent is running as
vdsm user and it should be able to refresh
/var/run/ovirt-hosted-engine-ha/vm.conf with the master copy on the
shared storage.
And previously than that it was failing with:
MainThread::ERROR::2015-09-12
13:53:23,727::agent::201::ovirt_hosted_engine_ha.agent.agent.Agent::(_run_agent)
Error: ''StorageServer' object has no attribute 'storageType'' -
trying to
restart agent
cause you were using ovirt-hosted-engine-ha agent
1.3.0-0.0.master.20150819082341 which was unfortunately bugged on
that. ovirt-hosted-engine-ha agent 1.3.0-0.0.master.20150909150500 you are
using now should be OK.
To me it looks like I better start over but I don't want to wipe my F22
> install. What is the preferred way to get a 'clean' system so that I can
> try again? (concerned about sanlock complaining about name conflicts)
>
I'm quite confident you can save your setup.
Great :-)
Joop
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users