Reboot reason: Illegal memory access - Emailing HTML Report

Hello

I have reports in HTML being sent out and I have modified one of them and added more tags. The file size 12kb (was 2kb) and whenever I go to send this email with the attachment, it reboots.

What do the logs show? Can you make a backup with eBuddy and check “Include Support Files” so we can take a look at them?

12KB seems like a small amount of data to be causing a memory issue like this, but if you are using a lot of memory for tags and scripts, I guess it’s possible. You can view the memory resources under ‘Diagnostic > Status > System Counters > Memory Information’.

eWON.tar (256.5 KB)

Here is the log.

01/11/2022 06:35:05 26804 stdios-Device ENTERS slow poll mode (ABLOGIX - Address IP: 192.168.100.1) ablsrv
01/11/2022 06:35:05 -20205 pattern of 1 event muted 2 times ablsrv
01/11/2022 06:35:03 -20205 muting (pattern of 1 event) ablsrv
01/11/2022 06:35:03 26813 stdios-device TCP connect failed socket ablsrv
01/11/2022 06:35:02 26813 stdios-device TCP connect failed socket ablsrv
01/11/2022 06:34:53 22904 Reboot reason: Illegal memory access (0x2C48CC) wd
01/11/2022 06:34:52 -22602 System Booting, FWR: EW_11_3s0 (11.3), SN: 1711-0017-59 [EF0000] elog
01/11/2022 06:34:26 -20205 muting (pattern of 1 event) http
01/11/2022 06:34:18 -20205 unmuting after 1570 s http
01/11/2022 06:29:49 -20205 muting (pattern of 2 events) ftps
31/10/2022 18:05:38 26804 stdios-Device ENTERS slow poll mode (ABLOGIX - Address IP: 192.168.100.1) ablsrv
31/10/2022 18:05:38 -20205 pattern of 1 event muted 2 times ablsrv
31/10/2022 18:05:36 -20205 muting (pattern of 1 event) ablsrv
31/10/2022 18:05:36 26813 stdios-device TCP connect failed socket ablsrv
31/10/2022 18:05:35 26813 stdios-device TCP connect failed socket ablsrv
31/10/2022 18:05:26 22904 Reboot reason: Illegal memory access (0x2C39EC) wd
31/10/2022 18:05:25 -22602 System Booting, FWR: EW_11_3s0 (11.3), SN: 1711-0017-59 [EF0000] elog
31/10/2022 07:57:44 -20205 muting (pattern of 2 events) ablsrv
31/10/2022 07:57:44 7555 gio-IO change queue error ablsrv
31/10/2022 07:57:44 20105 pla-Queue error (Rd/Wr) ablsrv

I didn’t see anything in memory usage that shows it is all being utilized. It looks like there more is more than enough.

It looks like it’s not a problem with too much memory being used, but accessing an illegal memory address.

It is most likely due to the script. Can you move all the code into the Init Section in the script?

MOVED TO STAFF NOTE (260 KB)
Here is the back up with the script out.

Same results.

Hi @JosephM,

Have you tried factory resetting the device yet?

You can backup the tags and settings and put them back after.

Also, do you mind creating a case at https://support.hms-networks.com so that I can escalate it to the Ewon engineers? We’ll also get alerts when you respond so we can get back to you quicker. You don’t have to rewrite anything, just leaving a link to this thread would be fine. Thank you.

I asked the Ewon engineers about this and they said it might be a bug and unfortunately this device is obsoleted, so there will be no more updates. So you would have to troubleshoot it yourself (I would recommend trying the reset) or replace the device with a Flexy.

It was the file size that was causing the issue.

I broke the singular file into 3 different ones and attached all 3 files to the email and it worked.

Maybe this should be marked as the solution?

Thanks for the update. It’s marked as the solution now.