Hide Forgot
Description of problem: SSL initialization messages reported when restarting directory server instances. Version-Release number of selected component (if applicable): 389-ds-base-1.2.11.15-85 How reproducible: Consistently Steps to Reproduce: 1. Install latest 389-ds-base on RHEL-6.9 and configure SSL. 2. Restart directory server instances 3. SSL initialization messages reported. Actual results: [root@auto-hv-02-guest09 ~]# /usr/sbin/restart-dirsrv Starting instance "Inst1" [01/Dec/2016:09:44:17 -0500] SSL Initialization - Configured SSL version range: min: TLS1.0, max: TLS1.2 Restarting instance "Inst2" [01/Dec/2016:09:44:20 -0500] SSL Initialization - Configured SSL version range: min: TLS1.0, max: TLS1.2 Expected results: SSL initialization message should not be printed on the command line. Additional info: [root@auto-hv-02-guest09 ~]# rpm -qa |grep -i 389-ds 389-ds-base-devel-1.2.11.15-85.el6.x86_64 389-ds-base-libs-1.2.11.15-85.el6.x86_64 389-ds-base-1.2.11.15-85.el6.x86_64 389-ds-base-debuginfo-1.2.11.15-85.el6.x86_64
After further testing it has been determined that this issue is specific to RHEL 6.x. This behaviour is not present in any of the RHEL 7.x releases.
(In reply to mreynolds from comment #4) > After further testing it has been determined that this issue is specific to > RHEL 6.x. This behaviour is not present in any of the RHEL 7.x releases. I don't remember seeing this issue with RHEL-6.8 builds. If needed, I will retest it on RHEL-6.8z and share the outcome.
(In reply to Sankar Ramalingam from comment #5) > (In reply to mreynolds from comment #4) > > After further testing it has been determined that this issue is specific to > > RHEL 6.x. This behaviour is not present in any of the RHEL 7.x releases. > > I don't remember seeing this issue with RHEL-6.8 builds. If needed, I will > retest it on RHEL-6.8z and share the outcome. I don't think that particular "logging code" existed in 6.8. On a side note - even though the that logging line is printed to stderr, it is still going into the errors log. So the message is not being lost. Like I said I don't think this logging existed in 6.8, but if it does exist in 6.8 then you should still see it in the 6.8 errors log("Configured SSL version range"). If it's not displayed in stderr or the errors log, then that logging code does not exist in 6.8 However, the current consensus in the team is that this is not going to be fixed since it's working in the most current release of the server(rhel 7.x), and rhel 6.x is reaching its EOL in the next 6 months.
(In reply to mreynolds from comment #6) > (In reply to Sankar Ramalingam from comment #5) > > (In reply to mreynolds from comment #4) > > > After further testing it has been determined that this issue is specific to > > > RHEL 6.x. This behaviour is not present in any of the RHEL 7.x releases. > > > > I don't remember seeing this issue with RHEL-6.8 builds. If needed, I will > > retest it on RHEL-6.8z and share the outcome. > > I don't think that particular "logging code" existed in 6.8. > > On a side note - even though the that logging line is printed to stderr, it > is still going into the errors log. So the message is not being lost. > True, it goes to the error logs. > Like I said I don't think this logging existed in 6.8, but if it does exist > in 6.8 then you should still see it in the 6.8 errors log("Configured SSL > version range"). If it's not displayed in stderr or the errors log, then > that logging code does not exist in 6.8 > > However, the current consensus in the team is that this is not going to be > fixed since it's working in the most current release of the server(rhel > 7.x), and rhel 6.x is reaching its EOL in the next 6 months. Thanks for clarification.
Closing bug as won't fix