raspibackup verliert Zugriff auf Fritz.nas

perry94 · May 2nd 2023

Hallo Forum,

hier erst mal Info zu meinem Pi und zum Linux:

Code

raspberrypi4-iob

Plattform                  linux
Betriebssystem             linux
Architektur                arm
CPUs                       4
Geschwindigkeit            1500 MHz
Modell                     ARMv7 Processor rev 3 (v7l)
RAM                        7.71 GB
System-Betriebszeit        1 T. 02:55:41
Node.js                    v14.21.3 (Empfohlene Version v18.16.0)
time                       1682953445827
timeOffset                 -120
Anzahl der Adapter         471
NPM                        6.14.18
Datenträgergröße           14.33 GB
freier Festplattenspeicher 9.07 GB
Aktive Instanzen           12
 
pi@raspberrypi4-iob:~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Description:    Raspbian GNU/Linux 10 (buster)
Release:        10
Codename:       buster
pi@raspberrypi4-iob:~ $

Display More

Hier nun mein Problem:

mit dem Skript "raspibackup" habe ich seit ca 3 Jahren regelmäßige Sicherungen auf dem Fritz.nas Laufwerk durchgeführt. Seit dem 06.03.2023 hat die Sicherung ihren Geist aufgegeben. Da ich mir keine Info habe zuschicken lassen, habe ich es erst vor kurzem festgestellt. Seit einigen Tagen versuche ich das Problem zu beseitigen. Bisher ohne Erfolg. Folgende Fehler bekomme ich angezeigt:

Code

pi@raspberrypi4-iob:~ $ cls
pi@raspberrypi4-iob:~ $ sudo umount /media/fritznas
umount: /media/fritznas: not mounted.

pi@raspberrypi4-iob:~ $ sudo mount    -t    cifs    -o    credentials=$HOME/.smbcredentials,vers=3.0,dir_mode=0777,file_mode=0777    //192.168.178.1/FRITZ.NAS/xxxxx/Sicherung/sich-pi-16gb/   /media/fritznas
pi@raspberrypi4-iob:~ $ cd /media/fritznas/
pi@raspberrypi4-iob:/media/fritznas $

pi@raspberrypi4-iob:/media/fritznas $ ls -l
drwxrwxrwx 2 root root      0 Apr 16 09:20 raspberrypi4-iob
-rw-rw-rw- 1 root root    105 Dez 23  2020 tt.txt
pi@raspberrypi4-iob:/media/fritznas $ rm tt.txt
rm: das Entfernen von 'tt.txt' ist nicht möglich: Datei oder Verzeichnis nicht gefunden

pi@raspberrypi4-iob:/media/fritznas $ cd raspberrypi4-iob/
pi@raspberrypi4-iob:/media/fritznas/raspberrypi4-iob $ ls -l
ls: Öffnen von Verzeichnis '.' nicht möglich: Datei oder Verzeichnis nicht gefunden

Display More

In der Fritz.box ist ein "user" angelegt auch mit den nötigen Rechten und der ist in den letzten Jahren nicht geändert worden.

Meine Vermutung weist auf Rechteprobleme hin ... aber ... . Vielleicht ist ja ein Linux Profi im Forum unterwegs und hat einen Tip für mich. Ich würde mich sehr freuen.

cu perry94

hyle · May 2nd 2023

Zeig mal die Ausgabe von ls -lisa /media/fritznas!

Mounte danach ggf. mal mit der zusätzlichen Option noserverino. Was passiert damit?

perry94 · May 2nd 2023

Moin hyle

vielen Dank für deine Rückmeldung. Hier das Gewünschte:

Code

pi@raspberrypi4-iob:~ $ ls -lisa /media/fritznas
insgesamt 757
10474459459077963225   0 drwxrwxrwx 2 root root      0 Apr 30 13:56 .
               16130   4 drwxr-xr-x 3 root root   4096 Dez 12  2020 ..
 8395528319575870234  40 -rw-rw-rw- 1 root root  37922 Jan 10  2021 20210101-Leerungstermine39459.ics
11156202359261982763 124 -rw-rw-rw- 1 root root 123243 Feb  5  2021 iobroker.2021-02-03.log
12686832390223169519  12 -rw-rw-rw- 1 root root  12269 Feb  5  2021 iobroker.2021-02-03.log.gz
 4441866145347627423 184 -rw-rw-rw- 1 root root 187573 Feb  5  2021 iobroker.2021-02-04.log
 1863671455899416088  16 -rw-rw-rw- 1 root root  15327 Feb  5  2021 iobroker.2021-02-04.log.gz
18098631744009814764  12 -rw-rw-rw- 1 root root  10728 Dez 21  2020 pishrink.sh
15160326902850351233   0 drwxrwxrwx 2 root root      0 Apr 16 09:20 raspberrypi4-iob
11113355665497211224 100 -rw-rw-rw- 1 root root 101621 Dez 21  2020 raspiBackupInstallUI.sh
 1048139343566181956 264 -rw-rw-rw- 1 root root 266883 Dez 21  2020 raspiBackup.sh
 1510353214680445414   1 -rw-rw-rw- 1 root root     10 Apr 30 13:56 tt1.txt
  332406888405987618   1 -rw-rw-rw- 1 root root    105 Dez 23  2020 tt.txt
pi@raspberrypi4-iob:~ $

pi@raspberrypi4-iob:~ $ sudo umount /media/fritznas
pi@raspberrypi4-iob:~ $ sudo umount /media/fritznas
umount: /media/fritznas: not mounted.
pi@raspberrypi4-iob:~ $ sudo mount    -t    cifs    -o    credentials=$HOME/.smbcredentials,vers=3.0,noserverino,dir_mode=0777,file_mode=0666    //192.168.178.1/FRITZ.NAS/Ordner/Ordner/Sicherung/sich-pi-16gb/   /media/fritznas
pi@raspberrypi4-iob:~ $ cd /media/fritznas/
pi@raspberrypi4-iob:/media/fritznas $ ls -l
insgesamt 753
-rw-rw-rw- 1 root root  37922 Jan 10  2021 20210101-Leerungstermine39459.ics
-rw-rw-rw- 1 root root 123243 Feb  5  2021 iobroker.2021-02-03.log
-rw-rw-rw- 1 root root  12269 Feb  5  2021 iobroker.2021-02-03.log.gz
-rw-rw-rw- 1 root root 187573 Feb  5  2021 iobroker.2021-02-04.log
-rw-rw-rw- 1 root root  15327 Feb  5  2021 iobroker.2021-02-04.log.gz
-rw-rw-rw- 1 root root  10728 Dez 21  2020 pishrink.sh
drwxrwxrwx 2 root root      0 Apr 16 09:20 raspberrypi4-iob
-rw-rw-rw- 1 root root 101621 Dez 21  2020 raspiBackupInstallUI.sh
-rw-rw-rw- 1 root root 266883 Dez 21  2020 raspiBackup.sh
-rw-rw-rw- 1 root root     10 Apr 30 13:56 tt1.txt
-rw-rw-rw- 1 root root    105 Dez 23  2020 tt.txt
pi@raspberrypi4-iob:/media/fritznas $ nano tt.txt
pi@raspberrypi4-iob:/media/fritznas $ cd raspberrypi4-iob/
-bash: cd: raspberrypi4-iob/: Datei oder Verzeichnis nicht gefunden

Display More

Mount mit Option noserverino hat keine Verbesserung gebracht.

Der Aufruf nano tt.txt ergibt

Code

[ Fehler beim Schreiben der Sperrdatei ./.tt.txt.swp: Datei oder Verzeichnis nicht gefunden ]

cu perry94

RTFM · May 2nd 2023

Wenn Du einen cifs (Windows) Mount mit sudo ausführst und keine uid= gid= Option setzt, wird der User root berechtigt, und nicht der User "user".

Servus !

daxb · May 2nd 2023

Quote from perry94

sudo mount -t cifs -o credentials=$HOME/.smbcredentials,vers=3.0,noserverino,dir_mode=0777,file_mode=0666 //192.168.178.1/FRITZ.NAS/Ordner/Ordner/Sicherung/sich-pi-16gb/ /media/fritznas

Dann sollte vers= und die flie/dir_mode Optionen überflüssig sein. Die Version wird automatisch ausgehandelt. Also, wenn du keinen speziellen Grund für die Optionen hast, kannst du diese weglassen. Die von RTFM genannten uid= und gid= machen allerdings Sinn.

Benutzt du tar oder dd als Backup Methode?

perry94 · May 2nd 2023

Hallo daxb

Quote from daxb

Benutzt du tar oder dd als Backup Methode?

Meine Sicherungsmethode ist "tar".

Quote from RTFM

Wenn Du einen cifs (Windows) Mount mit sudo ausführst und keine uid= gid= Option setzt, wird der User root berechtigt, und nicht der User "user".

Habe ich durchgeführt und hat leider keine Änderung ergeben.

Code

pi@raspberrypi4-iob:~ $ sudo umount /media/fritznas
pi@raspberrypi4-iob:~ $ sudo umount /media/fritznas
umount: /media/fritznas: not mounted.
pi@raspberrypi4-iob:~ $ sudo mount    -t    cifs    -o    credentials=$HOME/.smbcredentials,uid=1000,gid=1000  //192.168.178.1/FRITZ.NAS/Ordner/Ordner/Sicherung/sich-pi-16gb/   /media/fritznas
pi@raspberrypi4-iob:~ $ cd /media/fritznas/
pi@raspberrypi4-iob:/media/fritznas $ ls -l
drwxr-xr-x 2 pi pi      0 Apr 16 09:20 raspberrypi4-iob
-rwxr-xr-x 1 pi pi    105 Dez 23  2020 tt.txt
pi@raspberrypi4-iob:/media/fritznas $ nano tt.txt
pi@raspberrypi4-iob:/media/fritznas $ cd raspberrypi4-iob/
-bash: cd: raspberrypi4-iob/: Datei oder Verzeichnis nicht gefunden
pi@raspberrypi4-iob:/media/fritznas $

Display More

Der veränderte "mount" hat nicht das gewünschte Ergebnis erzielt.

Meine Fritz.Box ist eine 6591-Cabel, wobei "Unterstützung für SMBv1 aktivieren" aktiviert worden ist. Das war aber schon immer so. Vielleicht hilft dieser Hinweis.

cu perr94

hyle · May 2nd 2023

Quote from perry94

pi@raspberrypi4-iob:~ $ sudo mount -t cifs -o credentials=$HOME/.smbcredentials,uid=1000,gid=1000 //192.168.178.1/FRITZ.NAS/Ordner/Ordner/Sicherung/sich-pi-16gb/ /media/fritznas

So und jetzt noch noserverino mit rein und dann könnte es passen!

Btw. Zeig uns bitte immer ls -lisa statt nur ls -l! Wir wollen auch versteckte Dateien und die verwendeten Inodes sehen.

perry94 · May 2nd 2023

Hallo hyle

Quote from hyle

So und jetzt noch noserverino mit rein und dann könnte es passen!

leider keine Änderung sichbar:

Code

pi@raspberrypi4-iob:~ $ sudo umount /media/fritznas
pi@raspberrypi4-iob:~ $ sudo umount /media/fritznas
umount: /media/fritznas: not mounted.
pi@raspberrypi4-iob:~ $ sudo mount    -t    cifs    -o    credentials=$HOME/.smbcredentials,noserverino,uid=1000,gid=1000  //192.168.178.1/FRITZ.NAS/Ordner/Ordner/Sicherung/sich-pi-16gb/   /media/fritznas
pi@raspberrypi4-iob:~ $ cd /media/fritznas/
pi@raspberrypi4-iob:/media/fritznas $ ls -lisa
insgesamt 757
  897   0 drwxr-xr-x 2 pi   pi        0 Apr 30 13:56 .
16130   4 drwxr-xr-x 3 root root   4096 Dez 12  2020 ..
  907   1 -rwxr-xr-x 1 pi   pi      105 Dez 23  2020 tt.txt
pi@raspberrypi4-iob:/media/fritznas $ nano tt.txt
pi@raspberrypi4-iob:/media/fritznas $ cd raspberrypi4-iob/
pi@raspberrypi4-iob:/media/fritznas/raspberrypi4-iob $ ls -lisa
ls: Öffnen von Verzeichnis '.' nicht möglich: Datei oder Verzeichnis nicht gefunden
pi@raspberrypi4-iob:/media/fritznas/raspberrypi4-iob $

Display More

cu perry94

hyle · May 2nd 2023

Aber nano tt.txt funktioniert und Du kannst die Datei bearbeiten oder?

framp · May 2nd 2023

perry94 Du verstehst jetzt warum ich Dich auf dieses Forum verwiesen habe

Fuer alle Mitleser: Der TE hatte erst sein Problem auf meiner Kontakt Webseite die nun wirklich nicht fuer raspiBackup Fragen genutzt werden sollte plaziert, dann im ioBroker Forum als ioBroker Bug wo keiner natuerlich einen ioBroker Bug sah. Sowohl auf meiner Webseite als auch dann im ioBroker Thread habe ich immer wieder auf dieses Forum verwiesen weil ich weiss dass der TE hier guten Support bekommt . Zum Thema Samba/CIFS bin ich ein Noob und bin Euch dankbar dass Ihr dem TE helft

Ich kenne Samba nicht so genau aber kann es sein dass ein FW Upgrade in der Fritte das Problem verursacht? Irgendwo habe ich mal gelesen dass irgendeine Samba/CIFs Version nicht mehr standardmaessig unterstuetzt wird von den Fritten.

hyle Sollte der Thread nicht ins Backupforum verschoben werden?

hyle · May 2nd 2023

Quote from framp

Sollte der Thread nicht ins Backupforum verschoben werden?

Jain! Meiner Meinung nach geht es hier nur sekundär um Backups, primär ist das ein CIFS-Mountproblem auf einem Linuxsystem.

Wenn perry94 auf die Datei tt.txt zugreifen und diese bearbeiten kann, dann würde ich von einem Schaden im Dateisystem des an der Fritte angeschlossenen Laufwerks ausgehen und somit wär es dann auch kein Mountproblem mehr, sondern ein defektes Laufwerk usw. oder was auch immer in dieser Richtung passieren kann.

perry94 · May 2nd 2023

Hallo hyle,

Quote from hyle

Aber nano tt.txt funktioniert und Du kannst die Datei bearbeiten oder?

nein ... ich kann die Datei nicht bearbeiten.

Quote from framp

Du verstehst jetzt warum ich Dich auf dieses Forum verwiesen habe

ja ... du hattest Recht ... hier bin ich ( hoffe auf eine Lösung ) besser aufgehoben

Quote from hyle

... Schaden im Dateisystem des an der Fritte angeschlossenen Laufwerks ausgehen und somit wär es dann auch kein Mountproblem mehr, sondern ein defektes Laufwerk ...

Das Laufwerk war eine 2 Tbyte SSD ... da funkte es auch nicht mehr ab (wie gesagt) dem 06.03.2023 (vorher ohne Probleme) ... urplötzlich ohne eine Änderung an der Fritte oder sonstwo. Das das Laufwerk evt einen Schaden hat ... habe ich auch bedacht ... und eine neue SSD 4 tbyte installiert und eingebunden. Allerdings ohne Erfolg.

cu perry94

perry94 · May 2nd 2023

hyle

Code

nano tt.txt

 [ Fehler beim Schreiben der Sperrdatei ./.tt.txt.swp: Datei oder Verzeichnis nicht gefunden ]

cu perry94

hyle · May 2nd 2023

Btw. da ist vermutlich ein Punkt (.) vor tt.txt.swp zu viel. Ist aber auch möglich, dass Sperrdateien versteckt werden. Versuch mal rm tt.txt.swp!

Was passiert mit dem absoluten Pfad nano /media/fritznas/tt.txt?

raspbastler · May 2nd 2023

Alle Energiesparmaßnahmen der FRITZ!Box sollten ebenfalls deaktiviert werden, das kann manchmal zu langen Reaktionszeiten führen. Ergo: Datei kann nicht gefunden werden

perry94 · May 2nd 2023

Quote from hyle

... dass Sperrdateien versteckt werden. Versuch mal rm tt.txt.swp!

... Was passiert mit dem absoluten Pfad nano /media/fritznas/tt.txt?

bei beiden Versuchen

Code

pi@raspberrypi4-iob:/media/fritznas $ nano /media/fritznas/tt.txt
pi@raspberrypi4-iob:/media/fritznas $ rm tt.txt.swp
rm: das Entfernen von 'tt.txt.swp' ist nicht möglich: Datei oder Verzeichnis nicht gefunden
pi@raspberrypi4-iob:/media/fritznas $

Auch "nano" funkt nicht ...

Quote from raspbastler

Alle Energiesparmaßnahmen der FRITZ!Box sollten ebenfalls deaktiviert werden, das kann manchmal zu langen Reaktionszeiten führen. Ergo: Datei kann nicht gefunden werden

das ist geschehen ... keine Energiesparmaßnahmen aktiviert oder ähnliches

cu perry94

hyle · May 3rd 2023

Ich glaube jetzt verstehe ich. Die Sperrdatei kann garnicht angelegt werden, deshalb diese Meldung. D.h. nano hat dort vermutlich keine Schreibrechte.

Was sind die Ausgaben von findmnt?

Leg auch mal im /home/pi ein Verzeichnis an und mounte zum Test dahin!

RTFM · May 3rd 2023

In den Logfiles

a.) vom Pi

b.) der FritzBox

gibt es keinen Hinweis auf die Ursache ?

Z.B. auf a.) und b.) in /var/log/syslog*

Servus !

Der_Imperator · May 3rd 2023

Quote from hyle

Btw. da ist vermutlich ein Punkt (.) vor tt.txt.swp zu viel. Ist aber auch möglich, dass Sperrdateien versteckt werden. Versuch mal rm tt.txt.swp!

Was passiert mit dem absoluten Pfad nano /media/fritznas/tt.txt?

Quote from perry94

hyle

Code

nano tt.txt

 [ Fehler beim Schreiben der Sperrdatei ./.tt.txt.swp: Datei oder Verzeichnis nicht gefunden ]

cu perry94

Wenn es eine versteckete Datei ist dann den RM mit dem . vor dem Dateinamen, wie oben zu sehen ist.
rm .tt.txt.swp

EDIT :
Und schau mal auf die Fritzbox ob der User mit dem du mountest auch ausreichende Rechte hat.

perry94 · May 3rd 2023

Hallo hyle

Quote from hyle

Was sind die Ausgaben von findmnt?

Code

