Testversion 3.55.5.20210113

[deimos]

Hi,

da kann man vortrefflich drüber streiten. Ich sehe es kritisch an, weil man hier ggf. wichtige Updates von Geräten verpasst und das in keinster Weise mitbekommt.

Viele Grüße
Alex

[MathiasZ]

@jmaus
Müsste man den Watchdog nicht so anpassen, daß er gleich zuschlägt wenn der die Verbindung zur HB-RF-ETH verliert?

Ich hab das vorher bereits erklärt und bin ausführlich darauf eingegangen. Gehe hin und lies.

@jmaus
Warum gleich beleidigt?
Erst mal lesen, dann wüsste man was man vorher (nicht) geschrieben hat.

[Matthias K.]

Guten Morgen,

heute Nacht um kurz vor 5 Uhr (nach ca. 3,5 Tagen Betrieb) ist meine Hyper-V-VM gecrasht. War nicht mehr per Ping erreichbar und auch sonst keine Kommunikation möglich (WebUI, RemoteScript-API, usw.), aber sie hat immerhin weiterhin munter auf meinen Syslog-Server geschrieben.

Ein Login direkt auf der Konsole (ALT+F2) war nicht möglich, Passwort falsch.

Auszug aus dem Syslog ab kurz vor Crash:

Code: Alles auswählen

