#1654 Troubleshooting improvements
Closed: Fixed None Opened 8 years ago by edewata.

Sometimes it's difficult to troubleshoot PKI issues because the logs do not provide sufficient information, which could delay the resolution by several days and take away development resources.

There are several things that can be improved:

  • all methods should throw an exception instead of silently ignoring the error or discarding the exception info
  • the exception should include informative error message, and/or chained to the original exception
  • the stack trace should be logged by the top-level method

These changes can be done incrementally in multiple patches.


Per CS/DS Meeting of 10/19/2015: 10.3

Fixed in master:

  • c22d9a99240d2f24eb7b0ee11c3153fa475d47a1
  • 80fa9eefaeaeea94c650400f914b5831f1e28261
  • ca2332dfed7834c2fdcd2fe0c2201d58725388e9
  • 1cdfd17588dc2b83cb12cd11a8e5d86d28577940
  • 5847a485a16471f6c3a2a7552b719df3aec909df
  • 8e291fba835f6640a262e01333aa58cf9bd5220f

Various changes have been done in this ticket and other tickets to help troubleshooting major issues. There will be ongoing improvements in other areas.

Metadata Update from @edewata:
- Issue assigned to edewata
- Issue set to the milestone: 10.3.3

7 years ago

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/2213

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Login to comment on this ticket.

Metadata