[Users] ovirt 3.4 beta on F19: engine-setup error "Failed to execute stage 'Misc configuration': Command '/bin/systemctl' failed to execute"

Sandro Bonazzola sbonazzo at redhat.com
Thu Jan 23 10:56:40 EST 2014


Il 23/01/2014 16:07, Gianluca Cecchi ha scritto:
> On Thu, Jan 23, 2014 at 3:21 PM, Jorick Astrego  wrote:
>> Yes that's it:
>>
>> Adding "--otopi-environment="OVESETUP_SYSTEM/shmmax=int:68719476736" "
>> works.
>>
>> I never thought a known issue would crop up so soon, so I just started
>> installing.
>>
>> Thanks
>>
> 
> 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?

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.



> At least it worked from me for upgrade to 3.3.3beta1 and 3.3.3rc
> 
> Gianluca
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 


-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com


More information about the Users mailing list