Jan 22 04:46:13 192.168.81.220 root: check_mk_agent - connection accepted from 192.168.81.4:36108
Jan 22 04:46:49 192.168.81.220 local0:de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: 0 Accesspoints in Queue 
Jan 22 04:46:49 192.168.81.220 local0:de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Jan 22 04:46:49 192.168.81.220 local0:de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Jan 22 04:47:13 192.168.81.220 root: check_mk_agent - connection accepted from 192.168.81.4:36234
Jan 22 04:48:13 192.168.81.220 root: check_mk_agent - connection accepted from 192.168.81.4:36360
Jan 22 04:49:13 192.168.81.220 root: check_mk_agent - connection accepted from 192.168.81.4:36490
Jan 22 04:50:13 192.168.81.220 root: check_mk_agent - connection accepted from 192.168.81.4:36616
Jan 22 04:50:31 192.168.81.220 rfd: LGWPortWrapper::keepAliveThreadFunction(): Did not receive reply on keepalive.
Jan 22 04:50:34 192.168.81.220 rfd: LGWPortWrapper::ReadData(): Receive error
Jan 22 04:50:36 192.168.81.220 rfd: LGWPortWrapper::ReadData(): Receive error
Jan 22 04:50:37 192.168.81.220 cuxd[676]: sendbinrpc(192.168.81.229:2067) connect(7s) Connection timed out
Jan 22 04:50:50 192.168.81.220 cuxd[676]: sendbinrpc(192.168.81.228:2099) connect(7s) Connection timed out
Jan 22 04:50:57 192.168.81.220 cuxd[676]: sendbinrpc(192.168.81.228:2099) connect(7s) Connection timed out
Jan 22 04:51:02 192.168.81.220 rfd: (NEQ0219037) CCU2CommController::getDutyCycle(): Could not get DutyCycle from coprocessor.
Jan 22 04:51:03 192.168.81.220 rfd: (QEQ0692303) CCU2CommController::getDutyCycle(): Could not get DutyCycle from coprocessor.
Jan 22 04:51:03 192.168.81.220 dutycycle: DutyCycle-NEQ0219037, NAME: 'chagal-lgw', TYPE: HMLGW2, CONNECTED: 0, DC: -1 %
Jan 22 04:51:04 192.168.81.220 cuxd[676]: sendbinrpc(192.168.81.229:2067) connect(7s) Connection timed out
Jan 22 04:51:13 192.168.81.220 rfd: (NEQ0219037) CCU2CommController::getDutyCycle(): Could not get DutyCycle from coprocessor.
Jan 22 04:51:14 192.168.81.220 cuxd[676]: sendbinrpc(192.168.81.228:2099) connect(7s) Connection timed out
Jan 22 04:51:16 192.168.81.220 root: check_mk_agent - connection accepted from 192.168.81.4:36742
Jan 22 04:51:19 192.168.81.220 hs485d: XmlRpc transport failed (first try), retrying...
Jan 22 04:51:24 192.168.81.220 cuxd[676]: sendbinrpc(192.168.81.228:2099) connect(7s) Connection timed out
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255] rcu: INFO: rcu_preempt self-detected stall on CPU
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255] rcu: 	1-....: (59970 ticks this GP) idle=8a2/1/0x4000000000000004 softirq=5063692/5063693 fqs=14846 
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255] 	(t=60000 jiffies g=13754165 q=4653)
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255] NMI backtrace for cpu 1
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255] CPU: 1 PID: 520 Comm: k_hb_rf_eth_rec Tainted: G           O      5.4.86 #1
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007  05/18/2018
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255] Call Trace:
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  <IRQ>
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  dump_stack+0x8f/0xd0
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  ? lapic_can_unplug_cpu.cold+0x40/0x40
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  nmi_cpu_backtrace.cold+0x13/0x51
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  ? lapic_can_unplug_cpu.cold+0x40/0x40
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  nmi_trigger_cpumask_backtrace+0xc2/0xd0
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  rcu_dump_cpu_stacks+0x80/0xae
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  rcu_sched_clock_irq.cold+0x265/0x4f9
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  ? account_process_tick+0x28/0x160
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  ? hrtimer_run_queues+0x17/0x130
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  update_process_times+0x24/0x50
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  tick_sched_handle+0x34/0x50
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  tick_sched_timer+0x44/0x80
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  ? tick_sched_do_timer+0x60/0x60
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  __hrtimer_run_queues+0xf6/0x2c0
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  hrtimer_interrupt+0x118/0x240
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  hv_stimer0_vector_handler+0x4f/0xa0
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  hv_stimer0_callback_vector+0xf/0x20
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255] RIP: 0010:hv_qlock_wait+0x6d/0x80
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255] Code: 03 00 66 90 41 f7 c4 00 02 00 00 75 13 4c 89 e7 57 9d 0f 1f 44 00 00 5b 5d 41 5c e9 dd 2c 13 00 e8 b8 2d 13 00 4c 89 e7 57 9d <0f> 1f 44 00 00 5b 5d 41 5c c3 66 0f 1f 84 00 00 00 00 00 0f 1f 44
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255] RSP: 0018:ffffa3c200298e20 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff12
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255] RAX: 0000000000000102 RBX: 0000000000000003 RCX: 00000000400000f0
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000246
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255] RBP: ffffffffc0102ae8 R08: ffff8f6efffe7480 R09: 0000000000000044
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255] R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000246
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255] R13: 0000000000000001 R14: 0000000000000100 R15: 0000000000080000
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  ? hv_stimer0_callback_vector+0xa/0x20
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  __pv_queued_spin_lock_slowpath+0x282/0x2c0
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  _raw_spin_lock+0x2c/0x30
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  hb_rf_eth_send_msg+0xee/0x150 [hb_rf_eth]
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  hb_rf_eth_send_gpio+0x4b/0x70 [hb_rf_eth]
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  tasklet_action_common.isra.0+0x7e/0x140
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  __do_softirq+0x13c/0x38a
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  irq_exit+0xb4/0xd0
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  hv_stimer0_vector_handler+0x76/0xa0
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  hv_stimer0_callback_vector+0xf/0x20
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  </IRQ>
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255] RIP: 0010:udp_sendmsg+0x24d/0xb10
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255] Code: 0f 84 e4 05 00 00 0f b7 95 02 ff ff ff 44 8b 4f 10 c7 85 c0 fe ff ff 00 00 00 00 66 83 fa ff 0f 84 61 02 00 00 49 8b 44 24 60 <83> e2 1e f6 c4 20 75 0b 41 f6 47 48 04 0f 84 4e 05 00 00 c7 85 c0
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255] RSP: 0018:ffffa3c20040bcb0 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff12
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255] RAX: 0000000001000100 RBX: 0000000000000000 RCX: 00000000ffffffff
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255] RBP: ffffa3c20040be20 R08: 00000000dc51a8c0 R09: 00000000e051a8c0
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255] R10: ffffa3c20040be38 R11: 0000000000000004 R12: ffff8f6ef5bc5d80
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255] R13: 0000000000000004 R14: 0000000000000004 R15: ffffa3c20040be60
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  ? ip_do_fragment+0x4d0/0x4d0
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  ? kmem_cache_free+0x227/0x290
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  ? udp_recvmsg+0x1f9/0x520
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  ? inet_recvmsg+0x119/0x130
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  ? sock_sendmsg+0x41/0x60
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  sock_sendmsg+0x41/0x60
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  hb_rf_eth_send_msg+0x104/0x150 [hb_rf_eth]
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  hb_rf_eth_recv_threadproc+0x134/0x1e0 [hb_rf_eth]
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  kthread+0x122/0x160
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  ? hb_rf_eth_try_connect+0x1a0/0x1a0 [hb_rf_eth]
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  ? kthread_park+0x90/0x90
Jan 22 04:51:27 192.168.81.220 kernel: [285650.079255]  ret_from_fork+0x27/0x50
Jan 22 04:51:30 192.168.81.220 hs485d: XmlRpcClient error calling event({[methodName:"event",params:{"nr_G77eL3_BidCos-Wired","CENTRAL","PONG","nr"}]}) on http://192.168.81.229:2068/RPC2:
Jan 22 04:51:30 192.168.81.220 hs485d: XmlRpc transport error
Jan 22 04:51:30 192.168.81.220 hs485d: XmlRpcClient error calling event({[methodName:"event",params:{"BidCos-Wired","CENTRAL","PONG","nr"}]}) on http://192.168.81.228:2098/RPC2:
Jan 22 04:51:30 192.168.81.220 hs485d: XmlRpc transport error
Jan 22 04:51:31 192.168.81.220 cuxd[676]: sendbinrpc(192.168.81.228:2099) connect(7s) Connection timed out
Jan 22 04:51:38 192.168.81.220 cuxd[676]: sendbinrpc(192.168.81.229:2067) connect(7s) Connection timed out
Jan 22 04:51:46 192.168.81.220 cuxd[676]: sendbinrpc(192.168.81.228:2099) connect(7s) Connection timed out
Jan 22 04:51:49 192.168.81.220 local0:de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: 0 Accesspoints in Queue 
Jan 22 04:51:49 192.168.81.220 local0:de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Jan 22 04:51:49 192.168.81.220 local0:de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Jan 22 04:51:50 192.168.81.220 rfd: (NEQ0219037) CCU2CommController::getDutyCycle(): Could not get DutyCycle from coprocessor.
Jan 22 04:51:51 192.168.81.220 rfd: (QEQ0692303) CCU2CommController::getDutyCycle(): Could not get DutyCycle from coprocessor.
Jan 22 04:51:52 192.168.81.220 rfd: XmlRpc transport failed (first try), retrying...
Jan 22 04:51:53 192.168.81.220 cuxd[676]: sendbinrpc(192.168.81.229:2067) connect(7s) Connection timed out
Jan 22 04:52:00 192.168.81.220 rfd: (NEQ0219037) CCU2CommController::getDutyCycle(): Could not get DutyCycle from coprocessor.
Jan 22 04:52:01 192.168.81.220 rfd: (QEQ0692303) CCU2CommController::getDutyCycle(): Could not get DutyCycle from coprocessor.
Jan 22 04:52:02 192.168.81.220 dutycycle: DutyCycle-NEQ0219037, NAME: 'chagal-lgw', TYPE: HMLGW2, CONNECTED: 0, DC: -1 %
Jan 22 04:52:02 192.168.81.220 cuxd[676]: sendbinrpc(192.168.81.229:2067) connect(7s) Connection timed out
Jan 22 04:52:10 192.168.81.220 cuxd[676]: sendbinrpc(192.168.81.228:2099) connect(7s) Connection timed out
Jan 22 04:52:13 192.168.81.220 root: check_mk_agent - connection accepted from 192.168.81.4:36868
Jan 22 04:52:17 192.168.81.220 cuxd[676]: sendbinrpc(192.168.81.229:2067) connect(7s) Connection timed out
Jan 22 04:52:22 192.168.81.220 rfd: XmlRpc transport failed (first try), retrying...
Jan 22 04:52:31 192.168.81.220 cuxd[676]: sendbinrpc(192.168.81.228:2099) connect(7s) Connection timed out
Jan 22 04:52:32 192.168.81.220 rfd: XmlRpcClient error calling event({[methodName:"event",params:{"nr_G77eL3_BidCos-RF","CENTRAL","PONG","nr"}]}) on http://192.168.81.229:2068/RPC2:
Jan 22 04:52:32 192.168.81.220 rfd: XmlRpc transport error
Jan 22 04:52:38 192.168.81.220 cuxd[676]: sendbinrpc(192.168.81.228:2099) connect(7s) Connection timed out
Jan 22 04:52:45 192.168.81.220 cuxd[676]: sendbinrpc(192.168.81.228:2099) connect(7s) Connection timed out
Jan 22 04:52:46 192.168.81.220 rfd: UnifiedLanCommController::connect(): Unable to connect.
Jan 22 04:52:51 192.168.81.220 rfd: UnifiedLanCommController::connect(): Unable to connect.
Jan 22 04:52:51 192.168.81.220 rfd: LGWPortWrapper::keepAliveThreadFunction(): Cannot connect.
Jan 22 04:52:52 192.168.81.220 cuxd[676]: sendbinrpc(192.168.81.229:2067) connect(7s) Connection timed out
Jan 22 04:52:52 192.168.81.220 rfd: (CCU2LGW001) CCU2CommController::getDutyCycle(): Could not get DutyCycle from coprocessor.
Jan 22 04:52:52 192.168.81.220 rfd: (NEQ0219037) CCU2CommController::getDutyCycle(): Could not get DutyCycle from coprocessor.
Jan 22 04:52:52 192.168.81.220 rfd: XmlRpc transport failed (first try), retrying...
Jan 22 04:52:53 192.168.81.220 rfd: (QEQ0692303) CCU2CommController::getDutyCycle(): Could not get DutyCycle from coprocessor.
Jan 22 04:52:54 192.168.81.220 rfd: LGWPortWrapper::ReadData(): Receive error
Jan 22 04:52:56 192.168.81.220 rfd: UnifiedLanCommController::connect(): Unknown problem.
Jan 22 04:52:59 192.168.81.220 cuxd[676]: sendbinrpc(192.168.81.228:2099) connect(7s) Connection timed out
Jan 22 04:53:00 192.168.81.220 rfd: (CCU2LGW001) CCU2CommController::getDutyCycle(): Could not get DutyCycle from coprocessor.
Jan 22 04:53:00 192.168.81.220 rfd: (NEQ0219037) CCU2CommController::getDutyCycle(): Could not get DutyCycle from coprocessor.
Jan 22 04:53:01 192.168.81.220 rfd: (QEQ0692303) CCU2CommController::getDutyCycle(): Could not get DutyCycle from coprocessor.
Jan 22 04:53:02 192.168.81.220 dutycycle: DutyCycle-CCU2LGW001, NAME: 'chagal-lgw2', TYPE: HMLGW2, CONNECTED: 0, DC: -1 %
Jan 22 04:53:04 192.168.81.220 dutycycle: DutyCycle-NEQ0219037, NAME: 'chagal-lgw', TYPE: HMLGW2, CONNECTED: 0, DC: -1 %
Jan 22 04:53:06 192.168.81.220 cuxd[676]: sendbinrpc(192.168.81.229:2067) connect(7s) Connection timed out
Jan 22 04:53:13 192.168.81.220 cuxd[676]: sendbinrpc(192.168.81.228:2099) connect(7s) Connection timed out
Jan 22 04:53:19 192.168.81.220 rfd: (CCU2LGW001) CCU2CommController::getDutyCycle(): Could not get DutyCycle from coprocessor.
Jan 22 04:53:20 192.168.81.220 cuxd[676]: sendbinrpc(192.168.81.229:2067) connect(7s) Connection timed out
Jan 22 04:53:21 192.168.81.220 rfd: (CCU2LGW001) CCU2CommController::getDutyCycle(): Could not get DutyCycle from coprocessor.
Jan 22 04:53:22 192.168.81.220 root: check_mk_agent - connection accepted from 192.168.81.4:37016
Jan 22 04:53:29 192.168.81.220 hs485d: XmlRpc transport failed (first try), retrying...
Jan 22 04:53:31 192.168.81.220 cuxd[676]: sendbinrpc(192.168.81.229:2067) connect(7s) Connection timed out
Jan 22 04:53:39 192.168.81.220 hs485d: XmlRpcClient error calling event({[methodName:"event",params:{"nr_G77eL3_BidCos-Wired","OEQ2304206:3","LEVEL",1.000000}]}) on http://192.168.81.229:2068/RPC2:
Jan 22 04:53:39 192.168.81.220 hs485d: XmlRpc transport error
Jan 22 04:53:48 192.168.81.220 cuxd[676]: sendbinrpc(192.168.81.229:2067) connect(7s) Connection timed out
Jan 22 04:53:49 192.168.81.220 hs485d: XmlRpc transport failed (first try), retrying...
Jan 22 04:53:51 192.168.81.220 rfd: (CCU2LGW001) CCU2CommController::getDutyCycle(): Could not get DutyCycle from coprocessor.
Jan 22 04:53:51 192.168.81.220 rfd: (NEQ0219037) CCU2CommController::getDutyCycle(): Could not get DutyCycle from coprocessor.
Jan 22 04:53:52 192.168.81.220 rfd: (QEQ0692303) CCU2CommController::getDutyCycle(): Could not get DutyCycle from coprocessor.
Jan 22 04:53:59 192.168.81.220 cuxd[676]: sendbinrpc(192.168.81.228:2099) connect(7s) Connection timed out
Jan 22 04:54:00 192.168.81.220 rfd: (CCU2LGW001) CCU2CommController::getDutyCycle(): Could not get DutyCycle from coprocessor.
Jan 22 04:54:00 192.168.81.220 rfd: (NEQ0219037) CCU2CommController::getDutyCycle(): Could not get DutyCycle from coprocessor.
Jan 22 04:54:01 192.168.81.220 rfd: (QEQ0692303) CCU2CommController::getDutyCycle(): Could not get DutyCycle from coprocessor.
Jan 22 04:54:03 192.168.81.220 dutycycle: DutyCycle-CCU2LGW001, NAME: 'chagal-lgw2', TYPE: HMLGW2, CONNECTED: 0, DC: -1 %
Jan 22 04:54:04 192.168.81.220 dutycycle: DutyCycle-NEQ0219037, NAME: 'chagal-lgw', TYPE: HMLGW2, CONNECTED: 0, DC: -1 %
Jan 22 04:54:11 192.168.81.220 cuxd[676]: sendbinrpc(192.168.81.228:2099) connect(7s) Connection timed out
Jan 22 04:54:11 192.168.81.220 cuxd[676]: sendbinrpc(192.168.81.229:2067) - write() Connection refused
Jan 22 04:54:17 192.168.81.220 root: check_mk_agent - connection accepted from 192.168.81.4:37144
Jan 22 04:54:18 192.168.81.220 cuxd[676]: sendbinrpc(192.168.81.229:2067) connect(7s) Connection timed out
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255] rcu: INFO: rcu_preempt self-detected stall on CPU
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255] rcu: 	1-....: (239828 ticks this GP) idle=8a2/1/0x4000000000000004 softirq=5063692/5063693 fqs=59623 
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255] 	(t=240003 jiffies g=13754165 q=24722)
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255] NMI backtrace for cpu 1
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255] CPU: 1 PID: 520 Comm: k_hb_rf_eth_rec Tainted: G           O      5.4.86 #1
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007  05/18/2018
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255] Call Trace:
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  <IRQ>
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  dump_stack+0x8f/0xd0
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  ? lapic_can_unplug_cpu.cold+0x40/0x40
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  nmi_cpu_backtrace.cold+0x13/0x51
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  ? lapic_can_unplug_cpu.cold+0x40/0x40
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  nmi_trigger_cpumask_backtrace+0xc2/0xd0
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  rcu_dump_cpu_stacks+0x80/0xae
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  rcu_sched_clock_irq.cold+0x265/0x4f9
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  ? account_process_tick+0x28/0x160
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  ? hrtimer_run_queues+0x17/0x130
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  update_process_times+0x24/0x50
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  tick_sched_handle+0x34/0x50
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  tick_sched_timer+0x44/0x80
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  ? tick_sched_do_timer+0x60/0x60
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  __hrtimer_run_queues+0xf6/0x2c0
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  hrtimer_interrupt+0x118/0x240
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  hv_stimer0_vector_handler+0x4f/0xa0
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  hv_stimer0_callback_vector+0xf/0x20
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255] RIP: 0010:hv_qlock_wait+0x6d/0x80
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255] Code: 03 00 66 90 41 f7 c4 00 02 00 00 75 13 4c 89 e7 57 9d 0f 1f 44 00 00 5b 5d 41 5c e9 dd 2c 13 00 e8 b8 2d 13 00 4c 89 e7 57 9d <0f> 1f 44 00 00 5b 5d 41 5c c3 66 0f 1f 84 00 00 00 00 00 0f 1f 44
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255] RSP: 0018:ffffa3c200298e20 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff12
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255] RAX: 0000000000000102 RBX: 0000000000000003 RCX: 00000000400000f0
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000246
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255] RBP: ffffffffc0102ae8 R08: ffff8f6efffe7480 R09: 0000000000000044
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255] R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000246
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255] R13: 0000000000000001 R14: 0000000000000100 R15: 0000000000080000
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  ? hv_stimer0_callback_vector+0xa/0x20
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  __pv_queued_spin_lock_slowpath+0x282/0x2c0
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  _raw_spin_lock+0x2c/0x30
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  hb_rf_eth_send_msg+0xee/0x150 [hb_rf_eth]
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  hb_rf_eth_send_gpio+0x4b/0x70 [hb_rf_eth]
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  tasklet_action_common.isra.0+0x7e/0x140
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  __do_softirq+0x13c/0x38a
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  irq_exit+0xb4/0xd0
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  hv_stimer0_vector_handler+0x76/0xa0
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  hv_stimer0_callback_vector+0xf/0x20
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  </IRQ>
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255] RIP: 0010:udp_sendmsg+0x24d/0xb10
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255] Code: 0f 84 e4 05 00 00 0f b7 95 02 ff ff ff 44 8b 4f 10 c7 85 c0 fe ff ff 00 00 00 00 66 83 fa ff 0f 84 61 02 00 00 49 8b 44 24 60 <83> e2 1e f6 c4 20 75 0b 41 f6 47 48 04 0f 84 4e 05 00 00 c7 85 c0
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255] RSP: 0018:ffffa3c20040bcb0 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff12
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255] RAX: 0000000001000100 RBX: 0000000000000000 RCX: 00000000ffffffff
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255] RBP: ffffa3c20040be20 R08: 00000000dc51a8c0 R09: 00000000e051a8c0
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255] R10: ffffa3c20040be38 R11: 0000000000000004 R12: ffff8f6ef5bc5d80
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255] R13: 0000000000000004 R14: 0000000000000004 R15: ffffa3c20040be60
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  ? ip_do_fragment+0x4d0/0x4d0
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  ? kmem_cache_free+0x227/0x290
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  ? udp_recvmsg+0x1f9/0x520
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  ? inet_recvmsg+0x119/0x130
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  ? sock_sendmsg+0x41/0x60
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  sock_sendmsg+0x41/0x60
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  hb_rf_eth_send_msg+0x104/0x150 [hb_rf_eth]
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  hb_rf_eth_recv_threadproc+0x134/0x1e0 [hb_rf_eth]
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  kthread+0x122/0x160
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  ? hb_rf_eth_try_connect+0x1a0/0x1a0 [hb_rf_eth]
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  ? kthread_park+0x90/0x90
Jan 22 04:54:27 192.168.81.220 kernel: [285830.082255]  ret_from_fork+0x27/0x50
Jan 22 04:54:29 192.168.81.220 cuxd[676]: sendbinrpc(192.168.81.228:2099) connect(7s) Connection timed out
Jan 22 04:54:36 192.168.81.220 cuxd[676]: sendbinrpc(192.168.81.229:2067) connect(7s) Connection timed out
Jan 22 04:54:46 192.168.81.220 cuxd[676]: sendbinrpc(192.168.81.228:2099) connect(7s) Connection timed out
Jan 22 04:54:47 192.168.81.220 rfd: (CCU2LGW001) CCU2CommController::getDutyCycle(): Could not get DutyCycle from coprocessor.
Jan 22 04:54:47 192.168.81.220 rfd: (NEQ0219037) CCU2CommController::getDutyCycle(): Could not get DutyCycle from coprocessor.
Jan 22 04:54:48 192.168.81.220 rfd: (QEQ0692303) CCU2CommController::getDutyCycle(): Could not get DutyCycle from coprocessor.

