UPDATE: 2.0.0 has been released, and this topic has been locked.
Unimus 2.0.0-RC2 is being released today. This is a Beta release of Unimus & Unimus Core intended for testing purposes.
Release includes the new Unimus Core module (remote agent / remote probe) for remote network support.
2.0.0 has been in development for over 6 months, and will be the biggest release of Unimus yet.
There are many new features and bug fixes, and we highly recommend checking the entire Changelog.
! Please make sure to back-up your database before upgrading to any Beta/RC builds !
Builds are available for download here:
https://unimus.net/download-dev
[BETA] 2.0.0-Beta2 release thread (Unimus & Unimus Core)
Update: We've just pushed a fixed build with multiple fixes for the new Zones feature, as well as multiple fixes for Mass Config Push.
(we have bumped the version to Beta3 because of this)
A big thank you for everyone who is testing the Beta builds and reporting issues!
If you find any issues in the latest builds, please let us know.
(we have bumped the version to Beta3 because of this)
A big thank you for everyone who is testing the Beta builds and reporting issues!
If you find any issues in the latest builds, please let us know.
Hi Tomas,
Thanks for your continued work on a great product. I have one feedback item and one question:
1. During the install of core, I let the "port" default to 5509 during installation, but it looks like the config file didn't populate with 5509, and caused an error upon startup:
2020-04-19 17:04:25.618 ERROR 1424 --- [main] net.unimus.core.standalone.Boot : Boot failed, 'Malformed Unimus config.Value for unimus.port not found or it is not a number'
The config file looked like this:
# Unimus server port
unimus.port =
# Access key used for connection authentication
Once I filled in 5509 and restarted, I'm getting:
Boot failed, 'Malformed access key structure'
My question is, where do I get the "Access key used for connection authentication"? I checked my Unimus server config and can't find that value defined anywhere.
Thanks!
-Dan
Thanks for your continued work on a great product. I have one feedback item and one question:
1. During the install of core, I let the "port" default to 5509 during installation, but it looks like the config file didn't populate with 5509, and caused an error upon startup:
2020-04-19 17:04:25.618 ERROR 1424 --- [main] net.unimus.core.standalone.Boot : Boot failed, 'Malformed Unimus config.Value for unimus.port not found or it is not a number'
The config file looked like this:
# Unimus server port
unimus.port =
# Access key used for connection authentication
Once I filled in 5509 and restarted, I'm getting:
Boot failed, 'Malformed access key structure'
My question is, where do I get the "Access key used for connection authentication"? I checked my Unimus server config and can't find that value defined anywhere.
Thanks!
-Dan
Thanks for the feedback!dbrisson wrote: ↑Sun Apr 19, 2020 5:28 pm1. During the install of core, I let the "port" default to 5509 during installation, but it looks like the config file didn't populate with 5509, and caused an error upon startup:
2020-04-19 17:04:25.618 ERROR 1424 --- [main] net.unimus.core.standalone.Boot : Boot failed, 'Malformed Unimus config.Value for unimus.port not found or it is not a number'
The 5509 during Core installation is a hint, it doesn't populate the config file with it if you don't specify it.
You are totally right that it would be intuitive to use the default if nothing is entered. We will update the Core Installer to use the default port if nothing is entered during the installation.
Each Zone has it's own access key.
You can find it in the "Zones" menu in Unimus, after you expand a zone that is set to communicate over a "Remote Core".
Thanks! Now that I've updated the key on the core, it shows online in Unimus.
Unfortunately I'm not able to get it to discover a device. I see this in the long on the core:
2020-04-19 21:14:18.303 ERROR 4232 --- [discovery-8] n.u.core.api.ForwardingResponseSender : MessageSender not configured
2020-04-19 21:14:20.073 ERROR 4232 --- [discovery-8] n.u.core.api.ForwardingResponseSender : MessageSender not configured
Could that be the reason? Unimus log is just showing: Device is not discovered
Thanks,
-Dan
Unfortunately I'm not able to get it to discover a device. I see this in the long on the core:
2020-04-19 21:14:18.303 ERROR 4232 --- [discovery-8] n.u.core.api.ForwardingResponseSender : MessageSender not configured
2020-04-19 21:14:20.073 ERROR 4232 --- [discovery-8] n.u.core.api.ForwardingResponseSender : MessageSender not configured
Could that be the reason? Unimus log is just showing: Device is not discovered
Thanks,
-Dan
Thanks for the report - we had other testers report this issues as well.
These errors are indeed why devices jobs are failing.
We are fixing this and should have a build with fixes available soon.
Update:
We have released 2.0.0-RC2 today. This build fixes 48 various issues/bugs reported since Beta2.
A massive thank you goes to our devs, who have been working overtime and through the last 2 weekends to fix all of these.
We are currently tracking the following known issues in RC2:
As soon as these are fixed, 2.0.0 will be released into the stable branch.
We have released 2.0.0-RC2 today. This build fixes 48 various issues/bugs reported since Beta2.
A massive thank you goes to our devs, who have been working overtime and through the last 2 weekends to fix all of these.
We are currently tracking the following known issues in RC2:
2.0.0 has been through extensive QA testing over the last few weeks, and these are the last remaining issues.1) when devices are moved between Zones during running operations, operations might get stuck in rare cases
2) Unimus and Core might not detect connectivity loss under rare circumstances, and Core might show "Online" in Unimus even if it's not
3) you might receive empty configuration change notifications in rare cases
4) editing Per-Tag Connectors doesn't work on MySQL
As soon as these are fixed, 2.0.0 will be released into the stable branch.