We're updating the issue view to help you get more done. 

Debug log is not saving its state between restarts

Description

Looks like debug log can't be Enabled for good. It gets disabled after a server restart. Also some users report (although they use Linux), that they don't get any logs at all. If i enable it i get a few lines like

2011.06.19 21:58:19 JettyLog: servlet holder=
2011.06.19 21:58:19 JettyLog: chain=
2011.06.19 21:58:19 JettyLog: servlet holder=
2011.06.19 21:58:19 JettyLog: chain=
2011.06.19 21:58:19 JettyLog: servlet holder=
2011.06.19 21:58:19 JettyLog: chain=
2011.06.19 21:58:19 JettyLog: servlet holder=
2011.06.19 21:58:19 JettyLog: chain=

If i then try to chat in my client i get some additional debug lines. But it won't show anything after a restart and Disabled will be marked again.

Environment

Windows

Acceptance Test - Entry

None

Activity

Show:
Daryl Herzmann
October 27, 2014, 6:03 PM

This issue is still valid with current development version. It appears disabling debug from the admin console does not update the openfire.xml setting for debug.

Tom Evans
October 28, 2014, 7:19 PM

Due to the very large size of the debug logs, enabling the debug log (via the admin console) was originally intended to be a transient setting. However, as part of the changes made in we added the ability to enable the debug log permanently via a setting in openfire.xml:

<log><debug><enabled>true</enabled></debug></log>

This setting will persist across restarts.

wroot
October 28, 2014, 7:42 PM

I don't know what the intention was, but i remember it saving the debug log state many years ago. And i was actually able to read the debug log in the Admin Console after the restart.

Tom Evans
October 29, 2014, 8:56 PM

See PR #93.

wroot
October 31, 2014, 5:15 AM
Edited

Yep. Now it saves Enabled state after the restart.

Assignee

Tom Evans

Reporter

wroot

Labels

None

Expected Effort

None

Ignite Forum URL

Components

Fix versions

Affects versions

Priority

Minor
Configure