Server Cannot start inMem-objects on port 9001
-
@dieter_p
So grundsätzlich bist du da wie genau unterwegs?sudo ln -s /usr/bin/node /usr/bin/nodejs uname -m && which nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejsposten.
-
@thomas-braun said in Server Cannot start inMem-objects on port 9001:
sudo ln -s /usr/bin/node /usr/bin/nodejs
Danke
armv7l /usr/bin/nodejs /usr/bin/node /usr/bin/npm v14.19.3 v14.19.3 6.14.17 pi /home/pi OK:1 http://raspbian.raspberrypi.org/raspbian buster InRelease OK:2 http://archive.raspberrypi.org/debian buster InRelease OK:3 https://deb.nodesource.com/node_14.x buster InRelease Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen.... Fertig Alle Pakete sind aktuell. N: Paket nodejssudo kann nicht gefunden werden. N: Paket ln kann nicht gefunden werden. N: Paket /usr/bin/nodejs kann nicht gefunden werden. -
Bitte die komplette Eingabezeile inkl. des login prompts posten.
Da ist irgendwas krumm gelaufen, was ich jetzt nicht nachvollziehen kann, weil ich nicht sehe was da eingeklimpert wurde. (Am Rande: Mit der rechten Maustaste kann man in die Konsole pasten, in den meisten Terminalprogrammen jedenfalls) -
Sorry da stimmte was nicht:
pi@raspberrypi:~ $ uname -m && which nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs sudo ln -s /usr/bin/node /usr/bin/nodejs armv7l /usr/bin/nodejs /usr/bin/node /usr/bin/npm v14.19.3 v14.19.3 6.14.17 pi /home/pi OK:1 http://archive.raspberrypi.org/debian buster InRelease OK:2 http://raspbian.raspberrypi.org/raspbian buster InRelease OK:3 https://deb.nodesource.com/node_14.x buster InRelease Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen.... Fertig Alle Pakete sind aktuell. nodejs: Installiert: 14.19.3-deb-1nodesource1 Installationskandidat: 14.19.3-deb-1nodesource1 Versionstabelle: *** 14.19.3-deb-1nodesource1 500 500 https://deb.nodesource.com/node_14.x buster/main armhf Packages 100 /var/lib/dpkg/status 10.24.0~dfsg-1~deb10u1 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages sudo: Installiert: 1.8.27-1+deb10u3 Installationskandidat: 1.8.27-1+deb10u3 Versionstabelle: *** 1.8.27-1+deb10u3 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages 100 /var/lib/dpkg/status N: Paket ln kann nicht gefunden werden. N: Paket /usr/bin/nodejs kann nicht gefunden werden. -
@dieter_p sagte in Server Cannot start inMem-objects on port 9001:
Sorry da stimmte was nicht:
Da stimmt immer noch was nicht...
Egal.
cd /opt/iobroker sudo -H -u iobroker npm install iobroker.js-controller -
@thomas-braun said in Server Cannot start inMem-objects on port 9001:
sudo -H -u iobroker npm install iobroker.js-controller
das kommt raus:
pi@raspberrypi:~ $ cd /opt/iobroker pi@raspberrypi:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-controller > iobroker.js-controller@4.0.21 preinstall /opt/iobroker/node_modules/iobroker.js-controller > node lib/preinstallCheck.js NPM version: 6.14.17 > iobroker.js-controller@4.0.21 install /opt/iobroker/node_modules/iobroker.js-controller > node iobroker.js setup first No connection to databases possible ... npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/chokidar/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.7 (node_modules/osx-temperature-sensor): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/zigbee-herdsman/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/zigbee-herdsman-converters/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm ERR! code ELIFECYCLE npm ERR! errno 22 npm ERR! iobroker.js-controller@4.0.21 install: `node iobroker.js setup first` npm ERR! Exit status 22 npm ERR! npm ERR! Failed at the iobroker.js-controller@4.0.21 install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2022-07-07T14_57_18_192Z-debug.log pi@raspberrypi:/opt/iobroker $ -
@dieter_p läuft was anderes auf dem Host auf Port 9000 oder 9001?
-
@apollon77 said in Server Cannot start inMem-objects on port 9001:
@dieter_p läuft was anderes auf dem Host auf Port 9000 oder 9001?
Versuche mal ob ich das heraus bekomme aber wissentlich nein.
Auf dem Pi läuft noch ein WireGuard Client aber der nicht auf 9000/9001 und das auch nicht erst seit gestern sondern schon Monate. Sonst ist nichts installiert.
-
Kannst ja damit mal schauen:
sudo netstat -tulpenWas mich auch wundert:
iobroker.js-controller@4.0.21
Das müsste eigentlich auf allen Kanälen die 4.0.23 sein. Keine Ahnung wo das bei dir herkommt. Vielleicht aus dem npm cache.
-
da scheint nichts zu laufen:
pi@raspberrypi:~ $ netstat -an | grep 9000 pi@raspberrypi:~ $ netstat -an | grep 9001 pi@raspberrypi:~ $ man lsof pi@raspberrypi:~ $ lsof -i:9000 pi@raspberrypi:~ $ lsof -i:9001 pi@raspberrypi:~ $ sudo netstat -tulpen Aktive Internetverbindungen (Nur Server) Proto Recv-Q Send-Q Local Address Foreign Address State Benutzer Inode PID/Program name tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 16710 442/sshd tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 0 14477 287/cupsd tcp6 0 0 :::22 :::* LISTEN 0 16712 442/sshd tcp6 0 0 ::1:631 :::* LISTEN 0 14476 287/cupsd udp 0 0 0.0.0.0:68 0.0.0.0:* 0 16749 364/dhcpcd udp 0 0 0.0.0.0:631 0.0.0.0:* 0 14298 371/cups-browsed udp 0 0 0.0.0.0:36489 0.0.0.0:* 108 14190 298/avahi-daemon: r udp 0 0 0.0.0.0:48820 0.0.0.0:* 0 16853 - udp 0 0 0.0.0.0:5353 0.0.0.0:* 108 14188 298/avahi-daemon: r udp6 0 0 :::48820 :::* 0 16854 - udp6 0 0 :::50885 :::* 108 14191 298/avahi-daemon: r udp6 0 0 :::5353 :::* 108 14189 298/avahi-daemon: r udp6 0 0 :::546 :::* 0 16765 364/dhcpcd pi@raspberrypi:~ $ -
Vermutlich aber eine Desktop-Umgebung am Start.
-
Da Du immer darauf verweist und ich mir bewusst war mit dem RPI2 am Limit zu sein, bin ich mir zu 99,9% sicher nein
Edit:
pi@raspberrypi:~ $ who -r Runlevel 3 2022-07-07 16:20 -
Den cupsd fängt man sich halt bevorzugt mit einem Desktop ein, deswegen komme ich darauf.
npm cache mal gelöscht?
-
@thomas-braun said in Server Cannot start inMem-objects on port 9001:
Den cupsd fängt man sich halt bevorzugt mit einem Desktop ein, deswegen komme ich darauf.
npm cache mal gelöscht?
Sollte man das forcen?
pi@raspberrypi:~ $ sudo npm cache clean npm ERR! As of npm@5, the npm cache self-heals from corruption issues and data extracted from the cache is guaranteed to be valid. If you want to make sure everything is consistent, use 'npm cache verify' instead. On the other hand, if you're debugging an issue with the installer, you can use `npm install --cache /tmp/empty-cache` to use a temporary cache instead of nuking the actual one. npm ERR! npm ERR! If you're sure you want to delete the entire cache, rerun this command with --force. npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2022-07-07T16_39_18_206Z-debug.logEdit: Durch ein Verify des caches ergab sich keine Änderung:
pi@raspberrypi:~ $ npm cache verify Cache verified and compressed (~/.npm/_cacache): Content verified: 1864 (82698644 bytes) Index entries: 2895 Finished in 41.415s pi@raspberrypi:~ $ cd /opt/iobroker pi@raspberrypi:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-controller > iobroker.js-controller@4.0.21 preinstall /opt/iobroker/node_modules/iobroker.js-controller > node lib/preinstallCheck.js NPM version: 6.14.17 > iobroker.js-controller@4.0.21 install /opt/iobroker/node_modules/iobroker.js-controller > node iobroker.js setup first Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/chokidar/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.7 (node_modules/osx-temperature-sensor): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/zigbee-herdsman/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/zigbee-herdsman-converters/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm ERR! code ELIFECYCLE npm ERR! errno 24 npm ERR! iobroker.js-controller@4.0.21 install: `node iobroker.js setup first` npm ERR! Exit status 24 npm ERR! npm ERR! Failed at the iobroker.js-controller@4.0.21 install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2022-07-07T16_47_48_644Z-debug.log pi@raspberrypi:/opt/iobroker $Edit2: Etwas blöd, dass mir erst jetzt auffällt das ich in der Cloud nur BackUps bis zum 02.05.2022 liegen hab. Da scheint schon was länger nicht einwandfrei zu laufen. Sonst wäre eine Neuinstallation sicher der bessere Weg.
-
Dann ersuch mal Controller auf 4.0.23 ohne die install Skripte.
Also
cd /opt/iobroker
npm i iobroker.js-controller@4.0.23 --ignore-scriptsDann mal
iob status Bzw iob update
Edit:und vorher sicherstellen das wirklich aus ist. Also auch das im logfile unter /opt/iobroker/log nix neues kommt.
-
@apollon77
Danke. Leider noch gleiche Meldungen:pi@raspberrypi:/opt/iobroker/log $ nano iobroker.2022-07-08.log pi@raspberrypi:/opt/iobroker/log $ cd /opt/iobroker pi@raspberrypi:/opt/iobroker $ npm i iobroker.js-controller@4.0.23 --ignore-scripts npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/chokidar/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.7 (node_modules/osx-temperature-sensor): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/zigbee-herdsman-converters/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/zigbee-herdsman/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) + iobroker.js-controller@4.0.23 added 6 packages from 10 contributors and removed 3 packages in 156.871s 87 packages are looking for funding run `npm fund` for details pi@raspberrypi:/opt/iobroker $ cd pi@raspberrypi:~ $ iob status No connection to databases possible ... pi@raspberrypi:~ $ iob update No connection to databases possible ... pi@raspberrypi:~ $ npm fund /home/pi ╭────────────────────────────────────────────────────────────────╮ │ │ │ New major version of npm available! 6.14.17 → 8.13.2 │ │ Changelog: https://github.com/npm/cli/releases/tag/v8.13.2 │ │ Run npm install -g npm to update! │ │ │ ╰────────────────────────────────────────────────────────────────╯ pi@raspberrypi:~ $ -
@dieter_p Dann bitte "Iob custom" aufrufen und die Ausgabe zeigen. kannst DU mit CTRL-C abbrechen. Und bitte auch zeigen was ein "iob start" im ioBroker log bringt
-
@apollon77 said in Server Cannot start inMem-objects on port 9001:
Iob custom
Danke. Der Befehl "custom" fehlt oder ich mach was falsch
pi@raspberrypi:~ $ iob custom iobroker [command] Commands: iobroker setup Setup ioBroker iobroker start [all|<adapter>.<instance>] Starts the js-controller or a specified adapter instance iobroker stop [<adapter>.<instance>] stops the js-controller or a specified adapter instance iobroker restart [<adapter>.<instance>] Restarts js-controller or a specified adapter instance [aliases: r] iobroker debug <adapter>[.<instance>] Starts a Node.js debugging session for the adapter instance iobroker info Shows the host info iobroker logs [<adapter>] Monitor log iobroker add <adapter> [desiredNumber] Add instance of adapter [aliases: a] iobroker install <adapter> Installs a specified adapter [aliases: i] iobroker rebuild [<module>] Rebuild all native modules or path iobroker url <url> [<name>] Install adapter from specified url, e.g. GitHub iobroker del <adapter> Remove adapter and all instances from this host [aliases: delete] iobroker del <adapter>.<instance> Remove adapter instance [aliases: delete] iobroker update [<repositoryUrl>] Update repository and list adapters iobroker upgrade Upgrade management iobroker upload [all|<adapter>] Upload management [aliases: u] iobroker object Object management [aliases: o] iobroker state State management [aliases: s] iobroker message <adapter>[.instance] <command> [<message>] Send message to adapter instance/s iobroker list <type> [<filter>] List all entries, like objects iobroker chmod <mode> <file> Change file rights iobroker chown <user> <group> <file> Change file ownership iobroker touch <file> Touch file iobroker rm <file> Remove file iobroker file File management iobroker user User commands iobroker group group management iobroker host <hostname> Set host to given hostname iobroker set <adapter>.<instance> Change settings of adapter config iobroker license <license.file or license.text> Update license by given file iobroker cert Certificate management iobroker clean <yes> Clears all objects and states iobroker backup Create backup iobroker restore <backup name or path> Restore a specified backup iobroker validate <backup name or path> Validate a specified backup iobroker status [all|<adapter>.<instance>] Status of ioBroker or adapter instance [aliases: isrun] iobroker repo [<name>] Show repo information iobroker uuid Show uuid of the installation [aliases: id] iobroker unsetup Reset license, installation secret and language iobroker fix Execute the installation fixer script, this updates your ioBroker installation iobroker multihost Multihost management iobroker compact compact group management iobroker plugin Plugin management iobroker version [<adapter>] Show version of js-controller or specified adapter [aliases: v] Options: --help Show help [boolean] pi@raspberrypi:~ $ iob info No connection to databases possible ... pi@raspberrypi:~ $ iob start pi@raspberrypi:~ $ iob status Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! pi@raspberrypi:~ $ -
iobroker setup custom -
@thomas-braun said in Server Cannot start inMem-objects on port 9001:
iobroker setup custom
Danke
pi@raspberrypi:~ $ iobroker 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]:
