Skip to content
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

Archiving Admin Console Menu option fails to appear if indexprops.xml is corrupted #412

Open
staples1347 opened this issue Jan 6, 2025 · 0 comments

Comments

@staples1347
Copy link

In version 2.2.1 of the monitoring plugin and possibly newer version if the server crashes , the indexprops.xml files will often reset to 0 byte size and then when the Openfire is restarted, the monitoring plugin will continue to archive messages, but fail to add the Archiving menu option to the admin console. I haven't checked if the menu still fails to appear in the latest version of monitoring , but it looks like the latest version of the loadPropertiesFile function in LuceneIndex.java still doesn't check if XMLProperties has failed.

I think it should check if XMLProperties has failed and possibly recreate the XML file if this is the case as the valid version of the file only contains a lastModified tag.

Here is an example crash log if indexprops.xml is 0 bytes:
2025.01.07 09:35:47 ERROR [pool-4-thread-3]: org.jivesoftware.openfire.archive.ArchiveIndexer[MUCSEARCH] - An exception occurred while initializing the Lucene index that is expected to exist in: /usr/local/openfire-4.6.6/monitoring/mucsearch
java.io.IOException: Error on line 1 of document : Premature end of file.
at org.jivesoftware.util.XMLProperties.buildDoc(XMLProperties.java:744) ~[xmppserver-4.6.6.jar:4.6.6]
at org.jivesoftware.util.XMLProperties.(XMLProperties.java:163) ~[xmppserver-4.6.6.jar:4.6.6]
at org.jivesoftware.util.XMLProperties.(XMLProperties.java:123) ~[xmppserver-4.6.6.jar:4.6.6]
at org.jivesoftware.openfire.index.LuceneIndexer.loadPropertiesFile(LuceneIndexer.java:413) ~[monitoring-2.2.1.jar:?]
at org.jivesoftware.openfire.index.LuceneIndexer.start(LuceneIndexer.java:68) [monitoring-2.2.1.jar:?]
at org.jivesoftware.openfire.plugin.MonitoringPlugin.initializePlugin(MonitoringPlugin.java:203) [monitoring-2.2.1.jar:?]
at org.jivesoftware.openfire.container.PluginManager.loadPlugin(PluginManager.java:683) [xmppserver-4.6.6.jar:4.6.6]
at org.jivesoftware.openfire.container.PluginMonitor$MonitorTask$4.call(PluginMonitor.java:375) [xmppserver-4.6.6.jar:4.6.6]
at org.jivesoftware.openfire.container.PluginMonitor$MonitorTask$4.call(PluginMonitor.java:363) [xmppserver-4.6.6.jar:4.6.6]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
at java.lang.Thread.run(Thread.java:829) [?:?]
2025.01.07 09:35:47 ERROR [pool-4-thread-3]: org.jivesoftware.openfire.container.PluginManager - An exception occurred while loading plugin 'monitoring':
java.lang.NullPointerException: null
at org.jivesoftware.openfire.index.LuceneIndexer.getLastModified(LuceneIndexer.java:143) ~[monitoring-2.2.1.jar:?]
at org.jivesoftware.openfire.index.LuceneIndexer.start(LuceneIndexer.java:124) ~[monitoring-2.2.1.jar:?]
at org.jivesoftware.openfire.plugin.MonitoringPlugin.initializePlugin(MonitoringPlugin.java:203) ~[monitoring-2.2.1.jar:?]
at org.jivesoftware.openfire.container.PluginManager.loadPlugin(PluginManager.java:683) [xmppserver-4.6.6.jar:4.6.6]
at org.jivesoftware.openfire.container.PluginMonitor$MonitorTask$4.call(PluginMonitor.java:375) [xmppserver-4.6.6.jar:4.6.6]
at org.jivesoftware.openfire.container.PluginMonitor$MonitorTask$4.call(PluginMonitor.java:363) [xmppserver-4.6.6.jar:4.6.6]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
at java.lang.Thread.run(Thread.java:829) [?:?]

@staples1347 staples1347 changed the title Admin Console Menu fails to appear if indexprops.xml is zero size Admin Console Menu fails to appear if indexprops.xml is corrupted Jan 6, 2025
@staples1347 staples1347 changed the title Admin Console Menu fails to appear if indexprops.xml is corrupted Archiving Admin Console Menu option fails to appear if indexprops.xml is corrupted Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant