Getting an error what does it mean


Go to solution Solved by ich777,

Recommended Posts

  • Solution
21 hours ago, Coco said:

How do I fix it?

Can you try to disable the avahi services, to do that simply execute this two commands from the terminal and see if it fixes the issue:

/etc/rc.d/rc.avahidaemon stop
/etc/rc.d/rc.avahidnsconfd stop

 

Do you have Docker containers in br0 mode?

  • Thanks 1
Link to comment
3 hours ago, ich777 said:

Can you try to disable the avahi services, to do that simply execute this two commands from the terminal and see if it fixes the issue:

/etc/rc.d/rc.avahidaemon stop
/etc/rc.d/rc.avahidnsconfd stop

 

Do you have Docker containers in br0 mode?

Yes I do have dockers in br0, it is how I give my docker their own IP addresses, is this not how I am supposed to do it?

 

I'll try the command and see if it fix things.

 

Also what is the avahi daemon? Is this going to mess with my dockers?

 

Thx

Edited by Coco
Added a question
Link to comment
9 hours ago, Vr2Io said:

Those are call trace and problem relate macvlan, you may try in docker setting page change from macvlan to ipvlan.

Which one are we supposed to use, all tutorial I have seen uses macvlan, what is the difference?

Link to comment
13 minutes ago, Coco said:

Which one are we supposed to use, all tutorial I have seen uses macvlan, what is the difference?

Please try to disable the avahi services first and stick to macvlan and see if that solves the issue please.

 

Please also keep in mind that you have to run this command again if you restart your Server to disable it again.

 

14 minutes ago, Coco said:

Also what is the avahi daemon? Is this going to mess with my dockers?

Discovering the server on Windows for example but nothing to worry about, you will be still able to reach/connect to your server still just fine.

 

No it won‘t mess with anything.

  • Thanks 1
Link to comment
59 minutes ago, ich777 said:

Please try to disable the avahi services first and stick to macvlan and see if that solves the issue please.

 

Please also keep in mind that you have to run this command again if you restart your Server to disable it again.

 

Discovering the server on Windows for example but nothing to worry about, you will be still able to reach/connect to your server still just fine.

 

No it won‘t mess with anything.

Ok, I'll give it a try,

 

In order to not have to re run the command everytime I reboot should I create a user script that run on every boot with those 2 command?

 

Do I just put the commands in a user script and have it run on start up?

 

How do I automamize the process?

Edited by Coco
Link to comment
15 minutes ago, ich777 said:

Please try to disable the avahi services first and stick to macvlan and see if that solves the issue please.

 

Please also keep in mind that you have to run this command again if you restart your Server to disable it again.

 

Discovering the server on Windows for example but nothing to worry about, you will be still able to reach/connect to your server still just fine.

 

No it won‘t mess with anything.

I ran the command, both worked and daemon is stop.

 

How will I know if it worked, wait and see if error come back?

 

Also I am now getting this error

 

python3[24076]: segfault at 0 ip 0000000000000000 sp 00001484a665cd58 error 14

 

What is this one ?

jarvis-diagnostics-20230304-0804.zip

Link to comment
46 minutes ago, Coco said:

In order to not have to re run the command everytime I reboot should I create a user script that run on every boot with those 2 command?

Do you reboot your server that often? You can also put the two commands in the go file after the emhttp command.

 

41 minutes ago, Coco said:

How will I know if it worked, wait and see if error come back?

If you got a Kernel panic again it doesn‘t work, but please let me know if it doesn‘t work, then I would suggest that you switch over to IPVLAN.

 

42 minutes ago, Coco said:

Also I am now getting this error

 

python3[24076]: segfault at 0 ip 0000000000000000 sp 00001484a665cd58 error 14

Python3 is usually not installed on Unraid by default, why do you have it installed?

  • Like 1
Link to comment
31 minutes ago, ich777 said:

Do you reboot your server that often? You can also put the two commands in the go file after the emhttp command.

 

If you got a Kernel panic again it doesn‘t work, but please let me know if it doesn‘t work, then I would suggest that you switch over to IPVLAN.

 

Python3 is usually not installed on Unraid by default, why do you have it installed?

Ok I'll monitor to see if the error comes back and keep you posted.

 

Quite frankly, I do not know ... Maybe I installed it to try something out ... Not sure, should I just uninstall? If so, how ?

 

How do I uninstall it ?

 

Thx a lot for your help

 

Do not know what is going on with my server these days, seems like there is a new error popping up every few days.

 

I do not restart it that often, but if I do I do not want to have to look for the command all over ...

 

So if I want to put this in a user script, I create a new script, paste the two command in it and have  it run at array start up, is this correct?

Edited by Coco
Added a question
Link to comment
1 hour ago, Coco said:

So if I want to put this in a user script, I create a new script, paste the two command in it and have  it run at array start up, is this correct?

Yes, you can do it that way too.

But if you don't reboot that often I don't see a reason to do it that way, let's check if you are experiencing another crash or not...

 

1 hour ago, Coco said:

How do I uninstall it ?

Seems not to be installed from what I see from your Diagnostics.

The python3 error seems to be caused by some container that you've got installed but I'm not entirely sure about that... This would be a thing for another thread.

  • Thanks 1
Link to comment
6 minutes ago, ich777 said:

I know it's been only a few days but did your system crash or is it still running?

Hi, 

 

Yes actually it did yesterday, now unsure if it is caused by the cpu error, as I did get it in the log even after running the 2 avahi command. Or if it is cause by the python 3 error as o keep getting it.

 

Server just became unresponsive, could not load web GUI or anything, had to hard reboot to get it back online.

 

I have attached the diagnostic file.

 

Of corse it won't have the cause of the crash since I rebooted but the errors are showing in there.

 

Thx

jarvis-diagnostics-20230306-0918.zip

Link to comment
7 minutes ago, Coco said:

Server just became unresponsive, could not load web GUI or anything, had to hard reboot to get it back online.

Please go to your Docker Settings, enable Advanced View on the right top and switch from MACVLAN to IPVLAN and see if this solves the issue <- the Docker Service needs to be disabled in the first place to change this setting.

Link to comment
Just now, JorgeB said:

those will usually end up on the server crashing.

I think in this specific case pyhton3 is the cause of the issue:

Mar  5 10:21:14 Jarvis kernel: python3[17669]: segfault at ffffffffffffffe8 ip 000014e921d3a38a sp 000014e92bbfc168 error 5 in libstdc++.so.6.0.30[14e921cb0000+119000]
Mar  5 10:21:14 Jarvis kernel: Code: ed 10 00 4c 89 e7 48 83 c0 10 48 89 43 18 e8 5d 64 f7 ff 48 89 ef e8 15 a6 f7 ff 0f 1f 44 00 00 f3 0f 1e fa 48 8b 06 48 89 07 <48> 8b 40 e8 48 8b 56 28 48 89 14 07 48 8b 46 30 48 89 47 10 48 8b
Mar  5 10:21:26 Jarvis kernel: python3[9461]: segfault at ffffffffffffffe8 ip 000014fb16f3a38a sp 000014fb20cc9168 error 5 in libstdc++.so.6.0.30[14fb16eb0000+119000]
Mar  5 10:21:26 Jarvis kernel: Code: ed 10 00 4c 89 e7 48 83 c0 10 48 89 43 18 e8 5d 64 f7 ff 48 89 ef e8 15 a6 f7 ff 0f 1f 44 00 00 f3 0f 1e fa 48 8b 06 48 89 07 <48> 8b 40 e8 48 8b 56 28 48 89 14 07 48 8b 46 30 48 89 47 10 48 8b
Mar  5 10:21:38 Jarvis kernel: python3[10730]: segfault at ffffffffffffffe8 ip 000014a76b13a38a sp 000014a76caf4f28 error 5 in libstdc++.so.6.0.30[14a76b0b0000+119000]
Mar  5 10:21:38 Jarvis kernel: Code: ed 10 00 4c 89 e7 48 83 c0 10 48 89 43 18 e8 5d 64 f7 ff 48 89 ef e8 15 a6 f7 ff 0f 1f 44 00 00 f3 0f 1e fa 48 8b 06 48 89 07 <48> 8b 40 e8 48 8b 56 28 48 89 14 07 48 8b 46 30 48 89 47 10 48 8b
Mar  5 10:56:11 Jarvis nginx: 2023/03/05 10:56:11 [crit] 8919#8919: *30329 SSL_do_handshake() failed (SSL: error:141CF06C:SSL routines:tls_parse_ctos_key_share:bad key share) while SSL handshaking, client: 124.220.186.134, server: 0.0.0.0:3225
Mar  5 16:00:48 Jarvis kernel: python3[11546]: segfault at ffffffffffffffe8 ip 0000152b67f3a38a sp 0000152b6af00808 error 5 in libstdc++.so.6.0.30[152b67eb0000+119000]
Mar  5 16:00:48 Jarvis kernel: Code: ed 10 00 4c 89 e7 48 83 c0 10 48 89 43 18 e8 5d 64 f7 ff 48 89 ef e8 15 a6 f7 ff 0f 1f 44 00 00 f3 0f 1e fa 48 8b 06 48 89 07 <48> 8b 40 e8 48 8b 56 28 48 89 14 07 48 8b 46 30 48 89 47 10 48 8b
Mar  5 16:21:22 Jarvis kernel: veth5676f29: renamed from eth0
Mar  5 16:21:22 Jarvis kernel: eth0: renamed from veth3f7d124
Mar  5 16:21:24 Jarvis kernel: veth3f7d124: renamed from eth0
Mar  5 16:21:24 Jarvis kernel: eth0: renamed from vethee2bcfd
Mar  5 17:28:35 Jarvis kernel: ------------[ cut here ]------------
Mar  5 17:28:35 Jarvis kernel: WARNING: CPU: 10 PID: 20123 at net/netfilter/nf_conntrack_core.c:1208 __nf_conntrack_confirm+0xa5/0x2cb [nf_conntrack]
Mar  5 17:28:35 Jarvis kernel: Modules linked in: cmac cifs asn1_decoder cifs_arc4 cifs_md4 dns_resolver xt_connmark xt_mark xt_comment iptable_raw xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap nvidia_uvm(PO) wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha macvlan veth xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod nct6775 nct6775_core hwmon_vid efivarfs ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc bonding tls ixgbe xfrm_algo mdio igb i2c_algo_bit r8169 realtek nvidia_drm(PO) nvidia_modeset(PO) nvidia(PO) drm_kms_helper btusb btrtl btbcm wmi_bmof mxm_wmi asus_ec_sensors edac_mce_amd edac_core kvm_amd kvm crct10dif_pclmul crc32_pclmul
Mar  5 17:28:35 Jarvis kernel: crc32c_intel ghash_clmulni_intel aesni_intel btintel crypto_simd cryptd drm bluetooth rapl mpt3sas backlight i2c_piix4 k10temp ccp nvme syscopyarea sysfillrect input_leds ahci led_class sysimgblt fb_sys_fops ecdh_generic libahci raid_class nvme_core i2c_core ecc scsi_transport_sas tpm_crb tpm_tis tpm_tis_core tpm wmi button acpi_cpufreq unix [last unloaded: xfrm_algo]
Mar  5 17:28:35 Jarvis kernel: CPU: 10 PID: 20123 Comm: kworker/10:1 Tainted: P           O      5.19.17-Unraid #2
Mar  5 17:28:35 Jarvis kernel: Hardware name: ASUS System Product Name/ROG CROSSHAIR VIII DARK HERO, BIOS 3801 07/30/2021
Mar  5 17:28:35 Jarvis kernel: Workqueue: events macvlan_process_broadcast [macvlan]
Mar  5 17:28:35 Jarvis kernel: RIP: 0010:__nf_conntrack_confirm+0xa5/0x2cb [nf_conntrack]
Mar  5 17:28:35 Jarvis kernel: Code: c6 48 89 44 24 10 e8 dd e2 ff ff 8b 7c 24 04 89 da 89 c6 89 04 24 e8 56 e6 ff ff 84 c0 75 a2 48 8b 85 80 00 00 00 a8 08 74 18 <0f> 0b 8b 34 24 8b 7c 24 04 e8 16 de ff ff e8 2c e3 ff ff e9 7e 01
Mar  5 17:28:35 Jarvis kernel: RSP: 0018:ffffc90000420da0 EFLAGS: 00010202
Mar  5 17:28:35 Jarvis kernel: RAX: 0000000000000188 RBX: 0000000000000000 RCX: 97083bcc81c25e8d
Mar  5 17:28:35 Jarvis kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffffffffa02b3738
Mar  5 17:28:35 Jarvis kernel: RBP: ffff888206ba4e00 R08: b6465e0c0c21af44 R09: 8c6375c236efc03f
Mar  5 17:28:35 Jarvis kernel: R10: e01fc631bae11b77 R11: 714df502cfd5de91 R12: ffffffff82909480
Mar  5 17:28:35 Jarvis kernel: R13: 000000000000c03a R14: ffff8881ef89ba00 R15: 0000000000000000
Mar  5 17:28:35 Jarvis kernel: FS:  0000000000000000(0000) GS:ffff88880ea80000(0000) knlGS:0000000000000000
Mar  5 17:28:35 Jarvis kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Mar  5 17:28:35 Jarvis kernel: CR2: 000000c0003ee000 CR3: 00000001d06cc000 CR4: 0000000000750ee0
Mar  5 17:28:35 Jarvis kernel: PKRU: 55555554
Mar  5 17:28:35 Jarvis kernel: Call Trace:
Mar  5 17:28:35 Jarvis kernel: <IRQ>
Mar  5 17:28:35 Jarvis kernel: nf_conntrack_confirm+0x25/0x54 [nf_conntrack]
Mar  5 17:28:35 Jarvis kernel: nf_hook_slow+0x3d/0x96
Mar  5 17:28:35 Jarvis kernel: ? ip_protocol_deliver_rcu+0x164/0x164
Mar  5 17:28:35 Jarvis kernel: NF_HOOK.constprop.0+0x79/0xd9
Mar  5 17:28:35 Jarvis kernel: ? ip_protocol_deliver_rcu+0x164/0x164
Mar  5 17:28:35 Jarvis kernel: __netif_receive_skb_one_core+0x77/0x9c
Mar  5 17:28:35 Jarvis kernel: process_backlog+0x8c/0x116
Mar  5 17:28:35 Jarvis kernel: __napi_poll.constprop.0+0x2b/0x124
Mar  5 17:28:35 Jarvis kernel: net_rx_action+0x159/0x24f
Mar  5 17:28:35 Jarvis kernel: __do_softirq+0x129/0x288
Mar  5 17:28:35 Jarvis kernel: do_softirq+0x7f/0xab
Mar  5 17:28:35 Jarvis kernel: </IRQ>
Mar  5 17:28:35 Jarvis kernel: <TASK>
Mar  5 17:28:35 Jarvis kernel: __local_bh_enable_ip+0x4c/0x6b
Mar  5 17:28:35 Jarvis kernel: netif_rx+0x52/0x5a
Mar  5 17:28:35 Jarvis kernel: macvlan_broadcast+0x10a/0x150 [macvlan]
Mar  5 17:28:35 Jarvis kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan]
Mar  5 17:28:35 Jarvis kernel: process_one_work+0x1ab/0x295
Mar  5 17:28:35 Jarvis kernel: worker_thread+0x18b/0x244
Mar  5 17:28:35 Jarvis kernel: ? rescuer_thread+0x281/0x281
Mar  5 17:28:35 Jarvis kernel: kthread+0xe7/0xef
Mar  5 17:28:35 Jarvis kernel: ? kthread_complete_and_exit+0x1b/0x1b
Mar  5 17:28:35 Jarvis kernel: ret_from_fork+0x22/0x30
Mar  5 17:28:35 Jarvis kernel: </TASK>
Mar  5 17:28:35 Jarvis kernel: ---[ end trace 0000000000000000 ]---

 

 

@Coco Do you use something like Tdarr or Unmanic?

Link to comment
1 hour ago, ich777 said:

I think in this specific case pyhton3 is the cause of the issue:

Mar  5 10:21:14 Jarvis kernel: python3[17669]: segfault at ffffffffffffffe8 ip 000014e921d3a38a sp 000014e92bbfc168 error 5 in libstdc++.so.6.0.30[14e921cb0000+119000]
Mar  5 10:21:14 Jarvis kernel: Code: ed 10 00 4c 89 e7 48 83 c0 10 48 89 43 18 e8 5d 64 f7 ff 48 89 ef e8 15 a6 f7 ff 0f 1f 44 00 00 f3 0f 1e fa 48 8b 06 48 89 07 <48> 8b 40 e8 48 8b 56 28 48 89 14 07 48 8b 46 30 48 89 47 10 48 8b
Mar  5 10:21:26 Jarvis kernel: python3[9461]: segfault at ffffffffffffffe8 ip 000014fb16f3a38a sp 000014fb20cc9168 error 5 in libstdc++.so.6.0.30[14fb16eb0000+119000]
Mar  5 10:21:26 Jarvis kernel: Code: ed 10 00 4c 89 e7 48 83 c0 10 48 89 43 18 e8 5d 64 f7 ff 48 89 ef e8 15 a6 f7 ff 0f 1f 44 00 00 f3 0f 1e fa 48 8b 06 48 89 07 <48> 8b 40 e8 48 8b 56 28 48 89 14 07 48 8b 46 30 48 89 47 10 48 8b
Mar  5 10:21:38 Jarvis kernel: python3[10730]: segfault at ffffffffffffffe8 ip 000014a76b13a38a sp 000014a76caf4f28 error 5 in libstdc++.so.6.0.30[14a76b0b0000+119000]
Mar  5 10:21:38 Jarvis kernel: Code: ed 10 00 4c 89 e7 48 83 c0 10 48 89 43 18 e8 5d 64 f7 ff 48 89 ef e8 15 a6 f7 ff 0f 1f 44 00 00 f3 0f 1e fa 48 8b 06 48 89 07 <48> 8b 40 e8 48 8b 56 28 48 89 14 07 48 8b 46 30 48 89 47 10 48 8b
Mar  5 10:56:11 Jarvis nginx: 2023/03/05 10:56:11 [crit] 8919#8919: *30329 SSL_do_handshake() failed (SSL: error:141CF06C:SSL routines:tls_parse_ctos_key_share:bad key share) while SSL handshaking, client: 124.220.186.134, server: 0.0.0.0:3225
Mar  5 16:00:48 Jarvis kernel: python3[11546]: segfault at ffffffffffffffe8 ip 0000152b67f3a38a sp 0000152b6af00808 error 5 in libstdc++.so.6.0.30[152b67eb0000+119000]
Mar  5 16:00:48 Jarvis kernel: Code: ed 10 00 4c 89 e7 48 83 c0 10 48 89 43 18 e8 5d 64 f7 ff 48 89 ef e8 15 a6 f7 ff 0f 1f 44 00 00 f3 0f 1e fa 48 8b 06 48 89 07 <48> 8b 40 e8 48 8b 56 28 48 89 14 07 48 8b 46 30 48 89 47 10 48 8b
Mar  5 16:21:22 Jarvis kernel: veth5676f29: renamed from eth0
Mar  5 16:21:22 Jarvis kernel: eth0: renamed from veth3f7d124
Mar  5 16:21:24 Jarvis kernel: veth3f7d124: renamed from eth0
Mar  5 16:21:24 Jarvis kernel: eth0: renamed from vethee2bcfd
Mar  5 17:28:35 Jarvis kernel: ------------[ cut here ]------------
Mar  5 17:28:35 Jarvis kernel: WARNING: CPU: 10 PID: 20123 at net/netfilter/nf_conntrack_core.c:1208 __nf_conntrack_confirm+0xa5/0x2cb [nf_conntrack]
Mar  5 17:28:35 Jarvis kernel: Modules linked in: cmac cifs asn1_decoder cifs_arc4 cifs_md4 dns_resolver xt_connmark xt_mark xt_comment iptable_raw xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap nvidia_uvm(PO) wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha macvlan veth xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod nct6775 nct6775_core hwmon_vid efivarfs ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc bonding tls ixgbe xfrm_algo mdio igb i2c_algo_bit r8169 realtek nvidia_drm(PO) nvidia_modeset(PO) nvidia(PO) drm_kms_helper btusb btrtl btbcm wmi_bmof mxm_wmi asus_ec_sensors edac_mce_amd edac_core kvm_amd kvm crct10dif_pclmul crc32_pclmul
Mar  5 17:28:35 Jarvis kernel: crc32c_intel ghash_clmulni_intel aesni_intel btintel crypto_simd cryptd drm bluetooth rapl mpt3sas backlight i2c_piix4 k10temp ccp nvme syscopyarea sysfillrect input_leds ahci led_class sysimgblt fb_sys_fops ecdh_generic libahci raid_class nvme_core i2c_core ecc scsi_transport_sas tpm_crb tpm_tis tpm_tis_core tpm wmi button acpi_cpufreq unix [last unloaded: xfrm_algo]
Mar  5 17:28:35 Jarvis kernel: CPU: 10 PID: 20123 Comm: kworker/10:1 Tainted: P           O      5.19.17-Unraid #2
Mar  5 17:28:35 Jarvis kernel: Hardware name: ASUS System Product Name/ROG CROSSHAIR VIII DARK HERO, BIOS 3801 07/30/2021
Mar  5 17:28:35 Jarvis kernel: Workqueue: events macvlan_process_broadcast [macvlan]
Mar  5 17:28:35 Jarvis kernel: RIP: 0010:__nf_conntrack_confirm+0xa5/0x2cb [nf_conntrack]
Mar  5 17:28:35 Jarvis kernel: Code: c6 48 89 44 24 10 e8 dd e2 ff ff 8b 7c 24 04 89 da 89 c6 89 04 24 e8 56 e6 ff ff 84 c0 75 a2 48 8b 85 80 00 00 00 a8 08 74 18 <0f> 0b 8b 34 24 8b 7c 24 04 e8 16 de ff ff e8 2c e3 ff ff e9 7e 01
Mar  5 17:28:35 Jarvis kernel: RSP: 0018:ffffc90000420da0 EFLAGS: 00010202
Mar  5 17:28:35 Jarvis kernel: RAX: 0000000000000188 RBX: 0000000000000000 RCX: 97083bcc81c25e8d
Mar  5 17:28:35 Jarvis kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffffffffa02b3738
Mar  5 17:28:35 Jarvis kernel: RBP: ffff888206ba4e00 R08: b6465e0c0c21af44 R09: 8c6375c236efc03f
Mar  5 17:28:35 Jarvis kernel: R10: e01fc631bae11b77 R11: 714df502cfd5de91 R12: ffffffff82909480
Mar  5 17:28:35 Jarvis kernel: R13: 000000000000c03a R14: ffff8881ef89ba00 R15: 0000000000000000
Mar  5 17:28:35 Jarvis kernel: FS:  0000000000000000(0000) GS:ffff88880ea80000(0000) knlGS:0000000000000000
Mar  5 17:28:35 Jarvis kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Mar  5 17:28:35 Jarvis kernel: CR2: 000000c0003ee000 CR3: 00000001d06cc000 CR4: 0000000000750ee0
Mar  5 17:28:35 Jarvis kernel: PKRU: 55555554
Mar  5 17:28:35 Jarvis kernel: Call Trace:
Mar  5 17:28:35 Jarvis kernel: <IRQ>
Mar  5 17:28:35 Jarvis kernel: nf_conntrack_confirm+0x25/0x54 [nf_conntrack]
Mar  5 17:28:35 Jarvis kernel: nf_hook_slow+0x3d/0x96
Mar  5 17:28:35 Jarvis kernel: ? ip_protocol_deliver_rcu+0x164/0x164
Mar  5 17:28:35 Jarvis kernel: NF_HOOK.constprop.0+0x79/0xd9
Mar  5 17:28:35 Jarvis kernel: ? ip_protocol_deliver_rcu+0x164/0x164
Mar  5 17:28:35 Jarvis kernel: __netif_receive_skb_one_core+0x77/0x9c
Mar  5 17:28:35 Jarvis kernel: process_backlog+0x8c/0x116
Mar  5 17:28:35 Jarvis kernel: __napi_poll.constprop.0+0x2b/0x124
Mar  5 17:28:35 Jarvis kernel: net_rx_action+0x159/0x24f
Mar  5 17:28:35 Jarvis kernel: __do_softirq+0x129/0x288
Mar  5 17:28:35 Jarvis kernel: do_softirq+0x7f/0xab
Mar  5 17:28:35 Jarvis kernel: </IRQ>
Mar  5 17:28:35 Jarvis kernel: <TASK>
Mar  5 17:28:35 Jarvis kernel: __local_bh_enable_ip+0x4c/0x6b
Mar  5 17:28:35 Jarvis kernel: netif_rx+0x52/0x5a
Mar  5 17:28:35 Jarvis kernel: macvlan_broadcast+0x10a/0x150 [macvlan]
Mar  5 17:28:35 Jarvis kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan]
Mar  5 17:28:35 Jarvis kernel: process_one_work+0x1ab/0x295
Mar  5 17:28:35 Jarvis kernel: worker_thread+0x18b/0x244
Mar  5 17:28:35 Jarvis kernel: ? rescuer_thread+0x281/0x281
Mar  5 17:28:35 Jarvis kernel: kthread+0xe7/0xef
Mar  5 17:28:35 Jarvis kernel: ? kthread_complete_and_exit+0x1b/0x1b
Mar  5 17:28:35 Jarvis kernel: ret_from_fork+0x22/0x30
Mar  5 17:28:35 Jarvis kernel: </TASK>
Mar  5 17:28:35 Jarvis kernel: ---[ end trace 0000000000000000 ]---

 

 

@Coco Do you use something like Tdarr or Unmanic?

Yes, I use unmanic, could this be causing all the issues? Never had a problem with it before.

Link to comment
1 hour ago, ich777 said:

Please go to your Docker Settings, enable Advanced View on the right top and switch from MACVLAN to IPVLAN and see if this solves the issue <- the Docker Service needs to be disabled in the first place to change this setting.

Change docker setting to ipvlan, will this mess with dockers? Will I have to change anything in the docker settings?

Link to comment
3 minutes ago, Coco said:

Change docker setting to ipvlan, will this mess with dockers? Will I have to change anything in the docker settings?

No.

 

4 minutes ago, Coco said:

Yes, I use unmanic, could this be causing all the issues? Never had a problem with it before.

Try to not auto start it on boot and see if you can spot the python3 messages in your syslog, if you don't see any such messages try to start it and watch out the messages from above. It could also be the case that is another container which uses pyhton3 since you don't have python3 installed on the host.

Link to comment
2 minutes ago, ich777 said:

No.

 

Try to not auto start it on boot and see if you can spot the python3 messages in your syslog, if you don't see any such messages try to start it and watch out the messages from above. It could also be the case that is another container which uses pyhton3 since you don't have python3 installed on the host.

Ok, I did switch to ipvlan.

 

What is the difference between the two anyway?

 

As for unmanic, should I disable autostart, reboot and watch the log ?

Link to comment
4 minutes ago, Coco said:

Ok, I did switch to ipvlan.

 

What is the difference between the two anyway?

 

As for unmanic, should I disable autostart, reboot and watch the log ?

Ok, I disabled autostart on unmanic.

 

Downloaded a diagnostic file

 

Rebooted the server

 

When it is up, I will start unmanic and watch the log for the python error

 

I'll keep you posted

 

Thx again 

  • Like 1
Link to comment

It has been almost 3 hours now since reboot with dockers set to ipvlan and unmanic set to not start automatically, I started it manually once docker service was up.

 

Still no error message in log.

 

I'll keep monitoring 

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