I purchased a few licenses today for Unimus, and got some routers/switches setup and working. All was super smooth, and I'm really impressed. However, several hours later (at around 00:00 UTC), Unimus just.... stopped working. When I try to login to my local deployment, it tells me that my license key usage has been exceeded, and I need to purchase more or enter a new license key.
Furthermore (and honestly more worrisome to me) is that the logs on the app itself (deployed into Docker) state that it has disabled itself entirely due to this licensing issue - and is no longer protecting/backing up my configurations. I tried to login to the portal to check my licenses are still there, but that's throwing a 500 error.
Code: Select all
unimus_app.1.djf0ers1ditf@docker02.lan | 2021-11-16 15:58:09.004 INFO 12 --- [nio-8085-exec-4] net.unimus.business.aaa.AAAHandlerImpl : User 'user' logged out.
unimus_app.1.djf0ers1ditf@docker02.lan | 2021-11-16 18:01:31.917 INFO 12 --- [ qrtz--3] net.unimus.system.UnimusImpl : Setting new license key state 'AMOUNT_EXCEEDED'
unimus_app.1.djf0ers1ditf@docker02.lan | 2021-11-16 18:01:32.418 INFO 12 --- [pool-2-thread-1] net.unimus.business.scheduler.Scheduler : Un-scheduling 'discovery / backup' job 'At 3:00 AM, every day'
- Why did Unimus just randomly decide I was over my license limits, 3+ hours after I first set everything up and things were working great?
- If the portal being down coincides with my licensing issue, why is it that the app will stop working when there are server-side issues? Shouldn't it cache license info for some time, etc to survive issues such as this?
- How does one log a support ticket if portal.unimus.com is down?
Thanks!