Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Einsteigerfragen
    4. [gelöst] Kein Start mehr nach IP Adressen Änderung

    NEWS

    • Wir empfehlen: Node.js 22.x

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker goes Matter ... Matter Adapter in Stable

    [gelöst] Kein Start mehr nach IP Adressen Änderung

    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      aski71 @Homoran last edited by

      @homoran *** iob diag is starting up, please wait ***

      Dann kommt nix mehr.

      A 1 Reply Last reply Reply Quote 0
      • A
        aski71 @aski71 last edited by aski71

        @Homoran Ah. Dauerte nur recht lang.
        Ich denke, das Problem ist "No connection to objects 127.0.0.1:6379[redis]"

        Skript v.2023-10-10

        *** BASE SYSTEM ***
         Static hostname: butler
               Icon name: computer-vm
                 Chassis: vm
          Virtualization: kvm
        Operating System: Ubuntu 22.04.3 LTS
                  Kernel: Linux 5.15.0-86-generic
            Architecture: x86-64
         Hardware Vendor: QEMU
          Hardware Model: Standard PC _i440FX + PIIX, 1996_
        
        model name	: Westmere E56xx/L56xx/X56xx (Nehalem-C)
        Docker          : false
        Virtualization  : kvm
        Kernel          : x86_64
        Userland        : amd64
        
        Systemuptime and Load:
         19:05:28 up 30 min,  4 users,  load average: 0.00, 0.05, 0.12
        CPU threads: 2
        
        
        *** Time and Time Zones ***
                       Local time: Sun 2023-10-15 19:05:28 CEST
                   Universal time: Sun 2023-10-15 17:05:28 UTC
                         RTC time: Sun 2023-10-15 17:05:28
                        Time zone: Europe/Berlin (CEST, +0200)
        System clock synchronized: yes
                      NTP service: active
                  RTC in local TZ: no
        
        *** User and Groups ***
        ak
        /home/ak
        ak adm cdrom sudo dip plugdev lxd iobroker
        
        *** X-Server-Setup ***
        X-Server: 	false
        Desktop: 	
        Terminal: 	tty
        Boot Target: 	graphical.target
        
        *** MEMORY ***
                       total        used        free      shared  buff/cache   available
        Mem:            2.0G        855M        130M        2.0M        977M        913M
        Swap:           2.0G        3.0M        2.0G
        Total:          4.0G        859M        2.2G
        
                 1963 M total memory
                  855 M used memory
                  276 M active memory
                 1237 M inactive memory
                  130 M free memory
                   92 M buffer memory
                  885 M swap cache
                 2047 M total swap
                    3 M used swap
                 2044 M free swap
        
        *** FAILED SERVICES ***
        
          UNIT                             LOAD   ACTIVE SUB    DESCRIPTION
        * iobroker.service                 loaded failed failed ioBroker Server
        * snap.mosquitto.mosquitto.service loaded failed failed Service for snap application mosquitto.mosquitto
        
        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
        tmpfs                               tmpfs  197M  2.6M  194M   2% /run
        /dev/mapper/ubuntu--vg-ubuntu--lv   ext4    98G   11G   83G  11% /
        tmpfs                               tmpfs  982M     0  982M   0% /dev/shm
        tmpfs                               tmpfs  5.0M     0  5.0M   0% /run/lock
        /dev/vda2                           ext4   2.0G  129M  1.7G   8% /boot
        //fatboyslim.fritz.box/SecureBackup cifs    11T  8.5T  2.6T  78% /backup
        tmpfs                               tmpfs  197M  4.0K  197M   1% /run/user/1000
        
        Messages concerning ext4 filesystem in dmesg:
        [Sun Oct 15 18:35:30 2023] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
        [Sun Oct 15 18:35:34 2023] EXT4-fs (dm-0): re-mounted. Opts: (null). Quota mode: none.
        [Sun Oct 15 18:35:37 2023] EXT4-fs (vda2): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
        
        Show mounted filesystems \(real ones only\):
        TARGET                          SOURCE                              FSTYPE   OPTIONS
        /                               /dev/mapper/ubuntu--vg-ubuntu--lv   ext4     rw,relatime
        |-/snap/certbot/3390            /dev/loop1                          squashfs ro,nodev,relatime,errors=continue
        |-/snap/canonical-livepatch/246 /dev/loop0                          squashfs ro,nodev,relatime,errors=continue
        |-/snap/core20/1974             /dev/loop4                          squashfs ro,nodev,relatime,errors=continue
        |-/snap/core18/2790             /dev/loop3                          squashfs ro,nodev,relatime,errors=continue
        |-/snap/snapd/20290             /dev/loop8                          squashfs ro,nodev,relatime,errors=continue
        |-/snap/core/16202              /dev/loop2                          squashfs ro,nodev,relatime,errors=continue
        |-/snap/lxd/24322               /dev/loop6                          squashfs ro,nodev,relatime,errors=continue
        |-/snap/mosquitto/873           /dev/loop7                          squashfs ro,nodev,relatime,errors=continue
        |-/snap/snapd/19457             /dev/loop9                          squashfs ro,nodev,relatime,errors=continue
        |-/snap/core20/2015             /dev/loop5                          squashfs ro,nodev,relatime,errors=continue
        |-/boot                         /dev/vda2                           ext4     rw,relatime
        `-/backup                       //fatboyslim.fritz.box/SecureBackup cifs     rw,relatime,vers=3.1.1,cache=strict,username=raspi,uid=1000,noforceuid,gid=1000,noforcegid,addr=192.168.2.61,file_mode=0755,dir_mode=0755,iocharset=utf8,soft,nounix,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1,closetimeo=1
        
        Files in neuralgic directories:
        
        /var:
        1.4G	/var/
        999M	/var/lib
        553M	/var/lib/snapd
        289M	/var/cache
        269M	/var/cache/apt
        
        Archived and active journals take up 64.0M in the file system.
        
        /opt/iobroker/backups:
        47M	/opt/iobroker/backups/
        
        /opt/iobroker/iobroker-data:
        19M	/opt/iobroker/iobroker-data/
        15M	/opt/iobroker/iobroker-data/files
        13M	/opt/iobroker/iobroker-data/files/admin.admin/custom/static/js
        13M	/opt/iobroker/iobroker-data/files/admin.admin/custom/static
        13M	/opt/iobroker/iobroker-data/files/admin.admin/custom
        
        The five largest files in iobroker-data are:
        6.3M	/opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_js-node_modules_iobr-99c23e.847b8ad9.chunk.js.map
        3.8M	/opt/iobroker/iobroker-data/objects.jsonl
        2.8M	/opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_js-node_modules_iobr-99c23e.847b8ad9.chunk.js
        1.6M	/opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_mui_material_Accordion_index_js-node_modules_mui_material_AccordionDetai-57e02d.0886b730.chunk.js.map
        652K	/opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_mui_material_index_js.40e01f69.chunk.js.map
        
        USB-Devices by-id:
        USB-Sticks -  Avoid direct links to /dev/* in your adapter setups, please always prefer the links 'by-id':
        
        find: '/dev/serial/by-id/': No such file or directory
        
        *** NodeJS-Installation ***
        
        /usr/bin/nodejs 	v18.18.2
        /usr/bin/node 		v18.18.2
        /usr/bin/npm 		9.8.1
        /usr/bin/npx 		9.8.1
        /usr/bin/corepack 	0.19.0
        
        
        nodejs:
          Installed: 18.18.2-1nodesource1
          Candidate: 18.18.2-1nodesource1
          Version table:
         *** 18.18.2-1nodesource1 500
                500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
                100 /var/lib/dpkg/status
             18.18.1-1nodesource1 500
                500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
             18.18.0-1nodesource1 500
                500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
             18.17.1-1nodesource1 500
                500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
             18.17.0-1nodesource1 500
                500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
             18.16.1-1nodesource1 500
                500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
             18.16.0-1nodesource1 500
                500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
             18.15.0-1nodesource1 500
                500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
             18.14.2-1nodesource1 500
                500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
             18.14.1-1nodesource1 500
                500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
             18.14.0-1nodesource1 500
                500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
             18.13.0-1nodesource1 500
                500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
             18.12.0-1nodesource1 500
                500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
             18.11.0-1nodesource1 500
                500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
             18.10.0-1nodesource1 500
                500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
             18.9.1-1nodesource1 500
                500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
             18.9.0-1nodesource1 500
                500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
             18.8.0-1nodesource1 500
                500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
             18.7.0-1nodesource1 500
                500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
             18.6.0-1nodesource1 500
                500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
             18.5.0-1nodesource1 500
                500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
             18.4.0-1nodesource1 500
                500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
             18.3.0-1nodesource1 500
                500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
             18.2.0-1nodesource1 500
                500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
             18.1.0-1nodesource1 500
                500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
             18.0.0-1nodesource1 500
                500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
             12.22.9~dfsg-1ubuntu3 500
                500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
        
        Temp directories causing npm8 problem: 0
        No problems detected
        
        Errors in npm tree:
        
        *** ioBroker-Installation ***
        
        ioBroker Status
        No connection to objects 127.0.0.1:6379[redis]
        
        Core adapters versions
        js-controller: 	5.0.13
        admin: 		6.10.8
        javascript: 	7.1.5
        
        Adapters from github: 	0
        
        Adapter State
        No connection to objects 127.0.0.1:6379[redis]
        
        Enabled adapters with bindings
        
        ioBroker-Repositories
        No connection to objects 127.0.0.1:6379[redis]
        
        Installed ioBroker-Instances
        No connection to objects 127.0.0.1:6379[redis]
        
        Homoran Glasfaser 3 Replies Last reply Reply Quote 0
        • Homoran
          Homoran Global Moderator Administrators @aski71 last edited by

          @aski71 sagte in Kein Start mehr nach IP Adressen Änderung:

          Dauerte nur recht lang.

          deswegen nicht ohne Grund

          @aski71 sagte in Kein Start mehr nach IP Adressen Änderung:

          please wait

          1 Reply Last reply Reply Quote 0
          • Glasfaser
            Glasfaser @aski71 last edited by

            @aski71 sagte in Kein Start mehr nach IP Adressen Änderung:

            No connection to objects 127.0.0.1:6379[redis

            Was ist mit dem Redis Service ...

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

              @aski71 sagte in Kein Start mehr nach IP Adressen Änderung:

              Mem: 2.0G

              wird wohl nicht reichen

              1 Reply Last reply Reply Quote 0
              • Glasfaser
                Glasfaser @aski71 last edited by

                @aski71 sagte in Kein Start mehr nach IP Adressen Änderung:

                ich habe mein System komplett neu installiert.

                siehe auch hier :

                https://forum.iobroker.net/topic/31826/problem-mit-redis-nach-rückspielen-von-einem-backup

                Homoran 1 Reply Last reply Reply Quote 0
                • A
                  aski71 @Glasfaser last edited by

                  @glasfaser Oh mein Gott. Da saß ich ja wirklich auf den Augen! 🙄
                  Der war disabled. Läuft wieder, kaum startet man redis-server...

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

                    @glasfaser sagte in Kein Start mehr nach IP Adressen Änderung:

                    siehe auch hier :

                    meint der user dort wirklich Kernel oder etwa controller?

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

                      @homoran

                      Kernel , denn 2020 gab es noch nicht JS -Controller 5.x

                      1 Reply Last reply Reply Quote 1
                      • Glasfaser
                        Glasfaser @aski71 last edited by

                        @aski71 sagte in Kein Start mehr nach IP Adressen Änderung:

                        Läuft wieder,

                        sehr gerne ... 😉
                        Dann setze den Thread auf [gelöst]

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

                        Support us

                        ioBroker
                        Community Adapters
                        Donate

                        749
                        Online

                        32.0k
                        Users

                        80.4k
                        Topics

                        1.3m
                        Posts

                        database
                        3
                        12
                        334
                        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