[Solved] 0.2.0 dashboard issue

Beta release announcements and discussion around them
Post Reply
jstump
Posts: 16
Joined: Thu Jul 14, 2016 8:26 pm

Wed Aug 24, 2016 3:48 pm

Updated to 0.2.0 after creating a new MySQL db. My devices were there, but no descriptions. Fixed that in the DB, but I'm having errors now after checking all devices and telling to back up:
Screenshot 2016-08-24 11.40.12.png
Screenshot 2016-08-24 11.40.12.png (71.21 KiB) Viewed 7393 times
Last successful job shows Discovery with no info and failed jobs is empty:
Screenshot 2016-08-24 11.44.26.png
Screenshot 2016-08-24 11.44.26.png (106.57 KiB) Viewed 7393 times
User avatar
Tomas
Posts: 1206
Joined: Sat Jun 25, 2016 12:33 pm

Wed Aug 24, 2016 4:55 pm

The screenshots look like a really old version of Unimus - 0.1.2 or older.

The addOrUpdate() method which throws a NPE is no longer used in 0.2.0 on the Dashboard.
The entire Import section is also missing from the GUI in the 2nd screenshot.

Are you sure you are running the correct version against the correct DB?
jstump
Posts: 16
Joined: Thu Jul 14, 2016 8:26 pm

Wed Aug 24, 2016 5:22 pm

Perhaps a lot of my problems stem from not updating correctly in Tomcat?

I normally just stop the application and then upload/deploy the new war file. Should I have been clicking undeploy before uploading? I tried that just now and get this error when attempting to start in Tomcat:

FAIL - Application at context path /Unimus could not be started
FAIL - Encountered exception org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/Unimus]]
User avatar
Tomas
Posts: 1206
Joined: Sat Jun 25, 2016 12:33 pm

Wed Aug 24, 2016 5:25 pm

There should be a lot more detailed error log in catalina.out.

Also, make sure the DB which the config file ("/etc/unimus/unimus.properties" or "'C:\ProgramData\Unimus\unimus.properties") points to is empty before running 0.2.0 for the first time :)
jstump
Posts: 16
Joined: Thu Jul 14, 2016 8:26 pm

Wed Aug 24, 2016 5:37 pm

Yeah, that was likely it. Redeployed WAR with empty DB and it looks to be running now. Thanks!
Post Reply