Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.
Mango 3.7 Install on new AlmaLinux9
-
Hello,
I am hoping someone can help me out.After our server crash and rebuild, the web host company had to put AlmaLinux9 on the server.
I have been trying to re-install mango 3.7.12 with my downloaded zip.
I have tried using the script found in the Mango 3 documentation. I have also run through the steps manually. But it seems that so many other items have changed since Mango 3.7 came out.The web server does not let applications or remote connections create databases. So I had to create the databases from the Plesk control panel first.
I am at the point that this error has occurred and I am not web savvy enough to figure out how to get past this hurdle. I would be very grateful if anyone can tell me how to get past this point.
[root@m-2-m ~]# systemctl start mango [root@m-2-m ~]# systemctl status mango ● mango.service - Mango Automation Loaded: loaded (/etc/systemd/system/mango.service; enabled; preset: disabled) Active: active (running) since Tue 2024-03-26 10:41:24 UTC; 19s ago Process: 5060 ExecStart=/opt/mango/bin/start-mango.sh (code=exited, status=0/SUCCESS) Main PID: 5064 (java) Tasks: 38 (limit: 202900) Memory: 388.7M CPU: 10.531s CGroup: /system.slice/mango.service └─5064 java -server -Dma.home=/opt/mango com.serotonin.m2m2.Main Mar 26 10:41:27 m-2-m.com start-mango.sh[5064]: SLF4J: Class path contains SLF4J bindings targeting slf4j-api versions prior to 1.8. Mar 26 10:41:27 m-2-m.com start-mango.sh[5064]: SLF4J: Ignoring binding found at [jar:file:/opt/mango/lib/log4j-slf4j-impl-2.16.0.jar!/org/slf4j/impl/S> Mar 26 10:41:27 m-2-m.com start-mango.sh[5064]: SLF4J: See http://www.slf4j.org/codes.html#ignoredBindings for an explanation. Mar 26 10:41:28 m-2-m.com start-mango.sh[5064]: Unable to determine the machine id Mar 26 10:41:28 m-2-m.com start-mango.sh[5064]: FATAL (com.serotonin.m2m2.Lifecycle.loadLic:591) - Unable to determine the machine id Mar 26 10:41:28 m-2-m.com start-mango.sh[5064]: ERROR (com.serotonin.m2m2.Main.main:162) - Error during initialization Mar 26 10:41:28 m-2-m.com start-mango.sh[5064]: java.lang.RuntimeException: Unable to determine the machine id Mar 26 10:41:28 m-2-m.com start-mango.sh[5064]: at com.serotonin.m2m2.Lifecycle.loadLic(Lifecycle.java:594) ~[ma-priv-3.7.12.jar:?] Mar 26 10:41:28 m-2-m.com start-mango.sh[5064]: at com.serotonin.m2m2.Lifecycle.initialize(Lifecycle.java:276) ~[ma-priv-3.7.12.jar:?] Mar 26 10:41:28 m-2-m.com start-mango.sh[5064]: at com.serotonin.m2m2.Main.main(Main.java:159) ~[ma-priv-3.7.12.jar:?] [root@m-2-m ~]#Thank you for any help help given.
Cheers
Brian -
BG,
I've looked into the code on our end, and while I can't say for sure what is happening - I'm expecting that it may have something to do with your environment. We use some code to determine a unique machine identifier for licensing purposes, and the most likely issue seems like it's failing to either read or write to the HOME/.ma file.
What distribution and version of Linux were you using before? Also, how does Plesk play into this? Is MySQL hosted on your system, or is it a shared database cluster? When I used web hosts in the past with a control panel, sometimes they did some weird things with permissions. Or, it could potentially just be an incompatibility with Alma Linux 9. We have tested later versions with Alma, but I can't say I've tried Mango 3 with it. If I get a chance later, I'll try tossing Mango 3 onto a quick Alma Linux 9 container and seeing if I get an issue myself.
Liv
Radix IoT -
@lgorence
Hello Liv,
Thank you for replying to my question on the forum.
First of all, our HOME/.ma file has a permission set of 0644 with the owner as root.
Please confirm that is appropriate setting.Our previous Linux distro was Centos 7 but the web hosts could rebuild that distro due to its end of life. During the rebuild we discovered that the Mariadb version and the Plesk version were all end of life as well.
So now we use AlmaLinux 9 as it was supposed to be the closest to Centos 7. (Should have gone with Debian as Matt Fox suggested in one of my recent forum questions) I think it is what you call a shared databsse cluster. The web server is a dedicated physical box but set up so that I can set up and sell multiple domains. I don't use it like that but it is set up like that. The Plesk control panel is the GUI for the server and database settings and has been updated to Obsidian 18 and it has at least one major change in that we can't create databases remotely. One article in the Plesk forum says this is by design. I have a user with all rights and from any where wild card set but it still won't let me create a new db from mysql workbench on my desktop. Not sure what's going on there to be honest. But just in case, I created the db mango from the plesk control panel, then went through the set up procedure and hit that error right at the end of the install procedure that is in the Mango 3 documentation. No tables have been created in the mysql mango db yet.
Now, if this related to the Java version, I have openjdk version 21 running on the server. It may be that this is too new. I didn't want to go making changes on the server in that regard until I had some advice from people that a lot more about this than I do. :)
Let me know if you think I need to install an earlier version. I cannot remember what we had on the previous server but it would have been something from about 5 years ago and I think the Java licensing came into affect after that.Thank you for your help.
Cheers
Brian -
@BG
Brian,I've found that the documentation for v3 mentions Java 8, but has some very outdated links to recommendations for builds. For Mango versions 4 and 5, we recommend using Azul Zulu, so in this case I would recommend Azul Zulu JDK 8, which you can find here (I filled in the Java version, OS, and architecture for you): https://www.azul.com/downloads/?version=java-8-lts&os=rhel&architecture=x86-64-bit&package=jdk#zulu
I would recommend installing via RPM, instead of dropping a ZIP somewhere. Then, remove Java 21 to reduce confusion and the possibility that Mango still picks up 21.
Also, a heads up. We don't test with or support MariaDB, so I'm unsure if you could run into issues there. If it was working just fine for you before, then I'm sure it'll continue to work, but just letting you know.
Liv
Radix IoT -
@lgorence
Hello Liv,
Thank you for your reply. I have a support ticket now. So I guess I will work through the problem there. Your colleague referenced your advice as well and I will try that tonight.I will post our solution here for others using Mango 3 to reference .
Thank you
Brian -
@BG
Brian,No worries at all, glad to help out. I look forward to seeing the solution.
-
@lgorence Hello Liv, and anyone else who comes across this thread.
I discovered that the AlmaLinux 9 was not allowing the Mango 3 install to complete due to permissions. Even after making the mango user the owner of the /opt/mango folder
the install still failed at the last module and kept trying to restart itself over and over again.I recursively set the execute permission on the mango folder for the mango user and the install completed and we were able to get to the log in screen and pick up the correct license file.
That seems to have been the crux of the whole install problem.
Cheers
Brian
