Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. admin nach restore nicht erreichbar

NEWS

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    16
    1
    1.1k

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    13
    1
    720

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    25
    1
    2.0k

admin nach restore nicht erreichbar

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
16 Beiträge 4 Kommentatoren 51 Aufrufe 3 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde aufgespalten von ioBroker nach Restore nicht erreichbar Homoran
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • E Online
    E Online
    ece87
    schrieb zuletzt editiert von ece87
    #6

    Danke so hat es geklappt hab es in eine *txt Datei gespeichert.
    iob diag.txt

    ```bash
    Script v.2025-08-09
    
    *** BASE SYSTEM ***
    Operating System: Raspbian GNU/Linux 13 (trixie)
     Static hostname: Raspberry
           Icon name: computer
              Kernel: Linux 6.12.47+rpt-rpi-v8
        Architecture: arm64
    OS is similar to: debian
    
    Model           : Raspberry Pi 4 Model B Rev 1.2
    Docker          : false
    Virtualization  : none
    Kernel          : aarch64
    Userland        : 32 bit
    
    Systemuptime and Load:
     16:43:28 up 1 min,  1 user,  load average: 0.66, 0.26, 0.09
    CPU threads: 4
    
    
    *** LIFE CYCLE STATUS ***
    Operating System is the current Debian stable version codenamed 'trixie'!
    
    *** RASPBERRY THROTTLING ***
    Current issues:
    No throttling issues detected.
    
    Previously detected issues:
    No throttling issues detected.
    
    *** TIME AND TIMEZONES ***
                   Local time: Thu 2026-01-15 16:43:28 CET
               Universal time: Thu 2026-01-15 15:43:28 UTC
                     RTC time: n/a
                    Time zone: Europe/Berlin (CET, +0100)
    System clock synchronized: yes
                  NTP service: active
              RTC in local TZ: no
    
    *** Users and Groups ***
    User that called 'iob diag':
    raspberryio
    HOME=/home/raspberryio
    GROUPS=raspberryio adm dialout cdrom sudo audio video plugdev games users netdev gpio i2c spi render input iobroker
    
    User that is running 'js-controller':
    iobroker
    HOME=/home/iobroker
    SUDO_HOME=/home/raspberryio
    GROUPS=iobroker tty dialout audio video plugdev bluetooth redis gpio i2c
    
    *** DISPLAY-SERVER SETUP ***
    Display-Server:         false
    Unit display-manager.service could not be found.
    Display-Manager:
    Desktop:
    Session:                tty
    
    *** MEMORY ***
                   total        used        free      shared  buff/cache   available
    Mem:            4.0G        321M        3.4G        9.7M        285M        3.7G
    Swap:           2.1G          0B        2.1G
    Total:          6.1G        321M        5.6G
    
    Active iob-Instances:   2
    
             3796 M total memory
              306 M used memory
              279 M active memory
              107 M inactive memory
             3289 M free memory
               40 M buffer memory
              231 M swap cache
             2047 M total swap
                0 M used swap
             2047 M free swap
    
    *** top - Table Of Processes  ***
    top - 16:43:29 up 1 min,  1 user,  load average: 0.66, 0.26, 0.09
    Tasks: 193 total,   1 running, 192 sleeping,   0 stopped,   0 zombie
    %Cpu(s):  4.0 us,  0.0 sy,  0.0 ni, 94.0 id,  2.0 wa,  0.0 hi,  0.0 si,  0.0 st
    MiB Mem :   3796.7 total,   3287.6 free,    307.6 used,    272.3 buff/cache
    MiB Swap:   2048.0 total,   2048.0 free,      0.0 used.   3489.1 avail Mem
    
    *** FAILED SERVICES ***
    
      UNIT LOAD ACTIVE SUB DESCRIPTION
    
    0 loaded units listed.
    
    
    *** DMESG CRITICAL ERRORS ***
    No critical errors detected
    
    *** FILESYSTEM ***
    Filesystem     Type      Size  Used Avail Use% Mounted on
    udev           devtmpfs  1.6G     0  1.6G   0% /dev
    tmpfs          tmpfs     760M  9.3M  751M   2% /run
    /dev/mmcblk0p2 ext4       58G  5.5G   51G  10% /
    tmpfs          tmpfs     1.9G     0  1.9G   0% /dev/shm
    tmpfs          tmpfs     5.0M   16K  5.0M   1% /run/lock
    tmpfs          tmpfs     1.0M     0  1.0M   0% /run/credentials/systemd-journald.service
    tmpfs          tmpfs     1.9G     0  1.9G   0% /tmp
    /dev/mmcblk0p1 vfat      510M   78M  433M  16% /boot/firmware
    tmpfs          tmpfs     1.0M     0  1.0M   0% /run/credentials/serial-getty@ttyS0.service
    tmpfs          tmpfs     1.0M     0  1.0M   0% /run/credentials/getty@tty1.service
    tmpfs          tmpfs     380M  8.0K  380M   1% /run/user/1000
    
    Messages concerning ext4 filesystem in dmesg:
    [Thu Jan 15 16:42:05 2026] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_headphones=0 cgroup_disable=memory numa_policy=interleave nvme.max_host_mem_size_mb=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0  numa=fake=2 system_heap.max_order=0 smsc95xx.macaddr=E4:5F:01:04:54:66 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  console=ttyS0,115200 console=tty1 root=PARTUUID=a8836640-02 rootfstype=ext4 fsck.repair=yes rootwait cfg80211.ieee80211_regdom=DE
    [Thu Jan 15 16:42:09 2026] EXT4-fs (mmcblk0p2): orphan cleanup on readonly fs
    [Thu Jan 15 16:42:09 2026] EXT4-fs (mmcblk0p2): mounted filesystem a76206bf-fc14-4209-834e-7fc7275f6735 ro with ordered data mode. Quota mode: none.
    [Thu Jan 15 16:42:12 2026] EXT4-fs (mmcblk0p2): re-mounted a76206bf-fc14-4209-834e-7fc7275f6735 r/w.
    
    Show mounted filesystems:
    TARGET           SOURCE         FSTYPE OPTIONS
    /                /dev/mmcblk0p2 ext4   rw,noatime
    `-/boot/firmware /dev/mmcblk0p1 vfat   rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro
    
    Files in neuralgic directories:
    
    /var:
    2.4G    /var/
    187M    /var/cache
    182M    /var/cache/apt
    122M    /var/lib
    97M     /var/cache/apt/archives
    
    Archived and active journals take up 8M in the file system.
    
    /opt/iobroker/backups:
    13M     /opt/iobroker/backups/
    
    /opt/iobroker/iobroker-data:
    268M    /opt/iobroker/iobroker-data/
    257M    /opt/iobroker/iobroker-data/files
    51M     /opt/iobroker/iobroker-data/files/javascript.admin
    47M     /opt/iobroker/iobroker-data/files/admin.admin
    46M     /opt/iobroker/iobroker-data/files/admin.admin/custom/assets
    
    The five largest files in iobroker-data are:
    11M     /opt/iobroker/iobroker-data/objects.jsonl
    9.8M    /opt/iobroker/iobroker-data/files/vis-2/material-icons/knx-uf.json
    8.1M    /opt/iobroker/iobroker-data/files/backitup.admin/assets/index-Djx0nwYT.js
    6.9M    /opt/iobroker/iobroker-data/files/javascript.admin/static/js/610.de0231c9.chunk.js.map
    4.9M    /opt/iobroker/iobroker-data/files/javascript.admin/static/js/848.7424922d.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'
    
    Zigbee Network Settings on your coordinator/in nvbackup are:
    
    zigbee.X
    Extended Pan ID:
    *** MASKED ***
    Pan ID:
    *** MASKED ***
    Channel:
    *** MASKED ***
    Network Key:
    *** MASKED ***
    
    To unmask the settings run 'iob diag --unmask'
    
    
    *** NodeJS-Installation ***
    
    /usr/bin/nodejs         v20.19.2
    /usr/bin/node           v20.19.2
    /usr/bin/npm            9.2.0
    /usr/bin/npx            9.2.0
    /usr/bin/corepack       0.24.0
    
    nodejs:
      Installed: 20.19.2+dfsg-1+rpi1
      Candidate: 20.19.2+dfsg-1+rpi1
      Version table:
     *** 20.19.2+dfsg-1+rpi1 500
            500 http://raspbian.raspberrypi.com/raspbian trixie/main armhf Packages
            100 /var/lib/dpkg/status
    
    Temp directories causing deletion problem: 0
    No problems detected
    
    Errors in npm tree: 0
    No problems detected
    
    Checking for nodejs vulnerability:
    
    
    ██████   █████  ███    ██  ██████  ███████ ███████
    ██   ██ ██   ██ ████   ██ ██       ██      ██   ██
    ██   ██ ███████ ██ ██  ██ ██   ███ █████   ███████
    ██   ██ ██   ██ ██  ██ ██ ██    ██ ██      ██   ██
    ██████  ██   ██ ██   ████  ██████  ███████ ██   ██
    
    
    The current Node.js version (v20.19.2) is vulnerable to the following CVEs:
    
    CVE-2025-55130(high): A flaw in Node.js’s Permissions model allows attackers to bypass `--allow-fs-read` and `--allow-fs-write` restrictions using crafted relative symlink paths. By chaining directories and symlinks, a script granted access only to the current directory can escape the allowed path and read sensitive files. This breaks the expected isolation guarantees and enables arbitrary file read/write, leading to potential system compromise.
    This vulnerability affects users of the permission model on Node.js v20,  v22,  v24, and v25.
    Patched versions: ^20.20.0 || ^22.22.0 || ^24.13.0 || ^25.3.0
    =
    
    CVE-2025-55131(high): A flaw in Node.js's buffer allocation logic can expose uninitialized memory when allocations are interrupted, when using the `vm` module with the timeout option. Under specific timing conditions, buffers allocated with `Buffer.alloc` and other `TypedArray` instances like `Uint8Array` may contain leftover data from previous operations, allowing in-process secrets like tokens or passwords to leak or causing data corruption. While exploitation typically requires precise timing or in-process code execution, it can become remotely exploitable when untrusted input influences workload and timeouts, leading to potential confidentiality and integrity impact.
    Patched versions: ^20.20.0 || ^22.22.0 || ^24.13.0 || ^25.3.0
    =
    
    CVE-2025-55132(low): A flaw in Node.js's permission model allows a file's access and modification timestamps to be changed via `futimes()` even when the process has only read permissions. Unlike `utimes()`, `futimes()` does not apply the expected write-permission checks, which means file metadata can be modified in read-only directories. This behavior could be used to alter timestamps in ways that obscure activity, reducing the reliability of logs. This vulnerability affects users of the permission model on Node.js v20,  v22,  v24, and v25.
    Patched versions: ^20.20.0 || ^22.22.0 || ^24.13.0 || ^25.3.0
    =
    
    CVE-2025-59465(high): A malformed `HTTP/2 HEADERS` frame with oversized, invalid `HPACK` data can cause Node.js to crash by triggering an unhandled `TLSSocket` error `ECONNRESET`. Instead of safely closing the connection, the process crashes, enabling a remote denial of service. This primarily affects applications that do not attach explicit error handlers to secure sockets, for example:
    

    server.on('secureConnection', socket => {
    socket.on('error', err => {
    console.log(err)
    })
    })

    Patched versions: ^20.20.0 || ^22.22.0 || ^24.13.0 || ^25.3.0
    =
    
    CVE-2025-59466(medium): We have identified a bug in Node.js error handling where "Maximum call stack size exceeded" errors become uncatchable when `async_hooks.createHook()` is enabled. Instead of reaching `process.on('uncaughtException')`, the process terminates, making the crash unrecoverable. Applications that rely on `AsyncLocalStorage` (v22, v20) or `async_hooks.createHook()` (v24, v22, v20) become vulnerable to denial-of-service crashes triggered by deep recursion under specific conditions.
    Patched versions: ^20.20.0 || ^22.22.0 || ^24.13.0 || ^25.3.0
    =
    
    CVE-2026-21637(medium): A flaw in Node.js TLS error handling allows remote attackers to crash or exhaust resources of a TLS server when `pskCallback` or `ALPNCallback` are in use. Synchronous exceptions thrown during these callbacks bypass standard TLS error handling paths (tlsClientError and error), causing either immediate process termination or silent file descriptor leaks that eventually lead to denial of service. Because these callbacks process attacker-controlled input during the TLS handshake, a remote client can repeatedly trigger the issue. This vulnerability affects TLS servers using PSK or ALPN callbacks across Node.js versions where these callbacks throw without being safely wrapped.
    Patched versions: ^20.20.0 || ^22.22.0 || ^24.13.0 || ^25.3.0
    =
    
    *** ioBroker-Installation ***
    
    ioBroker Status
    iobroker is running on this host.
    
    
    Objects type: jsonl
    States  type: jsonl
    
    Hosts:
    Raspberry           Raspberry (version: 7.0.7, hostname: Raspberry     , alive, uptime: 82)
    
    Core adapters versions
    js-controller:  7.0.7
    admin:          6.3.5
    javascript:     6.1.4
    
    nodejs modules from github:     1
    +-- iobroker.tuya@3.14.0 (git+ssh://git@github.com/Apollon77/ioBroker.tuya.git#43f4c1b9bd2f1693f2a1160bc5423b0611c0a143)
    
    Adapter State
      system.adapter.admin.0                  : admin                 : Raspberry                                -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
    + system.adapter.backitup.0               : backitup              : Raspberry                                -  enabled
      system.adapter.cloud.0                  : cloud                 : Raspberry                                - disabled
      system.adapter.discovery.0              : discovery             : Raspberry                                - disabled
      system.adapter.icons-addictive-flavour-png.0: icons-addictive-flavour-png: Raspberry                                - disabled
      system.adapter.icons-icons8.0           : icons-icons8          : Raspberry                                - disabled
      system.adapter.icons-ultimate-png.0     : icons-ultimate-png    : Raspberry                                - disabled
      system.adapter.iqontrol.0               : iqontrol              : Raspberry                                - disabled
      system.adapter.javascript.0             : javascript            : Raspberry                                - disabled
      system.adapter.shelly.0                 : shelly                : Raspberry                                - disabled, port: 1882, bind: 0.0.0.0
      system.adapter.shelly.1                 : shelly                : Raspberry                                - disabled, port: 1882, bind: 0.0.0.0
      system.adapter.sonnen.0                 : sonnen                : Raspberry                                - disabled
      system.adapter.tuya.0                   : tuya                  : Raspberry                                - disabled
      system.adapter.vis-hqwidgets.0          : vis-hqwidgets         : Raspberry                                - disabled
      system.adapter.vis-icontwo.0            : vis-icontwo           : Raspberry                                - disabled
      system.adapter.vis-inventwo.0           : vis-inventwo          : Raspberry                                - disabled
      system.adapter.vis-metro.0              : vis-metro             : Raspberry                                - disabled
      system.adapter.vis-timeandweather.0     : vis-timeandweather    : Raspberry                                - disabled
      system.adapter.vis.0                    : vis                   : Raspberry                                - disabled
      system.adapter.web.0                    : web                   : Raspberry                                - disabled, port: 8082, bind: 192.168.178.55, run as: admin
    
    + instance is alive
    
    Enabled adapters with bindings
      system.adapter.admin.0                  : admin                 : Raspberry                                -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
    
    ioBroker-Repositories
    ┌─────────┬──────────┬─────────────────────────────────────────────────────────┬──────────────┐
    │ (index) │ name     │ url                                                     │ auto upgrade │
    ├─────────┼──────────┼─────────────────────────────────────────────────────────┼──────────────┤
    │ 0       │ 'stable' │ 'http://download.iobroker.net/sources-dist.json'        │ false        │
    │ 1       │ 'beta'   │ 'http://download.iobroker.net/sources-dist-latest.json' │ false        │
    └─────────┴──────────┴─────────────────────────────────────────────────────────┴──────────────┘
    
    Active repo(s): beta
    Upgrade policy: none
    
    Installed ioBroker-Adapters
    Used repository: beta
    Adapter    "admin"        : 7.7.22   , installed 6.3.5  [Updatable]
    Adapter    "backitup"     : 3.3.13   , installed 2.5.10 [Updatable]
    Adapter    "cloud"        : 5.1.2    , installed 4.3.0  [Updatable]
    Adapter    "discovery"    : 5.0.0    , installed 3.1.0  [Updatable]
    Adapter    "icons-addictive-flavour-png": 0.1.0, installed 0.1.0
    Adapter    "icons-icons8" : 0.0.1    , installed 0.0.1
    Adapter    "icons-ultimate-png": 1.0.1, installed 1.0.1
    Adapter    "iqontrol"     : 3.0.0    , installed 2.0.0  [Updatable]
    Adapter    "javascript"   : 9.0.18   , installed 6.1.4  [Updatable]
    Controller "js-controller": 7.1.0    , installed 7.0.7  [Updatable]
    Adapter    "shelly"       : 10.5.2   , installed 6.4.1  [Updatable]
    Adapter    "simple-api"   : 3.0.7    , installed 2.8.0  [Updatable]
    Adapter    "socketio"     : 7.0.8    , installed 4.2.0  [Updatable]
    Adapter    "sonnen"       : 1.18.1   , installed 1.15.6 [Updatable]
    Adapter    "tuya"         : 3.17.0   , installed 3.14.0 [Updatable]
    Adapter    "vis"          : 1.5.6    , installed 1.4.15 [Updatable]
    Adapter    "vis-hqwidgets": 1.6.0    , installed 1.3.0  [Updatable]
    Adapter    "vis-icontwo"  : 1.18.0   , installed 0.90.0 [Updatable]
    Adapter    "vis-inventwo" : 3.3.5    , installed 3.3.1  [Updatable]
    Adapter    "vis-metro"    : 1.2.0    , installed 1.2.0
    Adapter    "vis-timeandweather": 1.2.2, installed 1.2.2
    Adapter    "web"          : 7.0.9    , installed 4.3.0  [Updatable]
    Adapter    "ws"           : 3.0.19   , installed 1.3.0  [Updatable]
    
    Objects and States
    Please stand by - This may take a while
    Objects:        1037
    States:         747
    
    *** OS-Repositories and Updates ***
    Hit:1 http://archive.raspberrypi.com/debian trixie InRelease
    Hit:2 http://raspbian.raspberrypi.com/raspbian trixie InRelease
    Reading package lists...
    Pending Updates: 27
    
    *** 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          8534       1122/sshd: /usr/sbi
    tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN      0          150        1/init
    tcp        0      0 127.0.0.1:9001          0.0.0.0:*               LISTEN      1001       9483       1133/iobroker.js-co
    tcp        0      0 127.0.0.1:9000          0.0.0.0:*               LISTEN      1001       9488       1133/iobroker.js-co
    tcp        0      0 127.0.0.1:6379          0.0.0.0:*               LISTEN      104        9390       1110/redis-server 1
    tcp6       0      0 :::22                   :::*                    LISTEN      0          8536       1122/sshd: /usr/sbi
    tcp6       0      0 :::111                  :::*                    LISTEN      0          1569       1/init
    tcp6       0      0 ::1:6379                :::*                    LISTEN      104        9391       1110/redis-server 1
    udp        0      0 0.0.0.0:59166           0.0.0.0:*                           101        6574       614/avahi-daemon: r
    udp        0      0 0.0.0.0:111             0.0.0.0:*                           0          5031       1/init
    udp        0      0 0.0.0.0:5353            0.0.0.0:*                           101        6572       614/avahi-daemon: r
    udp6       0      0 :::111                  :::*                                0          151        1/init
    udp6       0      0 :::57932                :::*                                101        6575       614/avahi-daemon: r
    udp6       0      0 :::5353                 :::*                                101        6573       614/avahi-daemon: r
    
    *** Log File - Last 25 Lines ***
    
    2026-01-15 16:42:16.505  - info: host.Raspberry added notifications configuration of host
    2026-01-15 16:42:17.382  - info: host.Raspberry 20 instances found
    2026-01-15 16:42:17.430  - info: host.Raspberry starting 2 instances
    2026-01-15 16:42:18.342  - info: host.Raspberry instance system.adapter.admin.0 in version "6.3.5" started with pid 1175
    2026-01-15 16:42:22.526  - info: host.Raspberry instance system.adapter.backitup.0 in version "2.5.10" started with pid 1187
    2026-01-15 16:42:23.515  - info: admin.0 (1175) starting. Version 6.3.5 in /opt/iobroker/node_modules/iobroker.admin, node: v20.19.2, js-controller: 7.0.7
    2026-01-15 16:42:23.594  - info: admin.0 (1175) requesting all states
    2026-01-15 16:42:23.596  - info: admin.0 (1175) requesting all objects
    2026-01-15 16:42:25.512  - info: admin.0 (1175) received all objects
    2026-01-15 16:42:25.816  - error: admin.0 (1175) Cannot create web-server: TypeError: Cannot read properties of undefined (reading 'createServerAsync')
    2026-01-15 16:42:25.823  - info: admin.0 (1175) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
    2026-01-15 16:42:26.735  - info: admin.0 (1175) Request actual repository...
    2026-01-15 16:42:26.781  - info: admin.0 (1175) Repository received successfully.
    2026-01-15 16:42:27.111  - warn: admin.0 (1175) redis get admin.0.info.newsFeed, error - Connection is closed.
    2026-01-15 16:42:27.145  - warn: admin.0 (1175) get state error: Connection is closed.
    2026-01-15 16:42:27.147  - warn: admin.0 (1175) get state error: Connection is closed.
    2026-01-15 16:42:27.149  - warn: admin.0 (1175) get state error: Connection is closed.
    2026-01-15 16:42:27.151  - warn: admin.0 (1175) get state error: Connection is closed.
    2026-01-15 16:42:27.153  - warn: admin.0 (1175) get state error: Connection is closed.
    2026-01-15 16:42:27.159  - error: admin.0 (1175) Cannot update news: Error: DB closed
    2026-01-15 16:42:27.172  - info: admin.0 (1175) terminating http server on port 8081
    2026-01-15 16:42:27.262  - info: host.Raspberry instance system.adapter.admin.0 terminated by request of the instance itself and will not be restarted, before user restarts it.
    2026-01-15 16:42:27.264  - info: host.Raspberry Do not restart adapter system.adapter.admin.0 because desired by instance
    2026-01-15 16:42:27.947  - info: backitup.0 (1187) starting. Version 2.5.10 in /opt/iobroker/node_modules/iobroker.backitup, node: v20.19.2, js-controller: 7.0.7
    2026-01-15 16:42:28.066  - info: backitup.0 (1187) [iobroker] backup was activated at 02:40 every 1 day(s)
    
    Thomas BraunT HomoranH 2 Antworten Letzte Antwort
    0
    • H Offline
      H Offline
      HJRoe
      schrieb zuletzt editiert von
      #7

      Hallo,
      ich hatte ein ähnliches Problem. Ich musste IOB von Hand neu starten, da das alte Binding übernommen wurde!!
      Vielleicht hilft dieser Befehl im Terminal:

      iob list instances --allow-root
      Ja, man sollte nicht als root...

      7f154f44-37de-465e-ae13-6d29c8709f88-grafik.png
      f3d3a0ff-2a20-4fe3-b4a2-aee2b713a139-grafik.png
      Danach hat der Neustart funktioniert
      HJR

      Thomas BraunT 1 Antwort Letzte Antwort
      0
      • E ece87

        Danke so hat es geklappt hab es in eine *txt Datei gespeichert.
        iob diag.txt

        ```bash
        Script v.2025-08-09
        
        *** BASE SYSTEM ***
        Operating System: Raspbian GNU/Linux 13 (trixie)
         Static hostname: Raspberry
               Icon name: computer
                  Kernel: Linux 6.12.47+rpt-rpi-v8
            Architecture: arm64
        OS is similar to: debian
        
        Model           : Raspberry Pi 4 Model B Rev 1.2
        Docker          : false
        Virtualization  : none
        Kernel          : aarch64
        Userland        : 32 bit
        
        Systemuptime and Load:
         16:43:28 up 1 min,  1 user,  load average: 0.66, 0.26, 0.09
        CPU threads: 4
        
        
        *** LIFE CYCLE STATUS ***
        Operating System is the current Debian stable version codenamed 'trixie'!
        
        *** RASPBERRY THROTTLING ***
        Current issues:
        No throttling issues detected.
        
        Previously detected issues:
        No throttling issues detected.
        
        *** TIME AND TIMEZONES ***
                       Local time: Thu 2026-01-15 16:43:28 CET
                   Universal time: Thu 2026-01-15 15:43:28 UTC
                         RTC time: n/a
                        Time zone: Europe/Berlin (CET, +0100)
        System clock synchronized: yes
                      NTP service: active
                  RTC in local TZ: no
        
        *** Users and Groups ***
        User that called 'iob diag':
        raspberryio
        HOME=/home/raspberryio
        GROUPS=raspberryio adm dialout cdrom sudo audio video plugdev games users netdev gpio i2c spi render input iobroker
        
        User that is running 'js-controller':
        iobroker
        HOME=/home/iobroker
        SUDO_HOME=/home/raspberryio
        GROUPS=iobroker tty dialout audio video plugdev bluetooth redis gpio i2c
        
        *** DISPLAY-SERVER SETUP ***
        Display-Server:         false
        Unit display-manager.service could not be found.
        Display-Manager:
        Desktop:
        Session:                tty
        
        *** MEMORY ***
                       total        used        free      shared  buff/cache   available
        Mem:            4.0G        321M        3.4G        9.7M        285M        3.7G
        Swap:           2.1G          0B        2.1G
        Total:          6.1G        321M        5.6G
        
        Active iob-Instances:   2
        
                 3796 M total memory
                  306 M used memory
                  279 M active memory
                  107 M inactive memory
                 3289 M free memory
                   40 M buffer memory
                  231 M swap cache
                 2047 M total swap
                    0 M used swap
                 2047 M free swap
        
        *** top - Table Of Processes  ***
        top - 16:43:29 up 1 min,  1 user,  load average: 0.66, 0.26, 0.09
        Tasks: 193 total,   1 running, 192 sleeping,   0 stopped,   0 zombie
        %Cpu(s):  4.0 us,  0.0 sy,  0.0 ni, 94.0 id,  2.0 wa,  0.0 hi,  0.0 si,  0.0 st
        MiB Mem :   3796.7 total,   3287.6 free,    307.6 used,    272.3 buff/cache
        MiB Swap:   2048.0 total,   2048.0 free,      0.0 used.   3489.1 avail Mem
        
        *** FAILED SERVICES ***
        
          UNIT LOAD ACTIVE SUB DESCRIPTION
        
        0 loaded units listed.
        
        
        *** DMESG CRITICAL ERRORS ***
        No critical errors detected
        
        *** FILESYSTEM ***
        Filesystem     Type      Size  Used Avail Use% Mounted on
        udev           devtmpfs  1.6G     0  1.6G   0% /dev
        tmpfs          tmpfs     760M  9.3M  751M   2% /run
        /dev/mmcblk0p2 ext4       58G  5.5G   51G  10% /
        tmpfs          tmpfs     1.9G     0  1.9G   0% /dev/shm
        tmpfs          tmpfs     5.0M   16K  5.0M   1% /run/lock
        tmpfs          tmpfs     1.0M     0  1.0M   0% /run/credentials/systemd-journald.service
        tmpfs          tmpfs     1.9G     0  1.9G   0% /tmp
        /dev/mmcblk0p1 vfat      510M   78M  433M  16% /boot/firmware
        tmpfs          tmpfs     1.0M     0  1.0M   0% /run/credentials/serial-getty@ttyS0.service
        tmpfs          tmpfs     1.0M     0  1.0M   0% /run/credentials/getty@tty1.service
        tmpfs          tmpfs     380M  8.0K  380M   1% /run/user/1000
        
        Messages concerning ext4 filesystem in dmesg:
        [Thu Jan 15 16:42:05 2026] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_headphones=0 cgroup_disable=memory numa_policy=interleave nvme.max_host_mem_size_mb=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0  numa=fake=2 system_heap.max_order=0 smsc95xx.macaddr=E4:5F:01:04:54:66 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  console=ttyS0,115200 console=tty1 root=PARTUUID=a8836640-02 rootfstype=ext4 fsck.repair=yes rootwait cfg80211.ieee80211_regdom=DE
        [Thu Jan 15 16:42:09 2026] EXT4-fs (mmcblk0p2): orphan cleanup on readonly fs
        [Thu Jan 15 16:42:09 2026] EXT4-fs (mmcblk0p2): mounted filesystem a76206bf-fc14-4209-834e-7fc7275f6735 ro with ordered data mode. Quota mode: none.
        [Thu Jan 15 16:42:12 2026] EXT4-fs (mmcblk0p2): re-mounted a76206bf-fc14-4209-834e-7fc7275f6735 r/w.
        
        Show mounted filesystems:
        TARGET           SOURCE         FSTYPE OPTIONS
        /                /dev/mmcblk0p2 ext4   rw,noatime
        `-/boot/firmware /dev/mmcblk0p1 vfat   rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro
        
        Files in neuralgic directories:
        
        /var:
        2.4G    /var/
        187M    /var/cache
        182M    /var/cache/apt
        122M    /var/lib
        97M     /var/cache/apt/archives
        
        Archived and active journals take up 8M in the file system.
        
        /opt/iobroker/backups:
        13M     /opt/iobroker/backups/
        
        /opt/iobroker/iobroker-data:
        268M    /opt/iobroker/iobroker-data/
        257M    /opt/iobroker/iobroker-data/files
        51M     /opt/iobroker/iobroker-data/files/javascript.admin
        47M     /opt/iobroker/iobroker-data/files/admin.admin
        46M     /opt/iobroker/iobroker-data/files/admin.admin/custom/assets
        
        The five largest files in iobroker-data are:
        11M     /opt/iobroker/iobroker-data/objects.jsonl
        9.8M    /opt/iobroker/iobroker-data/files/vis-2/material-icons/knx-uf.json
        8.1M    /opt/iobroker/iobroker-data/files/backitup.admin/assets/index-Djx0nwYT.js
        6.9M    /opt/iobroker/iobroker-data/files/javascript.admin/static/js/610.de0231c9.chunk.js.map
        4.9M    /opt/iobroker/iobroker-data/files/javascript.admin/static/js/848.7424922d.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'
        
        Zigbee Network Settings on your coordinator/in nvbackup are:
        
        zigbee.X
        Extended Pan ID:
        *** MASKED ***
        Pan ID:
        *** MASKED ***
        Channel:
        *** MASKED ***
        Network Key:
        *** MASKED ***
        
        To unmask the settings run 'iob diag --unmask'
        
        
        *** NodeJS-Installation ***
        
        /usr/bin/nodejs         v20.19.2
        /usr/bin/node           v20.19.2
        /usr/bin/npm            9.2.0
        /usr/bin/npx            9.2.0
        /usr/bin/corepack       0.24.0
        
        nodejs:
          Installed: 20.19.2+dfsg-1+rpi1
          Candidate: 20.19.2+dfsg-1+rpi1
          Version table:
         *** 20.19.2+dfsg-1+rpi1 500
                500 http://raspbian.raspberrypi.com/raspbian trixie/main armhf Packages
                100 /var/lib/dpkg/status
        
        Temp directories causing deletion problem: 0
        No problems detected
        
        Errors in npm tree: 0
        No problems detected
        
        Checking for nodejs vulnerability:
        
        
        ██████   █████  ███    ██  ██████  ███████ ███████
        ██   ██ ██   ██ ████   ██ ██       ██      ██   ██
        ██   ██ ███████ ██ ██  ██ ██   ███ █████   ███████
        ██   ██ ██   ██ ██  ██ ██ ██    ██ ██      ██   ██
        ██████  ██   ██ ██   ████  ██████  ███████ ██   ██
        
        
        The current Node.js version (v20.19.2) is vulnerable to the following CVEs:
        
        CVE-2025-55130(high): A flaw in Node.js’s Permissions model allows attackers to bypass `--allow-fs-read` and `--allow-fs-write` restrictions using crafted relative symlink paths. By chaining directories and symlinks, a script granted access only to the current directory can escape the allowed path and read sensitive files. This breaks the expected isolation guarantees and enables arbitrary file read/write, leading to potential system compromise.
        This vulnerability affects users of the permission model on Node.js v20,  v22,  v24, and v25.
        Patched versions: ^20.20.0 || ^22.22.0 || ^24.13.0 || ^25.3.0
        =
        
        CVE-2025-55131(high): A flaw in Node.js's buffer allocation logic can expose uninitialized memory when allocations are interrupted, when using the `vm` module with the timeout option. Under specific timing conditions, buffers allocated with `Buffer.alloc` and other `TypedArray` instances like `Uint8Array` may contain leftover data from previous operations, allowing in-process secrets like tokens or passwords to leak or causing data corruption. While exploitation typically requires precise timing or in-process code execution, it can become remotely exploitable when untrusted input influences workload and timeouts, leading to potential confidentiality and integrity impact.
        Patched versions: ^20.20.0 || ^22.22.0 || ^24.13.0 || ^25.3.0
        =
        
        CVE-2025-55132(low): A flaw in Node.js's permission model allows a file's access and modification timestamps to be changed via `futimes()` even when the process has only read permissions. Unlike `utimes()`, `futimes()` does not apply the expected write-permission checks, which means file metadata can be modified in read-only directories. This behavior could be used to alter timestamps in ways that obscure activity, reducing the reliability of logs. This vulnerability affects users of the permission model on Node.js v20,  v22,  v24, and v25.
        Patched versions: ^20.20.0 || ^22.22.0 || ^24.13.0 || ^25.3.0
        =
        
        CVE-2025-59465(high): A malformed `HTTP/2 HEADERS` frame with oversized, invalid `HPACK` data can cause Node.js to crash by triggering an unhandled `TLSSocket` error `ECONNRESET`. Instead of safely closing the connection, the process crashes, enabling a remote denial of service. This primarily affects applications that do not attach explicit error handlers to secure sockets, for example:
        

        server.on('secureConnection', socket => {
        socket.on('error', err => {
        console.log(err)
        })
        })

        Patched versions: ^20.20.0 || ^22.22.0 || ^24.13.0 || ^25.3.0
        =
        
        CVE-2025-59466(medium): We have identified a bug in Node.js error handling where "Maximum call stack size exceeded" errors become uncatchable when `async_hooks.createHook()` is enabled. Instead of reaching `process.on('uncaughtException')`, the process terminates, making the crash unrecoverable. Applications that rely on `AsyncLocalStorage` (v22, v20) or `async_hooks.createHook()` (v24, v22, v20) become vulnerable to denial-of-service crashes triggered by deep recursion under specific conditions.
        Patched versions: ^20.20.0 || ^22.22.0 || ^24.13.0 || ^25.3.0
        =
        
        CVE-2026-21637(medium): A flaw in Node.js TLS error handling allows remote attackers to crash or exhaust resources of a TLS server when `pskCallback` or `ALPNCallback` are in use. Synchronous exceptions thrown during these callbacks bypass standard TLS error handling paths (tlsClientError and error), causing either immediate process termination or silent file descriptor leaks that eventually lead to denial of service. Because these callbacks process attacker-controlled input during the TLS handshake, a remote client can repeatedly trigger the issue. This vulnerability affects TLS servers using PSK or ALPN callbacks across Node.js versions where these callbacks throw without being safely wrapped.
        Patched versions: ^20.20.0 || ^22.22.0 || ^24.13.0 || ^25.3.0
        =
        
        *** ioBroker-Installation ***
        
        ioBroker Status
        iobroker is running on this host.
        
        
        Objects type: jsonl
        States  type: jsonl
        
        Hosts:
        Raspberry           Raspberry (version: 7.0.7, hostname: Raspberry     , alive, uptime: 82)
        
        Core adapters versions
        js-controller:  7.0.7
        admin:          6.3.5
        javascript:     6.1.4
        
        nodejs modules from github:     1
        +-- iobroker.tuya@3.14.0 (git+ssh://git@github.com/Apollon77/ioBroker.tuya.git#43f4c1b9bd2f1693f2a1160bc5423b0611c0a143)
        
        Adapter State
          system.adapter.admin.0                  : admin                 : Raspberry                                -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
        + system.adapter.backitup.0               : backitup              : Raspberry                                -  enabled
          system.adapter.cloud.0                  : cloud                 : Raspberry                                - disabled
          system.adapter.discovery.0              : discovery             : Raspberry                                - disabled
          system.adapter.icons-addictive-flavour-png.0: icons-addictive-flavour-png: Raspberry                                - disabled
          system.adapter.icons-icons8.0           : icons-icons8          : Raspberry                                - disabled
          system.adapter.icons-ultimate-png.0     : icons-ultimate-png    : Raspberry                                - disabled
          system.adapter.iqontrol.0               : iqontrol              : Raspberry                                - disabled
          system.adapter.javascript.0             : javascript            : Raspberry                                - disabled
          system.adapter.shelly.0                 : shelly                : Raspberry                                - disabled, port: 1882, bind: 0.0.0.0
          system.adapter.shelly.1                 : shelly                : Raspberry                                - disabled, port: 1882, bind: 0.0.0.0
          system.adapter.sonnen.0                 : sonnen                : Raspberry                                - disabled
          system.adapter.tuya.0                   : tuya                  : Raspberry                                - disabled
          system.adapter.vis-hqwidgets.0          : vis-hqwidgets         : Raspberry                                - disabled
          system.adapter.vis-icontwo.0            : vis-icontwo           : Raspberry                                - disabled
          system.adapter.vis-inventwo.0           : vis-inventwo          : Raspberry                                - disabled
          system.adapter.vis-metro.0              : vis-metro             : Raspberry                                - disabled
          system.adapter.vis-timeandweather.0     : vis-timeandweather    : Raspberry                                - disabled
          system.adapter.vis.0                    : vis                   : Raspberry                                - disabled
          system.adapter.web.0                    : web                   : Raspberry                                - disabled, port: 8082, bind: 192.168.178.55, run as: admin
        
        + instance is alive
        
        Enabled adapters with bindings
          system.adapter.admin.0                  : admin                 : Raspberry                                -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
        
        ioBroker-Repositories
        ┌─────────┬──────────┬─────────────────────────────────────────────────────────┬──────────────┐
        │ (index) │ name     │ url                                                     │ auto upgrade │
        ├─────────┼──────────┼─────────────────────────────────────────────────────────┼──────────────┤
        │ 0       │ 'stable' │ 'http://download.iobroker.net/sources-dist.json'        │ false        │
        │ 1       │ 'beta'   │ 'http://download.iobroker.net/sources-dist-latest.json' │ false        │
        └─────────┴──────────┴─────────────────────────────────────────────────────────┴──────────────┘
        
        Active repo(s): beta
        Upgrade policy: none
        
        Installed ioBroker-Adapters
        Used repository: beta
        Adapter    "admin"        : 7.7.22   , installed 6.3.5  [Updatable]
        Adapter    "backitup"     : 3.3.13   , installed 2.5.10 [Updatable]
        Adapter    "cloud"        : 5.1.2    , installed 4.3.0  [Updatable]
        Adapter    "discovery"    : 5.0.0    , installed 3.1.0  [Updatable]
        Adapter    "icons-addictive-flavour-png": 0.1.0, installed 0.1.0
        Adapter    "icons-icons8" : 0.0.1    , installed 0.0.1
        Adapter    "icons-ultimate-png": 1.0.1, installed 1.0.1
        Adapter    "iqontrol"     : 3.0.0    , installed 2.0.0  [Updatable]
        Adapter    "javascript"   : 9.0.18   , installed 6.1.4  [Updatable]
        Controller "js-controller": 7.1.0    , installed 7.0.7  [Updatable]
        Adapter    "shelly"       : 10.5.2   , installed 6.4.1  [Updatable]
        Adapter    "simple-api"   : 3.0.7    , installed 2.8.0  [Updatable]
        Adapter    "socketio"     : 7.0.8    , installed 4.2.0  [Updatable]
        Adapter    "sonnen"       : 1.18.1   , installed 1.15.6 [Updatable]
        Adapter    "tuya"         : 3.17.0   , installed 3.14.0 [Updatable]
        Adapter    "vis"          : 1.5.6    , installed 1.4.15 [Updatable]
        Adapter    "vis-hqwidgets": 1.6.0    , installed 1.3.0  [Updatable]
        Adapter    "vis-icontwo"  : 1.18.0   , installed 0.90.0 [Updatable]
        Adapter    "vis-inventwo" : 3.3.5    , installed 3.3.1  [Updatable]
        Adapter    "vis-metro"    : 1.2.0    , installed 1.2.0
        Adapter    "vis-timeandweather": 1.2.2, installed 1.2.2
        Adapter    "web"          : 7.0.9    , installed 4.3.0  [Updatable]
        Adapter    "ws"           : 3.0.19   , installed 1.3.0  [Updatable]
        
        Objects and States
        Please stand by - This may take a while
        Objects:        1037
        States:         747
        
        *** OS-Repositories and Updates ***
        Hit:1 http://archive.raspberrypi.com/debian trixie InRelease
        Hit:2 http://raspbian.raspberrypi.com/raspbian trixie InRelease
        Reading package lists...
        Pending Updates: 27
        
        *** 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          8534       1122/sshd: /usr/sbi
        tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN      0          150        1/init
        tcp        0      0 127.0.0.1:9001          0.0.0.0:*               LISTEN      1001       9483       1133/iobroker.js-co
        tcp        0      0 127.0.0.1:9000          0.0.0.0:*               LISTEN      1001       9488       1133/iobroker.js-co
        tcp        0      0 127.0.0.1:6379          0.0.0.0:*               LISTEN      104        9390       1110/redis-server 1
        tcp6       0      0 :::22                   :::*                    LISTEN      0          8536       1122/sshd: /usr/sbi
        tcp6       0      0 :::111                  :::*                    LISTEN      0          1569       1/init
        tcp6       0      0 ::1:6379                :::*                    LISTEN      104        9391       1110/redis-server 1
        udp        0      0 0.0.0.0:59166           0.0.0.0:*                           101        6574       614/avahi-daemon: r
        udp        0      0 0.0.0.0:111             0.0.0.0:*                           0          5031       1/init
        udp        0      0 0.0.0.0:5353            0.0.0.0:*                           101        6572       614/avahi-daemon: r
        udp6       0      0 :::111                  :::*                                0          151        1/init
        udp6       0      0 :::57932                :::*                                101        6575       614/avahi-daemon: r
        udp6       0      0 :::5353                 :::*                                101        6573       614/avahi-daemon: r
        
        *** Log File - Last 25 Lines ***
        
        2026-01-15 16:42:16.505  - info: host.Raspberry added notifications configuration of host
        2026-01-15 16:42:17.382  - info: host.Raspberry 20 instances found
        2026-01-15 16:42:17.430  - info: host.Raspberry starting 2 instances
        2026-01-15 16:42:18.342  - info: host.Raspberry instance system.adapter.admin.0 in version "6.3.5" started with pid 1175
        2026-01-15 16:42:22.526  - info: host.Raspberry instance system.adapter.backitup.0 in version "2.5.10" started with pid 1187
        2026-01-15 16:42:23.515  - info: admin.0 (1175) starting. Version 6.3.5 in /opt/iobroker/node_modules/iobroker.admin, node: v20.19.2, js-controller: 7.0.7
        2026-01-15 16:42:23.594  - info: admin.0 (1175) requesting all states
        2026-01-15 16:42:23.596  - info: admin.0 (1175) requesting all objects
        2026-01-15 16:42:25.512  - info: admin.0 (1175) received all objects
        2026-01-15 16:42:25.816  - error: admin.0 (1175) Cannot create web-server: TypeError: Cannot read properties of undefined (reading 'createServerAsync')
        2026-01-15 16:42:25.823  - info: admin.0 (1175) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
        2026-01-15 16:42:26.735  - info: admin.0 (1175) Request actual repository...
        2026-01-15 16:42:26.781  - info: admin.0 (1175) Repository received successfully.
        2026-01-15 16:42:27.111  - warn: admin.0 (1175) redis get admin.0.info.newsFeed, error - Connection is closed.
        2026-01-15 16:42:27.145  - warn: admin.0 (1175) get state error: Connection is closed.
        2026-01-15 16:42:27.147  - warn: admin.0 (1175) get state error: Connection is closed.
        2026-01-15 16:42:27.149  - warn: admin.0 (1175) get state error: Connection is closed.
        2026-01-15 16:42:27.151  - warn: admin.0 (1175) get state error: Connection is closed.
        2026-01-15 16:42:27.153  - warn: admin.0 (1175) get state error: Connection is closed.
        2026-01-15 16:42:27.159  - error: admin.0 (1175) Cannot update news: Error: DB closed
        2026-01-15 16:42:27.172  - info: admin.0 (1175) terminating http server on port 8081
        2026-01-15 16:42:27.262  - info: host.Raspberry instance system.adapter.admin.0 terminated by request of the instance itself and will not be restarted, before user restarts it.
        2026-01-15 16:42:27.264  - info: host.Raspberry Do not restart adapter system.adapter.admin.0 because desired by instance
        2026-01-15 16:42:27.947  - info: backitup.0 (1187) starting. Version 2.5.10 in /opt/iobroker/node_modules/iobroker.backitup, node: v20.19.2, js-controller: 7.0.7
        2026-01-15 16:42:28.066  - info: backitup.0 (1187) [iobroker] backup was activated at 02:40 every 1 day(s)
        
        Thomas BraunT Online
        Thomas BraunT Online
        Thomas Braun
        Most Active
        schrieb zuletzt editiert von Thomas Braun
        #8

        @ece87

        Installier das Betriebssytsem neu, diesmal dann als 64Bit-Version.

        Und ich vermute, dass deine Ausgangsbasis vollkommen veraltet ist und deswegen das ganze Ding in die Hose geht.
        Hat die alte Version redis verwendet?

        Linux-Werkzeugkasten:
        https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
        NodeJS Fixer Skript:
        https://forum.iobroker.net/topic/68035/iob-node-fix-skript
        iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

        1 Antwort Letzte Antwort
        0
        • E ece87

          Danke so hat es geklappt hab es in eine *txt Datei gespeichert.
          iob diag.txt

          ```bash
          Script v.2025-08-09
          
          *** BASE SYSTEM ***
          Operating System: Raspbian GNU/Linux 13 (trixie)
           Static hostname: Raspberry
                 Icon name: computer
                    Kernel: Linux 6.12.47+rpt-rpi-v8
              Architecture: arm64
          OS is similar to: debian
          
          Model           : Raspberry Pi 4 Model B Rev 1.2
          Docker          : false
          Virtualization  : none
          Kernel          : aarch64
          Userland        : 32 bit
          
          Systemuptime and Load:
           16:43:28 up 1 min,  1 user,  load average: 0.66, 0.26, 0.09
          CPU threads: 4
          
          
          *** LIFE CYCLE STATUS ***
          Operating System is the current Debian stable version codenamed 'trixie'!
          
          *** RASPBERRY THROTTLING ***
          Current issues:
          No throttling issues detected.
          
          Previously detected issues:
          No throttling issues detected.
          
          *** TIME AND TIMEZONES ***
                         Local time: Thu 2026-01-15 16:43:28 CET
                     Universal time: Thu 2026-01-15 15:43:28 UTC
                           RTC time: n/a
                          Time zone: Europe/Berlin (CET, +0100)
          System clock synchronized: yes
                        NTP service: active
                    RTC in local TZ: no
          
          *** Users and Groups ***
          User that called 'iob diag':
          raspberryio
          HOME=/home/raspberryio
          GROUPS=raspberryio adm dialout cdrom sudo audio video plugdev games users netdev gpio i2c spi render input iobroker
          
          User that is running 'js-controller':
          iobroker
          HOME=/home/iobroker
          SUDO_HOME=/home/raspberryio
          GROUPS=iobroker tty dialout audio video plugdev bluetooth redis gpio i2c
          
          *** DISPLAY-SERVER SETUP ***
          Display-Server:         false
          Unit display-manager.service could not be found.
          Display-Manager:
          Desktop:
          Session:                tty
          
          *** MEMORY ***
                         total        used        free      shared  buff/cache   available
          Mem:            4.0G        321M        3.4G        9.7M        285M        3.7G
          Swap:           2.1G          0B        2.1G
          Total:          6.1G        321M        5.6G
          
          Active iob-Instances:   2
          
                   3796 M total memory
                    306 M used memory
                    279 M active memory
                    107 M inactive memory
                   3289 M free memory
                     40 M buffer memory
                    231 M swap cache
                   2047 M total swap
                      0 M used swap
                   2047 M free swap
          
          *** top - Table Of Processes  ***
          top - 16:43:29 up 1 min,  1 user,  load average: 0.66, 0.26, 0.09
          Tasks: 193 total,   1 running, 192 sleeping,   0 stopped,   0 zombie
          %Cpu(s):  4.0 us,  0.0 sy,  0.0 ni, 94.0 id,  2.0 wa,  0.0 hi,  0.0 si,  0.0 st
          MiB Mem :   3796.7 total,   3287.6 free,    307.6 used,    272.3 buff/cache
          MiB Swap:   2048.0 total,   2048.0 free,      0.0 used.   3489.1 avail Mem
          
          *** FAILED SERVICES ***
          
            UNIT LOAD ACTIVE SUB DESCRIPTION
          
          0 loaded units listed.
          
          
          *** DMESG CRITICAL ERRORS ***
          No critical errors detected
          
          *** FILESYSTEM ***
          Filesystem     Type      Size  Used Avail Use% Mounted on
          udev           devtmpfs  1.6G     0  1.6G   0% /dev
          tmpfs          tmpfs     760M  9.3M  751M   2% /run
          /dev/mmcblk0p2 ext4       58G  5.5G   51G  10% /
          tmpfs          tmpfs     1.9G     0  1.9G   0% /dev/shm
          tmpfs          tmpfs     5.0M   16K  5.0M   1% /run/lock
          tmpfs          tmpfs     1.0M     0  1.0M   0% /run/credentials/systemd-journald.service
          tmpfs          tmpfs     1.9G     0  1.9G   0% /tmp
          /dev/mmcblk0p1 vfat      510M   78M  433M  16% /boot/firmware
          tmpfs          tmpfs     1.0M     0  1.0M   0% /run/credentials/serial-getty@ttyS0.service
          tmpfs          tmpfs     1.0M     0  1.0M   0% /run/credentials/getty@tty1.service
          tmpfs          tmpfs     380M  8.0K  380M   1% /run/user/1000
          
          Messages concerning ext4 filesystem in dmesg:
          [Thu Jan 15 16:42:05 2026] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_headphones=0 cgroup_disable=memory numa_policy=interleave nvme.max_host_mem_size_mb=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0  numa=fake=2 system_heap.max_order=0 smsc95xx.macaddr=E4:5F:01:04:54:66 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  console=ttyS0,115200 console=tty1 root=PARTUUID=a8836640-02 rootfstype=ext4 fsck.repair=yes rootwait cfg80211.ieee80211_regdom=DE
          [Thu Jan 15 16:42:09 2026] EXT4-fs (mmcblk0p2): orphan cleanup on readonly fs
          [Thu Jan 15 16:42:09 2026] EXT4-fs (mmcblk0p2): mounted filesystem a76206bf-fc14-4209-834e-7fc7275f6735 ro with ordered data mode. Quota mode: none.
          [Thu Jan 15 16:42:12 2026] EXT4-fs (mmcblk0p2): re-mounted a76206bf-fc14-4209-834e-7fc7275f6735 r/w.
          
          Show mounted filesystems:
          TARGET           SOURCE         FSTYPE OPTIONS
          /                /dev/mmcblk0p2 ext4   rw,noatime
          `-/boot/firmware /dev/mmcblk0p1 vfat   rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro
          
          Files in neuralgic directories:
          
          /var:
          2.4G    /var/
          187M    /var/cache
          182M    /var/cache/apt
          122M    /var/lib
          97M     /var/cache/apt/archives
          
          Archived and active journals take up 8M in the file system.
          
          /opt/iobroker/backups:
          13M     /opt/iobroker/backups/
          
          /opt/iobroker/iobroker-data:
          268M    /opt/iobroker/iobroker-data/
          257M    /opt/iobroker/iobroker-data/files
          51M     /opt/iobroker/iobroker-data/files/javascript.admin
          47M     /opt/iobroker/iobroker-data/files/admin.admin
          46M     /opt/iobroker/iobroker-data/files/admin.admin/custom/assets
          
          The five largest files in iobroker-data are:
          11M     /opt/iobroker/iobroker-data/objects.jsonl
          9.8M    /opt/iobroker/iobroker-data/files/vis-2/material-icons/knx-uf.json
          8.1M    /opt/iobroker/iobroker-data/files/backitup.admin/assets/index-Djx0nwYT.js
          6.9M    /opt/iobroker/iobroker-data/files/javascript.admin/static/js/610.de0231c9.chunk.js.map
          4.9M    /opt/iobroker/iobroker-data/files/javascript.admin/static/js/848.7424922d.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'
          
          Zigbee Network Settings on your coordinator/in nvbackup are:
          
          zigbee.X
          Extended Pan ID:
          *** MASKED ***
          Pan ID:
          *** MASKED ***
          Channel:
          *** MASKED ***
          Network Key:
          *** MASKED ***
          
          To unmask the settings run 'iob diag --unmask'
          
          
          *** NodeJS-Installation ***
          
          /usr/bin/nodejs         v20.19.2
          /usr/bin/node           v20.19.2
          /usr/bin/npm            9.2.0
          /usr/bin/npx            9.2.0
          /usr/bin/corepack       0.24.0
          
          nodejs:
            Installed: 20.19.2+dfsg-1+rpi1
            Candidate: 20.19.2+dfsg-1+rpi1
            Version table:
           *** 20.19.2+dfsg-1+rpi1 500
                  500 http://raspbian.raspberrypi.com/raspbian trixie/main armhf Packages
                  100 /var/lib/dpkg/status
          
          Temp directories causing deletion problem: 0
          No problems detected
          
          Errors in npm tree: 0
          No problems detected
          
          Checking for nodejs vulnerability:
          
          
          ██████   █████  ███    ██  ██████  ███████ ███████
          ██   ██ ██   ██ ████   ██ ██       ██      ██   ██
          ██   ██ ███████ ██ ██  ██ ██   ███ █████   ███████
          ██   ██ ██   ██ ██  ██ ██ ██    ██ ██      ██   ██
          ██████  ██   ██ ██   ████  ██████  ███████ ██   ██
          
          
          The current Node.js version (v20.19.2) is vulnerable to the following CVEs:
          
          CVE-2025-55130(high): A flaw in Node.js’s Permissions model allows attackers to bypass `--allow-fs-read` and `--allow-fs-write` restrictions using crafted relative symlink paths. By chaining directories and symlinks, a script granted access only to the current directory can escape the allowed path and read sensitive files. This breaks the expected isolation guarantees and enables arbitrary file read/write, leading to potential system compromise.
          This vulnerability affects users of the permission model on Node.js v20,  v22,  v24, and v25.
          Patched versions: ^20.20.0 || ^22.22.0 || ^24.13.0 || ^25.3.0
          =
          
          CVE-2025-55131(high): A flaw in Node.js's buffer allocation logic can expose uninitialized memory when allocations are interrupted, when using the `vm` module with the timeout option. Under specific timing conditions, buffers allocated with `Buffer.alloc` and other `TypedArray` instances like `Uint8Array` may contain leftover data from previous operations, allowing in-process secrets like tokens or passwords to leak or causing data corruption. While exploitation typically requires precise timing or in-process code execution, it can become remotely exploitable when untrusted input influences workload and timeouts, leading to potential confidentiality and integrity impact.
          Patched versions: ^20.20.0 || ^22.22.0 || ^24.13.0 || ^25.3.0
          =
          
          CVE-2025-55132(low): A flaw in Node.js's permission model allows a file's access and modification timestamps to be changed via `futimes()` even when the process has only read permissions. Unlike `utimes()`, `futimes()` does not apply the expected write-permission checks, which means file metadata can be modified in read-only directories. This behavior could be used to alter timestamps in ways that obscure activity, reducing the reliability of logs. This vulnerability affects users of the permission model on Node.js v20,  v22,  v24, and v25.
          Patched versions: ^20.20.0 || ^22.22.0 || ^24.13.0 || ^25.3.0
          =
          
          CVE-2025-59465(high): A malformed `HTTP/2 HEADERS` frame with oversized, invalid `HPACK` data can cause Node.js to crash by triggering an unhandled `TLSSocket` error `ECONNRESET`. Instead of safely closing the connection, the process crashes, enabling a remote denial of service. This primarily affects applications that do not attach explicit error handlers to secure sockets, for example:
          

          server.on('secureConnection', socket => {
          socket.on('error', err => {
          console.log(err)
          })
          })

          Patched versions: ^20.20.0 || ^22.22.0 || ^24.13.0 || ^25.3.0
          =
          
          CVE-2025-59466(medium): We have identified a bug in Node.js error handling where "Maximum call stack size exceeded" errors become uncatchable when `async_hooks.createHook()` is enabled. Instead of reaching `process.on('uncaughtException')`, the process terminates, making the crash unrecoverable. Applications that rely on `AsyncLocalStorage` (v22, v20) or `async_hooks.createHook()` (v24, v22, v20) become vulnerable to denial-of-service crashes triggered by deep recursion under specific conditions.
          Patched versions: ^20.20.0 || ^22.22.0 || ^24.13.0 || ^25.3.0
          =
          
          CVE-2026-21637(medium): A flaw in Node.js TLS error handling allows remote attackers to crash or exhaust resources of a TLS server when `pskCallback` or `ALPNCallback` are in use. Synchronous exceptions thrown during these callbacks bypass standard TLS error handling paths (tlsClientError and error), causing either immediate process termination or silent file descriptor leaks that eventually lead to denial of service. Because these callbacks process attacker-controlled input during the TLS handshake, a remote client can repeatedly trigger the issue. This vulnerability affects TLS servers using PSK or ALPN callbacks across Node.js versions where these callbacks throw without being safely wrapped.
          Patched versions: ^20.20.0 || ^22.22.0 || ^24.13.0 || ^25.3.0
          =
          
          *** ioBroker-Installation ***
          
          ioBroker Status
          iobroker is running on this host.
          
          
          Objects type: jsonl
          States  type: jsonl
          
          Hosts:
          Raspberry           Raspberry (version: 7.0.7, hostname: Raspberry     , alive, uptime: 82)
          
          Core adapters versions
          js-controller:  7.0.7
          admin:          6.3.5
          javascript:     6.1.4
          
          nodejs modules from github:     1
          +-- iobroker.tuya@3.14.0 (git+ssh://git@github.com/Apollon77/ioBroker.tuya.git#43f4c1b9bd2f1693f2a1160bc5423b0611c0a143)
          
          Adapter State
            system.adapter.admin.0                  : admin                 : Raspberry                                -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
          + system.adapter.backitup.0               : backitup              : Raspberry                                -  enabled
            system.adapter.cloud.0                  : cloud                 : Raspberry                                - disabled
            system.adapter.discovery.0              : discovery             : Raspberry                                - disabled
            system.adapter.icons-addictive-flavour-png.0: icons-addictive-flavour-png: Raspberry                                - disabled
            system.adapter.icons-icons8.0           : icons-icons8          : Raspberry                                - disabled
            system.adapter.icons-ultimate-png.0     : icons-ultimate-png    : Raspberry                                - disabled
            system.adapter.iqontrol.0               : iqontrol              : Raspberry                                - disabled
            system.adapter.javascript.0             : javascript            : Raspberry                                - disabled
            system.adapter.shelly.0                 : shelly                : Raspberry                                - disabled, port: 1882, bind: 0.0.0.0
            system.adapter.shelly.1                 : shelly                : Raspberry                                - disabled, port: 1882, bind: 0.0.0.0
            system.adapter.sonnen.0                 : sonnen                : Raspberry                                - disabled
            system.adapter.tuya.0                   : tuya                  : Raspberry                                - disabled
            system.adapter.vis-hqwidgets.0          : vis-hqwidgets         : Raspberry                                - disabled
            system.adapter.vis-icontwo.0            : vis-icontwo           : Raspberry                                - disabled
            system.adapter.vis-inventwo.0           : vis-inventwo          : Raspberry                                - disabled
            system.adapter.vis-metro.0              : vis-metro             : Raspberry                                - disabled
            system.adapter.vis-timeandweather.0     : vis-timeandweather    : Raspberry                                - disabled
            system.adapter.vis.0                    : vis                   : Raspberry                                - disabled
            system.adapter.web.0                    : web                   : Raspberry                                - disabled, port: 8082, bind: 192.168.178.55, run as: admin
          
          + instance is alive
          
          Enabled adapters with bindings
            system.adapter.admin.0                  : admin                 : Raspberry                                -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
          
          ioBroker-Repositories
          ┌─────────┬──────────┬─────────────────────────────────────────────────────────┬──────────────┐
          │ (index) │ name     │ url                                                     │ auto upgrade │
          ├─────────┼──────────┼─────────────────────────────────────────────────────────┼──────────────┤
          │ 0       │ 'stable' │ 'http://download.iobroker.net/sources-dist.json'        │ false        │
          │ 1       │ 'beta'   │ 'http://download.iobroker.net/sources-dist-latest.json' │ false        │
          └─────────┴──────────┴─────────────────────────────────────────────────────────┴──────────────┘
          
          Active repo(s): beta
          Upgrade policy: none
          
          Installed ioBroker-Adapters
          Used repository: beta
          Adapter    "admin"        : 7.7.22   , installed 6.3.5  [Updatable]
          Adapter    "backitup"     : 3.3.13   , installed 2.5.10 [Updatable]
          Adapter    "cloud"        : 5.1.2    , installed 4.3.0  [Updatable]
          Adapter    "discovery"    : 5.0.0    , installed 3.1.0  [Updatable]
          Adapter    "icons-addictive-flavour-png": 0.1.0, installed 0.1.0
          Adapter    "icons-icons8" : 0.0.1    , installed 0.0.1
          Adapter    "icons-ultimate-png": 1.0.1, installed 1.0.1
          Adapter    "iqontrol"     : 3.0.0    , installed 2.0.0  [Updatable]
          Adapter    "javascript"   : 9.0.18   , installed 6.1.4  [Updatable]
          Controller "js-controller": 7.1.0    , installed 7.0.7  [Updatable]
          Adapter    "shelly"       : 10.5.2   , installed 6.4.1  [Updatable]
          Adapter    "simple-api"   : 3.0.7    , installed 2.8.0  [Updatable]
          Adapter    "socketio"     : 7.0.8    , installed 4.2.0  [Updatable]
          Adapter    "sonnen"       : 1.18.1   , installed 1.15.6 [Updatable]
          Adapter    "tuya"         : 3.17.0   , installed 3.14.0 [Updatable]
          Adapter    "vis"          : 1.5.6    , installed 1.4.15 [Updatable]
          Adapter    "vis-hqwidgets": 1.6.0    , installed 1.3.0  [Updatable]
          Adapter    "vis-icontwo"  : 1.18.0   , installed 0.90.0 [Updatable]
          Adapter    "vis-inventwo" : 3.3.5    , installed 3.3.1  [Updatable]
          Adapter    "vis-metro"    : 1.2.0    , installed 1.2.0
          Adapter    "vis-timeandweather": 1.2.2, installed 1.2.2
          Adapter    "web"          : 7.0.9    , installed 4.3.0  [Updatable]
          Adapter    "ws"           : 3.0.19   , installed 1.3.0  [Updatable]
          
          Objects and States
          Please stand by - This may take a while
          Objects:        1037
          States:         747
          
          *** OS-Repositories and Updates ***
          Hit:1 http://archive.raspberrypi.com/debian trixie InRelease
          Hit:2 http://raspbian.raspberrypi.com/raspbian trixie InRelease
          Reading package lists...
          Pending Updates: 27
          
          *** 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          8534       1122/sshd: /usr/sbi
          tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN      0          150        1/init
          tcp        0      0 127.0.0.1:9001          0.0.0.0:*               LISTEN      1001       9483       1133/iobroker.js-co
          tcp        0      0 127.0.0.1:9000          0.0.0.0:*               LISTEN      1001       9488       1133/iobroker.js-co
          tcp        0      0 127.0.0.1:6379          0.0.0.0:*               LISTEN      104        9390       1110/redis-server 1
          tcp6       0      0 :::22                   :::*                    LISTEN      0          8536       1122/sshd: /usr/sbi
          tcp6       0      0 :::111                  :::*                    LISTEN      0          1569       1/init
          tcp6       0      0 ::1:6379                :::*                    LISTEN      104        9391       1110/redis-server 1
          udp        0      0 0.0.0.0:59166           0.0.0.0:*                           101        6574       614/avahi-daemon: r
          udp        0      0 0.0.0.0:111             0.0.0.0:*                           0          5031       1/init
          udp        0      0 0.0.0.0:5353            0.0.0.0:*                           101        6572       614/avahi-daemon: r
          udp6       0      0 :::111                  :::*                                0          151        1/init
          udp6       0      0 :::57932                :::*                                101        6575       614/avahi-daemon: r
          udp6       0      0 :::5353                 :::*                                101        6573       614/avahi-daemon: r
          
          *** Log File - Last 25 Lines ***
          
          2026-01-15 16:42:16.505  - info: host.Raspberry added notifications configuration of host
          2026-01-15 16:42:17.382  - info: host.Raspberry 20 instances found
          2026-01-15 16:42:17.430  - info: host.Raspberry starting 2 instances
          2026-01-15 16:42:18.342  - info: host.Raspberry instance system.adapter.admin.0 in version "6.3.5" started with pid 1175
          2026-01-15 16:42:22.526  - info: host.Raspberry instance system.adapter.backitup.0 in version "2.5.10" started with pid 1187
          2026-01-15 16:42:23.515  - info: admin.0 (1175) starting. Version 6.3.5 in /opt/iobroker/node_modules/iobroker.admin, node: v20.19.2, js-controller: 7.0.7
          2026-01-15 16:42:23.594  - info: admin.0 (1175) requesting all states
          2026-01-15 16:42:23.596  - info: admin.0 (1175) requesting all objects
          2026-01-15 16:42:25.512  - info: admin.0 (1175) received all objects
          2026-01-15 16:42:25.816  - error: admin.0 (1175) Cannot create web-server: TypeError: Cannot read properties of undefined (reading 'createServerAsync')
          2026-01-15 16:42:25.823  - info: admin.0 (1175) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
          2026-01-15 16:42:26.735  - info: admin.0 (1175) Request actual repository...
          2026-01-15 16:42:26.781  - info: admin.0 (1175) Repository received successfully.
          2026-01-15 16:42:27.111  - warn: admin.0 (1175) redis get admin.0.info.newsFeed, error - Connection is closed.
          2026-01-15 16:42:27.145  - warn: admin.0 (1175) get state error: Connection is closed.
          2026-01-15 16:42:27.147  - warn: admin.0 (1175) get state error: Connection is closed.
          2026-01-15 16:42:27.149  - warn: admin.0 (1175) get state error: Connection is closed.
          2026-01-15 16:42:27.151  - warn: admin.0 (1175) get state error: Connection is closed.
          2026-01-15 16:42:27.153  - warn: admin.0 (1175) get state error: Connection is closed.
          2026-01-15 16:42:27.159  - error: admin.0 (1175) Cannot update news: Error: DB closed
          2026-01-15 16:42:27.172  - info: admin.0 (1175) terminating http server on port 8081
          2026-01-15 16:42:27.262  - info: host.Raspberry instance system.adapter.admin.0 terminated by request of the instance itself and will not be restarted, before user restarts it.
          2026-01-15 16:42:27.264  - info: host.Raspberry Do not restart adapter system.adapter.admin.0 because desired by instance
          2026-01-15 16:42:27.947  - info: backitup.0 (1187) starting. Version 2.5.10 in /opt/iobroker/node_modules/iobroker.backitup, node: v20.19.2, js-controller: 7.0.7
          2026-01-15 16:42:28.066  - info: backitup.0 (1187) [iobroker] backup was activated at 02:40 every 1 day(s)
          
          HomoranH Nicht stören
          HomoranH Nicht stören
          Homoran
          Global Moderator Administrators
          schrieb zuletzt editiert von
          #9

          @ece87 sagte in admin nach restore nicht erreichbar:

          hab es in eine *txt Datei gespeichert.

          bitte als text in code-tags posten!
          fremde Dateien macht nicht jeder auf.

          kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

          Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

          der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

          1 Antwort Letzte Antwort
          0
          • E Online
            E Online
            ece87
            schrieb zuletzt editiert von
            #10

            64Bit habe ich auch schon versucht,
            ich vermute auch das es daran liegen könnte das ich nie Updates aufgespielt habe..
            das System ist ca 3-4 Jahre gelaufen.
            Backitup war die Version 2.5.10 ca mittlerweile gibt es 3.13

            wäre es möglich mit einer alten Version von Backitup und Iobroker, da noch evtl was zu machen?

            Danke schonmal

            Thomas BraunT HomoranH 3 Antworten Letzte Antwort
            0
            • E ece87

              64Bit habe ich auch schon versucht,
              ich vermute auch das es daran liegen könnte das ich nie Updates aufgespielt habe..
              das System ist ca 3-4 Jahre gelaufen.
              Backitup war die Version 2.5.10 ca mittlerweile gibt es 3.13

              wäre es möglich mit einer alten Version von Backitup und Iobroker, da noch evtl was zu machen?

              Danke schonmal

              Thomas BraunT Online
              Thomas BraunT Online
              Thomas Braun
              Most Active
              schrieb zuletzt editiert von
              #11

              @ece87 sagte in admin nach restore nicht erreichbar:

              64Bit habe ich auch schon versucht,

              Dann verwende es auch...

              ich vermute auch das es daran liegen könnte das ich nie Updates aufgespielt habe..

              Natürlich... Die Kiste ist ganz klassisch so lange nicht 'getatscht' worden, bis sie eben nicht mehr 'runnt'...

              Linux-Werkzeugkasten:
              https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
              NodeJS Fixer Skript:
              https://forum.iobroker.net/topic/68035/iob-node-fix-skript
              iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

              1 Antwort Letzte Antwort
              0
              • H HJRoe

                Hallo,
                ich hatte ein ähnliches Problem. Ich musste IOB von Hand neu starten, da das alte Binding übernommen wurde!!
                Vielleicht hilft dieser Befehl im Terminal:

                iob list instances --allow-root
                Ja, man sollte nicht als root...

                7f154f44-37de-465e-ae13-6d29c8709f88-grafik.png
                f3d3a0ff-2a20-4fe3-b4a2-aee2b713a139-grafik.png
                Danach hat der Neustart funktioniert
                HJR

                Thomas BraunT Online
                Thomas BraunT Online
                Thomas Braun
                Most Active
                schrieb zuletzt editiert von
                #12

                @HJRoe sagte in admin nach restore nicht erreichbar:

                Ja, man sollte nicht als root...

                ARRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRGH!

                Linux-Werkzeugkasten:
                https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                NodeJS Fixer Skript:
                https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                1 Antwort Letzte Antwort
                0
                • E ece87

                  64Bit habe ich auch schon versucht,
                  ich vermute auch das es daran liegen könnte das ich nie Updates aufgespielt habe..
                  das System ist ca 3-4 Jahre gelaufen.
                  Backitup war die Version 2.5.10 ca mittlerweile gibt es 3.13

                  wäre es möglich mit einer alten Version von Backitup und Iobroker, da noch evtl was zu machen?

                  Danke schonmal

                  HomoranH Nicht stören
                  HomoranH Nicht stören
                  Homoran
                  Global Moderator Administrators
                  schrieb zuletzt editiert von
                  #13

                  @ece87 sagte in admin nach restore nicht erreichbar:

                  Backitup war die Version 2.5.10 ca mittlerweile gibt es 3.13

                  das wird bei den Ketnkomponenten wahrscheinlich nicht anders aussehen

                  kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

                  Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

                  der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

                  1 Antwort Letzte Antwort
                  0
                  • E ece87

                    64Bit habe ich auch schon versucht,
                    ich vermute auch das es daran liegen könnte das ich nie Updates aufgespielt habe..
                    das System ist ca 3-4 Jahre gelaufen.
                    Backitup war die Version 2.5.10 ca mittlerweile gibt es 3.13

                    wäre es möglich mit einer alten Version von Backitup und Iobroker, da noch evtl was zu machen?

                    Danke schonmal

                    Thomas BraunT Online
                    Thomas BraunT Online
                    Thomas Braun
                    Most Active
                    schrieb zuletzt editiert von Thomas Braun
                    #14

                    @ece87

                    iob stop
                    sudo apt update
                    sudo apt full-upgrade
                    sudo reboot
                    

                    Dann:

                    iob nodejs-update
                    iob stop
                    iob update
                    iob upgrade self
                    iob update
                    iob upgrade all -y
                    iob start
                    

                    Dann sind dann hoffentlich keine Updates mehr ausstehend.
                    ioBroker ans Laufen bringen, davon dann ein Backup ziehen, Betriebssystem in der 64Bit-Lite-Version installieren, dort den ioBroker installieren, Backup einspielen, fertig.
                    Künftig die Kiste nicht mehr so versumpfen lassen.

                    Linux-Werkzeugkasten:
                    https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                    NodeJS Fixer Skript:
                    https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                    iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                    E 1 Antwort Letzte Antwort
                    0
                    • Thomas BraunT Thomas Braun

                      @ece87

                      iob stop
                      sudo apt update
                      sudo apt full-upgrade
                      sudo reboot
                      

                      Dann:

                      iob nodejs-update
                      iob stop
                      iob update
                      iob upgrade self
                      iob update
                      iob upgrade all -y
                      iob start
                      

                      Dann sind dann hoffentlich keine Updates mehr ausstehend.
                      ioBroker ans Laufen bringen, davon dann ein Backup ziehen, Betriebssystem in der 64Bit-Lite-Version installieren, dort den ioBroker installieren, Backup einspielen, fertig.
                      Künftig die Kiste nicht mehr so versumpfen lassen.

                      E Online
                      E Online
                      ece87
                      schrieb zuletzt editiert von ece87
                      #15

                      @Thomas-Braun sagte in admin nach restore nicht erreichbar:

                      @ece87

                      iob stop
                      sudo apt update
                      sudo apt full-upgrade
                      sudo reboot
                      

                      Dann:

                      iob nodejs-update
                      iob stop
                      iob update
                      iob upgrade self
                      iob update
                      iob upgrade all -y
                      iob start
                      

                      Dann sind dann hoffentlich keine Updates mehr ausstehend.
                      ioBroker ans Laufen bringen, davon dann ein Backup ziehen, Betriebssystem in der 64Bit-Lite-Version installieren, dort den ioBroker installieren, Backup einspielen, fertig.
                      Künftig die Kiste nicht mehr so versumpfen lassen.

                      Vielen Dank so hat es funktioniert
                      echt klasse was ihr für ein wissen habt.

                      Gruß Erich

                      Thomas BraunT 1 Antwort Letzte Antwort
                      0
                      • E ece87

                        @Thomas-Braun sagte in admin nach restore nicht erreichbar:

                        @ece87

                        iob stop
                        sudo apt update
                        sudo apt full-upgrade
                        sudo reboot
                        

                        Dann:

                        iob nodejs-update
                        iob stop
                        iob update
                        iob upgrade self
                        iob update
                        iob upgrade all -y
                        iob start
                        

                        Dann sind dann hoffentlich keine Updates mehr ausstehend.
                        ioBroker ans Laufen bringen, davon dann ein Backup ziehen, Betriebssystem in der 64Bit-Lite-Version installieren, dort den ioBroker installieren, Backup einspielen, fertig.
                        Künftig die Kiste nicht mehr so versumpfen lassen.

                        Vielen Dank so hat es funktioniert
                        echt klasse was ihr für ein wissen habt.

                        Gruß Erich

                        Thomas BraunT Online
                        Thomas BraunT Online
                        Thomas Braun
                        Most Active
                        schrieb zuletzt editiert von
                        #16

                        @ece87

                        Wie sieht das System denn nun nach der Aktion aus?
                        Gib nochmal den Output von

                        iob diag
                        

                        bekannt.

                        Linux-Werkzeugkasten:
                        https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                        NodeJS Fixer Skript:
                        https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                        iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                        1 Antwort Letzte Antwort
                        0
                        Antworten
                        • In einem neuen Thema antworten
                        Anmelden zum Antworten
                        • Älteste zuerst
                        • Neuste zuerst
                        • Meiste Stimmen


                        Support us

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

                        296

                        Online

                        32.6k

                        Benutzer

                        82.0k

                        Themen

                        1.3m

                        Beiträge
                        Community
                        Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                        ioBroker Community 2014-2025
                        logo
                        • Anmelden

                        • Du hast noch kein Konto? Registrieren

                        • Anmelden oder registrieren, um zu suchen
                        • Erster Beitrag
                          Letzter Beitrag
                        0
                        • Home
                        • Aktuell
                        • Tags
                        • Ungelesen 0
                        • Kategorien
                        • Unreplied
                        • Beliebt
                        • GitHub
                        • Docu
                        • Hilfe