TexasUnraid

Members
  • Posts

    1178
  • Joined

  • Last visited

Everything posted by TexasUnraid

  1. I forgot how I set it up to be honest I did most of the setup ~4-5 years ago. My kodi box is currently down due to moving things around. It is not in the normal videos/shows section though. Seems like it has an option for youtube videos or maybe I created that folder a long time ago. I forgot lol. I know on my dashboard it is near the bottom of the options and I have it setup with youtube > channels > videos IIRC. It then lists the videos from the youtube titles (also the file name title) and like you said the NFO feeds in the video description on the video that have it, I have changed how I download them a few times so not all of them do.
  2. Kodi is my media manager of choice, it has options to split the videos out by folder (and thus channel), not "officially" organized but it works ok. Also will just use windows explorer in some cases. Agreed the censoring has gotten out of hand, and I tend to go in spurts of video watching every week or 2 so I miss a fair amount without downloading lol.
  3. I like downloading channels to have a local copy. 3 basic categories. 1: Videos for the kids, I don't like letting the younger ones roam free on the internet so by giving them access to a local copy of some channels I select they can watch the videos without going down rabbit holes they don't need to know exist. 2: Videos for me where I like to archive channels I like, just because lol. 3: With the way channels/videos get purged the last few years, I like to have local copies of videos in case they disappear from youtube. Had a lot of videos bookmarked to watch later only for them to be gone when I wanted to watch them.
  4. Installing tartube and making it work is pretty easy indeed. The hard part is the GUI in a docker. That takes more work. Tubesync is in beta and was pointed out in another thread, it looks very promising once ready for full release, still missing some features I need ATM it looks like.
  5. I tried it last year when I ended up settling on tartube. There was some kind of usage breaking issue with material but forgot what it was, think it might of been the lack of 480p quality setting / proxy IIRC. Just know I tried it and could not make it work then for what I need. Might of also been an issue with large channels, some of them have 10,000's++ videos. Has anything changed in the last ~9 months?
  6. Yeah, the lack of info in the errors is why it took me so long to narrow it down. We had not talked about those, looked into them briefly just now though. Metube looks like a 1 time download client, very useful and I could see a use case for it on my server (when the kids want to download a single video/channel for example) but not what I am aiming for in this particular use case. I have a set of youtube channels that I like to keep a local copy of, so it will automatically download all videos on the channel and any new ones that are posted. Which is where tubesync comes in, this looks very interesting although still in beta. There are a few features that I am not sure if they are possible with it though, such as the ability to control the resolution downloaded (I limit a lot of channels to 480p to save space, the kids don't need HD vids). Also the ability to download from other sites is something that is quite handy. Doesn't look like it supports downloading through a proxy as well and I have had issues routing containers through a VPN container. Once fully fleshed out and a full release I could easily see it being a good option.
  7. Ok Thanks, here are the errors I was able to capture, the entire system would hard lock so I could not get the logs or anything. I did catch it mid-crash once and was able to extract this from the log before it died completely, this is actually what led me to suspect tartube was the issue due to the next image: ErrorWarningSystemArrayLogin Jan 16 07:29:58 NAS kernel: asm_call_irq_on_stack+0x12/0x20 Jan 16 07:29:58 NAS kernel: </IRQ> Jan 16 07:29:58 NAS kernel: sysvec_apic_timer_interrupt+0x71/0x95 Jan 16 07:29:58 NAS kernel: asm_sysvec_apic_timer_interrupt+0x12/0x20 Jan 16 07:29:58 NAS kernel: RIP: 0010:xas_descend+0x1e/0x49 Jan 16 07:29:58 NAS kernel: Code: 08 48 d3 e6 48 01 f0 48 89 47 08 c3 0f b6 0e 49 89 f9 48 8b 47 08 48 d3 e8 48 89 c1 83 e1 3f 89 c8 48 83 c0 04 4c 8b 44 c6 08 <48> 89 77 18 4c 89 c7 e8 77 ff ff ff 84 c0 74 13 49 c1 e8 02 44 89 Jan 16 07:29:58 NAS kernel: RSP: 0018:ffffc90034a67a38 EFLAGS: 00000216 Jan 16 07:29:58 NAS kernel: RAX: 0000000000000021 RBX: 0000000000000007 RCX: 000000000000001d Jan 16 07:29:58 NAS kernel: RDX: 0000000000000001 RSI: ffff88a28bc6c490 RDI: ffffc90034a67a48 Jan 16 07:29:58 NAS kernel: RBP: ffff88923c7c3358 R08: ffff88821d8eb688 R09: ffffc90034a67a48 Jan 16 07:29:58 NAS kernel: R10: ffffc90034a67a48 R11: 000000000000000e R12: ffff88821d8eb688 Jan 16 07:29:58 NAS kernel: R13: ffff88923c7c34c8 R14: 000000000001c05d R15: ffff88a64cb1ea68 Jan 16 07:29:58 NAS kernel: ? xas_descend+0x2a/0x49 Jan 16 07:29:58 NAS kernel: xas_load+0x2d/0x39 Jan 16 07:29:58 NAS kernel: find_get_entry+0x57/0xba Jan 16 07:29:58 NAS kernel: pagecache_get_page+0x20/0x13e Jan 16 07:29:58 NAS kernel: prepare_pages+0x73/0x133 Jan 16 07:29:58 NAS kernel: btrfs_buffered_write+0x285/0x5a2 Jan 16 07:29:58 NAS kernel: ? update_load_avg+0x39/0x2c4 Jan 16 07:29:58 NAS kernel: btrfs_file_write_iter+0x3cc/0x4b1 Jan 16 07:29:58 NAS kernel: do_iter_readv_writev+0x97/0xd7 Jan 16 07:29:58 NAS kernel: do_iter_write+0x7f/0xc0 Jan 16 07:29:58 NAS kernel: iter_file_splice_write+0x215/0x313 Jan 16 07:29:58 NAS kernel: direct_splice_actor+0x2e/0x2f Jan 16 07:29:58 NAS kernel: splice_direct_to_actor+0x125/0x1cd Jan 16 07:29:58 NAS kernel: ? generic_file_splice_read+0x15e/0x15e Jan 16 07:29:58 NAS kernel: do_splice_direct+0x94/0xbd Jan 16 07:29:58 NAS kernel: do_sendfile+0x185/0x24f Jan 16 07:29:58 NAS kernel: __do_sys_sendfile64+0x61/0xa7 Jan 16 07:29:58 NAS kernel: do_syscall_64+0x5d/0x6a Jan 16 07:29:58 NAS kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jan 16 07:29:58 NAS kernel: RIP: 0033:0x7efe3948e68e Jan 16 07:29:58 NAS kernel: Code: c3 0f 1f 00 4c 89 d2 4c 89 c6 e9 bd fd ff ff 0f 1f 44 00 00 31 c0 c3 0f 1f 44 00 00 f3 0f 1e fa 49 89 ca b8 28 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d d2 a7 0c 00 f7 d8 64 89 01 48 Jan 16 07:29:58 NAS kernel: RSP: 002b:00007ffe62eb1b68 EFLAGS: 00000246 ORIG_RAX: 0000000000000028 Jan 16 07:29:58 NAS kernel: RAX: ffffffffffffffda RBX: 00007ffe62eb1c20 RCX: 00007efe3948e68e Jan 16 07:29:58 NAS kernel: RDX: 00007ffe62eb1c40 RSI: 0000000000000005 RDI: 0000000000000007 Jan 16 07:29:58 NAS kernel: RBP: 00007ffe62f31fb0 R08: 0000000000000000 R09: 000000000008871d Jan 16 07:29:58 NAS kernel: R10: 0000000000080000 R11: 0000000000000246 R12: 00007ffe62eb1c10 Jan 16 07:29:58 NAS kernel: R13: 00007ffe62eb1c40 R14: 00007ffe62eb1bd8 R15: 00007ffe62eb1bd0 Jan 16 07:32:58 NAS kernel: rcu: INFO: rcu_sched self-detected stall on CPU Jan 16 07:32:58 NAS kernel: rcu: 36-....: (420005 ticks this GP) idle=692/1/0x4000000000000000 softirq=29122084/29122084 fqs=104638 Jan 16 07:32:58 NAS kernel: (t=420006 jiffies g=214476629 q=4370531) Jan 16 07:32:58 NAS kernel: NMI backtrace for cpu 36 Jan 16 07:32:58 NAS kernel: CPU: 36 PID: 4502 Comm: file.so Tainted: G O 5.10.28-Unraid #1 Jan 16 07:32:58 NAS kernel: Hardware name: Supermicro X9DAX/X9DAX, BIOS 3.2a 06/30/2015 Jan 16 07:32:58 NAS kernel: Call Trace: Jan 16 07:32:58 NAS kernel: <IRQ> Jan 16 07:32:58 NAS kernel: dump_stack+0x6b/0x83 Jan 16 07:32:58 NAS kernel: ? lapic_can_unplug_cpu+0x8e/0x8e Jan 16 07:32:58 NAS kernel: nmi_cpu_backtrace+0x7d/0x8f Jan 16 07:32:58 NAS kernel: nmi_trigger_cpumask_backtrace+0x56/0xd3 Jan 16 07:32:58 NAS kernel: rcu_dump_cpu_stacks+0x9f/0xc6 Jan 16 07:32:58 NAS kernel: rcu_sched_clock_irq+0x1ec/0x543 Jan 16 07:32:58 NAS kernel: ? _raw_spin_unlock_irqrestore+0xd/0xe Jan 16 07:32:58 NAS kernel: update_process_times+0x50/0x6e Jan 16 07:32:58 NAS kernel: tick_sched_timer+0x36/0x64 Jan 16 07:32:58 NAS kernel: __hrtimer_run_queues+0xb7/0x10b Jan 16 07:32:58 NAS kernel: ? tick_sched_do_timer+0x39/0x39 Jan 16 07:32:58 NAS kernel: hrtimer_interrupt+0x8d/0x15b Jan 16 07:32:58 NAS kernel: __sysvec_apic_timer_interrupt+0x5d/0x68 Jan 16 07:32:58 NAS kernel: asm_call_irq_on_stack+0x12/0x20 Jan 16 07:32:58 NAS kernel: </IRQ> Jan 16 07:32:58 NAS kernel: sysvec_apic_timer_interrupt+0x71/0x95 Jan 16 07:32:58 NAS kernel: asm_sysvec_apic_timer_interrupt+0x12/0x20 Jan 16 07:32:58 NAS kernel: RIP: 0010:__page_cache_add_speculative.constprop.0+0x17/0x1f Jan 16 07:32:58 NAS kernel: Code: 00 00 48 89 ef e8 7a fd ff ff 48 89 ef 5d e9 87 fa ff ff 8b 57 34 85 d2 74 10 8d 4a 01 89 d0 f0 0f b1 4f 34 74 04 89 c2 eb ec <31> c0 85 d2 0f 95 c0 c3 41 54 65 48 8b 04 25 c0 7b 01 00 55 89 fd Jan 16 07:32:58 NAS kernel: RSP: 0018:ffffc90034a67a40 EFLAGS: 00000246 Jan 16 07:32:58 NAS kernel: RAX: ffff88821d8eb688 RBX: 0000000000000007 RCX: 000000000000001d Jan 16 07:32:58 NAS kernel: RDX: 0000000000000000 RSI: ffff88a28bc6c490 RDI: ffff88821d8eb688 Jan 16 07:32:58 NAS kernel: RBP: ffff88923c7c3358 R08: ffff88821d8eb688 R09: ffffc90034a67a48 Jan 16 07:32:58 NAS kernel: R10: ffffc90034a67a48 R11: 000000000000000e R12: ffff88821d8eb688 Jan 16 07:32:58 NAS kernel: R13: ffff88923c7c34c8 R14: 000000000001c05d R15: ffff88a64cb1ea68 Jan 16 07:32:58 NAS kernel: find_get_entry+0x7b/0xba Jan 16 07:32:58 NAS kernel: pagecache_get_page+0x20/0x13e Jan 16 07:32:58 NAS kernel: prepare_pages+0x73/0x133 Jan 16 07:32:58 NAS kernel: btrfs_buffered_write+0x285/0x5a2 Jan 16 07:32:58 NAS kernel: ? update_load_avg+0x39/0x2c4 Jan 16 07:32:58 NAS kernel: btrfs_file_write_iter+0x3cc/0x4b1 Jan 16 07:32:58 NAS kernel: do_iter_readv_writev+0x97/0xd7 Jan 16 07:32:58 NAS kernel: do_iter_write+0x7f/0xc0 Jan 16 07:32:58 NAS kernel: iter_file_splice_write+0x215/0x313 Jan 16 07:32:58 NAS kernel: direct_splice_actor+0x2e/0x2f Jan 16 07:32:58 NAS kernel: splice_direct_to_actor+0x125/0x1cd Jan 16 07:32:58 NAS kernel: ? generic_file_splice_read+0x15e/0x15e Jan 16 07:32:58 NAS kernel: do_splice_direct+0x94/0xbd Jan 16 07:32:58 NAS kernel: do_sendfile+0x185/0x24f Jan 16 07:32:58 NAS kernel: __do_sys_sendfile64+0x61/0xa7 Jan 16 07:32:58 NAS kernel: do_syscall_64+0x5d/0x6a Jan 16 07:32:58 NAS kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jan 16 07:32:58 NAS kernel: RIP: 0033:0x7efe3948e68e Jan 16 07:32:58 NAS kernel: Code: c3 0f 1f 00 4c 89 d2 4c 89 c6 e9 bd fd ff ff 0f 1f 44 00 00 31 c0 c3 0f 1f 44 00 00 f3 0f 1e fa 49 89 ca b8 28 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d d2 a7 0c 00 f7 d8 64 89 01 48 Jan 16 07:32:58 NAS kernel: RSP: 002b:00007ffe62eb1b68 EFLAGS: 00000246 ORIG_RAX: 0000000000000028 Jan 16 07:32:58 NAS kernel: RAX: ffffffffffffffda RBX: 00007ffe62eb1c20 RCX: 00007efe3948e68e Jan 16 07:32:58 NAS kernel: RDX: 00007ffe62eb1c40 RSI: 0000000000000005 RDI: 0000000000000007 Jan 16 07:32:58 NAS kernel: RBP: 00007ffe62f31fb0 R08: 0000000000000000 R09: 000000000008871d Jan 16 07:32:58 NAS kernel: R10: 0000000000080000 R11: 0000000000000246 R12: 00007ffe62eb1c10 Jan 16 07:32:58 NAS kernel: R13: 00007ffe62eb1c40 R14: 00007ffe62eb1bd8 R15: 00007ffe62eb1bd0 Jan 16 07:33:04 NAS nginx: 2022/01/16 07:33:04 [error] 38735#38735: *1873274 upstream timed out (110: Connection timed out) while reading upstream, client: 192.168.1.20, server: , request: "GET /favicon.ico HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "nas.local", referrer: "https://nas.local/logging.htm" Jan 16 07:35:58 NAS kernel: rcu: INFO: rcu_sched self-detected stall on CPU Jan 16 07:35:58 NAS kernel: rcu: 36-....: (600008 ticks this GP) idle=692/1/0x4000000000000000 softirq=29122084/29122084 fqs=149437 Jan 16 07:35:58 NAS kernel: (t=600009 jiffies g=214476629 q=6281381) Jan 16 07:35:58 NAS kernel: NMI backtrace for cpu 36 Jan 16 07:35:58 NAS kernel: CPU: 36 PID: 4502 Comm: file.so Tainted: G O 5.10.28-Unraid #1 Jan 16 07:35:58 NAS kernel: Hardware name: Supermicro X9DAX/X9DAX, BIOS 3.2a 06/30/2015 Jan 16 07:35:58 NAS kernel: Call Trace: Jan 16 07:35:58 NAS kernel: <IRQ> Jan 16 07:35:58 NAS kernel: dump_stack+0x6b/0x83 Jan 16 07:35:58 NAS kernel: ? lapic_can_unplug_cpu+0x8e/0x8e Jan 16 07:35:58 NAS kernel: nmi_cpu_backtrace+0x7d/0x8f Jan 16 07:35:58 NAS kernel: nmi_trigger_cpumask_backtrace+0x56/0xd3 Jan 16 07:35:58 NAS kernel: rcu_dump_cpu_stacks+0x9f/0xc6 Jan 16 07:35:58 NAS kernel: rcu_sched_clock_irq+0x1ec/0x543 Jan 16 07:35:58 NAS kernel: ? _raw_spin_unlock_irqrestore+0xd/0xe Jan 16 07:35:58 NAS kernel: update_process_times+0x50/0x6e Jan 16 07:35:58 NAS kernel: tick_sched_timer+0x36/0x64 Jan 16 07:35:58 NAS kernel: __hrtimer_run_queues+0xb7/0x10b Jan 16 07:35:58 NAS kernel: ? tick_sched_do_timer+0x39/0x39 Jan 16 07:35:58 NAS kernel: hrtimer_interrupt+0x8d/0x15b Jan 16 07:35:58 NAS kernel: __sysvec_apic_timer_interrupt+0x5d/0x68 Jan 16 07:35:58 NAS kernel: asm_call_irq_on_stack+0x12/0x20 Jan 16 07:35:58 NAS kernel: </IRQ> Jan 16 07:35:58 NAS kernel: sysvec_apic_timer_interrupt+0x71/0x95 Jan 16 07:35:58 NAS kernel: asm_sysvec_apic_timer_interrupt+0x12/0x20 Jan 16 07:35:58 NAS kernel: RIP: 0010:find_get_entry+0x62/0xba Jan 16 07:35:58 NAS kernel: Code: 20 00 00 00 00 48 c7 44 24 28 00 00 00 00 48 c7 44 24 18 03 00 00 00 48 89 e7 e8 8d c0 26 00 48 3d 06 04 00 00 49 89 c4 74 e4 <48> 3d 02 04 00 00 74 dc 48 85 c0 74 27 a8 01 75 23 48 89 c7 e8 b8 Jan 16 07:35:58 NAS kernel: RSP: 0018:ffffc90034a67a48 EFLAGS: 00000286 Jan 16 07:35:58 NAS kernel: RAX: ffff88821d8eb688 RBX: 0000000000000007 RCX: 000000000000001d Jan 16 07:35:58 NAS kernel: RDX: 0000000000000000 RSI: ffff88a28bc6c490 RDI: ffff88821d8eb688 Jan 16 07:35:58 NAS kernel: RBP: ffff88923c7c3358 R08: ffff88821d8eb688 R09: ffffc90034a67a48 Jan 16 07:35:58 NAS kernel: R10: ffffc90034a67a48 R11: 000000000000000e R12: ffff88821d8eb688 Jan 16 07:35:58 NAS kernel: R13: ffff88923c7c34c8 R14: 000000000001c05d R15: ffff88a64cb1ea68 Jan 16 07:35:58 NAS kernel: ? find_get_entry+0x57/0xba Jan 16 07:35:58 NAS kernel: pagecache_get_page+0x20/0x13e Jan 16 07:35:58 NAS kernel: prepare_pages+0x73/0x133 Jan 16 07:35:58 NAS kernel: btrfs_buffered_write+0x285/0x5a2 Jan 16 07:35:58 NAS kernel: ? update_load_avg+0x39/0x2c4 Jan 16 07:35:58 NAS kernel: btrfs_file_write_iter+0x3cc/0x4b1 Jan 16 07:35:58 NAS kernel: do_iter_readv_writev+0x97/0xd7 Jan 16 07:35:58 NAS kernel: do_iter_write+0x7f/0xc0 Jan 16 07:35:58 NAS kernel: iter_file_splice_write+0x215/0x313 Jan 16 07:35:58 NAS kernel: direct_splice_actor+0x2e/0x2f Jan 16 07:35:58 NAS kernel: splice_direct_to_actor+0x125/0x1cd Jan 16 07:35:58 NAS kernel: ? generic_file_splice_read+0x15e/0x15e Jan 16 07:35:58 NAS kernel: do_splice_direct+0x94/0xbd Jan 16 07:35:58 NAS kernel: do_sendfile+0x185/0x24f Jan 16 07:35:58 NAS kernel: __do_sys_sendfile64+0x61/0xa7 Jan 16 07:35:58 NAS kernel: do_syscall_64+0x5d/0x6a Jan 16 07:35:58 NAS kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jan 16 07:35:58 NAS kernel: RIP: 0033:0x7efe3948e68e Jan 16 07:35:58 NAS kernel: Code: c3 0f 1f 00 4c 89 d2 4c 89 c6 e9 bd fd ff ff 0f 1f 44 00 00 31 c0 c3 0f 1f 44 00 00 f3 0f 1e fa 49 89 ca b8 28 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d d2 a7 0c 00 f7 d8 64 89 01 48 Jan 16 07:35:58 NAS kernel: RSP: 002b:00007ffe62eb1b68 EFLAGS: 00000246 ORIG_RAX: 0000000000000028 Jan 16 07:35:58 NAS kernel: RAX: ffffffffffffffda RBX: 00007ffe62eb1c20 RCX: 00007efe3948e68e Jan 16 07:35:58 NAS kernel: RDX: 00007ffe62eb1c40 RSI: 0000000000000005 RDI: 0000000000000007 Jan 16 07:35:58 NAS kernel: RBP: 00007ffe62f31fb0 R08: 0000000000000000 R09: 000000000008871d Jan 16 07:35:58 NAS kernel: R10: 0000000000080000 R11: 0000000000000246 R12: 00007ffe62eb1c10 Jan 16 07:35:58 NAS kernel: R13: 00007ffe62eb1c40 R14: 00007ffe62eb1bd8 R15: 00007ffe62eb1bd0 Jan 16 07:37:14 NAS nginx: 2022/01/16 07:37:14 [error] 38735#38735: *1874493 upstream timed out (110: Connection timed out) while reading upstream, client: 192.168.1.20, server: , request: "GET /Dashboard HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "nas.local", referrer: "https://nas.local/script" Jan 16 07:38:58 NAS kernel: rcu: INFO: rcu_sched self-detected stall on CPU Jan 16 07:38:58 NAS kernel: rcu: 36-....: (780011 ticks this GP) idle=692/1/0x4000000000000000 softirq=29122084/29122084 fqs=194300 Jan 16 07:38:58 NAS kernel: (t=780012 jiffies g=214476629 q=8153649) Jan 16 07:38:58 NAS kernel: NMI backtrace for cpu 36 Jan 16 07:38:58 NAS kernel: CPU: 36 PID: 4502 Comm: file.so Tainted: G O 5.10.28-Unraid #1 Jan 16 07:38:58 NAS kernel: Hardware name: Supermicro X9DAX/X9DAX, BIOS 3.2a 06/30/2015 Jan 16 07:38:58 NAS kernel: Call Trace: Jan 16 07:38:58 NAS kernel: <IRQ> Jan 16 07:38:58 NAS kernel: dump_stack+0x6b/0x83 Jan 16 07:38:58 NAS kernel: ? lapic_can_unplug_cpu+0x8e/0x8e Jan 16 07:38:58 NAS kernel: nmi_cpu_backtrace+0x7d/0x8f Jan 16 07:38:58 NAS kernel: nmi_trigger_cpumask_backtrace+0x56/0xd3 Jan 16 07:38:58 NAS kernel: rcu_dump_cpu_stacks+0x9f/0xc6 Jan 16 07:38:58 NAS kernel: rcu_sched_clock_irq+0x1ec/0x543 Jan 16 07:38:58 NAS kernel: ? _raw_spin_unlock_irqrestore+0xd/0xe Jan 16 07:38:58 NAS kernel: update_process_times+0x50/0x6e Jan 16 07:38:58 NAS kernel: tick_sched_timer+0x36/0x64 Jan 16 07:38:58 NAS kernel: __hrtimer_run_queues+0xb7/0x10b Jan 16 07:38:58 NAS kernel: ? tick_sched_do_timer+0x39/0x39 Jan 16 07:38:58 NAS kernel: hrtimer_interrupt+0x8d/0x15b Jan 16 07:38:58 NAS kernel: __sysvec_apic_timer_interrupt+0x5d/0x68 Jan 16 07:38:58 NAS kernel: asm_call_irq_on_stack+0x12/0x20 Jan 16 07:38:58 NAS kernel: </IRQ> Jan 16 07:38:58 NAS kernel: sysvec_apic_timer_interrupt+0x71/0x95 Jan 16 07:38:58 NAS kernel: asm_sysvec_apic_timer_interrupt+0x12/0x20 Jan 16 07:38:58 NAS kernel: RIP: 0010:xa_is_sibling+0x6/0x1a Jan 16 07:38:58 NAS kernel: Code: 10 c3 c6 07 00 0f 1f 40 00 c3 48 89 f8 83 e0 03 48 83 f8 02 0f 94 c0 48 81 ff 00 10 00 00 0f 97 c2 21 d0 c3 48 89 f8 83 e0 03 <48> 83 f8 02 0f 94 c0 48 81 ff fd 00 00 00 0f 96 c2 21 d0 c3 40 f6 Jan 16 07:38:58 NAS kernel: RSP: 0018:ffffc90034a67a30 EFLAGS: 00000202 Jan 16 07:38:58 NAS kernel: RAX: 0000000000000002 RBX: 0000000000000007 RCX: 000000000000001c Jan 16 07:38:58 NAS kernel: RDX: 0000000000000001 RSI: ffff88a3f19fc490 RDI: ffff88a28bc6e482 Jan 16 07:38:58 NAS kernel: RBP: ffff88923c7c3358 R08: ffff88a28bc6e482 R09: ffffc90034a67a48 Jan 16 07:38:58 NAS kernel: R10: ffffc90034a67a48 R11: 000000000000000e R12: ffff88821d8eb688 Jan 16 07:38:58 NAS kernel: R13: ffff88923c7c34c8 R14: 000000000001c05d R15: ffff88a64cb1ea68 Jan 16 07:38:58 NAS kernel: xas_descend+0x2a/0x49 Jan 16 07:38:58 NAS kernel: xas_load+0x2d/0x39 Jan 16 07:38:58 NAS kernel: find_get_entry+0x57/0xba Jan 16 07:38:58 NAS kernel: pagecache_get_page+0x20/0x13e Jan 16 07:38:58 NAS kernel: prepare_pages+0x73/0x133 Jan 16 07:38:58 NAS kernel: btrfs_buffered_write+0x285/0x5a2 Jan 16 07:38:58 NAS kernel: ? update_load_avg+0x39/0x2c4 Jan 16 07:38:58 NAS kernel: btrfs_file_write_iter+0x3cc/0x4b1 Jan 16 07:38:58 NAS kernel: do_iter_readv_writev+0x97/0xd7 Jan 16 07:38:58 NAS kernel: do_iter_write+0x7f/0xc0 Jan 16 07:38:58 NAS kernel: iter_file_splice_write+0x215/0x313 Jan 16 07:38:58 NAS kernel: direct_splice_actor+0x2e/0x2f Jan 16 07:38:58 NAS kernel: splice_direct_to_actor+0x125/0x1cd Jan 16 07:38:58 NAS kernel: ? generic_file_splice_read+0x15e/0x15e Jan 16 07:38:58 NAS kernel: do_splice_direct+0x94/0xbd Jan 16 07:38:58 NAS kernel: do_sendfile+0x185/0x24f Jan 16 07:38:58 NAS kernel: __do_sys_sendfile64+0x61/0xa7 Jan 16 07:38:58 NAS kernel: do_syscall_64+0x5d/0x6a Jan 16 07:38:58 NAS kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jan 16 07:38:58 NAS kernel: RIP: 0033:0x7efe3948e68e Jan 16 07:38:58 NAS kernel: Code: c3 0f 1f 00 4c 89 d2 4c 89 c6 e9 bd fd ff ff 0f 1f 44 00 00 31 c0 c3 0f 1f 44 00 00 f3 0f 1e fa 49 89 ca b8 28 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d d2 a7 0c 00 f7 d8 64 89 01 48 Jan 16 07:38:58 NAS kernel: RSP: 002b:00007ffe62eb1b68 EFLAGS: 00000246 ORIG_RAX: 0000000000000028 Jan 16 07:38:58 NAS kernel: RAX: ffffffffffffffda RBX: 00007ffe62eb1c20 RCX: 00007efe3948e68e Jan 16 07:38:58 NAS kernel: RDX: 00007ffe62eb1c40 RSI: 0000000000000005 RDI: 0000000000000007 Jan 16 07:38:58 NAS kernel: RBP: 00007ffe62f31fb0 R08: 0000000000000000 R09: 000000000008871d Jan 16 07:38:58 NAS kernel: R10: 0000000000080000 R11: 0000000000000246 R12: 00007ffe62eb1c10 Jan 16 07:38:58 NAS kernel: R13: 00007ffe62eb1c40 R14: 00007ffe62eb1bd8 R15: 00007ffe62eb1bd0 Jan 16 07:39:09 NAS shutdown[8721]: shutting down for system halt Jan 16 07:39:09 NAS init: Switching to runlevel: 0 Jan 16 07:39:09 NAS init: Trying to re-exec init Jan 16 07:39:10 NAS root: Starting Run at Shutdown script Jan 16 07:39:10 NAS root: Stopping Dockers Jan 16 07:40:14 NAS kernel: rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks: { 36-... } 63968 jiffies s: 2909 root: 0x4/. Jan 16 07:40:14 NAS kernel: rcu: blocking rcu_node structures: l=1:28-39:0x100/. Jan 16 07:40:14 NAS kernel: Task dump for CPU 36: Jan 16 07:40:14 NAS kernel: task:file.so state:R running task stack: 0 pid: 4502 ppid: 11242 flags:0x0000000e Jan 16 07:40:14 NAS kernel: Call Trace: Jan 16 07:40:14 NAS kernel: ? do_iter_readv_writev+0x97/0xd7 Jan 16 07:40:14 NAS kernel: ? do_iter_write+0x7f/0xc0 Jan 16 07:40:14 NAS kernel: ? iter_file_splice_write+0x215/0x313 Jan 16 07:40:14 NAS kernel: ? direct_splice_actor+0x2e/0x2f Jan 16 07:40:14 NAS kernel: ? splice_direct_to_actor+0x125/0x1cd Jan 16 07:40:14 NAS kernel: ? generic_file_splice_read+0x15e/0x15e Jan 16 07:40:14 NAS kernel: ? do_splice_direct+0x94/0xbd Jan 16 07:40:14 NAS kernel: ? do_sendfile+0x185/0x24f Jan 16 07:40:14 NAS kernel: ? __do_sys_sendfile64+0x61/0xa7 Jan 16 07:40:14 NAS kernel: ? do_syscall_64+0x5d/0x6a Jan 16 07:40:14 NAS kernel: ? entry_SYSCALL_64_after_hwframe+0x44/0xa9 The rest are just screen shots of the IPMI screen after the crash, they are all pretty simular just with slight variations of the errors. Most of them mention kernel panic and sync errors. I have more if you think they would help.
  8. @ich777 I ran into some strange issues with the debian buster docker with tartube installed where it would crash my entire server randomly for the last 6 months. I was not aware that docker could crash the host? Here is a link to the details if you want to take a look, I can post the screenshots of the errors.
  9. @ich777 TL:DR After ~6 months of testing and issues The Buster docker with tartube installed causes the entire server to crash with a kernel panic of some sort. I have some of the errors screen shotted if you want them. I was not aware this was even possible with how docker is setup? Is it possible to make a tartube docker that would not cause crashes like this? I have really fallen in love with the program after using it. I installed it in a VM and while it sort of works the slow SMB interface that unraid/linux has with small files seems to cause timeout issues beyond it simply taking forever to do stuff. the long version: So after using the buster docker with tartube for the last 6 months (which I love the program BTW), I think I FINALLY found what was causing my random kernel panics / crashes. It would sometimes last a week and others hours but sooner or later the whole system would hard crash and need a reboot. I started in safe mode and it never seemed to crash so I knew it was some kind of plugin but after testing all of those, it was still crashing. I was not aware that a docker could even crash the main system so I ignored them for a long time but then by chance I had a lot of dockers turned off while testing something else for a few weeks and noticed the long uptime but could not figure it out. After a lot of testing I think I narrowed it down to the tartube docker, I can't think of a time it crashed without it running. If I start it, it crashes at some point. The crashes also started about when I installed it in the first place.
  10. Plex is something you need to watch out for, it can really hammer the cache, I don't use it personally but others can help you with that. I have a server in the garage and even in 20 degree weather I hardly see those kinds of temps lol. I did read a paper from google that said keeping drives too cold actually caused them to fail sooner. The sweet spot seemed to be around 30-35c. I try to keep my drives in that range if possible.
  11. Depends on what all you have running and what you are doing. Overall though, assuming you have dockers running and use the cache for file transfers, I would not be worried about that. I do notice the 15c temps, you have it in the garage lol?
  12. I have been dealing with similar issues for months, it will just randomly lock up and require a hard reset. Sometimes multiple times in a single day, others it will go weeks between. I can not seem to narrow down the issue but it happens more when it is actively doing something. It never saves diagnostics or logs which makes it a real pain as well. Only started happening after updating to 6.9.2, although it was not right away after updating.
  13. I seem to be having general PIA wireguard VPN issues in addition to the prioxy issues above as well. Takes a long time for the qbittorrent to start up and it seems to be during the VPN setup. Then the connection seems really unstable with downloads sometimes not starting at all, others going very slow and other working normally. Once it starts working normally, it seems to stay that way as long as I don't touch anything. Very inconsistent though.
  14. For the last few weeks I have had issues with the privoxy HTTP proxy in qbittorrent. the *arr's can't seem to connect to anything through it most of the time. I tried using the binhex dedicated privoxy container that supported Socks5 proxy and they work fine through that but that is another VPN connection I have running. Does anyone know why the HTTP proxy in qbittorrent stopped working? Or does anyone know how to enable a socks5 proxy in it? I have not changed any settings in months and it was working fine.
  15. Not really the place to ask this but not sure of a better place. Long story short, I need to setup an openvpn connection between 2 locations so that I can share the lan connection between the locations. I need to manage some systems in home 2 from home 1 primarily, so SSH/VNC/IPMI/HTTP access to the LAN in home 2. Being able to send files across via smb would be a big bonus but I could figure out alternate options if needed. Home 1 has PFsense as a router, also my unraid server that runs almost 24/7 (been crashing randomly lately). The hardware in home 2 is an Ausu AC68U with merlin. Not sure what the best method would be, have an openvpn sever on pfsense and the client on AC68U with a bridged connection? What happens if it can't setup that tunnel? I need the internet on both ends to be unaffected regardless. Setup a VM/docker on unraid that connects to home 2 and then manage things through that? I am looking for noob friendly guides to watch/read to learn how to do this. Never messed with openvpn outside of PIA. Anyone know where to look or the keywords to search?
  16. Yeah, this is why I went with the more dedicated docker setup since it was designed for this use case. /tmp works fine for a lot of things but not everything. If it works, great go ahead and use it. If not then swap to the dedicated docker tmp.
  17. Just wanted to report that I got the title and icon changed. Ended up deciding it would be easier to just map the whole /usr/share/novnc/app/ to appdata then edit the files in there so they are persistent. Only issue I ran into is that firefox seems to pull the 192x192 icon image where chrome pulls the 144x144. So that threw me for a loop for a bit. After mapping it and clearing cookies etc it is working great!
  18. Great, that should get me going. I mostly had no idea where to start looking for the files. I will mess around with it later and see what I can come up with. Should be able to get it working with this info. Thanks
  19. Cool, that doesn't sound that bad, was considering coping the container and customizing it internally if there was not an option like this. Currently have 2 containers running but I am liking this setup so thinking about using another one or 2 if these pan out. For my work it makes life a lot easier. Is there a way to use that script to update the icon for the container as well? Where is the icon stored in the container?
  20. I am using your firefox image and it is working good to be able to stay logged into the same site under multiple accounts easily and from multiple machines. I was curious, is it possible to edit the icon/title that it shows in the VNC window? Is it stored someplace I could replace it? Or is there a variable that can be edited? It gets kinda confusing having multiple windows with the same icons next to each other.
  21. Depends on if he is talking packet sniffing reconnects or something larger. IIRC when some packet sniffing was done there was something like reconnects/timeouts happening at the protocol level in this thread but that was some time ago and might not remember correctly.
  22. I ended up moving everything to a VM on unraid and it has been a lot more stable since then. Although I also can't get a few to re-sync. Almost made it to 1 chia farmed, at this point really thinking about calling it quits once I reach that point. Already killed one SSD due to chia. With all the forks running, I am seeing ~400gb/day of writes ONLY farming. Total profit after 6 months of farming it like $250 with all the forks combined. VS mining on a single 3070 making $150 a month. Chia farming is just not making a lot of sense, all things considered it is hardly paying for the power usage in my case (~500w all combined)
  23. I am embarrassed that I didn't include this in the OP lol. Don't feel too bad, I setup a new docker the other day and forgot to do this as well and took me longer then it should have to figure out the issue.
  24. Was doing some more troubleshooting but since I have no idea how or why this works I am out of my depth. I did find this error in the syslog when clicking on the cpu power button though. nginx: 2021/10/22 13:11:56 [error] 15209#15209: *138612 open() "/usr/local/emhttp/script" failed (2: No such file or directory) while sending to client, client: 192.168.x.xxx, server: xxx, request: "GET /script HTTP/2.0", host: "xxxxxxx.xxxxx", referrer: "https://xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" I added the XXX's, the IP's and addresses were correct though. It seems to be looking for the script in "/usr/local/emhttp/script" instead of /usr/local/emhttp/plugins/myscript/script.page? No idea where to go from here.
  25. Ok, here is the script.page file: Menu="Tasks:94" Name="CPU Power" Type="xmenu" Tabs="true" Code="e942" and the cpu-power-switch.page file Menu="script" --- <? echo "<h1>Changing CPU Governer</h1><br><br>"; passthru("/bin/bash /boot/config/plugins/user.scripts/scripts/Power\ Governer\ switcher/script"); ?> <script>history.back();</script> I noticed that the 404 error just adds /script to the server address. aka, unraid.local/script Just confused since this all worked yesterday.