NEWS
js-controller 5.0.x jetzt für alle User im STABLE!
ioBroker Allgemein
509
Beiträge
82
Kommentatoren
139.1k
Aufrufe
65
Watching
-
Ich habe gestern den Sonos-Adapter deinstalliert. Das Backup ist die Nacht einwandfrei gelaufen.
Nutzt du den Sonos-Adapter?
@ofbeqnpolkkl6mby5e13 sagte in js-controller 5.0.x jetzt für alle User im STABLE!:
Ich habe gestern den Sonos-Adapter deinstalliert. Das Backup ist die Nacht einwandfrei gelaufen.
Nutzt du den Sonos-Adapter?
Hi, nein den nutze ich nicht.
Vom Bauchgefühl her tippe ich auf eine Änderung in Node 18.17.1, denn mit Node 18.17.0 läuft alles..
Ich habe 68 Adapter und 47000 States und 44000 Objekte, waren mal über 120000.. aber daran lag es nicht.
Mein lxc hat 32gb Ram und 8 Cores mit debian Bookworm, beim Betrieb sind meist 10-11 Gb Ram belegt, wobei linux ja einiges reserviert..Ich habe auch schon mit den Einstellungen im js-Controller beim Ram experimtiert, das brachte aber eher mehr Fehler..
Wenn ich in ein paar Wochen wieder zurück bin, nehm ich mir das Problem mal genauer vor..
zur Zeit muss das alles so bleiben, läuft auch ohne Probleme stable durch.. -
Ich habe ihn auch aus weiteren Gründen deinstalliert. Ich bin diesen Adapter einfach leid. Er stürzt immer mal wieder ab, mit JS-Controller 5 verursacht er eine Meldung des Web-Adapters (Binary States) und er wird letztlich seit Jahren nicht mehr gepflegt. Ich nutze zur Steuerung sowieso die HTTP-API.
@ofbeqnpolkkl6mby5e13
Hast du diesbezüglich ein issue beim Adapter eröffnet?
Binary States sind allerdings nur eine deprecation WARNUNG da diese mit js-controller 5 noch unterstütz werden, -
@ofbeqnpolkkl6mby5e13 sagte in js-controller 5.0.x jetzt für alle User im STABLE!:
Ich habe gestern den Sonos-Adapter deinstalliert. Das Backup ist die Nacht einwandfrei gelaufen.
Nutzt du den Sonos-Adapter?
Hi, nein den nutze ich nicht.
Vom Bauchgefühl her tippe ich auf eine Änderung in Node 18.17.1, denn mit Node 18.17.0 läuft alles..
Ich habe 68 Adapter und 47000 States und 44000 Objekte, waren mal über 120000.. aber daran lag es nicht.
Mein lxc hat 32gb Ram und 8 Cores mit debian Bookworm, beim Betrieb sind meist 10-11 Gb Ram belegt, wobei linux ja einiges reserviert..Ich habe auch schon mit den Einstellungen im js-Controller beim Ram experimtiert, das brachte aber eher mehr Fehler..
Wenn ich in ein paar Wochen wieder zurück bin, nehm ich mir das Problem mal genauer vor..
zur Zeit muss das alles so bleiben, läuft auch ohne Probleme stable durch..Dann wissen wir jetzt wohl nur eine Sache sicher:
- Hat nichts mit dem Sonos-Adapter zu tun
-
Dann wissen wir jetzt wohl nur eine Sache sicher:
- Hat nichts mit dem Sonos-Adapter zu tun
- doch gerade mit der 18.17.1 hab ich den Fehler
-
@ofbeqnpolkkl6mby5e13
Hast du diesbezüglich ein issue beim Adapter eröffnet?
Binary States sind allerdings nur eine deprecation WARNUNG da diese mit js-controller 5 noch unterstütz werden,@mcm57
Es gibt bereits ein Issue dafür, welches von @apollon77 mal erstellt wurde.
Beim Web-Adapter wurde das von mir erstellte Issue geschlossen, weil der Web-Adapter das vom Sonos-Adapter nur "durchreicht". -
- doch gerade mit der 18.17.1 hab ich den Fehler
Ach so, missverstanden! Mist!
-
- doch gerade mit der 18.17.1 hab ich den Fehler
-
Ich habe bei meinem Testpi nun einmal den Sonos Adapter installiert und dann ein Backup mit dem Backitup Adapter gemacht.
Es lief anstandslos durch.
node.js ist 18.17.1 und npm 9.6.7
js-controller 5.0.12
Pi mit Bookworm
Sonos Adapter 2.5.3Leider fehlt mir der Mut den js-controller auf meinem Aktivsystem zu aktualisieren
Aber vielleicht kann mein Beitrag trotzdem zur Fehlerfindung beitragen.Started iobroker ... [DEBUG] [iobroker] - host.Testpi 659 states saved [DEBUG] [iobroker] - host.Testpi 866 objects saved [DEBUG] [iobroker] - Backup created: /opt/iobroker/backups/iobroker_2023_09_18-12_11_15_Testpi_backupiobroker.tar.gz [DEBUG] [iobroker] - This backup can only be restored with js-controller version up from 4.1 [DEBUG] [iobroker] - done [DEBUG] [influxDB] - InfluxDB-Backup for influxDB-1 is started ... [DEBUG] [influxDB] - Start InfluxDB Backup ... [DEBUG] [influxDB] - InfluxDB Backup tmp directory created [DEBUG] [influxDB] - Backup created: /opt/iobroker/backups/influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [influxDB] - Try deleting the InfluxDB tmp directory: "/opt/iobroker/backups/influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker" [DEBUG] [influxDB] - InfluxDB tmp directory "/opt/iobroker/backups/influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker" successfully deleted [DEBUG] [influxDB] - InfluxDB-Backup for influxDB-1 is finish [DEBUG] [influxDB] - InfluxDB-Backup for influxDB-2 is started ... [DEBUG] [influxDB] - Start InfluxDB Backup ... [DEBUG] [influxDB] - InfluxDB Backup tmp directory created [DEBUG] [influxDB] - Backup created: /opt/iobroker/backups/influxDB_2023_09_18-12_11_39_influxDB-2_backupiobroker.tar.gz [DEBUG] [influxDB] - Try deleting the InfluxDB tmp directory: "/opt/iobroker/backups/influxDB_2023_09_18-12_11_39_influxDB-2_backupiobroker" [DEBUG] [influxDB] - InfluxDB tmp directory "/opt/iobroker/backups/influxDB_2023_09_18-12_11_39_influxDB-2_backupiobroker" successfully deleted [DEBUG] [influxDB] - InfluxDB-Backup for influxDB-2 is finish [DEBUG] [influxDB] - InfluxDB-Backup for influxDB-3 is started ... [DEBUG] [influxDB] - Start InfluxDB Backup ... [DEBUG] [influxDB] - InfluxDB Backup tmp directory created [DEBUG] [influxDB] - Backup created: /opt/iobroker/backups/influxDB_2023_09_18-12_11_39_influxDB-3_backupiobroker.tar.gz [DEBUG] [influxDB] - Try deleting the InfluxDB tmp directory: "/opt/iobroker/backups/influxDB_2023_09_18-12_11_39_influxDB-3_backupiobroker" [DEBUG] [influxDB] - InfluxDB tmp directory "/opt/iobroker/backups/influxDB_2023_09_18-12_11_39_influxDB-3_backupiobroker" successfully deleted [DEBUG] [influxDB] - InfluxDB-Backup for influxDB-3 is finish [DEBUG] [influxDB] - InfluxDB-Backup for influxDB-4 is started ... [DEBUG] [influxDB] - Start InfluxDB Backup ... [DEBUG] [influxDB] - InfluxDB Backup tmp directory created [DEBUG] [influxDB] - Backup created: /opt/iobroker/backups/influxDB_2023_09_18-12_11_40_influxDB-4_backupiobroker.tar.gz [DEBUG] [influxDB] - Try deleting the InfluxDB tmp directory: "/opt/iobroker/backups/influxDB_2023_09_18-12_11_40_influxDB-4_backupiobroker" [DEBUG] [influxDB] - InfluxDB tmp directory "/opt/iobroker/backups/influxDB_2023_09_18-12_11_40_influxDB-4_backupiobroker" successfully deleted [DEBUG] [influxDB] - InfluxDB-Backup for influxDB-4 is finish [DEBUG] [influxDB] - done [DEBUG] [zigbee] - found zigbee database: zigbee.0 [DEBUG] [zigbee] - done [DEBUG] [onedrive] - Onedrive: Copy iobroker_2023_09_18-12_11_15_Testpi_backupiobroker.tar.gz... [DEBUG] [onedrive] - 47% uploaded from iobroker_2023_09_18-12_11_15_Testpi_backupiobroker.tar.gz [DEBUG] [onedrive] - 94% uploaded from iobroker_2023_09_18-12_11_15_Testpi_backupiobroker.tar.gz [DEBUG] [onedrive] - 100% uploaded from iobroker_2023_09_18-12_11_15_Testpi_backupiobroker.tar.gz [DEBUG] [onedrive] - iobroker_2023_09_18-12_11_15_Testpi_backupiobroker.tar.gz with Id: 265B81AA2EF75ADE!1160 saved on Onedrive [DEBUG] [onedrive] - Onedrive: Copy influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz... [DEBUG] [onedrive] - 2% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 5% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 7% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 10% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 12% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 14% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 17% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 19% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 22% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 24% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 26% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 29% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 31% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 34% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 36% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 38% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 41% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 43% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 46% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 48% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 50% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 53% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 55% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 58% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 60% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 62% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 65% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 67% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 70% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 72% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 74% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 77% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 79% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 82% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 84% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 86% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 89% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 91% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 94% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 96% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 98% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 100% uploaded from influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - influxDB_2023_09_18-12_11_20_influxDB-1_backupiobroker.tar.gz with Id: 265B81AA2EF75ADE!1161 saved on Onedrive [DEBUG] [onedrive] - Onedrive: Copy influxDB_2023_09_18-12_11_39_influxDB-2_backupiobroker.tar.gz... [DEBUG] [onedrive] - 100% uploaded from influxDB_2023_09_18-12_11_39_influxDB-2_backupiobroker.tar.gz [DEBUG] [onedrive] - influxDB_2023_09_18-12_11_39_influxDB-2_backupiobroker.tar.gz with Id: 265B81AA2EF75ADE!1162 saved on Onedrive [DEBUG] [onedrive] - Onedrive: Copy influxDB_2023_09_18-12_11_39_influxDB-3_backupiobroker.tar.gz... [DEBUG] [onedrive] - 100% uploaded from influxDB_2023_09_18-12_11_39_influxDB-3_backupiobroker.tar.gz [DEBUG] [onedrive] - influxDB_2023_09_18-12_11_39_influxDB-3_backupiobroker.tar.gz with Id: 265B81AA2EF75ADE!1163 saved on Onedrive [DEBUG] [onedrive] - Onedrive: Copy influxDB_2023_09_18-12_11_40_influxDB-4_backupiobroker.tar.gz... [DEBUG] [onedrive] - 100% uploaded from influxDB_2023_09_18-12_11_40_influxDB-4_backupiobroker.tar.gz [DEBUG] [onedrive] - influxDB_2023_09_18-12_11_40_influxDB-4_backupiobroker.tar.gz with Id: 265B81AA2EF75ADE!1164 saved on Onedrive [DEBUG] [onedrive] - Onedrive: Copy zigbee.0_2023_09_18-12_11_41_Testpi_backupiobroker.tar.gz... [DEBUG] [onedrive] - 100% uploaded from zigbee.0_2023_09_18-12_11_41_Testpi_backupiobroker.tar.gz [DEBUG] [onedrive] - zigbee.0_2023_09_18-12_11_41_Testpi_backupiobroker.tar.gz with Id: 265B81AA2EF75ADE!1165 saved on Onedrive [DEBUG] [onedrive] - done [DEBUG] [clean] - No older backup files are deleted, because this backup was started manually [DEBUG] [clean] - done [DEBUG] [historyHTML] - new history html values created [DEBUG] [historyHTML] - done [DEBUG] [historyJSON] - new history json values created [DEBUG] [historyJSON] - done [EXIT] 0VG Duffy
@duffy Danke für Dein aufschlussreiches Feedback. Bei den Unterschieden unserer Systemvoraussetzungen ist mir neben dem Pi mit Bookworm aufgefallen, dass Du gegenüber meiner eingesetzten SONOS-Version 2.3.1 die neuere Version 2.5.3 vom SONOS Adapter angegeben hast. Wo und wie komme ich zu der Version 2.5.3 vom SONOS-Adapter?
Gerne würde ich einen Versuch mit dem backitup Adapter unter js-Controller 5.0.12, mit installiertem SONOS Adapter v 2.5.3 durchführen um zu testen, ob der backitup Adapter immer noch einen Systemcrash auslöst.
-
@duffy Danke für Dein aufschlussreiches Feedback. Bei den Unterschieden unserer Systemvoraussetzungen ist mir neben dem Pi mit Bookworm aufgefallen, dass Du gegenüber meiner eingesetzten SONOS-Version 2.3.1 die neuere Version 2.5.3 vom SONOS Adapter angegeben hast. Wo und wie komme ich zu der Version 2.5.3 vom SONOS-Adapter?
Gerne würde ich einen Versuch mit dem backitup Adapter unter js-Controller 5.0.12, mit installiertem SONOS Adapter v 2.5.3 durchführen um zu testen, ob der backitup Adapter immer noch einen Systemcrash auslöst.
Die aktuelle Version des sonos adapters (ioBroker.sonos) ist sowohl auf github als auch auf npm die 2.3.1. Hinweise auf eine 2.5.3 konnte ich nicht finden.
Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
Support Repositoryverwaltung.Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker
-
@mcm57 sagte in js-controller 5.0.x jetzt für alle User im STABLE!:
Hinweise auf eine 2.5.3 konnte ich nicht finden.
da wird @Duffy wohl in der Zeile verrutscht sein und den Sonoff Adapter erwischt haben ...
-
@duffy Danke für Dein aufschlussreiches Feedback. Bei den Unterschieden unserer Systemvoraussetzungen ist mir neben dem Pi mit Bookworm aufgefallen, dass Du gegenüber meiner eingesetzten SONOS-Version 2.3.1 die neuere Version 2.5.3 vom SONOS Adapter angegeben hast. Wo und wie komme ich zu der Version 2.5.3 vom SONOS-Adapter?
Gerne würde ich einen Versuch mit dem backitup Adapter unter js-Controller 5.0.12, mit installiertem SONOS Adapter v 2.5.3 durchführen um zu testen, ob der backitup Adapter immer noch einen Systemcrash auslöst.
-
Asche auf mein Haupt, Marc Berg hat recht.
Ich bitte vielmals um Entschuldigung!Edit:
Korrektur: Sonoff 2.5.3
Jetzt habe ich aber wirklich SONOS 2.3.1 installiert und ein Backup gemacht.
Es lief durch.
Started iobroker ... [DEBUG] [iobroker] - host.Testpi 730 states saved [DEBUG] [iobroker] - host.Testpi 950 objects saved [DEBUG] [iobroker] - Backup created: /opt/iobroker/backups/iobroker_2023_09_18-13_20_20_Testpi_backupiobroker.tar.gz This backup can only be restored with js-controller version up from 4.1 [DEBUG] [iobroker] - done [DEBUG] [influxDB] - InfluxDB-Backup for influxDB-1 is started ... [DEBUG] [influxDB] - Start InfluxDB Backup ... [DEBUG] [influxDB] - InfluxDB Backup tmp directory created [DEBUG] [influxDB] - Backup created: /opt/iobroker/backups/influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [influxDB] - Try deleting the InfluxDB tmp directory: "/opt/iobroker/backups/influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker" [DEBUG] [influxDB] - InfluxDB tmp directory "/opt/iobroker/backups/influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker" successfully deleted [DEBUG] [influxDB] - InfluxDB-Backup for influxDB-1 is finish [DEBUG] [influxDB] - InfluxDB-Backup for influxDB-2 is started ... [DEBUG] [influxDB] - Start InfluxDB Backup ... [DEBUG] [influxDB] - InfluxDB Backup tmp directory created [DEBUG] [influxDB] - Backup created: /opt/iobroker/backups/influxDB_2023_09_18-13_20_45_influxDB-2_backupiobroker.tar.gz [DEBUG] [influxDB] - Try deleting the InfluxDB tmp directory: "/opt/iobroker/backups/influxDB_2023_09_18-13_20_45_influxDB-2_backupiobroker" [DEBUG] [influxDB] - InfluxDB tmp directory "/opt/iobroker/backups/influxDB_2023_09_18-13_20_45_influxDB-2_backupiobroker" successfully deleted [DEBUG] [influxDB] - InfluxDB-Backup for influxDB-2 is finish [DEBUG] [influxDB] - InfluxDB-Backup for influxDB-3 is started ... [DEBUG] [influxDB] - Start InfluxDB Backup ... [DEBUG] [influxDB] - InfluxDB Backup tmp directory created [DEBUG] [influxDB] - Backup created: /opt/iobroker/backups/influxDB_2023_09_18-13_20_45_influxDB-3_backupiobroker.tar.gz [DEBUG] [influxDB] - Try deleting the InfluxDB tmp directory: "/opt/iobroker/backups/influxDB_2023_09_18-13_20_45_influxDB-3_backupiobroker" [DEBUG] [influxDB] - InfluxDB tmp directory "/opt/iobroker/backups/influxDB_2023_09_18-13_20_45_influxDB-3_backupiobroker" successfully deleted [DEBUG] [influxDB] - InfluxDB-Backup for influxDB-3 is finish [DEBUG] [influxDB] - InfluxDB-Backup for influxDB-4 is started ... [DEBUG] [influxDB] - Start InfluxDB Backup ... [DEBUG] [influxDB] - InfluxDB Backup tmp directory created [DEBUG] [influxDB] - Backup created: /opt/iobroker/backups/influxDB_2023_09_18-13_20_45_influxDB-4_backupiobroker.tar.gz [DEBUG] [influxDB] - Try deleting the InfluxDB tmp directory: "/opt/iobroker/backups/influxDB_2023_09_18-13_20_45_influxDB-4_backupiobroker" [DEBUG] [influxDB] - InfluxDB tmp directory "/opt/iobroker/backups/influxDB_2023_09_18-13_20_45_influxDB-4_backupiobroker" successfully deleted [DEBUG] [influxDB] - InfluxDB-Backup for influxDB-4 is finish [DEBUG] [influxDB] - done [DEBUG] [zigbee] - found zigbee database: zigbee.0 [DEBUG] [zigbee] - done [DEBUG] [onedrive] - Onedrive: Copy iobroker_2023_09_18-13_20_20_Testpi_backupiobroker.tar.gz... [DEBUG] [onedrive] - 47% uploaded from iobroker_2023_09_18-13_20_20_Testpi_backupiobroker.tar.gz [DEBUG] [onedrive] - 94% uploaded from iobroker_2023_09_18-13_20_20_Testpi_backupiobroker.tar.gz [DEBUG] [onedrive] - 100% uploaded from iobroker_2023_09_18-13_20_20_Testpi_backupiobroker.tar.gz [DEBUG] [onedrive] - iobroker_2023_09_18-13_20_20_Testpi_backupiobroker.tar.gz with Id: 265B81AA2EF75ADE!1166 saved on Onedrive [DEBUG] [onedrive] - Onedrive: Copy influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz... [DEBUG] [onedrive] - 2% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 5% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 7% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 10% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 12% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 14% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 17% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 19% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 22% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 24% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 26% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 29% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 31% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 34% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 36% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 38% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 41% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 43% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 46% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 48% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 50% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 53% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 55% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 58% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 60% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 62% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 65% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 67% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 70% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 72% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 74% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 77% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 79% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 82% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 84% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 86% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 89% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 91% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 94% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 96% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 98% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 100% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz with Id: 265B81AA2EF75ADE!1167 saved on Onedrive [DEBUG] [onedrive] - Onedrive: Copy influxDB_2023_09_18-13_20_45_influxDB-2_backupiobroker.tar.gz... [DEBUG] [onedrive] - 100% uploaded from influxDB_2023_09_18-13_20_45_influxDB-2_backupiobroker.tar.gz [DEBUG] [onedrive] - influxDB_2023_09_18-13_20_45_influxDB-2_backupiobroker.tar.gz with Id: 265B81AA2EF75ADE!1168 saved on Onedrive [DEBUG] [onedrive] - Onedrive: Copy influxDB_2023_09_18-13_20_45_influxDB-3_backupiobroker.tar.gz... [DEBUG] [onedrive] - 100% uploaded from influxDB_2023_09_18-13_20_45_influxDB-3_backupiobroker.tar.gz [DEBUG] [onedrive] - influxDB_2023_09_18-13_20_45_influxDB-3_backupiobroker.tar.gz with Id: 265B81AA2EF75ADE!1169 saved on Onedrive [DEBUG] [onedrive] - Onedrive: Copy influxDB_2023_09_18-13_20_45_influxDB-4_backupiobroker.tar.gz... [DEBUG] [onedrive] - 100% uploaded from influxDB_2023_09_18-13_20_45_influxDB-4_backupiobroker.tar.gz [DEBUG] [onedrive] - influxDB_2023_09_18-13_20_45_influxDB-4_backupiobroker.tar.gz with Id: 265B81AA2EF75ADE!1170 saved on Onedrive [DEBUG] [onedrive] - Onedrive: Copy zigbee.0_2023_09_18-13_20_47_Testpi_backupiobroker.tar.gz... [DEBUG] [onedrive] - 100% uploaded from zigbee.0_2023_09_18-13_20_47_Testpi_backupiobroker.tar.gz [DEBUG] [onedrive] - zigbee.0_2023_09_18-13_20_47_Testpi_backupiobroker.tar.gz with Id: 265B81AA2EF75ADE!1171 saved on Onedrive [DEBUG] [onedrive] - done [DEBUG] [clean] - No older backup files are deleted, because this backup was started manually [DEBUG] [clean] - done [DEBUG] [historyHTML] - new history html values created [DEBUG] [historyHTML] - done [DEBUG] [historyJSON] - new history json values created [DEBUG] [historyJSON] - done [EXIT] 0VG
-
Jetzt habe ich aber wirklich SONOS 2.3.1 installiert und ein Backup gemacht.
Es lief durch.
Started iobroker ... [DEBUG] [iobroker] - host.Testpi 730 states saved [DEBUG] [iobroker] - host.Testpi 950 objects saved [DEBUG] [iobroker] - Backup created: /opt/iobroker/backups/iobroker_2023_09_18-13_20_20_Testpi_backupiobroker.tar.gz This backup can only be restored with js-controller version up from 4.1 [DEBUG] [iobroker] - done [DEBUG] [influxDB] - InfluxDB-Backup for influxDB-1 is started ... [DEBUG] [influxDB] - Start InfluxDB Backup ... [DEBUG] [influxDB] - InfluxDB Backup tmp directory created [DEBUG] [influxDB] - Backup created: /opt/iobroker/backups/influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [influxDB] - Try deleting the InfluxDB tmp directory: "/opt/iobroker/backups/influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker" [DEBUG] [influxDB] - InfluxDB tmp directory "/opt/iobroker/backups/influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker" successfully deleted [DEBUG] [influxDB] - InfluxDB-Backup for influxDB-1 is finish [DEBUG] [influxDB] - InfluxDB-Backup for influxDB-2 is started ... [DEBUG] [influxDB] - Start InfluxDB Backup ... [DEBUG] [influxDB] - InfluxDB Backup tmp directory created [DEBUG] [influxDB] - Backup created: /opt/iobroker/backups/influxDB_2023_09_18-13_20_45_influxDB-2_backupiobroker.tar.gz [DEBUG] [influxDB] - Try deleting the InfluxDB tmp directory: "/opt/iobroker/backups/influxDB_2023_09_18-13_20_45_influxDB-2_backupiobroker" [DEBUG] [influxDB] - InfluxDB tmp directory "/opt/iobroker/backups/influxDB_2023_09_18-13_20_45_influxDB-2_backupiobroker" successfully deleted [DEBUG] [influxDB] - InfluxDB-Backup for influxDB-2 is finish [DEBUG] [influxDB] - InfluxDB-Backup for influxDB-3 is started ... [DEBUG] [influxDB] - Start InfluxDB Backup ... [DEBUG] [influxDB] - InfluxDB Backup tmp directory created [DEBUG] [influxDB] - Backup created: /opt/iobroker/backups/influxDB_2023_09_18-13_20_45_influxDB-3_backupiobroker.tar.gz [DEBUG] [influxDB] - Try deleting the InfluxDB tmp directory: "/opt/iobroker/backups/influxDB_2023_09_18-13_20_45_influxDB-3_backupiobroker" [DEBUG] [influxDB] - InfluxDB tmp directory "/opt/iobroker/backups/influxDB_2023_09_18-13_20_45_influxDB-3_backupiobroker" successfully deleted [DEBUG] [influxDB] - InfluxDB-Backup for influxDB-3 is finish [DEBUG] [influxDB] - InfluxDB-Backup for influxDB-4 is started ... [DEBUG] [influxDB] - Start InfluxDB Backup ... [DEBUG] [influxDB] - InfluxDB Backup tmp directory created [DEBUG] [influxDB] - Backup created: /opt/iobroker/backups/influxDB_2023_09_18-13_20_45_influxDB-4_backupiobroker.tar.gz [DEBUG] [influxDB] - Try deleting the InfluxDB tmp directory: "/opt/iobroker/backups/influxDB_2023_09_18-13_20_45_influxDB-4_backupiobroker" [DEBUG] [influxDB] - InfluxDB tmp directory "/opt/iobroker/backups/influxDB_2023_09_18-13_20_45_influxDB-4_backupiobroker" successfully deleted [DEBUG] [influxDB] - InfluxDB-Backup for influxDB-4 is finish [DEBUG] [influxDB] - done [DEBUG] [zigbee] - found zigbee database: zigbee.0 [DEBUG] [zigbee] - done [DEBUG] [onedrive] - Onedrive: Copy iobroker_2023_09_18-13_20_20_Testpi_backupiobroker.tar.gz... [DEBUG] [onedrive] - 47% uploaded from iobroker_2023_09_18-13_20_20_Testpi_backupiobroker.tar.gz [DEBUG] [onedrive] - 94% uploaded from iobroker_2023_09_18-13_20_20_Testpi_backupiobroker.tar.gz [DEBUG] [onedrive] - 100% uploaded from iobroker_2023_09_18-13_20_20_Testpi_backupiobroker.tar.gz [DEBUG] [onedrive] - iobroker_2023_09_18-13_20_20_Testpi_backupiobroker.tar.gz with Id: 265B81AA2EF75ADE!1166 saved on Onedrive [DEBUG] [onedrive] - Onedrive: Copy influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz... [DEBUG] [onedrive] - 2% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 5% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 7% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 10% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 12% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 14% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 17% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 19% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 22% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 24% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 26% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 29% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 31% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 34% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 36% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 38% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 41% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 43% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 46% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 48% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 50% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 53% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 55% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 58% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 60% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 62% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 65% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 67% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 70% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 72% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 74% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 77% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 79% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 82% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 84% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 86% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 89% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 91% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 94% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 96% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 98% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - 100% uploaded from influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz [DEBUG] [onedrive] - influxDB_2023_09_18-13_20_26_influxDB-1_backupiobroker.tar.gz with Id: 265B81AA2EF75ADE!1167 saved on Onedrive [DEBUG] [onedrive] - Onedrive: Copy influxDB_2023_09_18-13_20_45_influxDB-2_backupiobroker.tar.gz... [DEBUG] [onedrive] - 100% uploaded from influxDB_2023_09_18-13_20_45_influxDB-2_backupiobroker.tar.gz [DEBUG] [onedrive] - influxDB_2023_09_18-13_20_45_influxDB-2_backupiobroker.tar.gz with Id: 265B81AA2EF75ADE!1168 saved on Onedrive [DEBUG] [onedrive] - Onedrive: Copy influxDB_2023_09_18-13_20_45_influxDB-3_backupiobroker.tar.gz... [DEBUG] [onedrive] - 100% uploaded from influxDB_2023_09_18-13_20_45_influxDB-3_backupiobroker.tar.gz [DEBUG] [onedrive] - influxDB_2023_09_18-13_20_45_influxDB-3_backupiobroker.tar.gz with Id: 265B81AA2EF75ADE!1169 saved on Onedrive [DEBUG] [onedrive] - Onedrive: Copy influxDB_2023_09_18-13_20_45_influxDB-4_backupiobroker.tar.gz... [DEBUG] [onedrive] - 100% uploaded from influxDB_2023_09_18-13_20_45_influxDB-4_backupiobroker.tar.gz [DEBUG] [onedrive] - influxDB_2023_09_18-13_20_45_influxDB-4_backupiobroker.tar.gz with Id: 265B81AA2EF75ADE!1170 saved on Onedrive [DEBUG] [onedrive] - Onedrive: Copy zigbee.0_2023_09_18-13_20_47_Testpi_backupiobroker.tar.gz... [DEBUG] [onedrive] - 100% uploaded from zigbee.0_2023_09_18-13_20_47_Testpi_backupiobroker.tar.gz [DEBUG] [onedrive] - zigbee.0_2023_09_18-13_20_47_Testpi_backupiobroker.tar.gz with Id: 265B81AA2EF75ADE!1171 saved on Onedrive [DEBUG] [onedrive] - done [DEBUG] [clean] - No older backup files are deleted, because this backup was started manually [DEBUG] [clean] - done [DEBUG] [historyHTML] - new history html values created [DEBUG] [historyHTML] - done [DEBUG] [historyJSON] - new history json values created [DEBUG] [historyJSON] - done [EXIT] 0VG
Ich habe jetzt mal den Sonos-Adapter angehalten, die gesamten Datenpunkte gelöscht und dann manuell ein Backup mit Backitup gestartet. Das lief durch. Allerdings gab es auch wieder Hieroglyphen im Output, diesmal vom Sayit-Adapter und dessen mp3-Datenpunkt. Aber der zugewiesene Arbeitsspeicher hat wohl für das backup gereicht, es wurde eines erfolgreich erstellt.
Anscheinend besteht das Problem mit allen Datenpunkten, die in der Objektliste mit "type": "file" angelegt sind und bei denen sich dann beim Draufklicken eben ein Bild (cover_png bei Sonos) oder Soundfile (mp3 bei Sayit) direkt öffnen lassen.
Bei der vorherigen stable-Version vom js-controller bin ich ziemlich sicher, dass die Datenpunke da noch nicht so waren, dass sie sich beim Draufklicken öffnen ließen, oder?Gruss, Jürgen
EDIT: @Duffy Hattest Du auch bei einem Deiner Lautsprecher mal was abgespielt, so dass der Datenpunkt cover_png auch etwas enthielt und nicht nur leer war?
-
Ich habe jetzt mal den Sonos-Adapter angehalten, die gesamten Datenpunkte gelöscht und dann manuell ein Backup mit Backitup gestartet. Das lief durch. Allerdings gab es auch wieder Hieroglyphen im Output, diesmal vom Sayit-Adapter und dessen mp3-Datenpunkt. Aber der zugewiesene Arbeitsspeicher hat wohl für das backup gereicht, es wurde eines erfolgreich erstellt.
Anscheinend besteht das Problem mit allen Datenpunkten, die in der Objektliste mit "type": "file" angelegt sind und bei denen sich dann beim Draufklicken eben ein Bild (cover_png bei Sonos) oder Soundfile (mp3 bei Sayit) direkt öffnen lassen.
Bei der vorherigen stable-Version vom js-controller bin ich ziemlich sicher, dass die Datenpunke da noch nicht so waren, dass sie sich beim Draufklicken öffnen ließen, oder?Gruss, Jürgen
EDIT: @Duffy Hattest Du auch bei einem Deiner Lautsprecher mal was abgespielt, so dass der Datenpunkt cover_png auch etwas enthielt und nicht nur leer war?
Hallo,
habe das Problem, dass ich seit update auf JS-Controler 5.x nicht mehr auf- VIS Runtime (endlosSchleifen von 10 runterzählend)
- Visualisierung (no connection)
- Flot (no connection to server)
--> WebSrerver neu isntalliert, aber
Aktuelles Fehlerprotokoll
web.0 2023-09-18 16:08:10.435 error Error: Cannot find module './controllerTools'Require stack:- /opt/iobroker/node_modules/iobroker.socketio/node_modules/@iobroker/adapter-core/build/index.js- /opt/iobroker/node_modules/iobroker.socketio/node_modules/@iobroker/socket-classes/lib/socketCommands.js- /opt/iobroker/node_modules/iobroker.socketio/node_modules/@iobroker/socket-classes/lib/socketCommon.js- /opt/iobroker/node_modules/iobroker.socketio/node_modules/@iobroker/socket-classes/lib/socketAdmin.js- /opt/iobroker/node_modules/iobroker.socketio/node_modules/@iobroker/socket-classes/index.js- /opt/iobroker/node_modules/iobroker.socketio/lib/socketIO.js- /opt/iobroker/node_modules/iobroker.socketio/lib/socket.js- /opt/iobroker/node_modules/iobroker.web/main.js at Function.Module._resolveFilename (node:internal/modules/cjs/loader:1077:15) at Function.Module._load (node:internal/modules/cjs/loader:922:27) at Module.require (node:internal/modules/cjs/loader:1143:19) at require (node:internal/modules/cjs/helpers:121:18) at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.socketio/node_modules/@iobroker/adapter-core/build/index.js:19:27) at Module._compile (node:internal/modules/cjs/loader:1256:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1310:10) at Module.load (node:internal/modules/cjs/loader:1119:32) at Function.Module._load (node:internal/modules/cjs/loader:960:12) at Module.require (node:internal/modules/cjs/loader:1143:19) web.0 2023-09-18 16:08:10.428 error ERROR: Cannot find module './controllerTools'Require stack:- /opt/iobroker/node_modules/iobroker.socketio/node_modules/@iobroker/adapter-core/build/index.js- /opt/iobroker/node_modules/iobroker.socketio/node_modules/@iobroker/socket-classes/lib/socketCommands.js- /opt/iobroker/node_modules/iobroker.socketio/node_modules/@iobroker/socket-classes/lib/socketCommon.js- /opt/iobroker/node_modules/iobroker.socketio/node_modules/@iobroker/socket-classes/lib/socketAdmin.js- /opt/iobroker/node_modules/iobroker.socketio/node_modules/@iobroker/socket-classes/index.js- /opt/iobroker/node_modules/iobroker.socketio/lib/socketIO.js- /opt/iobroker/node_modules/iobroker.socketio/lib/socket.js- /opt/iobroker/node_modules/iobroker.web/main.js web.0 2023-09-18 16:08:10.427 error Initialization of integrated socket.io failed. Please reinstall the web adapter.iob diag summary
======================= SUMMARY ======================= v.2023-06-20 Static hostname: raspberrypi4-iob Icon name: computer Machine ID: 7520f6fd74454b99bf8a0c3666ca6ae6 Boot ID: 17ed88c2e25541859b6bb26e1bc933f3 Operating System: Raspbian GNU/Linux 10 (buster) Kernel: Linux 5.10.103-v7l+ Architecture: arm Installation: native Kernel: armv7l Userland: armhf Timezone: Europe/Berlin (CEST, +0200) User-ID: 1000 X-Server: false Boot Target: graphical.target Pending OS-Updates: 0 Pending iob updates: 1 Nodejs-Installation: /usr/bin/nodejs v18.17.1 /usr/bin/node v18.17.1 /usr/bin/npm 9.6.7 /usr/bin/npx 9.6.7 Recommended versions are nodejs 18.x.y and npm 9.x.y Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 3.8G 1.4G 1.8G 8.0M 633M 2.3G Swap: 99M 0B 99M Total: 3.9G 1.4G 1.9G Active iob-Instances: 31 Active repo(s): Stable (default) ioBroker Core: js-controller 5.0.12 admin 6.8.0 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: + system.adapter.admin.0 : admin : raspberrypi4-iob - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : raspberrypi4-iob - enabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 15062 States: 13143 Size of iob-Database: 23M /opt/iobroker/iobroker-data/objects.jsonl 11M /opt/iobroker/iobroker-data/objects.json.migrated 11M /opt/iobroker/iobroker-data/objects.json.bak.migrated 12M /opt/iobroker/iobroker-data/states.jsonl 2.5M /opt/iobroker/iobroker-data/states.json.migrated 2.5M /opt/iobroker/iobroker-data/states.json.bak.migrated =================== END OF SUMMARY ==================== -
Hallo,
habe das Problem, dass ich seit update auf JS-Controler 5.x nicht mehr auf- VIS Runtime (endlosSchleifen von 10 runterzählend)
- Visualisierung (no connection)
- Flot (no connection to server)
--> WebSrerver neu isntalliert, aber
Aktuelles Fehlerprotokoll
web.0 2023-09-18 16:08:10.435 error Error: Cannot find module './controllerTools'Require stack:- /opt/iobroker/node_modules/iobroker.socketio/node_modules/@iobroker/adapter-core/build/index.js- /opt/iobroker/node_modules/iobroker.socketio/node_modules/@iobroker/socket-classes/lib/socketCommands.js- /opt/iobroker/node_modules/iobroker.socketio/node_modules/@iobroker/socket-classes/lib/socketCommon.js- /opt/iobroker/node_modules/iobroker.socketio/node_modules/@iobroker/socket-classes/lib/socketAdmin.js- /opt/iobroker/node_modules/iobroker.socketio/node_modules/@iobroker/socket-classes/index.js- /opt/iobroker/node_modules/iobroker.socketio/lib/socketIO.js- /opt/iobroker/node_modules/iobroker.socketio/lib/socket.js- /opt/iobroker/node_modules/iobroker.web/main.js at Function.Module._resolveFilename (node:internal/modules/cjs/loader:1077:15) at Function.Module._load (node:internal/modules/cjs/loader:922:27) at Module.require (node:internal/modules/cjs/loader:1143:19) at require (node:internal/modules/cjs/helpers:121:18) at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.socketio/node_modules/@iobroker/adapter-core/build/index.js:19:27) at Module._compile (node:internal/modules/cjs/loader:1256:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1310:10) at Module.load (node:internal/modules/cjs/loader:1119:32) at Function.Module._load (node:internal/modules/cjs/loader:960:12) at Module.require (node:internal/modules/cjs/loader:1143:19) web.0 2023-09-18 16:08:10.428 error ERROR: Cannot find module './controllerTools'Require stack:- /opt/iobroker/node_modules/iobroker.socketio/node_modules/@iobroker/adapter-core/build/index.js- /opt/iobroker/node_modules/iobroker.socketio/node_modules/@iobroker/socket-classes/lib/socketCommands.js- /opt/iobroker/node_modules/iobroker.socketio/node_modules/@iobroker/socket-classes/lib/socketCommon.js- /opt/iobroker/node_modules/iobroker.socketio/node_modules/@iobroker/socket-classes/lib/socketAdmin.js- /opt/iobroker/node_modules/iobroker.socketio/node_modules/@iobroker/socket-classes/index.js- /opt/iobroker/node_modules/iobroker.socketio/lib/socketIO.js- /opt/iobroker/node_modules/iobroker.socketio/lib/socket.js- /opt/iobroker/node_modules/iobroker.web/main.js web.0 2023-09-18 16:08:10.427 error Initialization of integrated socket.io failed. Please reinstall the web adapter.iob diag summary
======================= SUMMARY ======================= v.2023-06-20 Static hostname: raspberrypi4-iob Icon name: computer Machine ID: 7520f6fd74454b99bf8a0c3666ca6ae6 Boot ID: 17ed88c2e25541859b6bb26e1bc933f3 Operating System: Raspbian GNU/Linux 10 (buster) Kernel: Linux 5.10.103-v7l+ Architecture: arm Installation: native Kernel: armv7l Userland: armhf Timezone: Europe/Berlin (CEST, +0200) User-ID: 1000 X-Server: false Boot Target: graphical.target Pending OS-Updates: 0 Pending iob updates: 1 Nodejs-Installation: /usr/bin/nodejs v18.17.1 /usr/bin/node v18.17.1 /usr/bin/npm 9.6.7 /usr/bin/npx 9.6.7 Recommended versions are nodejs 18.x.y and npm 9.x.y Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 3.8G 1.4G 1.8G 8.0M 633M 2.3G Swap: 99M 0B 99M Total: 3.9G 1.4G 1.9G Active iob-Instances: 31 Active repo(s): Stable (default) ioBroker Core: js-controller 5.0.12 admin 6.8.0 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: + system.adapter.admin.0 : admin : raspberrypi4-iob - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : raspberrypi4-iob - enabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 15062 States: 13143 Size of iob-Database: 23M /opt/iobroker/iobroker-data/objects.jsonl 11M /opt/iobroker/iobroker-data/objects.json.migrated 11M /opt/iobroker/iobroker-data/objects.json.bak.migrated 12M /opt/iobroker/iobroker-data/states.jsonl 2.5M /opt/iobroker/iobroker-data/states.json.migrated 2.5M /opt/iobroker/iobroker-data/states.json.bak.migrated =================== END OF SUMMARY ==================== -
Seit dem Upgrade auf js 5.0.x funktioniert bei mir der Fritzbox-Adapter nicht mehr, bleibt beharrlich auf "rot", das heißt, es gibt keine Verbindung mit dem Host und kein Lebenszeichen. Adapter wurde gelöscht und neu installiert, keine Änderung. Die Fehlermöglichkeit für falsche Settings sind bei diesem Adapter ja ausschließlich auf die IP-Adresse der Fritzbox beschränkt. Einstellungen der FB (7490) mehrfach kontrolliert, auch hier neueste Version der FRITZ!OS 7.57 vom 08.09.23. Alle Adapter im System auf dem neuesten Stand, IOB ebenso aktuell. Hat jemand eine Idee zur Problemlösung?
Darüber hinaus habe ich das Empfinden, dass das System (Intel NUC) jetzt mit einer CPU-Last von durchschnittlich 60 Prozent deutlich höher ausgelastet ist als vorher.
======================= SUMMARY ======================= v.2023-06-20 Static hostname: me-nuc Icon name: computer-desktop Chassis: desktop Machine ID: b9adafe7623d4472b96adc8d03b11f08 Boot ID: 89d1e20e22294a089055806c3f94db54 Operating System: Ubuntu 22.04.3 LTS Kernel: Linux 6.2.0-32-generic Architecture: x86-64 Installation: native Kernel: x86_64 Userland: amd64 Timezone: Europe/Berlin (CEST, +0200) User-ID: 1000 X-Server: true Boot Target: graphical.target Pending OS-Updates: 0 Pending iob updates: 1 Nodejs-Installation: /usr/bin/nodejs v18.17.1 /usr/bin/node v18.17.1 /usr/bin/npm 9.6.7 /usr/bin/npx 9.6.7 Recommended versions are nodejs 18.x.y and npm 9.x.y Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 7.7G 3.4G 1.1G 19M 3.2G 4.0G Swap: 2.0G 1.0M 2.0G Total: 9.8G 3.4G 3.2G Active iob-Instances: 31 Active repo(s): stable ioBroker Core: js-controller 5.0.12 admin 6.8.0 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: + system.adapter.admin.0 : admin : me-nuc - enabled, compact disabled, port: 8081, bind: 192.168.160.121, run as: admin + system.adapter.web.0 : web : me-nuc - enabled, compact disabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 18076 States: 15181 Size of iob-Database: 22M /opt/iobroker/iobroker-data/objects.jsonl 6.3M /opt/iobroker/iobroker-data/objects.json.migrated 6.3M /opt/iobroker/iobroker-data/objects.json.bak.migrated 6.3M /opt/iobroker/iobroker-data/states.jsonl 1.7M /opt/iobroker/iobroker-data/states.json.migrated 1.7M /opt/iobroker/iobroker-data/states.json.bak.migrated =================== END OF SUMMARY ====================Danke vorab von
Michael -
Seit dem Upgrade auf js 5.0.x funktioniert bei mir der Fritzbox-Adapter nicht mehr, bleibt beharrlich auf "rot", das heißt, es gibt keine Verbindung mit dem Host und kein Lebenszeichen. Adapter wurde gelöscht und neu installiert, keine Änderung. Die Fehlermöglichkeit für falsche Settings sind bei diesem Adapter ja ausschließlich auf die IP-Adresse der Fritzbox beschränkt. Einstellungen der FB (7490) mehrfach kontrolliert, auch hier neueste Version der FRITZ!OS 7.57 vom 08.09.23. Alle Adapter im System auf dem neuesten Stand, IOB ebenso aktuell. Hat jemand eine Idee zur Problemlösung?
Darüber hinaus habe ich das Empfinden, dass das System (Intel NUC) jetzt mit einer CPU-Last von durchschnittlich 60 Prozent deutlich höher ausgelastet ist als vorher.
======================= SUMMARY ======================= v.2023-06-20 Static hostname: me-nuc Icon name: computer-desktop Chassis: desktop Machine ID: b9adafe7623d4472b96adc8d03b11f08 Boot ID: 89d1e20e22294a089055806c3f94db54 Operating System: Ubuntu 22.04.3 LTS Kernel: Linux 6.2.0-32-generic Architecture: x86-64 Installation: native Kernel: x86_64 Userland: amd64 Timezone: Europe/Berlin (CEST, +0200) User-ID: 1000 X-Server: true Boot Target: graphical.target Pending OS-Updates: 0 Pending iob updates: 1 Nodejs-Installation: /usr/bin/nodejs v18.17.1 /usr/bin/node v18.17.1 /usr/bin/npm 9.6.7 /usr/bin/npx 9.6.7 Recommended versions are nodejs 18.x.y and npm 9.x.y Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 7.7G 3.4G 1.1G 19M 3.2G 4.0G Swap: 2.0G 1.0M 2.0G Total: 9.8G 3.4G 3.2G Active iob-Instances: 31 Active repo(s): stable ioBroker Core: js-controller 5.0.12 admin 6.8.0 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: + system.adapter.admin.0 : admin : me-nuc - enabled, compact disabled, port: 8081, bind: 192.168.160.121, run as: admin + system.adapter.web.0 : web : me-nuc - enabled, compact disabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 18076 States: 15181 Size of iob-Database: 22M /opt/iobroker/iobroker-data/objects.jsonl 6.3M /opt/iobroker/iobroker-data/objects.json.migrated 6.3M /opt/iobroker/iobroker-data/objects.json.bak.migrated 6.3M /opt/iobroker/iobroker-data/states.jsonl 1.7M /opt/iobroker/iobroker-data/states.json.migrated 1.7M /opt/iobroker/iobroker-data/states.json.bak.migrated =================== END OF SUMMARY ====================Danke vorab von
Michael@garbleflux sagte in js-controller 5.0.x jetzt für alle User im STABLE!:
Darüber hinaus habe ich das Empfinden, dass das System (Intel NUC) jetzt mit einer CPU-Last von durchschnittlich 60 Prozent deutlich höher ausgelastet ist als vorher.
Dann schmeiß den laufenden Desktop schon mal raus.
Seit dem Upgrade auf js 5.0.x funktioniert bei mir der Fritzbox-Adapter nicht mehr, bleibt beharrlich auf "rot",
Und was steht im LogFile zu dem Adapter? Bei einem kompletten Neustart des Adapters?
-
- Die hier von mir beschriebenen Probleme bestehen seit update auf JS-controller 5.0
- Die im anderen Thread behandelten Themen (u.a. Aktualität System) haben nix mit update js-controler zu tun, da aktuelles - Problem 100% identisch wie vor den Systemaktualisierungen im anderen Thread...
-
@garbleflux sagte in js-controller 5.0.x jetzt für alle User im STABLE!:
Darüber hinaus habe ich das Empfinden, dass das System (Intel NUC) jetzt mit einer CPU-Last von durchschnittlich 60 Prozent deutlich höher ausgelastet ist als vorher.
Dann schmeiß den laufenden Desktop schon mal raus.
Seit dem Upgrade auf js 5.0.x funktioniert bei mir der Fritzbox-Adapter nicht mehr, bleibt beharrlich auf "rot",
Und was steht im LogFile zu dem Adapter? Bei einem kompletten Neustart des Adapters?
@thomas-braun
Verehrter Herr Braun! Hier das LogFile zum Adapter:host.me-nuc 2023-09-18 17:07:26.866 error instance system.adapter.fritzbox.0 terminated with code 1 (JS_CONTROLLER_STOPPED) host.me-nuc 2023-09-18 17:07:26.865 error Caught by controller[0]: Node.js v18.17.1 host.me-nuc 2023-09-18 17:07:26.865 error Caught by controller[0]: } host.me-nuc 2023-09-18 17:07:26.865 error Caught by controller[0]: ] host.me-nuc 2023-09-18 17:07:26.865 error Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.fritzbox/main.js' host.me-nuc 2023-09-18 17:07:26.865 error Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.fritzbox/lib/utils.js', host.me-nuc 2023-09-18 17:07:26.865 error Caught by controller[0]: requireStack: [ host.me-nuc 2023-09-18 17:07:26.865 error Caught by controller[0]: code: 'MODULE_NOT_FOUND', host.me-nuc 2023-09-18 17:07:26.864 error Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1143:19) { host.me-nuc 2023-09-18 17:07:26.864 error Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:960:12) host.me-nuc 2023-09-18 17:07:26.864 error Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1119:32) host.me-nuc 2023-09-18 17:07:26.864 error Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1310:10) host.me-nuc 2023-09-18 17:07:26.864 error Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1256:14) host.me-nuc 2023-09-18 17:07:26.864 error Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.fritzbox/lib/utils.js:46:25) host.me-nuc 2023-09-18 17:07:26.864 error Caught by controller[0]: at require (node:internal/modules/cjs/helpers:121:18) host.me-nuc 2023-09-18 17:07:26.864 error Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1143:19) host.me-nuc 2023-09-18 17:07:26.864 error Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:922:27) host.me-nuc 2023-09-18 17:07:26.864 error Caught by controller[0]: at Module._resolveFilename (node:internal/modules/cjs/loader:1077:15) host.me-nuc 2023-09-18 17:07:26.863 error Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.fritzbox/main.js host.me-nuc 2023-09-18 17:07:26.863 error Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.fritzbox/lib/utils.js host.me-nuc 2023-09-18 17:07:26.863 error Caught by controller[0]: Require stack: host.me-nuc 2023-09-18 17:07:26.863 error Caught by controller[0]: Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js' host.me-nuc 2023-09-18 17:07:26.863 error Caught by controller[0]: ^ host.me-nuc 2023-09-18 17:07:26.863 error Caught by controller[0]: throw err; host.me-nuc 2023-09-18 17:07:26.862 error Caught by controller[0]: node:internal/modules/cjs/loader:1080 host.me-nuc 2023-09-18 17:07:26.660 info instance system.adapter.fritzbox.0 started with pid 45918Vorab danke für die Hilfestellung.
VG Michael -
- Die hier von mir beschriebenen Probleme bestehen seit update auf JS-controller 5.0
- Die im anderen Thread behandelten Themen (u.a. Aktualität System) haben nix mit update js-controler zu tun, da aktuelles - Problem 100% identisch wie vor den Systemaktualisierungen im anderen Thread...
Problem bzgl Web-Server gelöst.... kann es aber nicht nachvollziehen warum es jetzt funktioniert...
Web-Server neu installiert - gleiches Fehlerbild auch nach reboot... no connection etc.
Dann den Port von 8082 auf einfach mal 8081 geändert. WebServer verliert Verbindung und keine Connection
Wieder zurück auf 8082 und funktioniert alles...
705
Online32.4k
Benutzer81.4k
Themen1.3m
Beiträge