You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
on my azuracast docker installation, the following occurs.
I have several playlists with long files 1 hour, so a complete show.
At the end of the playlist, it happens that the trigger for the next playlist
does not start the next playlist when the song file is longer then the actual playlist allows.
For example, a playlist gets triggered to play at 19:00 and ends at 20:00
when a song file is longer, let's say 62 minutes the next playlist not getting triggered.
Or when the song file is shorter and gets triggered again, it also will not play the next
playlist at the given time.
I examined the error further and it seems to have nothing to do with the file length
You see here when it happens, time get stuck and "skip song" button is greyed out.
Icecast show "running" Liquidsoap show "running".
When you click "skip song", azuracast totally crash and isnt available anymore, you have to go thru complete update proces.
Following errors during update process for a coupleof days/weeks not sure if they related.
Error response from daemon: remove azuracast_www_data: volume is in use - [671be27701d2cb8a5026df71d6963a077f5a27edc006efbc1b6f1f591a197015] Error response from daemon: remove azuracast_tmp_data: volume is in use - [671be27701d2cb8a5026df71d6963a077f5a27edc006efbc1b6f1f591a197015]
ERROR: for azuracast_cron You cannot remove a running container 671be27701d2cb8a5026df71d6963a077f5a27edc006efbc1b6f1f591a197015. Stop the container before attempting removal or force remove
ERROR: for cron You cannot remove a running container 671be27701d2cb8a5026df71d6963a077f5a27edc006efbc1b6f1f591a197015. Stop the container before attempting removal or force remove
ERROR: Encountered errors while bringing up the project.
Update complete!
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Hello,
on my azuracast docker installation, the following occurs.
I have several playlists with long files 1 hour, so a complete show.
At the end of the playlist, it happens that the trigger for the next playlist
does not start the next playlist when the song file is longer then the actual playlist allows.
For example, a playlist gets triggered to play at 19:00 and ends at 20:00
when a song file is longer, let's say 62 minutes the next playlist not getting triggered.
Or when the song file is shorter and gets triggered again, it also will not play the next
playlist at the given time.
I examined the error further and it seems to have nothing to do with the file length
You see here when it happens, time get stuck and "skip song" button is greyed out.
Icecast show "running" Liquidsoap show "running".
When you click "skip song", azuracast totally crash and isnt available anymore, you have to go thru complete update proces.
Following errors during update process for a coupleof days/weeks not sure if they related.
Error response from daemon: remove azuracast_www_data: volume is in use - [671be27701d2cb8a5026df71d6963a077f5a27edc006efbc1b6f1f591a197015] Error response from daemon: remove azuracast_tmp_data: volume is in use - [671be27701d2cb8a5026df71d6963a077f5a27edc006efbc1b6f1f591a197015]
`
Recreating azuracast_cron ... error
Creating azuracast_cli_1_71f620caa4a7 ... done
Creating azuracast_nginx_1_28d0bbb00c9d ... done
ERROR: for azuracast_cron You cannot remove a running container 671be27701d2cb8a5026df71d6963a077f5a27edc006efbc1b6f1f591a197015. Stop the container before attempting removal or force remove
ERROR: for cron You cannot remove a running container 671be27701d2cb8a5026df71d6963a077f5a27edc006efbc1b6f1f591a197015. Stop the container before attempting removal or force remove
ERROR: Encountered errors while bringing up the project.
Update complete!
The text was updated successfully, but these errors were encountered: