Mango's Out of Memory Problem

[phildunlap]

Yes you can update through the UI without having license issues and whatnot. If you're worried about your data or configuration, leave the "backup before updating" checkbox ticked and wait for it to create a backup (provided backups are enabled in your system settings!). If updating through the modules page caused license issues (aside the 2 --> 3 major upgrade, and perhaps future major versions, which is clearly stated on the modules page during the upgrade process) we would be overwhelmed with the same requests all the time.

[Nikospps]

Hello @phildunlap ,

i issued a big problem,after the effort of upgrading in to latest version:

As a result i can't start (and open) the UI api.

Why, all this issue?

[Nikospps]

And also this, as i try to run upgrade.sh:

[phildunlap]

:-/ When I say the UI, I mean the webserver, not the command line. I guess you didn't chmod +x all the scripts when you did your installation? I suspect your invoking the upgrade.sh script directly didn't hurt anything, since it didn't know where Mango was installed, but we've never instructed anyone to do that.

You may still have the updated m2m2-core-3.4.1.zip in your Mango/ directory. If you attempted to start Mango again it would perform the upgrade.

Otherwise,

You should resolve this by downloading the enterprise bundle here: https://store.infiniteautomation.com/core

1. Place the downloaded file in your Mango/ directory with the name m2m2-core-3.4.1.zip ,
2. chmod +x Mango/bin/*.sh
3. You may need to chown -R yourOsUser:yourOsGroup Mango/ if you copy the files over with a different permission that the user that launches Mango doesn't have.
4. cd Mango/bin; ./ma.sh start

The start scripts will check for upgrades in the Mango/ directory.

[Nikospps]

Hello @phildunlap . When we said UI, i did use webserver and not command line. After the invoking, i made efforts to correct, using this. But NO, i didn't use terminal.
This problem was caused, during upgrade process. It was really bad, as i couldn't see, the place, where scada was created using Mango.

I will follow your steps and will inform you.

Thanks in adnvance,
Nikos.

[Nikospps]

Finally solved!

I made the same "upgrade process and in second one licensed Mango Software and caused me the same problem.

After this, i followed your steps and correct the problem on each of them.

I have upgrated-to 3.4.1-versions for each of these versions, for which i purchased the license.
Hope, that i will will not meet the same "Out Of Memory" problem again.

I will inform you, if yes.

Thanks for the support.

[Nikospps]

Goodmorning @phildunlap , @Jared-Wiltshire.
Unfortunately the problem still remains:

despite the fact i upgraded to 3.4.1 as we said:

As a result, i have connection problems with the scada, where i use Mango, and need to restart it every few days.

It's an important issue for me and my company, so i would like to find a solution together.

Waiting for your ideas.

Thanks,
Nikos.

[phildunlap]

From the information you've provided there are way too many unknowns. For instance, the extent that you've provided anything from your logs is images of your console with the lower part of a stack trace and some threads having errors.

Jared put many questions to you, and you should answer them.

Is it possible your events, user events, and audit tables would benefit from a purge? How large is your H2 database?

[Nikospps]

I will reply to Jared's questions one by one immediately.
I also quote this issue, that sometimes happens to my watchlists:
Normal Monitoring:

Strange Monitoring:

[phildunlap]

Don't forget to answer the questions I posed to you in the last post, while you're at it. I wouldn't be surprised if purging your events table helps.

[Nikospps]

@Jared-Wiltshire

1. Mango Version for each of two purchased modules (Commercial and Commercial Lite):
   3.4.1

2. Yes, i have updated all the modules.

3. Currently run JDK 1.8.0_162

4. 540/1000 Data points at Commercial Version and 80/500 at Commercial Lite Version.

5. Modbus I/P Data Sources are enabled on both two versions.

6. They are running about 4 months.

7. Send me please a link, in order to send two files for each of two versions.

8. Yes i do have. For example, an alarm, for a switch connector, when equals to zero (is 'OFF')

9. No, i don't have any report handler.

10. Currently two users: administrator and another one user with limited privileges.

@phildunlap if i "purge all events" on system settings, i will lose only data of these events during these months or all the configuration settings, which enabled, to run these?

Thanks,
Nikos.

[phildunlap]

'Purging all events' will only delete everything in the events and userEvents tables in the database. It does not delete event handlers or configuration settings, only previous times that events occurred and information about acknowledgements or comments on those events.

[Nikospps]

I had the same issues today morning. So, i "purged all events" and have to watch its progress (or not).

[Nikospps]

Hello again,

after 7 days of progress monitoring and delete of events, today i noticed again the same issue:

I had answer to all questions. So maybe any bug?

[phildunlap]

If there were, it would be a nightmare to investigate it through console screenshots.

You can email your logs and your latest Mango/backup/core-database-H2-...zip file to support@infiniteautomation.com and I'll give it a look.