Das ging dann immer so weiter, ca. jede Minute die "kernel:"-Meldungen und nachfolgend die weiteren Kommunikationsfehler.
Ich hab dann kurz nach 6 Uhr hart neugestartet, seitdem läuft wieder alles.

Kann da jemand rauslesen, woran das lag?

System:

• RaspberryMatic 3.55.5.20210118 OVA auf Hyper-V
• AddOns: check_mk_agent 1.3, CUxD 2.5.1 x86, JP HB Devices 3.3, Programmedrucken 2.3, XML-API 1.20
• RPI-RF-MOD auf HB-RF-ETH
• 1x Original Lan-Gateway (das eckige)
• 1x CCU2 umgebaut zum Lan-GW
• 1x HAP

[MathiasZ]

Gerade eben den Raspberry PI4 auf 3.55.10 hoch gezogen.
Ich habe bewußt die HB-RF-ETH nicht angeschlossen.
Der watchdog hat sofort gemeldet, dass die HB-RF-ETH nicht erreichbar ist

[MathiasZ]

@jmaus
Ich habe mir eben die 3.55.10.20210124
herunter geladen. Ich bleibe aber auf der
3.55.10.20210122 stehen.
Vielleicht die falsche Version eingegeben,
oder läuft was anderes schief?

[Baxxy]

