-
Notifications
You must be signed in to change notification settings - Fork 647
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
security/acme-client: logfile is scrambled in the GUI #69
Comments
|
squid has a similar issue. the regex is fixed for BSD, not per daemon. |
|
@fraenki It may be the hardcore solution for your log but you can look at the log viewer of the |
|
I can test opnsense/core@11f359c on top of 17.7.1 if you like me to... |
|
@Woi all help is welcome: ... but I think you know this :) Cheers, |
|
Looks nice now 👍 |
|
Thank you, Marco. We'll land this in 17.7.2 then :) |
|
Reporting #243, I stumbled about this bad looking line breaks in the date column, if a long log message exists: |
|
This can't be fixed. It writes a proper entry per line. It's the header dump that makes this awkward. 😊 |
We'll change acme.sh's default log level in the next release (#254). This will finally fix this issue :) |
|
@fraenki nice, thanks! |
PR: opnsense/plugins#69 (cherry picked from commit 11f359c)
|
it's not broken, literal newlines in log messages from the particular service are, er, silly... |
|
Whatever, it looks broken ;) |
|
ps: did you reboot? the services don't auto-restart |
|
Ah, no, I haven't. Will try that tonight. |
|
@StrikerTwo The fix changes the log setting of acme.sh, that's why it will only fix new log entries. Maybe clear the log and try again. |
|
Ah, I see. I have rebooted the box and generated some new entries in the LE log and it looks better now. Thanks! |


@fichtner: The logfile looks distorted in the GUI right now. Do you have some advise how I might fix this? :)
The text was updated successfully, but these errors were encountered: