WillWorkForAmmo

Members
  • Posts

    5
  • Joined

WillWorkForAmmo's Achievements

Noob

Noob (1/14)

0

Reputation

  1. I recently tried renewing my certs since they were expired. When running the 'renew' option from the GUI, the log shows the following: Failed to renew certificate npm-1 with error: [Errno 117] Structure needs cleaning: '/etc/letsencrypt/csr/2485_csr-certbot.pem' All renewals failed. The following certificates could not be renewed: /etc/letsencrypt/live/npm-1/fullchain.pem (failure) When I browse to the csr path in Krusader, the folder is empty. I was able to find online that this message usually means there is corruption. Is there a way to resolve this without just re-installing the container and setting up again?
  2. Correct. When I insert the disc (BR or DVD) the GUI shows the spin up like it's reading, then shows "No disc inserted". The drive light stops as well. I'm not 100% sure if it started after an update, but I feel as though it may have. I also tried removing the docker, but I'm not sure if that removes 100% of everything including maybe settings or something in Unraid (I'm a novice).
  3. This docker has been working perfectly for me up until the last week or so. I was able to successfully rip Ready Player One on BR 3 days ago. After that, I insert any BR or DVD, it spins up, and then says "No Disc Inserted". I've uninstalled, re-installed, added a 2nd drive (with sg/sr info), restarted system, and still nothing. Anyone have any suggestions? Here is my log: [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 00-app-niceness.sh: executing... [cont-init.d] 00-app-niceness.sh: exited 0. [cont-init.d] 00-app-script.sh: executing... [cont-init.d] 00-app-script.sh: exited 0. [cont-init.d] 00-app-user-map.sh: executing... [cont-init.d] 00-app-user-map.sh: exited 0. [cont-init.d] 00-clean-logmonitor-states.sh: executing... [cont-init.d] 00-clean-logmonitor-states.sh: exited 0. [cont-init.d] 00-clean-tmp-dir.sh: executing... [cont-init.d] 00-clean-tmp-dir.sh: exited 0. [cont-init.d] 00-set-app-deps.sh: executing... [cont-init.d] 00-set-app-deps.sh: exited 0. [cont-init.d] 00-set-home.sh: executing... [cont-init.d] 00-set-home.sh: exited 0. [cont-init.d] 00-take-config-ownership.sh: executing... [cont-init.d] 00-take-config-ownership.sh: exited 0. [cont-init.d] 00-xdg-runtime-dir.sh: executing... [cont-init.d] 00-xdg-runtime-dir.sh: exited 0. [cont-init.d] 10-certs.sh: executing... [cont-init.d] 10-certs.sh: exited 0. [cont-init.d] 10-cjk-font.sh: executing... [cont-init.d] 10-cjk-font.sh: exited 0. [cont-init.d] 10-nginx.sh: executing... [cont-init.d] 10-nginx.sh: exited 0. [cont-init.d] 10-vnc-password.sh: executing... [cont-init.d] 10-vnc-password.sh: exited 0. [cont-init.d] 10-web-index.sh: executing... [cont-init.d] 10-web-index.sh: exited 0. [cont-init.d] 90-makemkv.sh: executing... [cont-init.d] 90-makemkv.sh: generating machine-id... app_ccextractor = "/usr/bin/ccextractor" Checking for new beta key... Registration key already up-to-date. [cont-init.d] 90-makemkv.sh: exited 0. [cont-init.d] 95-check-optical-drive.sh: executing... [cont-init.d] 95-check-optical-drive.sh: looking for usable optical drives... [cont-init.d] 95-check-optical-drive.sh: found optical drive [/dev/sr0, /dev/sg4], group 19. [cont-init.d] 95-check-optical-drive.sh: found optical drive [/dev/sr1, /dev/sg7], group 19. [cont-init.d] 95-check-optical-drive.sh: exited 0. [cont-init.d] 96-install-autodiscripper-srv.sh: executing... [cont-init.d] 96-install-autodiscripper-srv.sh: installing automatic disc ripper service... [cont-init.d] 96-install-autodiscripper-srv.sh: exited 0. [cont-init.d] done. [services.d] starting services [services.d] starting s6-fdholderd... [services.d] starting certsmonitor... [services.d] starting nginx... [services.d] starting xvfb... [nginx] starting... [certsmonitor] disabling service: secure connection not enabled. [xvfb] starting... [services.d] starting autodiscripper... [services.d] starting statusmonitor... [statusmonitor] no file to monitor: disabling service... [services.d] starting logmonitor... [services.d] starting openbox... [logmonitor] no file to monitor: disabling service... [autodiscripper] starting... [openbox] starting... [autodiscripper] Ready. [services.d] starting x11vnc... [services.d] starting app... [x11vnc] starting... [app] starting MakeMKV... [services.d] done. 28/01/2019 15:52:56 passing arg to libvncserver: -rfbport 28/01/2019 15:52:56 passing arg to libvncserver: 5900 28/01/2019 15:52:56 passing arg to libvncserver: -rfbportv6 28/01/2019 15:52:56 passing arg to libvncserver: -1 28/01/2019 15:52:56 passing arg to libvncserver: -httpportv6 28/01/2019 15:52:56 passing arg to libvncserver: -1 28/01/2019 15:52:56 passing arg to libvncserver: -desktop 28/01/2019 15:52:56 passing arg to libvncserver: MakeMKV 28/01/2019 15:52:56 x11vnc version: 0.9.14 lastmod: 2015-11-14 pid: 1275 28/01/2019 15:52:56 Using X display :0 28/01/2019 15:52:56 rootwin: 0x43 reswin: 0x400001 dpy: 0xa9418a00 28/01/2019 15:52:56 28/01/2019 15:52:56 ------------------ USEFUL INFORMATION ------------------ 28/01/2019 15:52:56 X DAMAGE available on display, using it for polling hints. 28/01/2019 15:52:56 To disable this behavior use: '-noxdamage' 28/01/2019 15:52:56 28/01/2019 15:52:56 Most compositing window managers like 'compiz' or 'beryl' 28/01/2019 15:52:56 cause X DAMAGE to fail, and so you may not see any screen 28/01/2019 15:52:56 updates via VNC. Either disable 'compiz' (recommended) or 28/01/2019 15:52:56 supply the x11vnc '-noxdamage' command line option. 28/01/2019 15:52:56 X COMPOSITE available on display, using it for window polling. 28/01/2019 15:52:56 To disable this behavior use: '-noxcomposite' 28/01/2019 15:52:56 28/01/2019 15:52:56 Wireframing: -wireframe mode is in effect for window moves. 28/01/2019 15:52:56 If this yields undesired behavior (poor response, painting 28/01/2019 15:52:56 errors, etc) it may be disabled: 28/01/2019 15:52:56 - use '-nowf' to disable wireframing completely. 28/01/2019 15:52:56 - use '-nowcr' to disable the Copy Rectangle after the 28/01/2019 15:52:56 moved window is released in the new position. 28/01/2019 15:52:56 Also see the -help entry for tuning parameters. 28/01/2019 15:52:56 You can press 3 Alt_L's (Left "Alt" key) in a row to 28/01/2019 15:52:56 repaint the screen, also see the -fixscreen option for 28/01/2019 15:52:56 periodic repaints. 28/01/2019 15:52:56 GrabServer control via XTEST. 28/01/2019 15:52:56 28/01/2019 15:52:56 Scroll Detection: -scrollcopyrect mode is in effect to 28/01/2019 15:52:56 use RECORD extension to try to detect scrolling windows 28/01/2019 15:52:56 (induced by either user keystroke or mouse input). 28/01/2019 15:52:56 If this yields undesired behavior (poor response, painting 28/01/2019 15:52:56 errors, etc) it may be disabled via: '-noscr' 28/01/2019 15:52:56 Also see the -help entry for tuning parameters. 28/01/2019 15:52:56 You can press 3 Alt_L's (Left "Alt" key) in a row to 28/01/2019 15:52:56 repaint the screen, also see the -fixscreen option for 28/01/2019 15:52:56 periodic repaints. 28/01/2019 15:52:56 28/01/2019 15:52:56 XKEYBOARD: number of keysyms per keycode 7 is greater 28/01/2019 15:52:56 than 4 and 51 keysyms are mapped above 4. 28/01/2019 15:52:56 Automatically switching to -xkb mode. 28/01/2019 15:52:56 If this makes the key mapping worse you can 28/01/2019 15:52:56 disable it with the "-noxkb" option. 28/01/2019 15:52:56 Also, remember "-remap DEAD" for accenting characters. 28/01/2019 15:52:56 28/01/2019 15:52:56 X FBPM extension not supported. 28/01/2019 15:52:56 X display is not capable of DPMS. 28/01/2019 15:52:56 -------------------------------------------------------- 28/01/2019 15:52:56 28/01/2019 15:52:56 Default visual ID: 0x21 28/01/2019 15:52:56 Read initial data from X display into framebuffer. 28/01/2019 15:52:56 initialize_screen: fb_depth/fb_bpp/fb_Bpl 24/32/5120 28/01/2019 15:52:56 28/01/2019 15:52:56 X display :0 is 32bpp depth=24 true color 28/01/2019 15:52:56 28/01/2019 15:52:56 Listening for VNC connections on TCP port 5900 28/01/2019 15:52:56 28/01/2019 15:52:56 Xinerama is present and active (e.g. multi-head). 28/01/2019 15:52:56 Xinerama: number of sub-screens: 1 28/01/2019 15:52:56 Xinerama: no blackouts needed (only one sub-screen) 28/01/2019 15:52:56 28/01/2019 15:52:56 fb read rate: 1156 MB/sec 28/01/2019 15:52:56 fast read: reset -wait ms to: 10 28/01/2019 15:52:56 fast read: reset -defer ms to: 10 28/01/2019 15:52:56 The X server says there are 10 mouse buttons. 28/01/2019 15:52:56 screen setup finished. 28/01/2019 15:52:56 The VNC desktop is: 91c773d25fac:0 0 ****************************************************************************** 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 28/01/2019 15:54:46 Got connection from client 127.0.0.1 28/01/2019 15:54:46 other clients: 28/01/2019 15:54:46 Got 'ws' WebSockets handshake 28/01/2019 15:54:46 Got protocol: binary 28/01/2019 15:54:46 - webSocketsHandshake: using binary/raw encoding 28/01/2019 15:54:46 - WebSockets client version hybi-13 28/01/2019 15:54:46 Disabled X server key autorepeat. 28/01/2019 15:54:46 to force back on run: 'xset r on' (3 times) 28/01/2019 15:54:46 incr accepted_client=1 for 127.0.0.1:46320 sock=10 28/01/2019 15:54:46 Client Protocol Version 3.8 28/01/2019 15:54:46 Protocol version sent 3.8, using 3.8 28/01/2019 15:54:46 rfbProcessClientSecurityType: executing handler for type 1 28/01/2019 15:54:46 rfbProcessClientSecurityType: returning securityResult for client rfb version >= 3.8 28/01/2019 15:54:46 Pixel format for client 127.0.0.1: 28/01/2019 15:54:46 32 bpp, depth 24, little endian 28/01/2019 15:54:46 true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0 28/01/2019 15:54:46 no translation needed 28/01/2019 15:54:46 Enabling NewFBSize protocol extension for client 127.0.0.1 28/01/2019 15:54:46 Enabling full-color cursor updates for client 127.0.0.1 28/01/2019 15:54:46 Using image quality level 6 for client 127.0.0.1 28/01/2019 15:54:46 Using JPEG subsampling 0, Q79 for client 127.0.0.1 28/01/2019 15:54:46 Using compression level 9 for client 127.0.0.1 28/01/2019 15:54:46 Enabling LastRect protocol extension for client 127.0.0.1 28/01/2019 15:54:46 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFECC) 28/01/2019 15:54:46 Using tight encoding for client 127.0.0.1 28/01/2019 15:54:46 Got connection from client 127.0.0.1 28/01/2019 15:54:46 other clients: 28/01/2019 15:54:46 Got 'ws' WebSockets handshake 28/01/2019 15:54:46 Got protocol: binary 28/01/2019 15:54:46 - webSocketsHandshake: using binary/raw encoding 28/01/2019 15:54:46 - WebSockets client version hybi-13 28/01/2019 15:54:46 Disabled X server key autorepeat. 28/01/2019 15:54:46 to force back on run: 'xset r on' (3 times) 28/01/2019 15:54:46 incr accepted_client=1 for 127.0.0.1:46320 sock=10 28/01/2019 15:54:46 Client Protocol Version 3.8 28/01/2019 15:54:46 Protocol version sent 3.8, using 3.8 28/01/2019 15:54:46 rfbProcessClientSecurityType: executing handler for type 1 28/01/2019 15:54:46 rfbProcessClientSecurityType: returning securityResult for client rfb version >= 3.8 28/01/2019 15:54:46 Pixel format for client 127.0.0.1: 28/01/2019 15:54:46 32 bpp, depth 24, little endian 28/01/2019 15:54:46 true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0 28/01/2019 15:54:46 no translation needed 28/01/2019 15:54:46 Enabling NewFBSize protocol extension for client 127.0.0.1 28/01/2019 15:54:46 Enabling full-color cursor updates for client 127.0.0.1 28/01/2019 15:54:46 Using image quality level 6 for client 127.0.0.1 28/01/2019 15:54:46 Using JPEG subsampling 0, Q79 for client 127.0.0.1 28/01/2019 15:54:46 Using compression level 9 for client 127.0.0.1 28/01/2019 15:54:46 Enabling LastRect protocol extension for client 127.0.0.1 28/01/2019 15:54:46 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFECC) 28/01/2019 15:54:46 Using tight encoding for client 127.0.0.1 28/01/2019 15:54:46 client_set_net: 127.0.0.1 0.0000 28/01/2019 15:54:46 created xdamage object: 0x40002c 28/01/2019 15:54:47 copy_tiles: allocating first_line at size 41 28/01/2019 15:54:49 client 1 network rate 2789.4 KB/sec (43680.7 eff KB/sec) 28/01/2019 15:54:49 client 1 latency: 1.0 ms 28/01/2019 15:54:49 dt1: 0.0021, dt2: 0.0023 dt3: 0.0010 bytes: 10839 28/01/2019 15:54:49 link_rate: LR_LAN - 1 ms, 2789 KB/s 28/01/2019 15:54:56 created selwin: 0x40002d 28/01/2019 15:54:56 called initialize_xfixes() 28/01/2019 15:59:47 idle keyboard: turning X autorepeat back on. 28/01/2019 15:59:47 idle keyboard: turning X autorepeat back on.
  4. Can you tell me what you think may have caused this? I've just recently begun having the same type of kernel crashes. They tend to happen around 10 in the evening. The only thing, that I can think of that has a custom IP address is my docker running Pi-Hole. This was the most recent thing I setup and I believe when the issues started a couple weeks after it was up and running. Thanks for any insight.