Forget about it.
There was a stalled old configuration file which apparently did not work with newer
version.
deleted it and applied the new.
G
On 04/04/17 15:24, Kapetanakis Giannis wrote:
Hi,
Centos 7 (no self hosted).
Trying to upgrade from 4.1.0 to 4.1.1 he setup fails to start
ovirt-engine-notifier.service
● ovirt-engine-notifier.service - oVirt Engine Notifier
Loaded: loaded (/usr/lib/systemd/system/ovirt-engine-notifier.service; enabled; vendor
preset: disabled)
Active: failed (Result: exit-code) since Tue 2017-04-04 15:21:28 EEST; 30s ago
Process: 4489
ExecStart=/usr/share/ovirt-engine/services/ovirt-engine-notifier/ovirt-engine-notifier.py
--redirect-output --systemd=notify $EXTRA_ARGS start (code=exited, status=1/FAILURE)
Main PID: 4489 (code=exited, status=1/FAILURE)
Apr 04 15:21:28 vmgr.cc.uoc.gr ovirt-engine-notifier.py[4489]: stderr: at
org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:198)
Apr 04 15:21:28 vmgr.cc.uoc.gr ovirt-engine-notifier.py[4489]: stderr: at
org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363)
Apr 04 15:21:28 vmgr.cc.uoc.gr ovirt-engine-notifier.py[4489]: stderr: at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351)
Apr 04 15:21:28 vmgr.cc.uoc.gr ovirt-engine-notifier.py[4489]: stderr: at
org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93)
Apr 04 15:21:28 vmgr.cc.uoc.gr ovirt-engine-notifier.py[4489]: stderr: ... 7
more
Apr 04 15:21:28 vmgr.cc.uoc.gr ovirt-engine-notifier.py[4489]: Validation failed
returncode is 1:
Apr 04 15:21:28 vmgr.cc.uoc.gr systemd[1]: ovirt-engine-notifier.service: main process
exited, code=exited, status=1/FAILURE
Apr 04 15:21:28 vmgr.cc.uoc.gr systemd[1]: Failed to start oVirt Engine Notifier.
Apr 04 15:21:28 vmgr.cc.uoc.gr systemd[1]: Unit ovirt-engine-notifier.service entered
failed state.
Apr 04 15:21:28 vmgr.cc.uoc.gr systemd[1]: ovirt-engine-notifier.service failed.
From installation log:
2017-04-04 15:07:48 DEBUG otopi.context context._executeMethod:128 Stage closeup METHOD
otopi.plugins.ovirt_engine_common.base.system.hostile_services.Plugin._closeup
2017-04-04 15:07:48 DEBUG otopi.plugins.otopi.services.systemd systemd.exists:73 check if
service ovirt-engine-notifier exists
2017-04-04 15:07:48 DEBUG otopi.plugins.otopi.services.systemd plugin.executeRaw:813
execute: ('/bin/systemctl', 'show', '-p', 'LoadState',
'ovirt-engine-notifier.service'), executable='None', cwd='None',
env=None
2017-04-04 15:07:48 DEBUG otopi.plugins.otopi.services.systemd plugin.executeRaw:863
execute-result: ('/bin/systemctl', 'show', '-p',
'LoadState', 'ovirt-engine-notifier.service'), rc=0
2017-04-04 15:07:48 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:921
execute-output: ('/bin/systemctl', 'show', '-p',
'LoadState', 'ovirt-engine-notifier.service') stdout:
LoadState=loaded
2017-04-04 15:07:48 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:926
execute-output: ('/bin/systemctl', 'show', '-p',
'LoadState', 'ovirt-engine-notifier.service') stderr:
2017-04-04 15:07:48 DEBUG otopi.plugins.otopi.services.systemd systemd.state:130 starting
service ovirt-engine-notifier
2017-04-04 15:07:48 DEBUG otopi.plugins.otopi.services.systemd plugin.executeRaw:813
execute: ('/bin/systemctl', 'start',
'ovirt-engine-notifier.service'), executable='None', cwd='None',
env=None
2017-04-04 15:07:49 DEBUG otopi.plugins.otopi.services.systemd plugin.executeRaw:863
execute-result: ('/bin/systemctl', 'start',
'ovirt-engine-notifier.service'), rc=1
2017-04-04 15:07:49 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:921
execute-output: ('/bin/systemctl', 'start',
'ovirt-engine-notifier.service') stdout:
2017-04-04 15:07:48 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:926
execute-output: ('/bin/systemctl', 'show', '-p',
'LoadState', 'ovirt-engine-notifier.service') stderr:
2017-04-04 15:07:48 DEBUG otopi.plugins.otopi.services.systemd systemd.state:130 starting
service ovirt-engine-notifier
2017-04-04 15:07:48 DEBUG otopi.plugins.otopi.services.systemd plugin.executeRaw:813
execute: ('/bin/systemctl', 'start',
'ovirt-engine-notifier.service'), executable='None', cwd='None',
env=None
2017-04-04 15:07:49 DEBUG otopi.plugins.otopi.services.systemd plugin.executeRaw:863
execute-result: ('/bin/systemctl', 'start',
'ovirt-engine-notifier.service'), rc=1
2017-04-04 15:07:49 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:921
execute-output: ('/bin/systemctl', 'start',
'ovirt-engine-notifier.service') stdout:
2017-04-04 15:07:49 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:926
execute-output: ('/bin/systemctl', 'start',
'ovirt-engine-notifier.service') stderr:
Job for ovirt-engine-notifier.service failed because the control process exited with
error code. See "systemctl status ovirt-engine-notifier.service" and
"journalctl -xe" for details.
2017-04-04 15:07:49 DEBUG otopi.context context._executeMethod:142 method exception
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132, in
_executeMethod
method['method']()
File
"/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-common/base/system/hostile_services.py",
line 104, in _closeup
state=True
File "/usr/share/otopi/plugins/otopi/services/systemd.py", line 141, in
state
service=name,
RuntimeError: Failed to start service 'ovirt-engine-notifier'
2017-04-04 15:07:49 ERROR otopi.context context._executeMethod:151 Failed to execute
stage 'Closing up': Failed to start service 'ovirt-engine-notifier'
G