[Request] TarTube GUI docker container?


Recommended Posts

Tartube is the only youtube downloader I have found that allows you to download a channel AND select the quality of the downloaded videos (sorry, the kids do not need massive 4k videos taking up space on the drive, 720p is just fine for them lol).

 

It is also a very feature rich downloader in it's own right as well. The channel watch feature is quite nice. A perfect candidate for a home server IMHO.

 

I have stumbled through trying to make a GUI docker a few times with mixed results. Before I make a mess of it I was wondering if anyone else is interested in doing it properly?

 

https://github.com/axcore/tartube

Edited by TexasUnraid
Link to comment

I am using the unraid CA docker for that program and this is all I get:

 

firefox_xa6hfNbeNv.jpg.06c5cfc2eaef87adf80ff43cf0355d1d.jpg

 

I have like 6 or 7 dockers installed right now that download youtube and none of them let me select the quality sadly. 😪

 

Also after trying tartube on windows, it really is a step ahead of the rest as well would seem to make a good candidate for a docker.

Link to comment
5 minutes ago, jonathanm said:

The dialog you are showing is for 1 off downloads, the subscription / playlist dialog has other options.

 

Very interesting, the UI was too simple and I didn't even notice it had another area for downloads. Testing it now. Thanks for the heads up!

 

I still think that tartube would make for a good docker though, in my quick testing of it I really liked the feature set and options compared to this one. Also more intuitive.

Link to comment

Just finished the test and while it did seem to limit the quality to 720p, it also downloaded a few videos in as little as 240p strangly.

 

It is VERY slow though compared to when I ran the same test with tartube.

 

Worst case I guess I could spin up a VM just for tartube, seems like a waste though lol.

Link to comment
8 hours ago, TexasUnraid said:

I have stumbled through trying to make a GUI docker a few times with mixed results. Before I make a mess of it I was wondering if anyone else is interested in doing it properly?

...looks like there is no docker available anywhere.

The App comes in a .deb flavour, so you should be able to install it in a GUI Docker.

Did you try the Debian Buster from @ich777?

You should be able to download und and install the "tartube.deb" semi-automatic with a user.sh script every time the docker starts, as per the hint/instructions given in the docker, see:

If you want to install some other application you can do that by creating a user.sh
and mounting it to the container to /opt/scripts/user.sh (a standard bash script should do the trick).

[...]

Storage Note: All things that are saved in the container should be in the home or a subdirectory in your homefolder,
all files that are store outside your homefolder are not persistant and will be wiped if there is an update of the container
or you change something in the template.

 

just get you to see, that the path where tartube stores its config is mapped somewhere. outside, like /mnt/user/appdata/tartube....this should give you a start.

Edited by Ford Prefect
  • Like 1
  • Thanks 1
Link to comment
1 hour ago, Ford Prefect said:

The App comes in a .deb flavour, so you should be able to install it in a GUI Docker.

Works just fine in my Debian Bullseye container, but I recommend doing it with my Debian Buster container:

grafik.thumb.png.512e85e46ed559010ccc64a5da16f063.png

 

Of course you have to install python3, all dependencies manually and afterwards install tartube with dpgk (to gain root privileges in my container you have to type in "su" and then the specified password for your root user).

Since tartube creates a directory for all the files in ~/.config/tartube, the config from tartube is persistant. The only thing that I would do is to create a user.sh like @Ford Prefect mentioned above so that the container checks on every start/restart if tartube is actually installed and the needed dependencies.

 

You can of course add another directory to the template where you store your downloads from YT.

 

Looks like it's working perfectly fine:

grafik.thumb.png.35a2513c2dd69078962205d175680079.png

  • Like 1
  • Thanks 1
Link to comment

Very interesting, I remember trying out the buster docker at one point but it said it was a beta so I just kinda forgot about it figuring it still had bugs that needed to be worked out.

 

Is it out of beta now? If so then that could be a game changer for me as I could create GUI dockers based on it quite easily. Not as lightweight as a dedicated docker but should work.

 

I suppose that I could have the user.sh script start the GUI program automatically as well so that it could start watching the channels without having to manually enter the container?

 

What is the difference between the buster and bullseye containers besides the version?

Link to comment
3 hours ago, TexasUnraid said:

Very interesting, I remember trying out the buster docker at one point but it said it was a beta so I just kinda forgot about it figuring it still had bugs that needed to be worked out.

I leave some containers long at a Beta state because they never fell really finished to me... :P

 

3 hours ago, TexasUnraid said:

Is it out of beta now?

You can safely use it, I use it on a daily basis and also have writen many containers and plugins in it... ;)

 

3 hours ago, TexasUnraid said:

I suppose that I could have the user.sh script start the GUI program automatically as well so that it could start watching the channels without having to manually enter the container?

I think so, I'm not really familiar how this application works.

 

3 hours ago, TexasUnraid said:

What is the difference between the buster and bullseye containers besides the version?

Buster = Debian 10 based | Bullseye = Debian 11 based (since it's not really released it's really a beta, from what I know the official release is on 18th August)

  • Thanks 1
Link to comment
51 minutes ago, TexasUnraid said:

Cool, thanks for the info! Guess I will go about getting that setup.

Anyways, you can also try Bullseye but keep in mind that I update the container after a few days after the official release from Bullseye to be on the latest packages.

 

EDIT: Maybe I'm releasing a Bullseye container with KDE Plasma, don't know if it's worth it because I like function over looks... ;)

Link to comment

Ok, trying to setup the tartube in buster, took a bit to get all the dependencies sorted out but it seems to be working now.

 

This issue now is that the user.sh script does not seem to be able to start tartube?

 

If I run the script manually it starts it up perfectly but when I restart the container it does not?

 

edit: after some trial and error I figured out part of the problem was that the user.sh script is run before the desktop is started. I tried to work around that by starting another script with a delay but that also failed for some reason.

 

So I ended up using the built in startup option in debian and that seems to work.

Edited by TexasUnraid
Link to comment
  • 6 months later...

@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.

Link to comment
6 minutes ago, TexasUnraid said:

I have some of the errors screen shotted if you want them.

Sure, send them over please.

 

6 minutes ago, TexasUnraid said:

I was not aware this was even possible with how docker is setup?

A container can also crash the host if something goes terribly wrong... The best example is check_mk2.0

 

6 minutes ago, TexasUnraid said:

Is it possible to make a tartube docker

Have to look into this...

 

EDIT: I also have to say that the Buster container is now outdated and the Bullseye container should be used, you can simply switch the repository in the template and everything should work right OOB.

Link to comment
8 minutes ago, ich777 said:

Sure, send them over please.

 

A container can also crash the host if something goes terribly wrong... The best example is check_mk2.0

 

Have to look into this...

 

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

 

firefox_2AYveaSWfZ.jpg.c4adbfd4edc117a52db5fc241e3482bf.jpg

 

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.

 

vmware_gk2itEN59q.jpg.0d738e26c48e79fb81af04360be6985c.jpg

 

vmware_kDEEvXjc0A.jpg.6a4317994a78a71606c22d6686edfb00.jpg

 

vmware_npEZr6yonk.jpg.5ee6b1bf3f9fc46a6d72b27a1343c6bf.jpg

 

vmware_IBpP8EnRBt.jpg.d175c78979f2d3588d40f1a29d349c8e.jpg

 

vmware_iBnjYlBjLv.jpg.a2d63b47900ff04ccf168e0f828901be.jpg

 

vmware_WF5bo2nigp.jpg.46be5ce0d15f8caa4d976a221857a3c7.jpg

 

I have more if you think they would help.

 

Edited by TexasUnraid
Link to comment
18 minutes ago, hernandito said:

In reading about Tartube, it says it’s a front end for YouTube-dl. There already dockers for this. Wondering if it could be added to one of the existing Dockers…… 

 

 

D94262FE-6748-43B5-8FC0-E7254F45DEE6.jpeg

 

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.

Link to comment
4 hours ago, TexasUnraid said:

 

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.

 
looks interesting…. Not sure if I have a need for this. I usually watch YouTube videos in a random way on my tablet.  I once downloaded a full concert to use on my htpc box. I would love to hear use case scenarios….

 

 

Link to comment

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.

  • Like 1
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.