Closed sentry-io[bot] closed 2 years ago
We have had cases of this where people have replaced the concentrator with a non Nebra one that we don't support. Just as an FYI that it's not always an issue on our side
Seems to be directly related to Issue #80. So the method retry_start_concentrator logs an exception error which then exits the while loop and triggers the other exception from this issue in start.
@vpetersson @shawaj
So we know that this can be caused by a 3rd-party concentrator installed in the device but it could also be an actual issue on some devices.
After looking into the issue we have 3 possible solutions:
1) We silence the error completely to prevent spam in Sentry (we are getting double the errors when this happens as per my comment above)
2) We determine the root cause of the issue and find a way to differentiate which concentrator is installed in the device.
3) As of now due to the docker containers restarting and such the error is being spammed in sentry by the devices affected. We can limit this to once a day per device but it would require us to write a flag to a file on the system that is reset by a cron task or a timestamp difference on boot up to check if it's eligible to report another error(this error only) to sentry
@SebastianMaj if we are duplicating issues then yes as a start let's remove the duplication
This could be an actual issue on some devices you are right, although I'm not sure it's a particularly useful thing to be sending to sentry as it's essentially a hardware issue, if anything.
Sentry Issue: HM-PKTFWD-6