SummaryWhen using the Exinda, the device may become sluggish and unexpectedly restart in v7. Upon further inspection, the RAM and the page file were both full and the process "collectord" was using the majority of it.
OverviewWhen using the Exinda, the amount of RAM should be known to be sufficient for an environment that it is placed in. However, rogue processes can start requiring more memory while refusing to let go of what it holds. When RAM is fully utilized, the process will request space from swap - a page file stored on the Exinda to provide back up memory space if required. In most normal operation, this should not be used on a regular basis.
In some cases in v7 of the Exinda firmware, it is possible that a process, collectord, will start consuming a large amount of RAM to the point where the RAM is full (between it and the other operating processes) and will start consuming space in the page file. Eventually, it will fill the entirety of the page file, leaving no memory for anything else in the system to request, and as a result, the Exinda will crash on the next request for memory. When the device is brought back online, collectord will be using a normal amount of RAM but still start slowly climbing until it repeats its earlier action.
CauseThe root cause of this is currently unknown.
WorkaroundThis bug only seems to affect Exindas that have the optimizer turned off. As a last ditch effort to prevent the Exinda from crashing, turn off the optimizer until a graceful restart can be preformed.
It is possible to schedule a reboot through the use of scheduled jobs on the Exinda (Configuration > System > Setup, the "Scheduled Jobs" tab). By entering the command restart force in the job and scheduling it for a repetition at a time of the administrator's choosing, it is possible to reboot the Exinda preemptively before collectord crashes.