-
Notifications
You must be signed in to change notification settings - Fork 144
CA: Logging Improvement #2671
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Comment from mharmsen (@mharmsen) at 2016-11-18 00:34:24 Per PKI Bug Council of 11/17/2016: 10.4 - minor |
Comment from gkapoor (@geetikakay) at 2017-02-27 14:10:15 Metadata Update from @geetikakay:
|
Comment from mharmsen (@mharmsen) at 2017-03-03 14:34:20
|
Comment from mharmsen (@mharmsen) at 2017-08-09 16:52:55 Per CS/DS Meeting of August 7, 2017, it was determined to move this issue from 10.4 ==> FUTURE. |
Comment from mharmsen (@mharmsen) at 2017-08-09 16:52:55 Metadata Update from @mharmsen:
|
Comment from mharmsen (@mharmsen) at 2017-08-31 01:41:59 Metadata Update from @mharmsen:
|
Comment from edewata (@edewata) at 2020-02-09 23:13:47 This issue is no longer happening in PKI 10.8. |
Comment from edewata (@edewata) at 2020-02-09 23:13:47 Metadata Update from @edewata:
|
Comment from edewata (@edewata) at 2020-02-09 23:41:22 Metadata Update from @edewata:
|
Comment from edewata (@edewata) at 2020-02-09 23:53:22 Actually, the first scenario is still generating exceptions, but in general there has been a lot of logging improvements in PKI 10.8 so some logging issues may no longer exist or have been handled differently. The second scenario, however, is outside the scope of PKI. If the port is conflicting with another process, Tomcat will fail to start and it will log the reason in the systemd journal. pkispawn can only say that Tomcat fails to start. It's the admin's responsibility to check why Tomcat fails to start (by checking the systemd journal). |
This issue is stale because it has been open 365 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
This issue will be closed for inactivity. If the problem is still present reopen this or create a new issue. |
This issue was migrated from Pagure Issue #2551. Originally filed by gkapoor (@geetikakay) on 2016-11-16 20:15:08:
There are couple of places which needs logging improvement.Because logs might
mislead and are not user friendly.
Steps to Reproduce:
Additional info:
The text was updated successfully, but these errors were encountered: