Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

CrashPlan

Featured Replies

I got things going again...

 

One the bandwidth settings... it looks like it is always using the "away" speed... What determines away/present speeds when using a headless system?

  • Replies 533
  • Views 194.4k
  • Created
  • Last Reply

I just have them both set to no limit, but I have a 20M up / down connection.  In your case, I would set them to half your total upload.

I just have them both set to no limit, but I have a 20M up / down connection.  In your case, I would set them to half your total upload.

 

NICE! I'm at 10/1. Which is great. I'd like more upload... I think I can get a 50/5 now, but I'm sure they want a ton for that.

 

BTW: Boof,

 

I did the symbolic links and have it running from my cache drive now. Part of my shutdown script tars up and copies the crashplan stuff. Works great! Time to update the wiki entry. I'll be glad to help!

I just have them both set to no limit, but I have a 20M up / down connection.  In your case, I would set them to half your total upload.

 

NICE! I'm at 10/1. Which is great. I'd like more upload... I think I can get a 50/5 now, but I'm sure they want a ton for that.

 

BTW: Boof,

 

I did the symbolic links and have it running from my cache drive now. Part of my shutdown script tars up and copies the crashplan stuff. Works great! Time to update the wiki entry. I'll be glad to help!

 

Good stuff!  :D

 

I just went through the crashplan install and used unMenu for the dependencies' package install.  Thanks for the wiki entries and all the testing you guys did.  I installed on the cache drive (was OK but found the "official" instructions to do so *after* I was done ::) ) Then again, I haven't rebooted yet.

 

Now I need to figure out why the crashplan user script buttons don't show up in unMenu.  I see the scripts in \\TOWER\flash\unmenu and I tweaked them for my install path.  Probably messed something up in my unMenu 1.1 to 1.3 upgrade...

 

Gog

The buttons will not show up unless crashplan is installed and is executable in

/usr/local/crashplan/bin/CrashPlanEngine

as tested in the USER_SCRIPT_TEST line.

 

If you installed the engine elsewhere, the test will fail and the buttons will not show up.

Thanks, I thought those were comments.

 

Only 75GB left to upload...

 

Gog

Thanks, I thought those were comments.

 

Only 75GB left to upload...

 

Gog

Three  very special comments.... 

One defines the button label.

One defines the description.

One is a test to determine if the button should be shown at all.  (no sense showing buttons to manage software if it does not exists on a server)

The buttons will not show up unless crashplan is installed and is executable in

/usr/local/crashplan/bin/CrashPlanEngine

as tested in the USER_SCRIPT_TEST line.

 

If you installed the engine elsewhere, the test will fail and the buttons will not show up.

 

So will the symlink (as used in the previous post on setting it up to run from the cache drive) suffice? I just set it up this way and was wondering if I would see the buttons on reboot.

The buttons will not show up unless crashplan is installed and is executable in

/usr/local/crashplan/bin/CrashPlanEngine

as tested in the USER_SCRIPT_TEST line.

 

If you installed the engine elsewhere, the test will fail and the buttons will not show up.

 

So will the symlink (as used in the previous post on setting it up to run from the cache drive) suffice? I just set it up this way and was wondering if I would see the buttons on reboot.

You tell me.  Do they show up?  The "test" is just that, a test.

What do you see when you invoke:

test -x /usr/local/crashplan/bin/CrashPlanEngine && echo "Start CrashPlan Engine"

"Start Crashplan Engine"

 

thanks... my bad. I guess I could have checked that myself.  ::)

The symlink keeps everything seemingly where it would be as per the original install instructions. So any scripts etc (inc the unmenu one) *should* still work fine.

 

Only ones that might fail are the ones that check if /us/local/crashplan is actually a directory or not  ;D

Is it just me, or is the crashplan interface pretty slow and clunky?

I was thinking about going the Crashplan route and I has some general questions.  I want to backup 2 to 5 local networked PCs to the unRAID server.  Then I was hoping to backup the unRAID server to the cloud.  What service would I need?  I assume run the free version on each PC and then the plus (1 PC, unlimited version) on unRAID.  Am I sort of in the right direction?

I was thinking about going the Crashplan route and I has some general questions.  I want to backup 2 to 5 local networked PCs to the unRAID server.  Then I was hoping to backup the unRAID server to the cloud.  What service would I need?  I assume run the free version on each PC and then the plus (1 PC, unlimited version) on unRAID.  Am I sort of in the right direction?

 

Yes. That will work.

Looks like 3.0.1 got pushed out last night. For some reason neither of my clients can connect to the server installed on my Unraid box. I've tried stopping and restarting the service but still no go. The logs look like it's starting up OK with the new version, but when I try to stop the service from a telnet session, I get an error saying "no process found" or something like that. The start command seems to work fine, no errors there. No errors in any log file that I could find either.

 

One oddity I did find is that my when logging in to my Crashplan account online, my 3 systems show "CrashPlan+ Trial" as the license type, but only the Unraid box is highlighted in red and says "Expired". I've never upgraded to the "Plus" version and thought that nothing needed to be done, once the forced trial expired all would be well. Did I miss something during the version 3 upgrade?

Looks like 3.0.1 got pushed out last night. For some reason neither of my clients can connect to the server installed on my Unraid box. I've tried stopping and restarting the service but still no go. The logs look like it's starting up OK with the new version, but when I try to stop the service from a telnet session, I get an error saying "no process found" or something like that. The start command seems to work fine, no errors there. No errors in any log file that I could find either.

 

One oddity I did find is that my when logging in to my Crashplan account online, my 3 systems show "CrashPlan+ Trial" as the license type, but only the Unraid box is highlighted in red and says "Expired". I've never upgraded to the "Plus" version and thought that nothing needed to be done, once the forced trial expired all would be well. Did I miss something during the version 3 upgrade?

 

They updated to 3.0.1 to try and fix the sluggish UI. There is a thread over on their forums. I have the same issue as you, my "other" machines aren't seing my unraid box as "online"

 

I haven't had time to look, but is the version on your unraid box at 3.0.1? or is it just the GUI on your workstation that got updated?

 

Here is the link to their info:

https://crashplan.zendesk.com/entries/352477

They updated to 3.0.1 to try and fix the sluggish UI. There is a thread over on their forums. I have the same issue as you, my "other" machines aren't seing my unraid box as "online"

 

I haven't had time to look, but is the version on your unraid box at 3.0.1? or is it just the GUI on your workstation that got updated?

 

According to app.log it's the new version.

 

***************************************************************************************************
DateTime     = Fri Jan 28 07:52:08 EST 2011
OS           = Linux (2.6.32.9-unRAID, i386)
JVM          = Java(TM) 2 Runtime Environment, Standard Edition (1.5.0_14-b03, 32-bit)
Locale       = English, America/New_York
User         = root, /root

Application  = CrashPlan
CPVERSION    = 3.0.1 - 1296150374530 (2011-01-27T17:46:14:530+0000)
CPGUID       = ######### from file: /var/lib/crashplan/.identity
ProClient    = false
WorkingDir   = /usr/local/crashplan
LogDir       = /usr/local/crashplan/log
AppDataDir   = /usr/local/crashplan/conf
CacheDir     = /usr/local/crashplan/cache
ArchiveDir   = /mnt/disk3/Backup/
Args         = [  ]
LibraryPath  = /usr/local/crashplan/java/lib/i386/client:/usr/local/crashplan/java/lib/i386:/usr/local/crashplan/java/../lib/i386:.:lib
ClassPath    = [file:/usr/local/crashplan/lib/com.backup42.desktop.jar, file:/usr/local/crashplan/lang/]

***************************************************************************************************

Ok,  I'm very new to unRaid.  So I'll make my question here very brief.  Have been working on getting Crashplan installed today (1/28/11) and noticed that I'm at 3.0.1 on my Windows machine, and I assume the same (I downloaded the Linux client today) on the unRaid box.

 

If I understand what I'm reading here correctly,  I ought to just wait a bit and let this whole 3.0.1 thing sort itself out.  In other words, I should assume that my problems getting my Windows box to connect SSH to my newly-installed CrashPlan instance on the UnRaid box -- are possibly part of this new 3.0.1 issues.

 

 

Well, it seems I'm back up and running now. Since I knew that the server install updated itself (according to the app.log file), I took a chance and backed up my current Crashplan tar file and created a new one from the RAM disk with the handy unMenu "Tar Crashplan" user script button. I shutdown the server and restarted. All appears to be well now. My clients can now see the server instance just fine.

 

Looking through my syslog I do see some out of memory errors that seem to relate to java, so I'm wondering if something went a bit screwy with the auto update. For now it seems OK, I've been meaning to move Crashplan over to the newly installed cache drive, so that might be the project for tomorrow.

For what it's worth the update went through ok this end on :

 

- unraid

- windows desktop

- remote ubuntu target

 

 

If I understand what I'm reading here correctly,  I ought to just wait a bit and let this whole 3.0.1 thing sort itself out.   In other words, I should assume that my problems getting my Windows box to connect SSH to my newly-installed CrashPlan instance on the UnRaid box -- are possibly part of this new 3.0.1 issues.

 

Very unlikely. It should work ok.

 

 

Maybe somone can help me out.  I attached my syslog...

 

I successfully got unraid server listed as one of the destinations for CrashPlan.  My laptop said it was backing up to it so I thought I would go to the location on unraid to verify the contents being copied over and nothing is there and none of my drives were even spun up.  So I paused it, affraid for some reason it was either writing to the flash drive or cache.  When I unpaused it (after verifing it wasn't writing to the flash drive), it stoped a few minutes later saying the server was offline.

 

I now can't even get to the main unraid web page, although unmenu still works.  I can see I ran out of memory and the emhttp was killed.  So, what did I do wrong and how do I fix it.  Thanks.

syslog-2011-01-29.txt

Where was it writing to?

 

THis sounds exactly like it's writing to the ram disk or flash drive. Which has made your system run out of memory and oom kill java (crashplan most likely) and emhttp.

 

Where did you tell crashplan to put your backups? and is that actually where they were?

 

As for fixing - I imagine you can just restart emhttp by logging in and running /usr/local/sbin/emhttp.

 

 

Obviously you were writing to RAM, used it all up, and the linux kernel is killing processes that it thinks have been idle the longest.

 

All yo can do now is reboot.  (If you can reboot from unMENU's page it might stop the array cleanly... if there is enough ram for it to try.  It too might get killed off.)

 

Joe L.

 

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.