If you want to completely clear out ERGY, here are the latest files that it places into [tt]/etc/cmh-ludl/[/tt]:
-rw-r--r-- 1 root root 1289 Jan 30 2013 I_ErgyX300Thermostat.xml
-rw-r--r-- 1 root root 354 Jan 30 2013 I_ErgyWebPowerIII.xml
-rw-r--r-- 1 root root 124 Jan 30 2013 I_ErgyWattNode.xml
-rw-r--r-- 1 root root 183 Jan 30 2013 I_ErgyPM800.xml
-rw-r--r-- 1 root root 350 Jan 30 2013 I_ErgyMSNPlug.xml
-rw-r--r-- 1 root root 6744 Jan 30 2013 D_EthernetPowerController.json
-rw-r--r-- 1 root root 3035 Jan 30 2013 D_ErgyX300Thermostat.xml
-rw-r--r-- 1 root root 135 Mar 25 2013 I_ErgyBlueLine.xml
-rw-r--r-- 1 root root 659 Mar 25 2013 D_ErgyBlueLine.xml
-rw-r--r-- 1 root root 865 Mar 25 2013 S_Irradiance1.xml
-rw-r--r-- 1 root root 403 Mar 25 2013 S_ErgyModbus.xml
-rw-r--r-- 1 root root 387 Mar 25 2013 I_SimpleLanWaterMeter.xml
-rw-r--r-- 1 root root 435 Mar 25 2013 I_EthernetPowerControllerIII.xml
-rw-r--r-- 1 root root 125 Mar 25 2013 I_ErgyPVPModbus.xml
-rw-r--r-- 1 root root 127 Mar 25 2013 I_ErgyPVM1010.xml
-rw-r--r-- 1 root root 212 Mar 25 2013 I_ErgyIR.xml
-rw-r--r-- 1 root root 151 Mar 25 2013 I_ErgyEKMMeter.xml
-rw-r--r-- 1 root root 780 Mar 25 2013 D_SimpleLanWaterMeter.xml
-rw-r--r-- 1 root root 4634 Mar 25 2013 D_SimpleLanWaterMeter.json
-rw-r--r-- 1 root root 9424 Mar 25 2013 D_IRSensor1.json
-rw-r--r-- 1 root root 905 Mar 25 2013 D_EthernetPowerControllerIII.xml
-rw-r--r-- 1 root root 817 Mar 25 2013 D_ErgyWattNode.xml
-rw-r--r-- 1 root root 826 Mar 25 2013 D_ErgyPVPModbus.xml
-rw-r--r-- 1 root root 658 Mar 25 2013 D_ErgyPVM1010.xml
-rw-r--r-- 1 root root 861 Mar 25 2013 D_ErgyPM800.xml
-rw-r--r-- 1 root root 543 Mar 25 2013 D_ErgyMSNPlug.xml
-rw-r--r-- 1 root root 1054 Mar 25 2013 D_ErgyIR.xml
-rw-r--r-- 1 root root 853 Mar 25 2013 D_ErgyEKMMeter.xml
-rw-r--r-- 1 root root 128 Mar 25 2013 I_ErgyTED5000.xml
-rw-r--r-- 1 root root 122 Mar 25 2013 I_ErgyEGauge.xml
-rw-r--r-- 1 root root 546 Mar 25 2013 D_ErgyWebPowerIII.xml
-rw-r--r-- 1 root root 869 Mar 25 2013 D_ErgyTED5000.xml
-rw-r--r-- 1 root root 811 Mar 25 2013 D_ErgyEGauge.xml
-rw-r--r-- 1 root root 776 Jul 22 2013 S_Pulse1.xml
-rw-r--r-- 1 root root 376 Jul 22 2013 I_ErgyOmnimeter.xml
-rw-r--r-- 1 root root 657 Jul 22 2013 D_PulseMeter1.xml
-rw-r--r-- 1 root root 693 Jul 22 2013 D_OmniPulseOutput1.xml
-rw-r--r-- 1 root root 5119 Jul 22 2013 D_OmniPulseOutput.json
-rw-r--r-- 1 root root 6484 Jul 22 2013 D_ErgyPulseMeter.json
-rw-r--r-- 1 root root 914 Jul 22 2013 D_ErgyOmnimeter.xml
-rw-r--r-- 1 root root 7083 Jul 22 2013 D_ErgyOmnimeter.json
-rw-r--r-- 1 root root 3555 Sep 10 05:46 L_SimpleLanWaterMeter.lua
-rw-r--r-- 1 root root 4660 Sep 10 05:46 L_EthernetPowerControllerIII.lua
-rw-r--r-- 1 root root 8026 Sep 10 05:46 L_ErgyX300Thermostat.lua
-rw-r--r-- 1 root root 3829 Sep 10 05:46 L_ErgyWebPowerIII.lua
-rw-r--r-- 1 root root 1951 Sep 10 05:46 L_ErgyWattNode.lua
-rw-r--r-- 1 root root 6939 Sep 10 05:46 L_ErgyPVPModbus.lua
-rw-r--r-- 1 root root 7543 Sep 10 05:46 L_ErgyPM800.lua
-rw-r--r-- 1 root root 12109 Sep 10 05:46 L_ErgyOmnimeter.lua
-rw-r--r-- 1 root root 8191 Sep 10 05:46 L_ErgyIR.lua
-rw-r--r-- 1 root root 5449 Sep 10 05:46 L_ErgyEGauge.lua
-rw-r--r-- 1 root root 5071 Sep 10 05:46 L_ErgyTED5000.lua
-rw-r--r-- 1 root root 5395 Sep 10 05:46 L_ErgyPVM1010.lua
-rw-r--r-- 1 root root 4899 Sep 10 05:46 L_ErgyMSNPlug.lua
-rw-r--r-- 1 root root 2936 Sep 10 05:46 L_ErgyBlueLine.lua
-rw-r--r-- 1 root root 7974 Oct 2 03:47 L_ErgyEKMMeter.lua
-rw-r--r-- 1 root root 12276 Nov 19 06:16 D_PowerMeter1.json
-rw-r--r-- 1 root root 18571 Nov 19 06:16 D_Heater1.json
-rw-r--r-- 1 root root 38863 Nov 19 06:16 D_HVAC_ZoneThermostat1.json
-rw-r--r-- 1 root root 15300 Nov 19 06:16 D_DimmableLight1.json
-rw-r--r-- 1 root root 12809 Nov 19 06:16 D_BinaryLight1.json
-rw-r--r-- 1 root root 577 Feb 7 12:02 S_EchoEnergyManager.xml.lzo
-rw-r--r-- 1 root root 49054 Feb 7 12:02 L_EchoEnergyManager.lua.lzoenc
-rw-r--r-- 1 root root 3560 Feb 7 12:02 J_EchoEnergyManager2.js.lzoenc
-rw-r--r-- 1 root root 715 Feb 7 12:02 J_EchoEnergyManager.json.lzo
-rw-r--r-- 1 root root 13058 Feb 7 12:02 J_EchoEnergyManager.js.lzoenc
-rw-r--r-- 1 root root 526 Feb 7 12:02 I_EchoEnergyManager.xml.lzoenc
-rw-r--r-- 1 root root 734 Feb 7 12:02 D_EchoEnergyManager.xml.lzo
-rw-r--r-- 1 root root 30753 Feb 7 12:02 extra_ergy_files.tar.gz
I built this as a reference list for disabling/removing ERGY and the list was built using a “clean” VeraLite unit, after simply enabling the ERGY functionality (ERGY Plugin 2.0). There are some questionable overlay files in this list that will raise a few eyebrows, especially in the upgrade case (not the issue at hand), but that’s a different discussion.
Clearing these out will save ~300K of flash from the overlay, and presumably stop wasted stuff being pulled into LuaUPnP memory (although I can’t recall if they pull it all in, or on first-use)
At 22:01:37 the procmgr catches a SEGV (Signal 11) from LuaUPnP, it’s very sudden.
01 2014-2-6 22:1:37 caught signal 11 <0x2b797680>
This is likely the real problem they’re trying to chase down, and why they’re asking you to disable some plugins (presumably to reduce/isolate the complexity of the debug)
Normally this is done in a much more “verbose” (and orderly) type of shutdown. This one is different in that it’s extremely abrupt, which is likely causing them to scratch their heads
BTW, Looking at the data from Chris’s collector, your memory is running just fine. I’m not sure what Richard saw in the log that had him concerned about memory issues, but I’m sure he’ll chime in with data from your logs shortly.
Here are your memory stats in the minutes before the SEGV occurred (lines shortened for readability):
[code]02/06/14 21:51:33.101 Device_… device: 81 service: urn:cd-jackson-com:serviceId:SystemMonitor variable: memoryTotal was: 127456 now: 127456
02/06/14 21:51:33.102 Device_… device: 81 service: urn:cd-jackson-com:serviceId:SystemMonitor variable: memoryFree was: 76976 now: 76836
02/06/14 21:51:33.103 Device_… device: 81 service: urn:cd-jackson-com:serviceId:SystemMonitor variable: memoryBuffers was: 0 now: 0
02/06/14 21:51:33.104 Device_… device: 81 service: urn:cd-jackson-com:serviceId:SystemMonitor variable: memoryCached was: 22128 now: 22172
02/06/14 21:51:33.111 Device_… device: 81 service: urn:cd-jackson-com:serviceId:SystemMonitor variable: memoryUsed was: 50480 now: 50620
02/06/14 21:51:33.112 Device_… device: 81 service: urn:cd-jackson-com:serviceId:SystemMonitor variable: memoryAvailable was: 99104 now: 99008
02/06/14 21:56:33.101 Device_… device: 81 service: urn:cd-jackson-com:serviceId:SystemMonitor variable: memoryTotal was: 127456 now: 127456
02/06/14 21:56:33.102 Device_… device: 81 service: urn:cd-jackson-com:serviceId:SystemMonitor variable: memoryFree was: 76836 now: 76808
02/06/14 21:56:33.103 Device_… device: 81 service: urn:cd-jackson-com:serviceId:SystemMonitor variable: memoryBuffers was: 0 now: 0
02/06/14 21:56:33.103 Device_… device: 81 service: urn:cd-jackson-com:serviceId:SystemMonitor variable: memoryCached was: 22172 now: 22208
02/06/14 21:56:33.108 Device_… device: 81 service: urn:cd-jackson-com:serviceId:SystemMonitor variable: memoryUsed was: 50620 now: 50648
02/06/14 21:56:33.108 Device_… device: 81 service: urn:cd-jackson-com:serviceId:SystemMonitor variable: memoryAvailable was: 99008 now: 99016
02/06/14 22:01:33.101 Device_… device: 81 service: urn:cd-jackson-com:serviceId:SystemMonitor variable: memoryTotal was: 127456 now: 127456
02/06/14 22:01:33.102 Device_… device: 81 service: urn:cd-jackson-com:serviceId:SystemMonitor variable: memoryFree was: 76808 now: 76652
02/06/14 22:01:33.103 Device_… device: 81 service: urn:cd-jackson-com:serviceId:SystemMonitor variable: memoryBuffers was: 0 now: 0
02/06/14 22:01:33.103 Device_… device: 81 service: urn:cd-jackson-com:serviceId:SystemMonitor variable: memoryCached was: 22208 now: 22300
02/06/14 22:01:33.108 Device_… device: 81 service: urn:cd-jackson-com:serviceId:SystemMonitor variable: memoryUsed was: 50648 now: 50804
02/06/14 22:01:33.109 Device_… device: 81 service: urn:cd-jackson-com:serviceId:SystemMonitor variable: memoryAvailable was: 99016 now: 98952
[/code]
My Vera 3 runs with significantly less free/available memory than yours is reporting, has a lot more active logs, and is merrily ticking along (after much micro-surgery in 2013). Not sure why your memoryBuffers never reports non-Zero, but it’s that way either side of the restart(s)
You are also still getting the Z-Wave CAN problems with the Z-Wave dongle, so the MCV support team should spend some time understanding why those are occurring. I have none of these in my current system, but have had them a few yrs back, and MCV had to spend time diagnosing the problems. I doubt this is causing it to crash, per-se, but the logs should be clean of these.
Ultimately, the MCV support team need to deep dive into why you are seeing the SEGV problem. I can see why they want certain plugins disabled, since they have the last activity just before death but this could just be a co-incidence (without more data it’s hard to id a pattern).
If they’re doing standard development stuff, they’re likely just reducing the variables they have to look at. Just don’t let them off the hook for the real diagnosis once you do disable them
That said, it’ll be the overall frequency of these crashes/instability that will drive their attention.
When you started the thread, it was every 45 seconds. It’s not clear if that’s gotten generally better or not yet, but having numbers to support your case (frequency of occurrence) would definitely bolster any case being made