In Dogtag 9 the default logging level often times is not sufficient to troubleshoot installation issues:
debug.level=10
To get more logs it has to be changed and the installation has to be rerun:
debug.level=0
If possible, rerunning the installation should be avoided because it will slow down the investigation and it may burden the user.
Possible solutions:
Change the default to debug.level=0 (at least during installation, then change it back to 10). If there is an error, it's not necessary to rerun the installation. However, errors can also be harder to find in a large debug file. Also, in normal situations this will generate unnecessary logs.
Change the code to distinguish error vs debug logs. The installation should stop at the actual error (do not swallow the exception). All errors should be logged regardless of debug level. If the error log is descriptive enough, it could help troubleshooting without having to rerun the installation in debug mode. Note that logging frameworks such as Log4j work like this.
Per Dogtag 10.2.X TRIAGE meeting of 04/28/2015: 9.0.X
This can be done without new deployment parameters: http://pki.fedoraproject.org/wiki/Custom_Installation#Changing_debug_level
Metadata Update from @edewata: - Issue set to the milestone: 10.3.1
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/1911
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Login to comment on this ticket.