Home/Support/Support Forum/Memory consumption issues with ConnectPort X4
Welcome to Digi Forum, where you can ask questions and receive answers from other members of the community.

Memory consumption issues with ConnectPort X4

0 votes
Hi all,
I am having a memory consumption issue with the ConnectPort X4 running Dia that I need help with.

When I boot the ConnectPort X4 at the start of the day, I have 1707 KB free memory. After several hours (overnight), I only have 30KB available and ,of course, the unit is not very responsive. If I reboot, I go back to 1707 KB free memory. The log file does not show anything unusual.

What is consuming the memory and how do I prevent the problem without having to reboot every day?



Some background info:

I have a ConnectPort X4 with a BL4S100 running the gpio_Server_C application.

BL4S100 - Only 1 Analog input and 1 Digital output compiled in and reporting

(1) Digi Bridge Router - Temp / Light sensor
(1) Digi Battery powered Light Temp sensor
NTP Time server on the X4.

The ConnectPort X4 is set to poll the BL4S100 once every 5 seconds. The two sensors push data up every 5 seconds
The NTP server updates the time once a day.

Firmware Version: 2.8.4.7 (Version 82001536_E 03/31/2009)
Boot Version: 1.1.3 (release_82001531_A)
POST Version: 1.1.3 (release_82001537_F)
Product VPD Version: release_82001747_A
Product ID: 0x0074
Hardware Strapping: 0x0043

Any thoughts would be appreciated
asked Aug 20, 2009 in Python by apineda Community Contributor (65 points)

Please log in or register to answer this question.

20 Answers

0 votes
What version of the iDigi Dia are you using?

If you don't know offhand, this info can be found in the dia.py file next to the field "DIGI_DIA_BOOTSTRAP_VERSION".
answered Aug 20, 2009 by Admin Veteran of the Digi Community (732 points)
0 votes
DIGI_DIA_BOOTSTRAP_VERSION = "1.1.15"
answered Aug 20, 2009 by apineda Community Contributor (65 points)
0 votes
The memory leak you are experiencing is a known ConnectPort X firmware leak.

The leak will be addressed in the next version of firmware which is due out in September.


Jordan
answered Aug 20, 2009 by jordanh Community Contributor (92 points)
0 votes
Thanks,
Is there any workaround other than rebooting? Or is there a specific function that I should avoid to prolong the uptime until the firmware fix is available?
answered Aug 20, 2009 by apineda Community Contributor (65 points)
0 votes
The leak is a small leak that happens each time that the gateway does a DNS lookup. The best workaround right now would probably be to replace lookups that occur often with the IP address of the host being contacted.

The most common place where we have seen this be an issue is in devices configured for remote management through iDigi. If you have a domain name configured for the server address and are using the cwm_data presentation in Dia, the server address will be looked up each refresh interval.
answered Aug 20, 2009 by DigiGuy42 Community Contributor (102 points)
0 votes
Excellent, That gives me a good place to go look. I will try to eliminate DNS lookups and see if that helps.
answered Aug 20, 2009 by apineda Community Contributor (65 points)
0 votes
I switched all references from Domain Name to IP address and it seems to have resolved the issue.
Thanks for your help.
answered Aug 21, 2009 by apineda Community Contributor (65 points)
0 votes
Hopefully a pre-build for the X4 will be created to solve this sooner than Sep 2009.
answered Aug 21, 2009 by lynnl Veteran of the Digi Community (1,047 points)
0 votes
That would be great. Although changing the Domain names to IP addresses helped a lot, I am still losing a little memory when I check every hour or so.I will still have to reboot every few days or so to keep up the amount of free memory.
answered Aug 21, 2009 by apineda Community Contributor (65 points)
0 votes
Okay, the fixed firmwares are up (or going up) on the support.digi.com site now. You need:
X2 = 82001596_E2.bin
X2-WiFi = 82001630_E1.bin
X4 = 82001536_E3.bin
X8 = 82001115_F2.bin

They should be dated August-24-2009 (or 25th). If dated March or May 2009, those are older.

The cellular products also have new images, but I won't list all of those. The memory issue only is seen with code using DNS name lookup - so a cellular customer putting a DNS name in Surelink or other settings will cause the problem.
answered Aug 28, 2009 by lynnl Veteran of the Digi Community (1,047 points)
...