ioBroker kaputt :-( No connection to objects 127.0.0.1
-
Hallo.
Ich habe mal meinen Container mit ioBroker unter Proxmox geclont. (weil ich aus einem alten Backup was in die VIS kopieren wollte)
Nun startet aber mein originaler ioBroker Container nicht mehr :-(
Ich habe den geclonten Container wieder gelöscht und auch mal testweise ein Backup eingespielt in die alte VM. Hilft aber nicht.Mach ich "iob status" dann kommt:
No connection to objects 127.0.0.1:6379[redis]Was muss ich tun?
Skript v.2023-10-10 *** BASE SYSTEM *** Static hostname: iobroker-lxc Icon name: computer-container Chassis: container Virtualization: lxc Operating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 5.15.126-1-pve Architecture: x86-64 model name : AMD Ryzen 9 4900H with Radeon Graphics Docker : false Virtualization : lxc Kernel : x86_64 Userland : amd64 Systemuptime and Load: 17:15:13 up 11 min, 1 user, load average: 0.83, 0.93, 0.97 CPU threads: 16 *** Time and Time Zones *** Local time: Mon 2023-12-25 17:15:14 CET Universal time: Mon 2023-12-25 16:15:14 UTC RTC time: n/a Time zone: Europe/Berlin (CET, +0100) System clock synchronized: yes NTP service: inactive RTC in local TZ: no *** User and Groups *** iobroker /home/iobroker iobroker tty dialout audio video redis *** X-Server-Setup *** X-Server: false Desktop: Terminal: tty Boot Target: graphical.target *** MEMORY *** total used free shared buff/cache available Mem: 16G 913M 14G 0.0K 835M 15G Swap: 8.2G 0B 8.2G Total: 24G 913M 22G 16384 M total memory 913 M used memory 338 M active memory 1143 M inactive memory 14634 M free memory 0 M buffer memory 835 M swap cache 8191 M total swap 0 M used swap 8191 M free swap *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION * run-rpc_pipefs.mount loaded failed failed RPC Pipe File System * sys-kernel-config.mount loaded failed failed Kernel Configuration File S ystem * nut-driver.service loaded failed failed Network UPS Tools - power d evice driver controller * nut-monitor.service loaded failed failed Network UPS Tools - power d evice monitor and shutdown controller * systemd-journald-audit.socket loaded failed failed Journal Audit Socket 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. 5 loaded units listed. *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/pve-vm--201--disk--0 ext4 63G 20G 40G 33% / none tmpfs 492K 4.0K 488K 1% /dev udev devtmpfs 16G 0 16G 0% /dev/tty tmpfs tmpfs 16G 0 16G 0% /dev/shm tmpfs tmpfs 6.2G 452K 6.2G 1% /run tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs tmpfs 3.1G 0 3.1G 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [sudo] password for iobroker: Sorry, try again. [sudo] password for iobroker: Sorry, try again. [sudo] password for iobroker: sudo: 3 incorrect password attempts Show mounted filesystems \(real ones only\): TARGET SOURCE FSTYPE OPTIONS / /dev/mapper/pve-vm--201--disk--0 ext4 rw,relatime,stripe=16 Files in neuralgic directories: /var: [sudo] password for iobroker: 12G /var/lib 12G /var/ 10G /var/lib/docker 6.8G /var/lib/docker/containers/66af97a102d568e200f457413a4542fc75b1add1081eb 2cd0a8d88ba309befcd 6.8G /var/lib/docker/containers Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. Archived and active journals take up 34.4M in the file system. /opt/iobroker/backups: 2.1G /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 1.1G /opt/iobroker/iobroker-data/ 545M /opt/iobroker/iobroker-data/files 190M /opt/iobroker/iobroker-data/backup-objects 156M /opt/iobroker/iobroker-data/esphome.0/.esphome 156M /opt/iobroker/iobroker-data/esphome.0 The five largest files in iobroker-data are: 134M /opt/iobroker/iobroker-data/states.jsonl 76M /opt/iobroker/iobroker-data/objects.jsonl 63M /opt/iobroker/iobroker-data/esphome.0/.esphome/packages/f43db209/.git/ob jects/pack/pack-3581bc90ccbce7b30129d337ecaa1a965653eb19.pack 41M /opt/iobroker/iobroker-data/files/material/static/js/main.c5478f66.js.ma p 35M /opt/iobroker/iobroker-data/files/devices.admin/static/js/main.24f2bb56. 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.19.0 /usr/bin/node v18.19.0 /usr/bin/npm 10.2.3 /usr/bin/npx 10.2.3 /usr/bin/corepack 0.22.0 nodejs: Installed: 18.19.0-1nodesource1 Candidate: 18.19.0-1nodesource1 Version table: *** 18.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 18.18.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.17.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 12.22.12~dfsg-1~deb11u4 500 500 http://ftp.debian.org/debian bullseye/main amd64 Packages 500 http://security.debian.org bullseye-security/main amd64 Packages Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: npm ERR! code ELSPROBLEMS npm ERR! invalid: xml2js@0.4.23 /opt/iobroker/node_modules/xml2js npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2 023-12-25T16_15_37_326Z-debug-0.log *** ioBroker-Installation *** ioBroker Status No connection to objects 127.0.0.1:6379[redis] Core adapters versions js-controller: 5.0.17 admin: 6.12.0 javascript: 7.1.6 Adapters from github: 3 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 ^C iobroker@iobroker-lxc:~$ ^C iobroker@iobroker-lxc:~$NUC6i7KYK M.2 32GB RAM mit Proxmox
14 AccessPoints, 5 Switches 115 Adapter, 67913 Objekte, 57954 Zustände,126x Shelly, 26 Thermostate, Fire Tablets, DMX, USV, 18x echodot, 9xKlima, 4x heizung, beamer, 6x IP Speed dome, AiOnTheEdge, Tasmota Wemos, Fingerabdrucksensoren, VOIP TFE, Türsteuerung, BMZ,EMA -
Hallo.
Ich habe mal meinen Container mit ioBroker unter Proxmox geclont. (weil ich aus einem alten Backup was in die VIS kopieren wollte)
Nun startet aber mein originaler ioBroker Container nicht mehr :-(
Ich habe den geclonten Container wieder gelöscht und auch mal testweise ein Backup eingespielt in die alte VM. Hilft aber nicht.Mach ich "iob status" dann kommt:
No connection to objects 127.0.0.1:6379[redis]Was muss ich tun?
Skript v.2023-10-10 *** BASE SYSTEM *** Static hostname: iobroker-lxc Icon name: computer-container Chassis: container Virtualization: lxc Operating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 5.15.126-1-pve Architecture: x86-64 model name : AMD Ryzen 9 4900H with Radeon Graphics Docker : false Virtualization : lxc Kernel : x86_64 Userland : amd64 Systemuptime and Load: 17:15:13 up 11 min, 1 user, load average: 0.83, 0.93, 0.97 CPU threads: 16 *** Time and Time Zones *** Local time: Mon 2023-12-25 17:15:14 CET Universal time: Mon 2023-12-25 16:15:14 UTC RTC time: n/a Time zone: Europe/Berlin (CET, +0100) System clock synchronized: yes NTP service: inactive RTC in local TZ: no *** User and Groups *** iobroker /home/iobroker iobroker tty dialout audio video redis *** X-Server-Setup *** X-Server: false Desktop: Terminal: tty Boot Target: graphical.target *** MEMORY *** total used free shared buff/cache available Mem: 16G 913M 14G 0.0K 835M 15G Swap: 8.2G 0B 8.2G Total: 24G 913M 22G 16384 M total memory 913 M used memory 338 M active memory 1143 M inactive memory 14634 M free memory 0 M buffer memory 835 M swap cache 8191 M total swap 0 M used swap 8191 M free swap *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION * run-rpc_pipefs.mount loaded failed failed RPC Pipe File System * sys-kernel-config.mount loaded failed failed Kernel Configuration File S ystem * nut-driver.service loaded failed failed Network UPS Tools - power d evice driver controller * nut-monitor.service loaded failed failed Network UPS Tools - power d evice monitor and shutdown controller * systemd-journald-audit.socket loaded failed failed Journal Audit Socket 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. 5 loaded units listed. *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/pve-vm--201--disk--0 ext4 63G 20G 40G 33% / none tmpfs 492K 4.0K 488K 1% /dev udev devtmpfs 16G 0 16G 0% /dev/tty tmpfs tmpfs 16G 0 16G 0% /dev/shm tmpfs tmpfs 6.2G 452K 6.2G 1% /run tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs tmpfs 3.1G 0 3.1G 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [sudo] password for iobroker: Sorry, try again. [sudo] password for iobroker: Sorry, try again. [sudo] password for iobroker: sudo: 3 incorrect password attempts Show mounted filesystems \(real ones only\): TARGET SOURCE FSTYPE OPTIONS / /dev/mapper/pve-vm--201--disk--0 ext4 rw,relatime,stripe=16 Files in neuralgic directories: /var: [sudo] password for iobroker: 12G /var/lib 12G /var/ 10G /var/lib/docker 6.8G /var/lib/docker/containers/66af97a102d568e200f457413a4542fc75b1add1081eb 2cd0a8d88ba309befcd 6.8G /var/lib/docker/containers Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. Archived and active journals take up 34.4M in the file system. /opt/iobroker/backups: 2.1G /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 1.1G /opt/iobroker/iobroker-data/ 545M /opt/iobroker/iobroker-data/files 190M /opt/iobroker/iobroker-data/backup-objects 156M /opt/iobroker/iobroker-data/esphome.0/.esphome 156M /opt/iobroker/iobroker-data/esphome.0 The five largest files in iobroker-data are: 134M /opt/iobroker/iobroker-data/states.jsonl 76M /opt/iobroker/iobroker-data/objects.jsonl 63M /opt/iobroker/iobroker-data/esphome.0/.esphome/packages/f43db209/.git/ob jects/pack/pack-3581bc90ccbce7b30129d337ecaa1a965653eb19.pack 41M /opt/iobroker/iobroker-data/files/material/static/js/main.c5478f66.js.ma p 35M /opt/iobroker/iobroker-data/files/devices.admin/static/js/main.24f2bb56. 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.19.0 /usr/bin/node v18.19.0 /usr/bin/npm 10.2.3 /usr/bin/npx 10.2.3 /usr/bin/corepack 0.22.0 nodejs: Installed: 18.19.0-1nodesource1 Candidate: 18.19.0-1nodesource1 Version table: *** 18.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 18.18.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.17.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 12.22.12~dfsg-1~deb11u4 500 500 http://ftp.debian.org/debian bullseye/main amd64 Packages 500 http://security.debian.org bullseye-security/main amd64 Packages Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: npm ERR! code ELSPROBLEMS npm ERR! invalid: xml2js@0.4.23 /opt/iobroker/node_modules/xml2js npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2 023-12-25T16_15_37_326Z-debug-0.log *** ioBroker-Installation *** ioBroker Status No connection to objects 127.0.0.1:6379[redis] Core adapters versions js-controller: 5.0.17 admin: 6.12.0 javascript: 7.1.6 Adapters from github: 3 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 ^C iobroker@iobroker-lxc:~$ ^C iobroker@iobroker-lxc:~$@roelli sagte in ioBroker kaputt :-( No connection to objects 127.0.0.1:
testweise ein Backup eingespielt in die alte VM. Hilft aber nicht.
läuft da auch redis? ohne geht das nicht
-
Ha! Du hast natürlich Recht.
Wusste ich nur nicht das man den manuell starten muss. Weil.. ich hatte nach der Redis Installation scheinbar noch garnicht neu gestartet.Note To Self:
Redis starten:
sudo systemctl enable redis-serverRedis automatisch starten lassen:
systemctl enable redis-server.service
Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.
Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.
Mit deinem Input könnte dieser Beitrag noch besser werden 💗
Registrieren Anmelden526
Online32.8k
Benutzer82.8k
Themen1.3m
Beiträge