A couple of things I found:
- The Session Timeout of 0 is set back to 5.
- /home/sickbeard/.sickbeard is no longer the home directory, it gets set to /var/opt/sickbeard, breaking the entire content-structure of SickRage.
- For some reason apache2 gets started, breaking SickRage and giving an APACHE2 Default page when opening SickRage.
- Restore of SickRage does not work, as the restore does not place the files in the now new home of /var/opt/sickbeard.
This leaves me with a lot of questions regarding WHAT ELSE was broken/changed that the user does not realize?
Fixing the upgrade abortion:
- Initial apache2 problem:
This will give you the clean-slate SickRage page.
- SickRage restore: To get this working, shut down sickbeard with
then
then
then
and finally
What I would like to know:
How are we going to fix this as it creates a HUGE problem for novice users?
kind regards
cyber7
ps - Slating me because I criticize the poor upgrade documentation and roll-out will only prove the point that this was never tested on a stable environment...