23.04.1 problems... doesn't run (black screen, no RAM usage, etc.)

[dav1n]

I bravely upgraded to 23.04.1 shortly after you released it.

The browser when connecting to its 5800 port, is as follows:

• fully black main screen
• Left side-bar pop-out is there, and seems to look fine
• Top of the screen briefl has a gray bar that says "CrashPlan for Small Business - Connected (encrypted)" on reload, but then retracts.

From the QNAP Container Station, it shows that the container is there, but has 1% CPU | 0% RAM | 0 B /s | 0 B /s.

I'm going to try to revert to previous versions, for now.

Let me know if there is a way to collect any debug info for you.

[dav1n]

Pulling into a terminal shell shows the following processes: /tmp # ps augx
PID USER TIME COMMAND
1 root 0:00 /opt/base/sbin/cinit --progname supervisor --default-service-uid 0 --default-service-gid 0
963 root 0:00 Xvnc -nolisten tcp -nolisten local -listen unix -geometry 1920x1080 -depth 24 -rfbport=-1 -rfbunixpath=/tmp/vnc.sock -rfbunixmode=0660 -SecurityTypes=None -desktop=CrashPlan for Small Business :0
968 root 0:00 nginx: master process /opt/base/sbin/nginx -c /opt/base/etc/nginx/nginx.conf -g daemon off;
974 root 0:00 nginx: worker process
975 root 0:00 nginx: worker process
978 root 0:00 /opt/base/bin/openbox --config-file /var/run/openbox/rc.xml --startup touch /var/run/openbox/openbox.ready
1000 root 0:00 logmonitor
8860 root 0:00 /bin/sh
9381 root 0:00 [startapp.sh]
9383 root 0:00 [CrashPlanServic]
9387 root 0:00 ps augx

[jlesage]

Container's log ? docker logs <container name>

Also, how long did you wait in this state ? It can take some time for CrashPlan to load.

[dav1n]

It tries, but crashed immediately.

Here's the relevant snippet from the logs (let me know if you need more). And if there is any other debugging info that you're like me to gather.

... [supervisor ] loading service 'logmonitor'... [supervisor ] loading service 'logrotate'... [supervisor ] all services loaded. [supervisor ] starting services... [supervisor ] starting service 'CrashPlanEngine'... [supervisor ] ERROR: service 'CrashPlanEngine' failed to be started: not ready after 30000 msec, giving up. [supervisor ] starting service 'xvnc'... [xvnc ] Xvnc TigerVNC 1.13.0 - built Mar 4 2023 01:15:35 [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 12013000 [xvnc ] Fri Apr 14 09:14:09 2023 [xvnc ] vncext: VNC extension running! [xvnc ] vncext: Listening for VNC connections on /tmp/vnc.sock (mode 0660) [xvnc ] vncext: created VNC server for screen 0 [supervisor ] starting service 'nginx'... [nginx ] Listening for HTTPs connections on port 5800. [supervisor ] starting service 'openbox'... [supervisor ] starting service 'app'... [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 (with status 1). [supervisor ] restarting service 'CrashPlanEngine'. [supervisor ] starting service 'CrashPlanEngine'... [app ] Trace/breakpoint trap [supervisor ] service 'app' exited (with status 133). [supervisor ] service 'CrashPlanEngine' exited (with status 1). [supervisor ] restarting service 'app'. [supervisor ] starting service 'app'... [supervisor ] restarting service 'CrashPlanEngine'. [supervisor ] starting service 'CrashPlanEngine'... [app ] Trace/breakpoint trap [supervisor ] service 'app' exited (with status 133). [supervisor ] service 'CrashPlanEngine' exited (with status 1). [supervisor ] restarting service 'app'. [supervisor ] starting service 'app'... [supervisor ] restarting service 'CrashPlanEngine'. [supervisor ] starting service 'CrashPlanEngine'... [app ] Trace/breakpoint trap ... (ad infinitum)

[lcmsilek]

Looks like the JVM is not able to start, take a look below:

ui_error.log: [1002:0415/081358.486044:ERROR:platform_thread_posix.cc(148)] pthread_create: Operation not permitted (1) (over and over) engine_output.log: Launching as root jvm_args file found, loading arguments Paths: cwd: /usr/local/crashplan appData: /usr/local/crashplan jvm_args: /usr/local/crashplan/conf/jvm_args JVM arguments in use: -Dsun.jnu.encoding=UTF-8 -Dfile.encoding=UTF-8 -Dsun.net.inetaddr.ttl=300 -Dnetworkaddress.cache.ttl=300 -Dsun.net.inetaddr.negative.ttl=0 -Dnetworkaddress.cache.negative.ttl=0 -Dapp=CrashPlanService -DappBaseName=CrashPlan -Djna.nosys=true -Djava.awt.headless=true -DCrashPlan=CrashPlan -Dnashorn.args=--no-deprecation-warning -Dc42.installation.enforcement.enabled=true -XX:-ShrinkHeapInSteps -XX:MaxHeapFreeRatio=30 -XX:MinHeapFreeRatio=15 -Djava.library.path=/usr/local/crashplan/nlib -Djna.library.path=/usr/local/crashplan/nlib -Dc42.log.config=/usr/local/crashplan/conf/service.log.xml -Xmx3072m Arguments in use:

Initializing the JVM arguments. Creating the Java virtual machine. Number of arguments: 21 Error occurred during initialization of VM Unable to load native library: @<A3>^P'<FD>^? (over and over and it tries to start)

[jlesage]

Can you check log/engine_error.log and log/engine_output.log ?

[lcmsilek]

engine_error.log is blank

engine_output.log: Launching as root jvm_args file found, loading arguments Paths: cwd: /usr/local/crashplan appData: /usr/local/crashplan jvm_args: /usr/local/crashplan/conf/jvm_args JVM arguments in use: -Dsun.jnu.encoding=UTF-8 -Dfile.encoding=UTF-8 -Dsun.net.inetaddr.ttl=300 -Dnetworkaddress.cache.ttl=300 -Dsun.net.inetaddr.negative.ttl=0 -Dnetworkaddress.cache.negative.ttl=0 -Dapp=CrashPlanService -DappBaseName=CrashPlan -Djna.nosys=true -Djava.awt.headless=true -DCrashPlan=CrashPlan -Dnashorn.args=--no-deprecation-warning -Dc42.installation.enforcement.enabled=true -XX:-ShrinkHeapInSteps -XX:MaxHeapFreeRatio=30 -XX:MinHeapFreeRatio=15 -Djava.library.path=/usr/local/crashplan/nlib -Djna.library.path=/usr/local/crashplan/nlib -Dc42.log.config=/usr/local/crashplan/conf/service.log.xml -Xmx3072m Arguments in use:

Initializing the JVM arguments. Creating the Java virtual machine. Number of arguments: 21 Error occurred during initialization of VM Unable to load native library: @<A3>^P'<FD>^?

[dav1n]

My engine_error.log is also empty.

And here is what repeats continuously in engine_output.log:

Initializing the JVM arguments. Creating the Java virtual machine. Number of arguments: 21 Error occurred during initialization of VM Unable to load native library: ▒▒▒▒▒? Launching as root jvm_args file found, loading arguments Paths: cwd: /usr/local/crashplan appData: /usr/local/crashplan jvm_args: /usr/local/crashplan/conf/jvm_args JVM arguments in use: -Dsun.jnu.encoding=UTF-8 -Dfile.encoding=UTF-8 -Dsun.net.inetaddr.ttl=300 -Dnetworkaddress.cache.ttl=300 -Dsun.net.inetaddr.negative.ttl=0 -Dnetworkaddress.cache.negative.ttl=0 -Dapp=CrashPlanService -DappBaseName=CrashPlan -Djna.nosys=true -Djava.awt.headless=true -DCrashPlan=CrashPlan -Dnashorn.args=--no-deprecation-warning -Dc42.installation.enforcement.enabled=true -XX:-ShrinkHeapInSteps -XX:MaxHeapFreeRatio=30 -XX:MinHeapFreeRatio=15 -Djava.library.path=/usr/local/crashplan/nlib -Djna.library.path=/usr/local/crashplan/nlib -Dc42.log.config=/usr/local/crashplan/conf/service.log.xml -Xmx8192m Arguments in use:

[jlesage]

Just to make sure, can you instead run tail -f on the files and wait about a minute ?

[jlesage]

If this is not showing anything new, you might have to check in service.log.0.

[jdwilley]

I'm experiencing the same output at the terminal, same blank engine_error.log file, but my engine_output.log has this extra error at the end about pthread_create failing and insufficient memory. I'm running with CRASHPLAN_SRV_MAX_MEM=2048M, could that be too little?

Launching as root
jvm_args file found, loading arguments
Paths:
  cwd:      /usr/local/crashplan
  appData:  /usr/local/crashplan
  jvm_args: /usr/local/crashplan/conf/jvm_args
JVM arguments in use:
-Dsun.jnu.encoding=UTF-8
-Dfile.encoding=UTF-8
-Dsun.net.inetaddr.ttl=300
-Dnetworkaddress.cache.ttl=300
-Dsun.net.inetaddr.negative.ttl=0
-Dnetworkaddress.cache.negative.ttl=0
-Dapp=CrashPlanService
-DappBaseName=CrashPlan
-Djna.nosys=true
-Djava.awt.headless=true
-DCrashPlan=CrashPlan
-Dnashorn.args=--no-deprecation-warning
-Dc42.installation.enforcement.enabled=true
-XX:-ShrinkHeapInSteps
-XX:MaxHeapFreeRatio=30
-XX:MinHeapFreeRatio=15
-Djava.library.path=/usr/local/crashplan/nlib
-Djna.library.path=/usr/local/crashplan/nlib
-Dc42.log.config=/usr/local/crashplan/conf/service.log.xml
-Xmx2048M
Arguments in use:

Initializing the JVM arguments.
Creating the Java virtual machine.
Number of arguments: 21
[0.011s][warning][os,thread] Failed to start thread "GC Thread#0" - pthread_create failed (EPERM) for attributes: stacksize: 1024k, guardsize: 4k, detached.

#
# There is insufficient memory for the Java Runtime Environment to continue.
# Cannot create worker GC thread. Out of system resources.
# An error report file with more information is saved as:
# /usr/local/crashplan/hs_err_pid8864.log

[dav1n]

On my QNAP, tail -f on engine_output is just a repeat of the same "paragraph", but with different random characters after "Unable to load native library:"

Initializing the JVM arguments. Creating the Java virtual machine. Number of arguments: 21 Error occurred during initialization of VM Unable to load native library: ▒6▒ Launching as root jvm_args file found, loading arguments Paths: cwd: /usr/local/crashplan appData: /usr/local/crashplan jvm_args: /usr/local/crashplan/conf/jvm_args JVM arguments in use: -Dsun.jnu.encoding=UTF-8 -Dfile.encoding=UTF-8 -Dsun.net.inetaddr.ttl=300 -Dnetworkaddress.cache.ttl=300 -Dsun.net.inetaddr.negative.ttl=0 -Dnetworkaddress.cache.negative.ttl=0 -Dapp=CrashPlanService -DappBaseName=CrashPlan -Djna.nosys=true -Djava.awt.headless=true -DCrashPlan=CrashPlan -Dnashorn.args=--no-deprecation-warning -Dc42.installation.enforcement.enabled=true -XX:-ShrinkHeapInSteps -XX:MaxHeapFreeRatio=30 -XX:MinHeapFreeRatio=15 -Djava.library.path=/usr/local/crashplan/nlib -Djna.library.path=/usr/local/crashplan/nlib -Dc42.log.config=/usr/local/crashplan/conf/service.log.xml -Xmx8192m Arguments in use:

service.log.0 does not get anything logged to it from this new version. The last thing in it is always still stuff timestamped from when I was still running the previous release (which I keep restarting, so that things will continue backing up).

[johnripper1]

I am experiencingthe same issue on my Cobtainer Stationon my QNAP device with the lastest release

I'm experiencing the same output at the terminal, same blank engine_error.log file, but my engine_output.log has this extra error at the end about pthread_create failing and insufficient memory. I'm running with CRASHPLAN_SRV_MAX_MEM=2048M, could that be too little?

I am starting it with 10G RAM, but same error. The 10G RAM have been Stanard since years. Furthermore it crashes at the very beginning, so it's not too little if if worked before.

See https://github.com/jlesage/docker-crashplan-pro/issues/416#issuecomment-1512778971

If i can help somehow, pls let me know.

[JustAVapor]

I'm having a similar issue as OP. Running on a Debian system. I run using docker-compose.

Nothing in the engine_error.log engine_output.log gives me:

Launching as root jvm_args file found, loading arguments Paths: cwd: /usr/local/crashplan appData: /usr/local/crashplan jvm_args: /usr/local/crashplan/conf/jvm_args JVM arguments in use: -Dsun.jnu.encoding=UTF-8 -Dfile.encoding=UTF-8 -Dsun.net.inetaddr.ttl=300 -Dnetworkaddress.cache.ttl=300 -Dsun.net.inetaddr.negative.ttl=0 -Dnetworkaddress.cache.negative.ttl=0 -Dapp=CrashPlanService -DappBaseName=CrashPlan -Djna.nosys=true -Djava.awt.headless=true -DCrashPlan=CrashPlan -Dnashorn.args=--no-deprecation-warning -Dc42.installation.enforcement.enabled=true -XX:-ShrinkHeapInSteps -XX:MaxHeapFreeRatio=30 -XX:MinHeapFreeRatio=15 -Djava.library.path=/usr/local/crashplan/nlib -Djna.library.path=/usr/local/crashplan/nlib -Dc42.log.config=/usr/local/crashplan/conf/service.log.xml -Xmx16384m Arguments in use:

Initializing the JVM arguments. Creating the Java virtual machine. Number of arguments: 21 Error occurred during initialization of VM Unable to load native library: PD???

The only way I can get Crashplan to work is to go back to v23.03.1 Giving it time is not the issue either. Normally, things start coming up within 10-20 seconds. I've given this several minutes (15+) and nothing comes up.

[Atr3id3s]

Same issue here.

Upgraded today, engine_output.log just ends with this over and over:

Initializing the JVM arguments.
Creating the Java virtual machine.
Number of arguments: 21
Error occurred during initialization of VM
Unable to load native library: `̕�

[johnripper1]

The only way I can get Crashplan to work is to go back to v23.03.1

Same here.

[axemanozh]

For anyone on QNAP having this problem, are you running QTS 5? Just curious if that might be an issue; I am running the latest version in Container Station without issue on QTS 4.

[ning42]

just to share , running a QNAP QTS 5.0.1.2376, with the jlesage/crashplan-pro:latest with no problems Using watchtower to update Currently it is running v23.04.2 of crashplan

[NS1234567]

is this working for most QNAP users? . . . looking to apply the update shortly--thanks

[charlesdunbar]

I was also getting the pthread_create: Operation not permitted error on TrueNAS with a rancher vm. From what I can tell, a newer version of Docker would help, or disabling seccomp for the container.

Upgrading likely wasn't an option for me, so I added --security-opt=seccomp:unconfined to my docker run command and was able to have the container start without crashing.

[johnripper1]

Upgrading likely wasn't an option for me, so I added --security-opt=seccomp:unconfined to my docker run command and was able to have the container start without crashing.

I love you dude. That did the trick. Thank you!

[dav1n]

The same security-opt worked for me!!! Thank you @charlesdunbar !

[JustAVapor]

I was also getting the pthread_create: Operation not permitted error on TrueNAS with a rancher vm. From what I can tell, a newer version of Docker would help, or disabling seccomp for the container.

Upgrading likely wasn't an option for me, so I added --security-opt=seccomp:unconfined to my docker run command and was able to have the container start without crashing.

How might I run this with Docker compose?

[NS1234567]

FYI for QNAP users: when I logged into my QNAP today I saw container station app had updated--when I launched the app it informed me that a new version of Docker/certificate had also been installed. I had been running crashplan version 10 but after this container station update today, I just went ahead and installed crashplan version 11.0 (latest image) per the usual "inplace" upgrade method that I've used x years now--everything works fine w no seccomp edits or any other customizations to my old Docker run command. . . upgraded to version 11.0 with no change to anything I've been doing x years w no problems thus far....

[JustAVapor]

My problems were finally solved this morning with a couple upgrades. First, I upgraded my server from Debian Buster to Bullseye (and will have to do it again next week, when Bookworm is officially moved to the "Stable" stream.) I also upgraded the Docker engine from 18.09.1 to 24.0.2

[Venerit]

I was able to get it to work by adding

security_opt: - seccomp:unconfined

To my docker-compose file under the crashplan-pro service.

[wraithxiv]

I was able to get it to work by adding

security_opt: - seccomp:unconfined

To my docker-compose file under the crashplan-pro service.

This resolved my issue as well! Thanks!!!