Guten Abend zusammen
Wie das Thema schon verät, habe ich probleme mit der täglichen Backup Erstellung. Das funktioniert nämlich nur einmalig, nachdem ich den Raspberry neu gestartet habe. Danach nicht mehr! Hier ein Log eines geglückten Backups:
2023-03-05 23:30:10.192 - debug: backitup.0 (788) Backup has started ...
2023-03-05 23:30:20.195 - debug: backitup.0 (788) [iobroker/mount] nfs-mount command: "sudo mount 192.168.0.8:/media/EXTURBOPart1/ioBroker /opt/iobroker/backups"
2023-03-05 23:30:20.488 - debug: backitup.0 (788) [iobroker/mount] mount successfully completed
2023-03-05 23:30:20.491 - debug: backitup.0 (788) [iobroker/mount] done
2023-03-05 23:30:30.664 - debug: backitup.0 (788) [iobroker/iobroker] host.ioBroker 16682 states saved
2023-03-05 23:30:31.084 - debug: backitup.0 (788) [iobroker/iobroker] host.ioBroker 17479 objects saved
2023-03-05 23:35:13.551 - debug: backitup.0 (788) [iobroker/iobroker] Backup created: /opt/iobroker/backups/iobroker_2023_03_05-23_30_20_backupiobroker.tar.gz
2023-03-05 23:35:14.892 - debug: backitup.0 (788) [iobroker/iobroker] done
2023-03-05 23:35:16.859 - debug: backitup.0 (788) [iobroker/cifs] used copy path: /media/EXTURBOPart1/ioBroker
2023-03-05 23:35:16.868 - debug: backitup.0 (788) [iobroker/cifs] done
2023-03-05 23:35:17.489 - debug: backitup.0 (788) [iobroker/clean] delete /opt/iobroker/backups/iobroker_2023_01_07-23_30_20_backupiobroker.tar.gz
2023-03-05 23:35:17.496 - debug: backitup.0 (788) [iobroker/clean] done
2023-03-05 23:35:18.477 - debug: backitup.0 (788) [iobroker/historyHTML] new history html values created
2023-03-05 23:35:18.479 - debug: backitup.0 (788) [iobroker/historyHTML] done
2023-03-05 23:35:18.650 - debug: backitup.0 (788) [iobroker/historyJSON] new history json values created
2023-03-05 23:35:18.651 - debug: backitup.0 (788) [iobroker/historyJSON] done
2023-03-05 23:35:18.858 - debug: backitup.0 (788) [iobroker/umount] mount activ, umount is started ...
2023-03-05 23:35:24.194 - debug: backitup.0 (788) [iobroker/umount] umount successfully completed
2023-03-05 23:35:24.197 - debug: backitup.0 (788) [iobroker/umount] done
2023-03-05 23:35:24.351 - debug: backitup.0 (788) [iobroker] exec: done
Am nächsten Tag wird kein Backup mehr erstellt. Das Log sieht dann so aus:
2023-03-07 23:30:10.126 - debug: backitup.0 (788) Backup has started ...
2023-03-07 23:30:20.126 - debug: backitup.0 (788) [iobroker/mount] nfs-mount command: "sudo mount 192.168.0.8:/media/EXTURBOPart1/ioBroker /opt/iobroker/backups"
2023-03-07 23:30:20.426 - debug: backitup.0 (788) [iobroker/mount] mount successfully completed
2023-03-07 23:30:20.428 - debug: backitup.0 (788) [iobroker/mount] done
2023-03-07 23:30:32.019 - debug: backitup.0 (788) [iobroker/iobroker] host.ioBroker 16752 states saved
2023-03-07 23:30:32.466 - debug: backitup.0 (788) [iobroker/iobroker] host.ioBroker 17549 objects saved
2023-03-07 23:30:40.520 - debug: backitup.0 (788) [iobroker/iobroker] done
2023-03-07 23:30:42.566 - debug: backitup.0 (788) [iobroker/cifs] used copy path: /media/EXTURBOPart1/ioBroker
2023-03-07 23:30:42.578 - debug: backitup.0 (788) [iobroker/cifs] done
2023-03-07 23:30:43.191 - debug: backitup.0 (788) [iobroker/clean] done
2023-03-07 23:30:44.105 - debug: backitup.0 (788) [iobroker/historyHTML] new history html values created
2023-03-07 23:30:44.106 - debug: backitup.0 (788) [iobroker/historyHTML] done
2023-03-07 23:30:44.274 - debug: backitup.0 (788) [iobroker/historyJSON] new history json values created
2023-03-07 23:30:44.276 - debug: backitup.0 (788) [iobroker/historyJSON] done
2023-03-07 23:30:44.768 - debug: backitup.0 (788) [iobroker/umount] mount activ, umount is started ...
2023-03-07 23:30:50.332 - debug: backitup.0 (788) [iobroker/umount] umount successfully completed
2023-03-07 23:30:50.367 - debug: backitup.0 (788) [iobroker/umount] done
2023-03-07 23:30:50.520 - debug: backitup.0 (788) [iobroker] exec: done
Die Zeile mit: Backup created fehlt hier. Aber warum?
Ich habe zu dem Thema schon einmal etwas hier gelesen. Da wurde vermutet, dass die SD Karte nicht in Ordnung wäre. Der Ersteller berichtete dann aber, das sich das Problem von selbst gelöst hätte. Die wahre Ursache ist also nicht ermittelt worden.
Ich plage mich mit der Problematik schon ein paar Monate herum. Leider löst es sichbei mir nicht von alleine.
Was nun?
Gruß
edition
@edition sagte in Backup nur nach Raspi Neustart, danach nicht mehr!:
Was nun?
Du hast nicht aus Versehen hier einen Eintrag gemacht?
Wobei ich nicht weiß, ob der Zähler beim Neustart zurückgesetzt wird. Ist nur so 'ne Idee ...
Ja, so wie auf deinem Bild. Days 1! Heißt für mich jeden Tag. Es wird ja auch jeden Tag ausgeführt. Aber die Zeile Backup created fehlt halt!
edition
Zeig mal die Einstellungen im Adapter.
CIFS oder NFS Freigaben?
Haupt:
IoBroker:
NAS:
ups. ganz schön klein
Schaut soweit korrekt aus.
Da fällt mir nix gescheites zu ein.
Und der Rest vom System schaut wie aus?
Guck mal per
iob diag
rein.
@thomas-braun sagte in Backup nur nach Raspi Neustart, danach nicht mehr!:
iob diag
======================= SUMMARY =======================
v.2023-01-02
Operatingsystem: Debian GNU/Linux 11 (bullseye)
Installation: Native
Timezone: Europe/Berlin
User-ID: 1000
X-Server: false
Boot Target: graphical.target
Pending OS-Updates: 3
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
ioBroker Core: js-controller 4.0.24
admin 6.3.5
ioBroker Status: iobroker is running on this host.
Objects type: jsonl
States type: jsonl
Status admin:
+ system.adapter.admin.0 : admin : ioBroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin
Pending iob updates: 0
Active repo(s): stable
Objects: 17571
States: 16775
Size of iob-Database:
22M /opt/iobroker/iobroker-data/objects.jsonl
19M /opt/iobroker/iobroker-data/states.jsonl
=================== END OF SUMMARY ====================
Oder alles?
Das passiert übrigens im syslog des Raspberry beim geklückten Backup:
Mar 5 23:31:11 ioBroker kernel: [44734.207252] pl2303 ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
Mar 5 23:31:13 ioBroker kernel: [44736.262747] pl2303 ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
Mar 5 23:33:01 ioBroker kernel: [44844.163127] pl2303 ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
Mar 5 23:33:02 ioBroker kernel: [44845.179872] pl2303 ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
Mar 5 23:34:48 ioBroker kernel: [44950.900415] INFO: task kworker/0:2:5268 blocked for more than 120 seconds.
Mar 5 23:34:48 ioBroker kernel: [44950.900480] Tainted: G C 5.15.84-v8+ #1613
Mar 5 23:34:49 ioBroker kernel: [44950.900498] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Mar 5 23:34:50 ioBroker kernel: [44950.900512] task:kworker/0:2 state:D stack: 0 pid: 5268 ppid: 2 flags:0x00000008
Mar 5 23:34:50 ioBroker kernel: [44950.900555] Workqueue: events_freezable mmc_rescan
Mar 5 23:34:50 ioBroker kernel: [44950.900596] Call trace:
Mar 5 23:34:50 ioBroker kernel: [44950.900608] __switch_to+0x114/0x1c8
Mar 5 23:34:50 ioBroker kernel: [44950.900634] __schedule+0x2e4/0x888
Mar 5 23:34:50 ioBroker kernel: [44950.900657] schedule+0x68/0x128
Mar 5 23:34:50 ioBroker kernel: [44950.900678] __mmc_claim_host+0xbc/0x208
Mar 5 23:34:50 ioBroker kernel: [44950.900698] mmc_get_card+0x3c/0x50
Mar 5 23:34:50 ioBroker kernel: [44950.900726] mmc_sd_detect+0x28/0x98
Mar 5 23:34:50 ioBroker kernel: [44950.900750] mmc_rescan+0xa0/0x2c8
Mar 5 23:34:50 ioBroker kernel: [44950.900769] process_one_work+0x1f8/0x4a0
Mar 5 23:34:50 ioBroker kernel: [44950.900791] worker_thread+0x50/0x480
Mar 5 23:34:50 ioBroker kernel: [44950.900812] kthread+0x140/0x158
Mar 5 23:34:50 ioBroker kernel: [44950.900831] ret_from_fork+0x10/0x20
Mar 5 23:35:09 ioBroker systemd[1]: systemd-journald.service: Killing process 140 (systemd-journal) with signal SIGABRT.
Mar 5 23:35:09 ioBroker systemd[1]: Starting Flush Journal to Persistent Storage...
Mar 5 23:35:09 ioBroker systemd[1]: Finished Flush Journal to Persistent Storage.
Mar 5 23:35:24 ioBroker systemd[1]: opt-iobroker-backups.mount: Succeeded.
Und das beim fehlgeschlagenen:
Mar 7 23:30:39 ioBroker kernel: [217503.818752] CPU: 3 PID: 24286 Comm: node Tainted: G C 5.15.84-v8+ #1613
Mar 7 23:30:39 ioBroker kernel: [217503.818762] Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 (DT)
Mar 7 23:30:39 ioBroker kernel: [217503.818767] Call trace:
Mar 7 23:30:39 ioBroker kernel: [217503.818770] dump_backtrace+0x0/0x1b8
Mar 7 23:30:39 ioBroker kernel: [217503.818787] show_stack+0x20/0x30
Mar 7 23:30:39 ioBroker kernel: [217503.818795] dump_stack_lvl+0x8c/0xb8
Mar 7 23:30:39 ioBroker kernel: [217503.818805] dump_stack+0x18/0x34
Mar 7 23:30:39 ioBroker kernel: [217503.818812] dump_header+0x4c/0x204
Mar 7 23:30:39 ioBroker kernel: [217503.818819] oom_kill_process+0x1f8/0x200
Mar 7 23:30:39 ioBroker kernel: [217503.818828] out_of_memory+0xf0/0x330
Mar 7 23:30:39 ioBroker kernel: [217503.818835] __alloc_pages_slowpath.constprop.155+0x84c/0xba0
Mar 7 23:30:39 ioBroker kernel: [217503.818843] __alloc_pages+0x2b0/0x330
Mar 7 23:30:39 ioBroker kernel: [217503.818849] alloc_zeroed_user_highpage_movable+0x40/0x50
Mar 7 23:30:39 ioBroker kernel: [217503.818859] __handle_mm_fault+0x384/0xa38
Mar 7 23:30:39 ioBroker kernel: [217503.818868] handle_mm_fault+0x1a4/0x288
Mar 7 23:30:39 ioBroker kernel: [217503.818876] do_page_fault+0x240/0x480
Mar 7 23:30:39 ioBroker kernel: [217503.818883] do_translation_fault+0x60/0x78
Mar 7 23:30:39 ioBroker kernel: [217503.818889] do_mem_abort+0x48/0xb8
Mar 7 23:30:39 ioBroker kernel: [217503.818896] el0_da+0x3c/0x78
Mar 7 23:30:39 ioBroker kernel: [217503.818903] el0t_64_sync_handler+0x68/0xb8
Mar 7 23:30:39 ioBroker kernel: [217503.818910] el0t_64_sync+0x1a0/0x1a4
Mar 7 23:30:39 ioBroker kernel: [217503.818918] Mem-Info:
Mar 7 23:30:39 ioBroker kernel: [217503.818926] active_anon:47469 inactive_anon:164181 isolated_anon:0
Mar 7 23:30:39 ioBroker kernel: [217503.818926] active_file:1 inactive_file:0 isolated_file:0
Mar 7 23:30:39 ioBroker kernel: [217503.818926] unevictable:4 dirty:0 writeback:8
Mar 7 23:30:39 ioBroker kernel: [217503.818926] slab_reclaimable:4132 slab_unreclaimable:5797
Mar 7 23:30:39 ioBroker kernel: [217503.818926] mapped:11 shmem:31 pagetables:1246 bounce:0
Mar 7 23:30:39 ioBroker kernel: [217503.818926] kernel_misc_reclaimable:0
Mar 7 23:30:39 ioBroker kernel: [217503.818926] free:4960 free_pcp:0 free_cma:46
Mar 7 23:30:39 ioBroker kernel: [217503.818943] Node 0 active_anon:189876kB inactive_anon:656724kB active_file:4kB inactive_file:0kB unevictable:16kB isolated(anon):0kB isolated(file):0kB mapped:44kB dirty:0kB writeback:32kB shmem:124kB writeback_tmp:0kB kernel_stack:3344kB pagetables:4984kB all_unreclaimable? no
Mar 7 23:30:39 ioBroker kernel: [217503.818959] DMA free:19840kB min:20480kB low:24576kB high:28672kB reserved_highatomic:0KB active_anon:189876kB inactive_anon:656740kB active_file:152kB inactive_file:560kB unevictable:16kB writepending:32kB present:970752kB managed:931460kB mlocked:16kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:184kB
Mar 7 23:30:39 ioBroker kernel: [217503.818977] lowmem_reserve[]: 0 0 0 0
Mar 7 23:30:39 ioBroker kernel: [217503.819017] DMA: 904*4kB (UMEC) 525*8kB (UMEC) 260*16kB (UMEC) 139*32kB (UME) 36*64kB (UME) 15*128kB (UME) 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 20648kB
Mar 7 23:30:39 ioBroker kernel: [217503.819133] 535 total pagecache pages
Mar 7 23:30:39 ioBroker kernel: [217503.819140] 457 pages in swap cache
Mar 7 23:30:39 ioBroker kernel: [217503.819146] Swap cache stats: add 47969, delete 47512, find 16001/22071
Mar 7 23:30:39 ioBroker kernel: [217503.819154] Free swap = 0kB
Mar 7 23:30:39 ioBroker kernel: [217503.819160] Total swap = 102396kB
Mar 7 23:30:39 ioBroker kernel: [217503.819167] 242688 pages RAM
Mar 7 23:30:39 ioBroker kernel: [217503.819173] 0 pages HighMem/MovableOnly
Mar 7 23:30:39 ioBroker kernel: [217503.819179] 9823 pages reserved
Mar 7 23:30:39 ioBroker kernel: [217503.819185] 65536 pages cma reserved
Mar 7 23:30:39 ioBroker kernel: [217503.819191] Tasks state (memory values in pages):
Mar 7 23:30:39 ioBroker kernel: [217503.819197] [ pid ] uid tgid total_vm rss pgtables_bytes swapents oom_score_adj name
Mar 7 23:30:39 ioBroker kernel: [217503.819221] [ 169] 0 169 5304 101 53248 399 -1000 systemd-udevd
Mar 7 23:30:39 ioBroker kernel: [217503.819237] [ 285] 101 285 22027 40 65536 150 0 systemd-timesyn
Mar 7 23:30:39 ioBroker kernel: [217503.819251] [ 365] 108 365 1801 110 45056 45 0 avahi-daemon
Mar 7 23:30:39 ioBroker kernel: [217503.819263] [ 366] 0 366 1674 26 49152 38 0 cron
Mar 7 23:30:39 ioBroker kernel: [217503.819276] [ 368] 104 368 1997 94 49152 60 -900 dbus-daemon
Mar 7 23:30:39 ioBroker kernel: [217503.819288] [ 380] 108 380 1723 14 40960 64 0 avahi-daemon
Mar 7 23:30:39 ioBroker kernel: [217503.819301] [ 389] 0 389 55221 150 61440 136 0 rsyslogd
Mar 7 23:30:39 ioBroker kernel: [217503.819313] [ 396] 0 396 3528 38 61440 153 0 systemd-logind
Mar 7 23:30:39 ioBroker kernel: [217503.819326] [ 399] 65534 399 1371 8 45056 49 0 thd
Mar 7 23:30:39 ioBroker kernel: [217503.819338] [ 404] 0 404 3395 16 57344 150 0 wpa_supplicant
Mar 7 23:30:39 ioBroker kernel: [217503.819351] [ 451] 0 451 23073 27 45056 10 0 rngd
Mar 7 23:30:39 ioBroker kernel: [217503.819363] [ 457] 1001 457 271065 43811 925696 14939 0 iobroker.js-con
Mar 7 23:30:39 ioBroker kernel: [217503.819375] [ 471] 0 471 1369 0 40960 30 0 agetty
Mar 7 23:30:39 ioBroker kernel: [217503.819388] [ 477] 0 477 3413 0 53248 237 -1000 sshd
Mar 7 23:30:39 ioBroker kernel: [217503.819400] [ 480] 0 480 3497 23 57344 213 0 wpa_supplicant
Mar 7 23:30:39 ioBroker kernel: [217503.819414] [ 508] 0 508 531 0 32768 34 0 hciattach
Mar 7 23:30:39 ioBroker kernel: [217503.819426] [ 551] 0 551 5890 1 81920 297 0 bluetoothd
Mar 7 23:30:39 ioBroker kernel: [217503.819438] [ 664] 0 664 763 62 49152 51 0 dhcpcd
Mar 7 23:30:39 ioBroker kernel: [217503.819451] [ 708] 1001 708 239516 19031 520192 2140 0 io.admin.0
Mar 7 23:30:39 ioBroker kernel: [217503.819464] [ 739] 1001 739 170446 18503 454656 3106 0 io.fhem.0
Mar 7 23:30:39 ioBroker kernel: [217503.819476] [ 762] 1001 762 231373 14793 385024 693 0 io.smartmeter.0
Mar 7 23:30:39 ioBroker kernel: [217503.819489] [ 773] 1001 773 161000 8604 327680 646 0 io.discovery.0
Mar 7 23:30:39 ioBroker kernel: [217503.819508] [ 788] 1001 788 179938 10373 368640 1633 0 io.backitup.0
Mar 7 23:30:39 ioBroker kernel: [217503.819521] [ 5384] 0 5384 12272 222 90112 0 -250 systemd-journal
Mar 7 23:30:39 ioBroker kernel: [217503.819540] [ 24286] 1001 24286 257719 94356 1064960 0 0 node
Mar 7 23:30:39 ioBroker kernel: [217503.819552] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/,task=node,pid=24286,uid=1001
Mar 7 23:30:39 ioBroker kernel: [217503.819643] Out of memory: Killed process 24286 (node) total-vm:1030876kB, anon-rss:377420kB, file-rss:4kB, shmem-rss:0kB, UID:1001 pgtables:1040kB oom_score_adj:0
Mar 7 23:30:50 ioBroker systemd[1]: opt-iobroker-backups.mount: Succeeded.
Beim IO Backup vergehen über 5 min bis zum mount: Succeedd, beim NIO nicht mal eine! Außerdem lese ich da was von out of memory!
@edition sagte in Backup nur nach Raspi Neustart, danach nicht mehr!:
lese ich da was von out of memory!
Und ich vermute mit meinem laienhaften Halbwissen einfach mal: Da liegt der Hase im Pfeffer.
Kann es sein, dass die Kiste beim 2. (und allen weiteren) Backups einfach nicht mehr genügend RAM hat?
@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 145
Aktuelle 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!:
lese ich da was von out of memory!
Und ich vermute mit meinem laienhaften Halbwissen einfach mal: Da liegt der Hase im Pfeffer.
Kann es sein, dass die Kiste beim 2. (und allen weiteren) Backups einfach nicht mehr genügend RAM hat?
