Engineio.client flooding log with errors

Third party integrations
1

I don’t exactly know when it started, but I noticed it a day or two ago. All of a sudden, my log is getting flooded with the following error, over and over.

2021-05-07 15:13:39 ERROR (MainThread) [engineio.client] packet queue is empty, aborting
2021-05-07 15:15:04 ERROR (MainThread) [engineio.client] packet queue is empty, aborting
2021-05-07 15:16:12 ERROR (MainThread) [engineio.client] packet queue is empty, aborting
2021-05-07 15:17:39 ERROR (MainThread) [engineio.client] packet queue is empty, aborting
2021-05-07 15:19:04 ERROR (MainThread) [engineio.client] packet queue is empty, aborting
2021-05-07 15:20:31 ERROR (MainThread) [engineio.client] packet queue is empty, aborting
2021-05-07 15:21:57 ERROR (MainThread) [engineio.client] packet queue is empty, aborting
2021-05-07 15:23:12 ERROR (MainThread) [engineio.client] packet queue is empty, aborting
2021-05-07 15:24:38 ERROR (MainThread) [engineio.client] packet queue is empty, aborting
2021-05-07 15:26:04 ERROR (MainThread) [engineio.client] packet queue is empty, aborting
2021-05-07 15:27:31 ERROR (MainThread) [engineio.client] packet queue is empty, aborting
2021-05-07 15:28:57 ERROR (MainThread) [engineio.client] packet queue is empty, aborting
2021-05-07 15:30:12 ERROR (MainThread) [engineio.client] packet queue is empty, aborting

In my searching, it seems like the most likely culprit is Ambient Weather, which I do use. However, nothing I do seems to change it. I’ve tried increasing the log level to debug - only new info was JSON updates of its status. Tried changing to fatal or critical to exclude the message - it still shows. Additionally, I don’t see anything wrong with my integration. It’s updating it’s status as it should, not dropping off or anything. I’m at a loss.

Of course it’s possible it’s coming from something else, but I’m running out of ideas on where (or how) to look. Nothing I seem to try helps to confirm where this is coming from, let alone why.

I’m sure I could add a filter to keep it out of the logs. And if it’s truly innocuous, I can do that. But it seems more like a Band-Aid than a true fix.

Any help is greatly appreciated

2

I just updated to 2021.5.1 and I’m seeing the same thing. I use Ambient Weather also.

3

At least I’m not alone. :grin:

4

I am also getting this error after updating from 2021.3.3 to 2021.5.1. I also use Ambient Weather. Hopefully someone with helpful information will chime in, soon.

5

Having the same problem, also using Ambient Weather.
I also noticed these errors in the DNS log (I run pihole if that matters)
[INFO] 172.30.32.1:39904 - 44066 “A IN api.ambientweather.net. udp 40 false 512” NOERROR - 0 6.002960119s
[ERROR] plugin/errors: 2 api.ambientweather.net. A: read udp 172.30.32.3:35685->192.168.20.1:53: i/o timeout
[INFO] 172.30.32.1:58734 - 49449 “AAAA IN api.ambientweather.net. udp 40 false 512” NOERROR - 0 6.001644836s
[ERROR] plugin/errors: 2 api.ambientweather.net. AAAA: read udp 172.30.32.3:38575->192.168.20.1:53: i/o timeout
[INFO] 172.30.32.1:34990 - 60128 “AAAA IN api.ambientweather.net. udp 40 false 512” NOERROR - 0 6.002384894s
[ERROR] plugin/errors: 2 api.ambientweather.net. AAAA: read udp 172.30.32.3:35880->192.168.20.1:53: i/o timeout

6

No DNS errors for me. Might be pihole specific (I’m not using it).

I went ahead and opened an issue for this.

2 Likes