Closed bland328 closed 7 years ago
After posting this, I did some more googling, and learned that "signal: killed" is what I might see if I've run out of memory.
So, I started hklifx up again and used the top command to monitor RAM utilization.
I find the daemon slowly consumes more and more memory; after running for only 10 minutes, hklifxd is using 5.5% of memory.
So, I'd say this is likely related to other reports of RAM consumption.
Please refer to the linked issue on how to resolve the memory issue.
Summary: After working for minutes or hours, hklifx unexpectedly terminates with a "signal: killed" message.
Configuration: Latest (as of 2017-03-21) hklifx running under go1.7 on a Raspberry Pi 3 Model B running Raspbian 4.4.38-v7+, and controlling two (2) "Gen 2" LIFX Color 1000 bulbs
Observations: hklifx used to work perfectly for me for months at a time controlling two (2) "Gen 2" LIFX Color 1000 bulbs.
Eventually, I added one of the newer "Gen 3" LIFX A19 bulbs, and hklifx began working for only minutes or hours at a time; I can't say for certain if was the addition of the third bulb, the updating of other bulbs' firmware, the updating of hklifx, or possibly something else that precipitated the change in hklifx's behavior.
For a while, I assumed hklifx was choking on the "Gen 3" bulb, and hoped a new release would fix things up.
Recently, however, I removed the new bulb, and find hklifx is still unhappy for some reason.
Output: Below is the verbose output of everything from starting hklifx to watching it terminate, all without operating the bulbs at all: