subagon

Members
  • Posts

    58
  • Joined

  • Last visited

Everything posted by subagon

  1. Just update qbittorrentvpn (June 11) and it's not working. Most of the UI is missing and what is there doesn't respond. All my torrents that were listed are no longer displayed, but they exist on the filesystem. Can I fall back to the prior version? I don't see a version variable on the edit screen. I checked at docker.com and the container was updated 3 hours ago. The log file looked ok, no obvious errors.
  2. Two weeks and the system hasn't crashed. So I'm going to assume that removing all IPs from br0 and moving them to "bridge" has stabilized the server. Next I'll re-IP all my dockers back to br0 but adding a VLAN as described above. I hope Lime Tech addresses this issue in a future release so that this workaround isn't necessary.
  3. Update: For troubleshooting I have either shutdown or migrated all dockers from the "br0" to "bridge". I also upgrade back to 6.9.2 (from 6.9.1) since this issue seems to effect both 6.9.1 & 6.9.2. if this works, I'll likely use a VLAN as described in the links above. I'll see how long the system stays up. If I don't make any further updates to this thread after 2 weeks, assume that the problem is solved.
  4. JorgeB, Thanks for the info. I'll give it try and move my br0 connections over to a VLAN. I looked at my syslog and found this from this morning, but the server has not crashed since yesterday. May 17 07:59:41 asok kernel: ------------[ cut here ]------------ May 17 07:59:41 asok kernel: WARNING: CPU: 15 PID: 0 at net/netfilter/nf_conntrack_core.c:1120 __nf_conntrack_confirm+0x9b/0x1e6 May 17 07:59:41 asok kernel: Modules linked in: vhost_net tun vhost vhost_iotlb tap kvm_intel kvm iptable_raw wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libblake2s blake2s_x86_64 libblake2s_generic libchacha veth xt_CHECKSUM ipt_REJECT ip6table_mangle ip6table_nat iptable_mangle macvlan xt_nat xt_MASQUERADE iptable_nat nf_nat xfs md_mod nct7904 watchdog ip6table_filter ip6_tables iptable_filter ip_tables igb i2c_algo_bit ipmi_ssif sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd mpt3sas i2c_i801 i2c_smbus input_leds glue_helper rapl intel_cstate i2c_core ahci led_class raid_class intel_uncore acpi_ipmi libahci scsi_transport_sas wmi ipmi_si acpi_pad button [last unloaded: kvm] May 17 07:59:41 asok kernel: CPU: 15 PID: 0 Comm: swapper/15 Not tainted 5.10.21-Unraid #1 May 17 07:59:41 asok kernel: Hardware name: Supermicro X9DRD-7LN4F(-JBOD)/X9DRD-EF/X9DRD-7LN4F, BIOS 3.3 08/23/2018 May 17 07:59:41 asok kernel: RIP: 0010:__nf_conntrack_confirm+0x9b/0x1e6 May 17 07:59:41 asok kernel: Code: e8 64 f9 ff ff 44 89 fa 89 c6 41 89 c4 48 c1 eb 20 89 df 41 89 de e8 d5 f6 ff ff 84 c0 75 bb 48 8b 85 80 00 00 00 a8 08 74 18 <0f> 0b 89 df 44 89 e6 31 db e8 5d f3 ff ff e8 30 f6 ff ff e9 22 01 May 17 07:59:41 asok kernel: RSP: 0018:ffffc900066e08a8 EFLAGS: 00010202 May 17 07:59:41 asok kernel: RAX: 0000000000000188 RBX: 0000000000003c05 RCX: 00000000b0e84f5c May 17 07:59:41 asok kernel: RDX: 0000000000000000 RSI: 0000000000000061 RDI: ffffffff820099c4 May 17 07:59:41 asok kernel: RBP: ffff888179d86f00 R08: 00000000fac24da6 R09: ffff8888a1211ae0 May 17 07:59:41 asok kernel: R10: 0000000000000158 R11: ffff8884a537f200 R12: 0000000000008461 May 17 07:59:41 asok kernel: R13: ffffffff8210db40 R14: 0000000000003c05 R15: 0000000000000000 May 17 07:59:41 asok kernel: FS: 0000000000000000(0000) GS:ffff88885fc40000(0000) knlGS:0000000000000000 May 17 07:59:41 asok kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 May 17 07:59:41 asok kernel: CR2: 000014faebee29f8 CR3: 000000000200c006 CR4: 00000000001706e0 May 17 07:59:41 asok kernel: Call Trace: May 17 07:59:41 asok kernel: <IRQ> May 17 07:59:41 asok kernel: nf_conntrack_confirm+0x2f/0x36 May 17 07:59:41 asok kernel: nf_hook_slow+0x39/0x8e May 17 07:59:41 asok kernel: nf_hook.constprop.0+0xb1/0xd8 May 17 07:59:41 asok kernel: ? ip_protocol_deliver_rcu+0xfe/0xfe May 17 07:59:41 asok kernel: ip_local_deliver+0x49/0x75 May 17 07:59:41 asok kernel: ip_sabotage_in+0x43/0x4d May 17 07:59:41 asok kernel: nf_hook_slow+0x39/0x8e May 17 07:59:41 asok kernel: nf_hook.constprop.0+0xb1/0xd8 May 17 07:59:41 asok kernel: ? l3mdev_l3_rcv.constprop.0+0x50/0x50 May 17 07:59:41 asok kernel: ip_rcv+0x41/0x61 May 17 07:59:41 asok kernel: __netif_receive_skb_one_core+0x74/0x95 May 17 07:59:41 asok kernel: netif_receive_skb+0x79/0xa1 May 17 07:59:41 asok kernel: br_handle_frame_finish+0x30d/0x351 May 17 07:59:41 asok kernel: ? ipt_do_table+0x570/0x5c0 [ip_tables] May 17 07:59:41 asok kernel: ? br_pass_frame_up+0xda/0xda May 17 07:59:41 asok kernel: br_nf_hook_thresh+0xa3/0xc3 May 17 07:59:41 asok kernel: ? br_pass_frame_up+0xda/0xda May 17 07:59:41 asok kernel: br_nf_pre_routing_finish+0x23d/0x264 May 17 07:59:41 asok kernel: ? br_pass_frame_up+0xda/0xda May 17 07:59:41 asok kernel: ? br_handle_frame_finish+0x351/0x351 May 17 07:59:41 asok kernel: ? nf_nat_ipv4_in+0x1e/0x4a [nf_nat] May 17 07:59:41 asok kernel: ? br_nf_forward_finish+0xd0/0xd0 May 17 07:59:41 asok kernel: ? br_handle_frame_finish+0x351/0x351 May 17 07:59:41 asok kernel: NF_HOOK+0xd7/0xf7 May 17 07:59:41 asok kernel: ? br_nf_forward_finish+0xd0/0xd0 May 17 07:59:41 asok kernel: br_nf_pre_routing+0x229/0x239 May 17 07:59:41 asok kernel: ? br_nf_forward_finish+0xd0/0xd0 May 17 07:59:41 asok kernel: br_handle_frame+0x25e/0x2a6 May 17 07:59:41 asok kernel: ? br_pass_frame_up+0xda/0xda May 17 07:59:41 asok kernel: __netif_receive_skb_core+0x335/0x4e7 May 17 07:59:41 asok kernel: ? __update_load_avg_cfs_rq+0xd6/0x18f May 17 07:59:41 asok kernel: __netif_receive_skb_list_core+0x78/0x104 May 17 07:59:41 asok kernel: netif_receive_skb_list_internal+0x1bf/0x1f2 May 17 07:59:41 asok kernel: ? dev_gro_receive+0x55d/0x578 May 17 07:59:41 asok kernel: gro_normal_list+0x1d/0x39 May 17 07:59:41 asok kernel: napi_complete_done+0x79/0x104 May 17 07:59:41 asok kernel: igb_poll+0xc9a/0xec8 [igb] May 17 07:59:41 asok kernel: ? do_send_sig_info+0x63/0x86 May 17 07:59:41 asok kernel: net_rx_action+0xf4/0x29d May 17 07:59:41 asok kernel: __do_softirq+0xc4/0x1c2 May 17 07:59:41 asok kernel: asm_call_irq_on_stack+0x12/0x20 May 17 07:59:41 asok kernel: </IRQ> May 17 07:59:41 asok kernel: do_softirq_own_stack+0x2c/0x39 May 17 07:59:41 asok kernel: __irq_exit_rcu+0x45/0x80 May 17 07:59:41 asok kernel: common_interrupt+0x119/0x12e May 17 07:59:41 asok kernel: asm_common_interrupt+0x1e/0x40 May 17 07:59:41 asok kernel: RIP: 0010:arch_local_irq_enable+0x7/0x8 May 17 07:59:41 asok kernel: Code: 00 48 83 c4 28 4c 89 e0 5b 5d 41 5c 41 5d 41 5e 41 5f c3 9c 58 0f 1f 44 00 00 c3 fa 66 0f 1f 44 00 00 c3 fb 66 0f 1f 44 00 00 <c3> 55 8b af 28 04 00 00 b8 01 00 00 00 45 31 c9 53 45 31 d2 39 c5 May 17 07:59:41 asok kernel: RSP: 0018:ffffc900063fbea0 EFLAGS: 00000246 May 17 07:59:41 asok kernel: RAX: ffff88885fc62380 RBX: 0000000000000004 RCX: 000000000000001f May 17 07:59:41 asok kernel: RDX: 0000000000000000 RSI: 00000000313b14ef RDI: 0000000000000000 May 17 07:59:41 asok kernel: RBP: ffffe8f7ff47f700 R08: 00002a9d58969783 R09: 0000000000000000 May 17 07:59:41 asok kernel: R10: 000000000000f71a R11: 071c71c71c71c71c R12: 00002a9d58969783 May 17 07:59:41 asok kernel: R13: ffffffff820c7ec0 R14: 0000000000000004 R15: 0000000000000000 May 17 07:59:41 asok kernel: cpuidle_enter_state+0x101/0x1c4 May 17 07:59:41 asok kernel: cpuidle_enter+0x25/0x31 May 17 07:59:41 asok kernel: do_idle+0x1a6/0x214 May 17 07:59:41 asok kernel: cpu_startup_entry+0x18/0x1a May 17 07:59:41 asok kernel: secondary_startup_64_no_verify+0xb0/0xbb May 17 07:59:41 asok kernel: ---[ end trace eaf4c384b8419f52 ]--- I report back after I get the VLAN setup and dockers moved over to it. Mike
  5. My server has been kernel panicing every 2-3 days since mid-April. It panicked 3 times today alone. I'm looking for any help I can get. History and steps so far... Problems started about 10 days after I upgraded to 6.9.2. I searched the forum and redit and found other "not syncing" type problems. One some were at boot and the solution seems to be replacing the USB flash drive. My server has never failed to boot, so I have discounted the USB flash drive as the problem. The second type I found was bad RAM. My server has 64G of RAM on 4 DIMMs. I removed 32G and ran the server until it panicked within 2 days. I then swapped the RAM and again within 2 days the server panicked. So I think I can assume the RAM is okay. I've also downgraded to 6.9.1 thinking maybe 6.9,2 was the problem. Again, the server panicked within a few days. BTW, I'm still on 6.9.1. Since the server panics, I don't have much in the way of logs, etc. I do have screenshots of the IPMI console and they all look very similar. I've not made any major, or minor really, changes to the server prior to the panics. The system has been running well for years. I'm starting to think the problem is hardware based since switching unRAID versions and few changes prior to the panics would rule out software. After the second (of three) crashes today I change the Tunable (md_sync_limit) from the default setting of "5" to "10". This was a wild guess at trying to solve this problem. It's the only parameter I could find that has "sync" in it. I couldn't find any documentation on this parameter either. Changing the value to "10" doesn't seem to have helped since the server has since crashed. Since the panics have started the server has been in almost constant parity check status. So much so I've had 2 drive die. I can't be sure the constant parity checks killed them, but I'm sure it didn't help either. It took more than a week, but I was able to replace the 2 dead drives between panics. I also upgraded my parity drives from 10G to 18G and used the old 10G parity drives to replace the dead drives. For now I'm canceling parity checks since the server has crashed 3 times in just one day. I also stopped all but a few dockers and no VM's. Attached are my diagnostic files and a screenshot of the console after a panic. Any help will be welcome, Mike asok-diagnostics-20210516-1950.zip
  6. SOLVED: See below When thru all the install steps and have UUD kind of working. Biggest problem is getting Varken to connect to Tautulli and Sonarr. Here's the errors I get in the Varken log. 2021-04-03 01:10:30 : INFO : __init__ : Running job Every 30 seconds do thread(<bound method TautulliAPI.get_activity of <tautulli-1>>) (last run: 2021-04-03 01:10:00, next run: 2021-04-03 01:10:30) 2021-04-03 01:10:30 : DEBUG : connectionpool : Starting new HTTP connection (8): ********.1.37:8181 2021-04-03 01:10:33 : ERROR : helpers : Cannot resolve the url/ip/port. Check connectivity. Error: HTTPConnectionPool(host='192.168.1.37', port=8181): Max retries exceeded with url: /api/v2?apikey=xxxxxxxxxxxxxxxxxxxxxxx&cmd=get_activity (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x14a1e06afa90>: Failed to establish a new connection: [Errno 113] Host is unreachable')) 2021-04-03 01:13:03 : ERROR : helpers : Cannot resolve the url/ip/port. Check connectivity. Error: HTTPConnectionPool(host='192.168.1.37', port=8181): Max retries exceeded with url: /api/v2?apikey=xxxxxxxxxxxxxxxxxxx&cmd=get_activity (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x14a1e06943a0>: Failed to establish a new connection: [Errno 113] Host is unreachable')) Note: I've x'ed out the API key. Here's the varken.ini file. [global] sonarr_server_ids = 1 tautulli_server_ids = 1 maxmind_license_key = xxxxxxxxxxxxxxxxxxx [influxdb] url = 192.168.1.2 port = 8086 ssl = false verify_ssl = false username = telegraf password = metricsmetricsmetricsmetrics [tautulli-1] url = 192.168.1.37:8181 fallback_ip = 1.1.1.1 apikey = xxxxxxxxxxxxxxxxxxx ssl = false verify_ssl = false get_activity = true get_activity_run_seconds = 30 get_stats = true get_stats_run_seconds = 3600 [sonarr-1] url = 192.168.1.131:8989 apikey = xxxxxxxxxxxxxxxxxxx ssl = false verify_ssl = false missing_days = 7 missing_days_run_seconds = 300 future_days = 1 future_days_run_seconds = 300 queue = true queue_run_seconds = 300 Checked all setting many times. Either I'm missing something or overlooked a setting. Both Tautulli and Sonarr have been running for years and I verified both were running. Even restarted them several times. SOLVED: I followed the install instructions in the "Technically Speaking" YouTube videos. He setup his Varken docker with a "Bridge" network type. Not sure why, but this did not work for my setup. I tried "Host" and that failed too. So I used a custom interface, "br0" and gave the docker it's own IP address and now it's conneted to both Tautulli and Sonarr. If I had to guess why this happened is because most of my dockers are setup to use a different IP address from my UnRAID server.
  7. I'm having the same issue. I downgraded to 4.2.1-1-05 but I'm still getting the errors messages you listed above.
  8. Djoss, Thanks for setting me on the correct path. I swear I had turned on advanced setting, but obviously didn't.
  9. Is there any way to increase the size of the QDirStat window? I use another docker, MKVToolNix, which has two docker variables to adjust the screen size. They are, DISPLAY_WIDTH & DISPLAY_HEIGHT. I tried adding these to the QDirStat docker but it didn't cause any change.
  10. The third one you listed is what I'm using now and listed is a few of my previous post in this thread. The fourth one is very old and I contacted the author but they didn't seem to be interested in maintaining the code any longer. I'll need to look at the first two to see if the json layout is the same as the layout from youtube-dl, but as of now the YouTube-Agent.bundle works well for me as long as I follow the naming rules required by it. As I said earlier, my biggest problem is I don't have the ability to automate the addition of a sequence number to the downloaded files (s2019e23), record the sequence number and increment it for the next file from the youtube channel. I think I requested this feature in an earlier post.
  11. That will be great. This agent is very picky and I don't think the author is actively supporting it any longer. So are you saying goautoyt will interface with Plex in order to scrape metadata? I know youtube-dl can save thumbnails and metadata to a json file, but that doesn't get the metadata into Plex and I couldn't fine a Plex Library Agent that imports metadata from a json file.
  12. I use this Plex Library Agent to scrape youtube metadata, https://github.com/ZeroQI/YouTube-Agent.bundle It works fine, but is very picky about how you name your files and directories. Example file naming, The directory must match the name of the channel plus the channel ID in brackets. Each episode must have a sequence number to work with Plex, the numbers are up to you. I normally use the year followed by an episode number I make up. I add the episode title, not sure if it's required, plus the youtube episode ID in brackets (required). The agent uses the ID's and channel name to find and scrape the metadata. One more thing, you can't place the episode files in subdirectories, it breaks the library agent. Example screenshot of a youtube video with scraped metadata.
  13. Okay, I understand. But if go-auto-yt is using youtube-dl to download the files and youtube-dl can deal with spaces, then isn't it a matter of how the filename string is passed from go-auto-yt to youtube-dl? Please understand that I have no idea of what your code looks like and I'm just guessing.
  14. I'm afraid I don't understand your reply. If I run the youtube-dl command directly; youtube-dl -f best -ciw -o "%(upload_date)s %(title)s [%(id)s].%(ext)s" -v youtube-URL <-- note the spaces in the filename It works fine. In your example above I notice you didn't quote the filename string. Could that be the difference? The only reason I care about the spaces is the Plex Library Agent I'm using to scrape the metadata is very strict in how the file is named, underscores break it. If necessary I can use a second process, likely filebot, to change the names.
  15. Bug report... If I enter the following string in "Enter custom youtube-dl output" and click "Add channel and download" I get an error after a few seconds. /Kurzgesagt [UCsXVk37bltHxD1rDPwtNM8Q]/%(release_date)s %(title)s [%(id)s].%(ext)s If I replace the spaces with underscores, it works.
  16. Putting this here for anyone interested. This is my channels.json file. I'm editing it by hand instead of using the GUI for now. You can use any of the youtube-dl tags defined here; https://github.com/ytdl-org/youtube-dl/blob/master/README.md#output-template So far I've added the Youtube video ID to each filename. Still working on a way to add a seq #; e.g. s2019e05, s03e10, etc. [ { "URL": "https://www.youtube.com/channel/UC2LVhJH_9cT2XKp0VAfsKOQ", "LatestDownloaded": "y8iCbjNGKlE", "DownloadMode": "Video And Audio", "Name": "Uploads from The Tim Traveller", "PreferredExtensionForAudio": "", "PreferredExtensionForVideo": "any", "DownloadHistory": [ "y8iCbjNGKlE" ], "LastChecked": "12-08-2019 16:17:51", "CheckingInterval": "15", "Type": "Channel", "DownloadPath": "/%(uploader)s_[UC2LVhJH_9cT2XKp0VAfsKOQ]/%(title)s_[%(id)s].%(ext)s" }, { "URL": "https://www.youtube.com/channel/UCuxpxCCevIlF-k-K5YU8XPA", "LatestDownloaded": "IzLQlkmk5ps", "DownloadMode": "Video And Audio", "Name": "Uploads from Scotty Kilmer", "PreferredExtensionForAudio": "", "PreferredExtensionForVideo": "any", "DownloadHistory": [ "IzLQlkmk5ps" ], "LastChecked": "12-08-2019 16:17:57", "CheckingInterval": "15", "Type": "Channel", "DownloadPath": "/%(uploader)s_[UCuxpxCCevIlF-k-K5YU8XPA]/%(title)s_[%(id)s].%(ext)s" } ]
  17. Very happy to see this. I'd been looking for something like this too. I started to write a script (frontend for youtube_dl) to do something like this but never had the time to finish it. I'd like to suggest some features. The ability to customize the downloaded file names. I put youtube videos on my Plex server and manually assign a season and episode number to each filename, ex. The Tim Traveller [UC2LVhJH_9cT2XKp0VAfsKOQ]/s2018e01 Peak Quest - Climbing The Highest Point In All 48 Counties of England [rNkbRjb7YDY] I wanted to do something like... {Channel Name} [{youtube channel ID}]/sYYYYe## {Video Title} [{youtube video ID}].{ext} The trick would how to resolve the episode number for each download. I was going to keep a text file with the next episode number for each monitored channel. Also option to download entire channel newest to oldest or oldest to newest. Oldest to newest would be to default option if there was automated season/episode numbering. I needed the option to add the channel ID and video ID as part of the file name. I Need this to scrape the metadata, see below. I then use this Plex Library Agent to scrape all the metadata for each video, https://github.com/ZeroQI/YouTube-Agent.bundle This is really nice. It grabs the titles, dates, descriptions, thumbnails, etc. For this Agent to work correctly, the files must be named as shown above. EDIT: Messed around with the JSON file and was able to include the video id as follows; %(title)s_[%(id)s].%(ext)s Tried to use the GUI, but it resulted in a messed up filename, I think it was something like this; %(title)s_[%(id)s].%(ext)s.%(title)s.%(ext)s Still working on adding the seq # i.e. sYYYYe##
  18. Thanks, I try putting sonarr on an ip other than the unRaid server's ip. Update: That seems to have fixed it. Only issue was I had to re-ip several dockers off of the unRaid server ip to get sonarr talking to all of them (sabnzbd,deluge,jackett,nzbhydra2). I guess the lesson learned is to give each docker it's own ip and not share it with unRaid.
  19. I've been using pihole running on a raspberry pi for a few months and no problems. I migrated over to this docker but have a problem. My sonarr docker is no longer unable to resolve dns lookups. The sonarr docker is running on 192.168.1.2 (same as the unraid server) and pihole is on 192.168.1.10 (same ip I was using when running on raspberry pi). No other docker is using port 53 or 67. If I shutdown the pihole docker and restart the raspberry pi, sonarr starts resolving dns again. I feel like I'm missing something basic... Ideas?
  20. Been about a week since my last post and no crashes. I'm hoping that's the problem has been fixed. I've made a few changes, so I can't be sure what fixed it. I assume it was either one of the unRAID updates or replacing a failing/dead drive. I have been having a lot of problems with samba on my Mac, but don't think it's related and I'll start another thread for that topic.
  21. Just installed netdata and looking at the options and settings. I wonder how do you display the /proc/mdstat report/plugin? I looked in the conf file but didn't see any reference to mdstat. It does appear that the plugin is installed as part of the netdata package and docker.
  22. Quick update... My system has been somewhat stable since my last post (about a week). During that time I've had a few other issues that may or may not be related to the kernel panics. Fist, I had a drive go bad and had to replace it. I can't say if the drive problem was because of the numerous crashes (unlikely), or if the drive was causing the panics, or unrelated. I've also updated to 6.6.3. I've seen some error messages in the syslog that seem to be related to the age of the motherboard BIOS, so a BIOS update is needed. I'm also having a lot of problems with samba on my Mac desktop. I don't think it's unRAID since my Windows desktop isn't having any samba problems. I'll need to start a new thread because the samba/Mac is becoming unusable. I do see that's it's possible the Mac might be causing the kernel panics. Because of this, I've been unmounting any samba share on the Mac when not in use. Right now I'm in the middle of rebuilding the lost drive from parity so I'm trying to do as little as possible on the system as not to cause a crash.
  23. Thank you for the information. I'll investigate the dockers with custom IPs.
  24. No crash to report since the last post. Since then I have updated to 6.6.2 and kept an open terminal tailing /var/log/syslog. I just saw this from 30 minutes ago. It did not cause a kernel panic/crash but looked like it might provide a clue. Oct 25 13:59:54 asok kernel: WARNING: CPU: 15 PID: 20898 at net/netfilter/nf_conntrack_core.c:763 __nf_conntrack_confirm+0x96/0x4fc Oct 25 13:59:54 asok kernel: Modules linked in: macvlan xt_nat veth xt_CHECKSUM iptable_mangle ipt_REJECT ebtable_filter ebtables ip6table_filter ip6_tables vhost_net tun vhost tap ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat xfs md_mod nct7904 igb i2c_algo_bit sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd cryptd ipmi_ssif mpt3sas glue_helper i2c_i801 i2c_core intel_cstate intel_uncore ahci intel_rapl_perf libahci raid_class scsi_transport_sas pcc_cpufreq wmi ipmi_si button [last unloaded: i2c_algo_bit] Oct 25 13:59:54 asok kernel: CPU: 15 PID: 20898 Comm: kworker/15:1 Tainted: G W 4.18.14-unRAID #1 Oct 25 13:59:54 asok kernel: Hardware name: Supermicro X9DRD-7LN4F(-JBOD)/X9DRD-EF/X9DRD-7LN4F, BIOS 3.0 07/09/2013 Oct 25 13:59:54 asok kernel: Workqueue: events macvlan_process_broadcast [macvlan] Oct 25 13:59:54 asok kernel: RIP: 0010:__nf_conntrack_confirm+0x96/0x4fc Oct 25 13:59:54 asok kernel: Code: c1 ed 20 89 2c 24 e8 26 f7 ff ff 8b 54 24 04 89 ef 89 c6 41 89 c5 e8 bc f8 ff ff 84 c0 75 b9 49 8b 86 80 00 00 00 a8 08 74 02 <0f> 0b 4c 89 f7 e8 04 ff ff ff 49 8b 86 80 00 00 00 0f ba e0 09 73 Oct 25 13:59:54 asok kernel: RSP: 0018:ffff88085f443d30 EFLAGS: 00010202 Oct 25 13:59:54 asok kernel: RAX: 0000000000000188 RBX: ffff8801986ede00 RCX: 0000000000000101 Oct 25 13:59:54 asok kernel: RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffffffff81e09070 Oct 25 13:59:54 asok kernel: RBP: 000000000000b1af R08: 00000000c8ff4e01 R09: 0000000000000000 Oct 25 13:59:54 asok kernel: R10: 0000000000000098 R11: 0000000000000001 R12: ffffffff81e8cc80 Oct 25 13:59:54 asok kernel: R13: 000000000000729c R14: ffff8805f75e9a40 R15: ffff8805f75e9a98 Oct 25 13:59:54 asok kernel: FS: 0000000000000000(0000) GS:ffff88085f440000(0000) knlGS:0000000000000000 Oct 25 13:59:54 asok kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Oct 25 13:59:54 asok kernel: CR2: 0000153b5c810000 CR3: 0000000001e0a003 CR4: 00000000001606e0 Oct 25 13:59:54 asok kernel: Call Trace: Oct 25 13:59:54 asok kernel: <IRQ> Oct 25 13:59:54 asok kernel: ipv4_confirm+0xaf/0xb7 [nf_conntrack_ipv4] Oct 25 13:59:54 asok kernel: nf_hook_slow+0x37/0x96 Oct 25 13:59:54 asok kernel: ip_local_deliver+0xa7/0xd5 Oct 25 13:59:54 asok kernel: ? inet_del_offload+0x3e/0x3e Oct 25 13:59:54 asok kernel: ip_rcv+0x2dc/0x317 Oct 25 13:59:54 asok kernel: ? ip_local_deliver_finish+0x1aa/0x1aa Oct 25 13:59:54 asok kernel: __netif_receive_skb_core+0x6b2/0x740 Oct 25 13:59:54 asok kernel: ? kmem_cache_free_bulk+0x25b/0x273 Oct 25 13:59:54 asok kernel: process_backlog+0x7e/0x116 Oct 25 13:59:54 asok kernel: net_rx_action+0x10b/0x274 Oct 25 13:59:54 asok kernel: __do_softirq+0xce/0x1c8 Oct 25 13:59:54 asok kernel: do_softirq_own_stack+0x2a/0x40 Oct 25 13:59:54 asok kernel: </IRQ> Oct 25 13:59:54 asok kernel: do_softirq+0x4d/0x59 Oct 25 13:59:54 asok kernel: netif_rx_ni+0x1c/0x22 Oct 25 13:59:54 asok kernel: macvlan_broadcast+0x10f/0x153 [macvlan] Oct 25 13:59:54 asok kernel: ? __switch_to_asm+0x34/0x70 Oct 25 13:59:54 asok kernel: macvlan_process_broadcast+0xd5/0x131 [macvlan] Oct 25 13:59:54 asok kernel: process_one_work+0x16e/0x243 Oct 25 13:59:54 asok kernel: ? cancel_delayed_work_sync+0xa/0xa Oct 25 13:59:54 asok kernel: worker_thread+0x1dc/0x2ac Oct 25 13:59:54 asok kernel: kthread+0x10b/0x113 Oct 25 13:59:54 asok kernel: ? kthread_flush_work_fn+0x9/0x9 Oct 25 13:59:54 asok kernel: ret_from_fork+0x35/0x40 Oct 25 13:59:54 asok kernel: ---[ end trace 1da7a4f5b4f12c5a ]---