I switched back to java se. I was able to get version 1.8.0 212-b10 installed. Hopefully this will be the fix.

I'm not positive if its the latest because version 8 of debian that is installed on the Mango Es doesn't have openjdk in the standard sources, only in the backports sources. Looks like maybe there is newer, but I can't see to locate a version for armv7l

Looks like the problem is back and worse. Three times this morning it crashed with this in the hs_err_pid log.

# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00000000, pid=13432, tid=0x6e20f460
#
# JRE version: OpenJDK Runtime Environment (8.0_171-b11) (build 1.8.0_171-8u171-b11-1~bpo8+1-b11)
# Java VM: OpenJDK Client VM (25.171-b11 mixed mode linux-aarch32 )
# Problematic frame:
# C  0x00000000

I installed openjdk 1.8.0 1069. Hopefully this will fix it. Thanks for the help.

There is a hs_err_pid log from when it stopped working

# A fatal error has been detected by the Java Runtime Environment:
#
#  Internal Error (cfgnode.cpp:706), pid=2021, tid=1902113888
#  Error: ShouldNotReachHere()
#
# JRE version: Java(TM) SE Runtime Environment (8.0_33-b05) (build 1.8.0_33-b05)

I have a mango es that I upgraded to from v2 to v3. It was originally stopping because it was in demo mode, but it now has a paid license on it. Every couple days since I put it into production the core just stops running. The ES is still on, I can access webmin and DGLux 5 server keeps running. The logs just stop running and don't show whats happening. I can start Mango again and its run fine until it stops again.

Where should I start looking?
Thanks

I changed the rollup to 720 hours, saved it, and then ran it. It locked up the mango for couple a minutes and didn't email the report. I went to the finished reports paged and clicked the download button. I get an error the file is not found. So I changed the time period to 720 hours. Now I get a report emailed with the correct time stamps, but incorrect data. One of the data fields is a timer that counts in second and it is only showing 57,600 seconds or 16 hours far away from the 720 hours it should be. I guess my next try will be to delete this report and try making one using myNamedRange.delta for all the fields.

So I still have a problem that when the report runs, it isn't including the correct date range. I have it scheduled to run on the first of the month and the time period is 30 days with 30 day delta rollup. The email I received this morning showed the time as Time - 2017/07/03 00:00:00 EDT to 2017/08/01 00:00:00 EDT. But the excel file has timestamps of 6/23/17 12:00AM to 7/22/17 12:00AM. Any ideas on how to fix that?

I also get a system exception when going into system settings that looks related.

org.apache.jasper.JasperException: javax.servlet.ServletException: javax.servlet.jsp.JspException: javax.servlet.jsp.JspException: javax.servlet.ServletException: File "/modules/excelReports/web/settings.jspf" not found

I'm not sure if the update solved my problem or created a new one. I have the report set to past 30 days with a 30 day rollup. The email body lists the correct date, but the time stamps in the excel file are incorrect.