Problems after converting to 4.7.5

we had Openfire 3.10.2.0 with a built-in database and everything was fine until the database grew to such a volume that 32 versions began to lack memory.
we have updated in several stages to 4.7.5, there are also plugins: Search 1.7.4 and Monitoring Service 2.5.0
and it looks like the database has not been converted correctly, because everything works fine on a clean database, but errors are pouring in on ours.
although the correspondence works fine, but when you launch the client the next day (miranda NG v0.96.3) almost all messages for the last day pop up at once, from everyone I talked to.

Tell me, can this be fixed without clearing the database or how to transfer messages to a clean database?
You can not refuse them, the messages for the last 8 years, we have deleted the rest.

2023.12.06 16:58:56 e[1;31mERRORe[m [main]: org.jivesoftware.openfire.XMPPServer - java.sql.SQLException: ConnectionManager.getConnection() failed to obtain a connection after 11 retries. The exception from the last attempt is as follows: java.sql.SQLException: Database lock acquisition failure: lockFile: org.hsqldb.persist.LockFile@a090bba9[file =C:\Openfire\embedded-db\openfire.lck, exists=true, locked=false, valid=false, ] method: checkHeartbeat read: 2023-12-06 13:58:55 heartbeat - read: -2916 ms.
java.lang.IllegalArgumentException: java.sql.SQLException: ConnectionManager.getConnection() failed to obtain a connection after 11 retries. The exception from the last attempt is as follows: java.sql.SQLException: Database lock acquisition failure: lockFile: org.hsqldb.persist.LockFile@a090bba9[file =C:\Openfire\embedded-db\openfire.lck, exists=true, locked=false, valid=false, ] method: checkHeartbeat read: 2023-12-06 13:58:55 heartbeat - read: -2916 ms.
	at org.jivesoftware.openfire.XMPPServer.verifyDataSource(XMPPServer.java:1062) ~[xmppserver-4.7.5.jar:4.7.5]
	at org.jivesoftware.openfire.XMPPServer.start(XMPPServer.java:706) [xmppserver-4.7.5.jar:4.7.5]
	at org.jivesoftware.openfire.XMPPServer.<init>(XMPPServer.java:255) [xmppserver-4.7.5.jar:4.7.5]
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[?:1.8.0_202]
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) [?:1.8.0_202]
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) [?:1.8.0_202]
	at java.lang.reflect.Constructor.newInstance(Unknown Source) [?:1.8.0_202]
	at java.lang.Class.newInstance(Unknown Source) [?:1.8.0_202]
	at org.jivesoftware.openfire.starter.ServerStarter.start(ServerStarter.java:92) [startup.jar:4.7.5]
	at org.jivesoftware.openfire.starter.ServerStarter.main(ServerStarter.java:56) [startup.jar:4.7.5]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_202]
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_202]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_202]
	at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.8.0_202]
	at com.exe4j.runtime.LauncherEngine.launch(LauncherEngine.java:84) [i4jruntime.jar:?]
	at com.exe4j.runtime.WinLauncher.main(WinLauncher.java:94) [i4jruntime.jar:?]
	at com.install4j.runtime.launcher.WinLauncher.main(WinLauncher.java:25) [i4jruntime.jar:?]
Caused by: java.sql.SQLException: ConnectionManager.getConnection() failed to obtain a connection after 11 retries. The exception from the last attempt is as follows: java.sql.SQLException: Database lock acquisition failure: lockFile: org.hsqldb.persist.LockFile@a090bba9[file =C:\Openfire\embedded-db\openfire.lck, exists=true, locked=false, valid=false, ] method: checkHeartbeat read: 2023-12-06 13:58:55 heartbeat - read: -2916 ms.
	at org.jivesoftware.database.DbConnectionManager.getConnection(DbConnectionManager.java:204) ~[xmppserver-4.7.5.jar:4.7.5]
	at org.jivesoftware.openfire.XMPPServer.verifyDataSource(XMPPServer.java:1052) ~[xmppserver-4.7.5.jar:4.7.5]
	... 16 more
2023.12.06 17:03:25 e[33mWARN e[m [pool-monitoring5766]: org.jivesoftware.openfire.archive.ArchiveIndexer[MUCSEARCH] - Updating (not creating) an index since 'EPOCH'. This is suspicious, as it suggests that an existing, but empty index is being operated on. If the index is non-empty, index duplication might occur.
2023.12.06 17:06:08 e[33mWARN e[m [socket_c2s_ssl-thread-32]: org.jivesoftware.openfire.nio.ConnectionHandler - Closing connection due to exception in session: (0x000002F2: nio socket, server, /10.0.1.141:59407 => 0.0.0.0/0.0.0.0:5223)
java.io.IOException: The remote host forcibly terminated an existing connection
	at sun.nio.ch.SocketDispatcher.read0(Native Method) ~[?:1.8.0_202]
	at sun.nio.ch.SocketDispatcher.read(Unknown Source) ~[?:1.8.0_202]
	at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source) ~[?:1.8.0_202]
	at sun.nio.ch.IOUtil.read(Unknown Source) ~[?:1.8.0_202]
	at sun.nio.ch.SocketChannelImpl.read(Unknown Source) ~[?:1.8.0_202]
	at org.apache.mina.transport.socket.nio.NioProcessor.read(NioProcessor.java:378) ~[mina-core-2.1.3.jar:?]
	at org.apache.mina.transport.socket.nio.NioProcessor.read(NioProcessor.java:47) ~[mina-core-2.1.3.jar:?]
	at org.apache.mina.core.polling.AbstractPollingIoProcessor.read(AbstractPollingIoProcessor.java:519) ~[mina-core-2.1.3.jar:?]
	at org.apache.mina.core.polling.AbstractPollingIoProcessor.access$1200(AbstractPollingIoProcessor.java:68) ~[mina-core-2.1.3.jar:?]
	at org.apache.mina.core.polling.AbstractPollingIoProcessor$Processor.process(AbstractPollingIoProcessor.java:1222) ~[mina-core-2.1.3.jar:?]
	at org.apache.mina.core.polling.AbstractPollingIoProcessor$Processor.process(AbstractPollingIoProcessor.java:1211) ~[mina-core-2.1.3.jar:?]
	at org.apache.mina.core.polling.AbstractPollingIoProcessor$Processor.run(AbstractPollingIoProcessor.java:683) ~[mina-core-2.1.3.jar:?]
	at org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:64) ~[mina-core-2.1.3.jar:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) ~[?:1.8.0_202]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) ~[?:1.8.0_202]
	at java.lang.Thread.run(Unknown Source) [?:1.8.0_202]
2023.12.06 17:08:25 e[33mWARN e[m [pool-monitoring5770]: org.jivesoftware.openfire.archive.ArchiveIndexer[MUCSEARCH] - Updating (not creating) an index since 'EPOCH'. This is suspicious, as it suggests that an existing, but empty index is being operated on. If the index is non-empty, index duplication might occur.
2023.12.06 17:13:25 e[33mWARN e[m [pool-monitoring5773]: org.jivesoftware.openfire.archive.ArchiveIndexer[MUCSEARCH] - Updating (not creating) an index since 'EPOCH'. This is suspicious, as it suggests that an existing, but empty index is being operated on. If the index is non-empty, index duplication might occur.
2023.12.06 17:15:40 e[33mWARN e[m [socket_c2s_ssl-thread-30]: org.jivesoftware.openfire.nio.ConnectionHandler - Closing connection due to exception in session: (0x000002F4: nio socket, server, null => 0.0.0.0/0.0.0.0:5223)
javax.net.ssl.SSLException: Outbound done
	at org.apache.mina.filter.ssl.SslFilter.messageReceived(SslFilter.java:513) [mina-core-2.1.3.jar:?]
	at org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:650) [mina-core-2.1.3.jar:?]
	at org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1300(DefaultIoFilterChain.java:49) [mina-core-2.1.3.jar:?]
	at org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.messageReceived(DefaultIoFilterChain.java:1128) [mina-core-2.1.3.jar:?]
	at org.apache.mina.core.filterchain.IoFilterEvent.fire(IoFilterEvent.java:106) [mina-core-2.1.3.jar:?]
	at org.apache.mina.core.session.IoEvent.run(IoEvent.java:89) [mina-core-2.1.3.jar:?]
	at org.apache.mina.filter.executor.OrderedThreadPoolExecutor$Worker.runTask(OrderedThreadPoolExecutor.java:766) [mina-core-2.1.3.jar:?]
	at org.apache.mina.filter.executor.OrderedThreadPoolExecutor$Worker.runTasks(OrderedThreadPoolExecutor.java:758) [mina-core-2.1.3.jar:?]
	at org.apache.mina.filter.executor.OrderedThreadPoolExecutor$Worker.run(OrderedThreadPoolExecutor.java:697) [mina-core-2.1.3.jar:?]
	at java.lang.Thread.run(Unknown Source) [?:1.8.0_202]

also in the Server\Archiving\Archiving Settings sectio
when trying to rebuild the index, everything stops at 1%

You may be suffering from more than one problem. Let’s first address the problem with the database connectivity, and see how things then.

  1. Shut down Openfire
  2. Delete file C:\Openfire\embedded-db\openfire.lck if it exists.
  3. Start Openfire

after the service was stopped, the openfire.lck file disappeared

errors appeared after the launch:

2023.12.07 10:14:02 INFO [PluginMonitorTask-2]: org.jivesoftware.openfire.container.PluginManager - Successfully loaded plugin 'admin'.
2023.12.07 10:14:02 INFO [PluginMonitorExec-4]: org.jivesoftware.openfire.container.PluginManager - Successfully loaded plugin 'search-1.7.4'.
2023.12.07 10:14:17 INFO [Jetty-QTP-AdminConsole-31]: org.jivesoftware.util.cache.CacheFactory - Created cache [org.jivesoftware.util.cache.DefaultLocalCacheStrategy] for Locked Out Accounts
2023.12.07 10:14:17 INFO [Jetty-QTP-AdminConsole-31]: org.jivesoftware.util.cache.CacheFactory - Created cache [org.jivesoftware.util.cache.DefaultLocalCacheStrategy] for Sequences
2023.12.07 10:14:19 ERROR [pool-monitoring2]: org.jivesoftware.openfire.reporting.stats.RrdSqlBackend - Error while updating information in database: java.sql.SQLDataException: data exception: string data, right truncation
2023.12.07 10:14:19 ERROR [pool-monitoring2]: org.jivesoftware.openfire.reporting.stats.RrdSqlBackend - Error while updating information in database: java.sql.SQLDataException: data exception: string data, right truncation
2023.12.07 10:14:23 INFO [PluginMonitorExec-3]: org.jivesoftware.openfire.archive.ArchiveIndexer[CONVERSATION] - Lucene index is clean.
2023.12.07 10:14:23 INFO [PluginMonitorExec-3]: org.jivesoftware.openfire.archive.ArchiveIndexer[MUCSEARCH] - Lucene index is clean.
2023.12.07 10:14:23 INFO [PluginMonitorExec-3]: org.jivesoftware.openfire.archive.ArchiveIndexer[MUCSEARCH] - Lucene index has never been modified. Removing and rebuilding.
2023.12.07 10:14:27 INFO [PluginMonitorExec-3]: org.jivesoftware.openfire.archive.ArchiveIndexer[MESSAGE] - Lucene index is clean.
2023.12.07 10:14:27 INFO [PluginMonitorExec-3]: org.jivesoftware.openfire.container.PluginManager - Successfully loaded plugin 'monitoring-2.5.0'.
2023.12.07 10:14:27 INFO [PluginMonitorTask-2]: org.jivesoftware.openfire.container.PluginMonitor - Finished processing all plugins.
2023.12.07 10:14:27 INFO [PluginMonitorTask-2]: org.jivesoftware.openfire.spi.ConnectionListener[socket_c2s-legacyMode] - Started.
2023.12.07 10:14:27 WARN [PluginMonitorTask-2]: org.jivesoftware.openfire.spi.LegacyConnectionAcceptor - Configuration allows for up to 16 threads, although implementation is limited to exactly one.
2023.12.07 10:14:27 INFO [PluginMonitorTask-2]: org.jivesoftware.openfire.spi.ConnectionListener[socket_s2s] - Started.
2023.12.07 10:14:27 WARN [PluginMonitorTask-2]: org.jivesoftware.openfire.spi.LegacyConnectionAcceptor - Configuration allows for up to 16 threads, although implementation is limited to exactly one.
2023.12.07 10:14:27 INFO [PluginMonitorTask-2]: org.jivesoftware.openfire.spi.ConnectionListener[socket_s2s-legacyMode] - Started.
2023.12.07 10:15:23 WARN [pool-monitoring2]: org.jivesoftware.openfire.archive.ArchiveIndexer[MUCSEARCH] - Updating (not creating) an index since 'EPOCH'. This is suspicious, as it suggests that an existing, but empty index is being operated on. If the index is non-empty, index duplication might occur.
2023.12.07 10:16:20 INFO [socket_c2s_ssl-thread-3]: org.jivesoftware.util.cache.CacheFactory - Created cache [org.jivesoftware.util.cache.DefaultLocalCacheStrategy] for Remote Server Configurations
2023.12.07 10:16:20 WARN [Server SR - 1017836649]: org.jivesoftware.openfire.net.SocketReader - Closing session due to incorrect hostname in stream header. Host: jabber.tdf.local. Connection: org.jivesoftware.openfire.net.SocketConnection@326d1c54 socket: Socket[addr=/10.0.1.151,port=61101,localport=5269] session: null
2023.12.07 10:16:20 INFO [S2SOutgoingPromise-2]: org.jivesoftware.util.cache.CacheFactory - Created cache [org.jivesoftware.util.cache.DefaultLocalCacheStrategy] for Secret Keys Cache
2023.12.07 10:16:20 WARN [S2SOutgoingPromise-2]: org.jivesoftware.openfire.session.LocalOutgoingServerSession[Create outgoing session for: {ts3 -> jabber.tdf.local}] - Unable to create a new session: exhausted all options (not trying dialback as a fallback, as server dialback is disabled by configuration.
2023.12.07 10:16:20 WARN [S2SOutgoingPromise-2]: org.jivesoftware.openfire.session.LocalOutgoingServerSession[Authenticate local domain: 'ts3' to remote domain: 'jabber.tdf.local'] - Unable to authenticate: Fail to create new session.
2023.12.07 10:16:20 WARN [S2SOutgoingPromise-2]: org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor - An exception occurred while trying to establish a connection for {ts3 -> jabber.tdf.local}
java.lang.Exception: Failed to create connection to remote server
    at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.establishConnection(OutgoingSessionPromise.java:311) ~[xmppserver-4.7.5.jar:4.7.5]
    at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.run(OutgoingSessionPromise.java:254) [xmppserver-4.7.5.jar:4.7.5]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_202]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_202]
    at java.lang.Thread.run(Unknown Source) [?:1.8.0_202]
2023.12.07 10:17:03 WARN [S2SOutgoingPromise-2]: org.jivesoftware.openfire.session.LocalOutgoingServerSession[Create outgoing session for: {ts3 -> jabber.tdf.local}] - Unable to create a new session: exhausted all options (not trying dialback as a fallback, as server dialback is disabled by configuration.
2023.12.07 10:17:03 WARN [S2SOutgoingPromise-2]: org.jivesoftware.openfire.session.LocalOutgoingServerSession[Authenticate local domain: 'ts3' to remote domain: 'jabber.tdf.local'] - Unable to authenticate: Fail to create new session.
2023.12.07 10:17:03 WARN [S2SOutgoingPromise-2]: org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor - An exception occurred while trying to establish a connection for {ts3 -> jabber.tdf.local}
java.lang.Exception: Failed to create connection to remote server
    at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.establishConnection(OutgoingSessionPromise.java:311) ~[xmppserver-4.7.5.jar:4.7.5]
    at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.run(OutgoingSessionPromise.java:254) [xmppserver-4.7.5.jar:4.7.5]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_202]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_202]
    at java.lang.Thread.run(Unknown Source) [?:1.8.0_202]

and the latter are repeated, probably somehow related to DNS

Your Openfire server tries to communicate with another XMPP domain. If this is unexpected, then this is probably an addressing issue.

Could it be that your XMPP domain was previously called jabber.tdf.local but is now called ts3?

Such a ‘rename’ would mean that the addresses of your local users have effectively changed. This will cause Openfire to try and find a server that uses the old name when routing data. The errors that you see can be a result of such a rename.

Changing an XMPP domain name of a running server is not advisable, as it will break routing. However, maybe you need to change the XMPP domain name ‘back’ to the original version. You may be able to do this by modifying the openfire.xml file (make sure that Openfire is shut down when you do this). If that does not work, then it might be required to re-install Openfire.

This is probably because: XMPP Domain Name:ts3
but the users on the client are registered to connect to : jabber.tdf.local
the dns is specified CNAME ts3
and users are normally authenticated

these errors are clearly not because of this:

2023.12.07 16:15:24 WARN [pool-monitoring135]: org.jivesoftware.openfire.archive.ArchiveIndexer[MUCSEARCH] - Updating (not creating) an index since 'EPOCH'. This is suspicious, as it suggests that an existing, but empty index is being operated on. If the index is non-empty, index duplication might occur.
2023.12.07 16:20:24 WARN [pool-monitoring136]: org.jivesoftware.openfire.archive.ArchiveIndexer[MUCSEARCH] - Updating (not creating) an index since 'EPOCH'. This is suspicious, as it suggests that an existing, but empty index is being operated on. If the index is non-empty, index duplication might occur.
2023.12.07 16:25:24 WARN [pool-monitoring139]: org.jivesoftware.openfire.archive.ArchiveIndexer[MUCSEARCH] - Updating (not creating) an index since 'EPOCH'. This is suspicious, as it suggests that an existing, but empty index is being operated on. If the index is non-empty, index duplication might occur.
2023.12.07 16:30:24 WARN [pool-monitoring140]: org.jivesoftware.openfire.archive.ArchiveIndexer[MUCSEARCH] - Updating (not creating) an index since 'EPOCH'. This is suspicious, as it suggests that an existing, but empty index is being operated on. If the index is non-empty, index duplication might occur.
2023.12.07 16:35:24 WARN [pool-monitoring143]: org.jivesoftware.openfire.archive.ArchiveIndexer[MUCSEARCH] - Updating (not creating) an index since 'EPOCH'. This is suspicious, as it suggests that an existing, but empty index is being operated on. If the index is non-empty, index duplication might occur.
2023.12.07 16:40:24 WARN [pool-monitoring144]: org.jivesoftware.openfire.archive.ArchiveIndexer[MUCSEARCH] - Updating (not creating) an index since 'EPOCH'. This is suspicious, as it suggests that an existing, but empty index is being operated on. If the index is non-empty, index duplication might occur.
2023.12.07 16:45:24 WARN [pool-monitoring147]: org.jivesoftware.openfire.archive.ArchiveIndexer[MUCSEARCH] - Updating (not creating) an index since 'EPOCH'. This is suspicious, as it suggests that an existing, but empty index is being operated on. If the index is non-empty, index duplication might occur.
2023.12.07 16:50:24 WARN [pool-monitoring145]: org.jivesoftware.openfire.archive.ArchiveIndexer[MUCSEARCH] - Updating (not creating) an index since 'EPOCH'. This is suspicious, as it suggests that an existing, but empty index is being operated on. If the index is non-empty, index duplication might occur.
2023.12.07 16:55:24 WARN [pool-monitoring150]: org.jivesoftware.openfire.archive.ArchiveIndexer[MUCSEARCH] - Updating (not creating) an index since 'EPOCH'. This is suspicious, as it suggests that an existing, but empty index is being operated on. If the index is non-empty, index duplication might occur.
2023.12.07 17:00:24 WARN [pool-monitoring151]: org.jivesoftware.openfire.archive.ArchiveIndexer[MUCSEARCH] - Updating (not creating) an index since 'EPOCH'. This is suspicious, as it suggests that an existing, but empty index is being operated on. If the index is non-empty, index duplication might occur.
2023.12.07 17:03:47 WARN [socket_c2s_ssl-thread-2]: org.jivesoftware.openfire.nio.ConnectionHandler - Closing connection due to exception in session: (0x00000024: nio socket, server, /10.0.1.141:60793 => 0.0.0.0/0.0.0.0:5223)
java.io.IOException: ��������� ���� ������������� �������� ������������ �����������
    at sun.nio.ch.SocketDispatcher.read0(Native Method) ~[?:1.8.0_202]
    at sun.nio.ch.SocketDispatcher.read(Unknown Source) ~[?:1.8.0_202]
    at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source) ~[?:1.8.0_202]
    at sun.nio.ch.IOUtil.read(Unknown Source) ~[?:1.8.0_202]
    at sun.nio.ch.SocketChannelImpl.read(Unknown Source) ~[?:1.8.0_202]
    at org.apache.mina.transport.socket.nio.NioProcessor.read(NioProcessor.java:378) ~[mina-core-2.1.3.jar:?]
    at org.apache.mina.transport.socket.nio.NioProcessor.read(NioProcessor.java:47) ~[mina-core-2.1.3.jar:?]
    at org.apache.mina.core.polling.AbstractPollingIoProcessor.read(AbstractPollingIoProcessor.java:519) ~[mina-core-2.1.3.jar:?]
    at org.apache.mina.core.polling.AbstractPollingIoProcessor.access$1200(AbstractPollingIoProcessor.java:68) ~[mina-core-2.1.3.jar:?]
    at org.apache.mina.core.polling.AbstractPollingIoProcessor$Processor.process(AbstractPollingIoProcessor.java:1222) ~[mina-core-2.1.3.jar:?]
    at org.apache.mina.core.polling.AbstractPollingIoProcessor$Processor.process(AbstractPollingIoProcessor.java:1211) ~[mina-core-2.1.3.jar:?]
    at org.apache.mina.core.polling.AbstractPollingIoProcessor$Processor.run(AbstractPollingIoProcessor.java:683) ~[mina-core-2.1.3.jar:?]
    at org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:64) ~[mina-core-2.1.3.jar:?]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) ~[?:1.8.0_202]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) ~[?:1.8.0_202]
    at java.lang.Thread.run(Unknown Source) [?:1.8.0_202]
2023.12.07 17:05:24 WARN [pool-monitoring153]: org.jivesoftware.openfire.archive.ArchiveIndexer[MUCSEARCH] - Updating (not creating) an index since 'EPOCH'. This is suspicious, as it suggests that an existing, but empty index is being operated on. If the index is non-empty, index duplication might occur.
2023.12.07 17:10:24 WARN [pool-monitoring154]: org.jivesoftware.openfire.archive.ArchiveIndexer[MUCSEARCH] - Updating (not creating) an index since 'EPOCH'. This is suspicious, as it suggests that an existing, but empty index is being operated on. If the index is non-empty, index duplication might occur.
2023.12.07 17:15:24 WARN [pool-monitoring157]: org.jivesoftware.openfire.archive.ArchiveIndexer[MUCSEARCH] - Updating (not creating) an index since 'EPOCH'. This is suspicious, as it suggests that an existing, but empty index is being operated on. If the index is non-empty, index duplication might occur.
2023.12.07 17:20:24 WARN [pool-monitoring156]: org.jivesoftware.openfire.archive.ArchiveIndexer[MUCSEARCH] - Updating (not creating) an index since 'EPOCH'. This is suspicious, as it suggests that an existing, but empty index is being operated on. If the index is non-empty, index duplication might occur.

ts3 is an old name and if it is replaced, users lose their entire history, and with the update, the database was moved to a new server

I looked in the file openfire.xml specified: ts3.ski.loc
in the open fire interface: ts3

does it have any effect?

that is, why these errors, no one will tell?

The warnings that are logged suggest that either the message archive that’s stored on the server is empty (which can happen if no-one used the new system yet), or that its search-index is somehow broken. If that’s the case, then this affects keyword-based search, which can be annoying, but should’t be to much of a problem.

As for the domain name issues: you will have to make sure that the correct XMPP domain name of the server matches its original value.

if these errors are insignificant and everything should work fine, but only they are present in the log, then why is there such an effect that I wrote about at the very beginning:

although the correspondence works fine, but when you launch the client the next day (miranda NG v0.96.3) almost all messages for the last day pop up at once, from everyone I talked to.

and it happens every morning