Page 1 of 2

Crashplan unable to connect

Posted: Mon Jul 09, 2012 12:53 pm
by wvdlee
On a newly installed amahi 6.1 on Ubuntu I bought and installed Crashplan.
On the HDA itself I started it from terminal with CrashPlanDesktop.
Crashplan opens but when I try to create a new account or an existing account I get "Unable to connect check your network."
But http://www.crashplan.com is working properly, I also installed crashplan on a windows machine in the same network and that did work.
I also tried sudo chmod 666 /usr/local/crashplan/log/*.log as instructed in the wiki but that also did not work.
sudo CrashPlanDesktop also does not work, still getting the "unable to connect" error

What should I try now? Am I missing something.

I looked in amahi-app-installer.log and it apparently shows no errors.

Code: Select all

Welcome to the CrashPlan Installer. Validating environment... detected root permissions ERROR: Failed to find an acceptable Sun Java Runtime Environment These paths were searched: /bin /usr/bin /usr/local/bin Would you like to download the JRE and dedicate it to CrashPlan? (y/n) [y] jre will be downloaded What directory do you wish to install CrashPlan to? [/usr/local/crashplan] /usr/local/crashplan does not exist. Create /usr/local/crashplan? (y/n) [y] What directory do you wish to link the CrashPlan executable to? [/usr/local/bin] What directory do you wish to store backups in? [/var/hda/files/crashplan] /var/hda/files/crashplan does not exist. Create /var/hda/files/crashplan? (y/n) [y] What directory contains your SYSV init scripts? [/etc/init.d] What directory contains your runlevel init links? [/etc/rc2.d] Your selections: CrashPlan will install to: /usr/local/crashplan And put links to binaries in: /usr/local/bin And store datas in: /var/hda/files/crashplan Your init.d dir is: /etc/init.d Your current runlevel directory is: /etc/rc2.d Is this correct? (y/n) [y] Downloading the JVM .... --2012-07-08 23:35:38-- http://download.crashplan.com/linuxjvm/jre1.6.0_17_x64.tgz Resolving download.crashplan.com (download.crashplan.com)... 209.208.241.214, 209.208.241.215, 209.208.241.211, ... Connecting to download.crashplan.com (download.crashplan.com)|209.208.241.214|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 30716483 (29M) [application/x-tgz] Saving to: `jre1.6.0_17_x64.tgz' 0K .......... .......... .......... .......... .......... 0% 218K 2m18s 50K .......... .......... .......... .......... .......... 0% 191K 2m27s 100K .......... .......... .......... .......... .......... 0% 443K 2m0s etc etc etc 29950K .......... .......... .......... .......... ...... 100% 1.75M=25s 2012-07-08 23:36:03 (1.15 MB/s) - `jre1.6.0_17_x64.tgz' saved [30716483/30716483] Java Installed. Unpacking /root/CrashPlan-install/./CrashPlan_2010-03-08.cpi ... 31221 blocks Your Linux system is currently configured to watch 8192 files in real time. We recommend using a larger value; see the CrashPlan support site for details Starting CrashPlan Engine ... Using Ubuntu 9 startup OK CrashPlan has been installed and the Service has been started automatically. Important directories: Installation: /usr/local/crashplan Logs: /usr/local/crashplan/log Default archive location: /var/hda/files/crashplan Start Scripts: sudo /usr/local/crashplan/bin/CrashPlanEngine start|stop /usr/local/crashplan/bin/CrashPlanDesktop You can run the CrashPlan Desktop UI locally as your own user or connect a remote Desktop UI to this Service via port-forwarding and manage it remotely. Instructions for remote management are in the readme files placed in your installation directory: /usr/local/crashplan/doc To start the Desktop UI: /usr/local/bin/CrashPlanDesktop Installation is complete. Thank you for installing CrashPlan for Linux. Restarting CrashPlan Engine ... Stopping CrashPlan Engine ... OK Starting CrashPlan Engine ... Using Ubuntu 9 startup OK App: CrashPlan installed

Re: Crashplan unable to connect

Posted: Mon Jul 09, 2012 3:52 pm
by bigfoot65
We apologize for the inconvenience. We are experiencing problems with this app. We are looking into it now. Once it is resolved, we will post here.

Re: Crashplan unable to connect

Posted: Mon Jul 09, 2012 5:03 pm
by bigfoot65
We have moved the app back to BETA until the issues can be resolved.

Re: Crashplan unable to connect

Posted: Mon Jul 09, 2012 7:21 pm
by bigfoot65
Looks like we have the issues sorted out. We hope to move it back live in the next day or so.

Re: Crashplan unable to connect

Posted: Thu Jul 12, 2012 1:52 pm
by bigfoot65
CrashPlan has been updated and moved back to LIVE.

Re: Crashplan unable to connect

Posted: Thu Jul 12, 2012 4:00 pm
by wvdlee
CrashPlan has been updated and moved back to LIVE.
Unfortunately with the same result. I uninstalled Crashplan and installed again. Followed wiki and started sudo CrashPlanDesktop in a terminal.
The result is again:
UNABLE TO CONNECT. CHECK YOUR NETWORK

any ideas how to fix this?

Re: Crashplan unable to connect

Posted: Thu Jul 12, 2012 4:13 pm
by bigfoot65
When you uninstall, ensure all the pieces are removed from the HDA. Then reboot before trying to install.

If that does not work, it is likely you have something else causing problems. Our testing indicates it works fine now, but there is always an exception.

Re: Crashplan unable to connect

Posted: Thu Jul 12, 2012 7:48 pm
by schweitzer6
This resolved my issue. I was having a terrible time and didn't see the light at the end of the tunnel. One thing I did notice is when I uninstalled, the entire crashplan folder was left intact. So after reading this thread I deleted the folder rebooted and reinstalled. Fixed!

Thanks for the info and the effort in cleaning up the app.

edit:Apologies to all, I just noticed this was under Ubuntu version. I'm still on Fedora.

Re: Crashplan unable to connect

Posted: Thu Jul 12, 2012 7:58 pm
by bigfoot65
Awesome. Yes the old way was to leave the install files behind, then when you reinstalled it would uninstall things. Kind of backwards if you ask me.

Nonetheless, we seem to have it resolved now and working well for most so far. Thanks for the positive feedback!

Re: Crashplan unable to connect

Posted: Sat Jul 14, 2012 5:44 am
by wvdlee
still not working.

This is what I did.
First I uninstalled crashplan in the amahi dashboard.

Then I searched for all directories called crashplan and I removed these as root.

After that I rebooted the HDA
and Installed Crashplan again form the Amahi dashboard. Then started in a terminal sudo CrashPlanDesktop and......

Code: Select all

sudo: CrashPlanDesktop: command not found
this is in the amahi-app-installer.log:

Code: Select all

======= app install begin @ Sat Jul 14 14:31:41 +0200 2012 ========== Installing app id sp2uf8jdkx under /var/hda/platform/html ENV=production /usr/lib/ruby/1.8/timeout.rb:64:in `rbuf_fill': execution expired (Timeout::Error) from /usr/lib/ruby/1.8/net/protocol.rb:134:in `rbuf_fill' from /usr/lib/ruby/1.8/net/protocol.rb:86:in `read' from /usr/lib/ruby/1.8/net/http.rb:2220:in `read_body_0' from /usr/lib/ruby/1.8/net/http.rb:2181:in `read_body' from /usr/lib/ruby/1.8/net/http.rb:2206:in `body' from /usr/lib/ruby/1.8/net/http.rb:2145:in `reading_body' from /usr/lib/ruby/1.8/net/http.rb:1053:in `request' from /usr/bin/amahi-download:50:in `download_once' from /usr/lib/ruby/1.8/net/http.rb:543:in `start' from /usr/lib/ruby/1.8/net/http.rb:440:in `start' from /usr/bin/amahi-download:50:in `download_once' from /usr/bin/amahi-download:67:in `download' from /usr/bin/amahi-download:104:in `download_and_check_sha1' from /usr/bin/amahi-download:122:in `main' from /usr/bin/amahi-download:129 tar (child): CrashPlan_3.2.1_Linux.tgz: Cannot open: No such file or directory tar (child): Error is not recoverable: exiting now tar: Child returned status 2 tar: Error is not recoverable: exiting now /var/hda/apps/sp2uf8jdkx/elevated/installcp.sh: 3: cd: can't cd to CrashPlan-install /var/hda/apps/sp2uf8jdkx/elevated/installcp.sh: 7: /var/hda/apps/sp2uf8jdkx/elevated/installcp.sh: ./install.sh: Permission denied crashplan: unrecognized service App: CrashPlan installed ======= app install end @ Sat Jul 14 14:33:09 +0200 2012 ==========
So this is also not working, what to do next ???