Version: openfire-4.7.5-1
A clean installation with an LDAP connection. After starting the service and any actions in the web interface, let the /usr/share/openfire/logs/ directory.
After clicking Clear, an empty file /usr/share/openfire/logs/openfire.log appears on the log page, which is not filled in the future.
When Trace Logging is enabled, there is a reaction, but all entries only end up in the journal. how can I fix this bug?
1 Like
What distribution did you use to install Openfire? Typically, logs are saved in <openfire_home>/logs/
You can inspect the file <openfire_home>/lib/log4j2.xml which is what Openfire uses to configure its logging system. Usage of this file is documented here: Log4j – Configuring Log4j 2
Good afternoon, the Red-os distribution version 7.3 was used to install openfire.
I do not know what that is. Which installer did you download from our website?
This version is not available on the site. Program version 4.7.5
Having same issue with openfire.log. Log is here /usr/share/openfire/logs
Stopped logging on 3.7.2024 shortly after install. Last entries:
2024.03.07 14:14:50.721 INFO [PluginMonitorExec-3]: org.jivesoftware.openfire.container.PluginManager - Successfully loaded plugin ‘search-1.7.4’.
2024.03.07 14:14:50.722 INFO [PluginMonitorTask-2]: org.jivesoftware.openfire.container.PluginMonitor - Finished processing all plugins.
2024.03.07 14:14:50.878 INFO [PluginMonitorTask-2]: org.jivesoftware.openfire.spi.ConnectionListener[socket_c2s] - Started.
2024.03.07 14:14:50.906 INFO [PluginMonitorTask-2]: org.jivesoftware.openfire.spi.ConnectionListener[socket_c2s-directTLS] - Started.
2024.03.07 14:14:50.914 INFO [PluginMonitorTask-2]: org.jivesoftware.openfire.spi.ConnectionListener[socket_s2s] - Started.
2024.03.07 14:14:50.945 INFO [PluginMonitorTask-2]: org.jivesoftware.openfire.spi.ConnectionListener[socket_s2s-directTLS] - Started.
2024.03.07 14:14:50.950 INFO [PluginMonitorTask-2]: org.jivesoftware.openfire.spi.ConnectionListener[component] - Started.
2024.03.07 14:14:50.956 INFO [PluginMonitorTask-2]: org.jivesoftware.openfire.spi.ConnectionListener[component-directTLS] - Started.
2024.03.07 14:14:50.960 INFO [PluginMonitorTask-2]: org.jivesoftware.openfire.spi.ConnectionListener[connection_manager] - Started.
2024.03.07 14:14:50.971 INFO [PluginMonitorTask-2]: org.jivesoftware.openfire.spi.ConnectionListener[connection_manager-directTLS] - Started.
2024.03.07 14:14:50.990 INFO [PluginMonitorTask-2]: org.jivesoftware.openfire.spi.EncryptionArtifactFactory - Creating new SslContextFactory instance
2024.03.07 14:14:51.004 INFO [PluginMonitorTask-2]: org.jivesoftware.openfire.http.HttpSessionManager - Starting instance
2024.03.07 14:14:51.031 INFO [PluginMonitorTask-2]: org.jivesoftware.openfire.http.HttpBindManager - HTTP bind service started
Have experienced a few crashes that require reboot to recover.
Unable to see any logging happening. Checked log4j2.xml in /etc/openfire looks correct.
Forgot to mention it is version 4.8.1 recent install ldap ubuntu 22
Thank you,
Jon
Can you guys check if Openfire has ownership of the log file. ls -lh or whatever. if not give the correct permissions to Openfire.
1 Like
When you click on the “Mark” button, a single entry about the index is placed in the log. No entries in /usr/share/openfire/log/openfire.log are added either when the server is restarted, when Trace Logging is enabled, or when parameters are forced to break openfire.xml - right up to the collapse of the service. All DEBUG messages are sent only to the journal. At the same time, INFO messages are also observed in the logs (journald), which also do not fall into openfire.log.
There are no records either when changing to debug in /usr/share/openfire/lib/log4j2.xml with the restart of openfire:
Later, just in case, the following was added to the service startup parameters:
-Dlog4j2.configurationFile=/usr/share/openfire/lib/log4j2.xml
The result has not changed.
Example from the log of the logging system (the trace protocol is enabled):
June 17, 11:55:02 ro7clnt1.reddc.ro7 java[25881]: 11:55:02.779 [ main] I WARN you that org.jivesoftware.util.LocaleUtils - Missing key resource: system_property.xmpp.muc.occupants.clustertask.unblockable in the ru_RU locale.
June 17, 11:55:02 ro7clnt1.reddc.ro7 java[25881]: 11:55:02.780 [ main] DEBUGGING org.jivesoftware.openfire.muc.spi.OccupantManager - creating an instance for the conference service
June 17, 11:55:02 ro7clnt1.reddc.ro7 java[25881]: 11:55:02.780 [ main] TRACE org.jivesoftware.openfire.muc.MultiUserChatManager - … downloaded the MUC conference service from the database.
June 17, 11:55:02 ro7clnt1.reddc.ro7 java[25881]: 11:55:02.780 [ home] DEBUGGING program.jivesoftware.openfire.muc.MultiUserChatManager - Registration of the conference in the MUC service.
June 17, 11:55:02 ro7clnt1.reddc.ro7 java[25881]: 11:55:02.780 [ home] DEBUGGING org.jivesoftware.openfire.component.InternalComponentManager - InternalComponentManager: Registration component for domain: conference
June 17, 11:55:02 ro7clnt1.reddc.ro7 java[25881]: 11:55:02.780 [ home page] Added org tracing.jivesoftware.openfire.spi.LocalRoutingTable - route “conference.of” (for a pair: “{ → conference.of}”)
June 17, 11:55:02 ro7clnt1.reddc.ro7 java[25881]: 11:55:02.795 [ main] TRACKS org.jivesoftware.openfire.muc.MultiUserChatManager is the uploaded service ID for the “conference” of the MUC service
June 17, 11:55:02 ro7clnt1.reddc.ro7 java[25881]: 11:55:02.801 [ home] INFO org.jivesoftware.openfire.muc.spi.MultiUserChatServiceImpl - Changing the downtime schedule of a user task that repeats every 15 months.
June 17, 11:55:02 ro7clnt1.reddc.ro7 java[25881]: 11:55:02.804 [ main] I WARN you that org.jivesoftware.util.LocaleUtils - Missing key resource: system_property.xmpp.muc.vcard.included in the ru_RU locale.
June 17, 11:55:02 ro7clnt1.reddc.ro7 java[25881]: 11:55:02.807 [ home] INFORMATION organization.jivesoftware.openfire.muc.spi.The multi-user service IMPL is one of the largest in the world: conference.
June 17, 11:55:02 ro7clnt1.reddc.ro7 java[25881]: 11:55:02.807 [ home] DEBUGGING org.jivesoftware.openfire.muc.spi.MUCPersistenceManager - Download rooms for the chat service conference.
June 17, 11:55:02 ro7clnt1.reddc.ro7 java[25881]: 11:55:02.810 [ main] TRACKS org.jivesoftware.openfire.muc.MultiUserChatManager is the uploaded service ID for the “conference” of the MUC service