ioBroker Admin und Vis startet nicht mehr
-
Von Docker hab ich weiter keine Ahnung.
Aber die Doku dazu ist ganz gut. -
Ich habe jetzt mal einen neuen Container mit ioBroker (latest) erstellt. In den Admin Bereich komme ich wie sonst auch wieder rein, aber ist halt alles nackt. Jetzt bleibt die Frage wie ich die Daten vom alten Container in den Neuen bekomme.
-
@x-oli sagte in ioBroker Admin und Vis startet nicht mehr:
Ich habe jetzt mal einen neuen Container mit ioBroker (latest) erstellt.
Wenn mich nicht alles täuscht, kann man unter QNAP die Container duplizieren. Damit werden alle Einstellungen inkl. der Volumes "mitgenommen". Du solltest also den alten Container beenden, duplizieren (hier das latest Image auswählen) und den neuen Container starten. Damit werden die ioBroker-Daten übernommen.
Vorher natürlich den neu erstellten "leeren" Container löschen.
-
@Marc-Berg
Vielen Dank für den Hinweis. Das habe ich tatsächlich immer außer Acht gelassen.- Container ist jetzt auf dem neuesten Stand mit den ioBroker Daten von zuvor.
- Situation ist leider noch immer die Gleiche --> Admin Oberfläche lädt sich tot und startet nicht
- beim starten des Containers gibt es jetzt aber ein paar mehr Infos --> vielleicht hilft das jemandem ? Mir ist tatsächlich schon beim alten Container aufgefallen, dass er immer an der Instanz "tankerkoenig.1" zu kämpfen hatte. Kann ich die manuell (ohne Admin Oberfläche) komplett löschen, um da einen Fehler auszuschließen ?
-------------------------------------------------------------------------------- ------------------------- 2024-06-17 18:09:09 ------------------------- -------------------------------------------------------------------------------- ----- ----- ----- ██╗ ██████╗ ██████╗ ██████╗ ██████╗ ██╗ ██╗ ███████╗ ██████╗ ----- ----- ██║ ██╔═══██╗ ██╔══██╗ ██╔══██╗ ██╔═══██╗ ██║ ██╔╝ ██╔════╝ ██╔══██╗ ----- ----- ██║ ██║ ██║ ██████╔╝ ██████╔╝ ██║ ██║ █████╔╝ █████╗ ██████╔╝ ----- ----- ██║ ██║ ██║ ██╔══██╗ ██╔══██╗ ██║ ██║ ██╔═██╗ ██╔══╝ ██╔══██╗ ----- ----- ██║ ╚██████╔╝ ██████╔╝ ██║ ██║ ╚██████╔╝ ██║ ██╗ ███████╗ ██║ ██║ ----- ----- ╚═╝ ╚═════╝ ╚═════╝ ╚═╝ ╚═╝ ╚═════╝ ╚═╝ ╚═╝ ╚══════╝ ╚═╝ ╚═╝ ----- ----- ----- ----- Welcome to your ioBroker Docker container! ----- ----- Startupscript is now running! ----- ----- Please be patient! ----- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ----- System Information ----- ----- arch: armv7l ----- ----- hostname: ioBroker ----- ----- ----- ----- Version Information ----- ----- image: v9.1.2 ----- ----- build: 2024-06-13T23:44:37+00:00 ----- ----- node: v18.20.3 ----- ----- npm: 10.8.1 ----- ----- ----- ----- Environment Variables ----- ----- SETGID: 1000 ----- ----- SETUID: 1000 ----- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ----- Step 1 of 5: Preparing Container ----- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ----- Step 2 of 5: Detecting ioBroker Installation ----- -------------------------------------------------------------------------------- Existing installation of ioBroker detected in "/opt/iobroker". -------------------------------------------------------------------------------- ----- Step 3 of 5: Checking ioBroker Installation ----- -------------------------------------------------------------------------------- (Re)setting permissions (This might take a while! Please be patient!)... Done. Checking database connection... Done. Hostname in ioBroker matches the hostname of this container. No action required. -------------------------------------------------------------------------------- ----- Step 4 of 5: Applying Special Settings ----- -------------------------------------------------------------------------------- Some adapters have special requirements/ settings which can be activated by the use of environment variables. For more information see ioBroker Docker image docs (https://docs.buanet.de/iobroker-docker-image/docs/). -------------------------------------------------------------------------------- ----- Step 5 of 5: ioBroker Startup ----- -------------------------------------------------------------------------------- Starting ioBroker... ##### #### ### ## # iobroker.js-controller log output # ## ### #### ##### host.ioBroker check instance "system.adapter.admin.0" for host "ioBroker" host.ioBroker check instance "system.adapter.influxdb.0" for host "ioBroker" host.ioBroker check instance "system.adapter.javascript.0" for host "ioBroker" host.ioBroker check instance "system.adapter.scenes.0" for host "ioBroker" host.ioBroker check instance "system.adapter.telegram.0" for host "ioBroker" host.ioBroker check instance "system.adapter.backitup.0" for host "ioBroker" host.ioBroker check instance "system.adapter.alexa2.0" for host "ioBroker" host.ioBroker check instance "system.adapter.cloud.0" for host "ioBroker" host.ioBroker check instance "system.adapter.exchangerates.0" for host "ioBroker" host.ioBroker check instance "system.adapter.hmip.0" for host "ioBroker" host.ioBroker check instance "system.adapter.homeconnect.0" for host "ioBroker" host.ioBroker check instance "system.adapter.hue.0" for host "ioBroker" host.ioBroker check instance "system.adapter.ical.0" for host "ioBroker" host.ioBroker check instance "system.adapter.radar2.0" for host "ioBroker" host.ioBroker check instance "system.adapter.shelly.0" for host "ioBroker" host.ioBroker check instance "system.adapter.tuya.0" for host "ioBroker" host.ioBroker check instance "system.adapter.unifi-protect.0" for host "ioBroker" host.ioBroker check instance "system.adapter.unifi.0" for host "ioBroker" host.ioBroker check instance "system.adapter.mihome.0" for host "ioBroker" host.ioBroker check instance "system.adapter.mihome-vacuum.0" for host "ioBroker" host.ioBroker check instance "system.adapter.nuki-extended.0" for host "ioBroker" host.ioBroker check instance "system.adapter.discovery.0" for host "ioBroker" host.ioBroker check instance "system.adapter.daswetter.0" for host "ioBroker" host.ioBroker check instance "system.adapter.device-reminder.0" for host "ioBroker" host.ioBroker check instance "system.adapter.info.0" for host "ioBroker" host.ioBroker check instance "system.adapter.parser.0" for host "ioBroker" host.ioBroker check instance "system.adapter.pollenflug.0" for host "ioBroker" host.ioBroker check instance "system.adapter.tankerkoenig.0" for host "ioBroker" host.ioBroker check instance "system.adapter.text2command.0" for host "ioBroker" host.ioBroker check instance "system.adapter.trashschedule.0" for host "ioBroker" host.ioBroker check instance "system.adapter.vis-bars.0" for host "ioBroker" host.ioBroker check instance "system.adapter.vis-colorpicker.0" for host "ioBroker" host.ioBroker check instance "system.adapter.vis-fancyswitch.0" for host "ioBroker" host.ioBroker check instance "system.adapter.vis-hqwidgets.0" for host "ioBroker" host.ioBroker check instance "system.adapter.vis-inventwo.0" for host "ioBroker" host.ioBroker check instance "system.adapter.vis-jqui-mfd.0" for host "ioBroker" host.ioBroker check instance "system.adapter.vis-justgage.0" for host "ioBroker" host.ioBroker check instance "system.adapter.vis-rgraph.0" for host "ioBroker" host.ioBroker check instance "system.adapter.vis-timeandweather.0" for host "ioBroker" host.ioBroker check instance "system.adapter.vis.0" for host "ioBroker" host.ioBroker check instance "system.adapter.web.0" for host "ioBroker" host.ioBroker check instance "system.adapter.parcel.0" for host "ioBroker" host.ioBroker check instance "system.adapter.tankerkoenig.1" for host "ioBroker" This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: TypeError: Cannot read properties of undefined (reading 'name') at Hue.getSensorChannelById (/opt/iobroker/node_modules/iobroker.hue/src/main.ts:1325:23) at Hue.handleSensorUpdate (/opt/iobroker/node_modules/iobroker.hue/src/main.ts:1178:34) at Hue.handleUpdate (/opt/iobroker/node_modules/iobroker.hue/src/main.ts:1154:24) at HuePushClient.<anonymous> (/opt/iobroker/node_modules/iobroker.hue/src/main.ts:1117:30) at HuePushClient.emit (node:events:517:28) at HuePushClient.emit (node:domain:489:12) at _emit (/opt/iobroker/node_modules/eventsource/lib/eventsource.js:287:17) at parseEventStreamLine (/opt/iobroker/node_modules/eventsource/lib/eventsource.js:302:9) at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/eventsource/lib/eventsource.js:259:11) at IncomingMessage.emit (node:events:517:28) This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:632:26) at Socket.emit (node:events:517:28) at Socket.emit (node:domain:489:12) at TCP.<anonymous> (node:net:350:12) /bin/sh: 1: mdadm: not found ================================== > LOG REDIRECT system.adapter.admin.0 => true [system.adapter.admin.0.logging] /bin/sh: 1: hcitool: not foundHier mal ein aktueller Auszug von
iob diag:Skript v.2024-05-22 *** BASE SYSTEM *** cat: /sys/devices/virtual/dmi/id/sys_vendor: No such file or directory Hardware Vendor : Kernel : armv7l Userland : 32 bit Docker : v9.1.2 Virtualization : Docker Kernel : armv7l Userland : 32 bit Systemuptime and Load: 18:45:05 up 7:59, 0 user, load average: 3.81, 4.12, 3.87 CPU threads: 4 *** Time and Time Zones *** Mon Jun 17 16:45:05 UTC 2024 Mon Jun 17 18:45:05 CEST 2024 CEST +0200 Etc/UTC *** Users and Groups *** User that called 'iob diag': root HOME=/root GROUPS=root User that is running 'js-controller': iobroker HOME=/opt/iobroker GROUPS=iobroker tty dialout audio video plugdev *** Display-Server-Setup *** Display-Server: false Desktop: Terminal: *** MEMORY *** total used free shared buff/cache available Mem: 8.5G 4.4G 1.6G 280M 3.9G 4.0G Swap: 24G 81K 24G Total: 33G 4.4G 26G Active iob-Instances: 28 8097 M total memory 4237 M used memory 4080 M active memory 2043 M inactive memory 1545 M free memory 278 M buffer memory 3422 M swap cache 23447 M total swap 0 M used swap 23447 M free swap *** top - Table Of Processes *** top - 18:45:06 up 7:59, 0 user, load average: 3.81, 4.12, 3.87 Tasks: 35 total, 2 running, 33 sleeping, 0 stopped, 0 zombie %Cpu(s): 23.1 us, 7.7 sy, 0.0 ni, 46.2 id, 23.1 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 8097.5 total, 1544.4 free, 4238.7 used, 3701.3 buff/cache MiB Swap: 23447.2 total, 23447.2 free, 0.1 used. 3858.8 avail Mem *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on overlay overlay 2.0T 31G 2.0T 2% / tmpfs tmpfs 64M 0 64M 0% /dev tmpfs tmpfs 4.0G 0 4.0G 0% /sys/fs/cgroup shm tmpfs 64M 0 64M 0% /dev/shm /dev/mapper/cachedev1 ext4 2.0T 31G 2.0T 2% /opt/iobroker Messages concerning ext4 filesystem in dmesg: [Mon Jun 17 10:45:33 2024] ext4_init_reserve_inode_table0: sda1, 5 [Mon Jun 17 10:45:33 2024] ext4_init_reserve_inode_table2: sda1, 5, 0, 0, 4096 [Mon Jun 17 10:45:33 2024] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: data=ordered,barrier=1,nodelalloc [Mon Jun 17 10:45:34 2024] ext4_init_reserve_inode_table0: sda1, 5 [Mon Jun 17 10:45:34 2024] ext4_init_reserve_inode_table2: sda1, 5, 0, 0, 4096 [Mon Jun 17 10:45:34 2024] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: [Mon Jun 17 10:45:35 2024] ext4_init_reserve_inode_table0: sdb1, 5 [Mon Jun 17 10:45:35 2024] ext4_init_reserve_inode_table2: sdb1, 5, 0, 0, 4096 [Mon Jun 17 10:45:35 2024] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: [Mon Jun 17 10:45:37 2024] ext4_init_reserve_inode_table0: md9, 5 [Mon Jun 17 10:45:37 2024] ext4_init_reserve_inode_table2: md9, 5, 0, 0, 4096 [Mon Jun 17 10:45:37 2024] EXT4-fs (md9): mounted filesystem with ordered data mode. Opts: data=ordered,barrier=1,nodelalloc [Mon Jun 17 10:45:59 2024] ext4_init_reserve_inode_table0: dm-9, 3 [Mon Jun 17 10:45:59 2024] ext4_init_reserve_inode_table2: dm-9, 3, 0, 0, 4096 [Mon Jun 17 10:45:59 2024] EXT4-fs (dm-9): mounted filesystem with ordered data mode. Opts: data=ordered,barrier=1,nodelalloc [Mon Jun 17 10:46:01 2024] ext4_init_reserve_inode_table0: dm-10, 16384 [Mon Jun 17 10:46:01 2024] ext4_init_reserve_inode_table2: dm-10, 16384, 0, 0, 4096 [Mon Jun 17 10:46:01 2024] EXT4-fs (dm-10): mounted filesystem with ordered data mode. Opts: usrjquota=aquota.user,jqfmt=vfsv1,user_xattr,data=ordered,data_err=abort,delalloc,nopriv,nodiscard,noacl [Mon Jun 17 10:46:31 2024] ext4_init_reserve_inode_table0: md13, 4 [Mon Jun 17 10:46:31 2024] ext4_init_reserve_inode_table2: md13, 4, 0, 0, 4096 [Mon Jun 17 10:46:31 2024] EXT4-fs (md13): mounted filesystem with ordered data mode. Opts: data=ordered,barrier=1,nodelalloc Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / overlay overlay rw,relatime,lowerdir=/share/CACHEDEV1_DATA/Container/container-station-data/lib/docker/overlay2/l/WQR5E6SXTVQJ3ES4UHWS2NJBO2:/share/CACHEDEV1_DATA/Container/container-station-data/lib/docker/overlay2/l/LGQKPLH4TJVX66HW53PEAMMOBZ:/share/CACHEDEV1_DATA/Container/container-station-data/lib/docker/overlay2/l/N6ZWQF7JHJOOMJ5GQG2BJFLYUX:/share/CACHEDEV1_DATA/Container/container-station-data/lib/docker/overlay2/l/FNXVVOHORB6MF3G6UGCLA6LXJY:/share/CACHEDEV1_DATA/Container/container-station-data/lib/docker/overlay2/l/SLN5PJ2RFME5LSHURHYVZQZXEK:/share/CACHEDEV1_DATA/Container/container-station-data/lib/docker/overlay2/l/GXH372PFBBKWLGGTIW7OBOKXUY,upperdir=/share/CACHEDEV1_DATA/Container/container-station-data/lib/docker/overlay2/a4cb0f3d0ee9908eddff0b52dace1fc41858a61aed339c6e85ec7255c6071ca6/diff,workdir=/share/CACHEDEV1_DATA/Container/container-station-data/lib/docker/overlay2/a4cb0f3d0ee9908eddff0b52dace1fc41858a61aed339c6e85ec7255c6071ca6/work |-/proc proc proc rw,nosuid,nodev,noexec,relatime |-/dev tmpfs tmpfs rw,nosuid,size=65536k,mode=755 | |-/dev/console devpts[/0] devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=666 | |-/dev/pts devpts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=666 | |-/dev/mqueue mqueue mqueue rw,nosuid,nodev,noexec,relatime | `-/dev/shm shm tmpfs rw,nosuid,nodev,noexec,relatime,size=65536k |-/sys sysfs sysfs rw,nosuid,nodev,noexec,relatime | `-/sys/fs/cgroup tmpfs tmpfs rw,nosuid,nodev,noexec,relatime,mode=755 | |-/sys/fs/cgroup/memory none[/docker/ae954e88bb7fa7d6b47d8ebc2a5ce8d925550873c78d06e05d1720f8c20087b3] cgroup rw,nosuid,nodev,noexec,relatime,memory | |-/sys/fs/cgroup/cpu cpu[/docker/ae954e88bb7fa7d6b47d8ebc2a5ce8d925550873c78d06e05d1720f8c20087b3] cgroup rw,nosuid,nodev,noexec,relatime,cpu | |-/sys/fs/cgroup/cpuset cgroup[/docker/ae954e88bb7fa7d6b47d8ebc2a5ce8d925550873c78d06e05d1720f8c20087b3] cgroup rw,nosuid,nodev,noexec,relatime,cpuset | |-/sys/fs/cgroup/cpuacct cgroup[/docker/ae954e88bb7fa7d6b47d8ebc2a5ce8d925550873c78d06e05d1720f8c20087b3] cgroup rw,nosuid,nodev,noexec,relatime,cpuacct | |-/sys/fs/cgroup/blkio cgroup[/docker/ae954e88bb7fa7d6b47d8ebc2a5ce8d925550873c78d06e05d1720f8c20087b3] cgroup rw,nosuid,nodev,noexec,relatime,blkio | |-/sys/fs/cgroup/devices cgroup[/docker/ae954e88bb7fa7d6b47d8ebc2a5ce8d925550873c78d06e05d1720f8c20087b3] cgroup rw,nosuid,nodev,noexec,relatime,devices | |-/sys/fs/cgroup/freezer cgroup[/docker/ae954e88bb7fa7d6b47d8ebc2a5ce8d925550873c78d06e05d1720f8c20087b3] cgroup rw,nosuid,nodev,noexec,relatime,freezer | `-/sys/fs/cgroup/systemd cgroup[/docker/ae954e88bb7fa7d6b47d8ebc2a5ce8d925550873c78d06e05d1720f8c20087b3] cgroup rw,nosuid,nodev,noexec,relatime,name=systemd |-/opt/iobroker /dev/mapper/cachedev1[/Docker/iobroker-data] ext4 rw,relatime,no_mbcache,(null),stripe=256,data=ordered,jqfmt=vfsv1,usrjquota=aquota.user |-/etc/resolv.conf /dev/mapper/cachedev1[/Container/container-station-data/lib/docker/containers/ae954e88bb7fa7d6b47d8ebc2a5ce8d925550873c78d06e05d1720f8c20087b3/resolv.conf] ext4 rw,relatime,no_mbcache,(null),stripe=256,data=ordered,jqfmt=vfsv1,usrjquota=aquota.user |-/etc/hostname /dev/mapper/cachedev1[/Container/container-station-data/lib/docker/containers/ae954e88bb7fa7d6b47d8ebc2a5ce8d925550873c78d06e05d1720f8c20087b3/hostname] ext4 rw,relatime,no_mbcache,(null),stripe=256,data=ordered,jqfmt=vfsv1,usrjquota=aquota.user `-/etc/hosts /dev/mapper/cachedev1[/Container/container-station-data/lib/docker/containers/ae954e88bb7fa7d6b47d8ebc2a5ce8d925550873c78d06e05d1720f8c20087b3/hosts] ext4 rw,relatime,no_mbcache,(null),stripe=256,data=ordered,jqfmt=vfsv1,usrjquota=aquota.user Files in neuralgic directories: /var: 15M /var/ 13M /var/lib/dpkg 13M /var/lib 12M /var/lib/dpkg/info 1.9M /var/cache /opt/iobroker/backups: 115M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 725M /opt/iobroker/iobroker-data/ 370M /opt/iobroker/iobroker-data/files 138M /opt/iobroker/iobroker-data/files/javascript.admin 118M /opt/iobroker/iobroker-data/files/javascript.admin/static 118M /opt/iobroker/iobroker-data/backup-objects The five largest files in iobroker-data are: 134M /opt/iobroker/iobroker-data/states.jsonl 104M /opt/iobroker/iobroker-data/objects.jsonl 27M /opt/iobroker/iobroker-data/files/tankerkoenig.admin/build/index.js.map 26M /opt/iobroker/iobroker-data/files/scenes.admin/static/js/main.8947f24d.js.map 24M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.135279a0.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' *** NodeJS-Installation *** /usr/bin/nodejs v18.20.3 /usr/bin/node v18.20.3 /usr/bin/npm 10.8.1 /usr/bin/npx 10.8.1 /usr/bin/corepack 0.28.0 nodejs: Installed: 18.20.3-1nodesource1 Candidate: 18.20.3-1nodesource1 Version table: *** 18.20.3-1nodesource1 100 100 /var/lib/dpkg/status Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Core adapters versions js-controller: 5.0.19 admin: 6.13.16 javascript: 8.3.1 nodejs modules from github: 0 Adapter State + system.adapter.admin.0 : admin : ioBroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.alexa2.0 : alexa2 : ioBroker - enabled system.adapter.alias-manager.0 : alias-manager : ioBroker - disabled + system.adapter.backitup.0 : backitup : ioBroker - enabled + system.adapter.cloud.0 : cloud : ioBroker - enabled system.adapter.daswetter.0 : daswetter : ioBroker - disabled + system.adapter.device-reminder.0 : device-reminder : ioBroker - enabled + system.adapter.discovery.0 : discovery : ioBroker - enabled system.adapter.exchangerates.0 : exchangerates : ioBroker - disabled + system.adapter.hmip.0 : hmip : ioBroker - enabled system.adapter.homeconnect.0 : homeconnect : ioBroker - disabled + system.adapter.hue.0 : hue : ioBroker - enabled, port: 443 system.adapter.ical.0 : ical : ioBroker - enabled system.adapter.icons-mfd-png.0 : icons-mfd-png : ioBroker - disabled system.adapter.icons-ultimate-png.0 : icons-ultimate-png : ioBroker - disabled + system.adapter.influxdb.0 : influxdb : ioBroker - enabled, port: 8086 + system.adapter.info.0 : info : ioBroker - enabled + system.adapter.javascript.0 : javascript : ioBroker - enabled system.adapter.mihome-vacuum.0 : mihome-vacuum : ioBroker - disabled, port: 54321 system.adapter.mihome.0 : mihome : ioBroker - disabled, port: 9898, bind: 192.168.1.126 + system.adapter.nuki-extended.0 : nuki-extended : ioBroker - enabled + system.adapter.parcel.0 : parcel : ioBroker - enabled + system.adapter.parser.0 : parser : ioBroker - enabled + system.adapter.pollenflug.0 : pollenflug : ioBroker - enabled + system.adapter.radar2.0 : radar2 : ioBroker - enabled + system.adapter.scenes.0 : scenes : ioBroker - enabled + system.adapter.shelly.0 : shelly : ioBroker - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.tankerkoenig.0 : tankerkoenig : ioBroker - enabled + system.adapter.tankerkoenig.1 : tankerkoenig : ioBroker - enabled system.adapter.telegram.0 : telegram : ioBroker - disabled, port: 8443, bind: 0.0.0.0 + system.adapter.text2command.0 : text2command : ioBroker - enabled + system.adapter.trashschedule.0 : trashschedule : ioBroker - enabled + system.adapter.tuya.0 : tuya : ioBroker - enabled + system.adapter.unifi-protect.0 : unifi-protect : ioBroker - enabled + system.adapter.unifi.0 : unifi : ioBroker - enabled system.adapter.vis-bars.0 : vis-bars : ioBroker - disabled system.adapter.vis-colorpicker.0 : vis-colorpicker : ioBroker - disabled system.adapter.vis-fancyswitch.0 : vis-fancyswitch : ioBroker - disabled system.adapter.vis-hqwidgets.0 : vis-hqwidgets : ioBroker - disabled system.adapter.vis-icontwo.0 : vis-icontwo : ioBroker - disabled + system.adapter.vis-inventwo.0 : vis-inventwo : ioBroker - enabled system.adapter.vis-jqui-mfd.0 : vis-jqui-mfd : ioBroker - disabled system.adapter.vis-justgage.0 : vis-justgage : ioBroker - disabled system.adapter.vis-rgraph.0 : vis-rgraph : ioBroker - disabled system.adapter.vis-timeandweather.0 : vis-timeandweather : ioBroker - disabled system.adapter.vis.0 : vis : ioBroker - enabled + system.adapter.web.0 : web : ioBroker - enabled, port: 8080, bind: 0.0.0.0, run as: admin + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : ioBroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.hue.0 : hue : ioBroker - enabled, port: 443 + system.adapter.influxdb.0 : influxdb : ioBroker - enabled, port: 8086 + system.adapter.shelly.0 : shelly : ioBroker - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.web.0 : web : ioBroker - enabled, port: 8080, bind: 0.0.0.0, run as: admin ioBroker-Repositories stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json Active repo(s): stable Installed ioBroker-Instances Used repository: stable Adapter "admin" : 6.13.16 , installed 6.13.16 Adapter "alexa2" : 3.26.5 , installed 3.26.5 Adapter "alias-manager": 1.2.6 , installed 1.2.6 Adapter "backitup" : 2.11.0 , installed 2.11.0 Adapter "cloud" : 5.0.1 , installed 5.0.1 Adapter "daswetter" : 3.1.15 , installed 3.1.15 Adapter "device-reminder": 3.1.2 , installed 3.1.2 Adapter "discovery" : 4.5.0 , installed 4.5.0 Adapter "exchangerates": 0.1.0 , installed 0.1.0 Adapter "hmip" : 1.22.0 , installed 1.22.0 Adapter "homeconnect" : 1.4.0 , installed 1.4.0 Adapter "hue" : 3.11.0 , installed 3.11.0 Adapter "ical" : 1.15.0 , installed 1.15.0 Adapter "icons-mfd-png": 1.2.1 , installed 1.2.1 Adapter "icons-ultimate-png": 1.0.1, installed 1.0.1 Adapter "influxdb" : 4.0.2 , installed 4.0.2 Adapter "javascript" : 8.3.1 , installed 8.3.1 Controller "js-controller": 5.0.19 , installed 5.0.19 Adapter "mihome" : 1.4.0 , installed 1.4.0 Adapter "mihome-vacuum": 4.2.0 , installed 4.2.0 Adapter "nuki-extended": 2.7.0 , installed 2.7.0 Adapter "parser" : 2.1.0 , installed 2.1.0 Adapter "pollenflug" : 1.0.6 , installed 1.0.6 Adapter "radar2" : 2.2.0 , installed 2.2.0 Adapter "scenes" : 3.0.4 , installed 3.0.4 Adapter "shelly" : 7.0.0 , installed 7.0.0 Adapter "simple-api" : 2.8.0 , installed 2.8.0 Adapter "socketio" : 6.7.0 , installed 6.7.0 Adapter "tankerkoenig" : 3.4.0 , installed 3.4.0 Adapter "telegram" : 3.3.2 , installed 3.3.2 Adapter "text2command" : 3.0.3 , installed 3.0.3 Adapter "trashschedule": 3.3.0 , installed 3.3.0 Adapter "tuya" : 3.15.0 , installed 3.15.0 Adapter "unifi" : 0.7.0 , installed 0.7.0 Adapter "unifi-protect": 1.0.0 , installed 1.0.0 Adapter "vis" : 1.5.6 , installed 1.5.6 Adapter "vis-bars" : 0.1.4 , installed 0.1.4 Adapter "vis-colorpicker": 2.0.3 , installed 2.0.3 Adapter "vis-fancyswitch": 1.1.0 , installed 1.1.0 Adapter "vis-hqwidgets": 1.5.1 , installed 1.5.1 Adapter "vis-icontwo" : 1.5.0 , installed 1.5.0 Adapter "vis-inventwo" : 3.3.4 , installed 3.3.4 Adapter "vis-jqui-mfd" : 1.1.1 , installed 1.1.1 Adapter "vis-justgage" : 2.1.7 , installed 2.1.7 Adapter "vis-rgraph" : 0.0.2 , installed 0.0.2 Adapter "vis-timeandweather": 1.2.2, installed 1.2.2 Adapter "web" : 6.2.5 , installed 6.2.5 Adapter "ws" : 2.6.1 , installed 2.6.1 Objects and States Please stand by - This may take a while Objects: 127333 States: 94827 *** OS-Repositories and Updates *** Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://deb.debian.org/debian bookworm-updates InRelease Hit:3 http://deb.debian.org/debian-security bookworm-security InRelease Hit:4 https://deb.nodesource.com/node_18.x nodistro 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:9000 0.0.0.0:* LISTEN 1000 2515595 239/iobroker.js-con tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1000 2511648 239/iobroker.js-con tcp 0 0 127.0.0.11:45065 0.0.0.0:* LISTEN 0 2489265 - tcp6 0 0 :::8080 :::* LISTEN 1000 2587606 685/io.web.0 tcp6 0 0 :::8081 :::* LISTEN 1000 2564590 280/io.admin.0 udp 0 0 0.0.0.0:6666 0.0.0.0:* 1000 2590846 472/io.tuya.0 udp 0 0 0.0.0.0:6667 0.0.0.0:* 1000 2590847 472/io.tuya.0 udp 0 0 0.0.0.0:5683 0.0.0.0:* 1000 2606932 449/io.shelly.0 udp 0 0 127.0.0.11:46114 0.0.0.0:* 0 2489264 - udp 0 0 0.0.0.0:67 0.0.0.0:* 1000 2564502 438/io.radar2.0 *** Log File - Last 25 Lines *** 2024-06-17 18:51:28.058 - info: shelly.0 (449) [authEnabled] 192.168.1.37 (shelly1pm / shelly1pm-D8BFC01A0D3F / SHSW-PM#D8BFC01A0D3F#1): This device is not protected via restricted login (see adapter documentation for details) 2024-06-17 18:51:28.069 - info: shelly.0 (449) [authEnabled] 192.168.1.173 (shelly1pm / shelly1pm-F4CFA2E3885F / SHSW-PM#F4CFA2E3885F#1): This device is not protected via restricted login (see adapter documentation for details) 2024-06-17 18:51:28.073 - info: shelly.0 (449) [authEnabled] 192.168.1.95 (shelly1pm / shelly1pm-E09806A9C7ED / SHSW-PM#E09806A9C7ED#1): This device is not protected via restricted login (see adapter documentation for details) 2024-06-17 18:51:28.103 - info: shelly.0 (449) [authEnabled] 192.168.1.49 (shelly1pm / shelly1pm-F4CFA2E3B04B / SHSW-PM#F4CFA2E3B04B#1): This device is not protected via restricted login (see adapter documentation for details) 2024-06-17 18:51:28.145 - info: shelly.0 (449) [authEnabled] 192.168.1.75 (shelly1pm / shelly1pm-F4CFA2E3AF49 / SHSW-PM#F4CFA2E3AF49#1): This device is not protected via restricted login (see adapter documentation for details) 2024-06-17 18:51:28.213 - info: shelly.0 (449) [authEnabled] 192.168.1.151 (shelly1pm / shelly1pm-8CAAB542FD4A / SHSW-PM#8CAAB542FD4A#1): This device is not protected via restricted login (see adapter documentation for details) 2024-06-17 18:51:28.218 - info: shelly.0 (449) [authEnabled] 192.168.1.52 (shelly1pm / shelly1pm-D8BFC01A09FE / SHSW-PM#D8BFC01A09FE#1): This device is not protected via restricted login (see adapter documentation for details) 2024-06-17 18:51:28.399 - info: shelly.0 (449) [authEnabled] 192.168.1.45 (shelly1pm / shelly1pm-D8BFC01A19CB / SHSW-PM#D8BFC01A19CB#1): This device is not protected via restricted login (see adapter documentation for details) 2024-06-17 18:51:28.567 - info: shelly.0 (449) [authEnabled] 192.168.1.192 (shelly1pm / shelly1pm-E89F6D851685 / SHSW-PM#E89F6D851685#1): This device is not protected via restricted login (see adapter documentation for details) 2024-06-17 18:51:28.778 - info: shelly.0 (449) [authEnabled] 192.168.1.96 (shelly1pm / shelly1pm-D8BFC019C5AC / SHSW-PM#D8BFC019C5AC#1): This device is not protected via restricted login (see adapter documentation for details) 2024-06-17 18:51:28.790 - info: shelly.0 (449) [authEnabled] 192.168.1.59 (shellyswitch25 / shellyswitch25-483FDA4DA761 / SHSW-25#483FDA4DA761#1): This device is not protected via restricted login (see adapter documentation for details) 2024-06-17 18:51:28.850 - info: shelly.0 (449) [authEnabled] 192.168.1.189 (shellyswitch25 / shellyswitch25-40F520009F32 / SHSW-25#40F520009F32#1): This device is not protected via restricted login (see adapter documentation for details) 2024-06-17 18:51:28.900 - info: shelly.0 (449) [authEnabled] 192.168.1.91 (shellyswitch25 / shellyswitch25-10521CF1375C / SHSW-25#10521CF1375C#1): This device is not protected via restricted login (see adapter documentation for details) 2024-06-17 18:51:28.930 - info: shelly.0 (449) [authEnabled] 192.168.1.42 (shellyswitch25 / shellyswitch25-483FDA4CFBD4 / SHSW-25#483FDA4CFBD4#1): This device is not protected via restricted login (see adapter documentation for details) 2024-06-17 18:51:28.962 - warn: parser.0 (595) Cannot read link "http://192.168.1.118/general/information.html?kind=item": AxiosError: timeout of 60000ms exceeded 2024-06-17 18:51:28.964 - warn: parser.0 (595) Cannot read link "http://192.168.1.118/general/information.html?kind=item": AxiosError: timeout of 60000ms exceeded 2024-06-17 18:51:28.990 - info: shelly.0 (449) [authEnabled] 192.168.1.114 (shelly1pm / shelly1pm-D8BFC01A1497 / SHSW-PM#D8BFC01A1497#1): This device is not protected via restricted login (see adapter documentation for details) 2024-06-17 18:51:29.009 - info: shelly.0 (449) [authEnabled] 192.168.1.148 (shelly1pm / shelly1pm-D8BFC019C8FF / SHSW-PM#D8BFC019C8FF#1): This device is not protected via restricted login (see adapter documentation for details) 2024-06-17 18:51:29.168 - info: shelly.0 (449) [authEnabled] 192.168.1.111 (shelly1pm / shelly1pm-D8BFC019C74F / SHSW-PM#D8BFC019C74F#1): This device is not protected via restricted login (see adapter documentation for details) 2024-06-17 18:51:29.189 - info: shelly.0 (449) [authEnabled] 192.168.1.115 (shelly1pm / shelly1pm-D8BFC01A17FD / SHSW-PM#D8BFC01A17FD#1): This device is not protected via restricted login (see adapter documentation for details) 2024-06-17 18:51:29.270 - info: shelly.0 (449) [authEnabled] 192.168.1.100 (shelly1pm / shelly1pm-D8BFC01A10F1 / SHSW-PM#D8BFC01A10F1#1): This device is not protected via restricted login (see adapter documentation for details) 2024-06-17 18:51:29.662 - info: shelly.0 (449) [authEnabled] 192.168.1.147 (shelly1pm / shelly1pm-D8BFC019C211 / SHSW-PM#D8BFC019C211#1): This device is not protected via restricted login (see adapter documentation for details) 2024-06-17 18:51:30.445 - info: shelly.0 (449) [authEnabled] 192.168.1.164 (shellyswitch25 / shellyswitch25-F4CFA2E0B332 / SHSW-25#F4CFA2E0B332#1): This device is not protected via restricted login (see adapter documentation for details) 2024-06-17 18:51:31.149 - info: shelly.0 (449) [authEnabled] 192.168.1.108 (shelly1pm / shelly1pm-D8BFC01A134D / SHSW-PM#D8BFC01A134D#1): This device is not protected via restricted login (see adapter documentation for details) 2024-06-17 18:51:35.084 - info: shelly.0 (449) [authEnabled] 192.168.1.109 (shelly1pm / shelly1pm-E09806A9FEBF / SHSW-PM#E09806A9FEBF#1): This device is not protected via restricted login (see adapter documentation for details)und noch dazu das "Summary":
model name : Annapurna Labs Alpine AL314 Quad-core ARM Cortex-A15 CPU @ 1.70GHz Kernel : armv7l Userland : armhf Docker : v9.1.2 Installation: Docker Kernel: armv7l Userland: 32 bit Timezone: CEST +0200 User-ID: 0 Display-Server: false Pending OS-Updates: 0 Pending iob updates: 0 Nodejs-Installation: /usr/bin/nodejs v18.20.3 /usr/bin/node v18.20.3 /usr/bin/npm 10.8.1 /usr/bin/npx 10.8.1 /usr/bin/corepack 0.28.0 Recommended versions are nodejs 18.20.3 and npm 10.7.0 Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 8.5G 4.5G 1.6G 280M 3.8G 4.0G Swap: 24G 184K 24G Total: 33G 4.5G 26G Active iob-Instances: 28 Active repo(s): stable ioBroker Core: js-controller 5.0.19 admin 6.13.16 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: + system.adapter.admin.0 : admin : ioBroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : ioBroker - enabled, port: 8080, bind: 0.0.0.0, run as: admin Objects: 127333 States: 94827 Size of iob-Database: 111M /opt/iobroker/iobroker-data/objects.jsonl 140M /opt/iobroker/iobroker-data/states.jsonl -
@x-oli deine Festplatte, dein Dateisystem hat einen Treffer.
Ro75.
-
@x-oli sagte in ioBroker Admin und Vis startet nicht mehr:
Systemuptime and Load:
18:45:05 up 7:59, 0 user, load average: 3.81, 4.12, 3.87
CPU threads: 4Die Kiste ist aber auch schon gut ausgelastet...
Die Fehlermeldungen kommen aber nicht vom tankerkoenig sondern von hue.
iob stop hueund dann mal schauen was da passiert.
-
@ro75 sagte in ioBroker Admin und Vis startet nicht mehr:
@x-oli deine Festplatte, dein Dateisystem hat einen Treffer.
Oh, ja, das schaut nach Trouble aus. Hab ich übersehen.
-
lässt sich nicht stoppen:
iob stop hue Unable to enable Expiry Keyspace events from Redis Server: Connection is closed. Connection is closed. Uncaught Rejection: Error: States DB is not allowed to start in the current Multihost environment at Redis.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-states-redis/build/lib/states/statesInRedisClient.js:459:23) at process.processTicksAndRejections (node:internal/process/task_queues:95:5)@ro75 said in ioBroker Admin und Vis startet nicht mehr:
@x-oli deine Festplatte, dein Dateisystem hat einen Treffer.
Ro75.
Was genau meinte ihr damit ? Woran sehe ich das ? Sollte ich Festplatte tauschen ? Da hängt ein RAID mit 2 Platten drin.
Die Kiste ist aber auch schon gut ausgelastet...
Ja das merke ich auch .. obwohl die Leistung gar nicht zu wenig ist und da eigentlich nicht viel drauf läuft.
-
Hier ruft das Dateisystem um Hilfe:
Messages concerning ext4 filesystem in dmesg: [Mon Jun 17 10:45:33 2024] ext4_init_reserve_inode_table0: sda1, 5 [Mon Jun 17 10:45:33 2024] ext4_init_reserve_inode_table2: sda1, 5, 0, 0, 4096 [Mon Jun 17 10:45:33 2024] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: data=ordered,barrier=1,nodelalloc [Mon Jun 17 10:45:34 2024] ext4_init_reserve_inode_table0: sda1, 5 [Mon Jun 17 10:45:34 2024] ext4_init_reserve_inode_table2: sda1, 5, 0, 0, 4096 [Mon Jun 17 10:45:34 2024] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: [Mon Jun 17 10:45:35 2024] ext4_init_reserve_inode_table0: sdb1, 5 [Mon Jun 17 10:45:35 2024] ext4_init_reserve_inode_table2: sdb1, 5, 0, 0, 4096 [Mon Jun 17 10:45:35 2024] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: [Mon Jun 17 10:45:37 2024] ext4_init_reserve_inode_table0: md9, 5 [Mon Jun 17 10:45:37 2024] ext4_init_reserve_inode_table2: md9, 5, 0, 0, 4096 [Mon Jun 17 10:45:37 2024] EXT4-fs (md9): mounted filesystem with ordered data mode. Opts: data=ordered,barrier=1,nodelalloc [Mon Jun 17 10:45:59 2024] ext4_init_reserve_inode_table0: dm-9, 3 [Mon Jun 17 10:45:59 2024] ext4_init_reserve_inode_table2: dm-9, 3, 0, 0, 4096 [Mon Jun 17 10:45:59 2024] EXT4-fs (dm-9): mounted filesystem with ordered data mode. Opts: data=ordered,barrier=1,nodelalloc [Mon Jun 17 10:46:01 2024] ext4_init_reserve_inode_table0: dm-10, 16384 [Mon Jun 17 10:46:01 2024] ext4_init_reserve_inode_table2: dm-10, 16384, 0, 0, 4096 [Mon Jun 17 10:46:01 2024] EXT4-fs (dm-10): mounted filesystem with ordered data mode. Opts: usrjquota=aquota.user,jqfmt=vfsv1,user_xattr,data=ordered,data_err=abort,delalloc,nopriv,nodiscard,noacl [Mon Jun 17 10:46:31 2024] ext4_init_reserve_inode_table0: md13, 4 [Mon Jun 17 10:46:31 2024] ext4_init_reserve_inode_table2: md13, 4, 0, 0, 4096 [Mon Jun 17 10:46:31 2024] EXT4-fs (md13): mounted filesystem with ordered data mode. Opts: data=ordered,barrier=1,nodelalloc -
Wird man sich wahrscheinlich nicht drauf verlassen können, wenn das System Fehler ausspuckt.
Kann das mit meinen Problemen zu tun haben und sollte / muß die Platte getauscht werden, oder gibt es da andere Lösungen ? -
Das kann auch vom RAM kommen.
Google mal nach den Fehlermeldungen.
ext4_init_reserve_inode_table0 -
@thomas-braun said in ioBroker Admin und Vis startet nicht mehr:
sda1
Guten Morgen
Oh je .. das klingt nach großen Problemen. Das Thema RAM ist schnell zu testen. Ich werde heute oder morgen mal ein neues Modul einsetzen. Die Festplatten lasse ich gerade mal "intensiv" testen .. der sollte mir da ja irgendwas anzeigen wenn Sektoren kaputt sind ?!Es ist halt alles so mega langsam durch diese hohe Auslastung. Gibt es noch etwas Anderes was ich angehen und testen kann ?
LG Oli
-
@x-oli "Langsam" ist der Computer, weil er Probleme hat Daten von bzw. auf die Festplatte zu schreiben. Es kommt zum Stau.
Ro75.
