-
-
Notifications
You must be signed in to change notification settings - Fork 135
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
2.3.1 loops on "We must catchup" #4364
Comments
That log line shouldn't be a problem. Do you have more logs, in particular regarding clocks? Since CPU usage remains low, something must be off in the streaming loop. I'd also consider removing operators one by one until you cannot reproduce the issue anymore. |
Hi @toots, |
Yes! There's a
It would be an excellent idea to get metrics at this level to understand the bottleneck indeed. |
it turns out I can reproduce it with from the
but it only fails when one MP3 is in the folder. That file seems to cause a few occurrences of Said file is available for 7 days here, build config and debug log are here |
Thanks I'm testing it. Can you send logs with |
Also, I can't figure out the version you're using, could you give more details on it? |
Nevermind got it. |
I'm really unable to reproduce here. Could you do the following:
And send me the resulting file once you see a sufficient catchup. Also, could you try with the latest m |
I have the same problem/error: 2025/03/18 19:26:03 [clock.generic.8:2] We must catchup 17.89 seconds! and the playlist is only planed for thursday on 20 a Clock. but loaded outside of thursday with this log. And much other Playlists with other Dates and Times, with the same on the log. The Playlist Entry (only copied here the important data from the conf, it is correctly from azuracst and much more ): |
It might not be related :/ |
Thanks that is very much appreciated! I see two files in those logs and a safe blank. Do you have logs with the simple script or do I need a slightly more complex script? |
not sure I understand your question ; but that log is executing this script:
There was 3 files in the folder (but 2 from the same artist) |
Description
Since v2.3.0 , after a few (between 5 and 60) minutes of execution my script loops as follows:
Once in that loop, catchup time slowly increases.
Steps to reproduce
The script is mostly a combination of queues (complete script here) but this happens when queues were empty, so a
playlist
on a folder is playing. CPU use is low. The only suspicious log line above the loop isbut this appears a few (3 to 10) times before the catchup loop, it might be unrelated.
I'm trying to reproduce it in smaller scripts, but hardly could isolate something deterministic.
Expected behavior
Liquidsoap should catchup.
Liquidsoap version
Liquidsoap build config
Installation method
From OPAM
Additional Info
No response
The text was updated successfully, but these errors were encountered: