Neues YouTube-Video: Visualisierung im Devices-Adapter

[sunshineh]

@thomas-braun OK, diesmal ist ne Menge durchgelaufen:

/opt/iobroker $ sudo -H -u iobroker npm install iobroker                                        .js-controller
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman-converters/node_modules/acorn-globals
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman-converters/node_modules/char-regex
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman-converters/node_modules/jest-pnp-resolver
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman-converters/node_modules/bser
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman-converters/node_modules/fb-watchman
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman-converters/node_modules/capture-exit
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman-converters/node_modules/ecc-jsbn
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman-converters/node_modules/tr46
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman-converters/node_modules/w3c-hr-time
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/acorn-globals
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/char-regex
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/jest-pnp-resolver
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/bser
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/fb-watchman
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/capture-exit
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/ecc-jsbn
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/tr46
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/w3c-hr-time
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/node_modules/acorn-globals
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/node_modules/char-regex
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/node_modules/jest-pnp-resolver
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/node_modules/bser
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/node_modules/fb-watchman
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/node_modules/capture-exit
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/node_modules/ecc-jsbn
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/node_modules/tr46
npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/node_modules/w3c-hr-time
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.1 (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 typedoc@0.20.28 requires a peer of typescript@3.9.x || 4.0.x || 4.1.x but none is installed. You must install peer dependencies yourself.
npm WARN typedoc@0.20.28 requires a peer of typescript@3.9.x || 4.0.x || 4.1.x but none is installed. You must install peer dependencies yourself.

npm ERR! code EACCES
npm ERR! syscall access
npm ERR! path /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman-converters/node_modules/acorn-globals
npm ERR! errno -13
npm ERR! Error: EACCES: permission denied, access '/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman-converters/node_modules/acorn-globals'
npm ERR!  [Error: EACCES: permission denied, access '/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman-converters/node_modules/acorn-globals'] {
npm ERR!   errno: -13,
npm ERR!   code: 'EACCES',
npm ERR!   syscall: 'access',
npm ERR!   path: '/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman-converters/node_modules/acorn-globals'
npm ERR! }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/iobroker/.npm/_logs/2021-05-14T15_39_52_968Z-debug.log

[Thomas Braun]

@sunshineh

Als welcher user wurde das ausgeführt?
Und warum darf der iobroker nicht da herumschreiben?

iobroker fix
dmesg -T | grep -i ext4

[sunshineh]

@thomas-braun
Der Fix-Teil ist normal durchgelaufen, auf den 2. Befehl habe ich folgende antwort erhalten:

/opt/iobroker $ dmesg -T | grep -i ext4
[Fri May 14 08:56:39 2021] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  console=ttyS0,115200 console=tty1 root=PARTUUID=738a4d67-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
[Fri May 14 08:56:42 2021] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem
[Fri May 14 08:56:42 2021] EXT4-fs (mmcblk0p2): write access will be enabled during recovery
[Fri May 14 08:56:43 2021] EXT4-fs (mmcblk0p2): recovery complete
[Fri May 14 08:56:43 2021] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[Fri May 14 08:56:43 2021] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[Fri May 14 08:56:45 2021] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)

Dann habe ich noch

iobroker start

eingegeben, aber die Oberfläche ist dennoch nicht erreichbar.

Ich weiß nicht, ob's was hilft, aber ich hab noch folgenden Befehl getestet:

sudo netstat -tulpen
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       User       Inode      PID/Program name
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      0          17583      642/sshd
tcp        0      0 0.0.0.0:8765            0.0.0.0:*               LISTEN      0          16006      355/python
tcp        0      0 127.0.0.1:7999          0.0.0.0:*               LISTEN      0          16517      498/motion
tcp        0      0 0.0.0.0:8079            0.0.0.0:*               LISTEN      0          16515      498/motion
tcp        0      0 0.0.0.0:8083            0.0.0.0:*               LISTEN      0          16516      498/motion
tcp6       0      0 :::22                   :::*                    LISTEN      0          17585      642/sshd
udp        0      0 0.0.0.0:68              0.0.0.0:*                           0          15037      634/dhcpcd
udp        0      0 0.0.0.0:60003           0.0.0.0:*                           108        15733      386/avahi-daemon: r
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           108        15731      386/avahi-daemon: r
udp6       0      0 :::546                  :::*                                0          15832      634/dhcpcd
udp6       0      0 :::54391                :::*                                108        15734      386/avahi-daemon: r
udp6       0      0 :::5353                 :::*                                108        15732      386/avahi-daemon: r

[Thomas Braun]

@sunshineh
Da ist dein Dateisystem auf der SD-Karte zumindest angeschossen.
Starte den Server nochmal durch

sudo reboot

und dann als erste Aktion nochmal

dmesg -T | grep -i ext4

[sunshineh]

@thomas-braun

dmesg -T | grep -i ext4
[Sat May 15 11:14:18 2021] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  console=ttyS0,115200 console=tty1 root=PARTUUID=738a4d67-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
[Sat May 15 11:14:21 2021] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[Sat May 15 11:14:21 2021] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[Sat May 15 11:14:24 2021] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)

Ich bin hier auch diese Anleitung durch gegangen: elzershark.com

Doch da erhalte ich während der Ausführung folgenden Fehler

==========================================================================
    Installing ioBroker (3/4)
==========================================================================

npm ERR! code 22
npm ERR! path /opt/iobroker/node_modules/iobroker.js-controller
npm ERR! command failed
npm ERR! command sh -c node iobroker.js setup first
npm ERR! No connection to databases possible ...

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/pi/.npm/_logs/2021-05-15T09_09_16_803Z-debug.log

Also ich hab immer Probleme mit dem js-controller, der lässt sich aber nicht neu installieren.

[Thomas Braun]

@sunshineh
Vergiss den Elsterhai. Da kommt erfahrunggemäß nur Mist bei rum.

Hast du jetzt den ganzen Quatsch den der da in seiner Anleitung seinem Pfusch verzapft durchgeführt?

[sunshineh]

Ich bin bis Zeile 17 gekommen und hab dann nur Fehlermeldungen bekommen.
Glaubst du es wäre besser, das ganze System einfach neu aufzusetzen? Gibt es die Möglichkeit, dass ich mir Adapter oder meine erstellte VIS Oberfläche noch irgendwie sichere?

[Thomas Braun]

@sunshineh
Das heißt du hast bisher keine regelmäßigen Backups von deiner Installation?

Was passiert denn nun bei

cd /opt/iobroker
sudo -H -u iobroker npm install iobroker

Bitte VOLLSTÄNDIGE Ein- und Ausgaben, inkl. login prompt. Kopier einfach die komplette Konsole.

[sunshineh]

login as: 
pi@192.168.0.177's password:
Linux ioBroker-GartenHalle 5.10.17-v7+ #1414 SMP Fri Apr 30 13:18:35 BST 2021 armv7l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sat May 15 11:14:35 2021 from 192.168.0.245

SSH is enabled and the default password for the 'pi' user has not been changed.
This is a security risk - please login as the 'pi' user and type 'passwd' to set a new password.


Wi-Fi is currently blocked by rfkill.
Use raspi-config to set the country before use.

pi@ioBroker-GartenHalle:~ $ cd /opt/iobroker
pi@ioBroker-GartenHalle:/opt/iobroker $ sudo -H -u iobroker npm install iobroker
npm WARN deprecated request@2.88.0: request has been deprecated, see https://github.com/request/request/issues/3142
npm ERR! code 22
npm ERR! path /opt/iobroker/node_modules/iobroker.js-controller
npm ERR! command failed
npm ERR! command sh -c node iobroker.js setup first
npm ERR! No connection to databases possible ...

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/iobroker/.npm/_logs/2021-05-15T12_05_43_676Z-debug.log

[Thomas Braun]

@sunshineh sagte in ioBroker - keine Datenbank-Verbindung:

npm ERR! No connection to databases possible

Merkwürdig.
Hast du da mal auf redis umgestellt?
Was liefert

iobroker status

Am Rande: Dein Passwort für den pi solltest du auch mal von 'raspberry' auf was individuelles ändern.

sudo netstat -tulpen

bringt?

[Thomas Braun]

@sunshineh

node/npm richtig installiert?

which nodejs node npm && nodejs -v && node -v && npm -v && apt policy nodejs

[sunshineh]

Im Backup-Ordner habe ich folgendes gefunden

pi@ioBroker-GartenHalle:/opt/iobroker/backups $ dir
2021_04_12-22_58_14_backupiobroker.tar.gz
2021_05_03-00_16_22_backupiobroker.tar.gz

Kopier ich mir die jetzt auf meinen PC und setzt das System neu auf, oder kann ich die auch wieder einspielen?

[Homoran]

@thomas-braun sagte in ioBroker - keine Datenbank-Verbindung:

Merkwürdig.

package-lock json?

[sunshineh]

pi@ioBroker-GartenHalle:/opt/iobroker $ which nodejs node npm && nodejs -v && node -v && npm -v && apt policy nodejs
/usr/bin/nodejs
/usr/bin/node
/usr/bin/npm
v16.1.0
v16.1.0

[Thomas Braun]

@sunshineh
Das ist nicht die vollständige Ausgabe.
Aber nodeJS16 kommt i.d.R. mit npm7 daher und das funktioniert noch nicht zusammen mit dem js-controller Setup. Da kommen deine Probleme her.
Installier SAUBER nodeJS12 (max. nodeJS14). Anleitung wie das richtig geht in meiner Signatur.

(Edit:) Warum hast du eigentlich im ersten Beitrag geschrieben, es sei nodeJS 12 installiert? Da ist vermutlich so einiges krumm in dem System, was nodeJS angeht. Kann aber auch zusätzlich noch durch den Murks den die Elsterforelle da immer fabriziert verfrickelt worden sein.