Closed jceloria closed 5 years ago
Thanks for reporting and providing logs :-)
I have been able to reproduce this issue and will release a fix asap.
Wow, that was fast. Thank you!
On Fri, Feb 15, 2019, 6:22 AM Orne Brocaar notifications@github.com wrote:
Thanks for reporting and providing logs :-)
I have been able to reproduce this issue and will release a fix asap.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/brocaar/lora-app-server/issues/295#issuecomment-464029648, or mute the thread https://github.com/notifications/unsubscribe-auth/ABSrYJgFdP9DiDaXmf_lbBzsMVlaLjOTks5vNqZ0gaJpZM4a8T_u .
Is this a bug or a feature request?
bug
What did you expect?
InfluxDB integration
What happened?
panic: runtime error: invalid memory address or nil pointer dereference signal SIGSEGV: segmentation violation
What version are your using?
docker-ce-18.09.2-3.el7.x86_64 lora-app-server: 2.5.0 lora-gateway-bridge: 39c91ac lora-geo-server: cc6bb5c loraserver: cbf1ecd postgres:9.6-alpine redis:5-alpine eclipse-mosquitto: 1.5.6
I was using version 2 of the lora* containers before upgrading to latest
I'm using TEKTELIC Kona All-in-One Home Sensors with a Laird RG1xx gateway (Laird Linux gatwick-laird-93.7.3.4) configured with the MQTT forwarder (which frequently disconnects for some reason). I am using a slightly modified JS decoder from https://github.com/SensationalSystems/tektelic-kona-decoder for the payload
How can your issue be reproduced?
When I trigger an event on the node by placing a magnet near the reed switch sensor, I see the decoded message published to the topic:
I then immediately see the panic/SIGSEGV in the logs and the service crashes.
Could you share your log output?
log.txt