Hi forum,
Hope you will be able to help?
I have inherited a Unimus set up, and it has been fine for a number of months, but since yesterday we have a zone with a remote core that is showing as offline.
The main Unimus server has been rebooted, but the Core Status is still showing as offline.
The problem is, I do not know where the core has been installed, and cant seem to find any address info for this in the Unimus front end?
Is there anywhere I can see where this remote core is installed so I can then get onto that device and check the services?
Cheers
Rob
Locating Offline Remote Core?
Hi Rob,
when it comes to connection issues between the Unimus server and a remote core, the most common cause is a version mismatch between the server and the core.
To verify the IP address of the remote core and diagnose the connection issue, check the Unimus server log files. You can find them in:
Linux deployment: /var/log/unimus
Windows deployment: C:\ProgramData\Unimus\log
Look for the keyword CoreConnectionLogger in the logs.
Below is an example log entry where a Core was unable to connect to the Server. The remote core was at 10.1.2.3. The core was connecting from port 60040, while the Unimus server listens on local TCP port 5509. Logs on the server show:
Try searching the logs for similar entries to identify the remote core’s IP address and any related issues.
Once you locate the core, check its status and ensure it is running the exact same version as the Unimus server, as mismatched versions will cause connectivity problems.
You can find the steps to update your core instance on our wiki page:
https://wiki.unimus.net/pages/viewpage. ... d=36110338
Let us know if you need further assistance!
Cheers,
Ales
when it comes to connection issues between the Unimus server and a remote core, the most common cause is a version mismatch between the server and the core.
To verify the IP address of the remote core and diagnose the connection issue, check the Unimus server log files. You can find them in:
Linux deployment: /var/log/unimus
Windows deployment: C:\ProgramData\Unimus\log
Look for the keyword CoreConnectionLogger in the logs.
Below is an example log entry where a Core was unable to connect to the Server. The remote core was at 10.1.2.3. The core was connecting from port 60040, while the Unimus server listens on local TCP port 5509. Logs on the server show:
2025-03-20 15:31:19.299 INFO 8 --- [io-worker-1] s.n.t.c.i.CoreConnectionLogger : Connected '10.1.2.3:60040:5509:feb4fcb3-af95-481e-afda-2cf953df303a'
2025-03-20 15:31:19.413 WARN 8 --- [io-assembler-1] n.u.b.c.t.VersionExchangeValidatorImpl : Core connection acceptance denied, zone with coreId '883ac3d9-a6f4-4f14-b867-4b2f6357c282' not found in database
2025-03-20 15:31:19.414 INFO 8 --- [io-assembler-1] s.n.t.c.i.CoreConnectionLogger : Closed '10.1.2.3:60040:5509:feb4fcb3-af95-481e-afda-2cf953df303a'
Try searching the logs for similar entries to identify the remote core’s IP address and any related issues.
Once you locate the core, check its status and ensure it is running the exact same version as the Unimus server, as mismatched versions will cause connectivity problems.
You can find the steps to update your core instance on our wiki page:
https://wiki.unimus.net/pages/viewpage. ... d=36110338
Let us know if you need further assistance!
Cheers,
Ales