Today I updated one of my three servers again, including the versions of RPMs listed in the subject line above. The ipa-server-upgrade failed again without patching ipautil.py and ipa-replica-conncheck to fix the problem of waiting on tomcat for I suppose an IPv6 port that will never happen? I'm not sure, but there's been enough IPv4-only breaking things that I'm almost used to those.
When I rebooted the machine, however, nothing came up. The logs contained this bit:
Sep 7 13:35:31 auth ns-slapd: [07/Sep/2017:13:35:31.847507616 -0400] - INFO - main - 389-Directory/1.3.6.1 B2017.248.1842 starting up Sep 7 13:35:32 auth ns-slapd: [07/Sep/2017:13:35:32.158108855 -0400] - ERR - ldbm_config_dbcachesize_set - nsslapd-dbcachesize value is too large. Sep 7 13:35:32 auth ns-slapd: [07/Sep/2017:13:35:32.180891884 -0400] - ERR - parse_ldbm_config_entry - Error with config attribute nsslapd-dbcachesize : Error: nsslapd-dbcachesize value is too large. Sep 7 13:35:32 auth ns-slapd: [07/Sep/2017:13:35:32.202852469 -0400] - ERR - ldbm_config_load_dse_info - Error parsing the ldbm config DSE Sep 7 13:35:32 auth ns-slapd: [07/Sep/2017:13:35:32.223902244 -0400] - ERR - ldbm_back_start - Loading database configuration failed Sep 7 13:35:32 auth ns-slapd: [07/Sep/2017:13:35:32.248975920 -0400] - ERR - plugin_dependency_startall - Failed to start database plugin ldbm database
Interestingly, if I manually run 'ipactl start', then it will start ds-389 successfully and everything seems to work:
Sep 7 13:32:31 auth ns-slapd: [07/Sep/2017:13:32:31.598213558 -0400] - INFO - main - 389-Directory/1.3.6.1 B2017.248.1842 starting up Sep 7 13:32:31 auth ns-slapd: [07/Sep/2017:13:32:31.612870058 -0400] - INFO - ldbm_instance_config_cachememsize_set - force a minimal value 512000 Sep 7 13:32:31 auth ns-slapd: [07/Sep/2017:13:32:31.617381627 -0400] - WARN - default_mr_indexer_create - Plugin [caseIgnoreIA5Match] does not handle caseExactIA5Match Sep 7 13:32:31 auth ns-slapd: [07/Sep/2017:13:32:31.622605528 -0400] - INFO - ldbm_instance_config_cachememsize_set - force a minimal value 512000 Sep 7 13:32:31 auth ns-slapd: [07/Sep/2017:13:32:31.629501131 -0400] - INFO - ldbm_instance_config_cachememsize_set - force a minimal value 512000 Sep 7 13:32:31 auth ns-slapd: [07/Sep/2017:13:32:31.637443337 -0400] - NOTICE - ldbm_back_start - found 1879636k physical memory Sep 7 13:32:31 auth ns-slapd: [07/Sep/2017:13:32:31.638504556 -0400] - NOTICE - ldbm_back_start - found 1207892k available Sep 7 13:32:31 auth ns-slapd: [07/Sep/2017:13:32:31.639567173 -0400] - NOTICE - ldbm_back_start - cache autosizing: db cache: 75185k Sep 7 13:32:31 auth ns-slapd: [07/Sep/2017:13:32:31.640797237 -0400] - NOTICE - ldbm_back_start - cache autosizing: userRoot entry cache (3 total): 65536k Sep 7 13:32:31 auth ns-slapd: [07/Sep/2017:13:32:31.643930356 -0400] - NOTICE - ldbm_back_start - cache autosizing: ipaca entry cache (3 total): 65536k Sep 7 13:32:31 auth ns-slapd: [07/Sep/2017:13:32:31.647893792 -0400] - NOTICE - ldbm_back_start - cache autosizing: changelog entry cache (3 total): 65536k Sep 7 13:32:31 auth ns-slapd: [07/Sep/2017:13:32:31.651452253 -0400] - NOTICE - ldbm_back_start - total cache size: 294375784 B;
But if I then reboot the machine, it breaks again (thus why the timestamp of my first block of log messages is newer than the second block). Ideas?
freeipa-users@lists.fedorahosted.org