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
nzbToMedia Update fails #1729
Comments
Only thing I can suggest here is to re-clone, so from nzbToMedia directory:
Then test if everything is working... if so, you can delete the nzbToMedia.old (backup) |
Thank you @clinton-hall I have recloned and checked the settings in nzbGet -- they all appear correct. If anyone else is going through this, a few notes on the reclone script (which took me a bit to figure out, after getting error messages)
|
thanks for confirming... sorry i have the git clone URL wrong previously (fixed now in my original post). |
And it would have, had I executed it as written :-( A post-processing task completed successfully, but there are errors in a section of the log that were not there with the previous version. Current Version:
There was no cleaning bytecode section in the previous version. Is this something significant? Thanks. |
nothing to worry about. |
Thanks. |
My nzbToMedia installation in nzbGet has AutoUpdate selected, but that doesn't seem to work.
I was having a problem of recent onset where an attempt to post-process would create a message in the Sickchill log
User attempted a failed login to the sickchill web interface from IP 172.17.0.1
and the post-process would eventually fail.That problem was apparently fixed by stopping and restarting both nzbGet and SickChill, but in the course of trouble shooting I tried to update nzbToMedia, since changelog.txt showed: V11.03 15/01/2017
Executing
git pull
returned error message:Tried:
with same results
Was going to try
git stash …
but that returns a message:and I really don't know what to do with this.
Technical Specs
NZBget
SickChill
Expected behavior
git pull should update the scripts
Log
see above
The text was updated successfully, but these errors were encountered: