LuaUpnP crashing, termination code 137 and the strange ERGY plugin

Community Playground General Discussions
1

Hi everyone,

So last night all hell (sorry for my language) broke loose.
I have a Vera Light running the newest firmware.
The unit was running absolutely fine until last night.

Problem:
Whenever I run a scene or turn a light on or off the LuaUPnP crashes, then restarts. The yellow light on the Vera also turns off, then comes back on after 20 seconds. The termination code is 137. This started happening at 10/05/12 at approx 7:30pm. I did not make any changes to the unit before this happened, the unit was running fine. Whenever I run scenes (turn all light on, off, dimm all lights) this happenes. On the dashboard I get strange message as well when I turn off lights etc. It says: waiting for ack, then freezes and the LuaUPnP Engine restarts again :frowning:

This is from the logs:
05/10/12 19:36:04.013 Dumping 17 locks <0x2b7d7680>
02 05/10/12 19:36:04.013 finished check for exceptions <0x2b7d7680>
02 05/10/12 19:36:04.013 finished check for exceptions <0x2b7d7680>
02 05/10/12 19:36:04.014 finished check for exceptions <0x2b7d7680>
02 05/10/12 19:36:04.014 finished check for exceptions <0x2b7d7680>
02 05/10/12 19:36:04.014 finished check for exceptions <0x2b7d7680>
02 05/10/12 19:36:04.014 finished check for exceptions <0x2b7d7680>
02 05/10/12 19:36:04.015 finished check for exceptions <0x2b7d7680>
02 05/10/12 19:36:04.015 finished check for exceptions <0x2b7d7680>
02 05/10/12 19:36:04.015 finished check for exceptions <0x2b7d7680>5/10/12 Log for device LuaUPnP
192.168.1.201/cgi-bin/cmh/log.sh?Device=LuaUPnP 3/20
02 05/10/12 19:36:04.015 OL: (0xb01d84) (>2158) ThreadedClass …/JobHandler/JobHandler.cpp l:394 time: 4:00:00p (1336703764 s) thread: 0x2b0a3000 Rel: Y Got: Y
02 05/10/12 19:36:04.015 finished check for exceptions <0x2b7d7680>
02 05/10/12 19:36:04.016 OL: (0xcf7ce4) (>2352) Lua LuaInterface.cpp l:1739 time: DL7:34:52p (72 s) thread: 0x2b9d7680 Rel: N Got: Y
02 05/10/12 19:36:04.016 finished check for exceptions <0x2b7d7680>
02 05/10/12 19:36:04.016 OL: (0xc63a6c) (>2871) ThreadedClass …/JobHandler/JobHandler.cpp l:394 time: 4:00:00p (1336703764 s) thread: 0x2bbd7680 Rel: Y Got: Y
02 05/10/12 19:36:04.016 finished check for exceptions <0x2b7d7680>
02 05/10/12 19:36:04.017 OL: (0xc63a6c) (>2876) ThreadedClass …/ZWave/ZWaveJobHandler.cpp l:777 time: DL7:35:04p (60 s) thread: 0x2b7d7680 Rel: N Got: Y
02 05/10/12 19:36:04.017 finished check for exceptions <0x2b7d7680>
02 05/10/12 19:36:04.017 OL: (0xb01df4) (>2882) Variable Device_Basic.cpp l:446 time: 7:35:04p (60 s) thread: 0x2b7d7680 Rel: Y Got: Y
02 05/10/12 19:36:04.017 finished check for exceptions <0x2b7d7680>
02 05/10/12 19:36:04.018 OL: (0xb01df4) (>2888) Variable Device_Basic.cpp l:446 time: 7:35:04p (60 s) thread: 0x2b7d7680 Rel: Y Got: Y
02 05/10/12 19:36:04.018 finished check for exceptions <0x2b7d7680>
02 05/10/12 19:36:04.018 OL: (0xcf7ce4) (>2890) Lua LuaInterface.cpp l:1980 time: 7:35:04p (60 s) thread: 0x2b7d7680 Rel: N Got: N <0x2b7d7680>
02 05/10/12 19:36:04.018 finished check for exceptions <0x2b7d7680>
02 05/10/12 19:36:04.019 OL: (0xb01df4) (>3153) Variable JobHandler_LuaUPnP.cpp l:6709 time: 4:00:00p (1336703764 s) thread: 0x2e1d7680 Rel: Y Got: Y
02 05/10/12 19:36:04.019 finished check for exceptions <0x2b7d7680>
02 05/10/12 19:36:04.019 OL: (0xb01df4) (>3278) Variable JobHandler_LuaUPnP.cpp l:6709 time: 4:00:00p (1336703764 s) thread: 0x2dbd7680 Rel: Y Got: Y
01 05/10/12 19:36:04.019 Deadlock problem. going to reload and quit <0x2b7d7680>
03 05/10/12 19:36:04.020 JobHandler_LuaUPnP::Reload: deadlock Critical 1 m_bCriticalOnly 0 dirty data 1 <0x2b7d7680>
01 05/10/12 19:36:11.194 Main WatchDogRoutine: blocked - terminating 1 <0x2e3d7680>
02 05/10/12 19:36:11.196 Dumping 16 locks <0x2e3d7680>
02 05/10/12 19:36:11.196 finished check for exceptions <0x2e3d7680>
02 05/10/12 19:36:11.197 finished check for exceptions <0x2e3d7680>
02 05/10/12 19:36:11.197 finished check for exceptions <0x2e3d7680>
02 05/10/12 19:36:11.197 finished check for exceptions <0x2e3d7680>
02 05/10/12 19:36:11.197 finished check for exceptions <0x2e3d7680>
02 05/10/12 19:36:11.198 finished check for exceptions <0x2e3d7680>
02 05/10/12 19:36:11.198 finished check for exceptions <0x2e3d7680>
02 05/10/12 19:36:11.198 finished check for exceptions <0x2e3d7680>
02 05/10/12 19:36:11.198 finished check for exceptions <0x2e3d7680>
02 05/10/12 19:36:11.199 OL: (0xb01d84) (>2158) ThreadedClass …/JobHandler/JobHandler.cpp l:394 time: 4:00:00p (1336703771 s) thread: 0x2b0a3000 Rel: Y Got: Y
02 05/10/12 19:36:11.199 finished check for exceptions <0x2e3d7680>
02 05/10/12 19:36:11.199 OL: (0xcf7ce4) (>2352) Lua LuaInterface.cpp l:1739 time: DL7:34:52p (79 s) thread: 0x2b9d7680 Rel: N Got: Y
02 05/10/12 19:36:11.200 finished check for exceptions <0x2e3d7680>
02 05/10/12 19:36:11.200 OL: (0xc63a6c) (>2871) ThreadedClass …/JobHandler/JobHandler.cpp l:394 time: 4:00:00p (1336703771 s) thread: 0x2bbd7680 Rel: Y Got: Y
02 05/10/12 19:36:11.200 finished check for exceptions <0x2e3d7680>
02 05/10/12 19:36:11.200 OL: (0xc63a6c) (>2876) ThreadedClass …/ZWave/ZWaveJobHandler.cpp l:777 time: DL7:35:04p (67 s) thread: 0x2b7d7680 Rel: N Got: Y
02 05/10/12 19:36:11.201 finished check for exceptions <0x2e3d7680>
02 05/10/12 19:36:11.201 OL: (0xb01df4) (>2882) Variable Device_Basic.cpp l:446 time: 7:35:04p (67 s) thread: 0x2b7d7680 Rel: Y Got: Y
02 05/10/12 19:36:11.201 finished check for exceptions <0x2e3d7680>
02 05/10/12 19:36:11.201 OL: (0xb01df4) (>2888) Variable Device_Basic.cpp l:446 time: 7:35:04p (67 s) thread: 0x2b7d7680 Rel: Y Got: Y
02 05/10/12 19:36:11.201 finished check for exceptions <0x2e3d7680>
02 05/10/12 19:36:11.202 OL: (0xcf7ce4) (>2890) Lua LuaInterface.cpp l:1980 time: 7:35:04p (67 s) thread: 0x2b7d7680 Rel: N Got: N <0x2e3d7680>
02 05/10/12 19:36:11.202 finished check for exceptions <0x2e3d7680>
02 05/10/12 19:36:11.202 OL: (0xb033bc) (>3324) alarm AlarmManager.cpp l:109 time: 7:36:04p (7 s) thread: 0x2b7d7680 Rel: Y Got: Y <0x2e3d7680>
2012-05-10 19:36:11 - LuaUPnP Terminated with Exit Code: 137
2012-05-10 19:36:11 - LuaUPnP crash
01 2012-5-10 12:14:31 caught signal 6 <0x2c089680>

So basically I was not able to do anything with the unit. restore from abckup did not work, Repair did not work…
So I called the tech support. No luck :frowning: After 30min they asked me to open a ticket and we all know how long this takes…
Anyways… So I started thinking. 3 days ago I installed the ERGY Energy Plugin. I noticed that the system was a lot slower after the iinstall but did not think of this as a big issue.

Since I did not want to wait for couple of days and out of desperation I went ahead, deleted the ERGY plugin, removed the wattage info from the notes and bam… its working again like a charm…

My question is, has anyone observed this issue? Is anyone using ERGY? I am really getting kind of annoyed here. I am grateful Vera is working again but now I am unable to measure the energy usage… and there tech support soes not seem to know whats going on…

Flo >:( >:(

2

Ergy has always been an issue since day one and can cause the vera to slow down. It is one of the first things that I recommend to anyone who is having issues with their vera being slow and having the ergy plugin installed to remove it.

  • Garrett
3

Thanks Garrett,
I did not know that.
The unit is running better than ever after removing the plug in… but how do I measure my energy usage now…
Just sad :frowning: Its even more sad that MCV does not know or does not want to know about this… I told them I installed the Plugin 3 days ago - I would assume that if this really causes that many problems they would have advised me to delete it?

Happy friday though!

Flo

4

I am not positive, but I think they made some fixes in a private beta. One of the users states that ergy is working better for them. I can not confirm this as I will not touch the plugin. You can enter the energy values and use the basic usage in UI5 under the energy tab. Should be the last tab. It is not perfect, but at least you will still maintain your usage.

  • Garrett
5

Thanks Garrett,
I will try this.
And I also will never touch that plugin again!

Flo

6

I am sure in time things will get worked out.

  • Garrett
7

[quote=“garrettwp, post:6, topic:171487”]I am sure in time things will get worked out.

  • Garrett[/quote]
    Im sure it will…
    I am also positive that a version 0.99 plugin should NOT cause this.
    Anyways, since I can reproduce this… should I submit this bug or whatever it is to MCV? How would I do this?

Flo

8

Go to bugs.micasaverde.com and create an account. There you can submit a bug report. If one does not already exist.

  • Garrett
9

Thanks Garrett!
Have a good weekend.

Flo

10

We have notified the Ergy developers about this and they will investigate the issues you reported. Did you submit any tickets on the Ergy website?

11

MCVFlorin,
Thanks for your reply.

And thanks for letting the developers know.
I have not submitted any ticket and quite frankly I don’t think I will.
I just don’t want them to “poke around” on my unit which is working perfectly after deleting the plugin.

I don’t know if you can do that, but please feel free to submit my log files to them as well.
Also, are you saying that this is a plugin related issue? If so I do not have to open a bug report with MCV.

Please let me know.
Flo

12

On a second note,
I have the log file here on my computer. If you would like to take a look, let me know how to sent it to you :slight_smile:

Florian

13

@MCVFlorin

Same issue here:
http://forum.micasaverde.com/index.php/topic,10534.0.html

Florian