On Fri, Mar 09, 2018 at 07:02:23PM +1000, Fraser Tweedale wrote:
Hi,
It seems that with the change in logging backend, calls to
CMS.debug(Throwable e) no longer print the stack trace. The name of
the exception is printed by the error message has been suppressed.
I couldn't work out why this is happening but in my working tree I'm
carrying the below change to get the stack traces back. Not sure if
it's a "proper" way to fix it but it's doing the trick.
Another thing I just remembered to mention: when the day rolls over
the debug log starts going to stdout/journal(?), instead of a file
with the new date. I have to restart the server to get it logging
to the expected file after the day changes.
Cheers,
Fraser