Open Magicking opened 6 years ago
Oh, that's really strange, was this an isolated event or something you are able to reproduce?
I could reproduce this every time, the setup was 5 bulbs (4 identical) on the same WiFi and the build was https://github.com/lopter/lightsd/commit/9f976a67e2d0214dba13c8eef88aec9fb57db6fb
Have you tried to get some more info with a debug build? (cmake -DCMAKE_BUILD_TYPE=DEBUG …
).
I encountered this as well after re-compiling lightsd binary with newer gcc, glibc and more. Basically a more updated Linux OS overall. The hardware it runs on remained the same as always, it's just the software bits that are updated. Reverting to a lightsd binary compiled with older tools worked again.
Seeing as these two binaries I tried were built from the same source/version of lightsd, there seems to be some issue with lightsd when compiled with modern tools.
@lopter have you tried building lightsd with gcc 8? glibc 2.27 or 2.28? The latest libevent on my system is 2.1.8 and the latest cmake is 3.9.6.
When using the python client to get light state, the lightsd daemon segfault, here is the traceback:
ipython shell using lightsc.py
Lightsd: