Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Nach Absturz keine Verbindung mehr REDIS PROBLEM [gelöst]

    NEWS

    • Wir empfehlen: Node.js 22.x

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker goes Matter ... Matter Adapter in Stable

    Nach Absturz keine Verbindung mehr REDIS PROBLEM [gelöst]

    This topic has been deleted. Only users with topic management privileges can see it.
    • Glasfaser
      Glasfaser @meicker last edited by

      @meicker sagte in Nach Absturz keine Verbindung mehr zum Admin REDIS PROBLEM:

      diese Nacht ist mein TinkerBoard abgestürzt. Es tat sich nichts mehr. Ich habe es dann neu gestartet und es schien auch zunächst alles wieder OK zu sein.

      Also nach einem Absturz ... diese Nacht .

      Ist dort ein Zusammenhang vom 21.November , da du den gleichen Fehler bzw. dort nach einem Backup hast ??

      Ich habe nun mein iobroker neu installiert

      https://forum.iobroker.net/topic/8823/restore-iobroker-auf-tinkerboard/5

      M 1 Reply Last reply Reply Quote 0
      • M
        meicker @Thomas Braun last edited by

        @thomas-braun
        das hat keine Besserung gebracht:

        marc@ioBroker:~$ iobroker stop
        marc@ioBroker:~$ iobroker fix
        library: loaded
        Library version=2021-08-05
        
        ==========================================================================
        
            Welcome to the ioBroker installation fixer!
            Script version: 2021-04-07
            
            You might need to enter your password a couple of times.
        
        ==========================================================================
        
        
        ==========================================================================
            Installing prerequisites (1/3)
        ==========================================================================
        
        OK:1 http://deb.debian.org/debian bullseye InRelease
        OK:2 http://deb.debian.org/debian bullseye-updates InRelease                                                                                                             
        OK:3 http://deb.debian.org/debian bullseye-backports InRelease                                                                                                           
        OK:4 https://deb.nodesource.com/node_12.x bullseye InRelease                                                                                                             
        OK:5 https://www.pivccu.de/piVCCU stable InRelease                                                                      
        OK:6 http://mirror.armbian.de/apt bullseye InRelease
        Paketlisten werden gelesen… Fertig
        Installed gcc-c++
        Installed python-dev
        
        ==========================================================================
            Checking ioBroker user and directory permissions (2/3)
        ==========================================================================
        
        Created /etc/sudoers.d/iobroker
        Fixing directory permissions...
        
        ==========================================================================
            Checking autostart (3/3)
        ==========================================================================
        
        Enabling autostart...
        Autostart enabled!
        
        ==========================================================================
        
            Your installation was fixed successfully
            Run iobroker start to start ioBroker again!
        
        ==========================================================================
        
        marc@ioBroker:~$ sudo apt dist-upgrade
        Paketlisten werden gelesen… Fertig
        Abhängigkeitsbaum wird aufgebaut… Fertig
        Statusinformationen werden eingelesen… Fertig
        Paketaktualisierung (Upgrade) wird berechnet… Fertig
        Die folgenden Pakete werden aktualisiert (Upgrade):
          armbian-bsp-cli-tinkerboard armbian-config armbian-firmware armbian-zsh linux-libc-dev pivccu-modules-dkms pivccu3
        7 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
        Es müssen 132 MB an Archiven heruntergeladen werden.
        Nach dieser Operation werden 1.024 B Plattenplatz zusätzlich benutzt.
        Möchten Sie fortfahren? [J/n] J
        Holen:2 https://www.pivccu.de/piVCCU stable/main armhf pivccu-modules-dkms all 1.0.68 [41,1 kB]
        Holen:3 https://www.pivccu.de/piVCCU stable/main armhf pivccu3 armhf 3.61.6-62 [120 MB]
        Holen:1 http://armbian.hosthatch.com/apt bullseye/bullseye-utils armhf armbian-bsp-cli-tinkerboard armhf 21.08.6 [433 kB]
        Holen:4 http://mirror.armbian.de/apt bullseye/main armhf armbian-config all 21.08.6 [126 kB]            
        Holen:5 http://armbian.12z.eu/apt bullseye/main armhf armbian-firmware all 21.08.6 [7.934 kB]                         
        Holen:7 http://armbian.systemonachip.net/apt bullseye/main armhf linux-libc-dev armhf 21.08.6 [1.167 kB]             
        Holen:6 https://imola.armbian.com/apt bullseye/main armhf armbian-zsh all 21.08.6 [3.013 kB]                                                                        
        Es wurden 132 MB in 13 s geholt (10,4 MB/s).                                                                                                                                                            
        Preconfiguring packages ...
        (Lese Datenbank ... 100042 Dateien und Verzeichnisse sind derzeit installiert.)
        Vorbereitung zum Entpacken von .../pivccu-modules-dkms_1.0.68_all.deb ...
        Removed /etc/systemd/system/debmatic.service.wants/pivccu-dkms.service.
        Removed /etc/systemd/system/multi-user.target.wants/pivccu-dkms.service.
        Removed /etc/systemd/system/pivccu.service.requires/pivccu-dkms.service.
        
        -------- Uninstall Beginning --------
        Module:  pivccu
        Version: 1.0.64
        Kernel:  5.10.60-rockchip (armv7l)
        -------------------------------------
        
        Status: Before uninstall, this module version was ACTIVE on this kernel.
        
        dummy_rx8130.ko:
         - Uninstallation
           - Deleting from: /lib/modules/5.10.60-rockchip/updates/dkms/
         - Original module
           - No original module was found for this module on this kernel.
           - Use the dkms install command to reinstall any previous module version.
        
        
        dw_apb_raw_uart.ko:
         - Uninstallation
           - Deleting from: /lib/modules/5.10.60-rockchip/updates/dkms/
         - Original module
           - No original module was found for this module on this kernel.
           - Use the dkms install command to reinstall any previous module version.
        
        
        eq3_char_loop.ko:
         - Uninstallation
           - Deleting from: /lib/modules/5.10.60-rockchip/updates/dkms/
         - Original module
           - No original module was found for this module on this kernel.
           - Use the dkms install command to reinstall any previous module version.
        
        
        fake_hmrf.ko:
         - Uninstallation
           - Deleting from: /lib/modules/5.10.60-rockchip/updates/dkms/
         - Original module
           - No original module was found for this module on this kernel.
           - Use the dkms install command to reinstall any previous module version.
        
        
        generic_raw_uart.ko:
         - Uninstallation
           - Deleting from: /lib/modules/5.10.60-rockchip/updates/dkms/
         - Original module
           - No original module was found for this module on this kernel.
           - Use the dkms install command to reinstall any previous module version.
        
        
        hb_rf_eth.ko:
         - Uninstallation
           - Deleting from: /lib/modules/5.10.60-rockchip/updates/dkms/
         - Original module
           - No original module was found for this module on this kernel.
           - Use the dkms install command to reinstall any previous module version.
        
        
        hb_rf_usb-2.ko:
         - Uninstallation
           - Deleting from: /lib/modules/5.10.60-rockchip/updates/dkms/
         - Original module
           - No original module was found for this module on this kernel.
           - Use the dkms install command to reinstall any previous module version.
        
        
        hb_rf_usb.ko:
         - Uninstallation
           - Deleting from: /lib/modules/5.10.60-rockchip/updates/dkms/
         - Original module
           - No original module was found for this module on this kernel.
           - Use the dkms install command to reinstall any previous module version.
        
        
        led_trigger_timer.ko:
         - Uninstallation
           - Deleting from: /lib/modules/5.10.60-rockchip/updates/dkms/
         - Original module
           - No original module was found for this module on this kernel.
           - Use the dkms install command to reinstall any previous module version.
        
        
        meson_raw_uart.ko:
         - Uninstallation
           - Deleting from: /lib/modules/5.10.60-rockchip/updates/dkms/
         - Original module
           - No original module was found for this module on this kernel.
           - Use the dkms install command to reinstall any previous module version.
        
        
        pl011_raw_uart.ko:
         - Uninstallation
           - Deleting from: /lib/modules/5.10.60-rockchip/updates/dkms/
         - Original module
           - No original module was found for this module on this kernel.
           - Use the dkms install command to reinstall any previous module version.
        
        
        plat_eq3ccu2.ko:
         - Uninstallation
           - Deleting from: /lib/modules/5.10.60-rockchip/updates/dkms/
         - Original module
           - No original module was found for this module on this kernel.
           - Use the dkms install command to reinstall any previous module version.
        
        
        rpi_rf_mod_led.ko:
         - Uninstallation
           - Deleting from: /lib/modules/5.10.60-rockchip/updates/dkms/
         - Original module
           - No original module was found for this module on this kernel.
           - Use the dkms install command to reinstall any previous module version.
        
        
        rtc-rx8130.ko:
         - Uninstallation
           - Deleting from: /lib/modules/5.10.60-rockchip/updates/dkms/
         - Original module
           - No original module was found for this module on this kernel.
           - Use the dkms install command to reinstall any previous module version.
        
        depmod.....
        
        DKMS: uninstall completed.
        
        ------------------------------
        Deleting module version: 1.0.64
        completely from the DKMS tree.
        ------------------------------
        Done.
        Entpacken von pivccu-modules-dkms (1.0.68) über (1.0.64) ...
        pivccu-modules-dkms (1.0.68) wird eingerichtet ...
        Error! The module/version combo: pivccu-1.0.68
        is not located in the DKMS tree.
        
        Creating symlink /var/lib/dkms/pivccu/1.0.68/source ->
                         /usr/src/pivccu-1.0.68
        
        DKMS: add completed.
        
        Kernel preparation unnecessary for this kernel.  Skipping...
        
        Building module:
        cleaning build area...
        make -j4 KERNELRELEASE=5.10.60-rockchip ARCH=arm all......
        cleaning build area...
        
        DKMS: build completed.
        
        dummy_rx8130.ko:
        Running module version sanity check.
         - Original module
           - No original module exists within this kernel
         - Installation
           - Installing to /lib/modules/5.10.60-rockchip/updates/dkms/
        
        dw_apb_raw_uart.ko:
        Running module version sanity check.
         - Original module
           - No original module exists within this kernel
         - Installation
           - Installing to /lib/modules/5.10.60-rockchip/updates/dkms/
        
        eq3_char_loop.ko:
        Running module version sanity check.
         - Original module
           - No original module exists within this kernel
         - Installation
           - Installing to /lib/modules/5.10.60-rockchip/updates/dkms/
        
        fake_hmrf.ko:
        Running module version sanity check.
         - Original module
           - No original module exists within this kernel
         - Installation
           - Installing to /lib/modules/5.10.60-rockchip/updates/dkms/
        
        generic_raw_uart.ko:
        Running module version sanity check.
         - Original module
           - No original module exists within this kernel
         - Installation
           - Installing to /lib/modules/5.10.60-rockchip/updates/dkms/
        
        hb_rf_eth.ko:
        Running module version sanity check.
         - Original module
           - No original module exists within this kernel
         - Installation
           - Installing to /lib/modules/5.10.60-rockchip/updates/dkms/
        
        hb_rf_usb-2.ko:
        Running module version sanity check.
         - Original module
           - No original module exists within this kernel
         - Installation
           - Installing to /lib/modules/5.10.60-rockchip/updates/dkms/
        
        hb_rf_usb.ko:
        Running module version sanity check.
         - Original module
           - No original module exists within this kernel
         - Installation
           - Installing to /lib/modules/5.10.60-rockchip/updates/dkms/
        
        led_trigger_timer.ko:
        Running module version sanity check.
         - Original module
           - No original module exists within this kernel
         - Installation
           - Installing to /lib/modules/5.10.60-rockchip/updates/dkms/
        
        meson_raw_uart.ko:
        Running module version sanity check.
         - Original module
           - No original module exists within this kernel
         - Installation
           - Installing to /lib/modules/5.10.60-rockchip/updates/dkms/
        
        pl011_raw_uart.ko:
        Running module version sanity check.
         - Original module
           - No original module exists within this kernel
         - Installation
           - Installing to /lib/modules/5.10.60-rockchip/updates/dkms/
        
        plat_eq3ccu2.ko:
        Running module version sanity check.
         - Original module
           - No original module exists within this kernel
         - Installation
           - Installing to /lib/modules/5.10.60-rockchip/updates/dkms/
        
        rpi_rf_mod_led.ko:
        Running module version sanity check.
         - Original module
           - No original module exists within this kernel
         - Installation
           - Installing to /lib/modules/5.10.60-rockchip/updates/dkms/
        
        rtc-rx8130.ko:
        Running module version sanity check.
         - Original module
           - No original module exists within this kernel
         - Installation
           - Installing to /lib/modules/5.10.60-rockchip/updates/dkms/
        
        depmod.....
        
        DKMS: install completed.
        Created symlink /etc/systemd/system/multi-user.target.wants/pivccu-dkms.service → /lib/systemd/system/pivccu-dkms.service.
        Created symlink /etc/systemd/system/debmatic.service.wants/pivccu-dkms.service → /lib/systemd/system/pivccu-dkms.service.
        Created symlink /etc/systemd/system/pivccu.service.requires/pivccu-dkms.service → /lib/systemd/system/pivccu-dkms.service.
        (Lese Datenbank ... 100043 Dateien und Verzeichnisse sind derzeit installiert.)
        Vorbereitung zum Entpacken von .../0-pivccu3_3.61.6-62_armhf.deb ...
        Removed /etc/systemd/system/pivccu.service.wants/monitor-hb-rf-eth.service.
        Removed /etc/systemd/system/multi-user.target.wants/pivccu.service.
        Entpacken von pivccu3 (3.61.6-62) über (3.59.6-59) ...
        Vorbereitung zum Entpacken von .../1-armbian-bsp-cli-tinkerboard_21.08.6_armhf.deb ...
        Entpacken von armbian-bsp-cli-tinkerboard (21.08.6) über (21.08.5) ...
        Vorbereitung zum Entpacken von .../2-armbian-config_21.08.6_all.deb ...
        Entpacken von armbian-config (21.08.6) über (21.08.5) ...
        Vorbereitung zum Entpacken von .../3-armbian-firmware_21.08.6_all.deb ...
        Entpacken von armbian-firmware (21.08.6) über (21.08.5) ...
        Vorbereitung zum Entpacken von .../4-armbian-zsh_21.08.6_all.deb ...
        Entpacken von armbian-zsh (21.08.6) über (21.08.5) ...
        Vorbereitung zum Entpacken von .../5-linux-libc-dev_21.08.6_armhf.deb ...
        Entpacken von linux-libc-dev:armhf (21.08.6) über (21.08.5) ...
        pivccu3 (3.61.6-62) wird eingerichtet ...
        Created symlink /etc/systemd/system/multi-user.target.wants/pivccu.service → /lib/systemd/system/pivccu.service.
        Created symlink /etc/systemd/system/pivccu.service.wants/monitor-hb-rf-eth.service → /lib/systemd/system/monitor-hb-rf-eth.service.
        linux-libc-dev:armhf (21.08.6) wird eingerichtet ...
        armbian-zsh (21.08.6) wird eingerichtet ...
        armbian-config (21.08.6) wird eingerichtet ...
        armbian-firmware (21.08.6) wird eingerichtet ...
        armbian-bsp-cli-tinkerboard (21.08.6) wird eingerichtet ...
        Trigger für initramfs-tools (0.140) werden verarbeitet ...
        update-initramfs: Generating /boot/initrd.img-5.10.60-rockchip
        W: Possible missing firmware /lib/firmware/mrvl/sdsd8997_combo_v4.bin for built-in driver mwifiex_sdio
        W: Possible missing firmware /lib/firmware/mrvl/sd8987_uapsta.bin for built-in driver mwifiex_sdio
        W: Possible missing firmware /lib/firmware/mrvl/sdsd8977_combo_v2.bin for built-in driver mwifiex_sdio
        W: Possible missing firmware /lib/firmware/mrvl/sd8887_uapsta.bin for built-in driver mwifiex_sdio
        W: Possible missing firmware /lib/firmware/mrvl/sd8897_uapsta.bin for built-in driver mwifiex_sdio
        W: Possible missing firmware /lib/firmware/mrvl/sd8797_uapsta.bin for built-in driver mwifiex_sdio
        W: Possible missing firmware /lib/firmware/mrvl/sd8787_uapsta.bin for built-in driver mwifiex_sdio
        W: Possible missing firmware /lib/firmware/mrvl/sd8786_uapsta.bin for built-in driver mwifiex_sdio
        W: Possible missing firmware /lib/firmware/rt73.bin for built-in driver rt73usb
        W: Possible missing firmware /lib/firmware/rtlwifi/rtl8723bu_bt.bin for built-in driver rtl8xxxu
        W: Possible missing firmware /lib/firmware/xc3028L-v36.fw for built-in driver tuner_xc2028
        W: Possible missing firmware /lib/firmware/xc3028-v27.fw for built-in driver tuner_xc2028
        W: Possible missing firmware /lib/firmware/dvb-fe-xc5000c-4.1.30.7.fw for built-in driver xc5000
        W: Possible missing firmware /lib/firmware/dvb-fe-xc4000-1.4.fw for built-in driver xc4000
        W: Possible missing firmware /lib/firmware/dvb-fe-xc4000-1.4.1.fw for built-in driver xc4000
        W: Possible missing firmware /lib/firmware/bfubase.frm for built-in driver bfusb
        W: Possible missing firmware /lib/firmware/mediatek/mt7668pr2h.bin for built-in driver btusb
        W: Possible missing firmware /lib/firmware/mediatek/mt7663pr2h.bin for built-in driver btusb
        W: Possible missing firmware /lib/firmware/intel/ibt-12-16.ddc for built-in driver btintel
        W: Possible missing firmware /lib/firmware/intel/ibt-12-16.sfi for built-in driver btintel
        W: Possible missing firmware /lib/firmware/intel/ibt-11-5.ddc for built-in driver btintel
        W: Possible missing firmware /lib/firmware/intel/ibt-11-5.sfi for built-in driver btintel
        W: Possible missing firmware /lib/firmware/mrvl/sdsd8997_combo_v4.bin for built-in driver btmrvl_sdio
        W: Possible missing firmware /lib/firmware/mrvl/sd8987_uapsta.bin for built-in driver btmrvl_sdio
        W: Possible missing firmware /lib/firmware/mrvl/sdsd8977_combo_v2.bin for built-in driver btmrvl_sdio
        W: Possible missing firmware /lib/firmware/mrvl/sd8897_uapsta.bin for built-in driver btmrvl_sdio
        W: Possible missing firmware /lib/firmware/mrvl/sd8887_uapsta.bin for built-in driver btmrvl_sdio
        W: Possible missing firmware /lib/firmware/mrvl/sd8797_uapsta.bin for built-in driver btmrvl_sdio
        W: Possible missing firmware /lib/firmware/mrvl/sd8787_uapsta.bin for built-in driver btmrvl_sdio
        W: Possible missing firmware /lib/firmware/mrvl/sd8688.bin for built-in driver btmrvl_sdio
        W: Possible missing firmware /lib/firmware/mrvl/sd8688_helper.bin for built-in driver btmrvl_sdio
        W: Possible missing firmware /lib/firmware/rtl_bt/rtl8821a_config.bin for built-in driver btrtl
        W: Possible missing firmware /lib/firmware/rtl_bt/rtl8821a_fw.bin for built-in driver btrtl
        W: Possible missing firmware /lib/firmware/rtl_bt/rtl8761a_config.bin for built-in driver btrtl
        W: Possible missing firmware /lib/firmware/rtl_bt/rtl8761a_fw.bin for built-in driver btrtl
        W: Possible missing firmware /lib/firmware/rtl_bt/rtl8723bs_config.bin for built-in driver btrtl
        W: Possible missing firmware /lib/firmware/rtl_bt/rtl8723bs_fw.bin for built-in driver btrtl
        W: Possible missing firmware /lib/firmware/rtl_bt/rtl8723a_fw.bin for built-in driver btrtl
        update-initramfs: Converting to u-boot format
        piVCCU: DTB rk3288-tinker.dtb was already patched
        piVCCU: DTB rk3288-tinker-s.dtb was already patched
        marc@ioBroker:~$ sudo reboot
        Connection to 192.168.1.31 closed by remote host.
        Connection to 192.168.1.31 closed.
        marc@iMac-Marc ~ % ssh marc@192.168.1.31
        ssh: connect to host 192.168.1.31 port 22: Operation timed out
        marc@iMac-Marc ~ % ssh marc@192.168.1.31
        ssh: connect to host 192.168.1.31 port 22: Operation timed out
        marc@iMac-Marc ~ % ssh marc@192.168.1.31
        marc@192.168.1.31's password: 
         _____ _       _             _                         _ 
        |_   _(_)_ __ | | _____ _ __| |__   ___   __ _ _ __ __| |
          | | | | '_ \| |/ / _ \ '__| '_ \ / _ \ / _` | '__/ _` |
          | | | | | | |   <  __/ |  | |_) | (_) | (_| | | | (_| |
          |_| |_|_| |_|_|\_\___|_|  |_.__/ \___/ \__,_|_|  \__,_|
                                                                 
        Welcome to Armbian 21.08.6 Bullseye with Linux 5.10.60-rockchip
        
        System load:   30%           	Up time:       1 min	
        Memory usage:  10% of 1.95G  	IP:	       192.168.1.31 10.0.3.1
        CPU temp:      62°C           	Usage of /:    32% of 15G    	
        
        Last login: Sat Dec  4 14:39:37 2021 from 192.168.1.150
        marc@ioBroker:~$ iobroker status
        No connection to states 127.0.0.1:6379[redis]
        marc@ioBroker:~$ 
        
        Thomas Braun 1 Reply Last reply Reply Quote 0
        • Thomas Braun
          Thomas Braun Most Active @meicker last edited by

          @meicker

          sudo -u iobroker groups
          
          M 2 Replies Last reply Reply Quote 0
          • M
            meicker @Glasfaser last edited by

            @glasfaser
            ich kann keinen direkten Zusammenhang sehen. Nur ist es mit dem Board schon der zweite Absurz. Beim ersten war der emmc kaputt und konnte nicht mehr booten. Jeztt bootet die SD aber noch und startet pivccu aber keinen iobroker mehr bzw. jetzt habe ich das redis zugriffsproblem ...

            Ich muss leider mal weg, m,elde mich später wieder. Vielleicht hat ja noch jemand eine Idee, ansonsten neu aufsetzen 🙂 Hab ich ja jetzt Übung drin ...

            1 Reply Last reply Reply Quote 0
            • M
              meicker @Thomas Braun last edited by

              @thomas-braun

              iobroker tty dialout audio video i2c bluetooth redis
              marc@ioBroker:~$
              
              1 Reply Last reply Reply Quote 0
              • Glasfaser
                Glasfaser last edited by

                @meicker

                sudo systemctl status redis-server
                sudo systemctl enable redis-server
                
                M 1 Reply Last reply Reply Quote 0
                • M
                  meicker @Thomas Braun last edited by

                  @thomas-braun
                  ich muss mal kurz weg. Ich mache später weiter wenn Du noch einen Hinweis hast 🙂 ! Danke schonmal vorab !

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

                    @glasfaser sagte in Nach Absturz keine Verbindung mehr zum Admin REDIS PROBLEM:

                    > sudo systemctl enable redis-server
                    
                    marc@ioBroker:~$ sudo systemctl status redis-server
                    ● redis-server.service - Advanced key-value store
                         Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; vendor preset: enabled)
                         Active: failed (Result: exit-code) since Sat 2021-12-04 14:59:47 CET; 15s ago
                           Docs: http://redis.io/documentation,
                                 man:redis-server(1)
                        Process: 4541 ExecStart=/usr/bin/redis-server /etc/redis/redis.conf --supervised systemd --daemonize no (code=exited, status=1/FAILURE)
                       Main PID: 4541 (code=exited, status=1/FAILURE)
                         Status: "Redis is loading..."
                            CPU: 109ms
                    
                    Dez 04 14:59:47 ioBroker systemd[1]: redis-server.service: Scheduled restart job, restart counter is at 5.
                    Dez 04 14:59:47 ioBroker systemd[1]: Stopped Advanced key-value store.
                    Dez 04 14:59:47 ioBroker systemd[1]: redis-server.service: Start request repeated too quickly.
                    Dez 04 14:59:47 ioBroker systemd[1]: redis-server.service: Failed with result 'exit-code'.
                    Dez 04 14:59:47 ioBroker systemd[1]: Failed to start Advanced key-value store.
                    
                    Glasfaser 2 Replies Last reply Reply Quote 0
                    • Glasfaser
                      Glasfaser @meicker last edited by

                      @meicker

                      iobroker status
                      
                      M 1 Reply Last reply Reply Quote 0
                      • M
                        meicker @Glasfaser last edited by

                        @glasfaser sagte in Nach Absturz keine Verbindung mehr zum Admin REDIS PROBLEM:

                        iobroker status

                        marc@ioBroker:~$ iobroker status
                        No connection to states 127.0.0.1:6379[redis]
                        
                        Glasfaser 1 Reply Last reply Reply Quote 0
                        • Glasfaser
                          Glasfaser @meicker last edited by Glasfaser

                          @meicker

                          hast du

                          sudo systemctl enable redis-server
                          

                          gemacht , sehe ich nicht

                          EDIT :

                          war abgeschnitten .

                          Dann

                          iobroker stop
                          iobroker host this
                          iobroker start
                          
                          Homoran M 4 Replies Last reply Reply Quote 0
                          • Homoran
                            Homoran Global Moderator Administrators @Glasfaser last edited by

                            @glasfaser sagte in Nach Absturz keine Verbindung mehr zum Admin REDIS PROBLEM:

                            gemacht , sehe ich nicht

                            zeile 1 - sieht aber komisch aus

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

                              @glasfaser sagte in Nach Absturz keine Verbindung mehr zum Admin REDIS PROBLEM:

                              sudo systemctl enable redis-server

                              in Zeile 1 wqeiter oben im code

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

                                @meicker

                                Habe oben Edit gemacht ... mache die Befehle

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

                                  @glasfaser sagte in Nach Absturz keine Verbindung mehr zum Admin REDIS PROBLEM:

                                  sudo systemctl enable redis-server

                                  marc@ioBroker:~$ sudo systemctl enable redis-server
                                  [sudo] Passwort für marc: 
                                  Synchronizing state of redis-server.service with SysV service script with /lib/systemd/systemd-sysv-install.
                                  Executing: /lib/systemd/systemd-sysv-install enable redis-server
                                  marc@ioBroker:~$ iobroker status
                                  No connection to states 127.0.0.1:6379[redis]
                                  
                                  1 Reply Last reply Reply Quote 0
                                  • Glasfaser
                                    Glasfaser @meicker last edited by

                                    @meicker sagte in Nach Absturz keine Verbindung mehr zum Admin REDIS PROBLEM:

                                    Dez 04 14:59:47 ioBroker systemd[1]: Failed to start Advanced key-value store.

                                    Ist ioBroker in einer VM installiert !?

                                    https://forum.iobroker.net/topic/18835/auf-redis-umstellen/82?_=1638625607365

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

                                      @glasfaser

                                      marc@ioBroker:~$ iobroker stop
                                      marc@ioBroker:~$ iobroker host this
                                      No connection to states 127.0.0.1:6379[redis]
                                      marc@ioBroker:~$ iobroker start
                                      marc@ioBroker:~$ iobroker status
                                      No connection to states 127.0.0.1:6379[redis]
                                      marc@ioBroker:~$ 
                                      
                                      1 Reply Last reply Reply Quote 0
                                      • M
                                        meicker @Glasfaser last edited by

                                        @glasfaser sagte in Nach Absturz keine Verbindung mehr zum Admin REDIS PROBLEM:

                                        Ist ioBroker in einer VM installiert !?

                                        nein

                                        1 Reply Last reply Reply Quote 0
                                        • M
                                          meicker last edited by

                                          Hat bis zum Absturz einwandfrei funktioniert ... läuft auf einem Tinker Board ...

                                          Meister Mopper 1 Reply Last reply Reply Quote 0
                                          • Meister Mopper
                                            Meister Mopper @meicker last edited by

                                            @meicker
                                            Hast Du schon mal in den redis-server logfiles gesucht? Die liegen vermutlich in
                                            /var/log/redis

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

                                            Support us

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

                                            548
                                            Online

                                            32.0k
                                            Users

                                            80.4k
                                            Topics

                                            1.3m
                                            Posts

                                            5
                                            63
                                            4937
                                            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