• Content Count

  • Joined

  • Last visited

Community Reputation

19 Good

About jademonkee

  • Rank


  • Gender
  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Just popping in to say that 30 days later I FINALLY have backups completed again. Thanks again, everyone, for your help.
  2. Mine works fine as Bridge. Never had adoption issues (well, there were some when I had to factory reset my devices and completely nuke the controller install, but that wasn't related). I have the following ports mapped and am running version 5.14.23-ls76: EDIT: Be sure to make sure you have the broadcast address set manually in Settings > Controller > "Controller Hostname/IP" too!
  3. NEVERMIND I FIGURED IT OUT I'M SO SORRY I had manually added the CRASHPLAN_SRV_MAX_MEM variable, totally overlooking the one that was there by default, (worse yet: it looks like I had even previously set it to 3072M). I've now deleted the redundant variable, and changed the original one to 4096M, and the run command now looks like this: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='CrashPlanPRO' --net='bridge' -e TZ="Europe/London" -e HOST_OS="Unraid" -e 'USER_ID'='99' -e 'GROUP_ID'='100' -e 'UMASK'='000' -e 'APP_NICENESS'='' -e '
  4. root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='CrashPlanPRO' --net='bridge' -e TZ="Europe/London" -e HOST_OS="Unraid" -e 'USER_ID'='99' -e 'GROUP_ID'='100' -e 'UMASK'='000' -e 'APP_NICENESS'='' -e 'DISPLAY_WIDTH'='1280' -e 'DISPLAY_HEIGHT'='768' -e 'X11VNC_EXTRA_OPTS'='' -e 'CRASHPLAN_SRV_MAX_MEM'='3072M' -e 'SECURE_CONNECTION'='0' -p '7810:5800/tcp' -p '7910:5900/tcp' -v '/mnt/user':'/storage':'ro' -v '/boot':'/flash':'ro' -v '/mnt/user/appdata/CrashPlanPRO':'/config':'rw' 'jlesage/crashplan-pro' e82c65fd7d8a47d2d87b0de10f6624f4dd8a7c11843e2e2
  5. Correct. Container config has CRASHPLAN_SRV_MAX_MEM variable set as 4096M
  6. The file synchronisation did complete, and then it moved to the next maintenance task. I thought that would be a good time to upgrade to the latest version (as Crashplan support mentioned that I should), so I updated the container and now it's doing a "deep maintenance" with 9 hours remaining. Curiously, it says it's only found 76.7 GB of backups, so I'm assuming (hoping?) after the deep maintenance it will go up to the correct 3.6 TB - hopefully without another file information sync... Memory usage is currenlty 828MB After the restart, "xmx" in /mnt/user/appdata/CrashPlanPRO/lo
  7. Under the 'advanced' view of the Docker page in the Unraid GUI. I assumed that the synchronisation task would be a high memory usage situation because of the comment from support: So I was thinking that the issue I was having (the "synchronising file information" task always failing and restarting), was due to low memory, and so am was hopeful that it would work correctly now that I've upped the memory allocation. And, indeed, even though the Docker is using the same amount of memory as before (around 1GB), the file info sync is now at 95% complete. So fingers crossed it
  8. The log contains the line -Xmx3072M I applied the Crashplan console command (java mx 4096) without restarting the container. My synchronisation is now at 83% so I'm going to wait to see if it completes before I change anything that will require a container restart. If the engine log shows 3072, then is it likely that Crashplan doesn't need more than the ~1.1 GB it's currently using? Thanks for your help.
  9. I should note that in the output from the 'inspect' command above, the setting: Is inconsistent with the variable I have entered in the Edit Container page, which is 4096M
  10. 21/05/2021 17:17:34 Statistics events Received/ RawEquiv ( saved) 21/05/2021 17:17:34 ClientCutText : 3 | 73/ 73 ( 0.0%) 21/05/2021 17:17:34 PointerEvent : 419 | 2514/ 2514 ( 0.0%) 21/05/2021 17:17:34 FramebufferUpdate : 1645 | 16450/ 16450 ( 0.0%) 21/05/2021 17:17:34 SetEncodings : 1 | 56/ 56 ( 0.0%) 21/05/2021 17:17:34 SetPixelFormat : 1 | 20/ 20 ( 0.0%) 21/05/2021 17:17:34 TOTALS : 2069 | 19113/ 19113 ( 0.0%) 21/05/2021 17:17:34 destroyed xda
  11. [ { "Id": "1e463f69531251a51b36df5b799649a82b9d90857c2b53b63f4a3fafdf20c8cf", "Created": "2021-03-20T12:55:54.112795714Z", "Path": "/init", "Args": [], "State": { "Status": "running", "Running": true, "Paused": false, "Restarting": false, "OOMKilled": false, "Dead": false, "Pid": 49262, "ExitCode": 0, "Error": "", "StartedAt": "2021-05-27T16:19:11.877809809Z", "FinishedAt": "2021-05-27T16:19:11.394276837Z" },
  12. I searched for the word "memory" in the log accessible from the Container icon menu, and it found no results. EDIT: Also, FWIW, the memory usage for the container hasn't gone above 1.11 GB, and has now dropped back to 1.099 GB. So it's barely using any more RAM even now. I currently backup 3.6 TB to their servers, so I would expect it to want to use more than the current 1.09 GB RAM.
  13. FYI: My account hasn't backed up for 15 days now because it is constantly "Synchronizing File Information." It seems to get to a point then starts over from the beginning again (the highest I've seen it get is maybe around the high 60s?). I contacted customer support, and they replied with the following: Looking at my Docker usage, it was indeed only using 1 GB RAM. So I popped into the app and applied the memory increase command (even though I thought I'd done it before). I could immediately see its RAM usage slowly start increasing. But then I remember
  14. Worth a shot: did you clear your browser cache? Does the Android/iOS app still work?
  15. Yep: similarly, I moved over to the new plugin upon the advice given by CA Backup, but have no interest in the remote access feature (I have a VPN already configured). As the "restore" feature isn't currently a full restore, I don't think it's the best advice for CA Backup to say that this method is deprecated, when it's actually superior. Plus with the change in the top banner, I'm uninstalling and moving back to CA Backup for flash backups (recognising that I need to keep a copy off-array, too). Will come back and check on the progress later (probably once encrypted, full backups e