I can confirm as well that my Stirr docker is staying up now and is stable, though I have yet to re-add it to Channels. I never turned it off, so it seems like something corrected itself for sure!
EDIT: I added it back and it remembered all by favorites/unfavorites, so that was so nice! And even though it gave them new channel numbers, it still understood where they were in my Channel Collections. All and all, seems a-OK!
I have been getting this same error on Synology Docker from time-to-time. The problem will resolve itself, then come back again - sometimes hours, days, or maybe months later. I've confirmed I'm using the "latest" image from DockerHub dated April 28, 2021.
The error causes the Docker container to crash. The container is configured to auto-restart. Restarts are continual up to the maximum restart interval (1 minute).
Log entries show the following "triplet" entries for each restart of the container.
Beginning cache fill
Found 111 channels in lineup, getting channel metadata and guide. This may take a moment.
..Error when filling cache unexpected end of JSON input
The number of "dots" before the word "Error" in the third log entry can vary per occurrence. For example, all the log entries in today's occurrence have 2 "dots". The number of "dots" from a few days ago was different.
I do wish robbiet480 could address this error or provide some sort of recovery in the container.
I'm having this issue now!
2022/07/08 13:10:18 STIRR_STATION_ID env var not set, attempting to auto detect local station
2022/07/08 13:10:20 Local station identified as national
2022/07/08 13:10:20 Beginning cache fill
2022/07/08 13:10:20 Found 111 channels in lineup, getting channel metadata and guide. This may take a moment.
2022/07/08 13:10:20 Error when filling cache unexpected end of JSON input
can anyone help???
I am seeing the same thing in my logs but the content is playing okay. So it is recovering quick in my case.
Yup... getting the same JSON input error here too...
A new version of the docker container is available with a fix.
It's working now!
Thank you!
Awesome! The new docker container works!
Looking at the log, it appears there is still an error with one of the channels. However, the new container now posts the error and continues processing the rest of the channels.
Thanks for posting the new container with the recovery code.
sadly, it still isn't working for me on my Synology 218+
A new latest image was pushed on July 30. Make sure you're running the latest image.
For about the last week or so my stirr docker from robbie has not worked. It just keeps restarting in docker on my pc. Anyone else having an issue?
I seemed to have that issue, but I chalked it up to my image as being outdated as the last pull was over a year ago. I redid the setup and it seems to work now -- although there was a bit where it did a couple restarts before it came through.
As a reminder, you could also just use Hank's links
as robbie himself had mentioned in the first post...
Yes, there was a bug in the docker code causing it to error out when there was bad data sent from Stirr. @tmm1 posted a fix for the GO code which avoided this error, which is incorporated into the nocords.xyz links, but I'm not sure if it's been merged into the original docker repo.
Check the link above for the 'non-docker' links, I think it's discussed there about 1-2 months ago.
My issue did resolve itself after a few days & some restarts. I dont believe both the fix & original docker was ever merged.
this is weird ... when starting a fresh install of the container i'm seeing this
After some time it may or may not go away. When opening the link in Chrome, i get the 403 forbidden but opening the link in any other browser it works fine and i see Stirr data.
Browser problem? I've only installed chrome just for channels and have never used it as a browser so everything is as default as it gets.
I had to restore my mac mini from backup and resulted in resetting up docker stuff. Got pluto going, but when I tried stirr be reexecuting the command to load it, it went through the normal messages and then ended with the following and though it appears to be running, Channels won't show channels on the Stirr source.
Error response from daemon: driver failed programming external connectivity on endpoint stirr-for-channels (long code i didn't retype here): Bind for 0.0.0.0:8080 failed: port is already allocated.
Any ideas?
Some other container is already using that port
My suggestion is that instead of the Docker approach, you consider using the Stirr links provided by @HankLloydRight at https://nocords.xyz/, as it’s much easier.
Thanks, I'm guessing its Docker. Any suggestion on what port I could set it to? I had all this working great for a long time so don't recall what I did and wasn't expecting all the Docker stuff to be lost.
I also have a problem that after reboot Docker is in a "Docker Engine waiting..." state.
