December 20, 20241 yr I recently went in to CrashPlan to do a test restore, but noticed when I try and change the restore destination from /config to my restore location, the container crashes and I need to restart it. I searched and found some similar crashes from a few years ago, but they all look like the issue was resolved...can anyone confirm if there is a new issue with picking the restore location causing a crash? To reproduce: Choose 'Other'; instant crash
February 7, 20251 yr I am having the exact same issue when trying to access the "Other" location. The same when I try to add a "local destination" as a backup set destination. Here's my error log from file /config/log/ui_error.log (but I am not completely sure if those errors are directly related to the crash): [1046:0207/091616.681220:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory [1046:0207/091616.947969:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory [1046:0207/091616.948045:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory [1046:0207/091616.949317:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") [1046:0207/091616.949385:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") [1046:0207/091616.949405:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") [1046:0207/091616.949417:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") [1046:0207/091616.949426:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") [1083:0207/091616.957721:ERROR:egl_util.cc(44)] Failed to load GLES library: /usr/local/crashplan/electron/libGLESv2.so: /usr/local/crashplan/electron/libGLESv2.so: cannot open shared object file: No such file or directory [1083:0207/091616.959429:ERROR:viz_main_impl.cc(181)] Exiting GPU process due to errors during initialization [1046:0207/091616.968282:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory [1046:0207/091616.968369:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory [1046:0207/091616.968404:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory [1046:0207/091617.017560:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") [1046:0207/091617.032588:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") [1173:0207/091617.065293:ERROR:egl_util.cc(44)] Failed to load GLES library: /usr/local/crashplan/electron/libGLESv2.so: /usr/local/crashplan/electron/libGLESv2.so: cannot open shared object file: No such file or directory [1173:0207/091617.067194:ERROR:viz_main_impl.cc(181)] Exiting GPU process due to errors during initialization [1205:0207/091617.087507:ERROR:egl_util.cc(44)] Failed to load GLES library: /usr/local/crashplan/electron/libGLESv2.so: /usr/local/crashplan/electron/libGLESv2.so: cannot open shared object file: No such file or directory [1205:0207/091617.092052:ERROR:viz_main_impl.cc(181)] Exiting GPU process due to errors during initialization [1046:0207/091617.208794:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") [1046:0207/091617.220887:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") [1046:0207/091617.635473:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") [1046:0207/091617.740137:ERROR:nss_util.cc(345)] After loading Root Certs, loaded==false: libnssckbi.so: cannot open shared object file: No such file or directory Edited February 7, 20251 yr by markusibrom added Log
February 21, 20251 yr I am getting app crashes whenever I try to edit, add, or delete a local destination within the GUI. I can send logs, but I am not sure which one would be relevant in this situation. Anyone have similar issue?
February 24, 20251 yr On 12/20/2024 at 5:54 PM, quinnjudge said: I recently went in to CrashPlan to do a test restore, but noticed when I try and change the restore destination from /config to my restore location, the container crashes and I need to restart it. I searched and found some similar crashes from a few years ago, but they all look like the issue was resolved...can anyone confirm if there is a new issue with picking the restore location causing a crash? To reproduce: Choose 'Other'; instant crash I am also experiencing the same issue. Has anyone had any luck resolving? But looks like it is a reported bug, https://github.com/jlesage/docker-crashplan-pro/issues/483 Edited February 24, 20251 yr by ezzys
March 24, 20251 yr I lost my containers in an UnRaid upgrade to version 7. I restored appData from backups, but CrashplanPro is not working correctly - it gets a Bus Error and shuts down right away. Any suggestions? [supervisor ] starting service 'nginx'... [nginx ] Listening for HTTP connections on port 5800. [supervisor ] starting service 'openbox'... [supervisor ] starting service 'xcompmgr'... [supervisor ] starting service 'CrashPlanEngine'... [supervisor ] starting service 'app'... [app ] Bus error [supervisor ] starting service 'logmonitor'... [logmonitor ] Monitoring log file: /config/log/service.log.0 [logmonitor ] Monitoring status file: /config/log/app.log [supervisor ] all services started. [supervisor ] service 'CrashPlanEngine' exited (got signal SIGBUS). [supervisor ] service 'app' exited (with status 135). [supervisor ] service 'app' exited, shutting down... (Disregard - I did an install from previous and now it appears to be working...) Edited March 24, 20251 yr by rtinker
March 30, 20251 yr I have been having a lot of issues with "Waiting for connection". I tried to clear the cache and that didn't seem to help at all. The other day, I added a new folder to a "Backup Set", it read all the files, did about 10% of them and then kept going to "Waiting for connection". I was able to ping 8.8.8.8 from the container so I know it has internet access. No obvious errors in the logs. I did reinstall the docker and that didnt work either. Any suggestions?
April 1, 20251 yr When I go and try to restore some files I am getting [1061:0331/234538.763453:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") [1061:0331/234538.810478:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") [1061:0331/234538.814275:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") [1061:0331/234538.852562:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") [1061:0331/234538.873599:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") [1061:0331/234538.887636:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
May 3, 20251 yr Hi, I am trying to use the CrashPlanPRO container to back up my new Unraid server. I was able to install it, set up my account and back up to the cloud with no issues. However, I would also like to use it to back up to a local, external hard drive. Unfortunately, when I try to do that, I get an error telling me that the filesystem is read-only. My external drive is a USB Hard drive. I created a pool with one slot and assigned it to the pool. I created a share and gave my userid read/write access to the share. I then changed the puid in the container script from 99 to 100 (the PUID corresponding with my userid). In CrashPlanPRO, I also tried creating a new folder on the share but get the same error message. I've tried formatting the share as XFS and BTRFS and I've tried a couple of different disks but I always get the same message. I'm sure it's just a setting or variable I'm missing. Can someone please advise me? Thanks!
May 8, 20251 yr On 3/30/2025 at 12:16 AM, Hawkins12 said: I have been having a lot of issues with "Waiting for connection". I tried to clear the cache and that didn't seem to help at all. The other day, I added a new folder to a "Backup Set", it read all the files, did about 10% of them and then kept going to "Waiting for connection". I was able to ping 8.8.8.8 from the container so I know it has internet access. No obvious errors in the logs. I did reinstall the docker and that didnt work either. Any suggestions? I've been getting this the last several days as well. I actually went 3 days without a successful backup. Now I'm getting multiple hours since last backup - used to be 15 minutes.
May 9, 20251 yr I'm just switching to CrashPlan Pro after years limping along with the Backblaze Personal docker. I just setup CrashPlan and, after some struggles logging in -- looks like I just leave the Authentication Code field blank? -- I selected my Shares and it's actively backing up about 60-100mbps. It seems too easy. Am I missing something? I had heard CrashPlan was slower than Backblaze and more problematic, but it seems to be just the opposite... Moreoever, from my quick chat with CrashPlan support, they basically said that while Unraid installs aren't officially supported, the use of CrashPlan Pro on a NAS setup like Unraid does NOT violate their TOS. (This isn't a dig at the Backblaze docker, as it seems to be the Backblaze team clamping down their software that's creating headaches w Backblaze/Unraid)
May 10, 20251 yr 3 hours ago, newoski said: I'm just switching to CrashPlan Pro after years limping along with the Backblaze Personal docker. I just setup CrashPlan and, after some struggles logging in -- looks like I just leave the Authentication Code field blank? -- I selected my Shares and it's actively backing up about 60-100mbps. It seems too easy. Am I missing something? I had heard CrashPlan was slower than Backblaze and more problematic, but it seems to be just the opposite... Moreoever, from my quick chat with CrashPlan support, they basically said that while Unraid installs aren't officially supported, the use of CrashPlan Pro on a NAS setup like Unraid does NOT violate their TOS. (This isn't a dig at the Backblaze docker, as it seems to be the Backblaze team clamping down their software that's creating headaches w Backblaze/Unraid) How are you seeing the speed that it is uploading at? I am finding my uploading to be ungodly slow. The app is telling me 70 days before a backup is complete.
May 10, 20251 yr 26 minutes ago, comfox said: How are you seeing the speed that it is uploading at? I am finding my uploading to be ungodly slow. The app is telling me 70 days before a backup is complete. i just look at the Unraid Dashboard. Outgoing bandwidth is upload speed, so long as you don’t have any simultaneous dockers etc uploading anything
May 12, 20251 yr try jlesage/crashplan-pro:v24.08.1 - this was the last version that had correct speed uploads. I did try forking and updating this tags base image with the latest front end version and it seemed to upload at the correct rate. Trouble is the base image has updates that are important (like fixing restore issues) therefore its a bit of a pain. Personally I used this image to upload the data then swapped to the latest tag.
May 12, 20251 yr 4 hours ago, Flubster said: try jlesage/crashplan-pro:v24.08.1 - this was the last version that had correct speed uploads. I did try forking and updating this tags base image with the latest front end version and it seemed to upload at the correct rate. Trouble is the base image has updates that are important (like fixing restore issues) therefore its a bit of a pain. Personally I used this image to upload the data then swapped to the latest tag. Thanks! This massively increased my upload speeds. Is there any harm bouncing back and forth and back again between latest and older version?
May 12, 20251 yr Author On 5/3/2025 at 1:11 PM, atwillia009 said: Hi, I am trying to use the CrashPlanPRO container to back up my new Unraid server. I was able to install it, set up my account and back up to the cloud with no issues. However, I would also like to use it to back up to a local, external hard drive. Unfortunately, when I try to do that, I get an error telling me that the filesystem is read-only. My external drive is a USB Hard drive. I created a pool with one slot and assigned it to the pool. I created a share and gave my userid read/write access to the share. I then changed the puid in the container script from 99 to 100 (the PUID corresponding with my userid). In CrashPlanPRO, I also tried creating a new folder on the share but get the same error message. I've tried formatting the share as XFS and BTRFS and I've tried a couple of different disks but I always get the same message. I'm sure it's just a setting or variable I'm missing. Can someone please advise me? Thanks! How did you configure the "Path" you added to the template / container settings ?
May 12, 20251 yr Author 4 hours ago, Flubster said: try jlesage/crashplan-pro:v24.08.1 - this was the last version that had correct speed uploads. I did try forking and updating this tags base image with the latest front end version and it seemed to upload at the correct rate. Trouble is the base image has updates that are important (like fixing restore issues) therefore its a bit of a pain. Personally I used this image to upload the data then swapped to the latest tag. Did you report the issue to CrashPlan support team? Note that jlesage/crashplan-pro:v24.08.1 integrates CrashPlan version 11.4.0.
May 12, 20251 yr 1 hour ago, Djoss said: Did you report the issue to CrashPlan support team? Note that jlesage/crashplan-pro:v24.08.1 integrates CrashPlan version 11.4.0. why would I report an issue with an unsupported installation with the support team? I noticed a github comment in your repo mentioning the speed issue, with no resolution. Also a comment earlier in this thread with exactly the same findings. Either the base image is problematic (which I assume its not) or crashplan have limited the upload. Its either one or the other.
May 14, 20251 yr Author On 5/12/2025 at 9:44 AM, Flubster said: why would I report an issue with an unsupported installation with the support team? It was maybe the situation years ago, but it's no longer the case. On 5/12/2025 at 9:44 AM, Flubster said: I noticed a github comment in your repo mentioning the speed issue, with no resolution. Also a comment earlier in this thread with exactly the same findings. Either the base image is problematic (which I assume its not) or crashplan have limited the upload. Its either one or the other. Note that speed has always been an issue/limitation/trade-off. But if you are seeing difference between two versions of CrashPlan, it's worth checking if it's a bug.
May 16, 20251 yr Author As a workaround/fallback method, you can copy-paste the shown URL and perform the login externally in your browser instead.
May 16, 20251 yr On 5/8/2025 at 7:05 PM, Free Man said: I've been getting this the last several days as well. I actually went 3 days without a successful backup. Now I'm getting multiple hours since last backup - used to be 15 minutes. Things seem to be back up and running, but this is how far behind it got... And no, I don't seem to get that smoking hot upload speed someone else posted.
May 17, 20251 yr I will report to crashplan, but forking the repository so it has the latest base image updates, but changing the dockerfile to pull 11.4.0.503 rather than 11.5.0.445, my uploads are back at normal speed. Interesting that crashplan doesn't moan it wants an update either.... So I'm running with it like that at the moment. Edited May 17, 20251 yr by Flubster Grammar
May 17, 20251 yr @Flubster Downloads and uploads both at full speed with your fork? Edited May 17, 20251 yr by newoski
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.