November 12, 20223 yr On 11/7/2022 at 6:09 PM, Djoss said: A fix is in progres Installed and tested it for more than a day now - it works perfectly! Thank you!
November 16, 20223 yr Hi guys, I'm desperately trying to restore a backup but Crashplan is stuck on "Downloading files". I tried to only download smallish files to see if that would work but to no avail. Looking at my traffic it seems like it is downloading fine but then not being able to uncompress the files since nothing happens afterwards. According to the log everything seems to be in order. Sadly I get failed uploads rn so I can't post the logs in their entirety but here are some snippets: Restore Log: Quote INFO : 2022/11/16 03:47:18.927123 restore_tool.go:185: Read 4 bytes for message size INFO : 2022/11/16 03:47:18.927313 restore_tool.go:197: Need to read 14 more bytes INFO : 2022/11/16 03:47:18.927511 restore_tool.go:212: Finished reading 14 bytes for message INFO : 2022/11/16 03:47:18.927634 restore_tool.go:217: Finished sending byte array through channel INFO : 2022/11/16 03:47:18.927844 restore_tool.go:250: Request: request_id:1086914687985597102 request_type:KEEP_ALIVE request_keep_alive_data:{} INFO : 2022/11/16 03:47:18.927918 restore_tool.go:533: Received keep-alive message INFO : 2022/11/16 03:47:18.927976 restore_tool.go:604: Processing message: request_id:1086914687985597102 request_type:KEEP_ALIVE response_code:SUCCESS response_keep_alive_data:{} INFO : 2022/11/16 03:47:18.928062 restore_tool.go:614: Queued response message: request_id:1086914687985597102 request_type:KEEP_ALIVE response_code:SUCCESS response_keep_alive_data:{} INFO : 2022/11/16 03:47:18.928112 restore_tool.go:659: Wrote 4 response size bytes to response pipe, [0 0 0 16] INFO : 2022/11/16 03:47:18.928174 restore_tool.go:670: Wrote 16 bytes to response pipe INFO : 2022/11/16 03:47:28.928465 restore_tool.go:185: Read 4 bytes for message size INFO : 2022/11/16 03:47:28.928662 restore_tool.go:197: Need to read 14 more bytes INFO : 2022/11/16 03:47:28.928826 restore_tool.go:212: Finished reading 14 bytes for message INFO : 2022/11/16 03:47:28.929067 restore_tool.go:217: Finished sending byte array through channel INFO : 2022/11/16 03:47:28.929199 restore_tool.go:250: Request: request_id:1086914704762813102 request_type:KEEP_ALIVE request_keep_alive_data:{} INFO : 2022/11/16 03:47:28.929302 restore_tool.go:533: Received keep-alive message INFO : 2022/11/16 03:47:28.929348 restore_tool.go:604: Processing message: request_id:1086914704762813102 request_type:KEEP_ALIVE response_code:SUCCESS response_keep_alive_data:{} INFO : 2022/11/16 03:47:28.929401 restore_tool.go:614: Queued response message: request_id:1086914704762813102 request_type:KEEP_ALIVE response_code:SUCCESS response_keep_alive_data:{} INFO : 2022/11/16 03:47:28.929460 restore_tool.go:659: Wrote 4 response size bytes to response pipe, [0 0 0 16] INFO : 2022/11/16 03:47:28.929503 restore_tool.go:670: Wrote 16 bytes to response pipe INFO : 2022/11/16 03:47:38.929934 restore_tool.go:185: Read 4 bytes for message size INFO : 2022/11/16 03:47:38.930151 restore_tool.go:197: Need to read 14 more bytes INFO : 2022/11/16 03:47:38.930284 restore_tool.go:212: Finished reading 14 bytes for message INFO : 2022/11/16 03:47:38.930410 restore_tool.go:217: Finished sending byte array through channel INFO : 2022/11/16 03:47:38.930526 restore_tool.go:250: Request: request_id:1086914721556806318 request_type:KEEP_ALIVE request_keep_alive_data:{} INFO : 2022/11/16 03:47:38.930643 restore_tool.go:533: Received keep-alive message INFO : 2022/11/16 03:47:38.930810 restore_tool.go:604: Processing message: request_id:1086914721556806318 request_type:KEEP_ALIVE response_code:SUCCESS response_keep_alive_data:{} INFO : 2022/11/16 03:47:38.930893 restore_tool.go:614: Queued response message: request_id:1086914721556806318 request_type:KEEP_ALIVE response_code:SUCCESS response_keep_alive_data:{} INFO : 2022/11/16 03:47:38.930979 restore_tool.go:659: Wrote 4 response size bytes to response pipe, [0 0 0 16] INFO : 2022/11/16 03:47:38.931016 restore_tool.go:670: Wrote 16 bytes to response pipe INFO : 2022/11/16 03:47:48.931316 restore_tool.go:185: Read 4 bytes for message size INFO : 2022/11/16 03:47:48.931434 restore_tool.go:197: Need to read 14 more bytes INFO : 2022/11/16 03:47:48.931486 restore_tool.go:212: Finished reading 14 bytes for message INFO : 2022/11/16 03:47:48.931538 restore_tool.go:217: Finished sending byte array through channel INFO : 2022/11/16 03:47:48.931608 restore_tool.go:250: Request: request_id:1086914738334022318 request_type:KEEP_ALIVE request_keep_alive_data:{} INFO : 2022/11/16 03:47:48.931669 restore_tool.go:533: Received keep-alive message INFO : 2022/11/16 03:47:48.931727 restore_tool.go:604: Processing message: request_id:1086914738334022318 request_type:KEEP_ALIVE response_code:SUCCESS response_keep_alive_data:{} INFO : 2022/11/16 03:47:48.931774 restore_tool.go:614: Queued response message: request_id:1086914738334022318 request_type:KEEP_ALIVE response_code:SUCCESS response_keep_alive_data:{} INFO : 2022/11/16 03:47:48.931825 restore_tool.go:659: Wrote 4 response size bytes to response pipe, [0 0 0 16] INFO : 2022/11/16 03:47:48.931863 restore_tool.go:670: Wrote 16 bytes to response pipe INFO : 2022/11/16 03:47:58.932163 restore_tool.go:185: Read 4 bytes for message size INFO : 2022/11/16 03:47:58.932365 restore_tool.go:197: Need to read 14 more bytes INFO : 2022/11/16 03:47:58.932589 restore_tool.go:212: Finished reading 14 bytes for message INFO : 2022/11/16 03:47:58.933157 restore_tool.go:217: Finished sending byte array through channel INFO : 2022/11/16 03:47:58.933401 restore_tool.go:250: Request: request_id:1086914755111238318 request_type:KEEP_ALIVE request_keep_alive_data:{} INFO : 2022/11/16 03:47:58.933480 restore_tool.go:533: Received keep-alive message INFO : 2022/11/16 03:47:58.933530 restore_tool.go:604: Processing message: request_id:1086914755111238318 request_type:KEEP_ALIVE response_code:SUCCESS response_keep_alive_data:{} INFO : 2022/11/16 03:47:58.933591 restore_tool.go:614: Queued response message: request_id:1086914755111238318 request_type:KEEP_ALIVE response_code:SUCCESS response_keep_alive_data:{} INFO : 2022/11/16 03:47:58.933634 restore_tool.go:659: Wrote 4 response size bytes to response pipe, [0 0 0 16] INFO : 2022/11/16 03:47:58.933722 restore_tool.go:670: Wrote 16 bytes to response pipe Engine_error: Quote WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by com.code42.crypto.jce.ec.EcCurveLookup (file:/usr/local/crashplan/lib/c42-crypto-impl-15.2.7.jar) to method sun.security.util.CurveDB.lookup(java.security.spec.ECParameterSpec) WARNING: Please consider reporting this to the maintainers of com.code42.crypto.jce.ec.EcCurveLookup WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release Help would be much appreciated. I feel like I'm paying Crashplan for nothing.
November 16, 20223 yr Author Where are you restoring the files ? If it's under /storage, you have to first change container's settings and set permission to R/W for this path.
November 17, 20223 yr 15 hours ago, Djoss said: Where are you restoring the files ? If it's under /storage, you have to first change container's settings and set permission to R/W for this path. It is under storage and I have set the permissions to the nobody user group. This should be correct, right? Edited November 17, 20223 yr by DezzyTee Adding screenshots
November 17, 20223 yr Author 4 hours ago, DezzyTee said: It is under storage and I have set the permissions to the nobody user group. This should be correct, right? No, what you need to do is edit the container settings, activate the Advanced View, edit the "Storage" setting and change the Access Mode to Read/Write.
November 17, 20223 yr 6 hours ago, Djoss said: No, what you need to do is edit the container settings, activate the Advanced View, edit the "Storage" setting and change the Access Mode to Read/Write. Thank you so much. It seems like it worked.
November 19, 20223 yr My docker has been working for over a year without issue, but about a week ago I started getting alerts that it was not backing up. The docker will not start. Appreciate any advice you could provide. The log shows an error that I cannot find any reference to. "85-take-config-ownership.sh: terminated with error 1." [init ] container is starting... [cont-env ] loading container environment variables... [cont-env ] APP_NAME: loading... [cont-env ] APP_VERSION: loading... [cont-env ] DISPLAY: executing... [cont-env ] DISPLAY: terminated successfully. [cont-env ] DISPLAY: loading... [cont-env ] DOCKER_IMAGE_PLATFORM: loading... [cont-env ] DOCKER_IMAGE_VERSION: loading... [cont-env ] GTK_THEME: executing... [cont-env ] GTK_THEME: terminated successfully. [cont-env ] GTK_THEME: loading... [cont-env ] HOME: loading... [cont-env ] QT_STYLE_OVERRIDE: executing... [cont-env ] QT_STYLE_OVERRIDE: terminated successfully. [cont-env ] QT_STYLE_OVERRIDE: loading... [cont-env ] TAKE_CONFIG_OWNERSHIP: loading... [cont-env ] XDG_CACHE_HOME: loading... [cont-env ] XDG_CONFIG_HOME: loading... [cont-env ] XDG_DATA_HOME: loading... [cont-env ] XDG_RUNTIME_DIR: loading... [cont-env ] container environment variables initialized. [cont-secrets] loading container secrets... [cont-secrets] container secrets loaded. [cont-init ] executing container initialization scripts... [cont-init ] 10-certs.sh: executing... [cont-init ] 10-certs.sh: terminated successfully. [cont-init ] 10-check-app-niceness.sh: executing... [cont-init ] 10-check-app-niceness.sh: terminated successfully. [cont-init ] 10-cjk-font.sh: executing... [cont-init ] 10-cjk-font.sh: terminated successfully. [cont-init ] 10-clean-logmonitor-states.sh: executing... [cont-init ] 10-clean-logmonitor-states.sh: terminated successfully. [cont-init ] 10-clean-tmp-dir.sh: executing... [cont-init ] 10-clean-tmp-dir.sh: terminated successfully. [cont-init ] 10-fontconfig-cache-dir.sh: executing... [cont-init ] 10-fontconfig-cache-dir.sh: terminated successfully. [cont-init ] 10-init-users.sh: executing... [cont-init ] 10-init-users.sh: terminated successfully. [cont-init ] 10-jwm.sh: executing... [cont-init ] 10-jwm.sh: terminated successfully. [cont-init ] 10-nginx.sh: executing... [cont-init ] 10-nginx.sh: terminated successfully. [cont-init ] 10-vnc-password.sh: executing... [cont-init ] 10-vnc-password.sh: terminated successfully. [cont-init ] 10-web-data.sh: executing... [cont-init ] 10-web-data.sh: terminated successfully. [cont-init ] 10-x11-unix.sh: executing... [cont-init ] 10-x11-unix.sh: terminated successfully. [cont-init ] 10-xdg-runtime-dir.sh: executing... [cont-init ] 10-xdg-runtime-dir.sh: terminated successfully. [cont-init ] 15-install-pkgs.sh: executing... [cont-init ] 15-install-pkgs.sh: terminated successfully. [cont-init ] 55-crashplan-pro.sh: executing... [cont-init ] 55-crashplan-pro.sh: setting CrashPlan Engine maximum memory to 4096M [cont-init ] 55-crashplan-pro.sh: terminated successfully. [cont-init ] 55-validate_max_mem.sh: executing... [cont-init ] 55-validate_max_mem.sh: terminated successfully. [cont-init ] 85-take-config-ownership.sh: executing... [cont-init ] 85-take-config-ownership.sh: terminated with error 1.
November 24, 20223 yr Author On 11/19/2022 at 8:08 AM, jlmbkd said: My docker has been working for over a year without issue, but about a week ago I started getting alerts that it was not backing up. The docker will not start. Appreciate any advice you could provide. The log shows an error that I cannot find any reference to. "85-take-config-ownership.sh: terminated with error 1." [init ] container is starting... [cont-env ] loading container environment variables... [cont-env ] APP_NAME: loading... [cont-env ] APP_VERSION: loading... [cont-env ] DISPLAY: executing... [cont-env ] DISPLAY: terminated successfully. [cont-env ] DISPLAY: loading... [cont-env ] DOCKER_IMAGE_PLATFORM: loading... [cont-env ] DOCKER_IMAGE_VERSION: loading... [cont-env ] GTK_THEME: executing... [cont-env ] GTK_THEME: terminated successfully. [cont-env ] GTK_THEME: loading... [cont-env ] HOME: loading... [cont-env ] QT_STYLE_OVERRIDE: executing... [cont-env ] QT_STYLE_OVERRIDE: terminated successfully. [cont-env ] QT_STYLE_OVERRIDE: loading... [cont-env ] TAKE_CONFIG_OWNERSHIP: loading... [cont-env ] XDG_CACHE_HOME: loading... [cont-env ] XDG_CONFIG_HOME: loading... [cont-env ] XDG_DATA_HOME: loading... [cont-env ] XDG_RUNTIME_DIR: loading... [cont-env ] container environment variables initialized. [cont-secrets] loading container secrets... [cont-secrets] container secrets loaded. [cont-init ] executing container initialization scripts... [cont-init ] 10-certs.sh: executing... [cont-init ] 10-certs.sh: terminated successfully. [cont-init ] 10-check-app-niceness.sh: executing... [cont-init ] 10-check-app-niceness.sh: terminated successfully. [cont-init ] 10-cjk-font.sh: executing... [cont-init ] 10-cjk-font.sh: terminated successfully. [cont-init ] 10-clean-logmonitor-states.sh: executing... [cont-init ] 10-clean-logmonitor-states.sh: terminated successfully. [cont-init ] 10-clean-tmp-dir.sh: executing... [cont-init ] 10-clean-tmp-dir.sh: terminated successfully. [cont-init ] 10-fontconfig-cache-dir.sh: executing... [cont-init ] 10-fontconfig-cache-dir.sh: terminated successfully. [cont-init ] 10-init-users.sh: executing... [cont-init ] 10-init-users.sh: terminated successfully. [cont-init ] 10-jwm.sh: executing... [cont-init ] 10-jwm.sh: terminated successfully. [cont-init ] 10-nginx.sh: executing... [cont-init ] 10-nginx.sh: terminated successfully. [cont-init ] 10-vnc-password.sh: executing... [cont-init ] 10-vnc-password.sh: terminated successfully. [cont-init ] 10-web-data.sh: executing... [cont-init ] 10-web-data.sh: terminated successfully. [cont-init ] 10-x11-unix.sh: executing... [cont-init ] 10-x11-unix.sh: terminated successfully. [cont-init ] 10-xdg-runtime-dir.sh: executing... [cont-init ] 10-xdg-runtime-dir.sh: terminated successfully. [cont-init ] 15-install-pkgs.sh: executing... [cont-init ] 15-install-pkgs.sh: terminated successfully. [cont-init ] 55-crashplan-pro.sh: executing... [cont-init ] 55-crashplan-pro.sh: setting CrashPlan Engine maximum memory to 4096M [cont-init ] 55-crashplan-pro.sh: terminated successfully. [cont-init ] 55-validate_max_mem.sh: executing... [cont-init ] 55-validate_max_mem.sh: terminated successfully. [cont-init ] 85-take-config-ownership.sh: executing... [cont-init ] 85-take-config-ownership.sh: terminated with error 1. Are you using default container settings ?
January 20, 20233 yr Awesome software - used it for a long time and really appreciate it. Lately my CrashPlan is barfing (in the UI) about the inotify limit needing to be raised. As a result, it says that realtime file monitoring is not working. Is there a config parameter and recommended value to change inotify? Thanks
January 25, 20233 yr Author On 1/20/2023 at 10:11 AM, rtinker said: Awesome software - used it for a long time and really appreciate it. Lately my CrashPlan is barfing (in the UI) about the inotify limit needing to be raised. As a result, it says that realtime file monitoring is not working. Is there a config parameter and recommended value to change inotify? Thanks You can use the "Tips and Tweaks" unRAID plugin to increase the number of watches. The plugin shows the current number, along with the number used. There is no recommended values, since it depends directly on the number of files you backed. Using the plugin, try to increase the "Max User Watches" and then see how it goes.
January 31, 20233 yr I have a ton of files - mostly restart logs - in my log folder. 7904 objects: 2 directories, 7902 files (330 MB total) I assume I can get rid of most of these? Thanks!
February 5, 20233 yr If anyone else is seeing "Not Available" for the update to this container, then take a look at the following - it would appear this container is affected by a core bug that will be fixed in the next Unraid version. .
February 6, 20233 yr Author 19 hours ago, jtenman said: If anyone else is seeing "Not Available" for the update to this container, then take a look at the following - it would appear this container is affected by a core bug that will be fixed in the next Unraid version. . Thanks for the info! I was not aware of this issue.
February 6, 20233 yr 23 hours ago, jtenman said: If anyone else is seeing "Not Available" for the update to this container, then take a look at the following - it would appear this container is affected by a core bug that will be fixed in the next Unraid version. . thanks for this. I was baffled myself! Question -- Does this impact current functionality of the Docker? I suspect it doesn't, but figured I'd ask.
February 7, 20233 yr @Djoss Just an FYI in case you didn't receive their email about it, there is a branding update for Crashplan 11 that will affect the names of some packages or processes... Change is scheduled for March. https://support.crashplan.com/hc/en-us/articles/11427606025997
February 7, 20233 yr Author 8 minutes ago, ceyo14 said: @Djoss Just an FYI in case you didn't receive their email about it, there is a branding update for Crashplan 11 that will affect the names of some packages or processes... Change is scheduled for March. https://support.crashplan.com/hc/en-us/articles/11427606025997 Yes I've seen it. Hopefully it will be cosmetic changes only.
March 7, 20233 yr New issue in safari with the latest update. When I go to open the webUI in safari, I get a big red box error "undefined is not an object (evaluating 'i.generateKey')" Looks to be related to a security key. I found some notes referencing that for safari there are changes to some library that need to be made. It's ok for now for me because it works just fine in Firefox, and this is just for webUI access to the client. Appears that the change is in the code, not on the safari side? Anyway, wanted to make it known.
March 9, 20233 yr Anyone else seeing Unable to Connect to Destination? Otherwise everything seems to be fine on my end.
March 10, 20233 yr On 3/9/2023 at 7:42 AM, RAINMAN said: Anyone else seeing Unable to Connect to Destination? Otherwise everything seems to be fine on my end. I logged out and back in. It's maybe working now. its going through a re-sync.
March 28, 20233 yr Anyone else seeing "Unable to sign in." error when trying to sign in to the client? ui.log is showing warn RestAdapter: Error making service request to https://127.0.0.1:4244/v0/LoginRequest : Bad Request Clearing cache, deleting image and recreating it doesn't change it. Still get "Unable to sign in." EDIT: NM, problem went away on it's own. Edited April 2, 20233 yr by Fatal_Flaw
April 5, 20233 yr Hi all, anyone noticed a reduction in backup speed in recent times? Due to the lastpass hack, I decided to roll my client side keys and am in the process of doing a completely new backup. There is a lot of data, but it really is slow. For example, on one of my backups I have 3TB remaining and it is saying it will take 4.8 months to complete. I have a 1G connection that's giving me in reality around 700Mb/s upload. I suspect they might throttle transfers that take over a certain amount of time or something. Any thoughts? Thanks.
April 23, 20233 yr I can't get logged in... Has worked for yyears, and the data is there, but after a double disk failure, I have some restores to do. Says that it's "being updated", but has said that now for weeks. All apps and plugins updated, including this one. Help? Image cropped to not share user name, etc, but this happens after I try to login. I did change password in CrashPlan recently... Could that be it?
May 9, 20233 yr this is odd. I can back everything up except plex, which is what i was planning to be my main plan about using crashplan. i have set permissions and stuff. But it won't let me back up plex. does any1 have an idea
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.