NEWS
ioBroker startet nicht mehr
ioBroker Allgemein
123
Beiträge
11
Kommentatoren
16.1k
Aufrufe
12
Watching
-
In der Tat.
Die "alten" 11GB Dateien vom 08.04. sind Überbleibsel eines schon geführten Kampes.
e6iob@NUCioBroker:/opt/iobroker/iobroker-data$ ls -lh insgesamt 91G drwxrwxr-x+ 2 iobroker iobroker 4,0K 15. Apr 08:45 backitup drwxrwxrwx+ 2 iobroker iobroker 12K 23. Apr 16:54 backup-objects drwxrwxrwx+ 55 iobroker iobroker 4,0K 14. Apr 21:46 files drwxrwxr-x+ 4 iobroker iobroker 4,0K 23. Jan 12:58 ham_0 drwxrwxr-x+ 34 iobroker iobroker 4,0K 23. Feb 01:11 history -rwxrwxrwx+ 1 iobroker iobroker 5,1K 15. Apr 20:46 iobroker.json -rwxrwxr-x+ 1 e6iob e6iob 5,2K 15. Apr 20:45 iobroker.json_save drwxrwxr-x+ 4 iobroker iobroker 4,0K 15. Apr 08:56 node-red -rwxrwxrwx+ 1 iobroker iobroker 3 23. Apr 17:58 notifications.json -rw-rwxr--+ 1 iobroker iobroker 0 14. Feb 11:45 objects.json2022-02-12_11-46_objects.json.gz -rw-rwxr--+ 1 iobroker iobroker 20M 20. Mär 12:18 objects.json.bak.migrated_save -rw-rw-r--+ 1 iobroker iobroker 25M 23. Apr 17:59 objects.jsonl drwxrwxr-x+ 2 iobroker iobroker 4,0K 23. Apr 18:13 objects.jsonl.lock -rw-rwxr--+ 1 iobroker iobroker 20M 20. Mär 12:19 objects.json.migrated_save -rw-rwxr--+ 1 iobroker iobroker 4,2M 20. Mär 12:19 states.json.bak.migrated_save -rw-rwxr--+ 1 iobroker iobroker 0 14. Feb 11:21 states.json.broken -rw-rw-r--+ 1 iobroker iobroker 60G 23. Apr 17:58 states.jsonl drwxrwxr-x+ 2 iobroker iobroker 4,0K 23. Apr 18:13 states.jsonl.lock drwxrwxr-x+ 2 iobroker iobroker 4,0K 23. Apr 18:10 states.jsonl.lock.save -rw-rwxr--+ 1 iobroker iobroker 11G 8. Apr 16:49 states.jsonl_save -rw-rwxr--+ 1 iobroker iobroker 4,2M 20. Mär 12:19 states.json.migrated_save -rw-rwxr--+ 1 iobroker iobroker 2,8M 14. Feb 11:42 states.json.old -rw-rwxr--+ 1 iobroker iobroker 22G 15. Apr 07:53 states.save drwxrwxr-x+ 3 iobroker iobroker 4,0K 23. Jan 16:17 tmp drwxrwxr-x+ 2 iobroker iobroker 4,0K 23. Apr 17:58 zigbee_0 e6iob@NUCioBroker:/opt/iobroker/iobroker-data$ -
In der Tat.
Die "alten" 11GB Dateien vom 08.04. sind Überbleibsel eines schon geführten Kampes.
e6iob@NUCioBroker:/opt/iobroker/iobroker-data$ ls -lh insgesamt 91G drwxrwxr-x+ 2 iobroker iobroker 4,0K 15. Apr 08:45 backitup drwxrwxrwx+ 2 iobroker iobroker 12K 23. Apr 16:54 backup-objects drwxrwxrwx+ 55 iobroker iobroker 4,0K 14. Apr 21:46 files drwxrwxr-x+ 4 iobroker iobroker 4,0K 23. Jan 12:58 ham_0 drwxrwxr-x+ 34 iobroker iobroker 4,0K 23. Feb 01:11 history -rwxrwxrwx+ 1 iobroker iobroker 5,1K 15. Apr 20:46 iobroker.json -rwxrwxr-x+ 1 e6iob e6iob 5,2K 15. Apr 20:45 iobroker.json_save drwxrwxr-x+ 4 iobroker iobroker 4,0K 15. Apr 08:56 node-red -rwxrwxrwx+ 1 iobroker iobroker 3 23. Apr 17:58 notifications.json -rw-rwxr--+ 1 iobroker iobroker 0 14. Feb 11:45 objects.json2022-02-12_11-46_objects.json.gz -rw-rwxr--+ 1 iobroker iobroker 20M 20. Mär 12:18 objects.json.bak.migrated_save -rw-rw-r--+ 1 iobroker iobroker 25M 23. Apr 17:59 objects.jsonl drwxrwxr-x+ 2 iobroker iobroker 4,0K 23. Apr 18:13 objects.jsonl.lock -rw-rwxr--+ 1 iobroker iobroker 20M 20. Mär 12:19 objects.json.migrated_save -rw-rwxr--+ 1 iobroker iobroker 4,2M 20. Mär 12:19 states.json.bak.migrated_save -rw-rwxr--+ 1 iobroker iobroker 0 14. Feb 11:21 states.json.broken -rw-rw-r--+ 1 iobroker iobroker 60G 23. Apr 17:58 states.jsonl drwxrwxr-x+ 2 iobroker iobroker 4,0K 23. Apr 18:13 states.jsonl.lock drwxrwxr-x+ 2 iobroker iobroker 4,0K 23. Apr 18:10 states.jsonl.lock.save -rw-rwxr--+ 1 iobroker iobroker 11G 8. Apr 16:49 states.jsonl_save -rw-rwxr--+ 1 iobroker iobroker 4,2M 20. Mär 12:19 states.json.migrated_save -rw-rwxr--+ 1 iobroker iobroker 2,8M 14. Feb 11:42 states.json.old -rw-rwxr--+ 1 iobroker iobroker 22G 15. Apr 07:53 states.save drwxrwxr-x+ 3 iobroker iobroker 4,0K 23. Jan 16:17 tmp drwxrwxr-x+ 2 iobroker iobroker 4,0K 23. Apr 17:58 zigbee_0 e6iob@NUCioBroker:/opt/iobroker/iobroker-data$ -
-
-
@fraso evtl. hat sich die alte iobroker.json auch wieder durch das Restore eingeschlichen?
hier die aktuelle iobroker.json
ich habe die 60G Datei gelöscht und iobroker neu gestartet und jetzt aus dem Backup heute nacht wieder hergestellt. läuft gleich, dann sende ich die anderen Infos.
{ "system": { "memoryLimitMB": 0, "hostname": "", "statisticsInterval": 15000, "statisticsIntervalComment": "Interval how often the counters for input/output in adapters and controller will be updated", "checkDiskInterval": 300000, "checkDiskIntervalComment": "Interval how often the disk size will be checked", "instanceStartInterval": 2000, "noChmodComment": "Flag to test new feature with no chmod call. Must be deleted later and noChmod must be mainline (2018.06.04)", "compact": false, "compactComment": "Controller will try to start the instances as a part of the same process. No spawn will be done. Only by adapters that support it and have flag compact flag in io-package.json", "allowShellCommands": false, "allowShellCommandsComment": "Allow execution of \"shell\" sendToHost commands", "memLimitWarn": 100, "memLimitWarnComment": "If the available RAM is below this threshold on adapter start, a warning will be logged.", "memLimitError": 50, "memLimitErrorComment": "If the available RAM is below this threshold on adapter start, an error will be logged." }, "multihostService": { "enabled": false, "secure": true, "password": "" }, "objects": { "type": "jsonl", "typeComment": "Possible values: 'file' - [port 9001], redis - [port 6379], couch - [port 5984].", "host": "127.0.0.1", "port": 9001, "noFileCache": false, "maxQueue": 1000, "connectTimeout": 2000, "writeFileInterval": 5000, "dataDir": "", "options": { "auth_pass": null, "retry_max_delay": 5000, "retry_max_count": 19, "db": 0, "family": 0 }, "backup": { "disabled": false, "files": 24, "filesComment": "Minimal number of backup files, after the deletion will be executed according to backupTime settings", "hours": 48, "hoursComment": "All backups older than 48 hours will be deleted. But only if the number of files is greater than of backupNumber", "period": 120, "periodComment": "by default backup every 2 hours. Time is in minutes. To disable backup set the value to 0", "path": "", "pathComment": "Absolute path to backup directory or empty to backup in data directory" } }, "states": { "type": "jsonl", "typeComment": "Possible values: 'file' - [port 9000], 'redis' - [port 6379].", "host": "127.0.0.1", "port": 9000, "connectTimeout": 2000, "writeFileInterval": 30000, "dataDir": "", "options": { "auth_pass": null, "retry_max_delay": 5000, "retry_max_count": 19, "db": 0, "family": 0 }, "backup": { "disabled": false, "files": 24, "filesComment": "Minimal number of backup files, after the deletion will be executed according to backupTime settings", "hours": 48, "hoursComment": "All backups older than 48 hours will be deleted. But only if the number of files is greater than of backupNumber", "period": 120, "periodComment": "by default backup every 2 hours. Time is in minutes. To disable backup set the value to 0", "path": "", "pathComment": "Absolute path to backup directory or empty to backup in data directory" } }, "log": { "level": "info", "maxDays": 3, "noStdout": true, "transport": { "file1": { "type": "file", "enabled": true, "filename": "log/iobroker", "fileext": ".log", "maxsize": null, "maxFiles": null, "maxSize": null, "level": "" }, "syslog1": { "type": "syslog", "enabled": false, "host": "localhost", "hostComment": "The host running syslogd, defaults to localhost.", "portComment": "The port on the host that syslog is running on, defaults to syslogd's default port(514/UDP).", "protocol": "udp4", "protocolComment": "The network protocol to log over (e.g. tcp4, udp4, unix, unix-connect, etc).", "pathComment": "The path to the syslog dgram socket (i.e. /dev/log or /var/run/syslog for OS X).", "facilityComment": "Syslog facility to use (Default: local0).", "localhost": "iobroker", "localhostComment": "Host to indicate that log messages are coming from (Default: localhost).", "sysLogTypeComment": "The type of the syslog protocol to use (Default: BSD).", "app_nameComment": "The name of the application (Default: process.title).", "eolComment": "The end of line character to be added to the end of the message (Default: Message without modifications).", "level": "", "facility": "" }, "seq1": { "type": "seq", "enabled": false, "serverUrl": "http://IP:PORT", "serverUrlComment": "The http(s) URL including port of the seq server. If you use HTTPS a real certificate is needed; self signed certs are ot accepted.", "apiKey": "", "apiKeyComment": "The apiKey of the seq system", "level": "", "eol": "" } } }, "plugins": {}, "dataDir": "../../iobroker-data/" } -
Info zum System:
e6iob@NUCioBroker:/opt/iobroker/iobroker-data$ which nodejs node npm && nodejs -v && node -v && npm -v && apt policy nodejs /usr/bin/nodejs /usr/bin/node /usr/bin/npm v14.19.0 v14.19.0 [sudo] Passwort für e6iob: 8.6.0 nodejs: Installiert: 14.19.0-deb-1nodesource1 Installationskandidat: 14.19.1-deb-1nodesource1 Versionstabelle: 14.19.1-deb-1nodesource1 500 500 https://deb.nodesource.com/node_14.x bullseye/main amd64 Packages *** 14.19.0-deb-1nodesource1 100 100 /var/lib/dpkg/status 12.22.5~dfsg-2~11u1 500 500 http://deb.debian.org/debian bullseye/main amd64 Packages 500 http://security.debian.org/debian-security bullseye-security/main amd64 Packages e6iob@NUCioBroker:/opt/iobroker/iobroker-data$ -
Info zum System:
e6iob@NUCioBroker:/opt/iobroker/iobroker-data$ which nodejs node npm && nodejs -v && node -v && npm -v && apt policy nodejs /usr/bin/nodejs /usr/bin/node /usr/bin/npm v14.19.0 v14.19.0 [sudo] Passwort für e6iob: 8.6.0 nodejs: Installiert: 14.19.0-deb-1nodesource1 Installationskandidat: 14.19.1-deb-1nodesource1 Versionstabelle: 14.19.1-deb-1nodesource1 500 500 https://deb.nodesource.com/node_14.x bullseye/main amd64 Packages *** 14.19.0-deb-1nodesource1 100 100 /var/lib/dpkg/status 12.22.5~dfsg-2~11u1 500 500 http://deb.debian.org/debian bullseye/main amd64 Packages 500 http://security.debian.org/debian-security bullseye-security/main amd64 Packages e6iob@NUCioBroker:/opt/iobroker/iobroker-data$npm ist nicht die Version aus dem Paket.
Und halt nodejs aktuell. -
hier die aktuelle iobroker.json
ich habe die 60G Datei gelöscht und iobroker neu gestartet und jetzt aus dem Backup heute nacht wieder hergestellt. läuft gleich, dann sende ich die anderen Infos.
{ "system": { "memoryLimitMB": 0, "hostname": "", "statisticsInterval": 15000, "statisticsIntervalComment": "Interval how often the counters for input/output in adapters and controller will be updated", "checkDiskInterval": 300000, "checkDiskIntervalComment": "Interval how often the disk size will be checked", "instanceStartInterval": 2000, "noChmodComment": "Flag to test new feature with no chmod call. Must be deleted later and noChmod must be mainline (2018.06.04)", "compact": false, "compactComment": "Controller will try to start the instances as a part of the same process. No spawn will be done. Only by adapters that support it and have flag compact flag in io-package.json", "allowShellCommands": false, "allowShellCommandsComment": "Allow execution of \"shell\" sendToHost commands", "memLimitWarn": 100, "memLimitWarnComment": "If the available RAM is below this threshold on adapter start, a warning will be logged.", "memLimitError": 50, "memLimitErrorComment": "If the available RAM is below this threshold on adapter start, an error will be logged." }, "multihostService": { "enabled": false, "secure": true, "password": "" }, "objects": { "type": "jsonl", "typeComment": "Possible values: 'file' - [port 9001], redis - [port 6379], couch - [port 5984].", "host": "127.0.0.1", "port": 9001, "noFileCache": false, "maxQueue": 1000, "connectTimeout": 2000, "writeFileInterval": 5000, "dataDir": "", "options": { "auth_pass": null, "retry_max_delay": 5000, "retry_max_count": 19, "db": 0, "family": 0 }, "backup": { "disabled": false, "files": 24, "filesComment": "Minimal number of backup files, after the deletion will be executed according to backupTime settings", "hours": 48, "hoursComment": "All backups older than 48 hours will be deleted. But only if the number of files is greater than of backupNumber", "period": 120, "periodComment": "by default backup every 2 hours. Time is in minutes. To disable backup set the value to 0", "path": "", "pathComment": "Absolute path to backup directory or empty to backup in data directory" } }, "states": { "type": "jsonl", "typeComment": "Possible values: 'file' - [port 9000], 'redis' - [port 6379].", "host": "127.0.0.1", "port": 9000, "connectTimeout": 2000, "writeFileInterval": 30000, "dataDir": "", "options": { "auth_pass": null, "retry_max_delay": 5000, "retry_max_count": 19, "db": 0, "family": 0 }, "backup": { "disabled": false, "files": 24, "filesComment": "Minimal number of backup files, after the deletion will be executed according to backupTime settings", "hours": 48, "hoursComment": "All backups older than 48 hours will be deleted. But only if the number of files is greater than of backupNumber", "period": 120, "periodComment": "by default backup every 2 hours. Time is in minutes. To disable backup set the value to 0", "path": "", "pathComment": "Absolute path to backup directory or empty to backup in data directory" } }, "log": { "level": "info", "maxDays": 3, "noStdout": true, "transport": { "file1": { "type": "file", "enabled": true, "filename": "log/iobroker", "fileext": ".log", "maxsize": null, "maxFiles": null, "maxSize": null, "level": "" }, "syslog1": { "type": "syslog", "enabled": false, "host": "localhost", "hostComment": "The host running syslogd, defaults to localhost.", "portComment": "The port on the host that syslog is running on, defaults to syslogd's default port(514/UDP).", "protocol": "udp4", "protocolComment": "The network protocol to log over (e.g. tcp4, udp4, unix, unix-connect, etc).", "pathComment": "The path to the syslog dgram socket (i.e. /dev/log or /var/run/syslog for OS X).", "facilityComment": "Syslog facility to use (Default: local0).", "localhost": "iobroker", "localhostComment": "Host to indicate that log messages are coming from (Default: localhost).", "sysLogTypeComment": "The type of the syslog protocol to use (Default: BSD).", "app_nameComment": "The name of the application (Default: process.title).", "eolComment": "The end of line character to be added to the end of the message (Default: Message without modifications).", "level": "", "facility": "" }, "seq1": { "type": "seq", "enabled": false, "serverUrl": "http://IP:PORT", "serverUrlComment": "The http(s) URL including port of the seq server. If you use HTTPS a real certificate is needed; self signed certs are ot accepted.", "apiKey": "", "apiKeyComment": "The apiKey of the seq system", "level": "", "eol": "" } } }, "plugins": {}, "dataDir": "../../iobroker-data/" } -
@fraso die leeren jsonlOptions sind nicht da, so wie es sein soll. War nur so eine Idee. die js-controller version bekommst du unter Hosts angezeigt oder auf der Konsole mit
iob -v -
npm ist nicht die Version aus dem Paket.
Und halt nodejs aktuell. -
Hi Thomas,
habe in Deiner Signatur geschaut aber dort nicht gefunden wie man die npm "korrigiert".Gibt es hier eine korrekte Anleitung die ich abarbeiten kann ?
Danke.
Installier das Update, dann wird npm gleich richtig mitinstalliert.
Und lass die Finger davon npm global an der Paketverwaltung vorbei ins System zu knüppeln. -
@apollon77
Hallo,meine Dateien sind gewachsen. Normalerweise freue ich mich wenn etwas gutes wächst. Aber diesmal nicht.
Iobroker hat die Platte voll gemacht und dann war Ende. Konnte keine Instanzen mehr aufrufen.
Gestoppt
Gestartete6iob@NUCioBroker:~$ iob status Server Cannot start inMem-states on port 9000: Failed to lock DB file "/opt/iobroker/iobroker-data/states.jsonl"!Verzeichnis geprüft:
e6iob@NUCioBroker:/opt/iobroker/iobroker-data$ ls -l insgesamt 95420220 drwxrwxr-x+ 2 iobroker iobroker 4096 15. Apr 08:45 backitup drwxrwxrwx+ 2 iobroker iobroker 12288 23. Apr 16:54 backup-objects drwxrwxrwx+ 55 iobroker iobroker 4096 14. Apr 21:46 files drwxrwxr-x+ 4 iobroker iobroker 4096 23. Jan 12:58 ham_0 drwxrwxr-x+ 34 iobroker iobroker 4096 23. Feb 01:11 history -rwxrwxrwx+ 1 iobroker iobroker 5153 15. Apr 20:46 iobroker.json -rwxrwxr-x+ 1 e6iob e6iob 5308 15. Apr 20:45 iobroker.json_save drwxrwxr-x+ 4 iobroker iobroker 4096 15. Apr 08:56 node-red -rwxrwxrwx+ 1 iobroker iobroker 3 23. Apr 17:58 notifications.json -rw-rwxr--+ 1 iobroker iobroker 0 14. Feb 11:45 objects.json2022-02-12_11-46_objects.json.gz -rw-rwxr--+ 1 iobroker iobroker 20148088 20. Mär 12:18 objects.json.bak.migrated_save -rw-rw-r--+ 1 iobroker iobroker 25881289 23. Apr 17:59 objects.jsonl drwxrwxr-x+ 2 iobroker iobroker 4096 23. Apr 18:01 objects.jsonl.lock -rw-rwxr--+ 1 iobroker iobroker 20148725 20. Mär 12:19 objects.json.migrated_save -rw-rwxr--+ 1 iobroker iobroker 4322902 20. Mär 12:19 states.json.bak.migrated_save -rw-rwxr--+ 1 iobroker iobroker 0 14. Feb 11:21 states.json.broken -rw-rw-r--+ 1 iobroker iobroker 63986514378 23. Apr 17:58 states.jsonl drwxrwxr-x+ 2 iobroker iobroker 4096 23. Apr 18:01 states.jsonl.lock -rw-rwxr--+ 1 iobroker iobroker 10907835462 8. Apr 16:49 states.jsonl_save -rw-rwxr--+ 1 iobroker iobroker 4322931 20. Mär 12:19 states.json.migrated_save -rw-rwxr--+ 1 iobroker iobroker 2854480 14. Feb 11:42 states.json.old -rw-rwxr--+ 1 iobroker iobroker 22738108416 15. Apr 07:53 states.save drwxrwxr-x+ 3 iobroker iobroker 4096 23. Jan 16:17 tmp drwxrwxr-x+ 2 iobroker iobroker 4096 23. Apr 17:58 zigbee_0 e6iob@NUCioBroker:/opt/iobroker/iobroker-data$Jemand eine Idee wieso das passiert? Die oben genannten Tips hatte ich umgesetzt.
Danke sehr!
@fraso sagte in ioBroker startet nicht mehr:
Jemand eine Idee wieso das passiert? Die oben genannten Tips hatte ich umgesetzt.
Ja, Bitte js-controller 4.0.23 installieren (ggf states.jsonl einmalig löschen... kannst gern das states.json.migrated_save nach states.json umbenennen dasnn hast du den States stand.
EDIT: Da aber bei dir die defekte EInstellung nicht da war ist das komisch. Bitte nach dem contreoller Update beobachten das es nicht wieder sooo grioss wird - ggf melden
-
@fastfoot sagte in ioBroker startet nicht mehr:
iob -v
e6iob@NUCioBroker:/opt/iobroker/iobroker-data$ iob -v 4.0.21 -
Installier das Update, dann wird npm gleich richtig mitinstalliert.
Und lass die Finger davon npm global an der Paketverwaltung vorbei ins System zu knüppeln. -
Nein. Über die Paketverwaltung. Wie alle andere Updates des Betriebssystems auch.
sudo apt upgrade sudo apt full-upgradeFalls das noch nie gemacht wurde...
-
-
Installier das Update, dann wird npm gleich richtig mitinstalliert.
Und lass die Finger davon npm global an der Paketverwaltung vorbei ins System zu knüppeln.@thomas-braun sagte in ioBroker startet nicht mehr:
Und lass die Finger davon npm global an der Paketverwaltung vorbei ins System zu knüppeln.
npm selbst empfiehlt das aber wenn es zB ein minor update gibt. Gibt es da einen Grund für deine Empfehlung?
iobroker läuft unter Docker auf QNAP TS-451+
SkriptRecovery: https://forum.iobroker.net/post/930558 -
@fraso
iob update && iob upgrade selffür den js-controller
apt update && apt upgradefür node. zuvor iobroker natürlich stoppen.iob stop@fastfoot sagte in ioBroker startet nicht mehr:
iob upgrade self
sudo apt upgrade gemacht
sudo apt full-upgrade gemacht
iob update listet ed mir die "updateable"´s auf aber updated nicht
iob upgrade self gemachte6iob@NUCioBroker:/opt/iobroker/iobroker-data$ which nodejs node npm && nodejs -v && node -v && npm -v && apt policy nodejs /usr/bin/nodejs /usr/bin/node /usr/bin/npm v14.19.1 v14.19.1 6.14.16 nodejs: Installiert: 14.19.1-deb-1nodesource1 Installationskandidat: 14.19.1-deb-1nodesource1 Versionstabelle: *** 14.19.1-deb-1nodesource1 500 500 https://deb.nodesource.com/node_14.x bullseye/main amd64 Packages 100 /var/lib/dpkg/status 12.22.5~dfsg-2~11u1 500 500 http://deb.debian.org/debian bullseye/main amd64 Packages 500 http://security.debian.org/debian-security bullseye-security/main amd64 Packages e6iob@NUCioBroker:/opt/iobroker/iobroker-data$ -
@thomas-braun sagte in ioBroker startet nicht mehr:
Und lass die Finger davon npm global an der Paketverwaltung vorbei ins System zu knüppeln.
npm selbst empfiehlt das aber wenn es zB ein minor update gibt. Gibt es da einen Grund für deine Empfehlung?
@fastfoot sagte in ioBroker startet nicht mehr:
npm selbst empfiehlt das aber wenn es zB ein minor update gibt. Gibt es da einen Grund für deine Empfehlung?
Die empfehlen das auch für Major Upgrades.
Hat in der Vergangenheit regelmäßig für Probleme gesorgt. Upstream wird npm ja auch immer mit einer bestimmten Version von nodejs zusammengepackt. -
@fraso da gibt es die 4.0.23 welche genau dieses Problem behebt(obwohl das manuelle Entfernen der jsonlOptions das eig. auch behoben haben sollte)
784
Online32.4k
Benutzer81.5k
Themen1.3m
Beiträge