UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?

[Homoran]

Bei einen korrekt Installierten Linux und Installation des ioBrokers über das Skript unter dem User, wir diesem User alles notwendige an Rechten gegeben

[Thomas Braun]

@DennisMenger sagte in Neuinstallation ioBroker nach Script - Userrechte:

Brachte leider keine Veränderung.

Wie sehen denn nun die Rechte aus?

id
ls -l /home/

sagt?

[DennisMenger]

@Thomas-Braun

dennis@ioBroker2025:~$ id
uid=1000(dennis) gid=1000(dennis) Gruppen=1000(dennis),24(cdrom),25(floppy),29(audio),30(dip),44(video),46(plugdev),100(users),101(netdev)

dennis@ioBroker2025:~$ ls -l /home/
insgesamt 8
drwx------ 3 dennis   dennis   4096 19. Nov 19:39 dennis
drwxr-x--- 2 iobroker iobroker 4096 19. Nov 18:27 iobroker

[Homoran]

@DennisMenger unter welchem user hast du den installer ausgeführt

[Thomas Braun]

@DennisMenger

Der user 'dennis' ist nicht in der Gruppe 'iobroker' drin.
Deswegen darf der auch nix dahingehend.

sudo usermod -a -G iobroker dennis

Dann den dennis aus- und wieder einloggen.

[DennisMenger]

@Homoran ích bin der Meinung unter dennis. Einen anderen User außer noch root gab es ja nicht bin ich der Meinung. Und root soll ja eigentlich nicht genutzt werden habe ich hier im Forum gelernt.

[Homoran]

@DennisMenger sagte in Neuinstallation ioBroker nach Script - Userrechte:

ích bin der Meinung unter dennis

Der wäre dann in der Gruppe iobroker gekommen

[Thomas Braun]

@DennisMenger sagte in Neuinstallation ioBroker nach Script - Userrechte:

Einen anderen User außer noch root gab es ja nicht bin ich der Meinung.

In der Regel wird im Installer des OS schon ein default user angelegt.
Das root-PW bleibt leer, z. B. bei Debian

[DennisMenger]

@Thomas-Braun bekomme leider die gleiche Fehlermeldung

Leider darf der Benutzer dennis »/usr/sbin/usermod -a -G iobroker dennis« als root auf ioBroker2025 nicht ausführen.

[Thomas Braun]

@DennisMenger

sudo usermod -a -G sudo dennis

Es muss allerdings sudo eingerichtet sein. Was haste denn da als VM installiert?

bekomme leider die gleiche Fehlermeldung

Die Meldung ist übrigens eine andere... ;-)

[DennisMenger]

@Thomas-Braun Installiert ist debian-13.2.0

Stimmt, andere Meldung, aber vom Ergebnis konnte der User trotzdem das nicht ausführen.

Scheint jetzt zu funktionieren.

dennis@ioBroker2025:~$ id
uid=1000(dennis) gid=1000(dennis) Gruppen=1000(dennis),24(cdrom),25(floppy),27(sudo),29(audio),30(dip),44(video),46(plugdev),100(users),101(netdev),1001(iobroker)

dennis@ioBroker2025:~$ ls -l /home/
insgesamt 8
drwx------ 3 dennis   dennis   4096 19. Nov 19:39 dennis
drwxr-x--- 2 iobroker iobroker 4096 19. Nov 18:27 iobroker

Sind die Rechte jetzt so ok?

[Thomas Braun]

@DennisMenger

sudo usermod -a -G adm,dialout dennis

Dann nochmal neustarten und die Ausgabe von

iob diag

posten.

[DennisMenger]

@Thomas-Braun

