389-ds-base

#49639 IPA server installation fails in Fedora 28
Closed: wontfix Opened by rcritten.

Closed: wontfix
Reopen Issue

Issue Description

IPA installation fails in a libvirt VM running Fedora 28 beta 1.3 + updates as of April 17. VM is configured with 2GB RAM and has 2GB swap.

[17/Apr/2018:14:14:03.039195451 -0400] - ERR - memory allocator - realloc of 4294967295 bytes failed; OS error 12 (Cannot allocate memory)
The server has probably allocated all available virtual memory. To solve
this problem, make more virtual memory available to your server, or reduce
one or more of the following server configuration settings:
  nsslapd-cachesize        (Database Settings - Maximum entries in cache)
  nsslapd-cachememsize     (Database Settings - Memory available for cache)
  nsslapd-dbcachesize      (LDBM Plug-in Settings - Maximum cache size)
  nsslapd-import-cachesize (LDBM Plug-in Settings - Import cache size).
Can't recover; calling exit(1).

Package Version and Platform

389-ds-base-1.4.0.7-2.fc28.x86_64
freeipa git master 692a9931da326d2de00255c494786f90929843eb

Steps to reproduce

  1. build freeipa
  2. ipa-server-install -a password -p password -r EXAMPLE.TEST --setup-dns

... The error is as it says. You have run out of available memory on your system. Not much we can really do about that. There is a lot you may need to check like:

  • Do you allow vm overcommit?
  • What are the tomcat settings in freeipa?
  • What else is running on your machine?
  • is this 100% reproducable? Or just "random" occurance.

Thanks,

Metadata Update from @firstyear:
- Custom field component adjusted to None
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None

The error says it tried to allocate 4GB of RAM on a nearly empty database.

This is a fresh installation of F-28. using the 1.3 beta iso + dnf fixes + dnf -y update.

Zero tuning is done. It should work out-of-the-box.

I reproduced it twice in a row.

I just ran the Freeipa install twice on a F28 VM with 2 gigs of memory without aby problems.

What part of the install fails for you @rcritten ? Can you also provide the DS errors log from your VM?

Metadata Update from @mreynolds:
- Issue assigned to mreynolds

I was able to reproduce the exact error, but the ipa install completed. Continuing to investigate...

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.4.0

This is triggered by the update to 1.4.0.7 it seems. openQA hit it too.

This is a regression from https://pagure.io/389-ds-base/issue/49618. It only affects master (1.4.0.7).

ea033b6ba..28f69b393 master -> master

0001-Ticket-49639-Crash-when-failing-to-read-from-SASL-co.patch

Metadata Update from @mreynolds:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

@mreynolds I guess you'll do fixed builds for Fedora and update the F28 update? Thanks!

@mreynolds I guess you'll do fixed builds for Fedora and update the F28 update? Thanks!

Of course, I plan to do the builds first thing tomorrow!

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/2698

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: fixed)
Metadata
None
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.