Diskussion zum HowTo nodejs-Installation und upgrade

Thomas Braun

@djsirius sagte in Diskussion zum HowTo nodejs-Installation und upgrade:

Das ist ja das Problem, ich kann keine Adapter installieren und auch keine Adapter updaten und keine Adapter löschen.

Per git url muss das gehen.

djsirius

@thomas-braun Leider nicht!

Thomas Braun

@djsirius sagte in Diskussion zum HowTo nodejs-Installation und upgrade:

Leider nicht!

Meldungen?

djsirius

@thomas-braun Es gibt keine Meldung, weil er beim Installieren immer stehen bleibt.

Homoran

ich tippe immer noch auf ipv6 Thematik bei npm

Thomas Braun

@djsirius sagte in Diskussion zum HowTo nodejs-Installation und upgrade:

In einer Konsole den Installationsbefehl per git url (genaue Syntax habe ich gerade nicht parat, kannste aber aus dem entsprechenden Admin-Fenster entnehmen) eingeben.

djsirius

@thomas-braun

Sorry, aber damit kenne ich mich überhaupt nicht aus.

Ich habe jetzt

iobroker url https://github.com/oweitman/ioBroker.openligadb --host debian --debug

Über git bekomme ich es nicht hin, weil ich den Befehl nicht kenne.

Ist und bleibt aber das selbe Problem.

Was gibt es denn da genau für ein Problem mit ipv6?

Vielen Dank!

djsirius

Moin,

ich habe jetzt aus lauter Verzweiflung Nodejs nochmal neu installiert. Auf meinem Master ist alles OK.

Auf meinem Slave bekomme ich immer eine Meldung, wenn ich den iob fix drüber laufen lasse.

    Database maintenance (4/5)
==========================================================================

Checking for uncompressed JSONL databases... This might take a while!

npm ERR! code ETIMEDOUT
npm ERR! syscall connect
npm ERR! errno ETIMEDOUT
npm ERR! network request to https://registry.npmjs.org/@iobroker%2fjsonltool failed, reason: connect ETIMEDOUT 2606:4700::6810:1a22:443
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'

npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-01-08T08_12_15_007Z-debug-0.log

iob diag:

Skript v.2023-10-10

*** BASE SYSTEM ***
   Static hostname: raspberrypi
         Icon name: computer
  Operating System: Debian GNU/Linux 11 (bullseye)
            Kernel: Linux 6.1.21-v8+
      Architecture: arm64

Model           : Raspberry Pi 3 Model B Rev 1.2
Docker          : false
Virtualization  : none
Kernel          : aarch64
Userland        : arm64

Systemuptime and Load:
 09:20:56 up 3 days, 22:17,  1 user,  load average: 0.25, 0.45, 0.80
CPU threads: 4


*** RASPBERRY THROTTLING ***
Current issues:
No throttling issues detected.

Previously detected issues:
No throttling issues detected.

*** Time and Time Zones ***
               Local time: Mon 2024-01-08 09:20:56 CET
           Universal time: Mon 2024-01-08 08:20:56 UTC
                 RTC time: n/a
                Time zone: Europe/Berlin (CET, +0100)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

*** User and Groups ***
pi
/home/pi
pi adm dialout cdrom sudo audio video plugdev games users input render netdev gpio i2c spi iobroker

*** X-Server-Setup ***
X-Server:       false
Desktop:
Terminal:       tty
Boot Target:    multi-user.target

*** MEMORY ***
               total        used        free      shared  buff/cache   available
Mem:            909M        212M        138M        0.0K        558M        632M
Swap:            99M         78M         21M
Total:          1.0G        290M        160M

          909 M total memory
          212 M used memory
          238 M active memory
          396 M inactive memory
          138 M free memory
           39 M buffer memory
          518 M swap cache
           99 M total swap
           78 M used swap
           21 M free swap

Raspberry only:
oom events: 0
lifetime oom required: 0 Mbytes
total time in oom handler: 0 ms
max time spent in oom handler: 0 ms

*** FAILED SERVICES ***

  UNIT             LOAD   ACTIVE SUB    DESCRIPTION
* iobroker.service loaded failed failed ioBroker Server

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.
1 loaded units listed.

*** FILESYSTEM ***
Filesystem     Type      Size  Used Avail Use% Mounted on
/dev/root      ext4       59G   32G   25G  56% /
devtmpfs       devtmpfs  325M     0  325M   0% /dev
tmpfs          tmpfs     455M     0  455M   0% /dev/shm
tmpfs          tmpfs     182M 1008K  181M   1% /run
tmpfs          tmpfs     5.0M  4.0K  5.0M   1% /run/lock
/dev/mmcblk0p1 vfat      255M   31M  225M  13% /boot
tmpfs          tmpfs      91M     0   91M   0% /run/user/1000
tmpfs          tmpfs      91M     0   91M   0% /run/user/0

Messages concerning ext4 filesystem in dmesg:
[Thu Jan  4 11:03:22 2024] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 video=Composite-1:720x480@60i vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  console=ttyS0,115200 console=tty1 root=PARTUUID=d3cf0315-02 rootfstype=ext4 fsck.repair=yes rootwait
[Thu Jan  4 11:03:25 2024] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none.
[Thu Jan  4 11:03:25 2024] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[Thu Jan  4 11:03:29 2024] EXT4-fs (mmcblk0p2): re-mounted. Quota mode: none.

Show mounted filesystems \(real ones only\):
TARGET  SOURCE         FSTYPE OPTIONS
/       /dev/mmcblk0p2 ext4   rw,noatime
`-/boot /dev/mmcblk0p1 vfat   rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro

Files in neuralgic directories:

/var:
27G     /var/
22G     /var/lib/mysql/iobroker
22G     /var/lib/mysql
22G     /var/lib
4.2G    /var/log

Archived and active journals take up 3.9G in the file system.

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

/opt/iobroker/iobroker-data:
18M     /opt/iobroker/iobroker-data/
14M     /opt/iobroker/iobroker-data/files
13M     /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js
13M     /opt/iobroker/iobroker-data/files/admin.admin/custom/static
13M     /opt/iobroker/iobroker-data/files/admin.admin/custom

The five largest files in iobroker-data are:
6.3M    /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_js-node_modules_iobr-99c23e.847b8ad9.chunk.js.map
3.0M    /opt/iobroker/iobroker-data/objects.jsonl
2.8M    /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_js-node_modules_iobr-99c23e.847b8ad9.chunk.js
1.6M    /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_mui_material_Accordion_index_js-node_modules_mui_material_AccordionDetai-57e02d.0886b730.chunk.js.map
652K    /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_mui_material_index_js.40e01f69.chunk.js.map

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

/dev/serial/by-id/usb-1a86_USB_Serial-if00-port0

*** NodeJS-Installation ***

/usr/bin/nodejs         v18.19.0
/usr/bin/node           v18.19.0
/usr/bin/npm            10.2.3
/usr/bin/npx            10.2.3
/usr/bin/corepack       0.22.0


nodejs:
  Installed: 18.19.0-1nodesource1
  Candidate: 18.19.0-1nodesource1
  Version table:
 *** 18.19.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
        100 /var/lib/dpkg/status
     18.18.2-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
     18.18.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
     18.18.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
     18.17.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
     18.17.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
     18.16.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
     18.16.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
     18.15.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
     18.14.2-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
     18.14.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
     18.14.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
     18.13.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
     18.12.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
     18.11.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
     18.10.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
     18.9.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
     18.9.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
     18.8.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
     18.7.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
     18.6.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
     18.5.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
     18.4.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
     18.3.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
     18.2.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
     18.1.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
     18.0.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
     12.22.12~dfsg-1~deb11u4 500
        500 http://deb.debian.org/debian bullseye/main arm64 Packages
        500 http://security.debian.org/debian-security bullseye-security/main arm64 Packages

Temp directories causing npm8 problem: 0
No problems detected

Errors in npm tree:

*** ioBroker-Installation ***

ioBroker Status
iobroker is not running on this host.

At least one iobroker host is running.

Objects type: jsonl
States  type: jsonl

Core adapters versions
js-controller:  4.0.24
admin:          6.12.0
javascript:     "javascript" not found

Adapters from github:   0

Adapter State
+ system.adapter.admin.0                  : admin                 : debian                                   -  enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin
+ system.adapter.alexa2.0                 : alexa2                : debian                                   -  enabled
+ system.adapter.backitup.0               : backitup              : debian                                   -  enabled
  system.adapter.daswetter.0              : daswetter             : debian                                   -  enabled
  system.adapter.devices.0                : devices               : debian                                   -  enabled
+ system.adapter.discovery.0              : discovery             : debian                                   -  enabled
  system.adapter.dwd.0                    : dwd                   : debian                                   -  enabled
  system.adapter.enigma2.0                : enigma2               : raspberrypi                              -  enabled
  system.adapter.feiertage.0              : feiertage             : debian                                   -  enabled
  system.adapter.flot.0                   : flot                  : debian                                   -  enabled
+ system.adapter.history.0                : history               : debian                                   -  enabled
+ system.adapter.hm-rega.0                : hm-rega               : debian                                   -  enabled
+ system.adapter.hm-rpc.0                 : hm-rpc                : debian                                   -  enabled, port: 0
+ system.adapter.hm-rpc.1                 : hm-rpc                : debian                                   -  enabled, port: 0
  system.adapter.ical.0                   : ical                  : debian                                   -  enabled
  system.adapter.ical.1                   : ical                  : debian                                   -  enabled
  system.adapter.ical.2                   : ical                  : debian                                   -  enabled
  system.adapter.icons-mfd-png.0          : icons-mfd-png         : debian                                   -  enabled
  system.adapter.icons-mfd-svg.0          : icons-mfd-svg         : debian                                   -  enabled
+ system.adapter.info.0                   : info                  : debian                                   -  enabled
+ system.adapter.iot.0                    : iot                   : debian                                   -  enabled
+ system.adapter.javascript.0             : javascript            : debian                                   -  enabled
+ system.adapter.lg-thinq.0               : lg-thinq              : debian                                   -  enabled
+ system.adapter.linux-control.0          : linux-control         : debian                                   -  enabled
+ system.adapter.logparser.0              : logparser             : debian                                   -  enabled
+ system.adapter.meross.0                 : meross                : debian                                   -  enabled
+ system.adapter.mihome-vacuum.0          : mihome-vacuum         : debian                                   -  enabled, port: 54321
  system.adapter.mobile.0                 : mobile                : debian                                   -  enabled
+ system.adapter.modbus.0                 : modbus                : debian                                   -  enabled
+ system.adapter.openligadb.0             : openligadb            : debian                                   -  enabled
+ system.adapter.ping.0                   : ping                  : debian                                   -  enabled
+ system.adapter.pollenflug.0             : pollenflug            : debian                                   -  enabled
  system.adapter.rpi2.1                   : rpi2                  : raspberrypi                              -  enabled
+ system.adapter.scenes.0                 : scenes                : debian                                   -  enabled
+ system.adapter.shelly.0                 : shelly                : debian                                   -  enabled, port: 1882, bind: 0.0.0.0
+ system.adapter.simple-api.0             : simple-api            : debian                                   -  enabled, port: 8087, bind: 0.0.0.0, run as: admin
+ system.adapter.socketio.0               : socketio              : debian                                   -  enabled, port: 8084, bind: 0.0.0.0 (SSL), run as: admin
+ system.adapter.sql.0                    : sql                   : debian                                   -  enabled, port: 3306
+ system.adapter.systeminfo.0             : systeminfo            : debian                                   -  enabled
+ system.adapter.tankerkoenig.0           : tankerkoenig          : debian                                   -  enabled
+ system.adapter.telegram.0               : telegram              : debian                                   -  enabled, port: 8443, bind: 0.0.0.0
+ system.adapter.terminal.0               : terminal              : debian                                   -  enabled, port: 8088, bind: 0.0.0.0, run as: admin
+ system.adapter.text2command.0           : text2command          : debian                                   -  enabled
+ system.adapter.tibberlink.0             : tibberlink            : debian                                   -  enabled
+ system.adapter.tr-064.0                 : tr-064                : debian                                   -  enabled
+ system.adapter.trashschedule.0          : trashschedule         : debian                                   -  enabled
+ system.adapter.upnp.0                   : upnp                  : debian                                   -  enabled
+ system.adapter.viessmannapi.0           : viessmannapi          : debian                                   -  enabled
  system.adapter.vis-bars.0               : vis-bars              : debian                                   -  enabled
  system.adapter.vis-canvas-gauges.0      : vis-canvas-gauges     : debian                                   -  enabled
  system.adapter.vis-colorpicker.0        : vis-colorpicker       : debian                                   -  enabled
  system.adapter.vis-fancyswitch.0        : vis-fancyswitch       : debian                                   -  enabled
  system.adapter.vis-history.0            : vis-history           : debian                                   -  enabled
  system.adapter.vis-hqwidgets.0          : vis-hqwidgets         : debian                                   -  enabled
  system.adapter.vis-jqui-mfd.0           : vis-jqui-mfd          : debian                                   -  enabled
  system.adapter.vis-justgage.0           : vis-justgage          : debian                                   -  enabled
  system.adapter.vis-materialdesign.0     : vis-materialdesign    : debian                                   -  enabled
  system.adapter.vis-metro.0              : vis-metro             : debian                                   -  enabled
  system.adapter.vis-plumb.0              : vis-plumb             : debian                                   -  enabled
  system.adapter.vis-timeandweather.0     : vis-timeandweather    : debian                                   -  enabled
  system.adapter.vis-weather.0            : vis-weather           : debian                                   -  enabled
  system.adapter.vis.0                    : vis                   : debian                                   -  enabled
+ system.adapter.web.0                    : web                   : debian                                   -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
  system.adapter.zigbee.0                 : zigbee                : raspberrypi                              -  enabled, port: /dev/ttyUSB0

+ instance is alive

Enabled adapters with bindings
+ system.adapter.admin.0                  : admin                 : debian                                   -  enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin
+ system.adapter.hm-rpc.0                 : hm-rpc                : debian                                   -  enabled, port: 0
+ system.adapter.hm-rpc.1                 : hm-rpc                : debian                                   -  enabled, port: 0
+ system.adapter.mihome-vacuum.0          : mihome-vacuum         : debian                                   -  enabled, port: 54321
+ system.adapter.shelly.0                 : shelly                : debian                                   -  enabled, port: 1882, bind: 0.0.0.0
+ system.adapter.simple-api.0             : simple-api            : debian                                   -  enabled, port: 8087, bind: 0.0.0.0, run as: admin
+ system.adapter.socketio.0               : socketio              : debian                                   -  enabled, port: 8084, bind: 0.0.0.0 (SSL), run as: admin
+ system.adapter.sql.0                    : sql                   : debian                                   -  enabled, port: 3306
+ system.adapter.telegram.0               : telegram              : debian                                   -  enabled, port: 8443, bind: 0.0.0.0
+ system.adapter.terminal.0               : terminal              : debian                                   -  enabled, port: 8088, bind: 0.0.0.0, run as: admin
+ system.adapter.web.0                    : web                   : debian                                   -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
  system.adapter.zigbee.0                 : zigbee                : raspberrypi                              -  enabled, port: /dev/ttyUSB0

ioBroker-Repositories
stable        : http://download.iobroker.net/sources-dist.json
beta          : http://download.iobroker.net/sources-dist-latest.json

Active repo(s): stable

Installed ioBroker-Instances
Used repository: stable
Adapter    "admin"        : 6.12.0   , installed 6.12.0
Adapter    "discovery"    : 4.2.0    , installed 4.2.0
Adapter    "enigma2"      : 2.0.5    , installed 2.0.5
Controller "js-controller": 5.0.17   , installed 4.0.24 [Updatable]
Adapter    "rpi2"         : 1.3.2    , installed 1.3.2
Adapter    "unifi"        : 0.6.7    , installed 0.6.7
Adapter    "zigbee"       : 1.9.7    , installed 1.8.23 [Updatable]

Objects and States
Please stand by - This may take a while
Objects:        28092
States:         22715

*** OS-Repositories and Updates ***
Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
Hit:2 http://deb.debian.org/debian bullseye InRelease
Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:5 https://deb.nodesource.com/node_18.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:22              0.0.0.0:*               LISTEN      0          12641      525/sshd: /usr/sbin
tcp6       0      0 :::3306                 :::*                    LISTEN      110        12676      569/mariadbd
tcp6       0      0 :::22                   :::*                    LISTEN      0          12643      525/sshd: /usr/sbin
udp        0      0 0.0.0.0:68              0.0.0.0:*                           0          13987      780/dhcpcd
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           108        13921      394/avahi-daemon: r
udp        0      0 0.0.0.0:58656           0.0.0.0:*                           108        13923      394/avahi-daemon: r
udp6       0      0 :::41470                :::*                                108        13924      394/avahi-daemon: r
udp6       0      0 :::546                  :::*                                0          13999      780/dhcpcd
udp6       0      0 :::5353                 :::*                                108        13922      394/avahi-daemon: r

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

2024-01-08 09:11:19.565  - info: zigbee.0 (765235) debug devices set to []
2024-01-08 09:11:27.300  - info: host.raspberrypi received SIGTERM
2024-01-08 09:11:27.306  - info: zigbee.0 (765235) cleaned everything up...
2024-01-08 09:11:27.324  - info: rpi2.1 (765173) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2024-01-08 09:11:27.312  - info: host.raspberrypi stopInstance system.adapter.rpi2.1 (force=false, process=true)
2024-01-08 09:11:27.314  - info: host.raspberrypi stopInstance system.adapter.zigbee.0 (force=false, process=true)
2024-01-08 09:11:27.316  - info: host.raspberrypi stopInstance system.adapter.enigma2.0 (force=false, process=true)
2024-01-08 09:11:27.337  - info: rpi2.1 (765173) Got terminate signal TERMINATE_YOURSELF
2024-01-08 09:11:27.336  - info: enigma2.0 (765291) Got terminate signal TERMINATE_YOURSELF
2024-01-08 09:11:27.379  - info: host.raspberrypi stopInstance system.adapter.rpi2.1 send kill signal
2024-01-08 09:11:27.384  - info: host.raspberrypi stopInstance system.adapter.zigbee.0 send kill signal
2024-01-08 09:11:27.386  - info: host.raspberrypi stopInstance system.adapter.enigma2.0 send kill signal
2024-01-08 09:11:27.619  - info: zigbee.0 (765235) Zigbee: disabling joining new devices.
2024-01-08 09:11:27.670  - info: zigbee.0 (765235) Got terminate signal TERMINATE_YOURSELF
2024-01-08 09:11:27.834  - info: enigma2.0 (765291) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2024-01-08 09:11:27.879  - info: zigbee.0 (765235) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2024-01-08 09:11:28.310  - info: host.raspberrypi instance system.adapter.rpi2.1 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2024-01-08 09:11:28.387  - info: host.raspberrypi stopInstance system.adapter.zigbee.0 killing pid 765235
2024-01-08 09:11:28.389  - info: host.raspberrypi stopInstance system.adapter.enigma2.0 killing pid 765291
2024-01-08 09:11:28.834  - info: host.raspberrypi instance system.adapter.enigma2.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2024-01-08 09:11:28.836  - info: host.raspberrypi All instances are stopped.
2024-01-08 09:11:29.178  - warn: host.raspberrypi instance system.adapter.zigbee.0 terminated due to SIGTERM
2024-01-08 09:11:29.180  - info: host.raspberrypi instance system.adapter.zigbee.0 terminated with code null ()
2024-01-08 09:11:29.181  - info: host.raspberrypi All instances are stopped.
2024-01-08 09:11:29.271  - info: host.raspberrypi terminated

Vielen Dank!

Thomas Braun

@djsirius sagte in Diskussion zum HowTo nodejs-Installation und upgrade:

npm ERR! network request to https://registry.npmjs.org/@iobroker%2Fjsonltool failed, reason: connect ETIMEDOUT 2606:4700::6810:1a22:443

Schau mal nach, ob dein Router / Internet-Provider zur Gänze auf IPv6 umgestellt ist.

Z. B. in der FritzBox muss zum einen IPv6 grundsätzlich angehakt sein, aber auch das Routing nach draußen muss auf IPv6 gestellt werden.

djsirius

@thomas-braun

Hi,

macht das Sinn, weil das Master System diesen Fehler nicht hat. Die laufen ja beide über den selben Router.

Ist IPv6 ist aber auch angehakt.

djsirius

Ich habe jetzt ein Downgrade von Nodejs gemacht, weil ich nicht weiter komme.

Wenn noch jemand eine Idee hat, bitte her damit. Ich bin ratlos! :-(

Thomas Braun

@djsirius

npm ERR! network This is a problem related to network connectivity.

npm ERR! network In most cases you are behind a proxy or have bad network settings.

Ist zu 99,9% etwas in deinem Netzwerk.

Marc Berg

@djsirius sagte in Diskussion zum HowTo nodejs-Installation und upgrade:

Wenn noch jemand eine Idee hat, bitte her damit.

mach mal auf master und slave jeweils:

ping registry.npmjs.org
ping -4 registry.npmjs.org
ping -6 registry.npmjs.org

Thomas Braun

@marc-berg

Haste gerade die traceroute commandos für IPv6 und IPv4 parat?

djsirius

@marc-berg said in Diskussion zum HowTo nodejs-Installation und upgrade:

mach mal auf master und slave jeweils:

ping registry.npmjs.org <- geht auf beiden nicht
ping -4 registry.npmjs.org <- geht auf beiden
ping -6 registry.npmjs.org <- geht auf beiden nicht

Marc Berg

@thomas-braun sagte in Diskussion zum HowTo nodejs-Installation und upgrade:

Haste gerade die traceroute commandos für IPv6 und IPv4 parat?

traceroute6  heise.de
traceroute  heise.de

Marc Berg

@djsirius sagte in Diskussion zum HowTo nodejs-Installation und upgrade:

ping registry.npmjs.org <- geht auf beiden nicht

die Response zumindest für

ping registry.npmjs.org

wäre interessant

EDIT: und

nslookup registry.npmjs.org

djsirius

@marc-berg said in Diskussion zum HowTo nodejs-Installation und upgrade:

@djsirius sagte in Diskussion zum HowTo nodejs-Installation und upgrade:

ping registry.npmjs.org <- geht auf beiden nicht

die Response zumindest für
ping registry.npmjs.org
wäre interessant

EDIT: und
nslookup registry.npmjs.org

iobroker@debian:~$ ping registry.npmjs.org
PING registry.npmjs.org(2606:4700::6810:23 (2606:4700::6810:23)) 56 data bytes


^C
--- registry.npmjs.org ping statistics ---
288 packets transmitted, 0 received, 100% packet loss, time 293895ms

iobroker@debian:~$ nslookup registry.npmjs.org
Server:         192.168.1.1
Address:        192.168.1.1#53

Non-authoritative answer:
Name:   registry.npmjs.org
Address: 104.16.31.34
Name:   registry.npmjs.org
Address: 104.16.29.34
Name:   registry.npmjs.org
Address: 104.16.0.35
Name:   registry.npmjs.org
Address: 104.16.25.34
Name:   registry.npmjs.org
Address: 104.16.27.34
Name:   registry.npmjs.org
Address: 104.16.30.34
Name:   registry.npmjs.org
Address: 104.16.2.35
Name:   registry.npmjs.org
Address: 104.16.26.34
Name:   registry.npmjs.org
Address: 104.16.24.34
Name:   registry.npmjs.org
Address: 104.16.28.34
Name:   registry.npmjs.org
Address: 104.16.1.35
Name:   registry.npmjs.org
Address: 104.16.3.35
Name:   registry.npmjs.org
Address: 2606:4700::6810:23
Name:   registry.npmjs.org
Address: 2606:4700::6810:1922
Name:   registry.npmjs.org
Address: 2606:4700::6810:1822
Name:   registry.npmjs.org
Address: 2606:4700::6810:1a22
Name:   registry.npmjs.org
Address: 2606:4700::6810:1c22
Name:   registry.npmjs.org
Address: 2606:4700::6810:223
Name:   registry.npmjs.org
Address: 2606:4700::6810:323
Name:   registry.npmjs.org
Address: 2606:4700::6810:1d22
Name:   registry.npmjs.org
Address: 2606:4700::6810:123
Name:   registry.npmjs.org
Address: 2606:4700::6810:1b22
Name:   registry.npmjs.org
Address: 2606:4700::6810:1e22
Name:   registry.npmjs.org
Address: 2606:4700::6810:1f22

Marc Berg

@djsirius
Wie es für mich aussieht, ist IPv6 auf Betriebssystemseite priorisiert (was Standard ist), aber es kommt keine Kommunikation auf dem Protokoll zustande. Da musst du wirklich in deinem Netzwerk suchen, wahrscheinlich bei den Router Einstellungen.

djsirius

Auf meinem Windows-Rechner geht!

ping registry.npmjs.org

Ping wird ausgeführt für registry.npmjs.org [104.16.29.34] mit 32 Bytes Daten:
Antwort von 104.16.29.34: Bytes=32 Zeit=12ms TTL=58
Antwort von 104.16.29.34: Bytes=32 Zeit=11ms TTL=58
Antwort von 104.16.29.34: Bytes=32 Zeit=11ms TTL=58
Antwort von 104.16.29.34: Bytes=32 Zeit=11ms TTL=58

Ping-Statistik für 104.16.29.34:
    Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
    (0% Verlust),
Ca. Zeitangaben in Millisek.:
    Minimum = 11ms, Maximum = 12ms, Mittelwert = 11ms

Aber ping -6 registry.npmjs.org geht nicht!

Community Forum

NEWS

Diskussion zum HowTo nodejs-Installation und upgrade

Support us

867

32.4k

81.5k

1.3m