[Ovmsdev] Queue overflows
Chris van der Meijden
chris at arachnon.de
Mon Jan 11 18:15:52 HKT 2021
I know that one too.
Happens to me always, when I get CAN Errors when I wake up the CAN 3
Bus on the VW e-Up.
Greetinx from Bavaria
Am Montag, den 11.01.2021, 11:44 +0200 schrieb Steve Davies:
> I generally debug by watching the shell via the web interface with
> logging from my vehicle module at debug or verbose.
> I seem to be hitting throughput limitations for the websocket pushing
> the output to my client, though, and see many of these:
> log.20210110-144200:2021-01-10 14:17:39 SAST W (1630612) websocket:
> WebSocketHandler[0x3f8531a4]: job queue overflow resolved, 133 drops
> This especially happened when I went to a charger for a test and was
> connected to the OVMS system on 192.168.4.1 on the local Wifi AP that
> the OVMS creates.
> Is this to be expected? Is it more efficient to "log monitor" via
> ssh, or do I really need a serial connection over USB?
> I do see that the websocket overflows seem to occur when any client
> is connected whether you are looking at the shell or not. In my case
> I'm logging quite a lot and I guess I exceed the 100 deep queue.
> I see that I can make the queue bigger for the websocket - would it
> be a big problem to increase the 100 to 200 by default?
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OvmsDev