-
-
Notifications
You must be signed in to change notification settings - Fork 5
Periodic Sync for Docker #21
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
Comments
Hey lucky, this should already be the case but it looks like something is broken with the scheduler, I'll take a look this evening. |
@luckycold sorry, it's taking a while to figure this out. I don't really understand what's not working, I think it's not pulling in the API key on the scheduled runs for some reason. |
It's entirely possible that this is user error. I don't typically have a custom app on my interface not "just work". I would guess K8s typically figures out health checks on its own. I'll look at the logs and see if there's anything about it that might be triggering the "backing off" error. If I find anything specific to the app or if I find out that it's something I fixed on my own I'll let you know. |
Nah I just figured it out, based on your previous issue, I'm guessing you're also syncing to multiple users? It's switching to the secondary users, and then trying to run again when its scheduled, but its still trying to auth with that other user instead of the default user again like it does at the beginning. Should have a fixed pushed shortly |
Funny enough, I actually have my users blank. So it's not multiple users for me. The longer I look at my setup I wonder how I got it to even work partially in the first place. |
Seems I'm actually getting an error saying this:
|
I can tell you I didn't originally have this error a month or two ago. I only decided to report this recently and now I'm a bit more confused at what's going on. |
And if it's not clear I do have all the environment variables set (except users being blank) |
Oh, yep you're correct in that it's a different issue, but I recently introduced that issue. I should be able to fix that, but I'm not sure why its happening. It looks like its prompting you to go through the manual setup, as if its not in a container. I wonder if TrueNAS Scale doesn't set up containers the same way as standard docker. Let me investigate. |
@luckycold Would you mind pulling in the "test" tag instead of latest and seeing what happens? I think (tentatively) that its fixed! You should be able to set the interval env variable to set the seconds between runs. |
If you're using lidarr, its not going to work, if you're manually inputting the playlists, it should be fine. I need to go back and fix the way its processing the lists now. |
You caught me right before I was heading to bed. I went ahead and did as you asked and got a switch user error shown here:
So I decided to put in my Plex username to see if that would fix it and no luck same error but slightly different message:
It's getting late on my end, so I'm going to continue this tomorrow. Thanks for your work though! |
@luckycold are you syncing from Lidarr or from a manual list? Manual lists are definitely working once I push this commit, but lidarr takes a while on my end because of the volume of playlists so I'm not 100% sure on it yet |
@cmathews393 Pretty sure I'm doing manual list. I've specified lidarr sync to false. Still the switchUser error. |
The manual list is just a link to the playlist, correct? |
Yeah, try repulling the image? Shouldn't be getting the user switch error anymore |
Okay, it seems that it didn't like me switching branches for that specific "custom app" I just reinstalled it and it seems to have worked. What would be a recommended interval? I tried 10 and it broke, then changed it to 600 and it seems stable now. |
Hmm describe broke? But I'd recommend like, 6 hours? Interval is in seconds, I think that's 21600? |
I've had it set to 30, and it's been running without issue for almost 24 hours. Try that and see if it loops and then I'd do longer, not sure what Spotifys API limits are,. |
When set to 10 I get this:
|
I got that error when I was testing stuff, but it was an issue with the loop, not with the scheduling... Hmm. I'll have to investigate |
Is your feature request related to a problem? Please describe.
I use a Kubernetes front end called TrueNAS Scale and it expects apps that continually run and this app thinks it's constantly failing and restarting with a "failed, backing off" error.
Describe the solution you'd like
Instead of having the app end after running once, it'd be nice to have it periodically restart the sync process on a regular interval (e.g. daily, hourly, etc.) as an option.
The text was updated successfully, but these errors were encountered: