Advertisement
CrashPlan Community Forum – Support & Assistance

CrashPlan 1435813200470_317.jar upgrade failed

Home Forums Crashplan on Other NAS systems CrashPlan 1435813200470_317.jar upgrade failed

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #526

    Yoann M
    Participant

     

    Note: Not sure that the upgrade works fully, but CrashPlan is working after that

    To fix CrashPlan crash after 1435813200470_317.jar (may 2016) upgrade

    Problem
    CrashPlan do not want to start. In logs you have a file : engine_error.log that contain :
    Error: Could not find or load main class com.backup42.service.CPService

    And an upgrade.X.log file that end with :
    Mon May 9 22:13:20 CEST 2016 : Upgrade process in progress…
    Mon May 9 22:13:20 CEST 2016 : Is ARM device: false
    Mon May 9 22:13:20 CEST 2016 : Stopping CrashPlan
    Mon May 9 22:13:30 CEST 2016 : Stopped
    Mon May 9 22:13:30 CEST 2016 : Removing old jar files…
    Mon May 9 22:13:30 CEST 2016 : Moving new jar files…
    mv: unable to rename `*.jar’: No such file or directory
    Mon May 9 22:13:30 CEST 2016 : Starting CrashPlan
    Mon May 9 22:13:30 CEST 2016 : Started

    1) Uninstall Crashplan on your QNAP NAS
    2) Install Crashplan again
    3) Login SSH on your NAS, and open with vi the file /share/CACHEDEV1_DATA/.qpkg/CrashPlan/install.vars
    4) After echo “$(date) : Stopped” >> ${logFile} 2>&1
    add theses lines :

    cd ../UpgradeUI
    if [ $? -ne 0 ]; then
    echo “$(date) : Unable to change directory” >> ${logFile} 2>&1
    exit 1;
    fi

    a=`pwd`
    echo “$(date) : Current directory ‘$a'” >> ${logFile} 2>1

    5) On http://XXXX/crashplan/ , update the configuration, save, and stop , start Crashplan
    6) Go back on http://XXXX/crashplan/ to get the new ID and update .ui_info file on your desktop
    7) Start your CrashPlan desktop app on your computer and login
    8) On the welcome screen on CrashPlan app, “Adopt” your old backup (https://support.code42.com/CrashPlan/4/Configuring/Replacing_Your_Device)
    9) The CrashPlan app will ask your login/password again, but will say “CrashPlan updating”
    10) After some minutes, CrashPlan should restart upgrade done
    11) run # cat /share/CACHEDEV1_DATA/.qpkg/CrashPlan/log/upgrade.1435813200470_317*
    12) Last line should be like that :
    Sat May 14 18:24:01 CEST 2016 : Current directory ‘/share/CACHEDEV1_DATA/.qpkg/CrashPlan/upgrade/UpgradeUI’
    Sat May 14 18:24:01 CEST 2016 : Removing old jar files…
    Sat May 14 18:24:01 CEST 2016 : Moving new jar files…
    Sat May 14 18:24:01 CEST 2016 : Moving libjniwrap.so to the app dir…
    Sat May 14 18:24:01 CEST 2016 : Starting CrashPlan
    Sat May 14 18:24:01 CEST 2016 : Started
    13) Upgrade done

    #536

    Yoann M
    Participant

    This post is not correct, it’s not the correct solution. Please delete this post

Advertisement
Viewing 2 posts - 1 through 2 (of 2 total)
  • The topic ‘CrashPlan 1435813200470_317.jar upgrade failed’ is closed to new replies.

Here's what other Users are reading:

Affiliate Links
Advertisement