NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Crashplan no longer autostarts on 6.5.0
I updated my ReadyNas 516 from 6.4.2 to 6.5.0 and now crashplan no longer starts on bootup.
I have tried uninstalling and reinstalling crashplan 4.7.0 but it will not auto start on boot up. I can easily start it after boot up via SSH by using
/usr/local/crashplan/bin/CrashPlanEngine start
Any ideas on what to check to fix this?
Thanks to Viktor over at the Code42 forums, I have a working solution. The problem was I was missing a few symbolic links in the run folders. In my case, even after a fresh install of crashplan 4.7.0 I only had a single symbolic link in "/etc/rc5.d/S02crashplan" that pointed to my init script for the CrashPlanEngine service: “/etc/init.d/crashplan"
For those with my same issue, I only had to do these commands to solve this:
ln -s /etc/init.d/crashplan /etc/rc0.d/K01crashplan
ln -s /etc/init.d/crashplan /etc/rc1.d/K01crashplan
ln -s /etc/init.d/crashplan /etc/rc2.d/S01crashplan
ln -s /etc/init.d/crashplan /etc/rc3.d/S01crashplan
ln -s /etc/init.d/crashplan /etc/rc4.d/S01crashplan
ln -s /etc/init.d/crashplan /etc/rc6.d/K01crashplanupdate-rc.d crashplan defaults
4 Replies
Replies have been turned off for this discussion
CrashPlan being installed on the OS volume is not recommended. But anyway, what script were you using to start it automatically in the first place?
I appreciate the willingness to help, Thank You. I never needed a script, for many years and several versions of CrashPlan I just installed it and reboot and it always auto ran on boot up. I only use this NAS for one purpose, to act as a headless offsite CrashPlan server.
Something changed from 6.4.2 to 6.5.0 and I am not sure where or what to check?
I just found this...
Does this Help?
kohdee wrote:
CrashPlan being installed on the OS volume is not recommended.
Perhaps, though it is generally safe enough if you reconfigure the cache location (and perhaps symlink the upgrade folder).
kohdee wrote:
CrashPlan being installed on the OS volume is not recommended. But anyway, what script were you using to start it automatically in the first place?
If the OP was using the normal crashplan install, Crashplan would have created a symlink ( /etc/init.d/crashplan ) to /usr/local/crashplan/bin/CrashplanEngine
Thanks to Viktor over at the Code42 forums, I have a working solution. The problem was I was missing a few symbolic links in the run folders. In my case, even after a fresh install of crashplan 4.7.0 I only had a single symbolic link in "/etc/rc5.d/S02crashplan" that pointed to my init script for the CrashPlanEngine service: “/etc/init.d/crashplan"
For those with my same issue, I only had to do these commands to solve this:
ln -s /etc/init.d/crashplan /etc/rc0.d/K01crashplan
ln -s /etc/init.d/crashplan /etc/rc1.d/K01crashplan
ln -s /etc/init.d/crashplan /etc/rc2.d/S01crashplan
ln -s /etc/init.d/crashplan /etc/rc3.d/S01crashplan
ln -s /etc/init.d/crashplan /etc/rc4.d/S01crashplan
ln -s /etc/init.d/crashplan /etc/rc6.d/K01crashplanupdate-rc.d crashplan defaults
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
