Bitte in der nachfolgenden Übersicht die mit ... bzw x gekennzeichneten Felder ausfüllen und im Anschluss an die Tabelle auf Linux Systemen den Output des Commands iob diag einfügen.

Hinweis: Das Eröffnen eines Issues hier ersetzt NICHT das Anlegen eine Issues im Repository des Adapters. Fehlerbehebungen werden ausschließlich über Issues getrackt.

DANKE

Bitte ausfüllen:

• Adaptername:
• Link zu Adapterrepository: www.github.com...
• Adapterversion: ...
• js-controller Version: 7.0.0
• Admin Version: 7.2.6
• Hardwaresystem: LXC unter Proxmox auf NUC
• Arbeitsspeicher: 8GB
• Festplattenart: SSD
• Betriebssystem: Debian 12
• Nodejs-Version: 20.18.0
• NPM-Version: 10.8.2
• Installationsart: Skript
• Image, Docker genutzt: Nein
• Ort, Name der Imagedatei: ...

Linux User bitte hier den Output von iob diag einfügen.

======================= SUMMARY =======================
                        v.2024-08-12


 Static hostname: iobroker
       Icon name: computer-container
         Chassis: container ☐
  Virtualization: lxc
Operating System: Debian GNU/Linux 12 (bookworm)
          Kernel: Linux 6.8.12-2-pve
    Architecture: x86-64

Installation:           lxc
Kernel:                 x86_64
Userland:               64 bit
Timezone:               Europe/Berlin (CEST, +0200)
User-ID:                0
Display-Server:         false
Boot Target:            graphical.target

Pending OS-Updates:     0
Pending iob updates:    0

Nodejs-Installation:
/usr/bin/nodejs         v20.18.0
/usr/bin/node           v20.18.0
/usr/bin/npm            10.8.2
/usr/bin/npx            10.8.2
/usr/bin/corepack       0.29.3

Recommended versions are nodejs 20.18.0 and npm 10.8.2
Your nodejs installation is correct

MEMORY: 
               total        used        free      shared  buff/cache   available
Mem:            8.6G        1.6G        5.6G         86K        1.5G        7.0G
Swap:           8.6G        1.1M        8.6G
Total:           17G        1.6G         14G

Active iob-Instances:   22
Upgrade policy: none

ioBroker Core:          js-controller           7.0.0
                        admin                   7.2.6

ioBroker Status:        iobroker is running on this host.


Objects type: jsonl
States  type: jsonl

Status admin and web instance:
+ system.adapter.admin.0                  : admin                 : iobroker                                 -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
+ system.adapter.web.0                    : web                   : iobroker                                 -  enabled, port: 8082, bind: 0.0.0.0, run as: admin

Objects:                15063
States:                 12530

Size of iob-Database:

26M     /opt/iobroker/iobroker-data/objects.jsonl
4.5M    /opt/iobroker/iobroker-data/states.jsonl



=================== END OF SUMMARY ====================

Bei der Migration zu redis erhalte ich folgende Meldung und die Umstellung erfolgt nicht.

Connecting to previous DB "jsonl/jsonl"...
Creating backup ...
This can take some time ... please be patient!
host.iobroker 15067 objects saved
host.iobroker 12330 states saved
host.iobroker Validating backup ...
host.iobroker Backup not created: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.js-controller/tmp/backup/config.json'
Uncaught Rejection: IoBrokerError: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.js-controller/tmp/backup/config.json'
    at BackupRestore.createBackup (file:///opt/iobroker/node_modules/@iobroker/js-controller-cli/src/lib/setup/setupBackup.ts:382:19)
    at file:///opt/iobroker/node_modules/@iobroker/js-controller-cli/src/lib/setup/setupSetup.ts:597:36
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
IoBrokerError: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.js-controller/tmp/backup/config.json'
    at BackupRestore.createBackup (file:///opt/iobroker/node_modules/@iobroker/js-controller-cli/src/lib/setup/setupBackup.ts:382:19)
    at file:///opt/iobroker/node_modules/@iobroker/js-controller-cli/src/lib/setup/setupSetup.ts:597:36

Ein manuelles Backup mit iobroker backup läuft ohne Fehler durch.

@foxriver76
Auch hier Testsystem aktualisiert. Keine Probleme beim Start. Alle Adapter laufen ohne Fehler. Super.

@foxriver76 erledigt
issue 2945

@dlehmann

Hier noch eine Rückmeldung zu meinem Thema mit der Umstellung auf redis.

Ich hatte jetzt Zeit, das Update auf 7.0.2 zu machen. Danach lief die Umstellung auf redis erfolgreich durch und iobroker läuft jetzt mit redis Datenbank.

@dlehmann

Hier noch eine Rückmeldung zu meinem Thema mit der Umstellung auf redis.

Ich hatte jetzt Zeit, das Update auf 7.0.2 zu machen. Danach lief die Umstellung auf redis erfolgreich durch und iobroker läuft jetzt mit redis Datenbank.

@foxriver76

Leider noch nicht. Der Fehler sieht jetzt aber anders aus. Eine Umstellung erfolgt aber nicht. iobroker ist gestoppt und der neue iob fix lief auch erfolgreich drüber.

dirk@iobroker:~$ iob setup custom
Current configuration:
- Objects database:
  - Type: jsonl
  - Host/Unix Socket: 127.0.0.1
  - Port: 9001
- States database:
  - Type: jsonl
  - Host/Unix Socket: 127.0.0.1
  - Port: 9000
- Data Directory: ../../iobroker-data/

Type of objects DB [(j)sonl, (f)ile, (r)edis, ...], default [jsonl]: r

When Objects and Files are stored in a Redis database please consider the following:
1. All data will be stored in RAM, make sure to have enough free RAM available!
2. Make sure to check Redis persistence options to make sure a Redis problem will not cause data loss!
3. The Redis persistence files can get big, make sure not to use an SD card to store them.

Host / Unix Socket of objects DB(redis), default[127.0.0.1]: 
Port of objects DB(redis), default[6379]: 
Do you use a TLS connection for your "objects" redis-server? [y/N]:
Type of states DB [(j)sonl, (f)file, (r)edis, ...], default [redis]: 
Host / Unix Socket of states DB (redis), default[127.0.0.1]: 
Port of states DB (redis), default[6379]: 
Do you use a TLS connection for your "states" redis-server? [y/N]:
Host name of this machine [iobroker]: 
Please choose if this is a Master/single host (enter "m") or a Slave host (enter "S") you are about to edit. For Slave hosts the data migration will be skipped. [S/m]: m

Important: Using redis for the Objects database is only supported
with js-controller 2.0 or higher!
When your system consists of multiple hosts please make sure to have
js-controller 2.0 or higher installed on ALL hosts *before* continuing!


Important #2: If you already did the migration on an other host
please *do not* migrate again! This can destroy your system!


Important #3: The process will migrate all files that were officially
uploaded into the ioBroker system. If you have manually copied files into
iobroker-data/files/... into own directories then these files will NOT be
migrated! Make sure all files are in adapter directories inside the files
directory!


Do you want to migrate objects and states from "jsonl/jsonl" to "redis/redis" [y/N]: y

Migrating the objects database will overwrite all objects! Are you sure that this is not a slave host and you want to migrate the data? [y/N]: y

Connecting to previous DB "jsonl/jsonl"...
Creating backup ...
This can take some time ... please be patient!
host.iobroker 15138 objects saved
host.iobroker 12349 states saved
host.iobroker Validating backup ...
host.iobroker The backup is valid!
Backup created: /opt/iobroker/backups/2024_10_22-17_58_59_backupiobroker-migration.tar.gz
updating conf/iobroker.json

Connecting to new DB "redis/redis" (can take up to 20s) ...
 Cannot read system.config: null (OK when migrating or restoring)
Restore backup ...
This can take some time ... please be patient!
host.iobroker Cannot find extracted file "/opt/iobroker/node_modules/iobroker.js-controller/tmp/backup/backup.json" or "/opt/iobroker/node_modules/iobroker.js-controller/tmp/backup/config.json"
Error happened during restore. Exit-Code: 26

restoring conf/iobroker.json

Moin,

oben steht ja in der Beschreibung, dass der Fixer, wenn mit root läuft, anbietet, einen neuen User anzulegen. Mein iobroker läuft in einem LXC und kennt nur root. polkitd war auch nicht installiert. Das habe ich nachgeholt.
Nun bekomme ich folgende Meldung. Ist das aktuell so gewollt? Dann lege ich den User manuell an.

root@iobroker:/# iob fix

***For security reasons ioBroker should not be run or administrated as root.***
By default only a user that is member of iobroker group can execute ioBroker commands.
Please read the Documentation on how to set up such a user, if not done yet.
Only in very special cases you can run iobroker commands by adding the --allow-root option at the end of the command line.
Please note that this option may be disabled in the future, so please change your setup accordingly now.

Okay, mit --allow-root läuft es und ich konnte die Fragen beantworten.
Danke

@foxriver76 erledigt
issue 2945

@homoran getan

Ich wollte heute die Datenbank von iobroker von jsonl auf redis umstellen. Das hat leider nicht geklappt. Forenbeitrag hierzu ist hier zu finden.

Fehler bei der Magration von jsonl zu redis (https://forum.iobroker.net/topic/77556/fehler-bei-der-migration-von-jsonl-zu-redis)

@ro75 ist aktuell im Beta

@ro75 jawohl

@ro75

Current configuration:
- Objects database:
  - Type: jsonl
  - Host/Unix Socket: 127.0.0.1
  - Port: 9001
- States database:
  - Type: jsonl
  - Host/Unix Socket: 127.0.0.1
  - Port: 9000
- Data Directory: ../../iobroker-data/

Type of objects DB [(j)sonl, (f)ile, (r)edis, ...], default [jsonl]: r

When Objects and Files are stored in a Redis database please consider the following:
1. All data will be stored in RAM, make sure to have enough free RAM available!
2. Make sure to check Redis persistence options to make sure a Redis problem will not cause data loss!
3. The Redis persistence files can get big, make sure not to use an SD card to store them.

Host / Unix Socket of objects DB(redis), default[127.0.0.1]: 
Port of objects DB(redis), default[6379]: 
Do you use a TLS connection for your "objects" redis-server? [y/N]:
Type of states DB [(j)sonl, (f)file, (r)edis, ...], default [redis]: 
Host / Unix Socket of states DB (redis), default[127.0.0.1]: 
Port of states DB (redis), default[6379]: 
Do you use a TLS connection for your "states" redis-server? [y/N]:
Host name of this machine [iobroker]: 
Please choose if this is a Master/single host (enter "m") or a Slave host (enter "S") you are about to edit. For Slave hosts the data migration will be skipped. [S/m]: m

Important: Using redis for the Objects database is only supported
with js-controller 2.0 or higher!
When your system consists of multiple hosts please make sure to have
js-controller 2.0 or higher installed on ALL hosts *before* continuing!


Important #2: If you already did the migration on an other host
please *do not* migrate again! This can destroy your system!


Important #3: The process will migrate all files that were officially
uploaded into the ioBroker system. If you have manually copied files into
iobroker-data/files/... into own directories then these files will NOT be
migrated! Make sure all files are in adapter directories inside the files
directory!


Do you want to migrate objects and states from "jsonl/jsonl" to "redis/redis" [y/N]: y

Migrating the objects database will overwrite all objects! Are you sure that this is not a slave host and you want to migrate the data? [y/N]: y

Connecting to previous DB "jsonl/jsonl"...
Creating backup ...
This can take some time ... please be patient!
host.iobroker 15067 objects saved
host.iobroker 12330 states saved
host.iobroker Validating backup ...
host.iobroker Backup not created: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.js-controller/tmp/backup/config.json'
Uncaught Rejection: IoBrokerError: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.js-controller/tmp/backup/config.json'
    at BackupRestore.createBackup (file:///opt/iobroker/node_modules/@iobroker/js-controller-cli/src/lib/setup/setupBackup.ts:382:19)
    at file:///opt/iobroker/node_modules/@iobroker/js-controller-cli/src/lib/setup/setupSetup.ts:597:36
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
IoBrokerError: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.js-controller/tmp/backup/config.json'
    at BackupRestore.createBackup (file:///opt/iobroker/node_modules/@iobroker/js-controller-cli/src/lib/setup/setupBackup.ts:382:19)
    at file:///opt/iobroker/node_modules/@iobroker/js-controller-cli/src/lib/setup/setupSetup.ts:597:36

redis ist im gleich lxc installiert wie iobroker, Standardkonfiguration ohne Änderungen und läuft auch, ist mit redis-cli erreichbar.

Gestartet habe ich die Migration mit "iobroker setup custom", dort habe ich die notwendige Angaben gemacht (hauptsächlich mit Enter bestätigt, da keine Änderungen notwendig waren)

Oben genannte Meldung war dann der Abschluss von "iobroker setuo custom".

Wie ich die Fehlermeldung verstehe, kommen wir gar nicht bis redis sondern brechen bereits vorher ab.