ryoko227 Posted May 18, 2023 Share Posted May 18, 2023 (edited) Update- Seems to have been an issue with my PC or browser. Had no issues with it today. Unable to type, nor paste Japanese characters into the search bar while looking for a file to restore. The file names all show correctly in Japanese, but I would like to be able to search them in Japanese as well. Am I missing something? Am running on Version: 6.11.5 Edited May 19, 2023 by ryoko227 Adding the update Quote Link to comment
Djoss Posted May 18, 2023 Author Share Posted May 18, 2023 On 5/9/2023 at 2:22 PM, bubbadk said: 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 This is because the "Plex Media Server" folder is part of the internal CrashPlan exclusion list... Quote Link to comment
Djoss Posted May 18, 2023 Author Share Posted May 18, 2023 3 hours ago, ryoko227 said: Unable to type, nor paste Japanese characters into the search bar while looking for a file to restore. The file names all show correctly in Japanese, but I would like to be able to search them in Japanese as well. Am I missing something? Am running on Version: 6.11.5 Did you try to paste with "Ctrl-v" ? If that doesn't work, can you provide an example of what you are trying to copy/paste ? Quote Link to comment
ryoko227 Posted May 19, 2023 Share Posted May 19, 2023 14 hours ago, Djoss said: Did you try to paste with "Ctrl-v" ? If that doesn't work, can you provide an example of what you are trying to copy/paste ? My apologies, not sure why it didn't work yesterday, but I tried again this morning and had no issues! Probably something was just funky with my PC or Chrome Thank you though for responding! @Djoss Quote Link to comment
Flemming Posted June 16, 2023 Share Posted June 16, 2023 This one has stopped working for me. The problem is that I am not able to access the Web UI. Also I don't think the backup are running. Tested http://10.0.24.10:7810/ http://10.0.24.10:7910/ http://10.0.24.10:5800/ Apply: Removing container: CrashPlanPRO Successfully removed container 'CrashPlanPRO' Command execution docker run -d --name='CrashPlanPRO' --net='host' --privileged=true -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e HOST_HOSTNAME="UnRAID" -e HOST_CONTAINERNAME="CrashPlanPRO" -e 'USER_ID'='99' -e 'GROUP_ID'='100' -e 'UMASK'='000' -e 'APP_NICENESS'='' -e 'DISPLAY_WIDTH'='1280' -e 'DISPLAY_HEIGHT'='768' -e 'SECURE_CONNECTION'='0' -e 'X11VNC_EXTRA_OPTS'='' -e 'CRASHPLAN_SRV_MAX_MEM'='' -e 'TCP_PORT_7810'='7810' -e 'TCP_PORT_7910'='7910' -e 'TCP_PORT_7810'='7810' -e 'TCP_PORT_7910'='7910' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:5800]' -l net.unraid.docker.icon='https://raw.githubusercontent.com/jlesage/docker-templates/master/jlesage/images/crashplan-pro-icon.png' -v '/mnt/user':'/storage':'ro' -v '/mnt/user/appdata/CrashPlanPRO':'/config':'rw' 'jlesage/crashplan-pro' 85aca7548e2a4af0062f41b17f411e76009e5c05467885dbd2fc7d552f231278 The command finished successfully! Log: [supervisor ] service 'certsmonitor' is disabled. [supervisor ] loading service 'nginx'... [supervisor ] loading service 'xvnc'... [supervisor ] loading service 'openbox'... [supervisor ] loading service 'CrashPlanEngine'... [supervisor ] loading service 'logmonitor'... [supervisor ] loading service 'logrotate'... [supervisor ] all services loaded. [supervisor ] starting services... [supervisor ] starting service 'xvnc'... [xvnc ] Xvnc TigerVNC 1.13.1 - built May 16 2023 17:43:49 [xvnc ] Copyright (C) 1999-2022 TigerVNC Team and many others (see README.rst) [xvnc ] See https://www.tigervnc.org for information on TigerVNC. [xvnc ] Underlying X server release 12014000 [xvnc ] Fri Jun 16 10:32:11 2023 [xvnc ] vncext: VNC extension running! [xvnc ] vncext: Listening for VNC connections on /tmp/vnc.sock (mode 0660) [xvnc ] (EE) [xvnc ] Fatal server error: [xvnc ] (EE) vncExtInit: failed to bind socket: Address in use (98) [xvnc ] (EE) [supervisor ] service 'xvnc' failed to be started: not ready after 5000 msec, giving up. [supervisor ] stopping service 'xvnc'... [supervisor ] service 'xvnc' exited (with status 1). [finish ] executing container finish scripts... [finish ] all container finish scripts executed. [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 ] GTK2_RC_FILES: executing... [cont-env ] GTK2_RC_FILES: terminated successfully. [cont-env ] GTK2_RC_FILES: 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 ] XDG_STATE_HOME: 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-nginx.sh: executing... [cont-init ] 10-nginx.sh: terminated successfully. [cont-init ] 10-openbox.sh: executing... [cont-init ] 10-openbox.sh: terminated successfully. [cont-init ] 10-set-tmp-dir-perms.sh: executing... [cont-init ] 10-set-tmp-dir-perms.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: 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... ** Press ANY KEY to close this window ** d Quote Link to comment
Gico Posted June 20, 2023 Share Posted June 20, 2023 Occasionally (like half the times I try) I can't login the web-ui saying Crashplan is "upgrading to a new version". Looking at the history log I see these messages beginning on March 10th: 06/20/23 04:55 PM CrashPlan started, version 11.0.1, GUID 632038001948010500 06/20/23 04:56 PM Downloading a new version of CrashPlan. 06/20/23 04:57 PM Download of upgrade failed - version 15252000061111, connection lost. 06/20/23 04:57 PM Unable to apply upgrade(s), retrying in one hour Docker image version is 23.06.1 which is the latest. Should the image updated to get rid of this issue? Thanks. Quote Link to comment
landS Posted June 21, 2023 Share Posted June 21, 2023 Howdy folks, Since updating to 6.12 from 6.11 I've been having the same issue as @Gico: I can't login the web-ui saying Crashplan is "upgrading to a new version" Quote Link to comment
Djoss Posted June 22, 2023 Author Share Posted June 22, 2023 There is a new version of CrashPlan available. I'm working on this and a new image will be released soon. However, I'm not sure why this prevent you from accessing the interface. Do you usually have to enter your username/password every time you access the interface ? Quote Link to comment
Gico Posted June 22, 2023 Share Posted June 22, 2023 Thanks Djoss. Yes, I have to enter password every time. My user name already exists in the web-ui. Quote Link to comment
Djoss Posted June 22, 2023 Author Share Posted June 22, 2023 Is this fixed with the new image ? Quote Link to comment
landS Posted June 26, 2023 Share Posted June 26, 2023 (edited) Thanks for the quick turn-around Djoss. Alas no, Docker's WebGui Still shows the "upgrading to new version" message after entering login credentials into Web Gui's Interface. Edit after 3 hours: Docker's WebGui still throws the "upgrading to new version" issue Docker's WebGui shows version 11.1.1.2 CP's Website Portal indicates Computer is Online & Backup is 100% CP's Website Portal shows version 11.1.1.2 Edited June 26, 2023 by landS Quote Link to comment
Djoss Posted June 28, 2023 Author Share Posted June 28, 2023 Having a message about the upgrade failure is expected. However, it should not re-appear after you close it. Quote Link to comment
landS Posted June 30, 2023 Share Posted June 30, 2023 Alas, this appears to be a troublesome beast. I updated from v6.12.1 to 6.12.2. In the Crashplan Docker’s WebUi it shows in the left hand popout: Crashplan v11.1.1 & Docker Image v23.06.2 Image 1 is what the Crashplan WebUi looks like when I start the docker. Image 2 is what the Crashplan WebUi looks like after I insert the password and click Continue. This is where the message pops up. If I close the WebUi and open it up the problem persists. Image 3 is what Crashplan’s Website looks like. The only item of note here is that the computer shows as online. Quote Link to comment
stanger89 Posted June 30, 2023 Share Posted June 30, 2023 (edited) Is anyone else seeing really high, essentially constant disk reads with Crashplan? I'm not sure how long this has been going on but I've noticed in the last few days, there's a near constant "incredible" amount of disk reads going on on my server. I installed itop and narrowed it down to crashplan (by tracing the PID with ps). The crashplan process is almost always at the top of the iotop disk read list. And iotop -a show a ton of accumulated reads several GB after only a couple minutes: I've logged into the web GUI and it says all backups have been completed for several hours, and I haven't written to any of the backup sets in the mean time. I've confirmed that stopping the Crashplan container stops the excessive reads. Has anyone else seen anything like this? Or have any ideas. I have 3 backup sets but they only account for about 2TB and most of it rarely changes. Edited June 30, 2023 by stanger89 Quote Link to comment
CajunCoding Posted June 30, 2023 Share Posted June 30, 2023 (edited) @Flemming I had a similar issue with CrashPlan UI not showing -- just an error page in the browser. I had to change the Docker Network type in my template from `Bridge` which used to work fine to `Host` (no other type worked), and now my UI is showing and launching correctly from the Unraid right click menu.... Edited June 30, 2023 by CajunCoding Quote Link to comment
pchoi94 Posted August 25, 2023 Share Posted August 25, 2023 Hello, I am planning to install and use UNRAID for the first time and one of my requirements is to use Crashplan for backups. I noticed from this thread that people are having issues but no posts since June 30th. Is this fixed and stable now? Quote Link to comment
Djoss Posted August 25, 2023 Author Share Posted August 25, 2023 Yes, CrashPlan always worked fine for me and for a lot of people! 1 Quote Link to comment
pchoi94 Posted August 25, 2023 Share Posted August 25, 2023 9 hours ago, Djoss said: Yes, CrashPlan always worked fine for me and for a lot of people! great to hear, thanks so much! Quote Link to comment
acurcione Posted November 11, 2023 Share Posted November 11, 2023 (edited) 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? Edited November 11, 2023 by acurcione Quote Link to comment
Djoss Posted November 11, 2023 Author Share Posted November 11, 2023 Yeah it seems to have an issue with the Docker Hub: images can't be pulled right now... This is what I have if I try to manually pull the image: docker pull jlesage/crashplan-pro Using default tag: latest Error response from daemon: Get "https://registry-1.docker.io/v2/": EOF Quote Link to comment
acurcione Posted November 11, 2023 Share Posted November 11, 2023 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. Quote Link to comment
Djoss Posted November 11, 2023 Author Share Posted November 11, 2023 Incident can be followed here: https://www.dockerstatus.com Quote Link to comment
acurcione Posted November 13, 2023 Share Posted November 13, 2023 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. Quote Link to comment
acurcione Posted November 13, 2023 Share Posted November 13, 2023 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) Quote Link to comment
acurcione Posted November 13, 2023 Share Posted November 13, 2023 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? Quote Link to comment
Recommended Posts
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.