```bash
Script v.2025-08-09

*** BASE SYSTEM ***
Operating System: Debian GNU/Linux 13 (trixie)
 Static hostname: ioBroker2025
       Icon name: computer-vm
         Chassis: vm 🖴
    AF_VSOCK CID: 1
  Virtualization: kvm
          Kernel: Linux 6.12.57+deb13-amd64
    Architecture: x86-64
 Hardware Vendor: QEMU
  Hardware Model: Standard PC _i440FX + PIIX, 1996_
Firmware Version: rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org
   Firmware Date: Tue 2014-04-01
    Firmware Age: 11y 7month 2w 6d
OS is similar to:

model name      : QEMU Virtual CPU version 2.5+
Docker          : false
Virtualization  : kvm
Kernel          : x86_64
Userland        : 64 bit

Systemuptime and Load:
 22:14:40 up 1 min,  1 user,  load average: 0.19, 0.12, 0.04
CPU threads: 4


*** LIFE CYCLE STATUS ***
Operating System is the current Debian stable version codenamed 'trixie'!

*** TIME AND TIMEZONES ***
               Local time: Wed 2025-11-19 22:14:40 CET
           Universal time: Wed 2025-11-19 21:14:40 UTC
                 RTC time: Wed 2025-11-19 21:14:40
                Time zone: Europe/Berlin (CET, +0100)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

*** Users and Groups ***
User that called 'iob diag':
dennis
HOME=/home/dennis
GROUPS=dennis adm dialout cdrom floppy sudo audio dip video plugdev users netdev iobroker

User that is running 'js-controller':
iobroker
HOME=/home/iobroker
SUDO_HOME=/home/dennis
GROUPS=iobroker tty dialout audio video plugdev

*** DISPLAY-SERVER SETUP ***
Display-Server:         false
Unit display-manager.service could not be found.
Display-Manager:
Desktop:
Session:                tty

System is booting into 'graphical.target'. Usually a server is running in 'multi-user.target'. Please set BootTarget to 'multi-user.target' or run 'iobroker fix'

*** MEMORY ***
               total        used        free      shared  buff/cache   available
Mem:            8.3G        737M        7.5G        933K        286M        7.6G
Swap:           1.8G          0B        1.8G
Total:           10G        737M        9.4G

Active iob-Instances:   4

         7947 M total memory
          703 M used memory
          524 M active memory
           67 M inactive memory
         7197 M free memory
           24 M buffer memory
          248 M swap cache
         1721 M total swap
            0 M used swap
         1721 M free swap

*** top - Table Of Processes  ***
top - 22:14:40 up 1 min,  1 user,  load average: 0.19, 0.12, 0.04
Tasks: 140 total,   1 running, 139 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.0 us,  2.3 sy,  0.0 ni, 97.7 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
MiB Mem :   7947.3 total,   7197.2 free,    703.2 used,    273.5 buff/cache
MiB Swap:   1722.0 total,   1722.0 free,      0.0 used.   7244.0 avail Mem

*** FAILED SERVICES ***

  UNIT LOAD ACTIVE SUB DESCRIPTION

0 loaded units listed.


*** DMESG CRITICAL ERRORS ***
No critical errors detected

*** FILESYSTEM ***
Filesystem     Type      Size  Used Avail Use% Mounted on
udev           devtmpfs  3.9G     0  3.9G   0% /dev
tmpfs          tmpfs     795M  532K  795M   1% /run
/dev/sda1      ext4       30G  2.7G   26G  10% /
tmpfs          tmpfs     3.9G     0  3.9G   0% /dev/shm
tmpfs          tmpfs     5.0M     0  5.0M   0% /run/lock
tmpfs          tmpfs     1.0M     0  1.0M   0% /run/credentials/systemd-journald.service
tmpfs          tmpfs     3.9G  412K  3.9G   1% /tmp
tmpfs          tmpfs     1.0M     0  1.0M   0% /run/credentials/getty@tty1.service
tmpfs          tmpfs     795M  8.0K  795M   1% /run/user/1000

Messages concerning ext4 filesystem in dmesg:
[Wed Nov 19 22:12:49 2025] EXT4-fs (sda1): orphan cleanup on readonly fs
[Wed Nov 19 22:12:49 2025] EXT4-fs (sda1): mounted filesystem c05e89b3-8b22-491f-9297-88ed2de1a924 ro with ordered data mode. Quota mode: none.
[Wed Nov 19 22:12:50 2025] EXT4-fs (sda1): re-mounted c05e89b3-8b22-491f-9297-88ed2de1a924 r/w.

Show mounted filesystems:
TARGET SOURCE    FSTYPE OPTIONS
/      /dev/sda1 ext4   rw,relatime,errors=remount-ro

Files in neuralgic directories:

/var:
541M    /var/
286M    /var/cache
278M    /var/cache/apt
187M    /var/cache/apt/archives
185M    /var/lib

Archived and active journals take up 56M in the file system.

/opt/iobroker/backups:
4.0K    /opt/iobroker/backups/

/opt/iobroker/iobroker-data:
69M     /opt/iobroker/iobroker-data/
63M     /opt/iobroker/iobroker-data/files
47M     /opt/iobroker/iobroker-data/files/admin.admin
46M     /opt/iobroker/iobroker-data/files/admin.admin/custom/assets
46M     /opt/iobroker/iobroker-data/files/admin.admin/custom

The five largest files in iobroker-data are:
8.1M    /opt/iobroker/iobroker-data/files/backitup.admin/assets/index-C_W7K-9p.js
5.7M    /opt/iobroker/iobroker-data/objects.jsonl
3.7M    /opt/iobroker/iobroker-data/files/backitup.admin/custom/assets/index-ConOsPbp.js
3.7M    /opt/iobroker/iobroker-data/files/admin.admin/custom/assets/index-ZPb95xPG.js
3.7M    /opt/iobroker/iobroker-data/files/admin.admin/custom/assets/index-IIKn7Ixx.js

USB-Devices by-id:
USB-Sticks -  Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id':

No Devices found 'by-id'

Zigbee Network Settings on your coordinator/in nvbackup are:

zigbee.X
Extended Pan ID:
*** MASKED ***
Pan ID:
*** MASKED ***
Channel:
*** MASKED ***
Network Key:
*** MASKED ***

To unmask the settings run 'iob diag --unmask'


*** NodeJS-Installation ***

/usr/bin/nodejs         v22.21.0
/usr/bin/node           v22.21.0
/usr/bin/npm            10.9.4
/usr/bin/npx            10.9.4
/usr/bin/corepack       0.34.0

nodejs:
  Installed: 22.21.0-1nodesource1
  Candidate: 22.21.0-1nodesource1
  Version table:
 *** 22.21.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
        100 /var/lib/dpkg/status
     22.20.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.19.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.18.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.17.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.17.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.16.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.15.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.15.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.14.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.13.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.13.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.12.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.11.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.10.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.9.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.8.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.7.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.6.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.5.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.5.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.4.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.4.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.3.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.2.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.1.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.0.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     20.19.2+dfsg-1 500
        500 http://deb.debian.org/debian trixie/main amd64 Packages

Temp directories causing deletion problem: 0
No problems detected

Errors in npm tree: 0
No problems detected

Checking for nodejs vulnerability:


 █████  ██      ██           ██████   ██████   ██████  ██████         ██
██   ██ ██      ██          ██       ██    ██ ██    ██ ██   ██     ██  ██
███████ ██      ██          ██   ███ ██    ██ ██    ██ ██   ██         ██
██   ██ ██      ██          ██    ██ ██    ██ ██    ██ ██   ██     ██  ██
██   ██ ███████ ███████      ██████   ██████   ██████  ██████         ██



*** ioBroker-Installation ***

ioBroker Status
iobroker is running on this host.


Objects type: jsonl
States  type: jsonl

Hosts:
ioBroker2025        ioBroker2025 (version: 7.0.7, hostname: ioBroker2025  , alive, uptime: 106)

Core adapters versions
js-controller:  7.0.7
admin:          7.7.19
javascript:     "javascript" not found

nodejs modules from github:     0

Adapter State
+ system.adapter.admin.0                  : admin                 : ioBroker2025                             -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
+ system.adapter.backitup.0               : backitup              : ioBroker2025                             -  enabled
+ system.adapter.discovery.0              : discovery             : ioBroker2025                             -  enabled

+ instance is alive

Enabled adapters with bindings
+ system.adapter.admin.0                  : admin                 : ioBroker2025                             -  enabled, port: 8081, bind: 0.0.0.0, run as: admin

ioBroker-Repositories
┌─────────┬──────────┬─────────────────────────────────────────────────────────┬──────────────┐
│ (index) │ name     │ url                                                     │ auto upgrade │
├─────────┼──────────┼─────────────────────────────────────────────────────────┼──────────────┤
│ 0       │ 'stable' │ 'http://download.iobroker.net/sources-dist.json'        │ false        │
│ 1       │ 'beta'   │ 'http://download.iobroker.net/sources-dist-latest.json' │ false        │
└─────────┴──────────┴─────────────────────────────────────────────────────────┴──────────────┘

Active repo(s): stable
Upgrade policy: none

Installed ioBroker-Adapters
Used repository: stable
Adapter    "admin"        : 7.7.19   , installed 7.7.19
Adapter    "backitup"     : 3.3.10   , installed 3.3.10
Adapter    "discovery"    : 5.0.0    , installed 5.0.0
Controller "js-controller": 7.0.7    , installed 7.0.7

Objects and States
Please stand by - This may take a while
Objects:        149
States:         105

*** OS-Repositories and Updates ***
W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details
Hit:1 http://deb.debian.org/debian trixie InRelease
Hit:2 http://deb.debian.org/debian trixie-updates InRelease
Hit:3 http://security.debian.org/debian-security trixie-security InRelease
Hit:4 https://deb.nodesource.com/node_22.x nodistro InRelease
Reading package lists...
W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details
Pending Updates: 0

*** Listening Ports ***
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          5111       694/sshd: /usr/sbin
tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN      0          4180       1/init
tcp        0      0 127.0.0.1:9001          0.0.0.0:*               LISTEN      1001       8203       683/iobroker.js-con
tcp        0      0 127.0.0.1:9000          0.0.0.0:*               LISTEN      1001       8209       683/iobroker.js-con
tcp6       0      0 :::22                   :::*                    LISTEN      0          5113       694/sshd: /usr/sbin
tcp6       0      0 :::111                  :::*                    LISTEN      0          3188       1/init
tcp6       0      0 :::8081                 :::*                    LISTEN      1001       6819       850/io.admin.0
udp        0      0 192.168.178.120:68      0.0.0.0:*                           0          6785       823/dhcpcd: [BOOTP
udp        0      0 0.0.0.0:111             0.0.0.0:*                           0          270        1/init
udp6       0      0 :::111                  :::*                                0          4181       1/init
udp6       0      0 2a01:41e1:2654:600::546 :::*                                0          6747       778/dhcpcd: [DHCP6
udp6       0      0 2a01:41e1:2654:600::546 :::*                                0          7387       761/dhcpcd: [DHCP6
udp6       0      0 fe80::82fa:60d3:250:546 :::*                                0          8212       736/dhcpcd: [DHCP6

*** Log File - Last 25 Lines ***

2025-11-19 22:12:55.604  - error: host.ioBroker2025 instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2025-11-19 22:12:55.605  - info: host.ioBroker2025 Restart adapter system.adapter.admin.0 because enabled
2025-11-19 22:12:57.540  - info: host.ioBroker2025 instance system.adapter.backitup.0 in version "3.3.10" started with pid 767
2025-11-19 22:12:58.101  - error: backitup.0 (767) backitup.0 already running
2025-11-19 22:12:58.102  - warn: backitup.0 (767) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2025-11-19 22:12:58.616  - error: host.ioBroker2025 instance system.adapter.backitup.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2025-11-19 22:12:58.616  - info: host.ioBroker2025 Restart adapter system.adapter.backitup.0 because enabled
2025-11-19 22:13:01.536  - info: host.ioBroker2025 instance system.adapter.discovery.0 in version "5.0.0" started with pid 824
2025-11-19 22:13:02.067  - error: discovery.0 (824) discovery.0 already running
2025-11-19 22:13:02.067  - warn: discovery.0 (824) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2025-11-19 22:13:02.580  - error: host.ioBroker2025 instance system.adapter.discovery.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2025-11-19 22:13:02.580  - info: host.ioBroker2025 Restart adapter system.adapter.discovery.0 because enabled
2025-11-19 22:13:25.736  - info: host.ioBroker2025 instance system.adapter.admin.0 in version "7.7.19" started with pid 850
2025-11-19 22:13:26.730  - info: admin.0 (850) starting. Version 7.7.19 in /opt/iobroker/node_modules/iobroker.admin, node: v22.21.0, js-controller: 7.0.7
2025-11-19 22:13:26.752  - info: admin.0 (850) requesting all objects
2025-11-19 22:13:26.971  - info: admin.0 (850) received all objects
2025-11-19 22:13:27.089  - info: admin.0 (850) socket.io server listening on port 8081
2025-11-19 22:13:27.090  - info: admin.0 (850) http server listening on port 8081
2025-11-19 22:13:27.090  - info: admin.0 (850) Use link "http://127.0.0.1:8081" to configure.
2025-11-19 22:13:28.722  - info: host.ioBroker2025 instance system.adapter.backitup.0 in version "3.3.10" started with pid 896
2025-11-19 22:13:29.319  - info: backitup.0 (896) starting. Version 3.3.10 in /opt/iobroker/node_modules/iobroker.backitup, node: v22.21.0, js-controller: 7.0.7
2025-11-19 22:13:29.344  - info: backitup.0 (896) [iobroker] backup will be activated at 02:48 every 1 day(s)
2025-11-19 22:13:30.812  - info: admin.0 (850) ==> Connected system.user.admin from ::ffff:192.168.178.85
2025-11-19 22:13:32.689  - info: host.ioBroker2025 instance system.adapter.discovery.0 in version "5.0.0" started with pid 932
2025-11-19 22:13:33.258  - info: discovery.0 (932) starting. Version 5.0.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v22.21.0, js-controller: 7.0.7

============ Mark until here for C&P =============

[Thomas Braun]

@DennisMenger sagte in Neuinstallation ioBroker nach Script - Userrechte:

System is booting into 'graphical.target'. Usually a server is running in 'multi-user.target'. Please set BootTarget to 'multi-user.target' or run 'iobroker fix'

sudo systemctl set-default multi-user.target

Ansonsten schaut das gut aus.

[DennisMenger]

@Thomas-Braun Super, vielen Dank für die Unterstützung.

@Homoran dir auch vielen Dank

Schönen Abend noch

[Thomas Braun]

@DennisMenger

Das ganze hätte auch direkt funktioniert, wenn du den 'dennis' nicht nachträglich angelegt hättest sondern direkt schon im Debian-Installer (ohne Passwort für den root).
Dann fügt dich das ioBroker-Installationsskript nämlich gleich zu den passenden Gruppen hinzu.

[DennisMenger]

@Thomas-Braun Den User hatte ich direkt bei der Debian Installation mit hinzugefügt. Aber ich hatte ein Passwort für den root vergeben, was dann ja wahrscheinlich die Probleme verursacht hat.

[Homoran]

@DennisMenger sagte in Neuinstallation ioBroker nach Script - Userrechte:

Aber ich hatte ein Passwort für den root vergeben, was dann ja wahrscheinlich die Probleme verursacht hat.

dann bekommt der angelegte User keine sudo-Rechte!
Die hättest du dann selber vergeben müssen.

Deshalb dem root kein Passwort geben u d alles ist fine.

[DennisMenger]

Ok, das habe ich dann wahrscheinlich nicht aufmerksam genug gelesen.