[Fixed in 0.3.0] Installation reverted to first-time setup

Beta release announcements and discussion around them
Post Reply
pacmanfan
Posts: 1
Joined: Sun Dec 25, 2016 5:38 am

Sun Dec 25, 2016 5:53 am

Around Nov. 8th I installed Unimus on Ubuntu Server 16.04.1 64bit. It seems like I had some difficulty getting Tomcat working properly, but I eventually got it set up. I created and documented a user account, and an encryption key for the file-based db. I set up one Mikrotik device for regular backups, and haven't touched Unimus until today. I didn't even so much as log in between Nov. 8th and now.

Today I attempted to load http://x.x.x.x:8080/Unimus/, and after about 15 seconds it hadn't loaded. I tried http://x.x.x.x:8080 and the Tomcat welcome page loaded right away. I tried http://x.x.x.x:8080/Unimus/ again, and within a few seconds the first-time setup loaded. I went a couple pages into the setup before bailing out. I rebooted the server, and am still getting the first-time setup screen.

Any idea what's up with that? Wondering if I overwrote my file db by going into the setup.
User avatar
Tomas
Posts: 1206
Joined: Sat Jun 25, 2016 12:33 pm

Mon Dec 26, 2016 11:05 am

Hi,

This is sadly a known issue that affects around 5% of our installations. Sorry you were one of the affected.

The issue happens when Unimus switches from in-memory database (which it uses on startup) to the one you configure during Wizard (be it HSQL or MySQL). In certain cases, it doesnt switch properly and continues writing to the in-memory DB, which of course is gone when the application restarts (causing the issue you see).

We fixed this in 0.3.0.

In the meantime, restart the application multiple times after completing the Wizard, if you properly get a login screen, you know that everything is fine and you were not affected. If you get the Wizard a 2nd time, you ran into the bug. Simply complete the Wizard again and restart again, until you get a login properly after a restart.
wazza
Posts: 9
Joined: Thu Dec 15, 2016 1:33 am

Mon Dec 26, 2016 12:25 pm

Just as a 2c comment to add to this.

This particular issue is also a problem with the Docker version, and while that might be affected by they bug, you also have to factor in that the default image within Docker is read only. (Perhaps better instructions might help here. I'm a Docker newbie!)

It was a little distressing to have it setup and running, for about 20+ days, only to find that after restarting the machine, all the backups etc. where gone, and had to go through the setup process again. (Another reason for wanting the ability to backup / dump, the config, so that it could be loaded in quickly.)

Rgds,
W.

PS: As for Docker, the only reason I like the concept, is that in theory I can treat this as an appliance, and not have to worry about maintaining it, which in my current environment, would be just another tool that I have to look after.
Post Reply