10:33:30 The X server says there are 10 mouse buttons. 10:33:30 fast read: reset -defer ms to: 10 10:33:30 fast read: reset -wait ms to: 10 10:33:30 Xinerama: no blackouts needed (only one sub-screen) 10:33:30 Xinerama: number of sub-screens: 1 10:33:30 Xinerama is present and active (e.g. 10:33:30 Listening for VNC connections on TCP port 5900 10:33:30 X display :0 is 32bpp depth=24 true color 10:33:30 initialize_screen: fb_depth/fb_bpp/fb_Bpl 10:33:30 Read initial data from X display into framebuffer. If anyone needs any screen shots or other info, let me know. Below is my setup command and I also setup autorun.sh as mentioned above. I had this same container running in Docker on my Synology and never had this problem, so I am familiar with the setup. To provide a little background, I am setting up this QNAP NAS for the first time and coming from a Synology that died. If I reboot my TS-853BU and restart the container, it starts the process all over with the same results.

If I restart the container, the login hangs. CP just hangs in the 'Connecting' screen.

I can never get past that login once it copies my setting down (I don't think it is even getting through that phase). The problem I keep getting is after I log into the CP GUI and skip migrating files, the system will copy my settings to the new device/container and have me re-login.

I have tried everything I can find, and still can't get this to run properly. Triage notifications on the go with GitHub Mobile for iOS or Android.I just wanted to see if there was anyone who might be able to help me get this running. Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned. You should increase the inotify watch limit. To: Re: CrashPlan stopped backing up ( #264)Īlso, the log is flooded with inotify errors. How do I prevent the container from turning off? I turned it back on a couple weeks ago and the process started working again however, I checked again today and it was turned off again. It turns out that the container was turned off.

Crashplan pro docker