-
Notifications
You must be signed in to change notification settings - Fork 386
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
Recurring error messages (every night) #1020
Comments
hb-service logs | grep "timeout of 5000ms exceeded" |
Yes, you're right. The backup is created at the same time. And I don't see that as a problem either. I was just curious why the message shows up so regularly in my log (and not only in mine). However, that doesn't mean I understand it now. |
I have the same issue since sometime in December. I haven’t changed anything on my setup, |
Same "problem" here! |
if you disable backup, the message disappears, so it should be related to the backup function... |
Please try the current test version and see if the timeouts persist. https://github.com/oznu/homebridge-config-ui-x/wiki/How-To-Test-Upcoming-Changes |
This should happen less often now as the traffic to npm is spread over a 7 hour window. If it does happen on occasion then it's just an informational log and nothing to be worried about. |
Describe The Bug:
Is it a bug or a feature? For many people I know from a homebridge forum, and also for me, these messages show up in the log every night at the same time:
This is 0:15 UTC. The list depends on how many plugins are installed.
Of course, I checked the link in the log entry but this isn't too helpful. I completely understand what it says, but I wonder why (all?) homebridge-config-ui-x installations do that at all. It looks to me like npmjs.org doesn't want to respond anymore because of too many hits.
To Reproduce:
hb-service logs | grep "timeout of 5000ms exceeded"
Expected behavior:
n/a
Logs:
Homebridge Config:
Standard stuff. This happens with many, very different configurations.
Screenshots:
Environment:
The text was updated successfully, but these errors were encountered: