(gelöst) Backup nur nach Raspi Neustart, danach nicht mehr!
-
@edition sagte in Backup nur nach Raspi Neustart, danach nicht mehr!:
Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 (DT)
Der hat nur 1 GB RAM. Das ist zu wenig.
Gib mal die komplette Ausgabe von iob diag raus. -
Hmm, ich hatte schon einmal einen Raspi A mit 512MB RAM mit iobroker bespielt und die Backupeinstellungen identisch eingestellt. Der hat brav sein Backup durchgezogen! Jeden Tag!
-
@edition
In welchem Jahrhundert war das? -
@codierknecht War im letzten Jahr!
-
Gib mal die vollständige Ausgabe vom iob diag.
-
pi@ioBroker:~ $ free -m -t
gesamt benutzt frei gemns. Puffer/Cache verfügbar
Speicher: 909 522 145 0 242 332
Swap: 99 99 0
Gesamt: 1009 622 145Aktuelle Speicherauslastung!
-
@edition
1 GB RAM ist schon echt grenzwertig.
Und insbesondere das Backup braucht reichlich davon.
Sobald dann ein paar Adapter laufen, kann's schnell eng werden. -
Hier das ganze:
Skript v.2023-01-02 *** BASE SYSTEM *** Model : Raspberry Pi 3 Model B Plus Rev 1.3 Architecture: aarch64 Docker: false Virtualization: none Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye PRETTY_NAME="Debian GNU/Linux 11 (bullseye)" NAME="Debian GNU/Linux" VERSION_ID="11" VERSION="11 (bullseye)" VERSION_CODENAME=bullseye ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" Systemuptime and Load: 21:21:27 up 3 days, 10:15, 1 user, load average: 0.39, 0.15, 0.14 CPU threads: 4 *** Time and Time Zones *** Wed Mar 8 20:21:27 UTC 2023 Wed Mar 8 21:21:27 CET 2023 CET +0100 Europe/Berlin *** User and Groups *** pi /home/pi pi adm dialout cdrom sudo audio video plugdev games users input netdev gpio i2c spi iobroker *** X-Server-Setup *** X-Server: false Desktop: Terminal: tty Boot Target: graphical.target *** MEMORY *** total used free shared buff/cache available Mem: 909M 528M 102M 0.0K 278M 325M Swap: 99M 99M 0B Total: 1.0G 628M 102M 909 M total memory 529 M used memory 369 M active memory 355 M inactive memory 101 M free memory 16 M buffer memory 262 M swap cache 99 M total swap 99 M used swap 0 M free swap *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/root ext4 29G 3.3G 25G 12% / devtmpfs devtmpfs 325M 0 325M 0% /dev tmpfs tmpfs 455M 0 455M 0% /dev/shm tmpfs tmpfs 182M 712K 182M 1% /run tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock /dev/mmcblk0p1 vfat 253M 31M 222M 13% /boot tmpfs tmpfs 91M 0 91M 0% /run/user/1000 Messages in dmesg: Show mounted filesystems (real ones only): TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime `-/boot /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,flush,errors=remount-ro Files in neuralgic directories: /var: 1.3G /var/ 813M /var/log 809M /var/log/journal/2ac2779a3e264b89af8a628ac67e13bd 809M /var/log/journal 256M /var/cache /opt/iobroker/backups: 4.0K /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 118M /opt/iobroker/iobroker-data/ 53M /opt/iobroker/iobroker-data/backup-objects 23M /opt/iobroker/iobroker-data/files 13M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js 13M /opt/iobroker/iobroker-data/files/admin.admin/custom/static The five largest files in iobroker-data are: 22M /opt/iobroker/iobroker-data/objects.jsonl 21M /opt/iobroker/iobroker-data/states.jsonl 6.6M /opt/iobroker/iobroker-data/files/modbus.admin/static/js/main.8083c40d.js.map 6.3M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_js-node_modules_iobr-99c23e.847b8ad9.chunk.js.map 2.8M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_js-node_modules_iobr-99c23e.847b8ad9.chunk.js *** NodeJS-Installation *** /usr/bin/nodejs v16.19.1 /usr/bin/node v16.19.1 /usr/bin/npm 8.19.3 /usr/bin/npx 8.19.3 nodejs: Installed: 16.19.1-deb-1nodesource1 Candidate: 16.19.1-deb-1nodesource1 Version table: *** 16.19.1-deb-1nodesource1 500 500 https://deb.nodesource.com/node_16.x bullseye/main arm64 Packages 100 /var/lib/dpkg/status 12.22.12~dfsg-1~deb11u3 500 500 http://security.debian.org/debian-security bullseye-security/main arm64 Packages 12.22.5~dfsg-2~11u1 500 500 http://deb.debian.org/debian bullseye/main arm64 Packages Temp directories causing npm8 problem: 0 *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Core adapters versions js-controller: 4.0.24 admin: 6.3.5 javascript: "javascript" not found Adapters from github: 0 Adapter State + system.adapter.admin.0 : admin : ioBroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.backitup.0 : backitup : ioBroker - enabled + system.adapter.discovery.0 : discovery : ioBroker - enabled + system.adapter.fhem.0 : fhem : ioBroker - enabled, port: 7072 system.adapter.modbus.0 : modbus : ioBroker - disabled + system.adapter.smartmeter.0 : smartmeter : ioBroker - enabled system.adapter.sonoff.0 : sonoff : ioBroker - disabled, port: 1883, bind: 0.0.0.0 + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : ioBroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.fhem.0 : fhem : ioBroker - enabled, port: 7072 ioBroker-Repositories stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json Active repo(s): stable Installed ioBroker-Instances Used repository: stable Adapter "admin" : 6.3.5 , installed 6.3.5 Adapter "backitup" : 2.5.12 , installed 2.5.12 Adapter "discovery" : 3.1.0 , installed 3.1.0 Adapter "fhem" : 1.6.3 , installed 1.6.3 Controller "js-controller": 4.0.24 , installed 4.0.24 Adapter "modbus" : 5.0.11 , installed 5.0.11 Adapter "smartmeter" : 3.3.4 , installed 3.3.4 Adapter "sonoff" : 2.5.1 , installed 2.5.1 Objects and States Please stand by - This may take a while Objects: 17571 States: 16775 *** OS-Repositories and Updates *** Hit:1 http://security.debian.org/debian-security bullseye-security InRelease Hit:2 http://deb.debian.org/debian bullseye InRelease Hit:3 http://archive.raspberrypi.org/debian bullseye InRelease Hit:4 http://deb.debian.org/debian bullseye-updates InRelease Hit:5 https://deb.nodesource.com/node_16.x bullseye InRelease Reading package lists... Pending Updates: 3 *** Listening Ports *** Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 14086 457/iobroker.js-con tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 10696 457/iobroker.js-con tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 13072 477/sshd: /usr/sbin tcp6 0 0 :::8081 :::* LISTEN 1001 14277 708/io.admin.0 tcp6 0 0 :::22 :::* LISTEN 0 13074 477/sshd: /usr/sbin udp 0 0 0.0.0.0:54939 0.0.0.0:* 108 14003 365/avahi-daemon: r udp 0 0 0.0.0.0:5353 0.0.0.0:* 108 14001 365/avahi-daemon: r udp 0 0 0.0.0.0:68 0.0.0.0:* 0 14082 664/dhcpcd udp6 0 0 :::56008 :::* 108 14004 365/avahi-daemon: r udp6 0 0 :::5353 :::* 108 14002 365/avahi-daemon: r udp6 0 0 :::546 :::* 0 10676 664/dhcpcd *** Log File - Last 25 Lines *** 2023-03-08 21:02:25.586 - info: smartmeter.0 (762) Received 4 values, 2 updated 2023-03-08 21:03:26.586 - info: smartmeter.0 (762) Received 4 values, 2 updated 2023-03-08 21:04:27.568 - info: smartmeter.0 (762) Error: Error while parsing SML message: Error: Unknown TL-Field 0x49b for OctetString [Offset: 221]!: Message: 1b1b1b1b010101017605f1dcd405620062007263010176010102310b0a01445a4700039e0e3d7262016501f1a5c0620263dd26007605f2dcd405620062007263070177010b0a01445a4700039e0e3d070100620affff7262016501f1a5c07477070100603201010172620162006200520004445a470177070100600100ff017262016200620052000b0a01445a4700039e0e3d0177070100010800ff641c01047262016200621e52ff65031eec680177070100100700ff017262016200621b52fe54009e58010101631377007605f3dcd405620062007263020163c90b001b1b1b1b1a0038bd 2023-03-08 21:04:27.569 - warn: smartmeter.0 (762) Error while parsing SML message: Error: Unknown TL-Field 0x49b for OctetString [Offset: 221]!: Message: 1b1b1b1b010101017605f1dcd405620062007263010176010102310b0a01445a4700039e0e3d7262016501f1a5c0620263dd26007605f2dcd405620062007263070177010b0a01445a4700039e0e3d070100620affff7262016501f1a5c07477070100603201010172620162006200520004445a470177070100600100ff017262016200620052000b0a01445a4700039e0e3d0177070100010800ff641c01047262016200621e52ff65031eec680177070100100700ff017262016200621b52fe54009e58010101631377007605f3dcd405620062007263020163c90b001b1b1b1b1a0038bd 2023-03-08 21:05:28.633 - info: smartmeter.0 (762) Received 4 values, 2 updated 2023-03-08 21:06:29.564 - info: smartmeter.0 (762) Error: Error while parsing SML message: Error: Wrong TL-Field (7) for Unsigned!: Message: 1b1b1b1b0101010176055fded40562007263010176010102310b0a01445a4700039e0e3d7262016501f1a63a620263053100760560ded405620062007263070177010b0a01445a4700039e0e3d070100620affff7262016501f1a63a7477070100603201010172620162006200520004445a470177070100600100ff017262016200620052000b0a01445a4700039e0e3d0177070100010800ff641c01047262016200621e52ff65031eecf20177070100100700ff017262016200621b52fe54009ded010101633aee00760561ded40562006200726302017101634ead001b1b1b1b1a00978e 2023-03-08 21:06:29.565 - warn: smartmeter.0 (762) Error while parsing SML message: Error: Wrong TL-Field (7) for Unsigned!: Message: 1b1b1b1b0101010176055fded40562007263010176010102310b0a01445a4700039e0e3d7262016501f1a63a620263053100760560ded405620062007263070177010b0a01445a4700039e0e3d070100620affff7262016501f1a63a7477070100603201010172620162006200520004445a470177070100600100ff017262016200620052000b0a01445a4700039e0e3d0177070100010800ff641c01047262016200621e52ff65031eecf20177070100100700ff017262016200621b52fe54009ded010101633aee00760561ded40562006200726302017101634ead001b1b1b1b1a00978e 2023-03-08 21:07:49.846 - info: smartmeter.0 (762) Error: No or too long answer from Serial Device after last request. 2023-03-08 21:07:49.846 - warn: smartmeter.0 (762) No or too long answer from Serial Device after last request. 2023-03-08 21:08:51.577 - info: smartmeter.0 (762) Received 4 values, 2 updated 2023-03-08 21:09:52.580 - info: smartmeter.0 (762) Received 4 values, 2 updated 2023-03-08 21:10:53.552 - info: smartmeter.0 (762) Error: Error while parsing SML message: Error: Unknown TL-Field for SmlList!: Message: 1b1b1b1b01010101760577e1d405620062007263010176010102310b0a01445a4700039e0e3d7262016501f1a7426202633b2f00760578e1d405620062007263070177010b0a01445a4700039e0e3d070100620affff7262620001f1a7427477070100603201010172620162006200520004445a470177070100600100ff017262016200620052000b0a01445a4700039e0e3d0177070100010800ff641c01047262016200621e52ff65031eee150177070100100700ff017262016200621b52fe54009820010101633b7d00760579e1d4056200620072630201710163a14e001b1b1b1b1a000130 2023-03-08 21:10:53.553 - warn: smartmeter.0 (762) Error while parsing SML message: Error: Unknown TL-Field for SmlList!: Message: 1b1b1b1b01010101760577e1d405620062007263010176010102310b0a01445a4700039e0e3d7262016501f1a7426202633b2f00760578e1d405620062007263070177010b0a01445a4700039e0e3d070100620affff7262620001f1a7427477070100603201010172620162006200520004445a470177070100600100ff017262016200620052000b0a01445a4700039e0e3d0177070100010800ff641c01047262016200621e52ff65031eee150177070100100700ff017262016200621b52fe54009820010101633b7d00760579e1d4056200620072630201710163a14e001b1b1b1b1a000130 2023-03-08 21:11:54.607 - info: smartmeter.0 (762) Received 4 values, 2 updated 2023-03-08 21:12:55.559 - info: smartmeter.0 (762) Received 4 values, 2 updated 2023-03-08 21:13:56.560 - info: smartmeter.0 (762) Received 4 values, 2 updated 2023-03-08 21:14:57.555 - info: smartmeter.0 (762) Received 4 values, 2 updated 2023-03-08 21:15:59.552 - info: smartmeter.0 (762) Received 4 values, 2 updated 2023-03-08 21:17:00.550 - info: smartmeter.0 (762) Received 4 values, 2 updated 2023-03-08 21:18:01.545 - info: smartmeter.0 (762) Received 4 values, 2 updated 2023-03-08 21:19:02.542 - info: smartmeter.0 (762) Received 4 values, 2 updated 2023-03-08 21:20:03.540 - info: smartmeter.0 (762) Received 4 values, 2 updated 2023-03-08 21:21:04.539 - info: smartmeter.0 (762) Received 4 values, 2 updated 2023-03-08 21:22:05.539 - info: smartmeter.0 (762) Received 4 values, 2 updated 2023-03-08 21:23:06.542 - info: smartmeter.0 (762) Received 4 values, 2 updated ` `` -
@edition sagte in Backup nur nach Raspi Neustart, danach nicht mehr!:
javascript: "javascript" not found
? Kein javascript aktiv?
-
@edition sagte in Backup nur nach Raspi Neustart, danach nicht mehr!:
"javascript" not found
Stimmt! Meinst du das spielt mit da rein?
-
@edition sagte in Backup nur nach Raspi Neustart, danach nicht mehr!:
Meinst du das spielt mit da rein?
Ich war eigentlich der Meinung das der so essentiell sei, der ist immer installiert.
-
@edition sagte in Backup nur nach Raspi Neustart, danach nicht mehr!:
Swap: 99M 99M 0B
nee der ist trockengelaufen!
1GB reicht nicht mehr
-
Also auf PI4 umsteigen?
-
@edition sagte in Backup nur nach Raspi Neustart, danach nicht mehr!:
Also auf PI4 umsteigen?
oder was anderes, je nach Gusto
-
@homoran sagte in Backup nur nach Raspi Neustart, danach nicht mehr!:
oder was anderes, je nach Gusto
Gusto???????????
-
@edition sagte in Backup nur nach Raspi Neustart, danach nicht mehr!:
Also auf PI4 umsteigen?
Wird schwierig ... wenn Du überhaupt einen bekommst, ist der aktuell unverschämt teuer.
-
Hab noch ein 8GB Modell. Der hat gerade keine Aufgabe!
-
@edition ja dann
gib ihm was zu tun -
@edition sagte in Backup nur nach Raspi Neustart, danach nicht mehr!:
Gusto???????????
NUC, MiniPC, Docker auf'm NAS ... gibt verschiedene Möglichkeiten.
Evtl. geht auch OrangePi oder BananaPi? -
Dann ist das Wochenende ja gerettet!
