[Users] ovirt 3.4 beta on F19: engine-setup error "Failed to execute stage 'Misc configuration': Command '/bin/systemctl' failed to execute"
3:01 p.m.
Hi,
Installing a fresh fedora 19 minimal install and ovirt 3.4 beta got me
stuck again. Maybe we should do a bit more QA before releasing a beta?
--== CONFIGURATION PREVIEW ==--
Engine database name : engine
Engine database secured connection : False
Engine database host : localhost
Engine database user name : engine
Engine database host name validation : False
Engine database port : 5432
NFS setup : True
PKI organization : xxxxx.xxx
Application mode : both
Firewall manager : firewalld
Update Firewall : True
Configure WebSocket Proxy : True
Host FQDN : xxxx.xxxxx.xxxxx
NFS export ACL : 0.0.0.0/0.0.0.0(rw)
NFS mount point : /var/lib/exports/iso
Datacenter storage type : posixfs
Configure local Engine database : True
Set application as default page : True
Configure Apache SSL : True
Please confirm installation settings (OK, Cancel) [OK]:
[ INFO ] Stage: Transaction setup
[ INFO ] Stopping engine service
[ INFO ] Stopping websocket-proxy service
[ INFO ] Stage: Misc configuration
[ INFO ] Stage: Package installation
[ INFO ] Stage: Misc configuration
[ INFO ] Initializing PostgreSQL
[ INFO ] Creating PostgreSQL 'engine' database
[ INFO ] Configuring PostgreSQL
[ ERROR ] Failed to execute stage 'Misc configuration': Command
'/bin/systemctl' failed to execute
[ INFO ] Yum Performing yum transaction rollback
[ INFO ] Stage: Clean up
Log file is located
at /var/log/ovirt-engine/setup/ovirt-engine-setup-20140123145115.log
[ INFO ] Stage: Pre-termination
[ INFO ] Stage: Termination
[ ERROR ] Execution of setup failed
2014-01-23 14:52:35 DEBUG otopi.plugins.otopi.services.systemd
systemd.state:134 starting service postgresql
2014-01-23 14:52:35 DEBUG otopi.plugins.otopi.services.systemd
plugin.executeRaw:366 execute: ('/bin/systemctl', 'start',
'postgresql.service'), executable='None', cwd='None', env=None
2014-01-23 14:52:40 DEBUG otopi.plugins.otopi.services.systemd
plugin.executeRaw:383 execute-result: ('/bin/systemctl', 'start',
'postgresql.service'), rc=1
2014-01-23 14:52:40 DEBUG otopi.plugins.otopi.services.systemd
plugin.execute:441 execute-output: ('/bin/systemctl', 'start',
'postgresql.service') stdout:
2014-01-23 14:52:40 DEBUG otopi.plugins.otopi.services.systemd
plugin.execute:446 execute-output: ('/bin/systemctl', 'start',
'postgresql.service') stderr:
Job for postgresql.service failed. See 'systemctl status
postgresql.service' and 'journalctl -xn' for details.
2014-01-23 14:52:40 DEBUG otopi.context context._executeMethod:152
method exception
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/otopi/context.py", line 142, in
_executeMethod
method['method']()
File
"/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/provisioning/postgres.py",
line 182, in _misc
self._provisioning.provision()
File "/usr/share/ovirt-engine/setup/ovirt_engine_setup/postgres.py",
line 552, in provision
self._restart()
File "/usr/share/ovirt-engine/setup/ovirt_engine_setup/postgres.py",
line 407, in _restart
state=state,
File "/usr/share/otopi/plugins/otopi/services/systemd.py", line 138,
in state
'start' if state else 'stop'
File "/usr/share/otopi/plugins/otopi/services/systemd.py", line 77, in
_executeServiceCommand
raiseOnError=raiseOnError
File "/usr/lib/python2.7/site-packages/otopi/plugin.py", line 451, in
execute
command=args[0],
RuntimeError: Command '/bin/systemctl' failed to execute
2014-01-23 14:52:40 ERROR otopi.context context._executeMethod:161
Failed to execute stage 'Misc configuration': Command '/bin/systemctl'
failed to execute
2014-01-23 14:52:40 DEBUG otopi.transaction transaction.abort:131
aborting 'Yum Transaction'
2014-01-23 14:52:40 INFO otopi.plugins.otopi.packagers.yumpackager
yumpackager.info:92 Yum Performing yum transaction rollback
Loaded plugins: langpacks, refresh-packagekit, versionlock
2014-01-23 14:52:40 DEBUG otopi.transaction transaction.abort:131
aborting 'Database Transaction'
2014-01-23 14:52:40 DEBUG otopi.transaction transaction.abort:131
aborting 'Version Lock Transaction'
2014-01-23 14:52:40 DEBUG otopi.transaction transaction.abort:131
aborting 'Firewalld Transaction'
2014-01-23 14:52:40 DEBUG otopi.transaction transaction.abort:131
aborting 'File transaction for '/etc/sysctl.d/ovirt-engine.conf''
2014-01-23 14:52:40 DEBUG otopi.transaction transaction.abort:131
aborting 'File transaction for
'/etc/firewalld/services/ovirt-postgres.xml''
2014-01-23 14:52:40 DEBUG otopi.transaction transaction.abort:131
aborting 'File transaction for
'/etc/firewalld/services/ovirt-https.xml''
2014-01-23 14:52:40 DEBUG otopi.transaction transaction.abort:131
aborting 'File transaction for
'/etc/firewalld/services/ovirt-websocket-proxy.xml''
2014-01-23 14:52:40 DEBUG otopi.transaction transaction.abort:131
aborting 'File transaction for '/etc/firewalld/services/ovirt-nfs.xml''
2014-01-23 14:52:40 DEBUG otopi.transaction transaction.abort:131
aborting 'File transaction for '/etc/firewalld/services/ovirt-http.xml''
2014-01-23 14:52:40 DEBUG otopi.context context.dumpEnvironment:456
ENVIRONMENT DUMP - BEGIN
2014-01-23 14:52:40 DEBUG otopi.context context.dumpEnvironment:471 ENV
BASE/error=bool:'True'
2014-01-23 14:52:40 DEBUG otopi.context context.dumpEnvironment:473
ENVIRONMENT DUMP - END
2014-01-23 14:52:40 INFO otopi.context context.runSequence:395 Stage:
Clean up
2014-01-23 14:52:40 DEBUG otopi.context context.runSequence:399 STAGE
cleanup
Kind regards,
Jorick Astrego
Netbulae B.V.
3:08 p.m.
------=_Part_7020006_586082306.1390486139701
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Hi,
----- Original Message -----
Hi,
Installing a fresh fedora 19 minimal install and ovirt 3.4 beta got
me stuck
again. Maybe we should do a bit more QA before releasing a beta?
--== CONFIGURATION PREVIEW ==--
2014-01-23 14:52:40 DEBUG otopi.plugins.otopi.services.systemd
plugin.execute:446 execute-output: ('/bin/systemctl', 'start',
'postgresql.service') stderr:
Perhaps it's
http://bugzilla.redhat.com/1039616 ? Mentioned also on
http://www.ovirt.org/OVirt_3.4.0_release_notes#Known_issues .
Best,
--
Didi
------=_Part_7020006_586082306.1390486139701
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit
<html><body><div style="font-family: times new roman, new york, times,
serif; font-size: 12pt; color:
#000000"><div>Hi,</div><div><br></div><hr
id="zwchr"><blockquote style="border-left:2px solid
#1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From:
</b>"Jorick Astrego"
&lt;j.astrego(a)netbulae.eu&gt;<br><b>To: </b>"users"
&lt;users(a)ovirt.org&gt;<br><b>Sent: </b>Thursday, January 23,
2014 4:01:24 PM<br><b>Subject: </b>[Users] ovirt 3.4 beta on F19:
engine-setup error "Failed to execute stage 'Misc configuration': Command
'/bin/systemctl' failed to
execute"<br><div><br></div>
Hi,<br><br>
Installing a fresh fedora 19 minimal install and ovirt 3.4 beta got me stuck again. Maybe
we should do a bit more QA before releasing a beta?<br><br>
--== CONFIGURATION PREVIEW ==--<br><br>
Engine database
name
: engine<br>
Engine database secured connection :
False<br>
Engine database
host
: localhost<br>
Engine database user
name
: engine<br>
Engine database host name validation : False<br>
Engine database
port
: 5432<br>
NFS
setup
: True<br>
PKI
organization
: xxxxx.xxx<br>
Application
mode
: both<br>
Firewall
manager
: firewalld<br>
Update
Firewall
: True<br>
Configure WebSocket
Proxy
: True<br>
Host
FQDN
: xxxx.xxxxx.xxxxx<br>
NFS export
ACL
: 0.0.0.0/0.0.0.0(rw)<br>
NFS mount
point
: /var/lib/exports/iso<br>
Datacenter storage
type
: posixfs<br>
Configure local Engine
database :
True<br>
Set application as default
page :
True<br>
Configure Apache
SSL
: True<br><br>
Please confirm installation settings (OK, Cancel) [OK]: <br>
[ INFO ] Stage: Transaction setup<br>
[ INFO ] Stopping engine service<br>
[ INFO ] Stopping websocket-proxy service<br>
[ INFO ] Stage: Misc configuration<br>
[ INFO ] Stage: Package installation<br>
[ INFO ] Stage: Misc configuration<br>
[ INFO ] Initializing PostgreSQL<br>
[ INFO ] Creating PostgreSQL 'engine' database<br>
[ INFO ] Configuring PostgreSQL<br><b>[ ERROR ] Failed to execute
stage 'Misc configuration': Command '/bin/systemctl' failed to
execute</b><br>
[ INFO ] Yum Performing yum transaction rollback<br>
[ INFO ] Stage: Clean up<br>
Log file is located at
/var/log/ovirt-engine/setup/ovirt-engine-setup-20140123145115.log<br>
[ INFO ] Stage: Pre-termination<br>
[ INFO ] Stage: Termination<br>
[ ERROR ] Execution of setup failed<br><br>
2014-01-23 14:52:35 DEBUG otopi.plugins.otopi.services.systemd systemd.state:134 starting
service postgresql<br>
2014-01-23 14:52:35 DEBUG otopi.plugins.otopi.services.systemd plugin.executeRaw:366
execute: ('/bin/systemctl', 'start', 'postgresql.service'),
executable='None', cwd='None', env=None<br>
2014-01-23 14:52:40 DEBUG otopi.plugins.otopi.services.systemd plugin.executeRaw:383
execute-result: ('/bin/systemctl', 'start', 'postgresql.service'),
rc=1<br>
2014-01-23 14:52:40 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:441
execute-output: ('/bin/systemctl', 'start', 'postgresql.service')
stdout:<br><br><br>
2014-01-23 14:52:40 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:446
execute-output: ('/bin/systemctl', 'start', 'postgresql.service')
stderr:</blockquote><div><br></div><div>Perhaps
it's <a
href="http://bugzilla.redhat.com/1039616">http://bugzilla.re...
Mentioned also on</div><div><a
href="http://www.ovirt.org/OVirt_3.4.0_release_notes#Known_issues"
data-mce-href="http://www.ovirt.org/OVirt_3.4.0_release_notes#Known_...
style="font-size:
12pt;">-- </span></div><div><span
name="x"></span>Didi<span
name="x"></span><br></div><div><br></div></div></body></html>
------=_Part_7020006_586082306.1390486139701--
4:07 p.m.
On Thu, Jan 23, 2014 at 3:21 PM, Jorick Astrego wrote:
hello,
is it correct to say that if I put something like this in my
/etc/sysctl.d/ovirt-engine.conf
# cat /etc/sysctl.d/ovirt-engine.conf
# ovirt-engine configuration.
# Put 200Mb 15/01/14
kernel.shmmax = 209715200
And then
# systemctl stop ovirt-engine
# systemctl stop postgresql
# sysctl -p
# sysctl -a --system | grep shmmax
(to verify new settings)
# systemctl start postgresql
# systemctl start ovirt-engine
Then I can run engine-setup without need of putting the env variable any more?
At least it worked from me for upgrade to 3.3.3beta1 and 3.3.3rc
Gianluca
4:56 p.m.
Il 23/01/2014 16:07, Gianluca Cecchi ha scritto:
if you're on x86_64 you can set it to 68719476736.
I've asked kernel peoples and they said that arch limit is a safe value.
However, I'm going to have it fixed for 3.3.3 GA and 3.4.0 GA by engine-setup.
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
4068
days inactive
4068
days old
4 comments
4 participants
participants (4)
-
Gianluca Cecchi -
Jorick Astrego -
Sandro Bonazzola -
Yedidyah Bar David