-
Notifications
You must be signed in to change notification settings - Fork 327
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Strange issue with 0.6.5 and MQTT Connector #597
Comments
Hello. This is a bug. Could you please post the crash.log as well? It contains more details. Also, what did happen before the crash (uplink, downlink, test button press)? |
It's happening when I change the handler in the connectors list, I tried to create new based on old one and it crashed even. Looks like searching something in config that does not find or match. It's not happening on receiving, just when trying to change configuration. Then when restarting the server, the server start but not listening on 8080 and not responding anymore. I tried a lot except restarting from scratch (no backup restore) Here the last crash log
|
Clear, thanks for the report. It is a bug, I will fix that tonight. |
I made a fix. The 0.6.6 is not released, however I updated |
@gotthardp the 0.6.6 version has the bug fixed, changing connector on web interface does not crash anymore. I looked into the crash log and looks like an MQTT connector issue, may why I don't receive any data. I created another connector test to another server from scratch, same issue.
|
Alright. Another bug, another fix was made. I should have done more testing. |
petr,
bitbake looks recompiling the lorawan-server (0.6.6) but at the end, installing the .ipk (with force reinstall option) on target didn't work. I suspected having an old version then
and then installed the ipk and all went fine. I think an option to display the build number (or commit number) in the web interface would really help to debug and be sure we use the correct version. |
Sorry for the confusion. I wanted to avoid releasing another buggy version. I will make 0.6.6 from what you have now. |
We've built the latest 0.6.5 version on multitech as usual and it's works fine.
Then we imported with dbimport and since that web interface is crashing (no more listening on port 8080) even if all the rest looks like to work
I investigated an found it's related on connectors side, so I deleted database, imported back all except connectors.json and then created connectors by hands. It works fine with the 2 following connectors:
But as soon as I create the 3rd connector as follow, the server crash, that's strange because it using the same handler than the websocket one.
here are the log of the server
Any hints on what's going on ?
The text was updated successfully, but these errors were encountered: