neyrond
commented
7 months ago Removed cache /crashplan-pro/cache/*, still getting the same error: CPErrors.Global.UPGRADING
Open neyrond opened 7 months ago
neyrond
commented
7 months ago Removed cache /crashplan-pro/cache/*, still getting the same error: CPErrors.Global.UPGRADING
jlesage
commented
7 months ago Is this still an issue ? It's not clear to me if this error is related to upgrade of the CrashPlan server...
tchebyte
commented
7 months ago Is this still an issue ? It's not clear to me if this error is related to upgrade of the CrashPlan server...
same problem here.
INFO 34715192-132 backup42.service.ui.UIController] UI:: UserActionResponse: LoginResponseMessage@********[ errors=[CPErrors.Global.UPGRADING : []]session=********]{}
jlesage
commented
7 months ago Did you try to contact the CrashPlan support team about this ? If you do, please report back here about the solution/problem.
tchebyte
commented
7 months ago Did you try to contact the CrashPlan support team about this ? If you do, please report back here about the solution/problem.
I did. They replied:
If your device is stuck in this state, it is typically resolved by uninstalling and reinstalling the application manually. Please follow the Standard Uninstall steps listed below: Uninstalling and Reinstalling the CrashPlan App > Standard Uninstall
After uninstalling, you can download the latest version of the CrashPlan app by signing into the CrashPlan console and selecting Downloads on the top of the page, then selecting the installer appropriate for your operating system.
I'm new with docker. What should I to achieve this?
neyrond
commented
7 months ago follow the Standard Uninstall steps listed below
I just went through uninstall.sh in CrashPlanSmb_11.2.0_520_Linux.tgz archive. It looks in standard uninstall they remove some binaries, some config files, but leavings most of the user data:
rm -f "${BIN_DIR}/${APP_BASENAME}Desktop"
rm -f "/usr/local/bin/${APP_BASENAME_LOWER}"
...
rm -f "${APP_DIR}/conf/default.service.xml"
rm -f "${APP_DIR}/conf/service.log.xml"
...
I haven't researched it deeply, maybe I'm missing something important.
I tried to replace default.service.xml and service.log.xml in Crashplan Docker appdata to the ones from the last version, but it didn't help.
jlesage
commented
7 months ago I guess you can try to start from scratch and adopt your backup:
/config (e.g. mv /volume1/docker-appdata/crashplan-pro /volume1/docker-appdata/crashplan-pro.bk).You will have the option to adopt an existing device/backup to avoid re-uploading everything.
tchebyte
commented
7 months ago Thanks, that worked! I had to preserve conf/default.service.xml in the new /config folder to login though.
jlesage
commented
7 months ago I had to preserve conf/default.service.xml in the new /config folder to login though.
What was the problem ? You should not have to do this kind of action.
tchebyte
commented
7 months ago The first login page asked for "server name". I tried "central.crashplanpro.com:4287", "console.us2.crashplanpro.com:4287", "clients.us2.crashplan.com:4287", "console.us5.crashplanpro.com:4287", "clients.us5.crashplan.com:4287", but no luck.
So, I restored this file and I could login and I took over the backup as this instructions.
jlesage
commented
7 months ago Ok, I guess you are probably using the Small Business plan from CrashPlan.
You can set the CRASHPLAN_SERVER_ADDRESS environment variable to SMB to prevent this issue from occurring again.
Current Behavior
After upgrading to the latest version I cannot login to UI, getting the followings message after entering credentials:
Upgrading to a new version. You can sign in once the upgrade completes. This situation continues for several days.service.log.0gives me that:Expected Behavior
No response
Steps To Reproduce
No response
Environment
Device: DS918+
Container creation
docker run \ -d \ --privileged \ --name=crashplan-pro \ --restart=unless-stopped \ -v /volume1/docker-appdata/crashplan-pro:/config:rw \ -v /volume1:/volume1 \ -v CLEAN_TMP_DIR=1 \ -p 5800:5800 \ -e CRASHPLAN_SRV_MAX_MEM=4G \ -e USER_ID=0 -e GROUP_ID=0 \ -e KEEP_APP_RUNNING=1 \ jlesage/crashplan-pro:latest
Container log
Container inspect
No response
Anything else?
No response