Mango stuck after starting upgrade to 2.8.8
-
Hi Brian,
Are you starting it with
./ma.sh start
from the bin directory? That will be sure that we've got stderr coming back to the console with stdout.You can try moving Mango/databases to Mango/databases-bck and then starting Mango on a fresh database. You can then do a restore of the H2 database, test if restart works, then bring back your Mango/databases/mangoTSDB directory for your data, if you're using NoSQL.
-
Hello Phil,
I will give that a try. One other thing I was just looking at, and wanted your advice.My env.properties in the override folder is a bit old. The default env.properties has quite a few more lines in it that are not in my file. Should I transfer my required settings into the newer env.properties file and save it to the overrides folder?
Thank for your help so far.
Brian
-
Here are the last few lines from the command line after running the ma.sh start command:
INFO 2017-07-06 19:49:39,868 (com.serotonin.m2m2.Main.loadModules:416) - Loading module 'scheduledEvents', v1.6.0 by Infinite A utomation Systems Inc.
INFO 2017-07-06 19:49:39,870 (com.serotonin.m2m2.Main.loadModules:416) - Loading module 'pop3', v1.6.0 by Infinite Automation S ystems Inc.
INFO 2017-07-06 19:49:39,872 (com.serotonin.m2m2.Main.loadModules:416) - Loading module 'mangoNoSqlDatabase', v1.3.7 by Infinit e Automation Systems Inc.
INFO 2017-07-06 19:49:39,875 (com.serotonin.m2m2.Main.loadModules:416) - Loading module 'asciiFile', v1.3.0 by Infinite Automat ion Systems Inc.
INFO 2017-07-06 19:49:39,877 (com.serotonin.m2m2.Main.loadModules:416) - Loading module 'twilio', v1.2.0 by Infinite Automation Systems Inc.
INFO 2017-07-06 19:49:40,359 (com.serotonin.m2m2.Lifecycle.initialize:216) - Initializing Spring Object Mapper
Exception in thread "main" java.lang.UnsupportedClassVersionError: com/infiniteautomation/tsdb/IasTsdbConfig : Unsupported major .minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at com.infiniteautomation.nosql.MangoNoSqlMenuItemDefinition.preInitialize(MangoNoSqlMenuItemDefinition.java:50)
at com.serotonin.m2m2.module.Module.preInitialize(Module.java:104)
at com.serotonin.m2m2.Lifecycle.initialize(Lifecycle.java:228)
at com.serotonin.m2m2.Main.main(Main.java:115)
[root@M-2-M bin]#I will move the databases and try again.
-
Hi Brian,
Are you updating from Mango 2.7? That error means that you're using Java 7 probably (confirm with
java -version
at the terminal). You will need to update Java as 2.8 and 3.0 are written for Java 8.The properties in the env.properties file are added as we come up with new ones. The code has the opportunity to set defaults in the retrieval of the property as well, which gives us the option to set defaults for new users (who would copy new env.properties files to their new overrides) and set different defaults for existing users (as the property doesn't exist in their env.properties file). You can copy them across. I would say 95% of the time the default in the code and the default in the file are the same, so it doesn't really matter if you copy them across or not.
-
Thank you for your reply Phil,
I was wondering if it was java related. No I did not update my java version before the upgrade. i may have missed that requirement in the notes. I will put the databases back as they made no difference to the start up.I will update my java as my current version is 1.7.0_80
I will let you know if that works.
Cheers
-
I can't seem to get the links sorted so that java point to the new version... :(
-
Mango will preferentially use JAVA_HOME. You can define/export that in /etc/environment or in your service file.
Otherwise yeah, you're maybe playing with the update-alternatives command probably. It's a run around to get /usr/local/java --> /etc/alternatives/java --> /opt/java/jdk1.8.0_121/bin/java (and javac and javaws)
I think the commands you're looking for are the update-alternatives commands in this article, probably: https://help.infiniteautomation.com/linux-installation/
-
This post is deleted! -
This post is deleted! -
Hello Phil,
Thank you for your help. It was getting late last night and I made some silly tired brain mistakes. I started over this morning with your instructions and everything seems to be working now. No restore of the databases needed.My other worry was that we have another piece of software on the server and I thought it may require an older 32 bit version of Java. But it seems to be working with the latest 64 bit java as well.
Cheers
Brian