Server Cannot start inMem-objects on port 9001
-
@apollon77 also ich bin jetzt zwar im richtigen Pfad aber hab keinen Plan wie ich die iobroker.json öffne oder mir den Inhalt irgendwie sichtbar machen kann
-
@apollon77 ich mache für heute Schluss. Guts Nächtle.
Habe noch mal die gleichen Dateien von @radicalreel herangezogen - es scheint was mit dem Datumsformat teilweise bei mir nicht mehr zu stimmen.
Mal werden diese mit TT MM JJJJ und mal mit TT MM Time angezeigt.
Ob es von diesem ewt. kommt ? -
@rene-3 „cat iobroker.json“
-
pi@ReneRaspel:/opt/iobroker/iobroker-data $ cat iobroker.json { "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": 30000, "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": 30000, "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": 7, "noStdout": true, "transport": { "file1": { "type": "file", "enabled": true, "filename": "log/iobroker", "fileext": ".log", "maxsize": null, "maxFiles": null }, "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)." }, "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" } } }, "dataDirComment": "Always relative to iobroker.js-controller/", "plugins": {}, "dataDir": "../../iobroker-data/" } pi@ReneRaspel:/opt/iobroker/iobroker-data $ -
@rene-3 ok dann bitte noch sagen was „iob Version“ sagt
Dann bitte im iobroker.json unter objects die Zeile mit „connectTimeout“ (Zeile 33 laut deinem post) die Zahl von 30000 auf 600000 ändern (6 hundert tausend).
Dann bitte einmal „iob status“ ausführen und Geduld haben! Kannst ja mal Zeit stoppen wie lange es dauert.
Danach bitte wieder mit „ls -la“ schauen wie groß die objects.jsonl jetzt ist. Müsste deutlich kleiner sein.
-
pi@ReneRaspel:/opt/iobroker/iobroker-data $ iob version 4.0.23 -
Vielleicht war der Wert doch etwas zu hoch.
Sitz hier ca. 25 Min.Dann kam leider nur
pi@ReneRaspel:~ $ iob status iobroker is not running on this host. Objects type: jsonl States type: jsonl -
pi@ReneRaspel:~ $ ls -la /opt/iobroker/iobroker-data insgesamt 1111480 drwxrwxr-x+ 9 iobroker iobroker 4096 3. Sep 16:59 . drwxrwxr-x+ 6 iobroker iobroker 4096 1. Sep 11:58 .. drwxrwxr-x+ 2 iobroker iobroker 4096 21. Aug 02:40 backitup drwxrwxr-x+ 2 iobroker iobroker 12288 3. Sep 15:47 backup-objects drwxrwxr-x+ 26 iobroker iobroker 4096 27. Jun 19:27 files drwxrwxr-x+ 14 iobroker iobroker 4096 29. Aug 08:24 history drwxrwxr-x+ 2 iobroker iobroker 4096 10. Mär 20:00 homekit-controller.0 -rw-rwxr--+ 1 iobroker iobroker 5092 3. Sep 16:31 iobroker.json -rw-rwxr--+ 1 iobroker iobroker 3 29. Aug 08:24 notifications.json -rw-rwxr--+ 1 iobroker iobroker 6008528 9. Feb 2022 objects.json.bak.migrated -rw-rwxr--+ 1 iobroker iobroker 1123892076 3. Sep 16:53 objects.jsonl drwxrwxr-x+ 2 iobroker iobroker 4096 3. Sep 16:59 objects.jsonl.lock -rw-rwxr--+ 1 iobroker iobroker 6008525 9. Feb 2022 objects.json.migrated -rw-rwxr--+ 1 iobroker iobroker 92518 9. Feb 2022 states.json.bak.migrated -rw-rwxr--+ 1 iobroker iobroker 1994374 3. Sep 16:53 states.jsonl -rw-rwxr--+ 1 iobroker iobroker 92661 9. Feb 2022 states.json.migrated drwxrwxr-x+ 2 iobroker iobroker 4096 11. Mär 17:06 yahka.0.hapdata -
Date ist:
Samstag 3. Sep 17:36:00 CEST 2022
hatte ich ewt. gestern nicht richtig beantwortet
Also hier im letzten Bild sieht man es auch wieder, das in der vorletzten Spalte mal JJJJ und mal die Zeit TT:TT eingetragen wird ?
Irgendwie komisch -
-
Danke - probiere ich gleich aus
-
hat geklappt
pi@ReneRaspel:~ $ ls -la /opt/iobroker/iobroker-data insgesamt 1099560 drwxrwxr-x+ 9 iobroker iobroker 4096 3. Sep 17:45 . drwxrwxr-x+ 6 iobroker iobroker 4096 1. Sep 11:58 .. drwxrwxr-x+ 2 iobroker iobroker 4096 21. Aug 02:40 backitup drwxrwxr-x+ 2 iobroker iobroker 12288 3. Sep 15:47 backup-objects drwxrwxr-x+ 26 iobroker iobroker 4096 27. Jun 19:27 files drwxrwxr-x+ 14 iobroker iobroker 4096 29. Aug 08:24 history drwxrwxr-x+ 2 iobroker iobroker 4096 10. Mär 20:00 homekit-controller.0 -rw-rwxr--+ 1 iobroker iobroker 5092 3. Sep 16:31 iobroker.json -rw-rwxr--+ 1 iobroker iobroker 3 29. Aug 08:24 notifications.json -rw-rwxr--+ 1 iobroker iobroker 1123892076 3. Sep 16:53 objects.jsonl drwxrwxr-x+ 2 iobroker iobroker 4096 3. Sep 17:45 objects.jsonl.lock -rw-rwxr--+ 1 iobroker iobroker 1994374 3. Sep 16:53 states.jsonl drwxrwxr-x+ 2 iobroker iobroker 4096 11. Mär 17:06 yahka.0.hapdata pi@ReneRaspel:~ $ -
@apollon77 sagte in Server Cannot start inMem-objects on port 9001:
Müsste deutlich kleiner sein.
iob status vergrössert beide *.jsonl Dateien. Hier meine, man sieht es aber auch bei @rene-3
root@iobroker01:/opt/iobroker/iobroker-data# ps -ef && ls -ls *jsonl&&iob status && ls -ls *jsonl UID PID PPID C STIME TTY TIME CMD root 1 0 0 11:54 ? 00:00:00 /bin/bash /opt/scripts/iobroker_startup.sh root 21046 0 0 16:33 pts/0 00:00:00 bash root 25048 1 0 17:27 ? 00:00:00 tail -f /dev/null root 25972 21046 0 17:51 pts/0 00:00:00 ps -ef 25980 -rw-r--r-- 1 iobroker iobroker 26600624 Sep 3 17:50 objects.jsonl 19944 -rw-r--r-- 1 iobroker iobroker 20422637 Sep 3 17:50 states.jsonl iobroker is not running on this host. Objects type: jsonl States type: jsonl root@iobroker01:/opt/iobroker/iobroker-data# ls -ls *jsonl 25980 -rw-r--r-- 1 iobroker iobroker 26601216 Sep 3 17:51 objects.jsonl 19948 -rw-r--r-- 1 iobroker iobroker 20422811 Sep 3 17:51 states.jsonl root@iobroker01:/opt/iobroker/iobroker-data# -
Kann ich nicht bestätigen.
echad@chet:/opt/iobroker/iobroker-data $ ls -l && iobroker status && ls -l total 35408 drwxrwxr-x+ 2 iobroker iobroker 4096 Sep 3 03:43 backitup drwxrwxr-x+ 2 iobroker iobroker 4096 Sep 3 17:46 backup-objects drwxrwxr-x+ 41 iobroker iobroker 4096 Aug 19 22:05 files drwxrwxr-x+ 9 iobroker iobroker 4096 Sep 3 04:26 history -rw-rwxr--+ 1 iobroker iobroker 4972 Sep 3 00:29 iobroker.json drwxrwxr-x+ 4 iobroker iobroker 4096 Aug 19 22:02 node-red -rw-rw-r--+ 1 iobroker iobroker 3 Aug 31 15:45 notifications.json -rw-rw-r--+ 1 iobroker iobroker 31879257 Sep 3 17:58 objects.jsonl drwxrwxr-x+ 2 iobroker iobroker 4096 Sep 3 17:59 objects.jsonl.lock -rw-rw-r--+ 1 iobroker iobroker 4326154 Sep 3 17:59 states.jsonl drwxrwxr-x+ 2 iobroker iobroker 4096 Sep 3 17:59 states.jsonl.lock drwxrwxr-x+ 2 iobroker iobroker 4096 Sep 3 17:47 zigbee_0 iobroker is running on this host. Objects type: jsonl States type: jsonl total 35408 drwxrwxr-x+ 2 iobroker iobroker 4096 Sep 3 03:43 backitup drwxrwxr-x+ 2 iobroker iobroker 4096 Sep 3 17:46 backup-objects drwxrwxr-x+ 41 iobroker iobroker 4096 Aug 19 22:05 files drwxrwxr-x+ 9 iobroker iobroker 4096 Sep 3 04:26 history -rw-rwxr--+ 1 iobroker iobroker 4972 Sep 3 00:29 iobroker.json drwxrwxr-x+ 4 iobroker iobroker 4096 Aug 19 22:02 node-red -rw-rw-r--+ 1 iobroker iobroker 3 Aug 31 15:45 notifications.json -rw-rw-r--+ 1 iobroker iobroker 31879257 Sep 3 17:58 objects.jsonl drwxrwxr-x+ 2 iobroker iobroker 4096 Sep 3 17:59 objects.jsonl.lock -rw-rw-r--+ 1 iobroker iobroker 4326154 Sep 3 17:59 states.jsonl drwxrwxr-x+ 2 iobroker iobroker 4096 Sep 3 17:59 states.jsonl.lock drwxrwxr-x+ 2 iobroker iobroker 4096 Sep 3 17:47 zigbee_0 -
aber bei dir läuft der host
Bei uns leider nicht ( @fastfoot ) und mir.
-
@rene-3 sagte in Server Cannot start inMem-objects on port 9001:
leider nicht
was heisst leider, das war die Vorgabe dass er vorher gestoppt wird
-
also ich kann iob stoppen und starten - aber meine läuft überhaupt nicht mehr.
-
nach https://forum.iobroker.net/post/852366 hatte ich nur den host(eig. den Container) neu gestartet und jetzt ist die objects.jsonl als auch die states.jsonl nochmal um einiges größer
root@iobroker01:/opt/iobroker/iobroker-data# ls -ls *jsonl 32924 -rw-r--r-- 1 iobroker iobroker 33708285 Sep 3 18:07 objects.jsonl 22968 -rw-r--r-- 1 iobroker iobroker 23517085 Sep 3 18:07 states.jsonl root@iobroker01:/opt/iobroker/iobroker-data#ich bin zufrieden, wollte nur meine Beobachtung teilen
-
@rene-3 keine Meldung auf der Konsole nach
iob start?tail -f /opt/iobroker/log/*curr* -
Thx, habe es eingegeben, aber mein System ist zur Zeit so seeeehr langsam und zum "iob start" braucht es auch nochmal ein paar Minütchen ...
Vielleicht sieht man so mehr heraus.
