Log overflow with VideoQualityLayerLookup.transform#44: Unable to find encoding matching packet! #1703
Comments
|
The error remains after this update: |
|
Issue still present with latest stable jvb |
|
Still there with |
|
We are also experiencing this on Ubuntu 20.04. Our VM is hosted by Hetzner, like OP's is, too (coincidence or clue?). |
|
Same log, in debian 11 upated and stable jitsi updated on (VM Public Cloud OVH) : |
|
Not 100% sure yet, but using last stable jvb2 version (2.1-570-gb802be83-1) seems to fix that. |
|
I can confirm, that with the following versions, the warning is gone:
|
|
Happens here with a later version: Started only with my desktop browser, the messages appeared as soon as I joined with the iOS app which had a super-sharp video quality (note the component Also received a lot of #1769 when iOS enables video: |
|
Still having this. And streams get disabled "to save bandwith". |
|
Happening here for me with the following version |
|
For us, the error came back too, 23.880 of these errors yesterday only... |
|
Just from midnight to now (1pm) I got 909898 messages and there had just been 3 shorter meetings today with just ~4 participiants each. Is there anything what can be done to fix this? |
|
Try updating the latest from testing, those versions will soon be pushed to stable. |
|
The new stable is out, try it. |
|
Hey @damencho I have tested this against docker version stable-9646 and i still see the debug. Is the fix intended to be in this version? |
|
Can you share the message you see with the latest version? What is the scenario you test? Is it easy to reproduces? What browser versions dod you use to reproduce this? |
|
Hi, I can confirm, yesterday we still got a 144487 of these messages in a total of 668055 lines: JVB 2024-08-04 17:45:22.332 WARNING: [181] [confId=c4fba3a2d0995add conf_name=[email protected] meeting_id=541d968a epId=c954fa82 stats_id=Imelda-mpU] VideoQualityLayerLookup.transform#44: Unable to find encoding matching packet! packet=RtpPacket: PT=100, Ssrc=3442339265, SeqNum=1652, M=false, X=true, Ts=2811464945, EncID=-1, TID=-1; sources=MediaSourceDesc[name=c954fa82-v0 owner=c954fa82, videoType=CAMERA, encodings=primary_ssrc=312312174,secondary_ssrcs={2793454169=RTX},layers= This one comes up 43280 times too: JVB 2024-06-17 11:19:00.467 WARNING: [377] [confId=25876e56a78b0d98 conf_name=[email protected] meeting_id=e5728590 epId=05b03d9f stats_id=Reynold-E5h] SingleSourceAllocation.improve#133: Oversending above maxOversendBitrate, layer bitrate 758864.0 bps Versions: I am not able to reproduce this specifically, I can only see it in a production system. |
Sure: Aug 19 10:56:52 ip-10-0-1-10.ec2.internal matrix-jitsi-jvb[25110]: JVB 2024-08-19 10:56:52.401 WARNING: [73] [confId=e445df009f6fefdb conf_name=efggwt3kj5iu6q2tn5ze22sbn5uvcuz2orsxg5bomnwgkylsonygc3tvmmx The scenario was a two party jitsi vudei conference and seems to produce every time. Im using chrome Version 126.0.6478.126 (Official Build) (64-bit) and the lib jitsi meet client libraries |
|
Started seeing this issue today on docker-jitsi-meet stable-8960 with mostly participants on Chrome. Few of them were kicked out. Could it be related to latest chrome itself? |
Description
With a fresh install of jitsi-meet on an Ubuntu 20 server with a public IP address, we are seeing hundrets of these warnings in the jvb.log, just with one test conference:
JVB 2021-08-10 09:45:11.189 WARNING: [448] [confId=8de3eca41115067e epId=eb383b8a gid=127837 stats_id=Malinda-tZC [email protected]] VideoQualityLayerLookup.transform#44: Unable to find encoding matching packet! packet=RtpPacket: PT=96, Ssrc=3039135604, SeqNum=62186, M=true, X=true, Ts=3711187980; sources=MediaSourceDesc 1292347528 has encodings: primary_ssrc=2808700885,secondary_ssrcs={},layers= subjective_quality=0,temporal_id=0,spatial_id=-1 subjective_quality=1,temporal_id=1,spatial_id=-1 subjective_quality=2,temporal_id=2,spatial_id=-1 primary_ssrc=2343286782,secondary_ssrcs={},layers= subjective_quality=64,temporal_id=0,spatial_id=-1 subjective_quality=65,temporal_id=1,spatial_id=-1 subjective_quality=66,temporal_id=2,spatial_id=-1 primary_ssrc=2658891082,secondary_ssrcs={},layers= subjective_quality=128,temporal_id=0,spatial_id=-1 subjective_quality=129,temporal_id=1,spatial_id=-1 subjective_quality=130,temporal_id=2,spatial_id=-1Expected Behavior
No or little amount of warnings in the logs
Steps to reproduce
Just install jitsi-meet on an Ubuntu 20 VM (Hetzner in my case) and start a conference with Firefox and join the room with Chrome on the same machine (OS X). In our case: https://test.sichere-videokonferenz.de/
I did not change any configurations.
Environment details
root@test:/etc/jitsi/meet# dpkg -l | grep jitsi ii jitsi-meet 2.0.5963-1 all WebRTC JavaScript video conferences ii jitsi-meet-prosody 1.0.5056-1 all Prosody configuration for Jitsi Meet ii jitsi-meet-web 1.0.5056-1 all WebRTC JavaScript video conferences ii jitsi-meet-web-config 1.0.5056-1 all Configuration for web serving of Jitsi Meet ii jitsi-videobridge2 2.1-508-gb24f756c-1 all WebRTC compatible Selective Forwarding Unit (SFU)Also see https://community.jitsi.org/t/videoparser-transform-58-unable-to-find-encoding-matching-packet/60290
The text was updated successfully, but these errors were encountered: