krh1009

Members
  • Posts

    43
  • Joined

  • Last visited

Everything posted by krh1009

  1. I got a warning that my docker image was at 79%. Looking at my container size I saw the Ombi log is at 18G. I deleted the container and reinstalled. That fixed the problem. Is there a way to turn off logging or limit the log file size?
  2. I set up letsencrypt and then migrated to swag using the space invader one video. Access to my dockers is working fine. Two questions: 1. I'm running Zoneminder (for home security cameras) on a different (ubuntu) machine. Can I setup up a reverse proxy using swag in an unraid docker to access zoneminder on my ubuntu machine to from outside my home network? 2. Is thee a zoneminder.subdomain.conf file ? I didn't find one in the conf folder. Thanks
  3. I'm getting an SQLite Error 5: 'database is locked' error in my log file. Did some searching, I see the solution is to move to mysql (https://github.com/tidusjar/Ombi/issues/2750) I found migration to mysql instructions here: https://github.com/tidusjar/Ombi/wiki/Using-a-different-database I need help on how to do the migration when running Ombi in a docker. If I do get it to work by adding a mysql server in another docker, will an upgrade of the ombi docker wipe out my migration? Any help is appreciated.
  4. OK...so I took the cowards way out. I didn't feel like removing the cooler cleaning the TIM and reseating the CPU. So I ordered 2 sticks of 16G ram and place them in the lower two (working) slots. memtest showed 100% pass. SO I think I'm good for now. One long rainy weekend I'll attempt to reseat the CPU., which I think will solve the problem completely.
  5. Thanks for the video and the brand recommendation. I'm going to 1) lower the memory speed, if no luck 2) reseat CPU, if no luck 3) buy more ram
  6. I can give it a try....I need to find that setting the bios. I'd rather do that than re-seat CPU.
  7. So I tested each pair separately ( two tests of 16GB). Both tests show no errors, so I know the modules are not the problem. When I insert all four at one time I get a ton of errors. I think the CPU re-seating might be what is needed, Do i need to unmount the CPU completely and remount or can I loosen the bracket and re-tighten the screws in the proper sequence? Thanks again for the help
  8. Thanks. Going to re-seat and test each pair separately and see if I get errors
  9. Thank you for the suggestion! I didn't think brand new ram would could have a problem....but once again I was wrong. I have 4 X 8G modules installed. Is there a way to figure out which stick is bad, or should I just start over will all new ram? Using: G.SKILL Ripjaws V Series DDR4 PC4-25600 3200MHz Model F4-3200C16D-16GVKB Any recommendations on a replacement?
  10. I've been battling random system lock up for the last month and need help. I upgrade ram from 16G to 32G and started having problems with crashing after 12 to 24 hours of running. Things I've done so far: Updated bios to latest version reset bios to default config replaced my marvel HBA with an LSI Switch PCI slots of HBA Updated unraid to 6.8.2 None of these helped. I'm switched logging to flash drive. A copy of the syslog right after a crash and diag files are attached. ANY HELP WOULD BE APPRECIATED.... syslog crash mediaserv-diagnostics-20200204-0523.zip
  11. I was checking to see if this problem was fix. My sever keeps crashing after I upgraded from 16G to 32G of ram. Running unraid 6.8.2 now. See my log file below. Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: Node 0: DRAM ECC disabled. Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 2 12:22:59 Mediaserv kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 2 12:22:59 Mediaserv kernel: (Note that use of the override may cause unknown side effects.) Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: Node 1: DRAM ECC disabled. Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 2 12:22:59 Mediaserv kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 2 12:22:59 Mediaserv kernel: (Note that use of the override may cause unknown side effects.) Feb 2 12:22:59 Mediaserv kernel: Bluetooth: hci0: read Intel version: 370810225019140f34 Feb 2 12:22:59 Mediaserv kernel: Bluetooth: hci0: Intel device is already patched. patch num: 34 Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: Node 0: DRAM ECC disabled. Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 2 12:22:59 Mediaserv kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 2 12:22:59 Mediaserv kernel: (Note that use of the override may cause unknown side effects.) Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: Node 1: DRAM ECC disabled. Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 2 12:22:59 Mediaserv kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 2 12:22:59 Mediaserv kernel: (Note that use of the override may cause unknown side effects.) Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: Node 0: DRAM ECC disabled. Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 2 12:22:59 Mediaserv kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 2 12:22:59 Mediaserv kernel: (Note that use of the override may cause unknown side effects.) Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: Node 1: DRAM ECC disabled. Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 2 12:22:59 Mediaserv kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 2 12:22:59 Mediaserv kernel: (Note that use of the override may cause unknown side effects.) Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: Node 0: DRAM ECC disabled. Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 2 12:22:59 Mediaserv kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 2 12:22:59 Mediaserv kernel: (Note that use of the override may cause unknown side effects.) Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: Node 1: DRAM ECC disabled. Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 2 12:22:59 Mediaserv kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 2 12:22:59 Mediaserv kernel: (Note that use of the override may cause unknown side effects.) Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: Node 0: DRAM ECC disabled. Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 2 12:22:59 Mediaserv kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 2 12:22:59 Mediaserv kernel: (Note that use of the override may cause unknown side effects.) Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: Node 1: DRAM ECC disabled. Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 2 12:22:59 Mediaserv kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 2 12:22:59 Mediaserv kernel: (Note that use of the override may cause unknown side effects.) Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: Node 0: DRAM ECC disabled. Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 2 12:22:59 Mediaserv kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 2 12:22:59 Mediaserv kernel: (Note that use of the override may cause unknown side effects.) Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: Node 1: DRAM ECC disabled. Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 2 12:22:59 Mediaserv kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 2 12:22:59 Mediaserv kernel: (Note that use of the override may cause unknown side effects.) Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: Node 0: DRAM ECC disabled. Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 2 12:22:59 Mediaserv kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 2 12:22:59 Mediaserv kernel: (Note that use of the override may cause unknown side effects.) Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: Node 1: DRAM ECC disabled. Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 2 12:22:59 Mediaserv kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 2 12:22:59 Mediaserv kernel: (Note that use of the override may cause unknown side effects.) Feb 2 12:22:59 Mediaserv kernel: ata9: SATA link down (SStatus 0 SControl 300) Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: Node 0: DRAM ECC disabled. Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 2 12:22:59 Mediaserv kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 2 12:22:59 Mediaserv kernel: (Note that use of the override may cause unknown side effects.) Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: Node 1: DRAM ECC disabled. Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 2 12:22:59 Mediaserv kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 2 12:22:59 Mediaserv kernel: (Note that use of the override may cause unknown side effects.) Feb 2 12:22:59 Mediaserv kernel: ata10: SATA link down (SStatus 0 SControl 300) Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: Node 0: DRAM ECC disabled. Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 2 12:22:59 Mediaserv kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 2 12:22:59 Mediaserv kernel: (Note that use of the override may cause unknown side effects.) Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: Node 1: DRAM ECC disabled. Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 2 12:22:59 Mediaserv kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 2 12:22:59 Mediaserv kernel: (Note that use of the override may cause unknown side effects.) Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: Node 0: DRAM ECC disabled. Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 2 12:22:59 Mediaserv kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 2 12:22:59 Mediaserv kernel: (Note that use of the override may cause unknown side effects.) Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: Node 1: DRAM ECC disabled. Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 2 12:22:59 Mediaserv kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 2 12:22:59 Mediaserv kernel: (Note that use of the override may cause unknown side effects.) Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: Node 0: DRAM ECC disabled. Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 2 12:22:59 Mediaserv kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 2 12:22:59 Mediaserv kernel: (Note that use of the override may cause unknown side effects.) Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: Node 1: DRAM ECC disabled. Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 2 12:22:59 Mediaserv kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 2 12:22:59 Mediaserv kernel: (Note that use of the override may cause unknown side effects.) Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: Node 0: DRAM ECC disabled. Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 2 12:22:59 Mediaserv kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 2 12:22:59 Mediaserv kernel: (Note that use of the override may cause unknown side effects.) Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: Node 1: DRAM ECC disabled. Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 2 12:22:59 Mediaserv kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 2 12:22:59 Mediaserv kernel: (Note that use of the override may cause unknown side effects.) Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: Node 0: DRAM ECC disabled. Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 2 12:22:59 Mediaserv kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 2 12:22:59 Mediaserv kernel: (Note that use of the override may cause unknown side effects.) Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: Node 1: DRAM ECC disabled. Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 2 12:22:59 Mediaserv kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 2 12:22:59 Mediaserv kernel: (Note that use of the override may cause unknown side effects.) Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: Node 0: DRAM ECC disabled. Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 2 12:22:59 Mediaserv kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 2 12:22:59 Mediaserv kernel: (Note that use of the override may cause unknown side effects.) Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: Node 1: DRAM ECC disabled. Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 2 12:22:59 Mediaserv kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 2 12:22:59 Mediaserv kernel: (Note that use of the override may cause unknown side effects.) Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: Node 0: DRAM ECC disabled. Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 2 12:22:59 Mediaserv kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 2 12:22:59 Mediaserv kernel: (Note that use of the override may cause unknown side effects.) Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: Node 1: DRAM ECC disabled. Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 2 12:22:59 Mediaserv kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 2 12:22:59 Mediaserv kernel: (Note that use of the override may cause unknown side effects.) Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: Node 0: DRAM ECC disabled. Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 2 12:22:59 Mediaserv kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 2 12:22:59 Mediaserv kernel: (Note that use of the override may cause unknown side effects.) Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: Node 1: DRAM ECC disabled. Feb 2 12:22:59 Mediaserv kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 2 12:22:59 Mediaserv kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 2 12:22:59 Mediaserv kernel: (Note that use of the override may cause unknown side effects.)
  12. Been running for 12 hours in safe mode and the web GUI is fully functional, but these messages are repeating in the log: Jan 22 20:48:35 Mediaserv nginx: 2020/01/22 20:48:35 [error] 3086#3086: *113769 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.3, server: , request: "POST /plugins/fix.common.problems/include/fixExec.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.11", referrer: "http://192.168.1.11/Settings/FixProblems" Jan 22 20:48:36 Mediaserv nginx: 2020/01/22 20:48:36 [error] 3086#3086: *113769 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.3, server: , request: "POST /plugins/fix.common.problems/include/fixExec.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.11", referrer: "http://192.168.1.11/Settings/FixProblems" Jan 22 20:48:37 Mediaserv nginx: 2020/01/22 20:48:37 [error] 3086#3086: *113769 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.3, server: , request: "POST /plugins/fix.common.problems/include/fixExec.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.11", referrer: "http://192.168.1.11/Settings/FixProblems" The plug-in page shows there are no active plug-in, so not sure why the Fix Common Problems would still cause an error.
  13. I upgraded from 6.6 to 6.8.1 and after 24hours I can not access my dashboard or docker tabs. Some searching shows this was a problem in 6.5: Here are the log message I see that appear to be the same as the 6.5 problem: Jan 21 22:29:30 Mediaserv nginx: 2020/01/21 22:29:30 [crit] 13455#13455: *250054 connect() to unix:/var/run/php5-fpm.sock failed (2: No such file or directory) while connecting to upstream, client: 192.168.1.3, server: , request: "POST /plugins/dynamix.system.temp/include/SystemTemp.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.11", referrer: "http://192.168.1.11/Docker" Jan 21 22:29:30 Mediaserv nginx: 2020/01/21 22:29:30 [crit] 13455#13455: *250596 connect() to unix:/var/run/php5-fpm.sock failed (2: No such file or directory) while connecting to upstream, client: 192.168.1.3, server: , request: "POST /plugins/fix.common.problems/include/fixExec.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.11", referrer: "http://192.168.1.11/Settings/FixProblems" Jan 21 22:31:59 Mediaserv nginx: 2020/01/21 22:31:59 [error] 13455#13455: *250795 upstream timed out (110: Connection I attached my diag file mediaserv-diagnostics-20200121-2248.zip
  14. I've just started getting network issues and crashing. I stopped the crashing by setting shareAvahiEnabled="no" But friends are telling me plex is buffering a lot. Also get this in the log: Jan 10 20:48:12 Mediaserv kernel: docker0: port 1(vethc797b83) entered forwarding state Jan 10 20:48:12 Mediaserv kernel: docker0: port 1(vethc797b83) entered disabled state Jan 10 20:48:12 Mediaserv kernel: eth0: renamed from veth9ac5620 Jan 10 20:48:12 Mediaserv kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethc797b83: link becomes ready Jan 10 20:48:12 Mediaserv kernel: docker0: port 1(vethc797b83) entered blocking state Jan 10 20:48:12 Mediaserv kernel: docker0: port 1(vethc797b83) entered forwarding state Jan 10 20:50:11 Mediaserv kernel: veth8eada9e: renamed from eth0 Jan 10 20:50:11 Mediaserv kernel: docker0: port 6(veth06c928f) entered disabled state Jan 10 20:50:11 Mediaserv kernel: docker0: port 6(veth06c928f) entered disabled state Jan 10 20:50:11 Mediaserv kernel: device veth06c928f left promiscuous mode Jan 10 20:50:11 Mediaserv kernel: docker0: port 6(veth06c928f) entered disabled state Jan 10 20:50:14 Mediaserv kernel: docker0: port 6(veth277617b) entered blocking state Jan 10 20:50:14 Mediaserv kernel: docker0: port 6(veth277617b) entered disabled state Jan 10 20:50:14 Mediaserv kernel: device veth277617b entered promiscuous mode Jan 10 20:50:14 Mediaserv kernel: IPv6: ADDRCONF(NETDEV_UP): veth277617b: link is not ready Jan 10 20:50:14 Mediaserv kernel: docker0: port 6(veth277617b) entered blocking state Jan 10 20:50:14 Mediaserv kernel: docker0: port 6(veth277617b) entered forwarding state Jan 10 20:50:14 Mediaserv kernel: docker0: port 6(veth277617b) entered disabled state Jan 10 20:50:15 Mediaserv kernel: eth0: renamed from veth843a945 Jan 10 20:50:15 Mediaserv kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth277617b: link becomes ready Jan 10 20:50:15 Mediaserv kernel: docker0: port 6(veth277617b) entered blocking state Jan 10 20:50:15 Mediaserv kernel: docker0: port 6(veth277617b) entered forwarding state Jan 10 20:50:50 Mediaserv kernel: vethe68dcdd: renamed from eth0 Jan 10 20:50:50 Mediaserv kernel: docker0: port 8(vethcebc4bb) entered disabled state Jan 10 20:50:50 Mediaserv kernel: docker0: port 8(vethcebc4bb) entered disabled state Jan 10 20:50:50 Mediaserv kernel: device vethcebc4bb left promiscuous mode Jan 10 20:50:50 Mediaserv kernel: docker0: port 8(vethcebc4bb) entered disabled state Jan 10 20:50:52 Mediaserv kernel: docker0: port 8(veth5ef5404) entered blocking state Jan 10 20:50:52 Mediaserv kernel: docker0: port 8(veth5ef5404) entered disabled state Jan 10 20:50:52 Mediaserv kernel: device veth5ef5404 entered promiscuous mode Jan 10 20:50:52 Mediaserv kernel: IPv6: ADDRCONF(NETDEV_UP): veth5ef5404: link is not ready Jan 10 20:50:52 Mediaserv kernel: eth0: renamed from veth013cc31 Jan 10 20:50:52 Mediaserv kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth5ef5404: link becomes ready Jan 10 20:50:52 Mediaserv kernel: docker0: port 8(veth5ef5404) entered blocking state Jan 10 20:50:52 Mediaserv kernel: docker0: port 8(veth5ef5404) entered forwarding state My Diag zip is attached. Any suggesting would be helpful. mediaserv-diagnostics-20200111-0234.zip
  15. I get an "attempting to upgrade" message when I restart the docker and a long pause before it completes, is this new? Should it happen every time I restart plex? ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 999 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 40-chown-files: executing... [cont-init.d] 40-chown-files: exited 0. [cont-init.d] 45-plex-claim: executing... [cont-init.d] 45-plex-claim: exited 0. [cont-init.d] 50-gid-video: executing... [cont-init.d] 50-gid-video: exited 0. [cont-init.d] 60-plex-update: executing... Atempting to upgrade to: 1.18.4.2171-ac2afe5f8 2020-01-03 21:58:43 URL:https://downloads.plex.tv/plex-media-server-new/1.18.4.2171-ac2afe5f8/debian/plexmediaserver_1.18.4.2171-ac2afe5f8_amd64.deb [86833802/86833802] -> "/tmp/plexmediaserver_1.18.4.2171-ac2afe5f8_amd64.deb" [1] (Reading database ... 10445 files and directories currently installed.) Preparing to unpack .../plexmediaserver_1.18.4.2171-ac2afe5f8_amd64.deb ... Unpacking plexmediaserver (1.18.4.2171-ac2afe5f8) over (1.18.3.2156-349e9837e) ... Setting up plexmediaserver (1.18.4.2171-ac2afe5f8) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... [cont-init.d] 60-plex-update: exited 0. [cont-init.d] 99-custom-scripts: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-scripts: exited 0. [cont-init.d] done. [services.d] starting services Starting Plex Media Server. [services.d] done.
  16. Ohhhhhhh....I totally misunderstood that function. Thank you.
  17. I'm trying to track down a random reboot issue I'm having. I need to a syslog from a time before a reboot. I went to settings, turned on local Syslog Server, but no files show up in the share folder I selected. It appears the GUI modified the .conf files with the share information. Is there a step I'm missing?
  18. The config file changes didn't solve my problem. Jan 7 18:55:45 Mediaserv kernel: pcieport 0000:00:01.1: AER: Corrected error received: 0000:00:00.0 Jan 7 18:55:45 Mediaserv kernel: pcieport 0000:00:01.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Jan 7 18:55:45 Mediaserv kernel: pcieport 0000:00:01.1: device [1022:1453] error status/mask=00000040/00006000 Jan 7 18:55:45 Mediaserv kernel: pcieport 0000:00:01.1: [ 6] Bad TLP Is there a way to determine which PCI card is causing the problem? I only have a 1 raid card and a video card.
  19. Thanks! Not sure of the syntax of this file, I did not add a coma. I've updated the file to: append initrd=/bzroot pci=nommconfto,/bzroot-gui
  20. This problem just started appearing in my log: Jan 6 04:40:01 Mediaserv apcupsd[85286]: apcupsd exiting, signal 15 Jan 6 04:40:01 Mediaserv apcupsd[85286]: apcupsd shutdown succeeded Jan 6 04:40:04 Mediaserv apcupsd[26280]: apcupsd 3.14.14 (31 May 2016) slackware startup succeeded Jan 6 04:40:04 Mediaserv apcupsd[26280]: NIS server startup succeeded Jan 6 04:40:41 Mediaserv kernel: pcieport 0000:00:01.1: AER: Corrected error received: 0000:00:00.0 Jan 6 04:40:41 Mediaserv kernel: pcieport 0000:00:01.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Jan 6 04:40:41 Mediaserv kernel: pcieport 0000:00:01.1: device [1022:1453] error status/mask=00000040/00006000 Jan 6 04:40:41 Mediaserv kernel: pcieport 0000:00:01.1: [ 6] Bad TLP Jan 6 04:49:48 Mediaserv kernel: pcieport 0000:00:01.1: AER: Corrected error received: 0000:00:00.0 Jan 6 04:49:48 Mediaserv kernel: pcieport 0000:00:01.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Jan 6 04:49:48 Mediaserv kernel: pcieport 0000:00:01.1: device [1022:1453] error status/mask=00000040/00006000 Jan 6 04:49:48 Mediaserv kernel: pcieport 0000:00:01.1: [ 6] Bad TLP Jan 6 04:51:10 Mediaserv kernel: pcieport 0000:00:01.1: AER: Corrected error received: 0000:00:00.0 Jan 6 04:51:10 Mediaserv kernel: pcieport 0000:00:01.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Jan 6 04:51:10 Mediaserv kernel: pcieport 0000:00:01.1: device [1022:1453] error status/mask=00000040/00006000 Jan 6 04:51:10 Mediaserv kernel: pcieport 0000:00:01.1: [ 6] Bad TLP Jan 6 04:52:01 Mediaserv kernel: pcieport 0000:00:01.1: AER: Corrected error received: 0000:00:00.0 Jan 6 04:52:01 Mediaserv kernel: pcieport 0000:00:01.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Jan 6 04:52:01 Mediaserv kernel: pcieport 0000:00:01.1: device [1022:1453] error status/mask=00000040/00006000 Jan 6 04:52:01 Mediaserv kernel: pcieport 0000:00:01.1: [ 6] Bad TLP Jan 6 04:52:47 Mediaserv kernel: pcieport 0000:00:01.1: AER: Corrected error received: 0000:00:00.0 Jan 6 04:52:47 Mediaserv kernel: pcieport 0000:00:01.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Jan 6 04:52:47 Mediaserv kernel: pcieport 0000:00:01.1: device [1022:1453] error status/mask=00000040/00006000 Jan 6 04:52:47 Mediaserv kernel: pcieport 0000:00:01.1: [ 6] Bad TLP Jan 6 04:52:59 Mediaserv kernel: pcieport 0000:00:01.1: AER: Corrected error received: 0000:00:00.0 Jan 6 04:52:59 Mediaserv kernel: pcieport 0000:00:01.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Jan 6 04:52:59 Mediaserv kernel: pcieport 0000:00:01.1: device [1022:1453] error status/mask=00000040/00006000 Jan 6 04:52:59 Mediaserv kernel: pcieport 0000:00:01.1: [ 6] Bad TLP Jan 6 04:53:01 Mediaserv kernel: pcieport 0000:00:01.1: AER: Corrected error received: 0000:00:00.0 Jan 6 04:53:01 Mediaserv kernel: pcieport 0000:00:01.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Jan 6 04:53:01 Mediaserv kernel: pcieport 0000:00:01.1: device [1022:1453] error status/mask=00000040/00006000 Jan 6 04:53:01 Mediaserv kernel: pcieport 0000:00:01.1: [ 6] Bad TLP Jan 6 04:53:02 Mediaserv kernel: pcieport 0000:00:01.1: AER: Corrected error received: 0000:00:00.0 Jan 6 04:53:02 Mediaserv kernel: pcieport 0000:00:01.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Jan 6 04:53:02 Mediaserv kernel: pcieport 0000:00:01.1: device [1022:1453] error status/mask=00000040/00006000 Jan 6 04:53:02 Mediaserv kernel: pcieport 0000:00:01.1: [ 6] Bad TLP System Info Model: Custom M/B: ASRock - X399 Taichi CPU: AMD Ryzen Threadripper 1950X 16-Core @ 3400 HVM: Enabled IOMMU: Enabled Cache: 1536 kB, 8192 kB, 32768 kB Memory: 16 GB (max. installable capacity 512 GB) Network: eth0: 1000 Mb/s, full duplex, mtu 1500 eth1: not connected Kernel: Linux 4.18.8-unRAID x86_64 OpenSSL: 1.1.0i Uptime: 9 days, 09:46:49 Any recommendation on a solution?
  21. Looks like an ombi error. You should contact them Thanks...It appears to be a know issue logged on github. Question: is there a docker variable I can sent to pull an earlier (working) version until the issue is fixed?
  22. I just started getting this error: Something bad happened, ErrorMiddleware caught this System.OperationCanceledException: The operation was canceled. at System.Net.Http.HttpClient.HandleFinishSendAsyncError(Exception e, CancellationTokenSource cts) at System.Net.Http.HttpClient.FinishSendAsyncBuffered(Task`1 sendTask, HttpRequestMessage request, CancellationTokenSource cts, Boolean disposeCts) at Ombi.Api.OmbiHttpClient.SendAsync(HttpRequestMessage request) in C:\projects\requestplex\src\Ombi.Api\OmbiHttpClient.cs:line 61 at Ombi.Api.Api.Request[T](Request request) in C:\projects\requestplex\src\Ombi.Api\Api.cs:line 38 at Ombi.Api.FanartTv.FanartTvApi.GetMovieImages(String movieOrImdbId, String token) in C:\projects\requestplex\src\Ombi.Api.FanartTv\FanartTvApi.cs:line 42 at Ombi.Controllers.ImagesController.GetBackgroundImage() in C:\projects\requestplex\src\Ombi\Controllers\ImagesController.cs:line 197 at lambda_method(Closure , Object ) at Microsoft.AspNetCore.Mvc.Internal.ActionMethodExecutor.AwaitableObjectResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments) at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeActionMethodAsync() at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeNextActionFilterAsync() at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Rethrow(ActionExecutedContext context) at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeInnerFilterAsync() at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeNextResourceFilter() at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Rethrow(ResourceExecutedContext context) at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeFilterPipelineAsync() at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeAsync() at Microsoft.AspNetCore.Builder.RouterMiddleware.Invoke(HttpContext httpContext) at Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware.Invoke(HttpContext context) at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIIndexMiddleware.Invoke(HttpContext httpContext) at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext) at Microsoft.AspNetCore.Cors.Infrastructure.CorsMiddleware.Invoke(HttpContext context) at Ombi.ApiKeyMiddlewear.Invoke(HttpContext context) in C:\projects\requestplex\src\Ombi\ApiKeyMiddlewear.cs:line 50 at Ombi.ErrorHandlingMiddleware.Invoke(HttpContext context) in C:\projects\requestplex\src\Ombi\ErrorHandlingMiddlewear.cs:line 24
  23. My log show this message repeatedly: 2018-08-23 22:27:51,784 DEBG 'start-script' stdout output:[warn] Response code 000 from curl != 2xx[warn] Exit code 7 from curl != 0[info] 9 retries left[info] Retrying in 10 secs... Full debug log attached . Any recommendations on a fix would be appreciated. supervisord.log
  24. For some odd reason my Radarr docker became orphaned. I recreated the Radarr docker. Question: Movie requests were made will Radarr was down (it was down three days), will Ombi automatically update Radarr with those missing movies now that both are up or do I need to manually add those movies that were add while Radatt was down?
  25. I did not think of that...Very good point! Yes, I have set my upload speed in plex, so I agree this could trigger more transcoding to fit the available bandwidth. But that still points at getting a faster CPU as a solution...correct? Or am I missing something (else)?