Ich bleibe aber auf der
3.55.10.20210122 stehen.

Die Pi4 Version ließ sich bei mir problemlos von 3.55.10.20210122 auf 3.55.10.20210124 updaten.

[MathiasZ]

Wenn man die Firmware einspielt, nicht den Sicherheits-Hinweis bestätigt und sich dann vom Handy aus anmeldet, kann es auch nicht gehen.
Asche über mein Haupt

[EddyS]

Hallo zusammen,
habe in der aktuellen Nightly Build Version 3.55.10.20210129 ein Darstellungsfehler gefunden.
In Einstellung / Geräte werden, wenn man die Geräte aufklappt, ein Kanal 0 angezeigt.
...Oder gibt es eine Grund dafür

desweiteren wird die Aufzählung zb. bei der Virtuelle Fernbedienung die Zahl nicht richtig angezeigt.
Verschwindet am unteren Rand. Das ist bei der aktuelle Version 3.55.5.20201226 auch schon...
Ist jetzt nichts schlimmes, wollte ich nur mal anmerken....

...Danke an alle für die gute Arbeit die hier geleistet wird...

[jmaus]

Hallo zusammen,
habe in der aktuellen Nightly Build Version 3.55.10.20210129 ein Darstellungsfehler gefunden.
In Einstellung / Geräte werden, wenn man die Geräte aufklappt, ein Kanal 0 angezeigt.
...Oder gibt es eine Grund dafür

