tag:blogger.com,1999:blog-552736630635455340.post7087575718265688424..comments2014-08-27T05:45:30.827+02:00Comments on Kenneth Larsens blog: HOW-TO: Using crashplan with Synology NASKenneth Larsenhttp://www.blogger.com/profile/00564887939526959858noreply@blogger.comBlogger202125tag:blogger.com,1999:blog-552736630635455340.post-71200983453139875732014-08-27T05:45:30.827+02:002014-08-27T05:45:30.827+02:00Added: this is on a DS214 running DSM5Added: this is on a DS214 running DSM5Erik van de Polhttps://www.blogger.com/profile/00093829092368333260noreply@blogger.comtag:blogger.com,1999:blog-552736630635455340.post-26742656935310956352014-08-27T05:44:09.319+02:002014-08-27T05:44:09.319+02:00I kept getting restart.(date).log files in /volume...I kept getting restart.(date).log files in /volume1/@appstore/Crashplan/bin.<br />There was some permissions issue creating the CrashPlan.pid file.<br />There must be a cleaner solution, but I was more interested in getting it to work. In the end, I changed in CrashPlanEgine the line TARGETDIR="$SCRIPTDIR/.." to TARGETDIR=/volume1/@appstore/CrashPlan (which is correct for my setup). After this, the periodic restart stopped, and CrashPlan runs.Erik van de Polhttps://www.blogger.com/profile/00093829092368333260noreply@blogger.comtag:blogger.com,1999:blog-552736630635455340.post-60822139701756356372014-08-06T15:09:32.917+02:002014-08-06T15:09:32.917+02:00While installing in synology, getting "Syntax...While installing in synology, getting "Syntax error from install.sh unexpected "(", expected "then", line no:179"<br />Then if i am visiting that file, then in 179 line, having the following code<br /> if [[ ! ($IS_OPENJDK || $IS_HOTSPOT) ]]; then<br /> echo ""<br /> echo "The current installed version of Java is not supported."<br /> echo "$APP_BASENAME requires the Sun JRE or OpenJDK."<br /> exit 1 <br /> fi <br />Plz any body guide me on this, after so many attempt, finally i could not able to install it in my synology machine.Hope i will get reply soon>>>>>>>>>>>>Anonymoushttps://www.blogger.com/profile/17988582910720495615noreply@blogger.comtag:blogger.com,1999:blog-552736630635455340.post-26292702394320462222014-08-06T15:01:54.673+02:002014-08-06T15:01:54.673+02:001.I installed it in linux, "crashplan central...1.I installed it in linux, "crashplan central" is always showing "waiting for connection"<br />2.With proxy even it is not allowing me to create a account.<br />3.Unable to install crash plan in synology, i tried so many times still always getting install.sh file problem, even i downloaded 3/ 4 times<br />4.Even if after installation, unable to launchAnonymoushttps://www.blogger.com/profile/17988582910720495615noreply@blogger.comtag:blogger.com,1999:blog-552736630635455340.post-91505274936599741942013-02-25T23:54:08.168+01:002013-02-25T23:54:08.168+01:00If anyone else comes across the java "excepti...If anyone else comes across the java "exception in thread" error, I wanted to post another solution that worked for me:<br /><br />http://randomwindowstips.wordpress.com/2013/02/25/crashplan-pro-for-linux-stuck-at-waiting-for-backup-or-connecting-to-backup-destination/<br /><br />I hope this helps someone out there!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-552736630635455340.post-31846809651248891062012-04-21T23:47:49.621+02:002012-04-21T23:47:49.621+02:00Mine just started too after doing the package upgr...Mine just started too after doing the package upgrade on the Diskstation.<br /><br />I'm guessing they broke something in the 3.2 update and have since resolved it in 3.2.x.<br /><br />Once you do the update, you can just 'adopt' the 'new' machine it finds in the headless client. I don't think you need to worry about backing up the old client or logs or anything (unless your DS is a backup destination).Nickhttps://www.blogger.com/profile/18287219596514561319noreply@blogger.comtag:blogger.com,1999:blog-552736630635455340.post-23603690161443291892012-04-02T06:58:26.244+02:002012-04-02T06:58:26.244+02:00Well, oddly enough it started listening on both 42...Well, oddly enough it started listening on both 4242 and 4243 the next afternoon. I did not change anything during that time so I can't explain why it started working all of a sudden. <br /><br />I've moved on to being aggrevated with the performance of surveillance station.<br /><br />;)Ashrakhttps://www.blogger.com/profile/03340595077177952954noreply@blogger.comtag:blogger.com,1999:blog-552736630635455340.post-40152923888917640452012-03-30T23:42:06.680+02:002012-03-30T23:42:06.680+02:00I updated the Wiki articles. There is now a sectio...I updated the Wiki articles. There is now a section explaining how to reinstall CrashPlan after it stopped working because of an update.<br /><br /><a href="http://forum.synology.com/wiki/index.php/CrashPlan_Headless_Client" rel="nofollow">CrashPlan Headless Client Installation Guide (English)</a><br /><br /><a href="http://www.synology-wiki.de/index.php/CrashPlan_Headless_Client" rel="nofollow">CrashPlan Headless Client Installationsanleitung (deutsch)</a><br /><br />As I do not have access to an ARM based DiskStation it would be great if somebody with CrashPlan on such a DiskStation could add instructions to at least one of the Wikis above. Or donate an ARM based DiskStation to me ... :)Markhttps://www.blogger.com/profile/00350286729310895759noreply@blogger.comtag:blogger.com,1999:blog-552736630635455340.post-39697749818742253002012-03-25T23:58:25.166+02:002012-03-25T23:58:25.166+02:00Prior to the crashplan auto update on 3/15 I had e...Prior to the crashplan auto update on 3/15 I had everything running like clockwork for a little over a month. Yes, it was listening on both 4243 and 4242. After the reinstalled everything following the update the NAS is only listening on 4243. <br /><br />I'm hoping somebody has some word of wisdom.Ashrakhttps://www.blogger.com/profile/03340595077177952954noreply@blogger.comtag:blogger.com,1999:blog-552736630635455340.post-61889234604254538542012-03-25T23:50:36.592+02:002012-03-25T23:50:36.592+02:00I only have 4243 listening also.
Was 4242 listeni...I only have 4243 listening also.<br /><br />Was 4242 listening before for you? I never looked before the upgrade what ports the NAS was listening to but if I look inside my Crashplan client when connected to my PC as the client rather than redirecting it to the Diskstation, I can see the clients listed there and it says that my Diskstation was last connected at x.x.x.x:4242.Nickhttps://www.blogger.com/profile/18287219596514561319noreply@blogger.comtag:blogger.com,1999:blog-552736630635455340.post-43098811014237695092012-03-25T17:50:47.852+02:002012-03-25T17:50:47.852+02:00Have the same issue as Ashrak, after the update I ...Have the same issue as Ashrak, after the update I only see 4243 listening.edhttps://www.blogger.com/profile/04565422227960042164noreply@blogger.comtag:blogger.com,1999:blog-552736630635455340.post-86071458609920536902012-03-25T05:58:44.663+02:002012-03-25T05:58:44.663+02:00I have a Synology DS212+ running the latest Crashp...I have a Synology DS212+ running the latest Crashplan Headless client.<br /><br />When I run the following command:<br />netstat -an | grep ':424.'<br /><br />I only see the NAS listening on 4243 and not on 4242. <br /><br />I had this running successfully until a couple of weeks ago when crashplan decided to do an auto update. I just finished updating everything manually and can't connect do to the NAS not listening on 4242.<br /><br />Does anybody have any ideas what I might be missing?<br /><br />Thanks...Ashrakhttps://www.blogger.com/profile/03340595077177952954noreply@blogger.comtag:blogger.com,1999:blog-552736630635455340.post-644106327122564042012-03-24T06:42:15.607+01:002012-03-24T06:42:15.607+01:00Ok I have spent probably 10 hors on this now with ...Ok I have spent probably 10 hors on this now with no luck.<br /><br />Either DSM 4.0 or Upgrading to Crashplan 3.2 broke my DS1010+ DSM 4.0.<br /><br />Even more weird, when I log into my Crashplan account now and look at restorable files, it says my DS has never been backed up.<br /><br />The install seems to have gone fine, it just will not connect the Win7 Desktop client to the DS. You can tell the client sees the DS as it prompts for a Crashplan login as opposed to when it does not see it it does not prompt, however it does not accept my Crashplan login. The login is good because if you log in the Desktop client running solely on the Win 7 PC (ie connected to the PC not DS) the login works.<br /><br />I tried both the manual Crashplan install from Synology's Wiki and did it exactl the same as when I was running DSM 3.2 and Crashplan 3.03. I also tried the Package, which is awesome and saves a lot of effort, but it displays the exact same symptoms. I do not get a chance to enter the guid again anywhere as Ronald says, which I can access from my Crashplan account page.Nickhttps://www.blogger.com/profile/18287219596514561319noreply@blogger.comtag:blogger.com,1999:blog-552736630635455340.post-8526110413538709432012-03-21T11:44:57.241+01:002012-03-21T11:44:57.241+01:00Hm, I have a number of Synology devices on which I...Hm, I have a number of Synology devices on which I need to upgrade Crashplan. Does anyone have a good process for doing this? Or am I going to have to uninstall the client on each device and reinstall it and reconfigure? (*cries at the amount of work possibly involved*) :pMindspherehttps://www.blogger.com/profile/10141030907413379284noreply@blogger.comtag:blogger.com,1999:blog-552736630635455340.post-55039943250299052822012-03-20T22:07:56.538+01:002012-03-20T22:07:56.538+01:00Update: Synology support got back to me within one...Update: Synology support got back to me within one business day and told me I should use Synology Assistant to reinstall the same version of DSM that I had before. It worked perfectly, and all of my settings were preserved (which is more than I had hoped for). Then I upgraded to DSM 4.0, installed the Crashplan package (according to the instructions), and adopted my previous backup. Everything was just about perfect (other than the fact that Crashplan has spent a very long time scanning and rescanning my files and compacting and recompacting my old backups).<br /><br />One big difference with the packaged version is that Crashplan runs as a "crashplan" user instead of as root, so I needed to "chown -R crashplan" my backups, and Crashplan still has trouble seeing some files I had saved with 700 permissions. I'll probably have to locate and fix all such permissions, though I wish Crashplan had been installed so that it could read all files.Anonymoushttps://www.blogger.com/profile/00923850913014224145noreply@blogger.comtag:blogger.com,1999:blog-552736630635455340.post-88100566135429365832012-03-19T17:45:59.546+01:002012-03-19T17:45:59.546+01:00HI there!
I have a Synology DS411+ with Crashplan....HI there!<br />I have a Synology DS411+ with Crashplan. I installed the version 3.0.3 last year following the instruction on this blog + http://forum.synology.com/wiki/index.php/CrashPlan_Headless_Client<br />It was working perfectly until now. My guess is that the new version 3.2 is the problem.<br />Anyone facing the same issue?<br />How do I unistall the Crashplan? I wanna try install it from scratch again. Althought I might lose my backups.<br /><br />Thanks, FlavioFlaviohttps://www.blogger.com/profile/17778424186377296940noreply@blogger.comtag:blogger.com,1999:blog-552736630635455340.post-48048092092837331272012-03-19T12:53:19.546+01:002012-03-19T12:53:19.546+01:00Did the following:
1 - removed "/usr/syno/...Did the following: <br /><br />1 - removed "/usr/syno/etc/rc.d/S99crashplan start" from my /etc/rc.local file<br />2 - Stopped all crashplan Services<br />3 - installed the Crashplan package from http://pcloadletter.comlu.com<br />4 - rebooted<br />5 - started desktop client and point it towards the headless service <br />6 - Changed the guid (double click the Crashplan Icon and enter guid which can be retrieved when you check your account at the crashplan site)<br />7 - For some reason it could not use the old backup destication Si I needed to move the Backup achive (just change the location and it started to move)Ronaldhttps://www.blogger.com/profile/02738778514885627159noreply@blogger.comtag:blogger.com,1999:blog-552736630635455340.post-81083191271119439082012-03-19T09:27:35.204+01:002012-03-19T09:27:35.204+01:00I installed yesterday on my ds-712+ from the repos...I installed yesterday on my ds-712+ from the repository after upgrading to dam 4.0<br /><br />You will need to reboot and then "adopt" so you don't have to seed from scratchgnyfhttps://www.blogger.com/profile/05562925758620877454noreply@blogger.comtag:blogger.com,1999:blog-552736630635455340.post-54284433321440816102012-03-19T08:27:30.652+01:002012-03-19T08:27:30.652+01:00You mean the one from the repository is working fo...You mean the one from the repository is working for you? What kind of nas do you have ?Ronaldhttps://www.blogger.com/profile/02738778514885627159noreply@blogger.comtag:blogger.com,1999:blog-552736630635455340.post-25227021182717197662012-03-19T08:12:11.765+01:002012-03-19T08:12:11.765+01:00I had same issue with this package but a simply re...I had same issue with this package but a simply reboot of the DS was enoughgnyfhttps://www.blogger.com/profile/05562925758620877454noreply@blogger.comtag:blogger.com,1999:blog-552736630635455340.post-15102339919573407472012-03-19T07:58:51.429+01:002012-03-19T07:58:51.429+01:00The package is also not working in my case...I'...The package is also not working in my case...I'm not able to connect using my client to adapt the repository form the current one. Anybody know which file to edit to update the ID to the onde from my old install?Ronaldhttps://www.blogger.com/profile/02738778514885627159noreply@blogger.comtag:blogger.com,1999:blog-552736630635455340.post-10852155779966327082012-03-18T23:53:20.108+01:002012-03-18T23:53:20.108+01:00In /opt/crashplan, look for directories with "...In /opt/crashplan, look for directories with "upgrade" in the name. I think I saw two. They may have been identical at one point, and then the upgrade script starts moving the old files out of the way and moving the new files from the upgrade directory into place. The upgrade script itself was called upgrade.sh.<br /><br />@Aiden: Yes, I saw that there is now an unofficial Synology package for Crashplan. That was created just after I originally got mine working, so I didn't risk trying it, but if the DSM 4.0 upgrade was going to blow away my Crashplan installation, I was going to try the package next. Did the packaged Crashplan survive the Crashplan 3.2 upgrade last week, or did it require a re-install of the package?Anonymoushttps://www.blogger.com/profile/00923850913014224145noreply@blogger.comtag:blogger.com,1999:blog-552736630635455340.post-49337728846282038722012-03-18T22:36:33.219+01:002012-03-18T22:36:33.219+01:00If you don't already know....
There is a repo...If you don't already know....<br /><br />There is a repository with Java and Crashplan as a Synology package<br /><br />Add<br />http://pcloadletter.comlu.comAidanhttps://www.blogger.com/profile/02922730232367140215noreply@blogger.comtag:blogger.com,1999:blog-552736630635455340.post-53515957650936944972012-03-18T22:24:29.886+01:002012-03-18T22:24:29.886+01:00Sorry to Hear your DS is not working anymore... I&...Sorry to Hear your DS is not working anymore... I'v been busy with it the whole day and did not realize it is crashplan causing the issue... Any Idea where the upgrade script from autoupgrade is located?<br /><br /><br />Thx,<br />RonaldRonaldhttps://www.blogger.com/profile/02738778514885627159noreply@blogger.comtag:blogger.com,1999:blog-552736630635455340.post-18799029971999122322012-03-18T19:42:30.314+01:002012-03-18T19:42:30.314+01:00I don't have the complete answer here, but I t...I don't have the complete answer here, but I think the deletion of com.backup42.desktop.jar is a result of the release of Crashplan 3.2 a couple days ago, not your upgrade to DSM 4.0. Crashplan does an auto-upgrade, but the upgrade script has the same kind of problems that the original install script did: it assumes that mv has a -v flag and that ps accepts certain options. If you look at the upgrade script you can figure out how to attempt the upgrade manually.<br /><br />That said, my DS212 is currently non-bootable (pingable, but HTTP and ssh reject connections, and the status light flashes orange), perhaps a result of my attempt to get Crashplan working again. I'm waiting to hear from Synology about how best to proceed. :-(Anonymoushttps://www.blogger.com/profile/00923850913014224145noreply@blogger.com