You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I changed the tracing and logging configuration, adding a tracer and submitting the form with the "Save & Reload" button. However, the tracer does not get created until the Stalwart service is restarted, making the UI misleading. Same goes for deleting tracers.
How can we reproduce the problem?
I can reproduce the problem by doing the following steps:
Go to Settings > Logging & Tracing
Create a new tracer of any type, with method logfile, and "Save & Reload"
Tail that logfile
Even though the logfile appears to be created immediately, it does not receive any output until stalwart-mail.service is restarted
Version
v0.7.x
What database are you using?
None
What blob storage are you using?
None
Where is your directory located?
None
What operating system are you using?
Linux
Relevant log output
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
(I realize the web UI does not currently support restarting the service in this constellation, but I'd like it to tell me to restart the service manually instead of suggesting that Save & Reload would make a difference.)
What happened?
I changed the tracing and logging configuration, adding a tracer and submitting the form with the "Save & Reload" button. However, the tracer does not get created until the Stalwart service is restarted, making the UI misleading. Same goes for deleting tracers.
How can we reproduce the problem?
I can reproduce the problem by doing the following steps:
logfile
, and "Save & Reload"Version
v0.7.x
What database are you using?
None
What blob storage are you using?
None
Where is your directory located?
None
What operating system are you using?
Linux
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: