Nach Neustart keine Verbindung mehr
-
Hallo zusammen,
nach einem Neustart des Systems (Ubuntu) bekam ich diese Fehlermeldung im Browser (Firefox): Verbindung fehlgeschlagen. Keine Verbindung mehr zu ......
Das System lief bis zum Neustart seit Wochen ohne Probleme.
Dann iob fix laufen lassen. Nach Reboot die gleiche Meldung.
Mit "iob status" kam die Fehlermeldung: no connection to objects .... (redis)
Die Redis Datenbank läuft (mit "redis.cli" geprüft).
Ich habe auch den Redis-server neu gestartet, keine Änderung.
Jetzt bin ich mit meinem Halbwissen am Ende. Ich weiß nicht, ob der iob noch im Hintergrund läuft.
Gibt es Tipps, was ich noch testen kann?
Ich habe nur die aktuellen Stable- Versionen der Adapter installiert
Danke , Jürgen -
-
@ünne hat der Rechner nach dem Neustart ggfs eine andere IP Adresse bekommen?
-
@thomas-braun
Auszüge aus iob-diag
** FAILED SERVICES ***UNIT LOAD ACTIVE SUB DESCRIPTION
- snap.redis.server.service loaded failed failed Service for snap application redis.server
Legend: 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.oBroker Status
No connection to objects 192.168.178.55:6379[redis]Hosts:
No connection to objects 192.168.178.55:6379[redis]Core adapters versions
js-controller: 7.0.3
admin: 7.1.5
javascript: 8.8.3nodejs modules from github: 0
Adapter State
No connection to objects 192.168.178.55:6379[redis]Enabled adapters with bindings
ioBroker-Repositories
No connection to objects 192.168.178.55:6379[redis]Installed ioBroker-Instances
No connection to objects 192.168.178.55:6379[redis]Aus log-file:
2025-01-04 21:41:36.508 - error: host.juergen-NUC8i5BEK No connection to databases possible, restart -
@martinp
Wohl nicht.
Bei der Überprüfung der Redis-Installation: mit "iob setup custom" wird die normale IP aufgeführt. -
@ünne said in Nach Neustart keine Verbindung mehr:
@thomas-braun
Auszüge aus iob-diagWarum AUSZÜGE?
Thomas hat explizit die LANGFASSUNG angefordert. Bitte daher die LANGFASSUNG ungekürzt und unter Code Tags posten.
Danke -
@mcm1957
ok, gerne . Ist nur viel zu lesen.** BASE SYSTEM *** Static hostname: juergen-NUC8i5BEK Icon name: computer-desktop Chassis: desktop 🖥️ Operating System: Ubuntu 24.04.1 LTS Kernel: Linux 6.8.0-51-generic Architecture: x86-64 Hardware Vendor: Intel_R_ Client Systems Hardware Model: NUC8i5BEK Firmware Version: BECFL357.86A.0077.2019.1127.1452 Firmware Date: Wed 2019-11-27 Firmware Age: 5y 1month 1w 2d OS is similar to: debian model name : Intel(R) Core(TM) i5-8259U CPU @ 2.30GHz Docker : false Virtualization : none Kernel : x86_64 Userland : 64 bit Systemuptime and Load: 22:19:08 up 1:22, 1 user, load average: 0.42, 0.24, 0.15 CPU threads: 8 *** LIFE CYCLE STATUS *** Operating System is the current Ubuntu LTS release codenamed 'noble'! *** TIME AND TIMEZONES *** Local time: Sat 2025-01-04 22:19:08 CET Universal time: Sat 2025-01-04 21:19:08 UTC RTC time: Sat 2025-01-04 21:19:08 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': juergen HOME=/home/juergen GROUPS=juergen adm cdrom sudo dip plugdev lpadmin lxd sambashare iobroker User that is running 'js-controller': iobroker HOME=/home/iobroker GROUPS=iobroker tty dialout audio video plugdev bluetooth redis *** DISPLAY-SERVER SETUP *** Display-Server: true Desktop: ubuntu Terminal: wayland System is booting into 'graphical.target'. Usually a server is running in 'multi-user.target'. Please set BootTarget to 'multi-user.target' or run 'iobroker fix' *** MEMORY *** total used free shared buff/cache available Mem: 16G 3.9G 10G 557M 3.3G 12G Swap: 2.1G 0B 2.1G Total: 18G 3.9G 12G Active iob-Instances: 0 15860 M total memory 3735 M used memory 3510 M active memory 1338 M inactive memory 9813 M free memory 244 M buffer memory 2936 M swap cache 2047 M total swap 0 M used swap 2047 M free swap *** top - Table Of Processes *** top - 22:19:09 up 1:22, 1 user, load average: 0.42, 0.24, 0.15 Tasks: 293 total, 1 running, 292 sleeping, 0 stopped, 0 zombie %Cpu(s): 1.0 us, 1.9 sy, 0.0 ni, 96.2 id, 1.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 15860.9 total, 9807.7 free, 3741.3 used, 3185.4 buff/cache MiB Swap: 2048.0 total, 2048.0 free, 0.0 used. 12119.6 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION * snap.redis.server.service loaded failed failed Service for snap application redis.server Legend: LOAD -> Reflects whether the unit definition was properly loaded. ACTIVE -> The high-level unit activation state, i.e. generalization of SUB. SUB -> The low-level unit activation state, values depend on unit type. 1 loaded units listed. *** DMESG CRITICAL ERRORS *** No critical errors detected *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on tmpfs tmpfs 1.6G 2.4M 1.6G 1% /run /dev/nvme0n1p2 ext4 457G 272G 163G 63% / tmpfs tmpfs 7.8G 980K 7.8G 1% /dev/shm tmpfs tmpfs 5.0M 8.0K 5.0M 1% /run/lock efivarfs efivarfs 192K 75K 113K 40% /sys/firmware/efi/efivars /dev/nvme0n1p1 vfat 511M 6.3M 505M 2% /boot/efi tmpfs tmpfs 1.6G 128K 1.6G 1% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Sat Jan 4 20:56:57 2025] EXT4-fs (nvme0n1p2): mounted filesystem 8008f491-03d0-47e4-b616-82dd79965a9e ro with ordered data mode. Quota mode: none. [Sat Jan 4 20:56:58 2025] EXT4-fs (nvme0n1p2): re-mounted 8008f491-03d0-47e4-b616-82dd79965a9e r/w. Quota mode: none. Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/nvme0n1p2 ext4 rw,relatime,errors=remount-ro |-/run/user/1000/doc portal fuse.portal rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 |-/snap/bare/5 /dev/loop0 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/canonical-livepatch/282 /dev/loop1 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/canonical-livepatch/286 /dev/loop2 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/core/17200 /dev/loop4 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/core/16928 /dev/loop3 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/core18/2846 /dev/loop6 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/core18/2829 /dev/loop5 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/core20/2379 /dev/loop8 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/core20/2434 /dev/loop7 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/core22/1663 /dev/loop9 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/core22/1722 /dev/loop10 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/cups/1058 /dev/loop11 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/cups/1067 /dev/loop12 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/ffmpeg-2204/126 /dev/loop13 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/firefox/5437 /dev/loop15 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/firefox/5361 /dev/loop14 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/firmware-updater/127 /dev/loop16 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/firmware-updater/147 /dev/loop17 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/gnome-3-38-2004/140 /dev/loop18 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/gnome-3-38-2004/143 /dev/loop19 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/gnome-42-2204/172 /dev/loop20 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/gnome-42-2204/176 /dev/loop21 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/gnome-calculator/955 /dev/loop22 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/gtk-common-themes/1535 /dev/loop24 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/gtk-common-themes/1534 /dev/loop23 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/hunspell-dictionaries-1-7-2004/2 /dev/loop25 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/kde-frameworks-5-core18/32 /dev/loop27 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/kde-frameworks-5-96-qt-5-15-5-core20/7 /dev/loop26 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/kf5-5-104-qt-5-15-8-core22/9 /dev/loop30 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/kf5-5-104-qt-5-15-8-core22/7 /dev/loop29 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/kde-frameworks-5-core18/35 /dev/loop28 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/kf5-5-111-qt-5-15-11-core22/5 /dev/loop31 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/kf5-5-111-qt-5-15-11-core22/7 /dev/loop32 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/kf5-5-108-qt-5-15-10-core22/5 /dev/loop33 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/kf5-5-113-qt-5-15-11-core22/1 /dev/loop34 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/kf5-core22/3 /dev/loop35 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/krita/104 /dev/loop37 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/krita/108 /dev/loop38 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/snap-store/1248 /dev/loop36 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/redis/1572 /dev/loop39 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/snapd/23258 /dev/loop42 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/snap-store/1244 /dev/loop40 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/snapd/21759 /dev/loop41 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/snapd-desktop-integration/247 /dev/loop43 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/snapd-desktop-integration/253 /dev/loop44 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/spotify/80 /dev/loop45 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/spotify/81 /dev/loop46 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/thunderbird/601 /dev/loop47 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/thunderbird/609 /dev/loop48 squashfs ro,nodev,relatime,errors=continue,threads=single |-/var/snap/firefox/common/host-hunspell /dev/nvme0n1p2[/usr/share/hunspell] ext4 ro,noexec,noatime,errors=remount-ro |-/snap/vlc/3777 /dev/loop49 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/vlc/3721 /dev/loop50 squashfs ro,nodev,relatime,errors=continue,threads=single `-/boot/efi /dev/nvme0n1p1 vfat rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 14G /var/ 13G /var/lib 12G /var/lib/snapd 6.4G /var/lib/snapd/snaps 4.7G /var/lib/snapd/cache Archived and active journals take up 1.0G in the file system. /opt/iobroker/backups: 235M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 1.4G /opt/iobroker/iobroker-data/ 1.1G /opt/iobroker/iobroker-data/files 617M /opt/iobroker/iobroker-data/files/javascript.admin 560M /opt/iobroker/iobroker-data/files/javascript.admin/static 558M /opt/iobroker/iobroker-data/files/javascript.admin/static/js The five largest files in iobroker-data are: 38M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.d3d286bd.js.map 35M /opt/iobroker/iobroker-data/files/devices.admin/static/js/main.24f2bb56.js.map 26M /opt/iobroker/iobroker-data/files/echarts/static/js/main.41cee985.js.map 26M /opt/iobroker/iobroker-data/files/echarts.admin/chart/static/js/main.41cee985.js.map 24M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.4ff93037.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': /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_18aa58ef5386ec11813de93719c2d21c-if00-port0 *** NodeJS-Installation *** /usr/bin/nodejs v20.17.0 /usr/bin/node v20.17.0 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.29.3 nodejs: Installed: 20.17.0-1nodesource1 Candidate: 20.17.0-1nodesource1 Version table: *** 20.17.0-1nodesource1 100 100 /var/lib/dpkg/status 18.19.1+dfsg-6ubuntu5 500 500 http://archive.ubuntu.com/ubuntu noble/universe amd64 Packages Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected *** ioBroker-Installation *** ioBroker Status No connection to objects 192.168.178.55:6379[redis] Hosts: No connection to objects 192.168.178.55:6379[redis] Core adapters versions js-controller: 7.0.3 admin: 7.1.5 javascript: 8.8.3 nodejs modules from github: 0 Adapter State No connection to objects 192.168.178.55:6379[redis] Enabled adapters with bindings ioBroker-Repositories No connection to objects 192.168.178.55:6379[redis] Installed ioBroker-Instances No connection to objects 192.168.178.55:6379[redis] Objects and States Please stand by - This may take a while Objects: 1 States: 1 *** OS-Repositories and Updates *** Hit:1 http://archive.ubuntu.com/ubuntu noble InRelease Hit:2 http://archive.ubuntu.com/ubuntu noble-updates InRelease Hit:3 http://archive.ubuntu.com/ubuntu noble-backports InRelease Hit:4 http://security.ubuntu.com/ubuntu noble-security InRelease Hit:5 http://security.ubuntu.com/ubuntu focal-security InRelease Hit:6 https://packages.redis.io/deb noble InRelease Hit:7 https://esm.ubuntu.com/apps/ubuntu noble-apps-updates InRelease Hit:8 https://esm.ubuntu.com/apps/ubuntu noble-apps-security InRelease Hit:9 https://esm.ubuntu.com/infra/ubuntu noble-infra-security InRelease Hit:10 https://esm.ubuntu.com/infra/ubuntu noble-infra-updates InRelease Reading package lists... Pending Updates: 0 *** Listening Ports *** Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 127.0.0.1:4711 0.0.0.0:* LISTEN 998 22847 2524/pihole-FTL tcp 0 0 127.0.0.1:6379 0.0.0.0:* LISTEN 109 29557 5888/redis-server 1 tcp 0 0 127.0.0.1:1883 0.0.0.0:* LISTEN 128 16818 1753/mosquitto tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 0 20301 1680/cupsd tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 998 22841 2524/pihole-FTL tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 0 20813 2567/lighttpd tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 0 5118 1/init tcp6 0 0 ::1:1883 :::* LISTEN 128 16819 1753/mosquitto tcp6 0 0 ::1:631 :::* LISTEN 0 20300 1680/cupsd tcp6 0 0 ::1:6379 :::* LISTEN 109 29558 5888/redis-server 1 tcp6 0 0 :::22 :::* LISTEN 0 16541 1/init tcp6 0 0 :::53 :::* LISTEN 998 22843 2524/pihole-FTL tcp6 0 0 :::80 :::* LISTEN 0 20812 2567/lighttpd tcp6 0 0 :::111 :::* LISTEN 0 3353 1/init tcp6 0 0 ::1:4711 :::* LISTEN 998 22848 2524/pihole-FTL udp 0 0 0.0.0.0:52926 0.0.0.0:* 115 12171 1256/avahi-daemon: udp 0 0 0.0.0.0:5353 0.0.0.0:* 115 12169 1256/avahi-daemon: udp 0 0 0.0.0.0:53 0.0.0.0:* 998 22840 2524/pihole-FTL udp 0 0 0.0.0.0:111 0.0.0.0:* 0 5119 1/init udp6 0 0 fe80::e15b:6275:b15:546 :::* 0 20859 1392/NetworkManager udp6 0 0 :::5353 :::* 115 12170 1256/avahi-daemon: udp6 0 0 :::40549 :::* 115 12172 1256/avahi-daemon: udp6 0 0 :::53 :::* 998 22842 2524/pihole-FTL udp6 0 0 :::111 :::* 0 5120 1/init *** Log File - Last 25 Lines *** 2025-01-04 22:18:10.222 - info: host.juergen-NUC8i5BEK ip addresses: 192.168.178.55 2003:f5:974a:8d00:5f57:aa89:9661:bb7c 2003:f5:974a:8d00:444c:1876:f3f8:3715 fe80::e15b:6275:b15e:f4d8 2025-01-04 22:18:40.246 - error: host.juergen-NUC8i5BEK No connection to databases possible, restart 2025-01-04 22:18:40.252 - info: host.juergen-NUC8i5BEK iobroker _restart 2025-01-04 22:18:40.616 - info: host.juergen-NUC8i5BEK iobroker Starting node restart.js 2025-01-04 22:18:45.000 - info: host.juergen-NUC8i5BEK iobroker.js-controller version 7.0.3 js-controller starting 2025-01-04 22:18:45.002 - info: host.juergen-NUC8i5BEK Copyright (c) 2014-2024 bluefox, 2014 hobbyquaker 2025-01-04 22:18:45.002 - info: host.juergen-NUC8i5BEK hostname: juergen-NUC8i5BEK, node: v20.17.0 2025-01-04 22:18:45.003 - info: host.juergen-NUC8i5BEK ip addresses: 192.168.178.55 2003:f5:974a:8d00:5f57:aa89:9661:bb7c 2003:f5:974a:8d00:444c:1876:f3f8:3715 fe80::e15b:6275:b15e:f4d8 2025-01-04 22:19:15.029 - error: host.juergen-NUC8i5BEK No connection to databases possible, restart 2025-01-04 22:19:15.033 - info: host.juergen-NUC8i5BEK iobroker _restart 2025-01-04 22:19:15.395 - info: host.juergen-NUC8i5BEK iobroker Starting node restart.js 2025-01-04 22:19:19.748 - info: host.juergen-NUC8i5BEK iobroker.js-controller version 7.0.3 js-controller starting 2025-01-04 22:19:19.749 - info: host.juergen-NUC8i5BEK Copyright (c) 2014-2024 bluefox, 2014 hobbyquaker 2025-01-04 22:19:19.749 - info: host.juergen-NUC8i5BEK hostname: juergen-NUC8i5BEK, node: v20.17.0 2025-01-04 22:19:19.750 - info: host.juergen-NUC8i5BEK ip addresses: 192.168.178.55 2003:f5:974a:8d00:5f57:aa89:9661:bb7c 2003:f5:974a:8d00:444c:1876:f3f8:3715 fe80::e15b:6275:b15e:f4d8 2025-01-04 22:19:49.775 - error: host.juergen-NUC8i5BEK No connection to databases possible, restart 2025-01-04 22:19:49.780 - info: host.juergen-NUC8i5BEK iobroker _restart 2025-01-04 22:19:50.144 - info: host.juergen-NUC8i5BEK iobroker Starting node restart.js 2025-01-04 22:19:54.484 - info: host.juergen-NUC8i5BEK iobroker.js-controller version 7.0.3 js-controller starting 2025-01-04 22:19:54.486 - info: host.juergen-NUC8i5BEK Copyright (c) 2014-2024 bluefox, 2014 hobbyquaker 2025-01-04 22:19:54.486 - info: host.juergen-NUC8i5BEK hostname: juergen-NUC8i5BEK, node: v20.17.0 2025-01-04 22:19:54.487 - info: host.juergen-NUC8i5BEK ip addresses: 192.168.178.55 2003:f5:974a:8d00:5f57:aa89:9661:bb7c 2003:f5:974a:8d00:444c:1876:f3f8:3715 fe80::e15b:6275:b15e:f4d8 2025-01-04 22:20:24.511 - error: host.juergen-NUC8i5BEK No connection to databases possible, restart 2025-01-04 22:20:24.517 - info: host.juergen-NUC8i5BEK iobroker _restart 2025-01-04 22:20:24.905 - info: host.juergen-NUC8i5BEK iobroker Starting node restart.js============ Mark until here for C&P =============
iob diag has finished.
-
@ünne
Das ist ein snap-Paket.
Schau ich mir nicht an.Verwende statt Schnubbibuntu ein Debian 12.
Dann auch ohne den ganzen Desktop-Zirkus, der da jetzt mitrumpelt. -
Ganz spontan hätte ich da mal das piHole in Verdacht.
Ich kenne mich mit dem Ding nicht aus, aber kann man das zum Testen kurzzeitig ausschalten?Hast Du Deine Netzwerkadresse 192.168.178.55 so in Deine Rediskonfiguration eingegeben?
Setze da mal stattdessen Deine interne Loopback 127.0.0.1 bzw. einfach "default" ein.
(iobroker setup custom) -
@thomas-braun
Ich weiß nicht, wie mir dein Kommentar helfen kann.
Ich habe redis nicht über snap installiert, sondern mit diesen Befehlen:sudo apt install lsb-release curl gpg curl -fsSL https://packages.redis.io/gpg | sudo gpg --dearmor -o /usr/share/keyrings/redis-archive-keyring.gpg echo "deb [signed-by=/usr/share/keyrings/redis-archive-keyring.gpg] https://packages.redis.io/deb $(lsb_release -cs) main" | sudo tee /etc/apt/sources.list.d/redis.list sudo apt update sudo apt install redis sudo service redis-server status sudo systemctl enable redis-server -
Der startet aber nicht:
*** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION * snap.redis.server.service loaded failed failed Service for snap application redis.serverUbuntu scheint da auch ein snap für redis vorzuhalten. Vielleicht beides installiert?
Mit dem Schnubbibuntu-Snap-Gedöns mag ich mich aber nicht beschäftigen.Und auch nicht mit deinem vollaufgeblasenen Desktop-System.
-
@rscsb
Ich glaube, pi-hole ist nicht der Verursacher. Pi-hole läuft schon seit ca. einem Jahr auf dem Rechner, redis seit ein paar Wochen.Aber vielleicht gibt der Grund meines Reboots einen Hinweis:
Ich habe zwei neue Geräte installiert, die ich auch über iobroker steuern konnte. Beide Geräte wollte ich mit einem Blockly-Script verknüpfen, was leider nicht geklappt hat. Die Fehlermeldung lautete: Kann Objekt ID nicht finden. (Also auch schon die Objektdatenbank).
Da, dachte ich, kann ein Neustart helfen. Tat es aber nicht, denn dann kam die Meldung "No connection to objects...".Das waren die ersten Geräte, die ich nach Installation von Redis, mit iobroker verknüpft habe und das erste Script nach der Redis Installation.
Vielleicht kann jemand damit etwas anfangen.Ohne Iobroker merkt man schon den Komfortverlust: Heizungsregelung funktioniert nicht mehr sauber usw.
Kann ich eigentlich über "iobroker setup custom" wieder auf json zurück schalten, bzw was sind die Folgen?
Danke für Hilfe
Jürgen -
@thomas-braun
Sorry, ich bin kein Linux-Spezialist, sondern ein Nutzer.
Die Parallel-Installation könnte eine Erklärung sein.
Wie kann ich denn prüfen, ob beides installiert ist, bzw wie kann ich ggf. die Snap Installation wieder de-installieren?Ich weiß, dass ich dich nerve, aber ich suche halt Unterstützung.
-
@ünne sagte in Nach Neustart keine Verbindung mehr:
Ich weiß, dass ich dich nerve, aber ich suche halt Unterstützung.
Du nervst nicht, ubuntu nervt.
