docker-crashplan-pro Starting service 'CrashplanEngine' Service exited (with status 0)

Current Behavior

Crashplan stuck in book loop.... Than ks as ever for help.

Expected Behavior

normal function

Steps To Reproduce

updated to latest and restarted crash plan

Environment

OS:
OS version: 7.2
CPU:
Docker version:
Device model: 716II+
Browser/OS: Safari

Container creation

restart with latest image

Container log

and repeated......
2023/06/26 10:11:36 | stdout | [supervisor     ] restarting service 'CrashPlanEngine'.
2023/06/26 10:11:36 | stdout | [supervisor     ] service 'CrashPlanEngine' exited (with status 0).
2023/06/26 10:11:06 | stdout | [supervisor     ] starting service 'CrashPlanEngine'...
2023/06/26 10:11:06 | stdout | [supervisor     ] restarting service 'CrashPlanEngine'.
2023/06/26 10:11:06 | stdout | [supervisor     ] service 'CrashPlanEngine' exited (with status 0).
2023/06/26 10:10:37 | stdout | [supervisor     ] starting service 'CrashPlanEngine'...
                                    │
2023/06/26 09:33:03 | stdout | │ Application:           CrashPlan for Small Business                  │
2023/06/26 09:33:03 | stdout | │                                                                      │
2023/06/26 09:33:03 | stdout | ╭――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――╮
2023/06/26 09:33:03 | stdout | [cont-init   ] 89-info.sh: executing...
2023/06/26 09:33:03 | stdout | [cont-init   ] 85-take-config-ownership.sh: terminated successfully.
2023/06/26 09:33:00 | stdout | [cont-init   ] 85-take-config-ownership.sh: executing...
2023/06/26 09:33:00 | stdout | [cont-init   ] 55-validate_max_mem.sh: terminated successfully.
2023/06/26 09:33:00 | stdout | [cont-init   ] 55-validate_max_mem.sh: executing...
2023/06/26 09:33:00 | stdout | [cont-init   ] 55-crashplan-pro.sh: terminated successfully.
2023/06/26 09:33:00 | stdout | [cont-init   ] 55-crashplan-pro.sh: setting CrashPlan Engine maximum memory to 4096M
2023/06/26 09:33:00 | stdout | [cont-init   ] 55-crashplan-pro.sh: executing...
2023/06/26 09:33:00 | stdout | [cont-init   ] 15-install-pkgs.sh: terminated successfully.
2023/06/26 09:33:00 | stdout | [cont-init   ] 15-install-pkgs.sh: executing...
2023/06/26 09:33:00 | stdout | [cont-init   ] 10-xdg-runtime-dir.sh: terminated successfully.
2023/06/26 09:33:00 | stdout | [cont-init   ] 10-xdg-runtime-dir.sh: executing...
2023/06/26 09:33:00 | stdout | [cont-init   ] 10-x11-unix.sh: terminated successfully.
2023/06/26 09:33:00 | stdout | [cont-init   ] 10-x11-unix.sh: executing...
2023/06/26 09:33:00 | stdout | [cont-init   ] 10-web-data.sh: terminated successfully.
2023/06/26 09:33:00 | stdout | [cont-init   ] 10-web-data.sh: executing...
2023/06/26 09:33:00 | stdout | [cont-init   ] 10-vnc-password.sh: terminated successfully.
2023/06/26 09:33:00 | stdout | [cont-init   ] 10-vnc-password.sh: executing...
2023/06/26 09:33:00 | stdout | [cont-init   ] 10-set-tmp-dir-perms.sh: terminated successfully.
2023/06/26 09:33:00 | stdout | [cont-init   ] 10-set-tmp-dir-perms.sh: executing...
2023/06/26 09:33:00 | stdout | [cont-init   ] 10-openbox.sh: terminated successfully.
2023/06/26 09:33:00 | stdout | [cont-init   ] 10-openbox.sh: executing...
2023/06/26 09:33:00 | stdout | [cont-init   ] 10-nginx.sh: terminated successfully.
2023/06/26 09:33:00 | stdout | [cont-init   ] 10-nginx.sh: executing...
2023/06/26 09:33:00 | stdout | [cont-init   ] 10-init-users.sh: terminated successfully.
2023/06/26 09:33:00 | stdout | [cont-init   ] 10-init-users.sh: executing...
2023/06/26 09:33:00 | stdout | [cont-init   ] 10-fontconfig-cache-dir.sh: terminated successfully.
2023/06/26 09:33:00 | stdout | [cont-init   ] 10-fontconfig-cache-dir.sh: executing...
2023/06/26 09:33:00 | stdout | [cont-init   ] 10-clean-tmp-dir.sh: terminated successfully.
2023/06/26 09:33:00 | stdout | [cont-init   ] 10-clean-tmp-dir.sh: executing...
2023/06/26 09:33:00 | stdout | [cont-init   ] 10-clean-logmonitor-states.sh: terminated successfully.
2023/06/26 09:33:00 | stdout | [cont-init   ] 10-clean-logmonitor-states.sh: executing...
2023/06/26 09:33:00 | stdout | [cont-init   ] 10-cjk-font.sh: terminated successfully.
2023/06/26 09:33:00 | stdout | [cont-init   ] 10-cjk-font.sh: executing...
2023/06/26 09:33:00 | stdout | [cont-init   ] 10-check-app-niceness.sh: terminated successfully.
2023/06/26 09:33:00 | stdout | [cont-init   ] 10-check-app-niceness.sh: executing...
2023/06/26 09:33:00 | stdout | [cont-init   ] 10-certs.sh: terminated successfully.
2023/06/26 09:33:00 | stdout | [cont-init   ] 10-certs.sh: executing...
2023/06/26 09:33:00 | stdout | [cont-init   ] executing container initialization scripts...
2023/06/26 09:33:00 | stdout | [cont-secrets] container secrets loaded.
2023/06/26 09:33:00 | stdout | [cont-secrets] loading container secrets...
2023/06/26 09:33:00 | stdout | [cont-env    ] container environment variables initialized.
2023/06/26 09:33:00 | stdout | [cont-env    ] XDG_STATE_HOME: loading...
2023/06/26 09:33:00 | stdout | [cont-env    ] XDG_RUNTIME_DIR: loading...
2023/06/26 09:33:00 | stdout | [cont-env    ] XDG_DATA_HOME: loading...
2023/06/26 09:32:59 | stdout | [cont-env    ] XDG_CONFIG_HOME: loading...
2023/06/26 09:32:59 | stdout | [cont-env    ] XDG_CACHE_HOME: loading...
2023/06/26 09:32:59 | stdout | [cont-env    ] TAKE_CONFIG_OWNERSHIP: loading...
2023/06/26 09:32:59 | stdout | [cont-env    ] QT_STYLE_OVERRIDE: loading...
2023/06/26 09:32:59 | stdout | [cont-env    ] QT_STYLE_OVERRIDE: terminated successfully.
2023/06/26 09:32:59 | stdout | [cont-env    ] QT_STYLE_OVERRIDE: executing...
2023/06/26 09:32:59 | stdout | [cont-env    ] HOME: loading...
2023/06/26 09:32:59 | stdout | [cont-env    ] GTK_THEME: loading...
2023/06/26 09:32:59 | stdout | [cont-env    ] GTK_THEME: terminated successfully.
2023/06/26 09:32:59 | stdout | [cont-env    ] GTK_THEME: executing...
2023/06/26 09:32:59 | stdout | [cont-env    ] GTK2_RC_FILES: loading...
2023/06/26 09:32:59 | stdout | [cont-env    ] GTK2_RC_FILES: terminated successfully.
2023/06/26 09:32:59 | stdout | [cont-env    ] GTK2_RC_FILES: executing...
2023/06/26 09:32:59 | stdout | [cont-env    ] DOCKER_IMAGE_VERSION: loading...
2023/06/26 09:32:59 | stdout | [cont-env    ] DOCKER_IMAGE_PLATFORM: loading...
2023/06/26 09:32:59 | stdout | [cont-env    ] DISPLAY: loading...
2023/06/26 09:32:59 | stdout | [cont-env    ] DISPLAY: terminated successfully.
2023/06/26 09:32:59 | stdout | [cont-env    ] DISPLAY: executing...
2023/06/26 09:32:59 | stdout | [cont-env    ] APP_VERSION: loading...
2023/06/26 09:32:59 | stdout | [cont-env    ] APP_NAME: loading...
2023/06/26 09:32:59 | stdout | [cont-env    ] loading container environment variables...
2023/06/26 09:32:59 | stdout | [init        ] container is starting...

Container inspect

No response

Anything else?

No response

Jun 26 '23 09:06 Slartybart

PS... Sorry if this isn't a bug, they seem to have changed the way of reporting issues.

Jun 26 '23 09:06 Slartybart

What version of Docker are you using ? Can you look at log/engine_error.log and log/engine_output.log, under the directory you mapped to /config ?

Some users had issue when using an old version of Docker. See https://github.com/jlesage/docker-crashplan-pro/issues/423

Jun 26 '23 14:06 jlesage

I assumed it was a newer version of Docker, but I may have got it confused with the new ‘container Manager’. It seems to be 20.10.23-1413. It’s on a synology machine. I’ll try and pull the other logs, but I’m away from home. Thanks as ever.

Jun 26 '23 14:06 Slartybart

Screenshot 2023-06-26 at 15 29 33

Jun 26 '23 14:06 Slartybart

By Docker version, I was talking about the version of Docker itself, the one you get when you run docker version.

Jun 26 '23 14:06 jlesage

I'm seeing this same issue on my unRaid system (v6.11.5). Here's the docker version info:

Linux 5.19.17-Unraid.
# docker version
Client:
 Version:           20.10.21
 API version:       1.41
 Go version:        go1.18.7
 Git commit:        baeda1f
 Built:             Tue Oct 25 17:56:30 2022
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.21
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.18.7
  Git commit:       3056208
  Built:            Tue Oct 25 18:02:03 2022
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.6.9
  GitCommit:        1c90a442489720eec95342e1789ee8a5e1b9536f
 runc:
  Version:          1.1.4
  GitCommit:        v1.1.4-0-g5fd4c4d1
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Jul 20 '23 18:07 bdegeeter

Sorry for the delay... is this what you need? Screenshot 2023-07-27 at 17 14 48

Jul 28 '23 09:07 Slartybart

This is with my Synology: I ended up deleting the container and starting again. When making the new container I assigned 'high privileges' to the new container, set the ports to 'host' rather than 'bridge'. Then of course I had to 'replace the existing device' and told it to skip files (so it wouldn't delete stuff missing from the drives I'm backing up), but so far so good..... I've only added one of the drives to be backed up initially, but it's already found most of the one drive I've added, and although slow, it's syncing files and blocks ok. Fingers crossed.

Jul 31 '23 09:07 Slartybart

I'm experiencing the same behavior since a Synology update and reboot docker version Client: Version: 20.10.23 API version: 1.41 Go version: go1.19.1 Git commit: 876964a Built: Wed Jun 14 06:00:26 2023 OS/Arch: linux/amd64 Context: default Experimental: true

Aug 03 '23 19:08 jasonmarkperez

Downgrading to v23.06.1 seems to fix this for me, so I guess I'll hold at that version for now.

Aug 05 '23 20:08 jasonmarkperez

docker-crashplan-pro docker-crashplan-pro copied to clipboard

Starting service 'CrashplanEngine' Service exited (with status 0)

Current Behavior

Expected Behavior

Steps To Reproduce

Environment

Container creation

Container log

Container inspect

Anything else?

docker-crashplan-pro
docker-crashplan-pro copied to clipboard