Hi,
Mein 24/7 RPI4 hat gelegentlich kein Netz mehr.
Dann komme ich nicht mehr auf den VDR, der auf dem RPI4 läuft. Und umgekehrt. Internet geht noch.
Etwas Geduld, und dann geht es wieder.
Im Log sieht man, dass der RPI4 auch nicht auf andere Rechner kommt. Sonst fand ich nichts auffälliges. Sieht so aus:
Code
Mar 17 14:15:27 rpi4s connmand[420]: ntp: adjust (slew): -0.000089 sec
Mar 17 14:17:01 rpi4s CRON[688546]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Mar 17 14:19:02 rpi4s vdr: [688582] epg data writer thread started (pid=680847, tid=688582, prio=low)
Mar 17 14:19:02 rpi4s vdr: [688582] epg data writer thread ended (pid=680847, tid=688582)
Mar 17 14:19:57 rpi4s vdr: [680868] SVDRP sp < 192.168.178.56:6419 timeout while waiting for response from 'rpi3'
Mar 17 14:20:21 rpi4s vdr: [680866] tvscraper: start scraping epg
Mar 17 14:20:21 rpi4s vdr: [680866] tvscraper: epg scraping done
Mar 17 14:20:23 rpi4s vdr: [680867] SVDRP sp < rpi3 timeout on connection
Mar 17 14:20:23 rpi4s vdr: [680867] SVDRP sp < rpi3 connection closed
Mar 17 14:20:23 rpi4s vdr: [680867] SVDRP sp < rpi3 server destroyed
Mar 17 14:20:27 rpi4s vdr: [680868] SVDRP sp < 192.168.178.56:6419 timeout while waiting for response from 'rpi3'
Mar 17 14:20:27 rpi4s vdr: [680868] ERROR: can't send 'POLL sp TIMERS' to 'rpi3'
Mar 17 14:24:38 rpi4s kernel: [1287645.069856] usb 2-2.2: reset SuperSpeed USB device number 4 using xhci_hcd
Mar 17 14:24:38 rpi4s udisksd[463]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/WDC_WD40EZRX_00SPEB0_WD_WCC4E1381832: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#0120010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#012 (g-io-error-quark, 0)
Mar 17 14:24:58 rpi4s vdr: [680868] SVDRP sp < 192.168.178.56:6419 timeout while waiting for response from 'rpi3'
Mar 17 14:25:21 rpi4s vdr: [680866] tvscraper: start scraping epg
Mar 17 14:25:21 rpi4s vdr: [680866] tvscraper: Schedule was not changed, skipping scan
Mar 17 14:25:21 rpi4s vdr: [680866] tvscraper: epg scraping done
Mar 17 14:25:27 rpi4s vdr: [680868] SVDRP sp < 192.168.178.56:6419 timeout while waiting for response from 'rpi3'
Mar 17 14:25:27 rpi4s vdr: [680868] ERROR: can't send 'POLL sp TIMERS' to 'rpi3'
Mar 17 14:28:00 rpi4s vdr: [680857] EPGSearch: timer conflict check started
Mar 17 14:28:00 rpi4s vdr: [680857] EPGSearch: timer conflict check finished
Mar 17 14:28:00 rpi4s vdr: [680856] EPGSearch: search timer update started
Mar 17 14:28:01 rpi4s vdr: [680856] EPGSearch: search timer update finished
Mar 17 14:29:03 rpi4s vdr: [688715] epg data writer thread started (pid=680847, tid=688715, prio=low)
Mar 17 14:29:04 rpi4s vdr: [688715] epg data writer thread ended (pid=680847, tid=688715)
Mar 17 14:29:57 rpi4s vdr: [680868] SVDRP sp < 192.168.178.56:6419 timeout while waiting for response from 'rpi3'
Mar 17 14:30:01 rpi4s CRON[688731]: (root) CMD (sh /opt/spindown/spindown_all.sh)
Mar 17 14:30:22 rpi4s vdr: [680866] tvscraper: start scraping epg
Mar 17 14:30:22 rpi4s vdr: [680866] tvscraper: epg scraping done
Mar 17 14:30:27 rpi4s dhcpcd[675]: eth0: part of Router Advertisement expired
Mar 17 14:30:28 rpi4s vdr: [680868] SVDRP sp < 192.168.178.56:6419 timeout while waiting for response from 'rpi3'
Mar 17 14:30:28 rpi4s vdr: [680868] ERROR: can't send 'POLL sp TIMERS' to 'rpi3'
Mar 17 14:34:58 rpi4s vdr: [680868] SVDRP sp < 192.168.178.56:6419 timeout while waiting for response from 'rpi3'
Mar 17 14:35:19 rpi4s vdr: [680868] SVDRP sp < 192.168.178.56:6419 lost connection to remote server 'rpi3'
Mar 17 14:35:19 rpi4s vdr: [680868] SVDRP sp > 192.168.178.56:6419 client destroyed for 'rpi3'
Mar 17 14:35:23 rpi4s vdr: [680866] tvscraper: start scraping epg
Mar 17 14:35:23 rpi4s vdr: [680866] tvscraper: Schedule was not changed, skipping scan
Mar 17 14:35:23 rpi4s vdr: [680866] tvscraper: epg scraping done
Mar 17 14:39:01 rpi4s CRON[688939]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then
/usr/lib/php/sessionclean; fi)
Mar 17 14:39:04 rpi4s vdr: [688940] epg data writer thread started (pid=680847, tid=688940, prio=low)
Mar 17 14:39:05 rpi4s vdr: [688940] epg data writer thread ended (pid=680847, tid=688940)
Mar 17 14:39:45 rpi4s systemd[1]: Starting Clean php session files...
Mar 17 14:39:46 rpi4s systemd[1]: phpsessionclean.service: Succeeded.
Mar 17 14:39:46 rpi4s systemd[1]: Finished Clean php session files.
Mar 17 14:40:24 rpi4s vdr: [680866] tvscraper: start scraping epg
Mar 17 14:40:24 rpi4s vdr: [680866] tvscraper: epg scraping done
Mar 17 14:40:27 rpi4s dhcpcd[675]: eth0: fe80::7642:7fff:fe5f:81f4: router expired
Mar 17 14:40:27 rpi4s dhcpcd[675]: eth0: part of Router Advertisement expired
Mar 17 14:40:27 rpi4s dhcpcd[675]: eth0: deleting default route via fe80::7642:7fff:fe5f:81f4
Mar 17 14:41:23 rpi4s systemd-timesyncd[387]: Timed out waiting for reply from 213.239.234.28:123 (2.debian.pool.ntp.org).
Mar 17 14:41:33 rpi4s systemd-timesyncd[387]: Timed out waiting for reply from 136.243.177.133:123 (2.debian.pool.ntp.org).Mar 17 14:41:43 rpi4s systemd-timesyncd[387]: Timed out waiting for reply from 162.159.200.1:123 (2.debian.pool.ntp.org).
Mar 17 14:43:01 rpi4s connmand[420]: ntp: adjust (slew): +0.000534 sec
Mar 17 14:43:37 rpi4s dhcpcd[675]: eth0: adding default route via fe80::7642:7fff:fe5f:81f4Also um 14:15 war das Netz noch da.
14:19 war es weg.
um 14:43 ist das Netz wieder da.
Was kann da sein? In der Fritzbox habe ich nichts dazu gefunden.
Und Internet geht ja auch noch.
~Markus