Il 04/11/2013 17:17, Bob Doolittle ha scritto:
On 11/04/2013 05:43 AM, Sandro Bonazzola wrote:
Il 02/11/2013 17:51, Bob Doolittle ha scritto:
Hi,
I'm setting up Engine for the 2nd time - the first time I answered a configuration question wrong. So I did:
engine-setup engine-cleanup engine-setup
Things worked, until I rebooted the system. I found that postgresql would not startup, and was failing with "could not create shared memory segment: Invalid Argument".
I resolved this issue by creating a file /etc/sysctl.d/10-shmmax.conf, containing the line: kernel.shmmax = 1000000000
(I read somewhere that postgresql recommends setting shmmax to 1/4 of physical memory, and I have 4GB)
1. Is this a known bug? If not, should I file one? If so, how do I do that? :) Which version are you installing?
3.3, on Fedora 19.
Can you please attach all 3 logs from above sequence (setup, cleanup, setup)? I think something may have gone wrong on second setup execution while setting shmmax.
Unfortunately I no longer have those logs.
*However* last night I powered down my node and engine. Last night engine would at least come up.
Now when I boot up my engine I get the same error. So my guess is that the shmmax setting isn't being configured in a persistent fashion somehow, or is somehow reverting.
My most recent setup log is here (I hate to send large logs to lists): https://dl.dropboxusercontent.com/u/35965416/ovirt-engine-setup-201311031416...
2013-11-03 14:18:18 DEBUG otopi.plugins.ovirt_engine_setup.system.sysctl plugin.execute:441 execute-output: ('/sbin/sysctl', '-n', 'kernel.shmmax') stdout: 35554432 setup detected that your shmmax is already configured with a good value so it didn't change the configuration. If you set above value before running setup, please retry running setup without setting it or setting it to a value less than 35554432. setup will detect it's too low and will create needed configuration files for fixing it.
-Bob
2. Is there a better fix than the one I settled on? Does the normal configuration wind up increasing shmmax, or reducing postgresql's limits? What are the default values for this in a normal engine configuration? No better fix, engine-setup just do something like that, setting shmmax to 35554432.
Thanks, Bob
_______________________________________________ Users mailing list Users@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