"It's not a bug, it's a feature!"

Mit der nächsten kommenden Version werden automatisch die Maintenance-Kanäle (:0) von HomeMatic und homematicIP Geräte mit angezeigt werden ohne das man die wie bisher selbst aufwendig/unlogisch mit "Baumstruktur aufklappen" anzeigen lassen muss. Also nicht davon stören lassen, das ist ein neues Feature!

desweiteren wird die Aufzählung zb. bei der Virtuelle Fernbedienung die Zahl nicht richtig angezeigt.
Verschwindet am unteren Rand. Das ist bei der aktuelle Version 3.55.5.20201226 auch schon...
Ist jetzt nichts schlimmes, wollte ich nur mal anmerken....

Das ist sogar nicht nur in RaspberryMatic so, sondern auch bei der Standard CCU3 Firmware. Ist halt nen genereller WebUI bug, der aber IMHO vernachlässigbar ist. Du kannst dafür aber gerne im RaspberryMatic GitHub ein entsprechendes Ticket dafür aufmachen, damit das nicht in Vergessenheit gerät.

[MathiasZ]

Ist meiner Meinung nach gar kein Bug!
Im Gegenteil:
Man kann die Zwischenstecker mit Leistungsmessung direkt auslesen, ob ein Kom.-Fehler vorliegt.
Wenn Kom.-Fehler dann Stromausfall.
Bisher lief das nur mit einem Skript in Verbindung einer SysVar mit einer Kanalauswahl.
Läuft hier bestens.

Hier nochmal mit der SysVar:

Code: Alles auswählen

if (dom.GetObject("BidCos-RF.LEQ1234567:0.UNREACH").Value() == false) {
   dom.GetObject("Kommunikation").State("true");
}else {
   dom.GetObject("Kommunikation").State("false");
}

SysVar:

Programm:

Gruß,
Mathias