This boils down to "Current runtime state" != "Current configuration", but you are basing configuration decisions on the runtime state. These situations are always thorny to deal with. -Bob On 11/05/2013 10:46 AM, Bob Doolittle wrote:
On 11/05/2013 10:17 AM, Sandro Bonazzola wrote:
the file created by engine-setup is /etc/sysctl.d/ovirt-engine.conf. Note that the file is created by engine-setup only if shmmax is < 35554432 when it's running.
Hmmm, I think this explains the initial problem I saw, after doing setup; cleanup; setup
The first setup will bump up the shmmax. The cleanup will remove ovirt-engine.conf. However if you don't reboot, shmmax remains boosted. The second setup will detect that shmmax is fine, and not create ovirt-engine.conf.
A subsequent reboot will revert shmmax to the default value, and postgresql will fail to come up.
-Bob