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

Update error #35

Open
gillesoorts opened this issue Mar 6, 2018 · 3 comments
Open

Update error #35

gillesoorts opened this issue Mar 6, 2018 · 3 comments

Comments

@gillesoorts
Copy link

Got this error updating from 1.2.17 to 1.2.20 on my Synology. Stopped and started the package manually and it is working again, so I don't know if it's much of a problem...

screen shot 2018-03-06 at 23 59 19

@BenjV
Copy link
Owner

BenjV commented Mar 7, 2018

Small glitch.
Thr home page now uses a new variable to display the days left before the sub will be search for.
But during an upgrade the template are first replace and the python code afterwards, zo the webserver who displays the page is looking for a variable that is not yet there.
Only happens during upgrade and a refresh of the browser page will solve it. No need for stopping and starting the package.

@WeirDave
Copy link

WeirDave commented Apr 15, 2018

I have a QNAP TS-653A https://www.qnapclub.eu/en/qpkg/565 and I encountered this error and refreshing the page never worked I ended up having to stop and start the application in the App Center for it to come back up. I went from v1.2.17 to 1.2.22. Also as a side note note my settings did not save and I had to recreate (which was easy mind you).

@BenjV
Copy link
Owner

BenjV commented Apr 15, 2018

Sometimes there are changes that needs a stop and start of autosub.
This is because autosub is actually an application and also a webserver (for the gui) and when there is an update of the application from within the gui is restarts but of course the gui cannot restart itself, so that was what happend.
Stopping an starting autosub would have fixed the problem.

About the restore of the settings, that is an bug.
The restore works fine, but after a restore the config is not red automatically and you need een reboot (or stop/start) of autosub to read in the data.
I will fix this in the next release.

By the way backup and restore is only necessary if you completely remove autosub, not if you upgrade or do a reboot or stop/start cycle.

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

3 participants