docker-crashplan-pro
docker-crashplan-pro copied to clipboard
jlesage
Server disconnected 1006
I noticed that my backups hadn't happened in a few days and found out i am receiving this error message when i go to the web page. I pulled the latest version and started up the new container with the same error. I hope someone could point me in the right direction. Here is my console output:
[services.d] starting openbox... [openbox] starting... The XKEYBOARD keymap compiler (xkbcomp) reports:
Internal error: Could not resolve keysym XF86FullScreen Errors from xkbcomp are not fatal to the X server [services.d] starting x11vnc... [services.d] starting app... [x11vnc] starting... [app] starting CrashPlan for Small Business... 05/01/2022 10:25:04 passing arg to libvncserver: -rfbport 05/01/2022 10:25:04 passing arg to libvncserver: 5900 05/01/2022 10:25:04 passing arg to libvncserver: -rfbportv6 05/01/2022 10:25:04 passing arg to libvncserver: -1 05/01/2022 10:25:04 passing arg to libvncserver: -httpportv6 05/01/2022 10:25:04 passing arg to libvncserver: -1 05/01/2022 10:25:04 passing arg to libvncserver: -desktop 05/01/2022 10:25:04 passing arg to libvncserver: CrashPlan for Small Business [services.d] done. 05/01/2022 10:25:04 x11vnc version: 0.9.14 lastmod: 2015-11-14 pid: 10122 05/01/2022 10:25:04 Using X display :0 05/01/2022 10:25:04 rootwin: 0x43 reswin: 0x400001 dpy: 0xd86d9b20 05/01/2022 10:25:04 05/01/2022 10:25:04 ------------------ USEFUL INFORMATION ------------------ 05/01/2022 10:25:04 X DAMAGE available on display, using it for polling hints. 05/01/2022 10:25:04 To disable this behavior use: '-noxdamage' 05/01/2022 10:25:04 05/01/2022 10:25:04 Most compositing window managers like 'compiz' or 'beryl' 05/01/2022 10:25:04 cause X DAMAGE to fail, and so you may not see any screen 05/01/2022 10:25:04 updates via VNC. Either disable 'compiz' (recommended) or 05/01/2022 10:25:04 supply the x11vnc '-noxdamage' command line option. 05/01/2022 10:25:04 X COMPOSITE available on display, using it for window polling. 05/01/2022 10:25:04 To disable this behavior use: '-noxcomposite' 05/01/2022 10:25:04 05/01/2022 10:25:04 Wireframing: -wireframe mode is in effect for window moves. 05/01/2022 10:25:04 If this yields undesired behavior (poor response, painting 05/01/2022 10:25:04 errors, etc) it may be disabled: 05/01/2022 10:25:04 - use '-nowf' to disable wireframing completely. 05/01/2022 10:25:04 - use '-nowcr' to disable the Copy Rectangle after the 05/01/2022 10:25:04 moved window is released in the new position. 05/01/2022 10:25:04 Also see the -help entry for tuning parameters. 05/01/2022 10:25:04 You can press 3 Alt_L's (Left "Alt" key) in a row to 05/01/2022 10:25:04 repaint the screen, also see the -fixscreen option for 05/01/2022 10:25:04 periodic repaints. 05/01/2022 10:25:04 GrabServer control via XTEST. 05/01/2022 10:25:04 05/01/2022 10:25:04 Scroll Detection: -scrollcopyrect mode is in effect to 05/01/2022 10:25:04 use RECORD extension to try to detect scrolling windows 05/01/2022 10:25:04 (induced by either user keystroke or mouse input). 05/01/2022 10:25:04 If this yields undesired behavior (poor response, painting 05/01/2022 10:25:04 errors, etc) it may be disabled via: '-noscr' 05/01/2022 10:25:04 Also see the -help entry for tuning parameters. 05/01/2022 10:25:04 You can press 3 Alt_L's (Left "Alt" key) in a row to 05/01/2022 10:25:04 repaint the screen, also see the -fixscreen option for 05/01/2022 10:25:04 periodic repaints. 05/01/2022 10:25:04 05/01/2022 10:25:04 XKEYBOARD: number of keysyms per keycode 7 is greater 05/01/2022 10:25:04 than 4 and 51 keysyms are mapped above 4. 05/01/2022 10:25:04 Automatically switching to -xkb mode. 05/01/2022 10:25:04 If this makes the key mapping worse you can 05/01/2022 10:25:04 disable it with the "-noxkb" option. 05/01/2022 10:25:04 Also, remember "-remap DEAD" for accenting characters. 05/01/2022 10:25:04 05/01/2022 10:25:04 X FBPM extension not supported. Xlib: extension "DPMS" missing on display ":0". 05/01/2022 10:25:04 X display is not capable of DPMS. 05/01/2022 10:25:04 -------------------------------------------------------- 05/01/2022 10:25:04 05/01/2022 10:25:04 Default visual ID: 0x21 05/01/2022 10:25:04 Read initial data from X display into framebuffer. 05/01/2022 10:25:04 initialize_screen: fb_depth/fb_bpp/fb_Bpl 24/32/5120 05/01/2022 10:25:04 05/01/2022 10:25:04 X display :0 is 32bpp depth=24 true color 05/01/2022 10:25:04 05/01/2022 10:25:04 Listening for VNC connections on TCP port 5900 05/01/2022 10:25:04 05/01/2022 10:25:04 Xinerama is present and active (e.g. multi-head). 05/01/2022 10:25:04 Xinerama: number of sub-screens: 1 05/01/2022 10:25:04 Xinerama: no blackouts needed (only one sub-screen) 05/01/2022 10:25:04 05/01/2022 10:25:04 fb read rate: 2436 MB/sec 05/01/2022 10:25:04 fast read: reset -wait ms to: 10 05/01/2022 10:25:04 fast read: reset -defer ms to: 10 05/01/2022 10:25:04 The X server says there are 10 mouse buttons. 05/01/2022 10:25:04 screen setup finished. 05/01/2022 10:25:04
The VNC desktop is: e2f1d26c914b:0 PORT=5900
Have you tried the x11vnc '-ncache' VNC client-side pixel caching feature yet?
The scheme stores pixel data offscreen on the VNC viewer side for faster retrieval. It should work with any VNC viewer. Try it by running:
x11vnc -ncache 10 ...
One can also add -ncache_cr for smooth 'copyrect' window motion. More info: http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching
[services.d] stopping services [services.d] stopping app... [services.d] stopping x11vnc... caught signal: 15 05/01/2022 10:27:10 deleted 40 tile_row polling images. [services.d] stopping openbox... The XKEYBOARD keymap compiler (xkbcomp) reports: > Internal error: Could not resolve keysym XF86FullScreen [services.d] stopping logmonitor... Errors from xkbcomp are not fatal to the X server [services.d] stopping statusmonitor... [services.d] stopping xvfb... [services.d] stopping nginx... [services.d] stopping certsmonitor... [services.d] stopping CrashPlanEngine... s6-svlisten1: fatal: timed out [services.d] stopping s6-fdholderd... [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] syncing disks. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting.
I'm seeing this problem too and have very similar messages in the logs. I'm running on a QNAP NAS. However, it does appear to be backing up despite these log messages according to the Crashplan website. It is just that the connection via VNC appears to be broken so I can't see the Crashplan GUI.
Once it boots, it appears that openbox and vnc keep trying to load but fail with the following message repeating periodically:
[openbox] starting... [x11vnc] starting... Obt-Message: Xinerama extension is not present on the server 06/01/2022 13:23:10 passing arg to libvncserver: -rfbport 06/01/2022 13:23:10 passing arg to libvncserver: 5900 06/01/2022 13:23:10 passing arg to libvncserver: -rfbportv6 06/01/2022 13:23:10 passing arg to libvncserver: 5900 06/01/2022 13:23:10 passing arg to libvncserver: -desktop 06/01/2022 13:23:10 passing arg to libvncserver: CrashPlan for Small Business 06/01/2022 13:23:10 x11vnc version: 0.9.14 lastmod: 2015-11-14 pid: 24468 06/01/2022 13:23:10 Using X display :0 06/01/2022 13:23:10 rootwin: 0x11f reswin: 0x2400001 dpy: 0x5abf9ae0 06/01/2022 13:23:10 06/01/2022 13:23:10 ------------------ USEFUL INFORMATION ------------------ 06/01/2022 13:23:10 X DAMAGE available on display, using it for polling hints. 06/01/2022 13:23:10 To disable this behavior use: '-noxdamage' 06/01/2022 13:23:10 06/01/2022 13:23:10 Most compositing window managers like 'compiz' or 'beryl' 06/01/2022 13:23:10 cause X DAMAGE to fail, and so you may not see any screen 06/01/2022 13:23:10 updates via VNC. Either disable 'compiz' (recommended) or 06/01/2022 13:23:10 supply the x11vnc '-noxdamage' command line option. 06/01/2022 13:23:10 X COMPOSITE available on display, using it for window polling. 06/01/2022 13:23:10 To disable this behavior use: '-noxcomposite' 06/01/2022 13:23:10 06/01/2022 13:23:10 Wireframing: -wireframe mode is in effect for window moves. 06/01/2022 13:23:10 If this yields undesired behavior (poor response, painting 06/01/2022 13:23:10 errors, etc) it may be disabled: 06/01/2022 13:23:10 - use '-nowf' to disable wireframing completely. 06/01/2022 13:23:10 - use '-nowcr' to disable the Copy Rectangle after the 06/01/2022 13:23:10 moved window is released in the new position. 06/01/2022 13:23:10 Also see the -help entry for tuning parameters. 06/01/2022 13:23:10 You can press 3 Alt_L's (Left "Alt" key) in a row to 06/01/2022 13:23:10 repaint the screen, also see the -fixscreen option for 06/01/2022 13:23:10 periodic repaints. 06/01/2022 13:23:10 GrabServer control via XTEST. 06/01/2022 13:23:10 06/01/2022 13:23:10 Scroll Detection: -scrollcopyrect mode is in effect to 06/01/2022 13:23:10 use RECORD extension to try to detect scrolling windows 06/01/2022 13:23:10 (induced by either user keystroke or mouse input). 06/01/2022 13:23:10 If this yields undesired behavior (poor response, painting 06/01/2022 13:23:10 errors, etc) it may be disabled via: '-noscr' 06/01/2022 13:23:10 Also see the -help entry for tuning parameters. 06/01/2022 13:23:10 You can press 3 Alt_L's (Left "Alt" key) in a row to 06/01/2022 13:23:10 repaint the screen, also see the -fixscreen option for 06/01/2022 13:23:10 periodic repaints. 06/01/2022 13:23:10 06/01/2022 13:23:10 XKEYBOARD: number of keysyms per keycode 7 is greater 06/01/2022 13:23:10 than 4 and 51 keysyms are mapped above 4. 06/01/2022 13:23:10 Automatically switching to -xkb mode. 06/01/2022 13:23:10 If this makes the key mapping worse you can 06/01/2022 13:23:10 disable it with the "-noxkb" option. 06/01/2022 13:23:10 Also, remember "-remap DEAD" for accenting characters. 06/01/2022 13:23:10 06/01/2022 13:23:10 X FBPM extension not supported. 06/01/2022 13:23:10 X display is capable of DPMS. 06/01/2022 13:23:10 -------------------------------------------------------- 06/01/2022 13:23:10 06/01/2022 13:23:10 Default visual ID: 0x21 06/01/2022 13:23:10 Read initial data from X display into framebuffer. 06/01/2022 13:23:10 initialize_screen: fb_depth/fb_bpp/fb_Bpl 24/32/4096 06/01/2022 13:23:10 Openbox-Message: A window manager is already running on screen 0 06/01/2022 13:23:10 X display :0 is 32bpp depth=24 true color 06/01/2022 13:23:10 06/01/2022 13:23:10 Listening for VNC connections on TCP port 5900 06/01/2022 13:23:10 Listening for VNC connections on TCP6 port 5900 06/01/2022 13:23:10 listen6: bind: Address in use 06/01/2022 13:23:10 Not listening on IPv6 interface.
X11 MIT Shared Memory Attach failed: Is your DISPLAY=:0 on a remote machine? Suggestion, use: x11vnc -display :0 ... for local display :0
caught X11 error: 06/01/2022 13:23:10 deleted 32 tile_row polling images. X Error of failed request: BadAccess (attempt to access private resource denied) Major opcode of failed request: 130 (MIT-SHM) Minor opcode of failed request: 1 (X_ShmAttach) Serial number of failed request: 57 Current serial number in output stream: 91 [xvfb] starting... _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: server already running (EE) Fatal server error: (EE) Cannot establish any listening sockets - Make sure an X server isn't already running(EE)
@bhom920, the log shows that the container stopped. It is you that stopped it or it terminated itself ?
@khbecker, this is a different problem. You seem to have something else on your QNAP that is using the same ports has the container.
@bhom920, the log shows that the container stopped. It is you that stopped it or it terminated itself ?
it seems to be terminating itself. I've tried so far removing the container app, and then deleting the container folder. Then reinstall container and and redownload the latest docker with the same result. I did notice that on this qnap i need to configure the network has host instead of NAT in order to see anything at all. I have a total of 4 qnaps running the docker and this one is the only one experiencing this issue. I am not sure what version the other 3 are running as i typically leave them (so likely older) be unless i have issues with connection. Something i've been doing probably for the past 4 years.
Can you share the container's settings? If you used the CLI, it's the docker run command you used to create the container.
Can you share the container's settings? If you used the CLI, it's the
docker runcommand you used to create the container.
docker run -d
--name=crashplan-pro
--restart=always
-e USER_ID=0
-p 5800:5800
-e GROUP_ID=0
-e TZ=America/New_York
-e CRASHPLAN_SRV_MAX_MEM=8192M
-v /share/CACHEDEV1_DATA/Container/appdata/crashplan:/config:rw
-v /share/CACHEDEV1_DATA:/share:ro
jlesage/crashplan-pro
Can you share the container's settings? If you used the CLI, it's the
docker runcommand you used to create the container.
did you see anything wrong with my command?
The command looks good.
Can you check the following log files under /share/CACHEDEV1_DATA/Container/appdata/crashplan/log:
- ui_error.log
- ui_output.log
The command looks good. Can you check the following log files under
/share/CACHEDEV1_DATA/Container/appdata/crashplan/log:
- ui_error.log
- ui_output.log
I just took a look at this folder and i do not see a ui_error.log or a ui_output.log. The closest matching files that i see are engine_error.log, engine_output.log, and a ui.log
@jlesage I have exactly the same problem. QNAP NAS as well.
Backup seems to be working something is wrong with the VNC connection.
You can find logs below:
2022-03-11T15:47:15.417Z - info: ************************************************************
2022-03-11T15:47:15.419Z - info: Name: Code42
2022-03-11T15:47:15.419Z - info: Version: 8.8.3
2022-03-11T15:47:15.419Z - info: Options: sandbox=false, _=[], showMenubar=false, showDesktop=true, isDevEnv=false, isTestEnv=false
2022-03-11T15:47:15.419Z - info: Platform: linux (x64)
2022-03-11T15:47:15.420Z - info: Service Info: /var/lib/crashplan/.ui_info
2022-03-11T15:47:15.420Z - info: Log File: /config/.code42/log/ui.log
2022-03-11T15:47:15.421Z - info: Cache: /config/xdg/config/CrashPlan
2022-03-11T15:47:15.421Z - info: ************************************************************
2022-03-11T15:47:16.236Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 1
2022-03-11T15:47:17.267Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 2
2022-03-11T15:47:18.135Z - info: Updating system locale to en_US
2022-03-11T15:47:18.277Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 3
2022-03-11T15:47:19.294Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 4
2022-03-11T15:47:20.307Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 5
2022-03-11T15:47:21.321Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 6
2022-03-11T15:47:22.334Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 7
2022-03-11T15:47:23.372Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 8
2022-03-11T15:47:24.385Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 9
2022-03-11T15:47:25.395Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 10
2022-03-11T15:47:26.409Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 11
2022-03-11T15:47:27.417Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 12
2022-03-11T15:47:28.427Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 13
2022-03-11T15:47:29.459Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 14
2022-03-11T15:47:30.465Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 15
2022-03-11T15:47:31.475Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 16
2022-03-11T15:47:32.508Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 17
2022-03-11T15:47:33.523Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 18
2022-03-11T15:47:34.539Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 19
2022-03-11T15:47:35.561Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 20
2022-03-11T15:47:36.572Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 21
2022-03-11T15:47:37.584Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 22
2022-03-11T15:47:38.594Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 23
2022-03-11T15:47:39.615Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 24
2022-03-11T15:47:40.620Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 25
2022-03-11T15:47:41.632Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 26
2022-03-11T15:47:42.651Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 27
2022-03-11T15:47:43.666Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 28
2022-03-11T15:47:44.691Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 29
2022-03-11T15:47:45.697Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 30
2022-03-11T15:47:46.705Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 31
2022-03-11T15:47:47.713Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 32
2022-03-11T15:47:48.726Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 33
2022-03-11T15:47:49.738Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 34
2022-03-11T15:47:50.762Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 35
2022-03-11T15:47:51.782Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 36
2022-03-11T15:47:52.819Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 37
2022-03-11T15:47:53.836Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 38
2022-03-11T15:47:54.851Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 39
2022-03-11T15:47:55.865Z - info: Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244 attempt 40
2022-03-11T15:48:00.394Z - info: Setting locale after receiving loginSetup to AUTOMATIC_LOCALE
2022-03-11T15:48:00.410Z - info: Connected to service, show main window
2022-03-11T15:48:06.375Z - info: Closing splash screen
2022-03-11T15:48:06.223Z - info JS Console: Init browser console logging
2022-03-11T15:48:06.226Z - info main: Starting application initialization
2022-03-11T15:48:06.273Z - info ServiceInterface: init() with https://127.0.0.1:4244
2022-03-11T15:48:06.261Z - info main: Initialized ipc listeners to main process
2022-03-11T15:48:06.271Z - info main: Initialized push event interface to service
2022-03-11T15:48:06.274Z - info main: Initialized https interface to service
2022-03-11T15:48:06.386Z - info: Showing main window
2022-03-11T15:48:06.467Z - info main: Performed localization loading, attempting to connect to the service
2022-03-11T15:48:06.762Z - info main: Showing loading visuals
2022-03-11T15:48:07.922Z - info main: Connected to the service
2022-03-11T15:48:07.923Z - info main: Attempting to fetch customizations for un-authenticated state
2022-03-11T15:48:07.944Z - info main: System locale en_US did not match the locale returned from the service AUTOMATIC_LOCALE, requesting the correct locale
2022-03-11T15:48:08.256Z - info main: Attempting to auto-login
2022-03-11T15:48:08.270Z - info main: A token is available, test if the token is valid
2022-03-11T15:48:08.362Z - info main: Auto login - token is valid
2022-03-11T15:48:08.362Z - info main: Authenticate with push event interface and set logged in state
2022-03-11T15:48:08.363Z - info main: Requesting initial application data
2022-03-11T15:48:08.363Z - info AppInit: Set application state to be logged in
2022-03-11T15:48:08.385Z - info AppInit: Register authenticated event handlers
2022-03-11T15:48:08.385Z - info AppInit: Requesting all application initialization data
2022-03-11T15:48:10.250Z - info main: Starting main routing
2022-03-11T15:48:10.267Z - warn JS Console: Attempting to access localized key before initialization.
2022-03-11T15:48:10.269Z - warn JS Console: Attempting to access localized key before initialization.
2022-03-11T15:48:10.271Z - warn JS Console: Attempting to access localized key before initialization.
2022-03-11T15:48:11.716Z - info routes.js: onChange: previousPath=/devices/680777600972252260 with params={"deviceId":"680777600972252260"}
2022-03-11T15:48:11.717Z - info routes.js: onChange: nextPath=/devices/680777600972252260 with params={"deviceId":"680777600972252260"}
[/share/CACHEDEV1_DATA/Containers/crashplan/config/log] # more engine_error.log
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.3.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
[/share/CACHEDEV1_DATA/Containers/crashplan/config/log] # more 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=Code42Service
-DappBaseName=Code42
-Djna.nosys=true
-Djava.awt.headless=true
-DCode42=Code42
-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
Java virtual machine created.
Starting service.
[03.11.22 16:47:06.297 INFO main com.code42.utils.ClassFinder] Loaded classpaths in 3405 ms
[2022-03-11 16:47:37.886210] [00:00:13.819767] [INFO ] (UnknownModule) Initializing uaw module, rootInstall=true
[2022-03-11 16:47:37.900757] [00:00:13.834314] [INFO ] (UnknownModule) Initial Configuration:device_uaw_inactiveDurationInSec=900s.
[2022-03-11 16:47:37.959702] [00:00:13.893259] [INFO ] (UnknownModule) Configuration:device_uaw_inactiveDurationInSec is now 900s
[2022-03-11 16:47:37.964747] [00:00:13.898302] [INFO ] (uaw) Starting the uaw module.
[2022-03-11 16:47:37.967459] [00:00:13.901015] [WARN ] (uaw) Unable to watch user activity. filesystem error: directory iterator cannot open directory: No such file or directory [/dev/input/by-path]
[2022-03-11 16:47:37.980465] [00:00:13.914022] [ERROR] (uaw) Stopping the uaw module early, failed to start the watcher.
I Have this same issue on an Unraid NAS
This is the WebUI:
Please help, error 1006 (Server Disconnected)
It's probably not the same root cause as the original problem. Most of the time, the error 1006 comes from the browser itself. Try to clear the browser's cache. You can also try to use a private/incognito window.