snowy00
-
Posts
65 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by snowy00
-
-
I found this kind of messages in the Log - is that normal?
Mar 6 21:34:42 Tower kernel: usb 4-3: reset SuperSpeed USB device number 2 using xhci_hcd Mar 6 21:34:42 Tower kernel: usb 4-3: LPM exit latency is zeroed, disabling LPM. Mar 7 06:44:33 Tower kernel: usb 4-3: reset SuperSpeed USB device number 2 using xhci_hcd Mar 7 06:44:33 Tower kernel: usb 4-3: LPM exit latency is zeroed, disabling LPM. Mar 7 16:01:14 Tower kernel: usb 4-3: reset SuperSpeed USB device number 2 using xhci_hcd Mar 7 16:01:14 Tower kernel: usb 4-3: LPM exit latency is zeroed, disabling LPM. Mar 7 17:29:44 Tower kernel: usb 4-3: reset SuperSpeed USB device number 2 using xhci_hcd Mar 7 17:29:44 Tower kernel: usb 4-3: LPM exit latency is zeroed, disabling LPM.QuoteThe previous syslog only covers 10 minutes uptime, and there's nothing there relevant, did the server crash after 10 minutes?
Nope I started the server after the crash and did the diagnostics - the mirror logfile to flash was activated during the crash. As mentioned by itimpi (and my understanding is) that the logfile should survives a reboot, so I am confused that the log ist not available in this diagnostics.
-
Hi, today the serve crashed again! Could you please have a look...
-
Hi itimpi,
thanks for the information - pleas find attached the diagnostics from my system. I have already configured the syylog server but not the copy to the flash drive. Maybe you are able to finde some reasons for the crash.
Thanks a lot!
-
Hi, something happend this night and the Server was not reachable from the local network. After hard reset ""power off" the server starts running properly. This is the last log that received from server:
It seems there a lot network issues? By the way at 1:00 it starts a backup of my Docker appdata. (Appdata.Backup)
Mar 4 01:01:04 Tower kernel: veth30a58bb: renamed from eth0 Mar 4 01:01:04 Tower kernel: veth00da9cf: renamed from eth0 Mar 4 01:01:06 Tower kernel: vethcd6745b: renamed from eth0 Mar 4 01:01:06 Tower kernel: veth60d5d03: renamed from eth0 Mar 4 01:01:07 Tower kernel: vethbb4d0b3: renamed from eth0 Mar 4 01:01:07 Tower kernel: vethe8a0781: renamed from eth0 Mar 4 01:01:12 Tower kernel: veth628ba8c: renamed from eth0 Mar 4 01:01:13 Tower kernel: veth710ddf1: renamed from eth0 Mar 4 01:01:13 Tower kernel: veth2c67992: renamed from eth0 Mar 4 01:01:14 Tower kernel: veth68e5056: renamed from eth0 Mar 4 01:01:15 Tower kernel: vethb6d5f57: renamed from eth0 Mar 4 01:01:20 Tower kernel: veth0a6f738: renamed from eth0 Mar 4 01:01:26 Tower kernel: veth8afb35f: renamed from eth0 Mar 4 01:01:26 Tower kernel: vethf50f2c4: renamed from eth0 Mar 4 01:01:28 Tower kernel: docker0: port 1(vethd9eada9) entered disabled state Mar 4 01:01:28 Tower kernel: veth7ebc59c: renamed from eth0 Mar 4 01:01:29 Tower kernel: docker0: port 1(vethd9eada9) entered disabled state Mar 4 01:01:29 Tower kernel: device vethd9eada9 left promiscuous mode Mar 4 01:01:29 Tower kernel: docker0: port 1(vethd9eada9) entered disabled state Mar 4 01:01:33 Tower kernel: veth8147789: renamed from eth0 Mar 4 01:01:42 Tower kernel: veth3fb5ef5: renamed from eth0 Mar 4 01:01:44 Tower kernel: vethad0725a: renamed from eth0 Mar 4 01:01:55 Tower kernel: vethd22e44c: renamed from eth0 Mar 4 01:02:10 Tower kernel: vethbe7b9d3: renamed from eth0 Mar 4 01:02:11 Tower kernel: docker0: port 1(veth1c51ad7) entered blocking state Mar 4 01:02:11 Tower kernel: docker0: port 1(veth1c51ad7) entered disabled state Mar 4 01:02:11 Tower kernel: device veth1c51ad7 entered promiscuous mode Mar 4 01:02:14 Tower kernel: eth0: renamed from veth4422939 Mar 4 01:02:14 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth1c51ad7: link becomes ready Mar 4 01:02:14 Tower kernel: docker0: port 1(veth1c51ad7) entered blocking state Mar 4 01:02:14 Tower kernel: docker0: port 1(veth1c51ad7) entered forwarding state Mar 4 01:02:17 Tower kernel: eth0: renamed from veth4d295c1 Mar 4 01:02:17 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 4 01:02:19 Tower kernel: eth0: renamed from vethff47134 Mar 4 01:02:19 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 4 01:02:22 Tower kernel: eth0: renamed from veth6398c38 Mar 4 01:02:22 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 4 01:02:27 Tower kernel: eth0: renamed from veth64e7d71 Mar 4 01:02:27 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 4 01:02:31 Tower kernel: eth0: renamed from veth04c1a21 Mar 4 01:02:31 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 4 01:02:34 Tower kernel: eth0: renamed from veth3d1be86 Mar 4 01:02:34 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 4 01:02:37 Tower kernel: eth0: renamed from veth11676dd Mar 4 01:02:37 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 4 01:02:41 Tower kernel: eth0: renamed from vethd3fa0d0 Mar 4 01:02:41 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 4 01:02:44 Tower kernel: eth0: renamed from veth2fe8a48 Mar 4 01:02:44 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 4 01:02:47 Tower kernel: eth0: renamed from vethf6a7292 Mar 4 01:02:47 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 4 01:02:51 Tower kernel: eth0: renamed from veth09e4ce5 Mar 4 01:02:51 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 4 01:02:54 Tower kernel: eth0: renamed from veth3a4776a Mar 4 01:02:54 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 4 01:02:58 Tower kernel: eth0: renamed from veth6ca1441 Mar 4 01:02:58 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 4 01:03:02 Tower kernel: eth0: renamed from veth5a641ad Mar 4 01:03:02 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 4 01:03:05 Tower kernel: eth0: renamed from veth6702d54 Mar 4 01:03:05 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 4 01:03:09 Tower kernel: eth0: renamed from veth45a5fdc Mar 4 01:03:09 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 4 01:03:13 Tower kernel: eth0: renamed from veth8ead0f1 Mar 4 01:03:13 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 4 01:03:17 Tower kernel: eth0: renamed from vethd7596cf Mar 4 01:03:17 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 4 01:03:25 Tower kernel: eth0: renamed from veth81bff7d Mar 4 01:03:25 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 -
Thanks a lot for the support - what ist the best way to replace it. Rather to rebuild by parity or other way.
-
here is the reporttower-smart-20240215-1856.zip
-
hi, I did the test and the result looks quite positive.
Any idea what happened or what to do?
-
Hello together,
Since a crash of my server I have some read errors on my second HDD.
Could someone help me to solve it?
-
Also ich hatte folgendes Problem:
Unraid Version 6.12.3
Fritzbox + Digitus Switch + IPVLAN --> Crash (Verstand dass die Fritzbox damit nicht umgehen kann)
Unifi Gateway USG + Digitus Switch + IPVLAN --> Crash (sobald der Switch entfernt wird und gegen einen anderen getauscht wird geht es wieder für manchmal Tage --> wenn das Problem wieder Auftritt wieder Switch tausch und dann geht es wieder)
Wenn ich von Crash rede, dann nicht vom Unraid sondern von Netzwerk, das am Digitus Switch hängt.
Vielleicht gibt es hier Netzwerkspezialisten, die das erklären können - ich habe leider nichts mehr dazu gefunden.
Deshalb auch meine Vermutung, dass der Switch irgendwo im Cache die Mac Adressen speichert und dann irgendein Blödsinn damit macht - oder das routing nicht mehr richtig gemacht wird.
Ich kenne mich zwar mit Netzwerk und IT aus aber das übersteigt meine Kenntnisse.
-
Es muss einen Zusammenhang geben... Ich habe bereits ein Feldbett neben meinem Netzwerkschrank stehen...
Bin jetzt wieder auf die 11.5 zurück gegangen, ich hoffe, dass es nicht so oft solche Bugs gibt.
Bis man da als Laie dahinterkommt, was genau passiert und 10 Switches und Router tauscht ist man nervlich am Ende. (Insbesondere zu Zeiten vom Homeoffice)
-
Hi zusammen,
Ich kenne mich mit der Materie nicht genau aus, kann es aber sein, dass es auch Switches gibt, die mit IPVLAN Probleme machen. Ich habe einen DIGITUS Unmanaged Switch und nach einiger Zeit ist im Netzwerk nichts mehr erreichbar? Getestet mit einer Fritzbox und mit einem Unifi Router. Über Wlan kommt man zwar noch ins Internet aber das LAN-Netzwerk ist tot. Hilft nur noch alles vom Strom zunehmen.
Oder ist das nur ein blöder Zufall, dass der Switch ne Macke hat und gerade die Probleme mit Unraid macvlan vorhanden sind.
VG
-
Hallo zusammen,
nachdem ich die selben Probleme hatte und erst verstehen musste, warum ich diese Probleme habe und zusätzlich 3 Switches getauscht hatte, da ich dachte dass das Problem durch einen defekten Switch verursacht wurde, würde ich gerne die Fritzbox ersetzen.
Kann jemand eine Empfehlung für einen reinen Router geben?
Hatte an einen --> Ubiquiti EdgeRouter 4
KAnn den jemand empfehlen?
-
Danke für die Infos.
Hatte das selbe Problem und hab bereits den Switch getauscht, da ich dachte, dass dieser ne Macke hat.
-
works also fine for me - thanks
-
1
-
-
Should I add the extra parameter --> --device=/dev/dri
Any recommendation what can I set in the hardware decoder parameters?
-
Just a question - is it possible to use the AMD AGPU to reduce the processor power? --> set the parameter /dev/dri?
Thanks in advance!
-
Den Adapter hab ich da - bin aber noch nicht dazu gekommen es einzubauen.
-
Hello,
how can update it, is there a how to available?
Thanks!
-
Hi zusammen,
hab jetzt diesen Post gefunden:
https://forums.unraid.net/topic/120587-random-crashes/
Und habe das Docker Docker custom network type von Macvlan zu ipvlan geändert mal schauen was passiert.
(Settings -> Docker Settings -> Docker custom network type -> ipvlan)
-
Folgendes kommt immer wieder in den Logs:
Apr 21 17:31:53 Tower kernel: WARNING: CPU: 0 PID: 0 at net/netfilter/nf_nat_core.c:594 nf_nat_setup_info+0x6f/0x773 [nf_nat] Apr 21 17:31:53 Tower kernel: Modules linked in: veth xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle iptable_mangle vhost_net tun vhost vhost_iotlb tap macvlan xt_nat xt_tcpudp xt_conntrack nf_conntrack_netlink nfnetlink xt_addrtype br_netfilter xfs ip6table_nat md_mod nct6775 hwmon_vid av201x(O) tbsecp3(O) gx1133(O) tas2101(O) i2c_mux dvb_core(O) videobuf2_vmalloc(O) videobuf2_memops(O) videobuf2_common(O) videodev(O) mc(O) efivarfs iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 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 ip6table_filter ip6_tables iptable_filter ip_tables x_tables bonding amdgpu gpu_sched drm_ttm_helper ttm edac_mce_amd drm_kms_helper kvm_amd kvm drm crct10dif_pclmul crc32_pclmul crc32c_intel btusb btrtl btbcm ghash_clmulni_intel wmi_bmof aesni_intel nvme crypto_simd cryptd agpgart btintel syscopyarea sysfillrect Apr 21 17:31:53 Tower kernel: igb rapl bluetooth i2c_algo_bit nvme_core sysimgblt i2c_piix4 fb_sys_fops k10temp i2c_core ahci tpm_crb tpm_tis ccp video tpm_tis_core ecdh_generic ecc libahci backlight tpm wmi button acpi_cpufreq Apr 21 17:31:53 Tower kernel: CPU: 0 PID: 0 Comm: swapper/0 Tainted: G W O 5.15.30-Unraid #1 Apr 21 17:31:53 Tower kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B450 Gaming-ITX/ac, BIOS P4.60 08/11/2021 Apr 21 17:31:53 Tower kernel: RIP: 0010:nf_nat_setup_info+0x6f/0x773 [nf_nat] Apr 21 17:31:53 Tower kernel: Code: 89 fb 49 89 f5 41 89 d4 76 02 0f 0b 48 8b 93 80 00 00 00 89 d0 25 00 01 00 00 45 85 e4 75 07 89 d0 25 80 00 00 00 85 c0 74 07 <0f> 0b e9 32 06 00 00 48 8b 83 90 00 00 00 4c 8d 7c 24 28 48 8d 73 Apr 21 17:31:53 Tower kernel: RSP: 0018:ffffc90000003760 EFLAGS: 00010202 Apr 21 17:31:53 Tower kernel: RAX: 0000000000000080 RBX: ffff8881b6352dc0 RCX: ffff888104f68e80 Apr 21 17:31:53 Tower kernel: RDX: 0000000000000180 RSI: ffffc9000000384c RDI: ffff8881b6352dc0 Apr 21 17:31:53 Tower kernel: RBP: ffffc90000003830 R08: 0000000041b2a8c0 R09: 0000000000000000 Apr 21 17:31:53 Tower kernel: R10: 0000000000000158 R11: 0000000000000000 R12: 0000000000000000 Apr 21 17:31:53 Tower kernel: R13: ffffc9000000384c R14: 0000000000000000 R15: 0000000000000001 Apr 21 17:31:53 Tower kernel: FS: 0000000000000000(0000) GS:ffff8887a0600000(0000) knlGS:0000000000000000 Apr 21 17:31:53 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Apr 21 17:31:53 Tower kernel: CR2: 000014e75b7f2820 CR3: 00000001d318e000 CR4: 00000000003506f0 Apr 21 17:31:53 Tower kernel: Call Trace: Apr 21 17:31:53 Tower kernel: <IRQ> Apr 21 17:31:53 Tower kernel: ? ipt_do_table+0x563/0x5b0 [ip_tables] Apr 21 17:31:53 Tower kernel: ? slab_post_alloc_hook+0x50/0x157 Apr 21 17:31:53 Tower kernel: __nf_nat_alloc_null_binding+0x68/0x7f [nf_nat] Apr 21 17:31:53 Tower kernel: nf_nat_inet_fn+0xa6/0x187 [nf_nat] Apr 21 17:31:53 Tower kernel: nf_nat_ipv4_local_in+0x2a/0xae [nf_nat] Apr 21 17:31:53 Tower kernel: nf_hook_slow+0x3e/0x93 Apr 21 17:31:53 Tower kernel: ? ip_protocol_deliver_rcu+0x112/0x112 Apr 21 17:31:53 Tower kernel: NF_HOOK.constprop.0+0x73/0xce Apr 21 17:31:53 Tower kernel: ? ip_protocol_deliver_rcu+0x112/0x112 Apr 21 17:31:53 Tower kernel: ip_sabotage_in+0x4c/0x59 [br_netfilter] Apr 21 17:31:53 Tower kernel: nf_hook_slow+0x3e/0x93 Apr 21 17:31:53 Tower kernel: ? ip_rcv_finish_core.constprop.0+0x358/0x358 Apr 21 17:31:53 Tower kernel: NF_HOOK.constprop.0+0x73/0xce Apr 21 17:31:53 Tower kernel: ? ip_rcv_finish_core.constprop.0+0x358/0x358 Apr 21 17:31:53 Tower kernel: __netif_receive_skb_one_core+0x79/0x9a Apr 21 17:31:53 Tower kernel: netif_receive_skb+0xa3/0xf7 Apr 21 17:31:53 Tower kernel: br_handle_frame_finish+0x3c5/0x407 Apr 21 17:31:53 Tower kernel: ? br_handle_local_finish+0x13/0x13 Apr 21 17:31:53 Tower kernel: br_nf_hook_thresh+0xc6/0xf7 [br_netfilter] Apr 21 17:31:53 Tower kernel: ? br_handle_local_finish+0x13/0x13 Apr 21 17:31:53 Tower kernel: br_nf_pre_routing_finish+0x29d/0x2c4 [br_netfilter] Apr 21 17:31:53 Tower kernel: ? br_handle_local_finish+0x13/0x13 Apr 21 17:31:53 Tower kernel: ? NF_HOOK.isra.0+0xc5/0x119 [br_netfilter] Apr 21 17:31:53 Tower kernel: ? br_handle_frame_finish+0x407/0x407 Apr 21 17:31:53 Tower kernel: br_nf_pre_routing+0x226/0x236 [br_netfilter] Apr 21 17:31:53 Tower kernel: ? br_nf_forward_finish+0xdc/0xdc [br_netfilter] Apr 21 17:31:53 Tower kernel: br_handle_frame+0x292/0x2da Apr 21 17:31:53 Tower kernel: ? br_handle_local_finish+0x13/0x13 Apr 21 17:31:53 Tower kernel: __netif_receive_skb_core.constprop.0+0x354/0x515 Apr 21 17:31:53 Tower kernel: ? find_busiest_group+0x40/0x2ba Apr 21 17:31:53 Tower kernel: __netif_receive_skb_list_core+0x81/0x112 Apr 21 17:31:53 Tower kernel: netif_receive_skb_list_internal+0x1c7/0x1fc Apr 21 17:31:53 Tower kernel: gro_normal_list+0x22/0x3e Apr 21 17:31:53 Tower kernel: napi_complete_done+0x7f/0x118 Apr 21 17:31:53 Tower kernel: igb_poll+0xd69/0xf96 [igb] Apr 21 17:31:53 Tower kernel: ? rebalance_domains+0x1f9/0x22f Apr 21 17:31:53 Tower kernel: __napi_poll.constprop.0+0x2a/0x114 Apr 21 17:31:53 Tower kernel: net_rx_action+0xe8/0x1f2 Apr 21 17:31:53 Tower kernel: __do_softirq+0xef/0x218 Apr 21 17:31:53 Tower kernel: __irq_exit_rcu+0x4d/0x88 Apr 21 17:31:53 Tower kernel: common_interrupt+0x73/0x8b Apr 21 17:31:53 Tower kernel: </IRQ> Apr 21 17:31:53 Tower kernel: <TASK> Apr 21 17:31:53 Tower kernel: asm_common_interrupt+0x1e/0x40 Apr 21 17:31:53 Tower kernel: RIP: 0010:native_safe_halt+0x7/0x8 Apr 21 17:31:53 Tower kernel: Code: 60 02 df f0 83 44 24 fc 00 48 8b 00 a8 08 74 0b 65 81 25 8c 8b 84 7e ff ff ff 7f c3 e8 91 ce 87 ff f4 c3 e8 8a ce 87 ff fb f4 <c3> 0f 1f 44 00 00 31 ff 53 65 8b 35 b5 25 84 7e e8 dc b2 8b ff e8 Apr 21 17:31:53 Tower kernel: RSP: 0018:ffffffff82003e30 EFLAGS: 00000246 Apr 21 17:31:53 Tower kernel: RAX: 0000000000004000 RBX: 0000000000000001 RCX: 00000000018193d7 Apr 21 17:31:53 Tower kernel: RDX: ffff8887a0600000 RSI: ffff888100c10000 RDI: ffff888100c10064 Apr 21 17:31:53 Tower kernel: RBP: ffff888107e2d400 R08: ffff888107e2d400 R09: ffff8887a061ece0 Apr 21 17:31:53 Tower kernel: R10: 0000000000000020 R11: 0000000000000339 R12: 0000000000000001 Apr 21 17:31:53 Tower kernel: R13: ffff888100c10064 R14: ffffffff82114020 R15: 0000000000000000 Apr 21 17:31:53 Tower kernel: arch_safe_halt+0x5/0x8 Apr 21 17:31:53 Tower kernel: acpi_idle_do_entry+0x2a/0x3c Apr 21 17:31:53 Tower kernel: acpi_idle_enter+0x9a/0xa9 Apr 21 17:31:53 Tower kernel: cpuidle_enter_state+0xc6/0x1db Apr 21 17:31:53 Tower kernel: cpuidle_enter+0x2a/0x36 Apr 21 17:31:53 Tower kernel: do_idle+0x1b7/0x225 Apr 21 17:31:53 Tower kernel: cpu_startup_entry+0x1d/0x1f Apr 21 17:31:53 Tower kernel: start_kernel+0x651/0x676 Apr 21 17:31:53 Tower kernel: secondary_startup_64_no_verify+0xb0/0xbb Apr 21 17:31:53 Tower kernel: </TASK> Apr 21 17:31:53 Tower kernel: ---[ end trace dd5673d1565ecd92 ]---
-
Hallo zusammen,
hatte heute schon zweimal das Problem, dass UNRAID WEB UI nicht mehr erreichbar war. Alle Docker waren auch nicht mehr erreichbar. Das einzige was geholfen hat war ein Hardreset des Servers.
Nachfolgend noch die diagnose Datei - kann mir vielleicht jemand Helfen um die Ursache zu finden.
tower-diagnostics-20220421-1541.zip
Folgende Fehler noch entdeckt:
Apr 21 16:06:12 Tower kernel: WARNING: CPU: 1 PID: 28235 at net/netfilter/nf_conntrack_core.c:1179 __nf_conntrack_confirm+0xb8/0x254 [nf_conntrack] Apr 21 16:06:12 Tower kernel: CPU: 1 PID: 28235 Comm: kworker/1:1 Tainted: G O 5.15.30-Unraid #1 Apr 21 16:06:12 Tower kernel: Call Trace: Apr 21 16:06:12 Tower kernel: <IRQ> Apr 21 16:06:12 Tower kernel: nf_conntrack_confirm+0x2f/0x36 [nf_conntrack] Apr 21 16:06:12 Tower kernel: nf_hook_slow+0x3e/0x93 Apr 21 16:06:12 Tower kernel: ? ip_protocol_deliver_rcu+0x112/0x112 Apr 21 16:06:12 Tower kernel: NF_HOOK.constprop.0+0x73/0xce Apr 21 16:06:12 Tower kernel: ? ip_protocol_deliver_rcu+0x112/0x112 Apr 21 16:06:12 Tower kernel: __netif_receive_skb_one_core+0x79/0x9a Apr 21 16:06:12 Tower kernel: process_backlog+0xab/0x143 Apr 21 16:06:12 Tower kernel: __napi_poll.constprop.0+0x2a/0x114 Apr 21 16:06:12 Tower kernel: net_rx_action+0xe8/0x1f2 Apr 21 16:06:12 Tower kernel: __do_softirq+0xef/0x218 Apr 21 16:06:12 Tower kernel: do_softirq+0x50/0x68 Apr 21 16:06:12 Tower kernel: </IRQ> Apr 21 16:06:12 Tower kernel: <TASK> Apr 21 16:06:12 Tower kernel: netif_rx_ni+0x53/0x85 Apr 21 16:06:12 Tower kernel: macvlan_broadcast+0x116/0x144 [macvlan] Apr 21 16:06:12 Tower kernel: macvlan_process_broadcast+0xc7/0x110 [macvlan] Apr 21 16:06:12 Tower kernel: process_one_work+0x198/0x27a Apr 21 16:06:12 Tower kernel: worker_thread+0x19c/0x240 Apr 21 16:06:12 Tower kernel: ? rescuer_thread+0x28b/0x28b Apr 21 16:06:12 Tower kernel: kthread+0xde/0xe3 Apr 21 16:06:12 Tower kernel: ? set_kthread_struct+0x32/0x32 Apr 21 16:06:12 Tower kernel: ret_from_fork+0x22/0x30 Apr 21 16:06:12 Tower kernel: </TASK> Apr 21 16:06:12 Tower kernel: ---[ end trace dd5673d1565ecd91 ]---
-
5 hours ago, jj1987 said:
Denn die AMD IGPU kannst du wenn überhaupt nur entweder für Unrais (und damit DOcker) ODER für die VM nutzen
Gibt es eigentlich irgendwo eine Anleitung,, wie man das bei einem Ryzen 3 2200G machen kann. Ich bin eigentlich mit meinem System soweit zufrieden es fehlt halt nur die APU in der VM. Im englischen Forum gibt es schon einiges dazu nur die Profis halten sich da zurück... Deshalb glaube ich es irgendwie nicht, dass es jemand schon zum laufen bekommen hat.
Etwas off topic das aber vielleicht hilft es auch bei der Entscheidung.
-
Quote
Oh, das habe ich überlesen - probiere es nachher!
Hab gerade auf 4.3 geupdated und funktioniert einwandfrei.
-
1
-
-
Oh, das habe ich überlesen - probiere es nachher!
QuoteIch hab's... Das Template hat die Variable RUN_OPTS und die hat wiederum den Standard-Wert "run options here", wie man hier noch sehen kann:
Danke 🙂
-
1
-
[SUPPORT] blakeblackshear - Frigate
in Docker Containers
Posted · Edited by snowy00
Hi, I have those error messages mostly at night in my frigate los. Is that a configuration issue or it results due to unstable stream?
Error
2024-03-22 01:50:27.305718991 [2024-03-22 01:50:27] ffmpeg.doorbird.detect ERROR : Last message repeated 1 times 2024-03-22 01:50:32.425703756 [2024-03-22 01:50:32] frigate.video ERROR : doorbird: Unable to read frames from ffmpeg process. 2024-03-22 01:50:32.425705908 [2024-03-22 01:50:32] frigate.video ERROR : doorbird: ffmpeg process is not running. exiting capture thread... 2024-03-22 01:50:37.319557649 [2024-03-22 01:50:37] watchdog.doorbird ERROR : Ffmpeg process crashed unexpectedly for doorbird. 2024-03-22 01:50:37.319567635 [2024-03-22 01:50:37] watchdog.doorbird ERROR : The following ffmpeg logs include the last 100 lines prior to exit. 2024-03-22 01:50:37.319611590 [2024-03-22 01:50:37] ffmpeg.doorbird.detect ERROR : rtsp://127.0.0.1:8554/doorbird: Invalid data found when processing input 2024-03-22 01:50:40.358113961 [2024-03-22 01:50:40] frigate.video ERROR : doorbird: Unable to read frames from ffmpeg process. 2024-03-22 01:50:40.358220082 [2024-03-22 01:50:40] frigate.video ERROR : doorbird: ffmpeg process is not running. exiting capture thread... 2024-03-22 01:50:47.325184697 [2024-03-22 01:50:47] watchdog.doorbird ERROR : Ffmpeg process crashed unexpectedly for doorbird. 2024-03-22 01:50:47.325202542 [2024-03-22 01:50:47] watchdog.doorbird ERROR : The following ffmpeg logs include the last 100 lines prior to exit. 2024-03-22 01:50:47.325211543 [2024-03-22 01:50:47] ffmpeg.doorbird.detect ERROR : [rtsp @ 0x5586f00bd100] method DESCRIBE failed: 404 Not Found 2024-03-22 01:50:47.325331886 [2024-03-22 01:50:47] ffmpeg.doorbird.detect ERROR : rtsp://127.0.0.1:8554/doorbird: Server returned 404 Not Found 2024-03-22 07:38:37.857388889 [2024-03-22 07:38:37] frigate.watchdog INFO : Detection appears to be stuck. Restarting detection process... 2024-03-22 07:38:37.857399654 [2024-03-22 07:38:37] root INFO : Waiting for detection process to exit gracefully... 2024-03-22 07:39:07.887486615 [2024-03-22 07:39:07] root INFO : Detection process didnt exit. Force killing... 2024-03-22 07:39:07.890948093 [2024-03-22 07:39:07] root INFO : Detection process has exited... 2024-03-22 07:39:07.901002708 [2024-03-22 07:39:07] detector.coral INFO : Starting detection process: 23549 2024-03-22 07:39:07.908221679 [2024-03-22 07:39:07] frigate.detectors.plugins.edgetpu_tfl INFO : Attempting to load TPU as usb 2024-03-22 07:39:10.726405811 [2024-03-22 07:39:10] frigate.detectors.plugins.edgetpu_tfl INFO : TPU found 2024-03-22 09:06:47.964609337 [2024-03-22 09:06:47] frigate.watchdog INFO : Detection appears to be stuck. Restarting detection process... 2024-03-22 09:06:47.964611572 [2024-03-22 09:06:47] root INFO : Waiting for detection process to exit gracefully... 2024-03-22 09:07:17.994352506 [2024-03-22 09:07:17] root INFO : Detection process didnt exit. Force killing... 2024-03-22 09:07:18.002138068 [2024-03-22 09:07:18] root INFO : Detection process has exited... 2024-03-22 09:07:18.012648975 [2024-03-22 09:07:18] detector.coral INFO : Starting detection process: 6156 2024-03-22 09:07:20.620061572 [2024-03-22 09:07:18] frigate.detectors.plugins.edgetpu_tfl INFO : Attempting to load TPU as usb 2024-03-22 09:07:20.622411381 [2024-03-22 09:07:20] frigate.detectors.plugins.edgetpu_tfl INFO : TPU found 2024-03-22 11:20:48.104918569 [2024-03-22 11:20:48] frigate.watchdog INFO : Detection appears to be stuck. Restarting detection process... 2024-03-22 11:20:48.104946957 [2024-03-22 11:20:48] root INFO : Waiting for detection process to exit gracefully... 2024-03-22 11:21:18.115158164 [2024-03-22 11:21:18] root INFO : Detection process didnt exit. Force killing... 2024-03-22 11:21:18.121643469 [2024-03-22 11:21:18] root INFO : Detection process has exited... 2024-03-22 11:21:18.132285625 [2024-03-22 11:21:18] detector.coral INFO : Starting detection process: 28132 2024-03-22 11:21:20.740620712 [2024-03-22 11:21:18] frigate.detectors.plugins.edgetpu_tfl INFO : Attempting to load TPU as usb 2024-03-22 11:21:20.742499265 [2024-03-22 11:21:20] frigate.detectors.plugins.edgetpu_tfl INFO : TPU foundfrigate config:
mqtt: enabled: true host: 192.168.178.32 user: *************** password: ****************** topic_prefix: frigate birdseye: enabled: False detectors: coral: type: edgetpu device: usb objects: track: - person - car - cat - dog - motorcycle - bicycle - umbrella filters: person: min_area: 5000 max_area: 24000000 go2rtc: streams: # doorbird: # - rtsp://******:**********@192.168.178.125:554/mpeg/media.amp doorbird: - rtsp://************:***********@192.168.178.125:554/mpeg/1080p/media.amp cameras: doorbird: enabled: true ffmpeg: hwaccel_args: preset-vaapi output_args: record: preset-record-generic inputs: - path: rtsp://127.0.0.1:8554/doorbird input_args: preset-rtsp-restream roles: - detect - record detect: enabled: true width: 1920 height: 1080 stationary: interval: 50 threshold: 50 max_frames: objects: car: 1000 record: enabled: true retain: days: 5 mode: all events: required_zones: - zone_hof - zone_street retain: default: 15 snapshots: enabled: true required_zones: - zone_hof - zone_street retain: default: 20 zones: zone_hof: coordinates: 1920,1080,1920,744,1764,737,1664,778,751,833,269,783,0,834,0,1080 objects: - person - car - cat - dog - motorcycle - bicycle - umbrella filters: car: threshold: 0.75 zone_street: coordinates: 574,833,1331,804,1863,684,1863,598,210,603,213,748,281,780 objects: - person motion: mask: - 0,0,299,786,0,843 - 0,0,1920,0,1920,427,1920,613,1256,614,211,578I also see those messages in the unraid log, that the coral sometimes connected and disconnected from the usb port. Is there any connection between the errors?
Mar 22 07:39:09 Tower kernel: usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd Mar 22 07:39:09 Tower kernel: usb 2-3: LPM exit latency is zeroed, disabling LPM. Mar 22 08:15:06 Tower emhttpd: read SMART /dev/sdc Mar 22 08:37:31 Tower emhttpd: spinning down /dev/sdc Mar 22 09:07:19 Tower kernel: usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd Mar 22 09:07:19 Tower kernel: usb 2-3: LPM exit latency is zeroed, disabling LPM. Mar 22 09:20:06 Tower emhttpd: read SMART /dev/sdc Mar 22 09:42:28 Tower emhttpd: spinning down /dev/sdc Mar 22 10:25:07 Tower emhttpd: read SMART /dev/sdc Mar 22 10:47:25 Tower emhttpd: spinning down /dev/sdc Mar 22 11:21:19 Tower kernel: usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd Mar 22 11:21:19 Tower kernel: usb 2-3: LPM exit latency is zeroed, disabling LPM.