Skip to content
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

Unable to start concentrator. Shutting down. #81

Closed
sentry-io bot opened this issue Dec 23, 2021 · 4 comments
Closed

Unable to start concentrator. Shutting down. #81

sentry-io bot opened this issue Dec 23, 2021 · 4 comments
Assignees

Comments

@sentry-io
Copy link

sentry-io bot commented Dec 23, 2021

Sentry Issue: HM-PKTFWD-6

Unable to start concentrator. Shutting down.
@shawaj
Copy link
Member

shawaj commented Dec 31, 2021

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

@Kerrryu Kerrryu self-assigned this Jan 4, 2022
@Kerrryu
Copy link

Kerrryu commented Jan 4, 2022

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.

@Kerrryu
Copy link

Kerrryu commented Jan 4, 2022

@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

@shawaj
Copy link
Member

shawaj commented Jan 7, 2022

@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.

Kerrryu pushed a commit that referenced this issue Jan 10, 2022
* Silence issue #80 and #81 from showing on sentry
@Kerrryu Kerrryu closed this as completed Jan 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants