TexasUnraid
-
Posts
1,178 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by TexasUnraid
-
-
27 minutes ago, ich777 said:
Sorry I have to appologize... Completely forgot about that, will look into it on monday, already made a note on my calendar...
Sorry again...
No worries, was just not sure if I missed it.
-
On 2/25/2022 at 12:25 AM, ich777 said:
I will look into this ASAP, please give me a few days... hope that's not to late for you...
I was not sure if you had time to look at this yet? No big deal, didn't see an update so far. No worries if you have not had time.
To refresh your memory:
On 2/24/2022 at 2:32 PM, TexasUnraid said:Trying to setup your Debian-APT-Mirror docker but having an odd issue.
---Checking if UID: 99 matches user--- usermod: no changes ---Checking if GID: 100 matches user--- usermod: no changes ---Adding user: debian to www-data--- The user `debian' is already a member of `www-data'. ---Setting umask to 0000--- ---Checking for optional scripts--- ---No optional script found, continuing--- ---Starting cron--- ---Starting apache2--- ---Starting...--- ---Something went horribly wrong, can't find the mirror directory!---I have checked things over and over, I have the folder mapped to valid paths, if I manually create files in these folders, either inside the docker or on the server side, it is visible and editable from both ends.
I also manually created the mirror dir under the data folder but didn't help. It is like it is using another folder tree entirely.
I manually started apt-mirror and it ran but started filling up my docker image but I could not figure out where the files were going. It is using all default settings in the mirror.list file for now. The download itself seemed to be working fine.
-
1 minute ago, binhex said:
not yet, still doing my day job 🙂
Yeah no worries, sounded like you had it sorted so was not sure if it was an issue with it being pushed or just had not done it yet.
-
5 minutes ago, binhex said:
yeah there are some issues with ccextractor which was causing the build to fail, i have worked around it for now, not overly happy with it as it increases the image size, but hey for now i will go for the workaround.
Cool, band-aids are perfectly acceptable. lol.
I tried updating the docker but it did not pull anything, guess you have not pushed the update yet?
-
the makmkv docker is complaining that it is too old and must be updated to be used?
-
No, just a standard bridge network setup. It seems to be something about how it interacts with the drives since it always complains about sync issues when it does crash.
-
7 hours ago, ich777 said:
I will look into this ASAP, please give me a few days... hope that's not to late for you...
No worries, luckily I was getting a head start on this project so I have some time to spare.
Thanks!
-
Trying to setup your Debian-APT-Mirror docker but having an odd issue.
---Checking if UID: 99 matches user--- usermod: no changes ---Checking if GID: 100 matches user--- usermod: no changes ---Adding user: debian to www-data--- The user `debian' is already a member of `www-data'. ---Setting umask to 0000--- ---Checking for optional scripts--- ---No optional script found, continuing--- ---Starting cron--- ---Starting apache2--- ---Starting...--- ---Something went horribly wrong, can't find the mirror directory!---I have checked things over and over, I have the folder mapped to valid paths, if I manually create files in these folders, either inside the docker or on the server side, it is visible and editable from both ends.
I also manually created the mirror dir under the data folder but didn't help. It is like it is using another folder tree entirely.
I manually started apt-mirror and it ran but started filling up my docker image but I could not figure out where the files were going. It is using all default settings in the mirror.list file for now. The download itself seemed to be working fine.
-
5 minutes ago, ich777 said:
Have you actually tested if you can connect to the WebGUI?
This is not an error, this is as the message says a warning...
Nothing to worry about. Firefox is running just fine.
lol, I actually did not try the webui, sure enough it is working! thanks!
-
1
-
-
Ok, did a force update and that solved the firefox install issue but now getting a new error:
---Checking if UID: 99 matches user--- ---Checking if GID: 100 matches user--- ---Setting umask to 000--- ---Checking for optional scripts--- ---No optional script found, continuing--- ---Checking configuration for noVNC--- Nothing to do, noVNC resizing set to default Nothing to do, noVNC qaulity set to default Nothing to do, noVNC compression set to default ---Starting...--- ---Version Check--- ---Firefox not installed, installing--- ---Sucessfully downloaded Firefox--- ---Preparing Server--- ---Resolution check--- ---Checking for old logfiles--- ---Checking for old display lock files--- ---Starting TurboVNC server--- ---Preparing Server--- ---Resolution check--- ---Checking for old logfiles--- ---Checking for old display lock files--- ---Starting TurboVNC server--- ---Starting Fluxbox--- ---Starting noVNC server--- WebSocket server settings: - Listen on :8080 - Web server. Web root: /usr/share/novnc - No SSL/TLS support (no cert file) - Backgrounding (daemon) WebSocket server settings: - Listen on :8080 - Web server. Web root: /usr/share/novnc - No SSL/TLS support (no cert file) - Backgrounding (daemon) ---Starting Firefox--- [GFX1-]: glxtest: libpci missing (firefox:123): GLib-GIO-WARNING **: 07:58:18.494: Failed to execute child process “update-desktop-database” (No such file or directory) -
7 minutes ago, ich777 said:
Can you give me a screenshot from your template?
Or better speaking what language variable are you using?
Should be all default settings besides the port.
-
Been using the firefox container for some time, updated it and now I am getting an odd issue where it can't install firefox?
---Checking if UID: 99 matches user--- ---Checking if GID: 100 matches user--- ---Setting umask to 000--- ---Checking for optional scripts--- ---No optional script found, continuing--- ---Checking configuration for noVNC--- Nothing to do, noVNC resizing set to default Nothing to do, noVNC qaulity set to default Nothing to do, noVNC compression set to default ---Starting...--- ---Version Check--- ---Firefox not installed, installing--- ---Something went wrong, can't download Firefox, putting container in sleep mode---How do I figure out what went wrong or install firefox manually?
-
Ok, I am seriously confused at this point.
Server has been running great since I stopped using tartube. I have been using tubesync and just playing with it so far, downloaded 2 channels over the last few weeks and no crashes.
Then a few hours ago I added 6 more channels to download and the server crashed AGAIN now!
How in the heck is this possible? How can downloading youtube videos cause the whole system to freak out with a kernel panic no matter how it is done?
Docker, VM, it doesn't matter. It always seems to get some kind of sync error kernel panic.
The actual share setup is really basic, I have a share dedicated to youtube videos and set to only use 1 disk on the array and not to use cache. Basically as simple as it gets. I even have the docker mapped directly to the disk so it doesn't use the user share.
If only SMB performance was not so abysmally bad with unraid/linux I could use another system or a windows VM to isolate the issues hopefully.
-
The plot thickens.
I spun up an ubuntu VM and installed tartube, Started a sync and a half hour later, the server locked up just like before.
It was using the virtio share from unraid to access the files as SMB does not seem to work well.
I have no idea how it is possible for it to cause these crashes inside both a VM and docker?
Guess it is time to try tubesync. Does anyone know if it has the Ability to use a proxy/vpn so that my main IP does not get throttled?
Edit: Installed tubesync, really liking it so far, doing some test downloads now.
Just need to figure out the VPN/proxy issue as it tends to get throttled when checking as many channels as I have and it is really annoying if it is your main IP.
-
6 hours ago, hernandito said:
I am a Kodi guy as well. When you add the new library, what category do you use? I see that NFO’s are created. I am really liking this whole thing. Thanks.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.
-
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.
-
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.
-
1
-
-
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……
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.
-
2 minutes ago, JonathanM said:
Have you tried youtubedl-material recently? You are describing exactly what I use.
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?
-
7 hours ago, ich777 said:
Already looked at it but they don't tell much...
Can't remember but have we talked about tubesync or MeTube in the past? These should be similar applications that have actually a real WebGUI.
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.
-
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
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.
-
@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.
-
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.
-
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.
[Support] ich777 - Application Dockers
in Docker Containers
Posted · Edited by TexasUnraid
Great, that got it working!