Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
"the server crashed" means the server does not restart, right? And the cause is clear in the error log.
I agree it'd be nice if the Console could reject the cache size larger than available memory size. But there is no such ldap query that Console could send to the server to get the available memory size. Also, please note that the direct local query to the OS/system is not good enough since Console should be able to manage remote servers.
I'd think the server not restarting due to the too large cache size is the second best solution...
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHSA-2015-0416.html
Description of problem: if nsslapd-cachememsize set to the number larger than the RAM available, should result in proper error message. Steps to Reproduce: I tried giving a higher value of 1000GB to dn: cn=userRoot,cn=ldbm database,cn=plugins,cn=config's nsslapd-cachememsize from console, and the server crashed. Error :: >>> ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1) >>> < - deleted >>> > - added >>> 1,28d0 >>> < # extended LDIF >>> < # >>> < # LDAPv3 >>> < # base <cn=userRoot,cn=ldbm database,cn=plugins,cn=config> with >>> scope baseObject >>> < # filter: objectclass=* >>> < # requesting: ALL >>> < # >>> < >>> < # userRoot, ldbm database, plugins, config >>> < dn: cn=userRoot,cn=ldbm database,cn=plugins,cn=config >>> < objectClass: top >>> < objectClass: extensibleObject >>> < objectClass: nsBackendInstance >>> < cn: userRoot >>> < nsslapd-suffix: dc=example,dc=com >>> < nsslapd-cachesize: -1 >>> < nsslapd-cachememsize: 1073741824 >>> < nsslapd-readonly: off >>> < nsslapd-require-index: off >>> < nsslapd-directory: /var/lib/dirsrv/slapd-mgmt12/db/userRoot >>> < nsslapd-dncachememsize: 10485760 >>> < >>> < # search result >>> < search: 2 >>> < result: 0 Success >>> < >>> < # numResponses: 2 >>> < # numEntries: 1 >>> >>> ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1) >>> >>> >>> [root@mgmt12 scripts]# service dirsrv status >>> dirsrv mgmt12 dead but pid file exists >>> >>> [root@mgmt12 scripts]# tail -f /var/log/dirsrv/slapd-mgmt12/errors >>> [19/Mar/2013:07:22:31 -0400] memory allocator - calloc of 1 elems of >>> 268435664 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). >>> >>> >>> [root@mgmt12 scripts]# cat /proc/meminfo >>> MemTotal: 16396852 kB >>> MemFree: 13973916 kB >>> Buffers: 211892 kB >>> Cached: 1460572 kB >>> SwapCached: 0 kB >>> >>> #free -m >>> total used free shared buffers >>> cached >>> Mem: 16012 2366 13646 0 206 >>> 1426 >>> -/+ buffers/cache: 732 15279 >>> Swap: 8071 0 8071 >>> ===>>>It says "Can't contact LDAP server" ..we should display a better error message on console? Actual results: Error message says :: "Can't contact LDAP server" Expected results: we should display a better error message on console which indicates that RAM is not enough.