ich vor ca. 1Monat mein debmatic (aktuell habe ich 3.69.7.108) auf den neusten Stand gebracht (Raspi4)
da hier auch pi-hole läuft hab ich letztens festgestellt das der Raspi nicht mehr reagiert (auch nicht auf SSH)
Strom and und ab hat es erstmal gefixt.
Das selbe war heute morgen aber wieder.. und es muss so ca um 2 Uhr nachts gewesen sein.
genau zu diesem Zeitpunkt habe ich im Syslog diese Meldung:
Code: Alles auswählen
Jun 28 02:18:18 Homematic-iobroker-pihole kernel: [830579.836275] raw-uart raw-uart: generic_raw_uart_handle_rx_char(): rx fifo full.
Jun 28 02:18:48 Homematic-iobroker-pihole kernel: [830579.836310] raw-uart raw-uart: generic_raw_uart_handle_rx_char(): rx fifo full.
Jun 28 02:19:12 Homematic-iobroker-pihole kernel: [830579.836319] raw-uart raw-uart: generic_raw_uart_handle_rx_char(): rx fifo full.
Jun 28 02:19:33 Homematic-iobroker-pihole kernel: [830579.836328] raw-uart raw-uart: generic_raw_uart_handle_rx_char(): rx fifo full.
Jun 28 02:19:58 Homematic-iobroker-pihole kernel: [830579.836336] raw-uart raw-uart: generic_raw_uart_handle_rx_char(): rx fifo full.
Code: Alles auswählen
2023-06-28 02:56:55,040 de.eq3.cbcs.transaction.management.TransactionManager WARN [vert.x-eventloop-thread-7] AP 3014F711A0001F5A4993FAB0: Task 2298301: No active task found for task resp
onse of type TimeoutTaskResponse. Ignoring task response ...
2023-06-28 02:39:09,517 io.vertx.core.impl.BlockedThreadChecker WARN [vertx-blocked-thread-checker] Thread Thread[vert.x-eventloop-thread-6,5,main] has been blocked for 3610 ms, time limit
is 2000 ms
2023-06-28 02:44:16,149 io.vertx.core.impl.BlockedThreadChecker WARN [vertx-blocked-thread-checker] Thread Thread[vert.x-eventloop-thread-0,5,main] has been blocked for 14327 ms, time limi
t is 2000 ms
io.vertx.core.VertxException: Thread blocked
at sun.nio.ch.EPoll.wait(Native Method) ~[?:?]
at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:120) ~[?:?]
at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:124) ~[?:?]
at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:141) ~[?:?]
at io.netty.channel.nio.SelectedSelectionKeySetSelector.select(SelectedSelectionKeySetSelector.java:68) ~[HMIPServer.jar:?]
at io.netty.channel.nio.NioEventLoop.select(NioEventLoop.java:810) ~[HMIPServer.jar:?]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:457) ~[HMIPServer.jar:?]
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:986) ~[HMIPServer.jar:?]
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) ~[HMIPServer.jar:?]
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[HMIPServer.jar:?]
at java.lang.Thread.run(Thread.java:829) ~[?:?]
2023-06-28 05:40:23,133 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-7] SYSTEM: 0 Accesspoints in Queue
2023-06-28 05:40:26,127 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-7] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used
2023-06-28 05:40:29,207 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-7] SYSTEM: Eventlistener Handler utilization: 0/50 used
2023-06-28 03:46:52,580 io.vertx.core.impl.BlockedThreadChecker WARN [vertx-blocked-thread-checker] Thread Thread[vert.x-eventloop-thread-6,5,main] has been blocked for 18564 ms, time limi
t is 2000 ms
io.vertx.core.VertxException: Thread blocked
at sun.nio.ch.EPoll.wait(Native Method) ~[?:?]
at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:120) ~[?:?]
at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:124) ~[?:?]
at sun.nio.ch.SelectorImpl.selectNow(SelectorImpl.java:146) ~[?:?]
at io.netty.channel.nio.SelectedSelectionKeySetSelector.selectNow(SelectedSelectionKeySetSelector.java:56) ~[HMIPServer.jar:?]
at io.netty.channel.nio.NioEventLoop.select(NioEventLoop.java:814) ~[HMIPServer.jar:?]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:457) ~[HMIPServer.jar:?]
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:986) ~[HMIPServer.jar:?]
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) ~[HMIPServer.jar:?]
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[HMIPServer.jar:?]
at java.lang.Thread.run(Thread.java:829) ~[?:?]
Zur info (iobroker ist auch installiert. das lief aber Jahre lang Problem los.
debmatic-info
Code: Alles auswählen
debmatic version: 3.69.7-108
OS: Debian GNU/Linux 11 (bullseye)
Kernel: 6.1.21-v8+ aarch64
Service Status: Running
Kernel modules: Available
Raw UART dev: Available
Rasp.Pi UART: Assigned to GPIO pins
HMRF Hardware: RPI-RF-MOD
Connected via: HB-RF-USB@usb-0000:01:00.0-1.3 (/dev/raw-uart)
Board serial: 5A4993FAB0
Radio MAC: 0xFFFAB0
HMIP Hardware: RPI-RF-MOD
Connected via: HB-RF-USB@usb-0000:01:00.0-1.3 (/dev/raw-uart)
SGTIN: 3014F711A0001F5A4993FAB0
Radio MAC: 0xB187B7
6.1.21-v8+
ich hab jetzt mal ein "sudo dpkg-reconfigure pivccu-modules-dkms" versucht..
da wir demnächst 3 Wochen nicht da sind währe es äuserst blöd wenn das passieren würde.
jemand vielleicht eine Idee was das sein könnte?