Bug 1057011 - Default installation in 4 GiB machine fails because PostgreSQL can't create shared memory
Summary: Default installation in 4 GiB machine fails because PostgreSQL can't create s...
Keywords:
Status: CLOSED DUPLICATE of bug 1039616
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-installer
Version: 3.4
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Sandro Bonazzola
QA Contact: bugs@ovirt.org
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-23 10:39 UTC by Juan Hernández
Modified: 2014-01-23 10:46 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-23 10:46:09 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)

Description Juan Hernández 2014-01-23 10:39:56 UTC
Description of problem:

The basic installation fails with the following error message:

[ ERROR ] Failed to execute stage 'Misc configuration': Command '/bin/systemctl' failed to execute

The system log contains the following:

Jan 23 11:00:22 localhost pg_ctl[2141]: FATAL:  could not create shared memory segment: Invalid argument
Jan 23 11:00:22 localhost pg_ctl[2141]: DETAIL:  Failed system call was shmget(key=5432001, size=43753472, 03600).
Jan 23 11:00:22 localhost pg_ctl[2141]: HINT:  This error usually means that PostgreSQL's request for a shared memory segment exceeded your kernel's SHMMAX parameter.  You can either reduce the request size or reconfigure the kernel with larger SHMMAX.  To reduce the request size (currently 43753472 bytes), reduce PostgreSQL's shared memory usage, perhaps by reducing shared_buffers or max_connections.
Jan 23 11:00:22 localhost pg_ctl[2141]: If the request size is already small, it's possible that it is less than your kernel's SHMMIN parameter, in which case raising the request size or reconfiguring SHMMIN is called for.
Jan 23 11:00:22 localhost pg_ctl[2141]: The PostgreSQL documentation contains more information about shared memory configuration.


Version-Release number of selected component (if applicable):

# rpm -qa 'ovirt-engine-setup*'
ovirt-engine-setup-plugin-websocket-proxy-3.4.0-0.5.beta1.fc19.noarch
ovirt-engine-setup-base-3.4.0-0.5.beta1.fc19.noarch
ovirt-engine-setup-plugin-ovirt-engine-3.4.0-0.5.beta1.fc19.noarch
ovirt-engine-setup-plugin-ovirt-engine-common-3.4.0-0.5.beta1.fc19.noarch

# rpm -q postgresql-server
postgresql-server-9.2.6-1.fc19.x86_64

The /etc/sysctl.conf file and /etc/sysctl.d directory are empty.

How reproducible:

Always.

Steps to Reproduce:

1. Perform a fresh installation of Fedora 19 in a machine with 4 GiB of RAM.
2. Install oVirt Engine.
3. Run engine-setup.

Comment 1 Sandro Bonazzola 2014-01-23 10:46:09 UTC

*** This bug has been marked as a duplicate of bug 1039616 ***


Note You need to log in before you can comment on or make changes to this bug.