How to upgrade core on MangoES?

[JoelHaggar]

Hi Jenny,

Here is a link to a good build of Mango 2.6 beta: https://dl.dropboxusercontent.com/u/6546748/m2m2-mango-2.6.0.zip

You can follow the manual instructions in our wiki for the upgrade: http://infiniteautomation.com/wiki/doku.php?id=system_admin:upgrading

Here are the basic commands you would follow after connecting via ssh:

cd /opt

sudo service mango stop

sudo cp -avr /opt/mango/ /opt/mango-backup

cd mango

sudo wget https://dl.dropboxusercontent.com/u/6546748/m2m2-mango-2.6.0.zip

cd web/modules

sudo wget https://dl.dropboxusercontent.com/u/6546748/m2m2-mangoESConfiguration-1.1.0.zip

cd /opt/mango

sudo rm -r lib

sudo unzip m2m2-mango-2.6.0.zip

A

sudo service mango start

[jeremyh]

Hi Jenny

I also am having difficulty with SNMP on some MangoES units running 2.5.2 and haven't been able to work out the problem (haven't had time either..)

Were you getting the same error as me? If so did upgrading to 2.6.2 fix it?

My error:

Thanks
Jeremy

[Jenny]

Hi Joel,

After upgrade to core version 2.6, the modules are unstable. SNMP are still can not connect to the devices.

Any suggestion?

[JoelHaggar]

Is the new version of Mango still running in the /opt/mango folder? It looks like either the GUID has changed or the license file has been overwritten. You can contact our support at support@infiniteautomation.com and if you can provide remote access we will take a look and get the license issue resolved.

I wonder if the error is a networking issue. It might be worth checking the /etc/resolv.conf file to make sure it has the right DNS server setting in it.

[Jenny]

Hi Joel,

I try to redo upgrade core to 2.6 version. But I'm not sure it's fineshed, cause I see message "sudo: unable to resolve host mango."
Capture as below for your reference.

[JoelHaggar]

Can you check your: /etc/resolv.conf and make sure the DNS setting is correct for your network.

[Jenny]

Hi Joel,

I have checked /etc/resolv.conf and the DNS setting is correct.

[JoelHaggar]

ok thanks. Either way this error shouldn't cause any issues with mango strating. If Mango doesn't start as expected then stop the service and start it manualally by going to the /opt/mango/bin folder and running sudo ./ma.sh start

This will start it manually and you will see in the terminal if there are any startup errors.

On a side note, did you change the hostname of the MangoES? It should be something like mangoes2154

[JoelHaggar]

I think I know why you are getting the error about unable to resolve the host mango.

If you check your /etc/hosts file you will probably see something like mangoes1234. If you change that to just mango then I think your issue will be resolved.

[JoelHaggar]

@jeremyh You can put these two lines in your classes/log4j.xml file toward the bottom to turn on debug logging for snmp. In Mango on the system setting page there is an area where you can reload the Log4J configuration so you don't have to reboot Mango.

<category name="com.serotonin.m2m2.snmp"><level value="debug"/></category>
<category name="org.snmp4j"><level value="debug"/></category>

See if you get any more specific error messages in the logs/ma.logs file.

[Jenny]

Joel,

Thank you for kindly help, it's work.

[JoelHaggar]

@jeremyh @Jenny
In regards to the follow error I believe I know the solution:

The issue is in the /etc/hosts file.

On your MangoES SSH in and run "sudo nano /etc/hosts"

Your file should look like this:

The last line if the part to note. This needs to match what the host name is of your MangoES. There is a bug in the MangoES configuration module where if you change the Hostname there the hosts file does not get updated. In my tests getting the hostname correct in the hosts file will resolve this issue.

Please let me know if that works

[Jenny]

Hi Joel,

Thank you for kindly reply.

This is work, this solved SNMP issue.