pi@raspberrypi4-iob:~ $ findmnt
TARGET                                SOURCE         FSTYPE     OPTIONS
/                                     /dev/mmcblk0p2 ext4       rw,noatime
├─/dev                                devtmpfs       devtmpfs   rw,relatime,size=3879288k,nr_inodes=74941,mode=755
│ ├─/dev/shm                          tmpfs          tmpfs      rw,nosuid,nodev
│ ├─/dev/pts                          devpts         devpts     rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000
│ └─/dev/mqueue                       mqueue         mqueue     rw,relatime
├─/sys                                sysfs          sysfs      rw,nosuid,nodev,noexec,relatime
│ ├─/sys/kernel/security              securityfs     securityfs rw,nosuid,nodev,noexec,relatime
│ ├─/sys/fs/cgroup                    tmpfs          tmpfs      ro,nosuid,nodev,noexec,mode=755
│ │ ├─/sys/fs/cgroup/unified          cgroup2        cgroup2    rw,nosuid,nodev,noexec,relatime,nsdelegate
│ │ ├─/sys/fs/cgroup/systemd          cgroup         cgroup     rw,nosuid,nodev,noexec,relatime,xattr,name=systemd
│ │ ├─/sys/fs/cgroup/devices          cgroup         cgroup     rw,nosuid,nodev,noexec,relatime,devices
│ │ ├─/sys/fs/cgroup/cpu,cpuacct      cgroup         cgroup     rw,nosuid,nodev,noexec,relatime,cpu,cpuacct
│ │ ├─/sys/fs/cgroup/net_cls,net_prio cgroup         cgroup     rw,nosuid,nodev,noexec,relatime,net_cls,net_prio
│ │ ├─/sys/fs/cgroup/blkio            cgroup         cgroup     rw,nosuid,nodev,noexec,relatime,blkio
│ │ ├─/sys/fs/cgroup/freezer          cgroup         cgroup     rw,nosuid,nodev,noexec,relatime,freezer
│ │ ├─/sys/fs/cgroup/perf_event       cgroup         cgroup     rw,nosuid,nodev,noexec,relatime,perf_event
│ │ ├─/sys/fs/cgroup/pids             cgroup         cgroup     rw,nosuid,nodev,noexec,relatime,pids
│ │ └─/sys/fs/cgroup/cpuset           cgroup         cgroup     rw,nosuid,nodev,noexec,relatime,cpuset
│ ├─/sys/fs/bpf                       none           bpf        rw,nosuid,nodev,noexec,relatime,mode=700
│ ├─/sys/kernel/debug                 debugfs        debugfs    rw,relatime
│ └─/sys/kernel/config                configfs       configfs   rw,relatime
├─/proc                               proc           proc       rw,relatime
│ └─/proc/sys/fs/binfmt_misc          systemd-1      autofs     rw,relatime,fd=27,pgrp=1,timeout=0,minproto=5,maxprot
├─/run                                tmpfs          tmpfs      rw,nosuid,nodev,mode=755
│ ├─/run/lock                         tmpfs          tmpfs      rw,nosuid,nodev,noexec,relatime,size=5120k
│ ├─/run/rpc_pipefs                   sunrpc         rpc_pipefs rw,relatime
│ └─/run/user/1000                    tmpfs          tmpfs      rw,nosuid,nodev,relatime,size=808828k,mode=700,uid=10
├─/boot                               /dev/mmcblk0p1 vfat       rw,relatime,fmask=0022,dmask=0022,codepage=437,iochar
└─/media/fritznas                     //192.168.178.1/FRITZ.NAS/Ordner/Ordner/Sicherung/sich-pi-16gb/
                                                     cifs       rw,relatime,vers=3.1.1,cache=strict,username=xxxxx,do
pi@raspberrypi4-iob:~ $

Display More

hallo Der_Imperator

Quote from Der_Imperator

Wenn es eine versteckete Datei ist dann den RM mit dem . vor dem Dateinamen, wie oben zu sehen ist.
rm .tt.txt.swp

Ergebnis

Code

pi@raspberrypi4-iob:/media/nas $ rm .tt.txt.swp
rm: das Entfernen von '.tt.txt.swp' ist nicht möglich: Datei oder Verzeichnis nicht gefunden
pi@raspberrypi4-iob:/media/nas $

Quote from Der_Imperator

Und schau mal auf die Fritzbox ob der User mit dem du mountest auch ausreichende Rechte hat.

hallo rftm

Quote from RTFM

In den Logfiles
a.) vom Pi
b.) der FritzBox
gibt es keinen Hinweis auf die Ursache ?

Z.B. auf a.) und b.) in /var/log/syslog*

zu a)

Code

May  3 00:00:25 raspberrypi4-iob rsyslogd:  [origin software="rsyslogd" swVersion="8.1901.0" x-pid="365" x-info="htt$
May  3 00:00:25 raspberrypi4-iob systemd[1]: logrotate.service: Succeeded.
May  3 00:00:25 raspberrypi4-iob systemd[1]: Started Rotate log files.
May  3 00:00:26 raspberrypi4-iob systemd[1]: man-db.service: Succeeded.
May  3 00:00:26 raspberrypi4-iob systemd[1]: Started Daily man-db regeneration.
May  3 00:11:13 raspberrypi4-iob rngd[696]: stats: bits received from HRNG source: 1800064
May  3 00:11:13 raspberrypi4-iob rngd[696]: stats: bits sent to kernel pool: 1742048
May  3 00:11:13 raspberrypi4-iob rngd[696]: stats: entropy added to kernel pool: 1742048
May  3 00:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2 successes: 90
May  3 00:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2 failures: 0
May  3 00:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Monobit: 0
May  3 00:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Poker: 0
May  3 00:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Runs: 0
May  3 00:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Long run: 0
May  3 00:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Continuous run: 0
May  3 00:11:13 raspberrypi4-iob rngd[696]: stats: HRNG source speed: (min=342.690; avg=505.378; max=522.114)Kibits/s
May  3 00:11:13 raspberrypi4-iob rngd[696]: stats: FIPS tests speed: (min=11.019; avg=18.979; max=31.423)Mibits/s
May  3 00:11:13 raspberrypi4-iob rngd[696]: stats: Lowest ready-buffers level: 2
May  3 00:11:13 raspberrypi4-iob rngd[696]: stats: Entropy starvations: 0
May  3 00:11:13 raspberrypi4-iob rngd[696]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
May  3 00:17:01 raspberrypi4-iob CRON[27579]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May  3 00:17:23 raspberrypi4-iob dhcpcd[686]: eth0: fe80::9a9b:cbff:fe90:880f is reachable again
May  3 00:17:23 raspberrypi4-iob dhcpcd[686]: eth0: fe80::9a9b:cbff:fe90:880f is reachable again
May  3 00:23:01 raspberrypi4-iob deCONZ-WIFI2.sh[362]: command failed: Network is down (-100)
May  3 00:57:37 raspberrypi4-iob deCONZ-WIFI2.sh[362]: command failed: Network is down (-100)
May  3 01:11:13 raspberrypi4-iob rngd[696]: stats: bits received from HRNG source: 1820064
May  3 01:11:13 raspberrypi4-iob rngd[696]: stats: bits sent to kernel pool: 1772288
May  3 01:11:13 raspberrypi4-iob rngd[696]: stats: entropy added to kernel pool: 1772288
May  3 01:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2 successes: 91
May  3 01:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2 failures: 0
May  3 01:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Monobit: 0
May  3 01:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Poker: 0
May  3 01:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Runs: 0
May  3 01:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Long run: 0
May  3 01:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Continuous run: 0
May  3 01:11:13 raspberrypi4-iob rngd[696]: stats: HRNG source speed: (min=342.690; avg=505.476; max=522.114)Kibits/s
May  3 01:11:13 raspberrypi4-iob rngd[696]: stats: FIPS tests speed: (min=11.019; avg=19.038; max=31.423)Mibits/s
May  3 01:11:13 raspberrypi4-iob rngd[696]: stats: Lowest ready-buffers level: 2
May  3 01:11:13 raspberrypi4-iob rngd[696]: stats: Entropy starvations: 0
May  3 01:11:13 raspberrypi4-iob rngd[696]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
May  3 01:17:01 raspberrypi4-iob CRON[31856]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May  3 01:32:11 raspberrypi4-iob deCONZ-WIFI2.sh[362]: command failed: Network is down (-100)
May  3 02:06:45 raspberrypi4-iob deCONZ-WIFI2.sh[362]: command failed: Network is down (-100)
May  3 02:11:13 raspberrypi4-iob rngd[696]: stats: bits received from HRNG source: 1860064
May  3 02:11:13 raspberrypi4-iob rngd[696]: stats: bits sent to kernel pool: 1802048
May  3 02:11:13 raspberrypi4-iob rngd[696]: stats: entropy added to kernel pool: 1802048
May  3 02:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2 successes: 93
May  3 02:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2 failures: 0
May  3 02:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Monobit: 0
May  3 02:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Poker: 0
May  3 02:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Runs: 0
May  3 02:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Long run: 0
May  3 02:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Continuous run: 0
May  3 02:11:13 raspberrypi4-iob rngd[696]: stats: HRNG source speed: (min=342.690; avg=505.674; max=522.114)Kibits/s
May  3 02:11:13 raspberrypi4-iob rngd[696]: stats: FIPS tests speed: (min=11.019; avg=19.013; max=31.423)Mibits/s
May  3 02:11:13 raspberrypi4-iob rngd[696]: stats: Lowest ready-buffers level: 2
May  3 02:11:13 raspberrypi4-iob rngd[696]: stats: Entropy starvations: 0
May  3 02:11:13 raspberrypi4-iob rngd[696]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
May  3 02:17:01 raspberrypi4-iob CRON[3549]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May  3 02:34:09 raspberrypi4-iob bash[28272]: host.raspberrypi4-iob Delete log file iobroker.2023-04-25.log.gz
May  3 02:41:18 raspberrypi4-iob deCONZ-WIFI2.sh[362]: command failed: Network is down (-100)
May  3 03:00:42 raspberrypi4-iob deCONZ-update2.sh[380]: Error: database is locked
May  3 03:11:13 raspberrypi4-iob rngd[696]: stats: bits received from HRNG source: 1880064
May  3 03:11:13 raspberrypi4-iob rngd[696]: stats: bits sent to kernel pool: 1832288
May  3 03:11:13 raspberrypi4-iob rngd[696]: stats: entropy added to kernel pool: 1832288
May  3 03:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2 successes: 94
May  3 03:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2 failures: 0
May  3 03:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Monobit: 0
May  3 03:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Poker: 0
May  3 03:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Runs: 0
May  3 03:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Long run: 0
May  3 03:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Continuous run: 0
May  3 03:11:13 raspberrypi4-iob rngd[696]: stats: HRNG source speed: (min=342.690; avg=505.761; max=522.114)Kibits/s
May  3 03:11:13 raspberrypi4-iob rngd[696]: stats: FIPS tests speed: (min=11.019; avg=18.904; max=31.423)Mibits/s
May  3 03:11:13 raspberrypi4-iob rngd[696]: stats: Lowest ready-buffers level: 2
May  3 03:11:13 raspberrypi4-iob rngd[696]: stats: Entropy starvations: 0
May  3 03:11:13 raspberrypi4-iob rngd[696]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
May  3 03:15:52 raspberrypi4-iob deCONZ-WIFI2.sh[362]: command failed: Network is down (-100)
May  3 03:17:01 raspberrypi4-iob CRON[7685]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May  3 03:50:26 raspberrypi4-iob deCONZ-WIFI2.sh[362]: command failed: Network is down (-100)
May  3 04:11:13 raspberrypi4-iob rngd[696]: stats: bits received from HRNG source: 1920064
May  3 04:11:13 raspberrypi4-iob rngd[696]: stats: bits sent to kernel pool: 1862048
May  3 04:11:13 raspberrypi4-iob rngd[696]: stats: entropy added to kernel pool: 1862048
May  3 04:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2 successes: 96
May  3 04:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2 failures: 0
May  3 04:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Monobit: 0
May  3 04:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Poker: 0
May  3 04:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Runs: 0
May  3 04:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Long run: 0
May  3 04:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Continuous run: 0
May  3 04:11:13 raspberrypi4-iob rngd[696]: stats: HRNG source speed: (min=342.690; avg=505.942; max=522.114)Kibits/s
May  3 04:11:13 raspberrypi4-iob rngd[696]: stats: FIPS tests speed: (min=11.019; avg=19.062; max=31.474)Mibits/s
May  3 04:11:13 raspberrypi4-iob rngd[696]: stats: Lowest ready-buffers level: 2
May  3 04:11:13 raspberrypi4-iob rngd[696]: stats: Entropy starvations: 0
May  3 04:11:13 raspberrypi4-iob rngd[696]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
May  3 04:17:01 raspberrypi4-iob CRON[12213]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May  3 04:24:59 raspberrypi4-iob deCONZ-WIFI2.sh[362]: command failed: Network is down (-100)
May  3 04:59:34 raspberrypi4-iob deCONZ-WIFI2.sh[362]: command failed: Network is down (-100)
May  3 05:11:13 raspberrypi4-iob rngd[696]: stats: bits received from HRNG source: 1940064
May  3 05:11:13 raspberrypi4-iob rngd[696]: stats: bits sent to kernel pool: 1892288
May  3 05:11:13 raspberrypi4-iob rngd[696]: stats: entropy added to kernel pool: 1892288
May  3 05:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2 successes: 97
May  3 05:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2 failures: 0
May  3 05:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Monobit: 0
May  3 05:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Poker: 0
May  3 05:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Runs: 0
May  3 05:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Long run: 0
May  3 05:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Continuous run: 0
May  3 05:11:13 raspberrypi4-iob rngd[696]: stats: HRNG source speed: (min=342.690; avg=506.033; max=522.114)Kibits/s
May  3 05:11:13 raspberrypi4-iob rngd[696]: stats: FIPS tests speed: (min=11.019; avg=19.003; max=31.474)Mibits/s
May  3 05:11:13 raspberrypi4-iob rngd[696]: stats: Lowest ready-buffers level: 2
May  3 05:11:13 raspberrypi4-iob rngd[696]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
May  3 05:17:01 raspberrypi4-iob CRON[16352]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May  3 05:34:07 raspberrypi4-iob deCONZ-WIFI2.sh[362]: command failed: Network is down (-100)
May  3 06:08:41 raspberrypi4-iob deCONZ-WIFI2.sh[362]: command failed: Network is down (-100)
May  3 06:11:13 raspberrypi4-iob rngd[696]: stats: bits received from HRNG source: 1980064
May  3 06:11:13 raspberrypi4-iob rngd[696]: stats: bits sent to kernel pool: 1922048
May  3 06:11:13 raspberrypi4-iob rngd[696]: stats: entropy added to kernel pool: 1922048
May  3 06:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2 successes: 99
May  3 06:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2 failures: 0
May  3 06:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Monobit: 0
May  3 06:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Poker: 0
May  3 06:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Runs: 0
May  3 06:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Long run: 0
May  3 06:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Continuous run: 0
May  3 06:11:13 raspberrypi4-iob rngd[696]: stats: HRNG source speed: (min=342.690; avg=506.213; max=522.114)Kibits/s
May  3 06:11:13 raspberrypi4-iob rngd[696]: stats: FIPS tests speed: (min=11.019; avg=19.155; max=31.474)Mibits/s
May  3 06:11:13 raspberrypi4-iob rngd[696]: stats: Lowest ready-buffers level: 2
May  3 06:11:13 raspberrypi4-iob rngd[696]: stats: Entropy starvations: 0
May  3 06:11:13 raspberrypi4-iob rngd[696]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
May  3 06:17:01 raspberrypi4-iob CRON[20528]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May  3 06:25:01 raspberrypi4-iob CRON[25384]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report $
May  3 06:31:05 raspberrypi4-iob systemd[1]: Starting Daily apt upgrade and clean activities...
May  3 06:31:06 raspberrypi4-iob systemd[1]: apt-daily-upgrade.service: Succeeded.
May  3 06:31:06 raspberrypi4-iob systemd[1]: Started Daily apt upgrade and clean activities.
May  3 06:43:15 raspberrypi4-iob deCONZ-WIFI2.sh[362]: command failed: Network is down (-100)
May  3 07:11:13 raspberrypi4-iob rngd[696]: stats: bits received from HRNG source: 2000064
May  3 07:11:13 raspberrypi4-iob rngd[696]: stats: bits sent to kernel pool: 1952288
May  3 07:11:13 raspberrypi4-iob rngd[696]: stats: entropy added to kernel pool: 1952288
May  3 07:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2 successes: 100
May  3 07:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2 failures: 0
May  3 07:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Monobit: 0
May  3 07:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Poker: 0
May  3 07:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Runs: 0
May  3 07:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Long run: 0
May  3 07:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Continuous run: 0
May  3 07:11:13 raspberrypi4-iob rngd[696]: stats: HRNG source speed: (min=342.690; avg=506.298; max=522.114)Kibits/s
May  3 07:11:13 raspberrypi4-iob rngd[696]: stats: FIPS tests speed: (min=11.019; avg=19.151; max=31.474)Mibits/s
May  3 07:11:13 raspberrypi4-iob rngd[696]: stats: Lowest ready-buffers level: 2
May  3 07:11:13 raspberrypi4-iob rngd[696]: stats: Entropy starvations: 0
May  3 07:11:13 raspberrypi4-iob rngd[696]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
May  3 07:17:01 raspberrypi4-iob CRON[24751]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May  3 07:17:50 raspberrypi4-iob deCONZ-WIFI2.sh[362]: command failed: Network is down (-100)
May  3 07:42:25 raspberrypi4-iob systemd[1]: Starting Daily apt download activities...
May  3 07:42:26 raspberrypi4-iob systemd[1]: apt-daily.service: Succeeded.
May  3 07:42:26 raspberrypi4-iob systemd[1]: Started Daily apt download activities.
May  3 07:52:24 raspberrypi4-iob deCONZ-WIFI2.sh[362]: command failed: Network is down (-100)
May  3 08:07:37 raspberrypi4-iob deCONZ-update2.sh[380]: Error: database is locked
May  3 08:09:07 raspberrypi4-iob deCONZ-WIFI2.sh[362]: Error: database is locked
May  3 08:09:07 raspberrypi4-iob deCONZ-WIFI2.sh[362]: Error: database is locked
May  3 08:11:13 raspberrypi4-iob rngd[696]: stats: bits received from HRNG source: 2040064
May  3 08:11:13 raspberrypi4-iob rngd[696]: stats: bits sent to kernel pool: 1982048
May  3 08:11:13 raspberrypi4-iob rngd[696]: stats: entropy added to kernel pool: 1982048
May  3 08:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2 successes: 102
May  3 08:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2 failures: 0
May  3 08:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Monobit: 0
May  3 08:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Poker: 0
May  3 08:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Runs: 0
May  3 08:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Long run: 0
May  3 08:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Continuous run: 0
May  3 08:11:13 raspberrypi4-iob rngd[696]: stats: HRNG source speed: (min=342.690; avg=506.446; max=522.114)Kibits/s
May  3 08:11:13 raspberrypi4-iob rngd[696]: stats: FIPS tests speed: (min=11.019; avg=19.240; max=31.474)Mibits/s
May  3 08:11:13 raspberrypi4-iob rngd[696]: stats: Lowest ready-buffers level: 2
May  3 08:11:13 raspberrypi4-iob rngd[696]: stats: Entropy starvations: 0
May  3 08:11:13 raspberrypi4-iob rngd[696]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
May  3 08:17:01 raspberrypi4-iob CRON[29045]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May  3 08:21:47 raspberrypi4-iob deCONZ-update2.sh[380]: Error: database is locked
May  3 08:26:57 raspberrypi4-iob deCONZ-WIFI2.sh[362]: command failed: Network is down (-100)
May  3 08:32:32 raspberrypi4-iob deCONZ-update2.sh[380]: Error: database is locked
May  3 08:59:03 raspberrypi4-iob dhcpcd[686]: eth0: fe80::9a9b:cbff:fe90:880f is reachable again
May  3 09:01:32 raspberrypi4-iob deCONZ-WIFI2.sh[362]: command failed: Network is down (-100)
May  3 09:01:54 raspberrypi4-iob deCONZ-update2.sh[380]: Error: database is locked
May  3 09:11:13 raspberrypi4-iob rngd[696]: stats: bits received from HRNG source: 2060064
May  3 09:11:13 raspberrypi4-iob rngd[696]: stats: bits sent to kernel pool: 2012288
May  3 09:11:13 raspberrypi4-iob rngd[696]: stats: entropy added to kernel pool: 2012288
May  3 09:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2 successes: 103
May  3 09:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2 failures: 0
May  3 09:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Monobit: 0
May  3 09:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Poker: 0
May  3 09:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Runs: 0
May  3 09:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Long run: 0
May  3 09:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Continuous run: 0
May  3 09:11:13 raspberrypi4-iob rngd[696]: stats: HRNG source speed: (min=342.690; avg=506.527; max=522.114)Kibits/s
May  3 09:11:13 raspberrypi4-iob rngd[696]: stats: FIPS tests speed: (min=11.019; avg=19.312; max=31.474)Mibits/s
May  3 09:11:13 raspberrypi4-iob rngd[696]: stats: Lowest ready-buffers level: 2
May  3 09:11:13 raspberrypi4-iob rngd[696]: stats: Entropy starvations: 0
May  3 09:11:13 raspberrypi4-iob rngd[696]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
May  3 09:17:01 raspberrypi4-iob CRON[620]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May  3 09:23:35 raspberrypi4-iob dhcpcd[686]: eth0: fe80::9a9b:cbff:fe90:880f is reachable again
May  3 09:23:35 raspberrypi4-iob dhcpcd[686]: eth0: fe80::9a9b:cbff:fe90:880f is reachable again
May  3 09:27:12 raspberrypi4-iob deCONZ-WIFI2.sh[362]: Error: database is locked
May  3 09:27:12 raspberrypi4-iob deCONZ-WIFI2.sh[362]: Error: database is locked
May  3 09:29:26 raspberrypi4-iob deCONZ-WIFI2.sh[362]: Error: database is locked
May  3 09:29:26 raspberrypi4-iob deCONZ-WIFI2.sh[362]: Error: database is locked
May  3 09:29:26 raspberrypi4-iob deCONZ-WIFI2.sh[362]: Error: database is locked
May  3 09:29:26 raspberrypi4-iob deCONZ-WIFI2.sh[362]: Error: database is locked
May  3 09:29:26 raspberrypi4-iob deCONZ-WIFI2.sh[362]: Error: database is locked
May  3 09:29:26 raspberrypi4-iob deCONZ-WIFI2.sh[362]: Error: database is locked
May  3 09:29:26 raspberrypi4-iob deCONZ-WIFI2.sh[362]: Error: database is locked
May  3 09:34:41 raspberrypi4-iob deCONZ-update2.sh[380]: Error: database is locked
May  3 09:35:02 raspberrypi4-iob deCONZ-WIFI2.sh[362]: command failed: Network is down (-100)
May  3 10:09:37 raspberrypi4-iob deCONZ-WIFI2.sh[362]: command failed: Network is down (-100)
May  3 10:11:13 raspberrypi4-iob rngd[696]: stats: bits received from HRNG source: 2100064
May  3 10:11:13 raspberrypi4-iob rngd[696]: stats: bits sent to kernel pool: 2042048
May  3 10:11:13 raspberrypi4-iob rngd[696]: stats: entropy added to kernel pool: 2042048
May  3 10:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2 successes: 105
May  3 10:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2 failures: 0
May  3 10:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Monobit: 0
May  3 10:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Poker: 0
May  3 10:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Runs: 0
May  3 10:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Long run: 0
May  3 10:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Continuous run: 0
May  3 10:11:13 raspberrypi4-iob rngd[696]: stats: HRNG source speed: (min=342.690; avg=506.671; max=522.114)Kibits/s
May  3 10:11:13 raspberrypi4-iob rngd[696]: stats: FIPS tests speed: (min=11.019; avg=19.268; max=31.474)Mibits/s
May  3 10:11:13 raspberrypi4-iob rngd[696]: stats: Lowest ready-buffers level: 2
May  3 10:11:13 raspberrypi4-iob rngd[696]: stats: Entropy starvations: 0
May  3 10:11:13 raspberrypi4-iob rngd[696]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
May  3 10:17:01 raspberrypi4-iob CRON[4774]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May  3 10:44:11 raspberrypi4-iob deCONZ-WIFI2.sh[362]: command failed: Network is down (-100)
May  3 11:11:13 raspberrypi4-iob rngd[696]: stats: bits received from HRNG source: 2120064
May  3 11:11:13 raspberrypi4-iob rngd[696]: stats: bits sent to kernel pool: 2072288
May  3 11:11:13 raspberrypi4-iob rngd[696]: stats: entropy added to kernel pool: 2072288
May  3 11:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2 successes: 106
May  3 11:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2 failures: 0
May  3 11:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Monobit: 0
May  3 11:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Poker: 0
May  3 11:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Runs: 0
May  3 11:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Long run: 0
May  3 11:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Continuous run: 0
May  3 11:11:13 raspberrypi4-iob rngd[696]: stats: HRNG source speed: (min=342.690; avg=506.747; max=522.114)Kibits/s
May  3 11:11:13 raspberrypi4-iob rngd[696]: stats: FIPS tests speed: (min=11.019; avg=19.339; max=31.474)Mibits/s
May  3 11:11:13 raspberrypi4-iob rngd[696]: stats: Lowest ready-buffers level: 2
May  3 11:11:13 raspberrypi4-iob rngd[696]: stats: Entropy starvations: 0
May  3 11:11:13 raspberrypi4-iob rngd[696]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
May  3 11:17:01 raspberrypi4-iob CRON[9046]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May  3 11:18:45 raspberrypi4-iob deCONZ-WIFI2.sh[362]: command failed: Network is down (-100)
May  3 11:53:18 raspberrypi4-iob deCONZ-WIFI2.sh[362]: command failed: Network is down (-100)
May  3 12:11:13 raspberrypi4-iob rngd[696]: stats: bits received from HRNG source: 2160064
May  3 12:11:13 raspberrypi4-iob rngd[696]: stats: bits sent to kernel pool: 2102048
May  3 12:11:13 raspberrypi4-iob rngd[696]: stats: entropy added to kernel pool: 2102048
May  3 12:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2 successes: 108
May  3 12:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2 failures: 0
May  3 12:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Monobit: 0
May  3 12:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Poker: 0
May  3 12:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Runs: 0
May  3 12:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Long run: 0
May  3 12:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Continuous run: 0
May  3 12:11:13 raspberrypi4-iob rngd[696]: stats: HRNG source speed: (min=342.690; avg=506.874; max=522.114)Kibits/s
May  3 12:11:13 raspberrypi4-iob rngd[696]: stats: FIPS tests speed: (min=11.019; avg=19.299; max=31.474)Mibits/s
May  3 12:11:13 raspberrypi4-iob rngd[696]: stats: Lowest ready-buffers level: 2
May  3 12:11:13 raspberrypi4-iob rngd[696]: stats: Entropy starvations: 0
May  3 12:11:13 raspberrypi4-iob rngd[696]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
May  3 12:17:01 raspberrypi4-iob CRON[13202]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May  3 12:27:50 raspberrypi4-iob deCONZ-WIFI2.sh[362]: command failed: Network is down (-100)
May  3 12:31:54 raspberrypi4-iob deCONZ-update2.sh[380]: Error: database is locked
May  3 13:02:24 raspberrypi4-iob deCONZ-WIFI2.sh[362]: command failed: Network is down (-100)
May  3 13:09:12 raspberrypi4-iob systemd[1]: Created slice User Slice of UID 1000.
May  3 13:09:12 raspberrypi4-iob systemd[1]: Starting User Runtime Directory /run/user/1000...
May  3 13:09:12 raspberrypi4-iob systemd[1]: Started User Runtime Directory /run/user/1000.
May  3 13:09:12 raspberrypi4-iob systemd[1]: Starting User Manager for UID 1000...
May  3 13:09:12 raspberrypi4-iob systemd[12598]: Listening on GnuPG cryptographic agent and passphrase cache (restri$
May  3 13:09:12 raspberrypi4-iob systemd[12598]: Listening on GnuPG cryptographic agent and passphrase cache.
May  3 13:09:12 raspberrypi4-iob systemd[12598]: Reached target Timers.
May  3 13:09:12 raspberrypi4-iob systemd[12598]: Listening on GnuPG network certificate management daemon.
May  3 13:09:12 raspberrypi4-iob systemd[12598]: Listening on GnuPG cryptographic agent and passphrase cache (access$
May  3 13:09:12 raspberrypi4-iob systemd[12598]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
May  3 13:09:12 raspberrypi4-iob systemd[12598]: Starting D-Bus User Message Bus Socket.
May  3 13:09:12 raspberrypi4-iob systemd[12598]: Reached target Paths.
May  3 13:09:12 raspberrypi4-iob systemd[12598]: Listening on D-Bus User Message Bus Socket.
May  3 13:09:12 raspberrypi4-iob systemd[12598]: Reached target Sockets.
May  3 13:09:12 raspberrypi4-iob systemd[12598]: Reached target Basic System.
May  3 13:09:12 raspberrypi4-iob systemd[12598]: Reached target Default.
May  3 13:09:12 raspberrypi4-iob systemd[12598]: Startup finished in 145ms.
May  3 13:09:12 raspberrypi4-iob systemd[1]: Started User Manager for UID 1000.
May  3 13:09:12 raspberrypi4-iob systemd[1]: Started Session 93 of user pi.
May  3 13:11:13 raspberrypi4-iob rngd[696]: stats: bits received from HRNG source: 2180064
May  3 13:11:13 raspberrypi4-iob rngd[696]: stats: bits sent to kernel pool: 2132288
May  3 13:11:13 raspberrypi4-iob rngd[696]: stats: entropy added to kernel pool: 2132288
May  3 13:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2 successes: 109
May  3 13:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2 failures: 0
May  3 13:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Monobit: 0
May  3 13:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Poker: 0
May  3 13:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Runs: 0
May  3 13:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Long run: 0
May  3 13:11:13 raspberrypi4-iob rngd[696]: stats: FIPS 140-2(2001-10-10) Continuous run: 0
May  3 13:11:13 raspberrypi4-iob rngd[696]: stats: HRNG source speed: (min=342.690; avg=506.936; max=522.114)Kibits/s
May  3 13:11:13 raspberrypi4-iob rngd[696]: stats: FIPS tests speed: (min=11.019; avg=19.204; max=31.474)Mibits/s
May  3 13:11:13 raspberrypi4-iob rngd[696]: stats: Lowest ready-buffers level: 2
May  3 13:11:13 raspberrypi4-iob rngd[696]: stats: Entropy starvations: 0
May  3 13:11:13 raspberrypi4-iob rngd[696]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
May  3 13:13:22 raspberrypi4-iob systemd[12598]: media-fritznas.mount: Succeeded.
May  3 13:13:22 raspberrypi4-iob systemd[1]: media-fritznas.mount: Succeeded.
May  3 13:17:01 raspberrypi4-iob CRON[17403]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May  3 13:17:25 raspberrypi4-iob kernel: [255994.076062] CIFS: Attempting to mount //192.168.178.1/FRITZ.NAS/Ordner
May  3 13:36:58 raspberrypi4-iob deCONZ-WIFI2.sh[362]: command failed: Network is down (-100)

Display More

zu b)

Was mir aufgefallen ist command failed: Network is down (-100) ... Aber keine Idee woher das kommen könnte ... Das LAN läuft sonst einwandfrei

Vielen Dank für eure Bemühungen ... Ich hoffe die Info hilft evt weiter

cu perry94

Tags