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.
DescriptionJan Pazdziora (Red Hat)
2015-08-27 09:41:00 UTC
Description of problem:
After fresh ipa-server-install, there is file /run/certmonger/.ipa/log/renew.log created. Given /run is mounted as tmpfs, the log file will get lost after reboot.
Version-Release number of selected component (if applicable):
ipa-server-4.2.0-5.el7.x86_64
certmonger-0.78.4-1.el7.x86_64
How reproducible:
Deterministic.
Steps to Reproduce:
1. Install ipa-server, run ipa-server-install.
2. Check /run/certmonger/.ipa/log.
Actual results:
There is /run/certmonger/.ipa/log/renew.log there.
Expected results:
No log file there.
Additional info:
On this particular installation, the log file is actually empty, even if I also saw upstream installation in container which had
2015-08-26T15:32:24Z 94 MainThread ipa.ipalib.session.MemcacheSessionManager WARNING session memcached servers not running
2015-08-26T15:32:24Z 101 MainThread ipa.ipalib.session.MemcacheSessionManager WARNING session memcached servers not running
2015-08-26T15:32:24Z 98 MainThread ipa.ipalib.session.MemcacheSessionManager WARNING session memcached servers not running
2015-08-26T15:32:24Z 96 MainThread ipa.ipalib.session.MemcacheSessionManager WARNING session memcached servers not running
2015-08-26T15:32:24Z 97 MainThread ipa.ipalib.session.MemcacheSessionManager WARNING session memcached servers not running
in it -- pretty important information not to be lost.
the
ipa.ipalib.session.MemcacheSessionManager WARNING session memcached servers not running
is a bug in IPA API initialization.
Honza, could you check the log.
The log file is bogus, it is created automatically by IPA when API is initialized in dogtag-ipa-ca-renew-agent, which logs everything into syslog rather than the log file.
The script is executed by certmonger, which does not have access to memcached, hence the warning. It is not a bug in API initialization, but rather the session manager code.
IdM team doesn't have capacity to fix this bug for RHEL 7.4. Moving to next RHEL version. Fixing the bug there will depend on capacity of FreeIPA upstream. Without sufficient justification there is a chance that it will be moved again later.
The message was removed by not using memcached in FreeIPA 4.4.
Comment 10Jan Pazdziora (Red Hat)
2018-05-21 10:14:35 UTC
I'm sorry but the concern in this bugzilla was not the content of the log file, it was the sole fact that something which serves as log file is not stored where it likely should. I don't think this bugzilla should be CLOSED/CURRENTRELEASE unless the location of that log file has changed, in which case it should likely go through normal QE cycle.