Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. pivCCU nach Update node.js nicht erreichbar

    NEWS

    • [erledigt] 15. 05. Wartungsarbeiten am ioBroker Forum

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    pivCCU nach Update node.js nicht erreichbar

    This topic has been deleted. Only users with topic management privileges can see it.
    • Thomas Braun
      Thomas Braun Most Active @Meister Mopper last edited by

      @meister-mopper sagte in pivCCU nach Update node.js nicht erreichbar:

      klopp bitte die lange Fassung in </> (codetags) hier rein.

      Die Ausgabe von iob diag hat die schon dabei. Muss nur kopiert und eingefügt werden.
      Jetzt sind zwei CodeTags drumherum, das ist auch falsch.

      1 Reply Last reply Reply Quote 0
      • W
        wibear @Meister Mopper last edited by Homoran

        @meister-mopper sagte in pivCCU nach Update node.js nicht erreichbar:

        klopp bitte die lange Fassung in </> (codetags) hier rein

        Ist es besser?

        Skript v.2024-05-22
        
        *** BASE SYSTEM ***
           Static hostname: iobroker-pi
                 Icon name: computer
          Operating System: Raspbian GNU/Linux 11 (bullseye)
                    Kernel: Linux 6.6.44-v7l+
              Architecture: arm
        
        Model           : Raspberry Pi 4 Model B Rev 1.5
        Docker          : false
        Virtualization  : none
        Kernel          : armv7l
        Userland        : 32 bit
        
        Systemuptime and Load:
         16:21:41 up 13 min,  1 user,  load average: 1.00, 1.08, 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: Tue 2024-08-13 16:21:42 CEST
                   Universal time: Tue 2024-08-13 14:21:42 UTC
                         RTC time: n/a
                        Time zone: Europe/Berlin (CEST, +0200)
        System clock synchronized: yes
                      NTP service: active
                  RTC in local TZ: no
        
        *** Users and Groups ***
        User that called 'iob diag':
        wibear
        HOME=/home/wibear
        GROUPS=wibear adm dialout cdrom sudo audio video plugdev games users input render netdev gpio i2c spi iobroker
        
        User that is running 'js-controller':
        iobroker
        HOME=/home/iobroker
        GROUPS=iobroker tty dialout audio video plugdev bluetooth gpio i2c
        
        *** Display-Server-Setup ***
        Display-Server: false
        Desktop:
        Terminal:       tty
        Boot Target:    multi-user.target
        
        *** MEMORY ***
                       total        used        free      shared  buff/cache   available
        Mem:            3.9G        941M        2.3G        1.0M        626M        2.8G
        Swap:            99M          0B         99M
        Total:          4.0G        941M        2.4G
        
        Active iob-Instances:   21
        
                 3885 M total memory
                  942 M used memory
                  230 M active memory
                 1233 M inactive memory
                 2317 M free memory
                   76 M buffer memory
                  550 M swap cache
                   99 M total swap
                    0 M used swap
                   99 M free swap
        
        *** top - Table Of Processes  ***
        top - 16:21:42 up 13 min,  1 user,  load average: 1.00, 1.08, 0.80
        Tasks: 194 total,   1 running, 193 sleeping,   0 stopped,   0 zombie
        %Cpu(s): 30.0 us, 11.4 sy,  0.0 ni, 52.9 id,  4.3 wa,  0.0 hi,  1.4 si,  0.0 st
        MiB Mem :   3885.9 total,   2316.9 free,    942.0 used,    627.0 buff/cache
        MiB Swap:    100.0 total,    100.0 free,      0.0 used.   2817.4 avail Mem
        
        *** FAILED SERVICES ***
        
          UNIT                       LOAD   ACTIVE SUB    DESCRIPTION
        * pivccu-dkms.service        loaded failed failed piVCCU DKMS Modules
        * pivccu-rpi-modules.service loaded failed failed piVCCU RPi Kernel loader
        
        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.
        2 loaded units listed.
        
        *** FILESYSTEM ***
        Filesystem     Type      Size  Used Avail Use% Mounted on
        /dev/root      ext4       29G   11G   18G  39% /
        devtmpfs       devtmpfs  1.7G     0  1.7G   0% /dev
        tmpfs          tmpfs     1.9G     0  1.9G   0% /dev/shm
        tmpfs          tmpfs     778M  1.1M  777M   1% /run
        tmpfs          tmpfs     5.0M  4.0K  5.0M   1% /run/lock
        /dev/mmcblk0p1 vfat      255M   63M  193M  25% /boot
        tmpfs          tmpfs     389M     0  389M   0% /run/user/1000
        
        Messages concerning ext4 filesystem in dmesg:
        [Tue Aug 13 16:08:37 2024] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0  smsc95xx.macaddr=D8:3A:DD:16:18:C4 vc_mem.mem_base=0x3f000000 vc_mem.mem_size=0x3f600000  console=tty1 root=PARTUUID=e605bf32-02 rootfstype=ext4 fsck.repair=yes rootwait
        [Tue Aug 13 16:08:38 2024] EXT4-fs (mmcblk0p2): mounted filesystem d3104e7d-5f59-47e0-8621-290882475163 ro with ordered data mode. Quota mode: none.
        [Tue Aug 13 16:08:38 2024] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
        [Tue Aug 13 16:08:39 2024] EXT4-fs (mmcblk0p2): re-mounted d3104e7d-5f59-47e0-8621-290882475163 r/w. Quota mode: none.
        
        Show mounted filesystems:
        TARGET                       SOURCE         FSTYPE     OPTIONS
        /                            /dev/mmcblk0p2 ext4       rw,noatime
        |-/dev                       devtmpfs       devtmpfs   rw,relatime,size=1726396k,nr_inodes=34271,mode=755
        | |-/dev/shm                 tmpfs          tmpfs      rw,nosuid,nodev
        | |-/dev/pts                 devpts         devpts     rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000
        | `-/dev/mqueue              mqueue         mqueue     rw,nosuid,nodev,noexec,relatime
        |-/proc                      proc           proc       rw,relatime
        | `-/proc/sys/fs/binfmt_misc systemd-1      autofs     rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct
        |-/sys                       sysfs          sysfs      rw,nosuid,nodev,noexec,relatime
        | |-/sys/kernel/security     securityfs     securityfs rw,nosuid,nodev,noexec,relatime
        | |-/sys/fs/cgroup           cgroup2        cgroup2    rw,nosuid,nodev,noexec,relatime
        | |-/sys/fs/pstore           pstore         pstore     rw,nosuid,nodev,noexec,relatime
        | |-/sys/fs/bpf              bpf            bpf        rw,nosuid,nodev,noexec,relatime,mode=700
        | |-/sys/kernel/tracing      tracefs        tracefs    rw,nosuid,nodev,noexec,relatime
        | |-/sys/kernel/debug        debugfs        debugfs    rw,nosuid,nodev,noexec,relatime
        | |-/sys/kernel/config       configfs       configfs   rw,nosuid,nodev,noexec,relatime
        | `-/sys/fs/fuse/connections fusectl        fusectl    rw,nosuid,nodev,noexec,relatime
        |-/run                       tmpfs          tmpfs      rw,nosuid,nodev,size=795828k,nr_inodes=819200,mode=755
        | |-/run/lock                tmpfs          tmpfs      rw,nosuid,nodev,noexec,relatime,size=5120k
        | |-/run/rpc_pipefs          sunrpc         rpc_pipefs rw,relatime
        | `-/run/user/1000           tmpfs          tmpfs      rw,nosuid,nodev,relatime,size=397912k,nr_inodes=99478,mode=700,uid=1000,gid=1000
        |-/boot                      /dev/mmcblk0p1 vfat       rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro
        `-/var/lib/lxcfs             lxcfs          fuse.lxcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other
        
        Files in neuralgic directories:
        
        /var:
        du: cannot access '/var/lib/lxcfs/cgroup': Input/output error
        4.7G    /var/
        3.3G    /var/log
        2.9G    /var/log/journal/6462312882a642219bbda7aff5f4f5b9
        2.9G    /var/log/journal
        738M    /var/lib
        
        Archived and active journals take up 2.8G in the file system.
        
        /opt/iobroker/backups:
        82M     /opt/iobroker/backups/
        
        /opt/iobroker/iobroker-data:
        746M    /opt/iobroker/iobroker-data/
        594M    /opt/iobroker/iobroker-data/files
        441M    /opt/iobroker/iobroker-data/files/javascript.admin
        409M    /opt/iobroker/iobroker-data/files/javascript.admin/static
        408M    /opt/iobroker/iobroker-data/files/javascript.admin/static/js
        
        The five largest files in iobroker-data are:
        27M     /opt/iobroker/iobroker-data/files/backitup.admin/static/js/main.ce422ec2.js.map
        24M     /opt/iobroker/iobroker-data/files/web.admin/static/js/main.135279a0.js.map
        13M     /opt/iobroker/iobroker-data/states.jsonl
        9.6M    /opt/iobroker/iobroker-data/objects.jsonl
        8.7M    /opt/iobroker/iobroker-data/files/javascript.admin/static/js/838.0aa41cb0.chunk.js.map
        
        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.16.0
        /usr/bin/node           v20.16.0
        /usr/bin/npm            10.8.1
        /usr/bin/npx            10.8.1
        /usr/bin/corepack       0.28.2
        
        
        nodejs:
          Installed: 20.16.0-1nodesource1
          Candidate: 20.16.0-1nodesource1
          Version table:
         *** 20.16.0-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages
                100 /var/lib/dpkg/status
             20.15.1-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages
             20.15.0-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages
             20.14.0-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages
             20.13.1-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages
             20.13.0-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages
             20.12.2-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages
             20.12.1-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages
             20.12.0-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages
             20.11.1-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages
             20.11.0-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages
             20.10.0-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages
             20.9.0-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages
             20.8.1-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages
             20.8.0-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages
             20.7.0-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages
             20.6.1-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages
             20.6.0-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages
             20.5.1-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages
             20.5.0-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages
             20.4.0-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages
             20.3.1-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages
             20.3.0-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages
             20.2.0-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages
             20.1.0-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages
             20.0.0-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages
             12.22.12~dfsg-1~deb11u4 500
                500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
        
        Temp directories causing npm8 problem: 0
        No problems detected
        
        Errors in npm tree:
        
        *** ioBroker-Installation ***
        
        ioBroker Status
        iobroker is running on this host.
        
        
        Objects type: jsonl
        States  type: jsonl
        
        Core adapters versions
        js-controller:  5.0.19
        admin:          7.0.22
        javascript:     8.7.6
        
        nodejs modules from github:     1
        +-- iobroker.vw-connect@0.5.3 (git+ssh://git@github.com/TA2k/ioBroker.vw-connect.git#b5fbfb41f65b8a1efb646e9efb68f1cbd1627d27)
        
        Adapter State
        + system.adapter.admin.0                  : admin                 : iobroker-pi                              -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
        + system.adapter.alexa2.0                 : alexa2                : iobroker-pi                              -  enabled
        + system.adapter.backitup.0               : backitup              : iobroker-pi                              -  enabled
        + system.adapter.device-reminder.0        : device-reminder       : iobroker-pi                              -  enabled
        + system.adapter.discovery.0              : discovery             : iobroker-pi                              -  enabled
        + system.adapter.ems-esp.0                : ems-esp               : iobroker-pi                              -  enabled
        + system.adapter.fb-checkpresence.0       : fb-checkpresence      : iobroker-pi                              -  enabled
          system.adapter.habpanel.0               : habpanel              : iobroker-pi                              -  enabled
        + system.adapter.history.0                : history               : iobroker-pi                              -  enabled
        + system.adapter.hm-rega.0                : hm-rega               : iobroker-pi                              -  enabled
        + system.adapter.hm-rpc.0                 : hm-rpc                : iobroker-pi                              -  enabled, port: 18701
          system.adapter.hm-rpc.1                 : hm-rpc                : iobroker-pi                              -  enabled, port: 12001
          system.adapter.hm-rpc.2                 : hm-rpc                : iobroker-pi                              -  enabled, port: 12010
        + system.adapter.influxdb.0               : influxdb              : iobroker-pi                              -  enabled, port: 8086
          system.adapter.info.0                   : info                  : iobroker-pi                              -  enabled
        + system.adapter.javascript.0             : javascript            : iobroker-pi                              -  enabled
        + system.adapter.mqtt.0                   : mqtt                  : iobroker-pi                              -  enabled, port: 1883, bind: 192.168.178.10
          system.adapter.netatmo-crawler.0        : netatmo-crawler       : iobroker-pi                              -  enabled
        + system.adapter.rpi2.0                   : rpi2                  : iobroker-pi                              -  enabled
        + system.adapter.shelly.0                 : shelly                : iobroker-pi                              -  enabled, port: 1882, bind: 0.0.0.0
        + system.adapter.simple-api.0             : simple-api            : iobroker-pi                              -  enabled, port: 8087, bind: 0.0.0.0, run as: admin
        + system.adapter.tr-064.0                 : tr-064                : iobroker-pi                              -  enabled
          system.adapter.tuya.0                   : tuya                  : iobroker-pi                              - disabled
        + system.adapter.vw-connect.0             : vw-connect            : iobroker-pi                              -  enabled
          system.adapter.weatherunderground.0     : weatherunderground    : iobroker-pi                              - disabled
        + system.adapter.web.0                    : web                   : iobroker-pi                              -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
        + system.adapter.whatsapp-cmb.0           : whatsapp-cmb          : iobroker-pi                              -  enabled
        
        + instance is alive
        
        Enabled adapters with bindings
        + system.adapter.admin.0                  : admin                 : iobroker-pi                              -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
        + system.adapter.hm-rpc.0                 : hm-rpc                : iobroker-pi                              -  enabled, port: 18701
          system.adapter.hm-rpc.1                 : hm-rpc                : iobroker-pi                              -  enabled, port: 12001
          system.adapter.hm-rpc.2                 : hm-rpc                : iobroker-pi                              -  enabled, port: 12010
        + system.adapter.influxdb.0               : influxdb              : iobroker-pi                              -  enabled, port: 8086
        + system.adapter.mqtt.0                   : mqtt                  : iobroker-pi                              -  enabled, port: 1883, bind: 192.168.178.10
        + system.adapter.shelly.0                 : shelly                : iobroker-pi                              -  enabled, port: 1882, bind: 0.0.0.0
        + system.adapter.simple-api.0             : simple-api            : iobroker-pi                              -  enabled, port: 8087, bind: 0.0.0.0, run as: admin
        + system.adapter.web.0                    : web                   : iobroker-pi                              -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
        
        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"        : 7.0.22   , installed 7.0.22
        Adapter    "alexa2"       : 3.26.5   , installed 3.26.5
        Adapter    "backitup"     : 3.0.16   , installed 3.0.16
        Adapter    "device-reminder": 3.1.2  , installed 3.1.2
        Adapter    "discovery"    : 4.5.0    , installed 4.5.0
        Adapter    "ems-esp"      : 3.5.0    , installed 3.5.0
        Adapter    "fb-checkpresence": 1.2.4 , installed 1.2.4
        Adapter    "habpanel"     : 0.5.0    , installed 0.5.0
        Adapter    "history"      : 3.0.1    , installed 3.0.1
        Adapter    "hm-rega"      : 4.0.0    , installed 4.0.0
        Adapter    "hm-rpc"       : 1.17.0   , installed 1.17.0
        Adapter    "influxdb"     : 4.0.2    , installed 4.0.2
        Adapter    "javascript"   : 8.7.6    , installed 8.7.6
        Controller "js-controller": 6.0.9    , installed 5.0.19 [Updatable]
        Adapter    "mqtt"         : 5.2.0    , installed 5.2.0
        Adapter    "netatmo-crawler": 0.8.1  , installed 0.8.1
        Adapter    "rpi2"         : 1.3.2    , installed 1.3.2
        Adapter    "shelly"       : 7.0.0    , installed 7.0.0
        Adapter    "simple-api"   : 2.8.0    , installed 2.8.0
        Adapter    "socketio"     : 6.7.1    , installed 6.7.1
        Adapter    "tr-064"       : 4.3.0    , installed 4.3.0
        Adapter    "tuya"         : 3.15.0   , installed 3.15.0
        Adapter    "weatherunderground": 3.7.0, installed 3.7.0
        Adapter    "web"          : 6.2.5    , installed 6.2.5
        Adapter    "whatsapp-cmb" : 0.3.0    , installed 0.3.0
        Adapter    "ws"           : 2.6.2    , installed 2.6.2
        
        Objects and States
        Please stand by - This may take a while
        Objects:        7430
        States:         6279
        
        *** OS-Repositories and Updates ***
        Hit:1 https://repos.influxdata.com/debian bullseye InRelease
        Hit:2 http://archive.raspberrypi.org/debian bullseye InRelease
        Hit:3 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
        Hit:4 https://deb.nodesource.com/node_20.x nodistro InRelease
        Hit:5 https://apt.pivccu.de/piVCCU stable InRelease
        Hit:6 https://packages.grafana.com/oss/deb stable 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 10.0.3.1:53             0.0.0.0:*               LISTEN      0          6228       814/dnsmasq
        tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      0          6194       785/sshd: /usr/sbin
        tcp        0      0 192.168.178.10:12001    0.0.0.0:*               LISTEN      1001       39110      5590/io.hm-rpc.1
        tcp        0      0 192.168.178.10:12010    0.0.0.0:*               LISTEN      1001       36706      5591/io.hm-rpc.2
        tcp        0      0 0.0.0.0:1882            0.0.0.0:*               LISTEN      1001       9377       1407/io.shelly.0
        tcp        0      0 192.168.178.10:1883     0.0.0.0:*               LISTEN      1001       8528       1324/io.mqtt.0
        tcp        0      0 127.0.0.1:9001          0.0.0.0:*               LISTEN      1001       7195       905/iobroker.js-con
        tcp        0      0 127.0.0.1:9000          0.0.0.0:*               LISTEN      1001       5644       905/iobroker.js-con
        tcp        0      0 127.0.0.1:8088          0.0.0.0:*               LISTEN      999        6272       730/influxd
        tcp6       0      0 :::22                   :::*                    LISTEN      0          6196       785/sshd: /usr/sbin
        tcp6       0      0 :::3000                 :::*                    LISTEN      111        5642       904/grafana
        tcp6       0      0 :::8086                 :::*                    LISTEN      999        6362       730/influxd
        tcp6       0      0 :::8087                 :::*                    LISTEN      1001       6952       1464/io.simple-api.
        tcp6       0      0 :::8082                 :::*                    LISTEN      1001       7769       1483/io.web.0
        tcp6       0      0 :::8081                 :::*                    LISTEN      1001       7239       990/io.admin.0
        udp        0      0 0.0.0.0:5353            0.0.0.0:*                           108        787        337/avahi-daemon: r
        udp        0      0 0.0.0.0:47656           0.0.0.0:*                           108        789        337/avahi-daemon: r
        udp        0      0 10.0.3.1:53             0.0.0.0:*                           0          6227       814/dnsmasq
        udp        0      0 0.0.0.0:67              0.0.0.0:*                           0          6224       814/dnsmasq
        udp        0      0 0.0.0.0:68              0.0.0.0:*                           0          897        598/dhclient
        udp6       0      0 :::5353                 :::*                                108        788        337/avahi-daemon: r
        udp6       0      0 :::34059                :::*                                108        790        337/avahi-daemon: r
        
        *** Log File - Last 25 Lines ***
        
        2024-08-13 16:21:48.384  - info: hm-rpc.2 (4770) Terminated (NO_ERROR): Without reason
        2024-08-13 16:21:49.099  - info: host.iobroker-pi instance system.adapter.hm-rpc.1 terminated with code 0 (NO_ERROR)
        2024-08-13 16:21:49.099  - info: host.iobroker-pi Restart adapter system.adapter.hm-rpc.1 because enabled
        2024-08-13 16:21:49.099  - info: host.iobroker-pi instance system.adapter.hm-rpc.2 terminated with code 0 (NO_ERROR)
        2024-08-13 16:21:49.100  - info: host.iobroker-pi Restart adapter system.adapter.hm-rpc.2 because enabled
        2024-08-13 16:21:49.884  - info: hm-rpc.0 (5004) starting. Version 1.17.0 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v20.16.0, js-controller: 5.0.19
        2024-08-13 16:21:50.185  - info: hm-rpc.0 (5004) binrpc server is trying to listen on 192.168.178.10:18701
        2024-08-13 16:21:50.187  - info: hm-rpc.0 (5004) binrpc client is trying to connect to 192.168.178.12:8701/ with ["xmlrpc_bin://192.168.178.10:18701","iobroker-pi:hm-rpc.0:586ced57dee52ef270bfb61be9f07a73"]
        2024-08-13 16:21:50.457  - error: hm-rpc.0 (5004) Init not possible, going to stop: connect EHOSTUNREACH 192.168.178.12:8701
        2024-08-13 16:21:50.461  - error: hm-rega.0 (1231) CCU 192.168.178.12 unreachable
        2024-08-13 16:22:19.230  - info: host.iobroker-pi instance system.adapter.hm-rpc.1 started with pid 5590
        2024-08-13 16:22:19.243  - info: host.iobroker-pi instance system.adapter.hm-rpc.2 started with pid 5591
        2024-08-13 16:22:20.462  - info: hm-rpc.0 (5004) binrpc -> 192.168.178.12:8701/ init ["xmlrpc_bin://192.168.178.10:18701",""]
        2024-08-13 16:22:20.481  - error: hm-rpc.0 (5004) Cannot call init: [xmlrpc_bin://192.168.178.10:18701, ""] Socket closed before the connection was established
        2024-08-13 16:22:20.542  - info: hm-rpc.0 (5004) terminating
        2024-08-13 16:22:20.544  - info: hm-rpc.0 (5004) Terminated (NO_ERROR): Without reason
        2024-08-13 16:22:21.115  - info: host.iobroker-pi instance system.adapter.hm-rpc.0 terminated with code 0 (NO_ERROR)
        2024-08-13 16:22:23.573  - error: hm-rega.0 (1231) CCU 192.168.178.12 unreachable
        2024-08-13 16:22:21.116  - info: host.iobroker-pi Restart adapter system.adapter.hm-rpc.0 because enabled
        2024-08-13 16:22:25.483  - info: hm-rpc.1 (5590) starting. Version 1.17.0 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v20.16.0, js-controller: 5.0.19
        2024-08-13 16:22:25.516  - info: hm-rpc.2 (5591) starting. Version 1.17.0 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v20.16.0, js-controller: 5.0.19
        2024-08-13 16:22:25.834  - info: hm-rpc.1 (5590) xmlrpc server is trying to listen on 192.168.178.10:12001
        2024-08-13 16:22:25.835  - info: hm-rpc.1 (5590) xmlrpc client is trying to connect to 192.168.178.12:2001/ with ["http://192.168.178.10:12001","iobroker-pi:hm-rpc.1:b7e0bbb00b214da627cd2ac33e1e6a94"]
        2024-08-13 16:22:25.863  - info: hm-rpc.2 (5591) xmlrpc server is trying to listen on 192.168.178.10:12010
        2024-08-13 16:22:25.865  - info: hm-rpc.2 (5591) xmlrpc client is trying to connect to 192.168.178.12:2010/ with ["http://192.168.178.10:12010","iobroker-pi:hm-rpc.2:53dc961ed27d3c18a140cba29ed780cc"]
        
        
        DJMarc75 1 Reply Last reply Reply Quote 0
        • DJMarc75
          DJMarc75 @wibear last edited by

          @wibear sagte in pivCCU nach Update node.js nicht erreichbar:

          Ist es besser?

          Wie Du vielleicht selbst siehst - nein 😉

          Homoran 1 Reply Last reply Reply Quote 0
          • Homoran
            Homoran Global Moderator Administrators @DJMarc75 last edited by Homoran

            @djmarc75 sagte in pivCCU nach Update node.js nicht erreichbar:

            @wibear sagte in pivCCU nach Update node.js nicht erreichbar:

            Ist es besser?

            Wie Du vielleicht selbst siehst - nein 😉

            jetzt, ja!

            im ersten hab ich nicht alle versteckten code-tags finden und fixen können

            EDIT: Jetzt aber!

            1 Reply Last reply Reply Quote 1
            • W
              wibear @Thomas Braun last edited by

              @thomas-braun sagte in pivCCU nach Update node.js nicht erreichbar:

              Controller "js-controller": 6.0.9 , installed 5.0.19 [Updatable]

              ausgeführt

              Thomas Braun 1 Reply Last reply Reply Quote 0
              • Thomas Braun
                Thomas Braun Most Active @wibear last edited by

                @wibear

                Dann ist ioBroker-seitig jetzt alles i.O.

                1 Reply Last reply Reply Quote 0
                • paul53
                  paul53 @wibear last edited by paul53

                  @wibear sagte:

                  FAILED SERVICES
                  UNIT                       LOAD   ACTIVE SUB    DESCRIPTION 
                  pivccu-dkms.service        loaded failed failed piVCCU DKMS Modules 
                  pivccu-rpi-modules.service loaded failed failed piVCCU RPi Kernel loader
                  

                  Das hat nichts mit Node.js oder ioBroker zu tun.

                  1 Reply Last reply Reply Quote 0
                  • W
                    wibear last edited by

                    @paul53 Was könnte der Grund für FailedServices sein?

                    Thomas Braun 1 Reply Last reply Reply Quote 0
                    • Thomas Braun
                      Thomas Braun Most Active @wibear last edited by

                      @wibear

                      systemctl status pivccu-dkms.service
                      systemctl status pivccu-rpi-modules.service
                      

                      könnte dir das vielleicht verraten. Ansonsten wäre das ein Fall für die Kollegen eine Tür weiter bei pivCCU.

                      Homoran W 2 Replies Last reply Reply Quote 0
                      • Homoran
                        Homoran Global Moderator Administrators @Thomas Braun last edited by

                        @thomas-braun
                        @wibear

                        oder mal mit sudo pivccu-info nachsehen

                        W 1 Reply Last reply Reply Quote 0
                        • W
                          wibear @Homoran last edited by

                          @homoran
                          pivCCU zeigt State: STOPPED
                          Kann ich das starten?

                          Thomas Braun Homoran 2 Replies Last reply Reply Quote 0
                          • Thomas Braun
                            Thomas Braun Most Active @wibear last edited by

                            @wibear sagte in pivCCU nach Update node.js nicht erreichbar:

                            pivCCU zeigt State: STOPPED

                            Das zeigt aber mit Sicherheit noch mehr...

                            sudo systemctl start pivccu-dkms.service
                            sudo systemctl start pivccu-rpi-modules.service
                            
                            W 1 Reply Last reply Reply Quote 0
                            • W
                              wibear @Thomas Braun last edited by

                              @thomas-braun

                               systemctl status pivccu-rpi-modules.service
                              ● pivccu-rpi-modules.service - piVCCU RPi Kernel loader
                                   Loaded: loaded (/lib/systemd/system/pivccu-rpi-modules.service; enabled; v>
                                   Active: failed (Result: exit-code) since Tue 2024-08-13 16:08:45 CEST; 36m>
                                  Process: 727 ExecStart=/var/lib/piVCCU/rpi-modules/ensure_headers.sh (code=>
                                 Main PID: 727 (code=exited, status=1/FAILURE)
                                      CPU: 15ms
                              
                              Aug 13 16:08:45 iobroker-pi systemd[1]: Starting piVCCU RPi Kernel loader...
                              Aug 13 16:08:45 iobroker-pi ensure_headers.sh[727]: Could not determine kernel >
                              Aug 13 16:08:45 iobroker-pi systemd[1]: pivccu-rpi-modules.service: Main proces>
                              Aug 13 16:08:45 iobroker-pi systemd[1]: pivccu-rpi-modules.service: Failed with>
                              Aug 13 16:08:45 iobroker-pi systemd[1]: Failed to start piVCCU RPi Kernel loade>
                              

                              An wen kann ich mich mit pivCCU wenden?
                              Hilft es, ein pivCCU Backup einzuspielen?

                              Thomas Braun 1 Reply Last reply Reply Quote 0
                              • W
                                wibear @Thomas Braun last edited by

                                @thomas-braun sagte in pivCCU nach Update node.js nicht erreichbar:

                                Das zeigt aber mit Sicherheit noch mehr...

                                sudo systemctl start pivccu-dkms.service
                                Job for pivccu-dkms.service failed because the control process exited with error code.
                                See "systemctl status pivccu-dkms.service" and "journalctl -xe" for details.
                                
                                1 Reply Last reply Reply Quote 0
                                • Thomas Braun
                                  Thomas Braun Most Active @wibear last edited by Thomas Braun

                                  @wibear

                                  Zieh dein Mäusekino breiter. Die Meldungen sind abgeschnitten.

                                  Hilft es, ein pivCCU Backup einzuspielen?

                                  Vermutlich nicht, sind das doch Kernel-Module.
                                  Vielleicht sind die noch nicht gegen den aktuellen Kernel gebaut worden?

                                  W 2 Replies Last reply Reply Quote 0
                                  • W
                                    wibear @Thomas Braun last edited by

                                    @thomas-braun sagte in pivCCU nach Update node.js nicht erreichbar:

                                    Die Meldungen sind abgeschnitten.

                                    systemctl status pivccu-rpi-modules.service
                                    ● pivccu-rpi-modules.service - piVCCU RPi Kernel loader
                                         Loaded: loaded (/lib/systemd/system/pivccu-rpi-modules.service; enabled; v>
                                         Active: failed (Result: exit-code) since Tue 2024-08-13 16:08:45 CEST; 36m>
                                        Process: 727 ExecStart=/var/lib/piVCCU/rpi-modules/ensure_headers.sh (code=>
                                       Main PID: 727 (code=exited, status=1/FAILURE)
                                            CPU: 15ms
                                    
                                    Aug 13 16:08:45 iobroker-pi systemd[1]: Starting piVCCU RPi Kernel loader...
                                    Aug 13 16:08:45 iobroker-pi ensure_headers.sh[727]: Could not determine kernel >
                                    Aug 13 16:08:45 iobroker-pi systemd[1]: pivccu-rpi-modules.service: Main proces>
                                    Aug 13 16:08:45 iobroker-pi systemd[1]: pivccu-rpi-modules.service: Failed with>
                                    Aug 13 16:08:45 iobroker-pi systemd[1]: Failed to start piVCCU RPi Kernel loade>
                                    lines 1-12/12 (END)...skipping...
                                    ● pivccu-rpi-modules.service - piVCCU RPi Kernel loader
                                         Loaded: loaded (/lib/systemd/system/pivccu-rpi-modules.service; enabled; vendor preset: enabled)
                                         Active: failed (Result: exit-code) since Tue 2024-08-13 16:08:45 CEST; 36min ago
                                        Process: 727 ExecStart=/var/lib/piVCCU/rpi-modules/ensure_headers.sh (code=exited, status=1/FAILURE)
                                       Main PID: 727 (code=exited, status=1/FAILURE)
                                            CPU: 15ms
                                    
                                    Aug 13 16:08:45 iobroker-pi systemd[1]: Starting piVCCU RPi Kernel loader...
                                    Aug 13 16:08:45 iobroker-pi ensure_headers.sh[727]: Could not determine kernel source.
                                    Aug 13 16:08:45 iobroker-pi systemd[1]: pivccu-rpi-modules.service: Main process exited, code=exited, status=1/FAILURE
                                    Aug 13 16:08:45 iobroker-pi systemd[1]: pivccu-rpi-modules.service: Failed with result 'exit-code'.
                                    Aug 13 16:08:45 iobroker-pi systemd[1]: Failed to start piVCCU RPi Kernel loader.
                                    
                                    
                                    1 Reply Last reply Reply Quote 0
                                    • W
                                      wibear @Thomas Braun last edited by

                                      @thomas-braun sagte in pivCCU nach Update node.js nicht erreichbar:

                                      Vielleicht sind die noch nicht geggen den aktuellen Kernel gebaut worden?

                                      Kann ich da ein downgrade machen?

                                      Thomas Braun 1 Reply Last reply Reply Quote 0
                                      • Thomas Braun
                                        Thomas Braun Most Active @wibear last edited by

                                        @wibear sagte in pivCCU nach Update node.js nicht erreichbar:

                                        Kann ich da ein downgrade machen?

                                        Du solltest eher ein Upgrade der pivCCU-Pakete machen, wenn es denn welche gibt.

                                        Hier gibt es aber ein paar Hinweise, was man da machen kann:

                                        https://alexreinert.github.io/piVCCU/docs/setup/raspberrypi.html

                                        W Homoran 2 Replies Last reply Reply Quote 0
                                        • W
                                          wibear @Thomas Braun last edited by

                                          @thomas-braun sagte in pivCCU nach Update node.js nicht erreichbar:

                                          Upgrade der pivCCU-Pakete machen

                                          Habe es schon versucht, es gibt aber momentan keine...

                                          Thomas Braun 1 Reply Last reply Reply Quote 0
                                          • Thomas Braun
                                            Thomas Braun Most Active @wibear last edited by

                                            @wibear

                                            Unterstützt pivCCU RaspberryOS 11 überhaupt? Oder wird sich da auf die jeweils aktuelle stable beschränkt?

                                            W 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate
                                            FAQ Cloud / IOT
                                            HowTo: Node.js-Update
                                            HowTo: Backup/Restore
                                            Downloads
                                            BLOG

                                            394
                                            Online

                                            31.6k
                                            Users

                                            79.5k
                                            Topics

                                            1.3m
                                            Posts

                                            7
                                            63
                                            1895
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo