Can anyone explain what “Exit Code 139” is? The luup engine of my vera keeps rebooting, vera unusable at the moment, happened over night, no changes were made…
2012-03-10 08:38:59 - LuaUPnP Terminated with Exit Code: 139In Unix tradition, exit code 139 is signal 139-128=11, segmentation fault. This could be a null pointer dereference or heap corruption. It’s undeniably a bug, but the cause could be pretty much anything.
thanks futzle.
do you have any approach I could use for finding the problem? I just don’t know where to start, no changes were made to the vera, no usable errors are shown in the log.
Could you post some lines from the log just before the ‘139’ line?
You could try deactivating plugins by renaming the corresponding files in [tt]/etc/cmh-ludl[/tt].
Even if nothing changed on your end, LuaUPnP might have changed in how it interacts with the Internet at large (say, timing), or a new variable could have popped up in a device, or a Z-Wave device could have drifted subtly out of range.
If you have backups, see if you can find the last one that worked, and the first one that doesn’t. If none of the backups work, even those from a time that you didn’t have the problem, then it’s more likely to be environmental. Also, disable plugins and remove devices until you hit stability, then add stuff back in until you cause the error again (or, if you don’t cause it, be happy and move on).
Finally, alert MCV tech support. Mentioning that there is a segfault is going to get their attention.
This is what shows up in the log.LuaUPnP. If i tail -f the log on the vera i see a new segfault every ~20-30 seconds.
I didn’t found out which software it is but here’s the developers website, maybe one of you guys find anything helpful.
(sorry i’m not allowed to post external links: → google Thomas Krennwallner)
Copyright (C) 2000-2004 Thomas Krennwallner <krennwallner@aon.at>
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Segmentation fault
wol 0.7.1
Copyright (C) 2000-2004 Thomas Krennwallner <krennwallner@aon.at>
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Segmentation fault
wol 0.7.1
Copyright (C) 2000-2004 Thomas Krennwallner <krennwallner@aon.at>
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
set_close_on_exec 10
Error doing statfs on '/etc/cmh/persist/'.
Reloading
2012-3-10 13:17:19 caught signal 6 <0x2c307680>
wol 0.7.1(guest post from chixxi’s roomie – kru ; i was not allowed to post this?!)
WOL = Wake on LAN. WOL 0.7.1 Relates to the original Linux magic packet software… Try removing WOL.
thank you, we will remove the wol vera plug-in.
the wol binary itself seems to work. maybe the dev of the wol vera plug-in calls it in a strange way? but it looks like the segfault comes from there.
i think chixx will keep u informed.
Greetings – kru
It may sound a little weird, that even though I identify WOL, that may not be the root cause. I remember years back there were problems relating something alike this error with Linux and WOL abending; however, the root cause was to do with media players activities over the LAN. You need to search google to test my memory and I only mention this because I see Chixxi is the developer of popcorn hour plugin. Has you done any dev work recently because the WOL hasn’t changed as far as I know.
I am getting 139’s all the time as well (no wol plugin) I was getting 245’s all the time prior to the beta (this is a one for one replacement ie now only 139’s) This pretty much has removed my ability to add any complex device (other then on off switch)
i also think its not the primary problem. because i can execute wol with any switches and can’t reproduce a segfault.
At the moment the vera is in a more or less stable condition i think, also the segfault is gone from the log. but i’m not sure if it’s because we removed the wol plug-in…
Could it be since you added a new device and the luup engine restarted as well as maybe later at night when doing a heal? Just throwing some ideas out there.
- Garrett