Hi!
I have had a user account for my Mango software for a long time.
But now it seems to be gone, is there a need to register again ?
I had an account in infiniteautomation.com(and prior to that) the forum cridentials are working.
I have been running Mango sinse prior to version 2.

Hi !
I am installing Mango on a old PC with a fresh UBUNTU installation 16.04.
After Java installation according to Installatiob section in Documents page I have some starting up issue
See attached text, what do I do?

// Stensma

“ma-start: MA started with Process ID: 3167
INFO 2018-02-27T08:49:05,543 (com.serotonin.m2m2.Main.main:90) - Starting Mango 3.3.0 with Schema Version: 23
Exception in thread "main" com.serotonin.m2m2.Main$ModulePropertiesException: java.security.InvalidKeyException: Illegal key size or default parameters
at com.serotonin.m2m2.Main.getProperties(Main.java:838)
at com.serotonin.m2m2.Main.loadReleaseProperties(Main.java:322)
at com.serotonin.m2m2.Main.main(Main.java:101)
Caused by: java.security.InvalidKeyException: Illegal key size or default parameters
at javax.crypto.Cipher.a(Unknown Source)
at javax.crypto.Cipher.a(Unknown Source)
at javax.crypto.Cipher.a(Unknown Source)
at javax.crypto.Cipher.init(Unknown Source)
at javax.crypto.Cipher.init(Unknown Source)
at com.serotonin.m2m2.Main.cipher(Main.java:861)
at com.serotonin.m2m2.Main.getProperties(Main.java:823)
... 2 more
ma-start: no restart flag found, not restarting MA
ma-start: MA done

@phildunlap It looks like the same issue i have posted on my mini mac
I got the java to hang.
Please provide the same info and post a answer on the forum what happens

I can not manage to start my Mango after a possible power failure on my Mac Mini that hosts the Mango software. It has been running for several mounts witout any major problems.

I add now when I saw anothet topic that it was after i started a upgrade of the software the restart hanged and now it is still so after som days and after a power cycle of the mini mac. So there is no power failure causing this.)

The " ma start " does not complete, the java icon does not show up, abd a java process is using 99% of processor time for up to 9 hours until i forced the process to shut down.
At the Command prompt following was printed then:
"ma-start: MA started with Process ID: 678
INFO 2017-08-24T06:38:06,937 (com.serotonin.m2m2.Main.main:90) - Starting Mango 3.2.0+20170807191436 with Schema Version: 17
/Users/perfer/Documents/Mango3/bin/ma-start.sh: line 147: 678 Killed: 9 $EXECJAVA $JPDA $JAVAOPTS -server -cp "$MA_CP" "-Dma.home=$MA_HOME" "-Djava.library.path=$MA_HOME/overrides/lib:$MA_HOME/lib:/usr/lib/jni/:$PATH" com.serotonin.m2m2.Main
ma-start: no restart flag found, not restarting MA"

What is the problem?

I found the bad guy !
A Cron Job create all the files in /var/spool/exim4/input.
When I disable this task, the folder is quiet .
But why is this job there ? and what is it suppose to do?

New files are created all the time.
There two different contents one is:

The other has following content:

I have now created an empty log.txt file in the missing mango-backups folder,
lets see if this does the trick...

I have now removed the files in the /var/spool/exim4/input.
Now the resources is back on track, but still what is creating the files?

After :

Then I am able to run basic Webmin functions, but what is creating the problem?
I have tried no to run apt-get purge and autoremove but there is nothing to clean out.

Now I work with following command.
$ for i in /*; do echo $i; find $i |wc -l; done
This lists the folders and inode number.
and I fount that /var had over 300k nodes
I will dig deeper on where exactly

What is creating the files in /var/spool/exim4/input ??

SSH picture

Result with Find size

mango@stensmango:/opt/mango/logs$ sudo find / -size +100M
find: /proc/26770/task/26770/fd/5': No such file or directory find: /proc/26770/task/26770/fdinfo/5': No such file or directory
find: /proc/26770/fd/5': No such file or directory find: /proc/26770/fdinfo/5': No such file or directory

@phildunlap

Hi this pictures was taken right after a cold boot.
And ALL backup are moved to an external disk.

Hi all !
Mango still has some issues.
There was not room for the temp files needed in the commands.
What is wrong ? Where do I find space?

mango@stensmango:/$ sudo du -ahx / | sort -rh | head -20
[sudo] password for mango:
Sorry, try again.
[sudo] password for mango:
sort: cannot create temporary file in ‘/tmp’: No space left on device
ot local

Filesystem from Webmin:

Please look at my error in the past with unaccessable Mango

I have described my problems in the past. Now it is happening again.
The Mango ES is not starting up the web service, or it is impossible to access.
This time there is no huge log files on the disk, and no way for me to find where or what is causing this overloaded disk. There is a brief error code in the Webmin interface when I try to get the system status that imply that the disk is full and the temporary file could not be created. The result is that I have deleted all obvious files as logs and other stuff to get some free space on the disk.
But no I can not access the Mango ES at all from the browser.
Please advis how I could find my Mango ES and clean the disk, and find why the disk gets full.
The system is very small so it should not be a problem.
My raspeberry is running a free version collecting all data into a modbus publishing then collected by the Mango ES and this is where I keep my status screen as a graphical view and some other data sources collected.
What do I do?

Hi!
I still have alarms but they are not as many.
I found that I get them when the system do backup.
see picture

//Per

Terry
I have now used the new garbage collector, for 24h
it seems to work better only one timeout alarm and that was when the backup of db had started.
The memory usage is down to 50% now.

/Per

I will try this !
Have just created the symbolic link, when I did this I saw that the memory usage between my two similar systems was significant different.
The MangoES system seems much more loaded that the installed free system on a raspberry Pi (V3)
Even when I have all my temp readings on the latter one(Pi) and publish them over my network as Modbus TCP to the Mango ES instance to read and present, could I optimize MangoES to use less memory? I notice that MangoES has no swap space!

My MangoES was getting slow after big log files both in in the OS files /var/log and in Mango opt/mango/logs They where inGB size eventually the MangoES did not start up at all.
So many alerts and errors could create problems like this,
//Per

The MangoEs has been running now for a few days with the latest sw upgrade, and I still got timeout alarms this is reported in another already existing thread.
All ports active now seem to work fine.
/Per