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.

acurcione

Members
  • Joined

  • Last visited

  1. That did the trick. Upload time went from 89 days to 15 hours. I’d say there’s a definite issue in that build somewhere.
  2. Thanks for that. Trying now. I wasn’t sure how to revert to an earlier build. 😀
  3. Everything I see in my logs supports this, but I have no clue how to fix it. Is there something new or a change in the container that could be the cause? A setting or something? This is freaking painful.
  4. Anybody else’s upload speed gone to shit after the latest update? I’m not seeing any errors in logs anywhere, but the speeds reported have dropped to the low kbps range. I removed the speed cap in settings just in case, checked my actual internet connection, checked the Ethernet connection, and I see no issues. I rebooted the server as well and waiting to see if that does anything, but I’m not hopeful. I feel like I’m on the worst dial-up connection ever.
  5. FYI - so far so good. Apparently this hasn’t been working for a while even though the thing was running and said everything was backed up. I had a 3TB backlog which I’m guessing is why it kept erroring out after the update. Giving 8GB memory has kept it stable. I have more memory on the way so I’ll allocate more soon. Thanks much.
  6. Well that’s going to be a problem. I have a total of 37TB currently backed up. It doesn’t go up often any more, but when it does is many GB at a time. it’s currently just doing a scan and my memory usage has already doubled from before. I never had this thing stopping like this before and the size hasn’t changed. This is new since the update, but I never did see all those restarts in the logs cause I had no reason to go looking. If you’re right then even the 6Gb I allocated isn’t going to be enough and I obviously don’t have enough memory to do what’s recommended. Guess I’ll see how this goes.
  7. I increased the max mem substantially from the default when blank. I’ll see how that goes. No idea why I’d have that issue all of a sudden though. I’ve literally been running this for years.
  8. Now I got something in the logs. Says an out of memory error? I’ve not seen this before. The variable setting on the docker container is blank. Any recommendations?
  9. I can see in the history when it just stops, both in the UI and in the log files. I’m not sure where else to look for errors though. The UI error log is full of errors, but it seems to working so I have no idea if that has anything to do with it. here it is just in case: [936:1113/083714.032167: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 [936:1113/083714.849564: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 [936:1113/083714.849796: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 [936:1113/083714.869040: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") [936:1113/083714.869298: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") [936:1113/083714.869422: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") [936:1113/083714.869537: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") [2243:1113/083714.884187: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 [2243:1113/083714.898575:ERROR:viz_main_impl.cc(196)] Exiting GPU process due to errors during initialization [936:1113/083714.907892: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 [936:1113/083714.908125: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 [936:1113/083714.908298: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 [936:1113/083714.988668: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") [936:1113/083715.006942: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") [2448:1113/083715.069487: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 [2448:1113/083715.073034:ERROR:viz_main_impl.cc(196)] Exiting GPU process due to errors during initialization [2484:1113/083715.102722: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 [2484:1113/083715.106734:ERROR:viz_main_impl.cc(196)] Exiting GPU process due to errors during initialization [936:1113/083715.221764: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") [936:1113/083715.244763: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") [936:1113/083715.850714: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") [936:1113/083716.619686:ERROR:nss_util.cc(357)] After loading Root Certs, loaded==false: libnssckbi.so: cannot open shared object file: No such file or directory [936:1113/083716.620196:ERROR:cert_verify_proc_builtin.cc(701)] CertVerifyProcBuiltin for 127.0.0.1 failed: ----- Certificate i=0 (C=US,ST=Minnesota,L=Minneapolis,O=CrashPlan,OU=CrashPlan Service,CN=Default) ----- ERROR: No matching issuer found [936:1113/083716.683206: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") [936:1113/083716.844730: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") [936:1113/083716.902131: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") [936:1113/083717.106647: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") [936:1113/083717.210573: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") [936:1113/083717.281361: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") Warning: vkCreateInstance: Found no drivers! Warning: vkCreateInstance failed with VK_ERROR_INCOMPATIBLE_DRIVER at CheckVkSuccessImpl (../../third_party/dawn/src/dawn/native/vulkan/VulkanError.cpp:88) at CreateVkInstance (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:458) at Initialize (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:344) at Create (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:266) at operator() (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:521) Warning: Couldn't load Vulkan. Searched /usr/local/crashplan/electron/libvk_swiftshader.so, /usr/local/crashplan/electron/libvk_swiftshader.so, libvk_swiftshader.so. at operator() (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:299) at Initialize (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:310) at Create (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:266) at operator() (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:521) Warning: Failed to load libEGL.so at DiscoverPhysicalDevices (../../third_party/dawn/src/dawn/native/opengl/BackendGL.cpp:61)
  10. Thanks! Things are back to normal and I was able to update. Now CrashPlan Pro keeps crashing after some time and I can’t figure out why. I see nothing in the system logs, but when I hopped into the appdata folder it looks like I had issues I wasn’t aware of. The damn thing appears to just exit and then start up again just about an hour apart. Now it just stops. Any ideas on where to look to fix this? Honestly thought this thing was running smoothly cause I never saw any errors.
  11. Ah. Ok. I rebooted the server since it’s been on for 2 months and now all but on of my dockers shows “not available” status. Only one showing ok is Plex. Go figure. Haven’t had this issue since going to 6.12.+. I’ll wait a bit and hopefully this gets resolved.
  12. I was notified that 3 dockers from you - CrashPlan Pro, DupeGuru, and Hanbrake had updates. Every time I try to update it doesn’t pull anything, but doesn’t seem to throw an error in the console. I’ve tried all of them several times and no dice. This is the output from CrashPlan Pro. Ideas?
  13. Mine cleared up by the next day. Not sure what’s going on. It was weird.
  14. Anyone else having trouble with the server list? I’ve been running mine daily with no issues for a while, but when I went to do a manual test recently it threw back nothing. So I popped into settings where I had manually selected a nearby Spectrum server and the list that’s coming up now has very few servers and none anywhere near my state (Florida). If I go to the Speedtest website it auto selects the nearby server so I don’t know what’s going on. to make sure it was still at least working I changed it to Auto and it selected something in Nebraska or something. It worked though and didn’t give any errors.
  15. Yeah... I’m beginning to think I might need to. Duplicati and Backblaze B2 is probably the cheapest for large data storage. Definitely not as cheap as CrashPlan though. Sent from my iPad using Tapatalk Pro

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.