neu installierter ioBroker über Browser nicht erreichbar
-
curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add - -
curl -sL https://iobroker.net/install.sh | bash - library: loaded Library version=2020-04-12 ========================================================================== Welcome to the ioBroker installer! Installer version: 2020-04-12 ========================================================================== ========================================================================== Installing prerequisites (1/4) ========================================================================== Hit:1 https://deb.nodesource.com/node_12.x buster InRelease Get:2 https://dl.yarnpkg.com/debian stable InRelease [17.1 kB] Hit:3 http://ftp.halifax.rwth-aachen.de/raspbian/raspbian buster InRelease Err:2 https://dl.yarnpkg.com/debian stable InRelease The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging <yarn@dan.cx> Reading package lists... Done W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://dl.yarnpkg.com/debian stable InRelease: The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging <yarn@dan.cx> W: Failed to fetch https://dl.yarnpkg.com/debian/dists/stable/InRelease The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging <yarn@dan.cx> W: Some index files failed to download. They have been ignored, or old ones used instead. Changing npm registry to https://registry.npmjs.org Installed gcc-c++ ========================================================================== Creating ioBroker user and directory (2/4) ========================================================================== Created /etc/sudoers.d/iobroker Directory /opt/iobroker created ========================================================================== Installing ioBroker (3/4) ========================================================================== ========================================================================== Finalizing installation (4/4) ========================================================================== Enabling autostart... Autostart enabled! Fixing directory permissions... ========================================================================== ioBroker was installed successfully Open http://xxx.xxx.xxx.xxx:8081 in a browser and start configuring! ========================================================================== -
curl -sS https://dl.yarnpkg.com/debia/pubkey.gpg | sudo apt-key add - gpg: no valid OpenPGP data found. -
@C3PO
Da fehlt dir ein 'n'. Kopier die Befehle doch rein.curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add - -
curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add - OK -
@C3PO Jetzt sollte die Meldung von apt auch weg sein.
apt update && apt upgrade -
done
apt update && apt upgrade Hit:1 http://ftp.halifax.rwth-aachen.de/raspbian/raspbian buster InRelease Hit:2 https://deb.nodesource.com/node_12.x buster InRelease Hit:3 https://dl.yarnpkg.com/debian stable InRelease Reading package lists... Done Building dependency tree Reading state information... Done 1 package can be upgraded. Run 'apt list --upgradable' to see it. Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: yarn 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 891 kB of archives. After this operation, 8,192 B of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 https://dl.yarnpkg.com/debian stable/main armhf yarn all 1.22.4-1 [891 kB] Fetched 891 kB in 0s (2,805 kB/s) (Reading database ... 83280 files and directories currently installed.) Preparing to unpack .../archives/yarn_1.22.4-1_all.deb ... Unpacking yarn (1.22.4-1) over (1.19.1-1) ... Setting up yarn (1.22.4-1) ... -
@C3PO Siehste, jetzt funktioniert das yarn-Repo auch wieder.
iobroker version iobroker start whoami sudo -u iobroker whoami ls -la /etc/sudoers.d/ -
muss ich wohl wieder als root machen
loxberry@loxberry:~ $ iobroker version 2.2.9 loxberry@loxberry:~ $ iobroker start loxberry@loxberry:~ $ whoami loxberry loxberry@loxberry:~ $ sudo -u iobroker whoami [sudo] password for loxberry: Sorry, user loxberry is not allowed to execute '/usr/bin/whoami' as iobroker on loxberry. -
@C3PO
Als rootapt install sudo -
root@loxberry:~# whoami root root@loxberry:~# sudo -u iobroker whoami iobroker root@loxberry:~# ls -la /etc/sudoers.d/ total 28 dr-xr-xr-x 2 root root 4096 May 15 23:17 . drwxr-xr-x 21 loxberry loxberry 4096 Sep 24 2019 .. -r--r----- 1 root root 1145 May 15 23:17 iobroker -rw-rw-r-- 1 root root 1684 Oct 25 2019 lbdefaults -rw-r--r-- 1 root root 586 May 15 15:54 mqttgateway -r--r----- 1 root root 958 Apr 1 2018 README -rw-r--r-- 1 root root 158 May 15 15:59 weather4lox -
apt install sudo Reading package lists... Done Building dependency tree Reading state information... Done sudo is already the newest version (1.8.27-1+deb10u2). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root@loxberry:~#hatte ich schon mal probiert, sudo geht trotzdem nicht
-
usermod -aG sudo loxberry -
root@loxberry:~# usermod -aG sudo loxberry root@loxberry:~# exit logout loxberry@loxberry:~ $ sudo nodejs -v [sudo] password for loxberry: Sorry, user loxberry is not allowed to execute '/usr/bin/nodejs -v' as root on loxberry. loxberry@loxberry:~ $ -
@C3PO
Als loxberrygroups -
loxberry@loxberry:~ $ groups loxberry tty dialout sudo audio www-data gpio -
@C3PO Dann klemmen die den user noch irgendwo anders ab.
Soll mir jetzt auch egal sein...iobroker status -
iobroker status Socket.io Server detected. Please update to js-controller 2.0 or higher! Socket.io Server detected. Please update to js-controller 2.0 or higher! Socket.io Server detected. Please update to js-controller 2.0 or higher! Socket.io Server detected. Please update to js-controller 2.0 or higher! Socket.io Server detected. Please update to js-controller 2.0 or higher! Socket.io Server detected. Please update to js-controller 2.0 or higher! Socket.io Server detected. Please update to js-controller 2.0 or higher! Socket.io Server detected. Please update to js-controller 2.0 or higher! iobroker is running on this host. No iobroker host is running. Objects type: file States type: file -
@C3PO
Keine Ahnung wie die 'Kollegen' von LoxBerry da im System rumfuhrwerken.
Sieht auf jedenfalls für mich äußerst schräg aus.In /opt/iobroker
npm install iobroker.js-controller -
root@loxberry:/opt/iobroker# npm install iobroker.js-controller > iobroker.js-controller@2.2.9 preinstall /opt/iobroker/node_modules/iobroker.js-controller > node lib/preinstallCheck.js NPM version: 6.14.4 > iobroker.js-controller@2.2.9 install /opt/iobroker/node_modules/iobroker.js-controller > node iobroker.js setup first Socket.io Server detected. Please update to js-controller 2.0 or higher! Socket.io Server detected. Please update to js-controller 2.0 or higher! Socket.io Server detected. Please update to js-controller 2.0 or higher! Socket.io Server detected. Please update to js-controller 2.0 or higher! Socket.io Server detected. Please update to js-controller 2.0 or higher! Socket.io Server detected. Please update to js-controller 2.0 or higher! Socket.io Server detected. Please update to js-controller 2.0 or higher! Socket.io Server detected. Please update to js-controller 2.0 or higher! npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules/chokidar/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.5 (node_modules/osx-temperature-sensor): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.5: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) + iobroker.js-controller@2.2.9 updated 1 package in 32.054s 3 packages are looking for funding run `npm fund` for details
