Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#78830 - [openfire] Logging broken
Attached to Project:
Arch Linux
Opened by Polarian (Polarian) - Sunday, 18 June 2023, 22:24 GMT
Last edited by Massimiliano Torromeo (mtorromeo) - Monday, 19 June 2023, 20:47 GMT
Opened by Polarian (Polarian) - Sunday, 18 June 2023, 22:24 GMT
Last edited by Massimiliano Torromeo (mtorromeo) - Monday, 19 June 2023, 20:47 GMT
|
DetailsDescription:
Currently openfire logging does not work, nothing is written to the logfile within the openfire storage directory, or loaded when using the integrated log viewer in the browser. Additional info: * package version(s): 4.7.5-1 * config and/or log files etc: N/A * link to upstream bug report, if any: N/A Steps to reproduce: 1. Install openfire 2. Start openfire 3. Go to the "logs" tab in the web frontend, you will see that the log is "0 K" therefore not containing anything, it should contain the startup logs etc. Fix: I have already found the fix, modify the systemd service to include the following flag within the execution: -Dlog4j.configurationFile=/usr/lib/openfire/log4j2.xml This will fix the logging. |
This task depends upon
Closed by Massimiliano Torromeo (mtorromeo)
Monday, 19 June 2023, 20:47 GMT
Reason for closing: Fixed
Additional comments about closing: openfire-4.7.5-2
Monday, 19 June 2023, 20:47 GMT
Reason for closing: Fixed
Additional comments about closing: openfire-4.7.5-2
https://discourse.igniterealtime.org/t/logs-folder-not-updating/87436/4
I then modified the command line argument using the path to l4g4j2.xml which the PKGBUILD installs it to currently.
Have a good night :)