Skip to content
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

logs not really working (maybe only on kubernetes?) #6

Open
madejackson opened this issue Aug 5, 2024 · 3 comments
Open

logs not really working (maybe only on kubernetes?) #6

madejackson opened this issue Aug 5, 2024 · 3 comments

Comments

@madejackson
Copy link

madejackson commented Aug 5, 2024

Hey so after running your script since some days on my cluster, I just wanna inform you that the log-output is not really working after a couple of hours.

So actually I have no idea where the progress is atm.

putty just outputs a whole lot of nothing:
image

rancher spits out the first couple of log msg's and doesn't really goes forward:
image

@ajmandourah
Copy link
Owner

can you give me more context on how you are running it.
the scripts is not a loop. It will go over all the subs and sync it. other than that you might need to rerun it on intervals if you have a specefic usage.

@madejackson
Copy link
Author

madejackson commented Aug 5, 2024

My goal is to sync all subtitles at once and only once as I have maybe ~20TB tv shows with unsynced subs. As i don't know which one are out of sync, i just sync all of them once. New subtitles are synced automatically.

As my System runs on kubernetes, I'm doing that command inside the cluster. Otherwise bazarr-sync is unable to connect to bazarr though traefik for whatever reason.

Not sure what other context I can give you.

Also I'm not fond of starting the sync process by hand for 275 shows:
image

@ajmandourah
Copy link
Owner

Thank you for the explanation.
The logging library have a bug related to the terminal itself that is not fixed untill now. Mainly that's if the terminal got resized for any reasons the output will be missed up. Something related with the size of the terminal report.

To be honest I don't use k8 as I have a small use case and run it in docker. What worked for me is running tmux with the command run from the container mentioned in the Readme. This insures that the script will not be killed at least.

I will test it out for and try to debug it. But I can't promise fixing it as it's out of my hand.
I might add a simpler logs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants