iobroker läuft nicht mehr
-
Das ist ein alter Raspberry.
Der muss bezüglich nodejs besonders/anders angepackt werden. In meinem nodejs-HowTo wird das aber auch erwähnt. Schau mal reinDer hat 512MB RAM, oder? Das dürfte kaum für eine
sinnvollen Betrieb ausreichen. Das Doppelte ist schon schwierig. -
Habe ich versucht aber v14 wird nicht gefunden:
micros02@smartmeter:~ $ wget https://unofficial-builds.nodejs.org/download/release/14/node-v14-linux-armv6l.tar.xz --2022-04-30 16:45:25-- https://unofficial-builds.nodejs.org/download/release/14/node-v14-linux-armv6l.tar.xz Resolving unofficial-builds.nodejs.org (unofficial-builds.nodejs.org)... 45.55.98.129 Connecting to unofficial-builds.nodejs.org (unofficial-builds.nodejs.org)|45.55.98.129|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2022-04-30 16:45:26 ERROR 404: Not Found. -
@emi-0 sagte in iobroker läuft nicht mehr:
VERSION muss ersetzt werden.
Statt
wget https://unofficial-builds.nodejs.org/download/release/VERSION/node-vVERSION-linux-armv6l.tar.xzalso
wget https://unofficial-builds.nodejs.org/download/release/v14.19.1/node-v14.19.1-linux-armv6l.tar.xz -
ja, der hat 512MB. Hat, wie gesagt, seit März gut funktioniert. Er liest nur alle 5s die aktuelle Leistung und den Stromverbrauch über einen Infrarot-Lesekopf aus und schreibt die Werte in je eine json-Datei.
-
ich hatte VERSION durch 14 ersetzt.
Anscheinend ist die aktuelle Version 14.19.1
Das wusste ich nicht.
Jetzt habe ich dieses Ergebnis:micros02@smartmeter:~ $ micros02@smartmeter:~ $ wget https://unofficial-builds.nodejs.org/download/release/14/node-v14-linux-armv6l.tar.xz --2022-04-30 16:45:25-- https://unofficial-builds.nodejs.org/download/release/14/node-v14-linux-armv6l.tar.xz Resolving unofficial-builds.nodejs.org (unofficial-builds.nodejs.org)... 45.55.98.129 Connecting to unofficial-builds.nodejs.org (unofficial-builds.nodejs.org)|45.55.98.129|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2022-04-30 16:45:26 ERROR 404: Not Found. wget https://unofficial-builds.nodejs.org/download/release/v14.19.1/node-v14.19.1-linux-armv6l.tar.xz -bash: micros02@smartmeter:~: command not found -bash: --2022-04-30: command not found -bash: syntax error near unexpected token `(' -bash: syntax error near unexpected token `(' -bash: HTTP: command not found -bash: 2022-04-30: command not found --2022-04-30 17:07:41-- https://unofficial-builds.nodejs.org/download/release/v14.19.1/node-v14.19.1-linux-armv6l.tar.xz Resolving unofficial-builds.nodejs.org (unofficial-builds.nodejs.org)... 45.55.98.129 Connecting to unofficial-builds.nodejs.org (unofficial-builds.nodejs.org)|45.55.98.129|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 19453756 (19M) [application/x-xz] Saving to: ‘node-v14.19.1-linux-armv6l.tar.xz’ node-v14.19.1-linux 100%[===================>] 18.55M 2.90MB/s in 6.8s 2022-04-30 17:07:48 (2.73 MB/s) - ‘node-v14.19.1-linux-armv6l.tar.xz’ saved [19453756/19453756] -
Dann ist das Archiv jetzt heruntergeladen worden.
Also weiter im Text.VERSION wie gehabt ersetzen. Die Tab-Taste ist dein Freund.
tar -xvf node-vVERSION-linux-armv6l.tar.xz cd node-vVERSION-linux-armv6l/ sudo cp -R * /usr/local/ sudo ln -s /usr/local/bin/node /usr/local/bin/nodejs sudo reboot -
habe alle Schritte ausgeführt und die nodejs-Installation geprüft:
micros02@smartmeter:~ $ sudo ln -s /usr/bin/node /usr/bin/nodejs ln: failed to create symbolic link '/usr/bin/nodejs': File exists micros02@smartmeter:~ $ which nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs /usr/local/bin/nodejs /usr/local/bin/node /usr/local/bin/npm v14.19.1 v14.19.1 6.14.16 micros02 /home/micros02 Hit:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease Hit:2 http://archive.raspberrypi.org/debian bullseye InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done 2 packages can be upgraded. Run 'apt list --upgradable' to see them. nodejs: Installed: (none) Candidate: 12.22.5~dfsg-2~11u1 Version table: 12.22.5~dfsg-2~11u1 500 500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages micros02@smartmeter:~ $ -
@emi-0 sagte in iobroker läuft nicht mehr:
nodeJS passt nun.
Die beiden Updates noch einspielen:
2 packages can be upgraded
sudo apt full-upgrade -
das hat funktioniert:
micros02@smartmeter:~ $ sudo apt full-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: gyp javascript-common libc-ares2 libjs-highlight.js libjs-inherits libjs-is-typedarray libjs-psl libjs-typedarray-to-buffer libnode-dev libnode72 libssl-dev libuv1-dev xdg-utils Use 'sudo apt autoremove' to remove them. The following packages will be upgraded: libexpat1 libexpat1-dev 2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 198 kB of archives. After this operation, 3,072 B of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf libexpat1-dev armhf 2.2.10-2+deb11u3 [123 kB] Get:2 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf libexpat1 armhf 2.2.10-2+deb11u3 [74.9 kB] Fetched 198 kB in 1s (182 kB/s) Reading changelogs... Done (Reading database ... 49910 files and directories currently installed.) Preparing to unpack .../libexpat1-dev_2.2.10-2+deb11u3_armhf.deb ... Unpacking libexpat1-dev:armhf (2.2.10-2+deb11u3) over (2.2.10-2+deb11u2) ... Preparing to unpack .../libexpat1_2.2.10-2+deb11u3_armhf.deb ... Unpacking libexpat1:armhf (2.2.10-2+deb11u3) over (2.2.10-2+deb11u2) ... Setting up libexpat1:armhf (2.2.10-2+deb11u3) ... Setting up libexpat1-dev:armhf (2.2.10-2+deb11u3) ... Processing triggers for libc-bin (2.31-13+rpt2+rpi1+deb11u2) ... micros02@smartmeter:~ $ -
@emi-0 sagte in iobroker läuft nicht mehr:
Jetzt noch
sudo apt autoremoveum den überflüssigen Rest auch noch loszuwerden.
-
das hat jetzt auch funktioniert:
micros02@smartmeter:~ $ sudo apt autoremove Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. micros02@smartmeter:~ $ -
@emi-0
Dann dürfte die nodeJS-Laufzeitumgebung jetzt sauber sein. -
leider lässt sich iobroker immer noch nicht starten
micros02@smartmeter:~ $ iobroker fix library: loaded Library version=2022-02-10 ========================================================================== Welcome to the ioBroker installation fixer! Script version: 2022-02-13 You might need to enter your password a couple of times. ========================================================================== ========================================================================== Installing prerequisites (1/3) ========================================================================== Hit:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease Hit:2 http://archive.raspberrypi.org/debian bullseye InRelease Reading package lists... Done Installed gcc-c++ Installed python-dev ========================================================================== Checking ioBroker user and directory permissions (2/3) ========================================================================== Created /etc/sudoers.d/iobroker Fixing directory permissions... ========================================================================== Checking autostart (3/3) ========================================================================== Enabling autostart... Autostart enabled! ========================================================================== Your installation was fixed successfully Run iobroker start to start ioBroker again! ========================================================================== micros02@smartmeter:~ $ iobroker start micros02@smartmeter:~ $ iob status Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! micros02@smartmeter:~ $ -
@emi-0 sagte in iobroker läuft nicht mehr:
/opt/iobroker/iobroker-data/objects.jsonl
ls -l /opt/iobroker/iobroker-data/objects.jsonl sudo lsof /opt/iobroker/iobroker-data/objects.jsonl -
micros02@smartmeter:~ $ ls -l /opt/iobroker/iobroker-data/objects.jsonl -rw-rwxr--+ 1 iobroker iobroker 120034159 Apr 25 21:05 /opt/iobroker/iobroker-data/objects.jsonl micros02@smartmeter:~ $ sudo lsof /opt/iobroker/iobroker-data/objects.jsonl COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME iobroker. 1919 iobroker 19u REG 179,2 120034159 268535 /opt/iobroker/iobroker-data/objects.jsonl micros02@smartmeter:~ $ iob start micros02@smartmeter:~ $ iob status Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! micros02@smartmeter:~ $ -
getfacl /opt/iobroker/iobroker-data/objects.jsonl -
geht noch nicht:
micros02@smartmeter:~ $ getfacl /opt/iobroker/iobroker-data/objects.jsonl -bash: micros02@smartmeter:~: command not found -bash: -rw-rwxr--+: command not found -bash: micros02@smartmeter:~: command not found -bash: COMMAND: command not found -bash: iobroker.: command not found -bash: micros02@smartmeter:~: command not found -bash: micros02@smartmeter:~: command not found -bash: Server: command not found -bash: micros02@smartmeter:~: command not found getfacl: Removing leading '/' from absolute path names # file: opt/iobroker/iobroker-data/objects.jsonl # owner: iobroker # group: iobroker user::rw- group::r-- group:iobroker:rwx mask::rwx other::r-- micros02@smartmeter:~ $ iob start micros02@smartmeter:~ $ iob status Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! micros02@smartmeter:~ $ -
Da stimmen die Rechte nicht.
Auf meinem System schauen die anders aus.
Aber erstmal Sportschau gucken... -
erstmal vielen Dank
Viel Spaß bei der Sportschau.
Bis Morgen .... -
Hallo Thomas,
kannst Du bitte noch etwas zu den Rechten sagen, wie sie aussehen müssen, dass iobroker wieder gestartet werden kann?
