Can you check the /opt/mango/lib folder I wonder if it is empty? If so there could have been a upgrade issue in which case you would want to download the core zip file again and copy all the contents of the lib folder. This is just another guess. If that doesn't resolve it contact us at support and we'll hop on a screen share with you to poke around directly.
Mango on Ubuntu 14.04
Definitely not empty - 156 jar files in there.
Well, more information could be gained by modifying the bin/ma-init.sh script to echo relevant stuff during the bin/ma.sh launch
ls -l $(echo $EXECJAVA | sed -e 's/java$//') | grep java
... around line 27 of bin/ma-init.sh
OK, that did the trick thanks Phil. Even though
sudo echo $PATHdidn't suggest that the path was being reset, adding those lines into the init script showed that it actually was being reset. Launching with
sudo -E ./ma.sh startworked correctly! :)
We've been having a similar problem (not auto starting at boot) for months now. However, I'm not so Linux savvy as smith. Could one of you poke around and try to resolve this issue?
PS, We're Sheridan Point Condominiums.
Can you email us the log from your Mango? You can find these on the computer at /opt/mango/logs/ma.log or more easily by logging in to Mango as the admin, navigating to the logging console page (tree log icon), and clicking the 'email logs to Infinite Automation' button (I believe this is Core 2.7+)
Hi Mihairosu, I may already be able to look into it. I will conduct the rest by email.
Thanks for fixing it for us Phil, this is much nicer!
No problem! I wasn't sure why JAVA_HOME wasn't in the environment, but I sourced the environment from the service and exported JAVA_HOME, problem solved.
Added the lines...
to your Mango service file