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

[LastActionHero]

@thomas-braun und ich dachte schon, ich sei fertig...

*** iob diag is starting up, please wait ***
iob diag needs to be updated. Please execute 'iobroker fix' first.
ioadmin@iobroker:~$ iobroker fix

Your system is booting into 'graphical.target', which means that a user interface or desktop is available. Usually a server is running without a desktop to have more RAM available. Do you want to switch to 'multi-user.target'? (y/N)
library: loaded
Library version=2024-10-22
ioBroker or some processes are still running:
119 iobroker.js-con
311 io.admin.0
352 io.javascript.0
378 io.scenes.0
393 io.history.0
408 io.telegram.0
423 io.hue.0
438 io.hm-rpc.0
468 io.hm-rega.0
483 io.hm-rpc.1
498 io.sonos.0
530 io.mqtt.0
545 io.tr-064.0
583 io.discovery.0
598 io.web.0
616 io.lovelace.0
640 io.trashschedul
708 io.yahka.0
723 io.smartgarden.
Please stop them first and try again!
ioadmin@iobroker:~$ 

[Thomas Braun]

@lastactionhero sagte in Wir Empfehlen: Node.js 20.x :-):

Please stop them first and try again!

iob stop
iob fix
iob start
iob diag

[LastActionHero]

@thomas-braun

========== Start marking the full check here ===========

```bash
Script v.2024-10-19

*** BASE SYSTEM ***
   Static hostname: iobroker
         Icon name: computer-container
           Chassis: container
    Virtualization: lxc
  Operating System: Debian GNU/Linux 11 (bullseye)
            Kernel: Linux 6.8.12-1-pve
      Architecture: x86-64
OS is similar to: 

model name      : Intel(R) Celeron(R) J4105 CPU @ 1.50GHz
Docker          : false
Virtualization  : lxc
Kernel          : x86_64
Userland        : 64 bit

Systemuptime and Load:
 21:17:03 up 16 min,  2 users,  load average: 1.52, 0.86, 0.59
CPU threads: 2


*** LIFE CYCLE STATUS ***
Unknown release codenamed ''. Please check yourself if the Operating System is actively maintained.

*** TIME AND TIMEZONES ***
               Local time: Tue 2024-12-03 21:17:03 CET
           Universal time: Tue 2024-12-03 20:17:03 UTC
                 RTC time: n/a
                Time zone: Europe/Berlin (CET, +0100)
System clock synchronized: yes
              NTP service: inactive
          RTC in local TZ: no

*** Users and Groups ***
User that called 'iob diag':
ioadmin
HOME=/home/ioadmin
GROUPS=ioadmin adm sudo iobroker

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

*** DISPLAY-SERVER SETUP ***
Display-Server: false
Desktop: 
Terminal:       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:            3.1G        1.3G        1.3G        0.0K        447M        1.8G
Swap:           1.0G          0B        1.0G
Total:          4.1G        1.3G        2.4G

Active iob-Instances:   5

         3072 M total memory
         1294 M used memory
         1274 M active memory
          319 M inactive memory
         1330 M free memory
            0 M buffer memory
          447 M swap cache
         1024 M total swap
            0 M used swap
         1024 M free swap

*** top - Table Of Processes  ***
top - 21:17:04 up 16 min,  2 users,  load average: 1.52, 0.86, 0.59
Tasks:  46 total,   1 running,  45 sleeping,   0 stopped,   0 zombie
%Cpu(s): 75.0 us,  9.4 sy,  0.0 ni, 15.6 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
MiB Mem :   3072.0 total,   1335.6 free,   1288.7 used,    447.7 buff/cache
MiB Swap:   1024.0 total,   1024.0 free,      0.0 used.   1783.1 avail Mem 

*** FAILED SERVICES ***

  UNIT                          LOAD   ACTIVE SUB    DESCRIPTION
* run-rpc_pipefs.mount          loaded failed failed RPC Pipe File System
* sys-kernel-config.mount       loaded failed failed Kernel Configuration File System
* systemd-journald-audit.socket loaded failed failed Journal Audit Socket

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
3 loaded units listed.


*** DMESG CRITICAL ERRORS ***
dmesg: read kernel buffer failed: Operation not permitted
No critical errors detected

*** FILESYSTEM ***
Filesystem                       Type      Size  Used Avail Use% Mounted on
/dev/mapper/pve-vm--102--disk--0 ext4      9.8G  5.9G  3.5G  64% /
none                             tmpfs     492K  4.0K  488K   1% /dev
udev                             devtmpfs  3.8G     0  3.8G   0% /dev/tty
tmpfs                            tmpfs     3.8G     0  3.8G   0% /dev/shm
tmpfs                            tmpfs     1.6G  116K  1.6G   1% /run
tmpfs                            tmpfs     5.0M     0  5.0M   0% /run/lock
tmpfs                            tmpfs     772M     0  772M   0% /run/user/1001

Messages concerning ext4 filesystem in dmesg:
dmesg: read kernel buffer failed: Operation not permitted

Show mounted filesystems:
TARGET SOURCE                           FSTYPE OPTIONS
/      /dev/mapper/pve-vm--102--disk--0 ext4   rw,relatime,stripe=16

Files in neuralgic directories:

/var:
896M    /var/
518M    /var/cache
513M    /var/cache/apt
446M    /var/cache/apt/archives
242M    /var/log

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

/opt/iobroker/backups:
64M     /opt/iobroker/backups/
4.0K    /opt/iobroker/backups/redistmp

/opt/iobroker/iobroker-data:
989M    /opt/iobroker/iobroker-data/
808M    /opt/iobroker/iobroker-data/files
617M    /opt/iobroker/iobroker-data/files/javascript.admin
560M    /opt/iobroker/iobroker-data/files/javascript.admin/static
558M    /opt/iobroker/iobroker-data/files/javascript.admin/static/js

The five largest files in iobroker-data are:
24M     /opt/iobroker/iobroker-data/files/web.admin/static/js/main.135279a0.js.map
24M     /opt/iobroker/iobroker-data/files/scenes.admin/static/js/main.c9369f6c.js.map
24M     /opt/iobroker/iobroker-data/files/modbus.admin/static/js/main.6a71b34c.js.map
15M     /opt/iobroker/iobroker-data/objects.jsonl
12M     /opt/iobroker/iobroker-data/files/backitup.admin/static/js/main.bd24114f.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'

*** NodeJS-Installation ***

/usr/bin/nodejs         v20.18.1
/usr/bin/node           v20.18.1
/usr/bin/npm            10.8.2
/usr/bin/npx            10.8.2
/usr/bin/corepack       0.29.4

nodejs:
  Installed: 20.18.1-1nodesource1
  Candidate: 20.18.1-1nodesource1
  Version table:
 *** 20.18.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
        100 /var/lib/dpkg/status
     20.18.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.17.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.16.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.15.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.15.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.14.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.13.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.13.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.12.2-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.12.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.12.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.11.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.11.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.10.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.9.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.8.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.8.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.7.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.6.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.6.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.5.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.5.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.4.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.3.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.3.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.2.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.1.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.0.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     12.22.12~dfsg-1~deb11u5 500
        500 http://security.debian.org bullseye-security/main amd64 Packages
     12.22.12~dfsg-1~deb11u4 500
        500 http://deb.debian.org/debian bullseye/main amd64 Packages

Temp directories causing deletion problem: 0
No problems detected

Errors in npm tree: 0
No problems detected

*** ioBroker-Installation ***

ioBroker Status
iobroker is running on this host.


Objects type: jsonl
States  type: jsonl

Hosts:
iobroker            iobroker (version: 7.0.3, hostname: iobroker      , alive, uptime: 77)

Core adapters versions
js-controller:  7.0.3
admin:          7.1.5
javascript:     8.8.3

nodejs modules from github:     0

Adapter State
+ system.adapter.admin.0                  : admin                 : iobroker                                 -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
  system.adapter.alias-manager.0          : alias-manager         : iobroker                                 -  enabled
  system.adapter.backitup.0               : backitup              : iobroker                                 - disabled
  system.adapter.discovery.0              : discovery             : iobroker                                 -  enabled
+ system.adapter.history.0                : history               : iobroker                                 -  enabled
  system.adapter.hm-rega.0                : hm-rega               : iobroker                                 -  enabled
  system.adapter.hm-rpc.0                 : hm-rpc                : iobroker                                 -  enabled, port: 0
  system.adapter.hm-rpc.1                 : hm-rpc                : iobroker                                 -  enabled, port: 0
  system.adapter.hue.0                    : hue                   : iobroker                                 -  enabled, port: 443
  system.adapter.ical.0                   : ical                  : iobroker                                 -  enabled
+ system.adapter.javascript.0             : javascript            : iobroker                                 -  enabled
  system.adapter.lovelace.0               : lovelace              : iobroker                                 -  enabled, port: 8091, bind: 0.0.0.0, run as: admin
  system.adapter.modbus.0                 : modbus                : iobroker                                 - disabled
  system.adapter.mqtt.0                   : mqtt                  : iobroker                                 -  enabled, port: 1883, bind: 0.0.0.0
+ system.adapter.scenes.0                 : scenes                : iobroker                                 -  enabled
  system.adapter.smartgarden.0            : smartgarden           : iobroker                                 -  enabled
  system.adapter.sonos.0                  : sonos                 : iobroker                                 -  enabled
  system.adapter.telegram.0               : telegram              : iobroker                                 -  enabled, port: 8443, bind: 0.0.0.0
  system.adapter.tr-064.0                 : tr-064                : iobroker                                 -  enabled
  system.adapter.trashschedule.0          : trashschedule         : iobroker                                 -  enabled
  system.adapter.vis.0                    : vis                   : iobroker                                 -  enabled
  system.adapter.weatherunderground.0     : weatherunderground    : iobroker                                 -  enabled
  system.adapter.web.0                    : web                   : iobroker                                 -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
  system.adapter.yahka.0                  : yahka                 : iobroker                                 -  enabled

+ instance is alive

Enabled adapters with bindings
+ system.adapter.admin.0                  : admin                 : iobroker                                 -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
  system.adapter.hm-rpc.0                 : hm-rpc                : iobroker                                 -  enabled, port: 0
  system.adapter.hm-rpc.1                 : hm-rpc                : iobroker                                 -  enabled, port: 0
  system.adapter.hue.0                    : hue                   : iobroker                                 -  enabled, port: 443
  system.adapter.lovelace.0               : lovelace              : iobroker                                 -  enabled, port: 8091, bind: 0.0.0.0, run as: admin
  system.adapter.mqtt.0                   : mqtt                  : iobroker                                 -  enabled, port: 1883, bind: 0.0.0.0
  system.adapter.telegram.0               : telegram              : iobroker                                 -  enabled, port: 8443, bind: 0.0.0.0
  system.adapter.web.0                    : web                   : iobroker                                 -  enabled, port: 8082, 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-Instances
Used repository: stable
Adapter    "admin"        : 7.1.5    , installed 7.1.5
Adapter    "alias-manager": 2.0.0    , installed 2.0.0
Adapter    "backitup"     : 3.0.25   , installed 3.0.25
Adapter    "discovery"    : 5.0.0    , installed 5.0.0
Adapter    "history"      : 3.0.1    , installed 3.0.1
Adapter    "hm-rega"      : 5.1.0    , installed 5.1.0
Adapter    "hm-rpc"       : 2.0.2    , installed 2.0.2
Adapter    "hue"          : 3.13.1   , installed 3.13.1
Adapter    "ical"         : 1.16.1   , installed 1.16.1
Adapter    "javascript"   : 8.8.3    , installed 8.8.3
Controller "js-controller": 7.0.3    , installed 7.0.3
Adapter    "lovelace"     : 4.1.10   , installed 4.1.10
Adapter    "modbus"       : 6.3.2    , installed 6.3.2
Adapter    "mqtt"         : 6.1.2    , installed 6.1.2
Adapter    "scenes"       : 3.2.3    , installed 3.2.3
Adapter    "simple-api"   : 2.8.0    , installed 2.8.0
Adapter    "smartgarden"  : 2.0.1    , installed 2.0.1
Adapter    "socketio"     : 6.7.1    , installed 6.7.1
Adapter    "sonos"        : 3.0.0    , installed 3.0.0
Adapter    "telegram"     : 3.9.0    , installed 3.9.0
Adapter    "tr-064"       : 4.3.0    , installed 4.3.0
Adapter    "trashschedule": 3.3.0    , installed 3.3.0
Adapter    "vis"          : 1.5.6    , installed 1.5.6
Adapter    "weatherunderground": 3.7.0, installed 3.7.0
Adapter    "web"          : 6.2.5    , installed 6.2.5
Adapter    "ws"           : 2.6.2    , installed 2.6.2
Adapter    "yahka"        : 1.0.3    , installed 1.0.3

Objects and States
Please stand by - This may take a while
Objects:        7327
States:         5987

*** OS-Repositories and Updates ***
Hit:1 http://deb.debian.org/debian bullseye InRelease
Hit:2 http://deb.debian.org/debian bullseye-updates InRelease
Hit:3 http://security.debian.org bullseye-security InRelease
Hit:4 https://deb.nodesource.com/node_20.x nodistro InRelease
Reading package lists...
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:111             0.0.0.0:*               LISTEN      0          119584219  1/init              
tcp        0      0 127.0.0.1:9000          0.0.0.0:*               LISTEN      1000       119618342  2467/iobroker.js-co 
tcp        0      0 127.0.0.1:9001          0.0.0.0:*               LISTEN      1000       119618337  2467/iobroker.js-co 
tcp        0      0 0.0.0.0:1883            0.0.0.0:*               LISTEN      1000       119619961  2798/io.mqtt.0      
tcp        0      0 0.0.0.0:5355            0.0.0.0:*               LISTEN      104        119584462  107/systemd-resolve 
tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN      0          119585851  292/master          
tcp        0      0 192.168.5.152:2010      0.0.0.0:*               LISTEN      1000       119619867  2753/io.hm-rpc.1    
tcp        0      0 192.168.5.152:2001      0.0.0.0:*               LISTEN      1000       119621983  2708/io.hm-rpc.0    
tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      104        119584468  107/systemd-resolve 
tcp6       0      0 :::22                   :::*                    LISTEN      0          119584381  1/init              
tcp6       0      0 :::111                  :::*                    LISTEN      0          119584221  1/init              
tcp6       0      0 :::5355                 :::*                    LISTEN      104        119584465  107/systemd-resolve 
tcp6       0      0 :::33895                :::*                    LISTEN      1000       119623804  3100/io.yahka.0     
tcp6       0      0 ::1:25                  :::*                    LISTEN      0          119585852  292/master          
tcp6       0      0 :::8082                 :::*                    LISTEN      1000       119622413  2843/io.web.0       
tcp6       0      0 :::8081                 :::*                    LISTEN      1000       119618409  2485/io.admin.0     
tcp6       0      0 :::8091                 :::*                    LISTEN      1000       119622449  2858/io.lovelace.0  
tcp6       0      0 :::3500                 :::*                    LISTEN      1000       119622086  2768/io.sonos.0     
udp        0      0 127.0.0.53:53           0.0.0.0:*                           104        119584467  107/systemd-resolve 
udp        0      0 0.0.0.0:111             0.0.0.0:*                           0          119584220  1/init              
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           1000       119623805  3100/io.yahka.0     
udp        0      0 0.0.0.0:5355            0.0.0.0:*                           104        119584461  107/systemd-resolve 
udp6       0      0 :::111                  :::*                                0          119584222  1/init              
udp6       0      0 :::5355                 :::*                                104        119584464  107/systemd-resolve 

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

2024-12-03 21:16:54.868  - info: mqtt.0 (2798) Client [Zisterne_2_1B6875] publishOnSubscribe send all known states
2024-12-03 21:16:54.871  - info: mqtt.0 (2798) Client [Zisterne_2_1B6875] publishOnSubscribe send all known states
2024-12-03 21:16:54.871  - info: mqtt.0 (2798) Client [Zisterne_2_1B6875] publishOnSubscribe send all known states
2024-12-03 21:16:55.717  - info: web.0 (2843) starting. Version 6.2.5 in /opt/iobroker/node_modules/iobroker.web, node: v20.18.1, js-controller: 7.0.3
2024-12-03 21:16:55.836  - info: web.0 (2843) socket.io server listening on port 8082
2024-12-03 21:16:55.840  - info: web.0 (2843) http server listening on port 8082
2024-12-03 21:16:58.174  - info: host.iobroker instance system.adapter.lovelace.0 in version "4.1.10" started with pid 2858
2024-12-03 21:17:00.157  - info: lovelace.0 (2858) starting. Version 4.1.10 in /opt/iobroker/node_modules/iobroker.lovelace, node: v20.18.1, js-controller: 7.0.3
2024-12-03 21:17:00.203  - info: lovelace.0 (2858) http server listening on port 8091
2024-12-03 21:17:02.203  - info: host.iobroker instance system.adapter.trashschedule.0 in version "3.3.0" started with pid 2873
2024-12-03 21:17:03.637  - info: trashschedule.0 (2873) starting. Version 3.3.0 in /opt/iobroker/node_modules/iobroker.trashschedule, node: v20.18.1, js-controller: 7.0.3
2024-12-03 21:17:03.838  - info: trashschedule.0 (2873) [onReady] starting with source "ical" -> ical
2024-12-03 21:17:03.845  - info: trashschedule.0 (2873) [ical] configured ical preview is 45 days (until 17.01.2025) - increase this value to find more events in the future
2024-12-03 21:17:03.846  - info: trashschedule.0 (2873) [ical] found configured ical event "Vacation" without "display" flag. Activate the display flag on this entry if this is a relevant "trash event".
2024-12-03 21:17:07.700  - info: vis.0 (3071) starting. Version 1.5.6 in /opt/iobroker/node_modules/iobroker.vis, node: v20.18.1, js-controller: 7.0.3
2024-12-03 21:17:08.325  - info: vis.0 (3071) Terminated (NO_ERROR): Without reason
2024-12-03 21:17:08.882  - info: host.iobroker instance system.adapter.vis.0 terminated while should be started once
2024-12-03 21:17:10.144  - info: host.iobroker instance system.adapter.yahka.0 in version "1.0.3" started with pid 3100
2024-12-03 21:17:12.024  - info: yahka.0 (3100) starting. Version 1.0.3 in /opt/iobroker/node_modules/iobroker.yahka, node: v20.18.1, js-controller: 7.0.3
2024-12-03 21:17:12.039  - info: yahka.0 (3100) adapter ready, checking config
2024-12-03 21:17:12.048  - info: yahka.0 (3100) adding Weihnachtsbaum with UUID: 5e60d7d4-355c-4836-8517-c5a84ea95a56
2024-12-03 21:17:12.053  - info: yahka.0 (3100) adding Garagentor with UUID: eb975574-a3b2-4c0a-9953-c3aa23b9d845
2024-12-03 21:17:12.057  - info: yahka.0 (3100) publishing bridge ioBroker Bridge on 0.0.0.0 using avahi
2024-12-03 21:17:14.220  - info: host.iobroker instance system.adapter.smartgarden.0 in version "2.0.1" started with pid 3144
2024-12-03 21:17:15.960  - info: smartgarden.0 (3144) starting. Version 2.0.1 in /opt/iobroker/node_modules/iobroker.smartgarden, node: v20.18.1, js-controller: 7.0.3

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

[Thomas Braun]

@lastactionhero sagte in Wir Empfehlen: Node.js 20.x :-):

Debian GNU/Linux 11 (bullseye)

Kannste direkt schon mal auf 12 (bookworm) bringen. Debian 11 ist EndOfLife und wird nicht mehr aktiv unterstützt.

System is booting into 'graphical.target'.

Stell das wie vom Fixer angeboten auf multi-user um.

[Alexander Hauser]

@feuersturm super dankeschön. hat ganz easy ohne Problem funktioniert.

[shellyrulestheworld]

bei mir kommt leider ne Fehlermeldung:

Hat jemand eine Idee, wie ich auf nodejs 20 komme?

[Thomas Braun]

@shellyrulestheworld sagte in Wir Empfehlen: Node.js 20.x :-):

bei mir kommt leider ne Fehlermeldung

Text aus einem Terminal immer auch als Text in CodeTags eingebettet posten, nicht als Screenshot.

[shellyrulestheworld]

@thomas-braun OK, immerhin kein Handy Foto 😜
Nächstes Mal kommt wieder Code 😃

[Thomas Braun]

@shellyrulestheworld sagte in Wir Empfehlen: Node.js 20.x :-):

Nächstes Mal kommt wieder Code

Dann kann ich ja beim nächsten Mal antworten.

[shellyrulestheworld]

@thomas-braun das Angebot nehme ich an. Irgendwie scheint es jetzt geklappt zu haben, oder?

ioBroker nodejs fixer 2024-10-10
You requested to install latest version from nodejs v20 tree.

Your current setup is:
/usr/bin/nodejs         v18.20.6
/usr/bin/node           v18.20.6
/usr/bin/npm            10.8.2
/usr/bin/npx            10.8.2
/usr/bin/corepack       0.29.4

We found these nodejs versions available for installation:

nodejs:
  Installed: 18.20.6-1nodesource1
  Candidate: 18.20.6-1nodesource1
  Version table:
 *** 18.20.6-1nodesource1 100
        100 /var/lib/dpkg/status
     18.19.0+dfsg-6~deb12u2 500
        500 http://deb.debian.org/debian bookworm/main amd64 Packages
     18.19.0+dfsg-6~deb12u1 500
        500 http://security.debian.org/debian-security bookworm-security/main amd64 Packages



Nothing to do - Your installation is using the correct paths.

You are running nodejs v18.20.6. Do you want to install latest version from nodejs v.20 tree? 

Press <y> to continue or any other key to quit
Trying to fix your installation now. Please be patient.
rm: cannot remove '/etc/apt/keyrings/nodesource.gpg 2> /dev/null': No such file or directory

Virtualization: lxc
Waiting for ioBroker to shut down - Give me a minute...
############################################################

Removing dfsg-nodejs


*** These repos are active on your system:
Hit:1 http://security.debian.org/debian-security bookworm-security InRelease
Hit:2 http://deb.debian.org/debian bookworm InRelease   
Hit:3 http://deb.debian.org/debian bookworm-updates InRelease
Hit:4 https://packagecloud.io/ookla/speedtest-cli/debian bookworm InRelease
Reading package lists... Done

*** Installing ca-certificates, curl and gnupg, just in case they are missing.

*** Creating new /etc/apt/sources.list.d/nodesource.list and pinning source

deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_20.x nodistro main
Package: nodejs
Pin: origin deb.nodesource.com
Pin-Priority: 1001

*** These repos are active after the adjustments:
Hit:1 http://deb.debian.org/debian bookworm InRelease
Hit:2 http://security.debian.org/debian-security bookworm-security InRelease
Hit:3 http://deb.debian.org/debian bookworm-updates InRelease                                                                                                
Get:4 https://deb.nodesource.com/node_20.x nodistro InRelease [12.1 kB]                                                                                      
Get:6 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages [10.4 kB]                                                     
Hit:5 https://packagecloud.io/ookla/speedtest-cli/debian bookworm InRelease
Fetched 22.5 kB in 1s (18.6 kB/s)
Reading package lists... Done

Installing nodejs now!

(Reading database ... 43850 files and directories currently installed.)
Preparing to unpack .../nodejs_20.18.2-1nodesource1_amd64.deb ...
Detected old npm client, removing...
Unpacking nodejs (20.18.2-1nodesource1) over (18.20.6-1nodesource1) ...
Setting up nodejs (20.18.2-1nodesource1) ...
Processing triggers for man-db (2.11.2-2) ...
Installing nodejs now!

*** You need to manually restart your container/virtual machine now! *** 

We tried our best to fix your nodejs. Please run 'iob diag' again to verify.
peter@iobroker:~$ 

[Thomas Braun]

@shellyrulestheworld sagte in Wir Empfehlen: Node.js 20.x :-):

Irgendwie scheint es jetzt geklappt zu haben, oder?

Vermutlich. Container neugestartet?
Dann nochmal

iob nodejs-update

Da sollte dann auch was passendes stehen.

[shellyrulestheworld]

@thomas-braun genau. Ich habe den Container neu gestartet. jetzt kommt folgdendes:

ioBroker nodejs fixer 2024-10-10

Recommended nodejs-version is: 20.18.2
Checking your installation now. Please be patient!

Your current setup is:
/usr/bin/nodejs         v20.18.2
/usr/bin/node           v20.18.2
/usr/bin/npm            10.8.2
/usr/bin/npx            10.8.2
/usr/bin/corepack       0.29.4

We found these nodejs versions available for installation:

nodejs:
  Installed: 20.18.2-1nodesource1
  Candidate: 20.18.2-1nodesource1
  Version table:
 *** 20.18.2-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
        100 /var/lib/dpkg/status
     20.18.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.18.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.17.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.16.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.15.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.15.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.14.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.13.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.13.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.12.2-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.12.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.12.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.11.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.11.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.10.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.9.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.8.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.8.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.7.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.6.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.6.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.5.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.5.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.4.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.3.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.3.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.2.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.1.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.0.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     18.19.0+dfsg-6~deb12u2 500
        500 http://deb.debian.org/debian bookworm/main amd64 Packages
     18.19.0+dfsg-6~deb12u1 500
        500 http://security.debian.org/debian-security bookworm-security/main amd64 Packages



Nothing to do - Your installation is using the correct paths.
Nothing to do - Your version is the recommended one.

***You can now keep your whole system up-to-date using the usual 'sudo apt update && sudo apt full-upgrade' commands. ***
*** DO NOT USE node version managers like 'nvm', 'n' and others in parallel. They will break your current installation! ***

 *** DO NOT use 'nodejs-update' as part of a regular update process! ***
peter@iobroker:~$ 

Komischerweise steht im IOB folgendes:

CPU: 14,58 %
RAM: 28 %
Betriebszeit: 0h
Verfügbar: 7.0.6
Installiert: 7.0.6
Ereignisse: ⇥40 / ↦13
Plattform: linux
Betriebssystem: linux
Architektur: x64
CPUs: 4
Geschwindigkeit: 2799 MHz
Modell: Intel(R) Celeron(R) N5105 @ 2.00GHz
RAM: 8 GB
System-Betriebszeit: 00:00:48
Node.js: v18.20.6
time: 1738393951080
timeOffset: -60
NPM: 10.8.2
Adapter-Anzahl: 559
Datenträgergröße: 13.7 GB
Freier Festplattenspeicher: 5.3 GB
Aktive Instanzen: 7
Pfad: /opt/iobroker/
Betriebszeit: 00:00:43

[Thomas Braun]

@shellyrulestheworld sagte in Wir Empfehlen: Node.js 20.x :-):

Nothing to do - Your installation is using the correct paths.
Nothing to do - Your version is the recommended one.

Alles richtig. ioBroker-GUI neuladen.

[shellyrulestheworld]

@thomas-braun perfekt. Wie immer: herzlichen Dank für deinen Support :-)

[Maddin77]

Servus zusammen

hoffe ich darf hier bissi Fragen
ich bin ziemlich neu in der Welt

und IOB möchte gerne das ich Node update, allerdings habe ich ziemlich keine Ahnung davon
bei mir läuft IOB auf einem Synology NAS als Container

soll ich im NAS Terminal updaten oder im IOB
was wäre zu bevorzugen?

danke schon mal für eure hilfe

[Thomas Braun]

@maddin77

Von welcher Version auf welche neue Version?

[Maddin77]

@thomas-braun sagte in Wir Empfehlen: Node.js 20.x :-):

@maddin77

Von welcher Version auf welche neue Version?

im Terminal wird mir das angezeigt
/opt/iobroker$ node -v

v18.20.3
/opt/iobroker$

manche Adapter schreiben einfach >20

[Thomas Braun]

@maddin77

Dann roll einen aktuellen Container drüber.

[Maddin77]

@thomas-braun sagte in Wir Empfehlen: Node.js 20.x :-):

@maddin77

Dann roll einen aktuellen Container drüber.

ist das dann mit

sudo apt-get install -y nodejs

[Thomas Braun]

@maddin77

Nein. Du nimmst das aktuelle Container-Image und tauschst die Umgebung für den ioBroker aus.