ioBroker sehr träg und langsam
-
Hallo zusammen
Mein ioBroker ist ziemlich träge und langsam... jeder klick dauert.
htop sieht meiner Meinung nach nicht besondersschlimm aus:
iobroker läuft in einer VM über Proxmox mit 6gb Ram und 2 CPU Kernen..
Gruss Raphi
-
-
@thomas-braun said in ioBroker sehr träg und langsam:
iob diag
bin zu doof:
rapha@ioBroker:~$ sudo iob diag [sudo] Passwort für rapha: Leider darf der Benutzer rapha »/usr/bin/iob diag« als root auf ioBroker nicht ausführen. -
@cainam
Wo steht dass Du das als "su" ausführen sollst? -
-
-
danke für eine kurze debian instruktion: wie mache ich das richtig, resp. passe ich es an
groups rapha cdrom floppy audio dip video plugdev netdev rapha@ioBroker:~$ -
Den rapha abmelden.
Als root:usermod -a -G sudo,adm,iobroker raphaDann den root abmelden, rapha wieder anmelden, im weiteren nie mehr direkt als root herumhampeln und iobroker-Kommandos nie mit
sudoeinleiten.Den
iobroker fixausführen.
-
Danke ein fix habe ich gemacht... jedoch habe ich nun diverse fehlermeldungen im protokol:
telegram.0 2024-01-26 22:53:32.920 error Cannot send message [chatId - 907966621]: Error: EFATAL: Error: read ETIMEDOUT telegram.0 2024-01-26 22:45:49.021 error getMe (reconnect #0) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org telegram.0 2024-01-26 22:45:28.996 warn polling_error: EFATAL, EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org mqtt.0 2024-01-26 22:45:22.950 warn Client [Wasserzaehler_0] Message 9 deleted after 11 retries telegram.0 2024-01-26 22:45:12.937 error Cannot send message [chatId - 907966621]: Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org telegram.0 2024-01-26 22:45:07.954 error Cannot send message [chatId - 907966621]: Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org telegram.0 2024-01-26 22:44:52.922 error Cannot send message [chatId - 907966621]: Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org telegram.0 2024-01-26 22:44:47.933 error Cannot send message [chatId - 907966621]: Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org javascript.0 2024-01-26 22:44:32.893 warn script.js.Informationen.Influx_offline: telegram: InfluxDB hat einen Fehler und ist OFFLINE!!!!! influxdb.0 2024-01-26 22:44:32.885 error Error during ping: RequestTimedOutError: Request timed out. Attempting reconnect. influxdb.0 2024-01-26 22:44:28.730 warn Error on writePoint("{"value":28.4,"time":"2024-01-26T21:43:58.720Z","from":"system.adapter.shelly.0","q":0,"ack":true}): RequestTimedOutError: Request timed out / "Request timed out"" influxdb.0 2024-01-26 22:44:28.729 warn Point could not be written to database: iobroker influxdb.1 2024-01-26 22:44:26.346 error Error during ping: RequestTimedOutError: Request timed out. Attempting reconnect. influxdb.0 2024-01-26 22:44:24.713 warn Error on writePoint("{"value":0.53,"time":"2024-01-26T21:43:54.699Z","from":"system.adapter.shelly.0","q":0,"ack":true}): RequestTimedOutError: Request timed out / "Request timed out"" influxdb.0 2024-01-26 22:44:24.713 warn Point could not be written to database: iobroker influxdb.0 2024-01-26 22:44:24.707 warn Error on writePoint("{"value":67.39,"time":"2024-01-26T21:43:54.699Z","from":"system.adapter.shelly.0","q":0,"ack":true}): RequestTimedOutError: Request timed out / "Request timed out"" influxdb.0 2024-01-26 22:44:24.706 warn Point could not be written to database: iobroker influxdb.0 2024-01-26 22:44:24.694 warn Error on writePoint("{"value":174.63,"time":"2024-01-26T21:43:54.682Z","from":"system.adapter.shelly.0","q":0,"ack":true}): RequestTimedOutError: Request timed out / "Request timed out"" influxdb.0 2024-01-26 22:44:24.693 warn Point could not be written to database: iobroker influxdb.0 2024-01-26 22:44:24.686 warn Error on writePoint("{"value":287.68,"time":"2024-01-26T21:43:54.681Z","from":"system.adapter.shelly.0","q":0,"ack":true}): RequestTimedOutError: Request timed out / "Request timed out"" influxdb.0 2024-01-26 22:44:24.686 warn Point could not be written to database: iobroker telegram.0 2024-01-26 22:44:22.991 error Cannot send message [chatId - 907966621]: Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org telegram.0 2024-01-26 22:44:22.916 error Cannot send message [chatId - 907966621]: Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org influxdb.0 2024-01-26 22:44:18.730 warn Error on writePoint("{"value":28.6,"time":"2024-01-26T21:43:48.720Z","from":"system.adapter.shelly.0","q":0,"ack":true}): RequestTimedOutError: Request timed out / "Request timed out"" influxdb.0 2024-01-26 22:44:18.726 warn Point could not be written to database: iobroker influxdb.0 2024-01-26 22:44:17.884 error Error during ping: RequestTimedOutError: Request timed out. Attempting reconnect. influxdb.0 2024-01-26 22:44:13.729 warn Error on writePoint("{"value":28.8,"time":"2024-01-26T21:43:43.722Z","from":"system.adapter.shelly.0","q":0,"ack":true}): RequestTimedOutError: Request timed out / "Request timed out"" influxdb.0 2024-01-26 22:44:13.727 warn Point could not be written to database: iobroker tuya.0 2024-01-26 22:44:12.908 warn bf0a6cadad47907ceb6ddu: Error on Reconnect (1): connection timed out influxdb.1 2024-01-26 22:44:11.345 error Error during ping: RequestTimedOutError: Request timed out. Attempting reconnect. influxdb.0 2024-01-26 22:44:09.749 warn Error on writePoint("{"value":70.12,"time":"2024-01-26T21:43:39.731Z","from":"system.adapter.shelly.0","q":0,"ack":true}): RequestTimedOutError: Request timed out / "Request timed out"" influxdb.0 2024-01-26 22:44:09.748 warn Point could not be written to database: iobroker influxdb.0 2024-01-26 22:44:09.739 warn Error on writePoint("{"value":172.95,"time":"2024-01-26T21:43:39.728Z","from":"system.adapter.shelly.0","q":0,"ack":true}): RequestTimedOutError: Request timed out / "Request timed out"" influxdb.0 2024-01-26 22:44:09.738 warn Point could not be written to database: iobroker influxdb.0 2024-01-26 22:44:09.734 warn Error on writePoint("{"value":289.74,"time":"2024-01-26T21:43:39.728Z","from":"system.adapter.shelly.0","q":0,"ack":true}): RequestTimedOutError: Request timed out / "Request timed out"" influxdb.0 2024-01-26 22:44:09.733 warn Point could not be written to database: iobroker influxdb.0 2024-01-26 22:44:08.733 warn Error on writePoint("{"value":29.1,"time":"2024-01-26T21:43:38.725Z","from":"system.adapter.shelly.0","q":0,"ack":true}): RequestTimedOutError: Request timed out / "Request timed out"" influxdb.0 2024-01-26 22:44:08.730 warn Point could not be written to database: iobroker influxdb.0 2024-01-26 22:44:03.752 warn Error on writePoint("{"value":29.3,"time":"2024-01-26T21:43:33.747Z","from":"system.adapter.shelly.0","q":0,"ack":true}): RequestTimedOutError: Request timed out / "Request timed out"" influxdb.0 2024-01-26 22:44:03.751 warn Point could not be written to database: iobroker javascript.0 2024-01-26 22:44:02.892 warn script.js.Informationen.Influx_offline: telegram: InfluxDB hat einen Fehler und ist OFFLINE!!!!! influxdb.0 2024-01-26 22:44:02.885 error Error during ping: RequestTimedOutError: Request timed out. Attempting reconnect. modbus.0 2024-01-26 22:43:37.291 warn Poll error count: 1 code: {"err":"timeout","timeout":5000} modbus.0 2024-01-26 22:43:37.290 error Client in error state. modbus.0 2024-01-26 22:43:37.290 error Request timed out. modbus.0 2024-01-26 22:43:37.289 warn Error: undefined telegram.0 2024-01-26 22:43:22.857 error Cannot send message [chatId - 907966621]: Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org influxdb.1 2024-01-26 22:43:01.263 error RequestTimedOutError: Request timed out influxdb.0 2024-01-26 22:42:37.543 error RequestTimedOutError: Request timed out influxdb.1 2024-01-26 22:42:21.258 error RequestTimedOutError: Request timed out influxdb.0 2024-01-26 22:41:57.540 error RequestTimedOutError: Request timed out telegram.0 2024-01-26 22:41:56.890 error Cannot send message [chatId - 907966621]: Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org influxdb.1 2024-01-26 22:41:41.255 error RequestTimedOutError: Request timed out telegram.0 2024-01-26 22:41:37.565 error Cannot send message [chatId - 907966621]: Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org telegram.0 2024-01-26 22:41:36.871 error Cannot send message [chatId - 907966621]: Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org javascript.0 2024-01-26 22:41:17.543 warn script.js.Informationen.Influx_offline: telegram: InfluxDB hat einen Fehler und ist OFFLINE!!!!! influxdb.0 2024-01-26 22:41:17.536 error RequestTimedOutError: Request timed out influxdb.1 2024-01-26 22:41:01.250 error RequestTimedOutError: Request timed out influxdb.0 2024-01-26 22:40:59.713 error RequestTimedOutError: Request timed out telegram.0 2024-01-26 22:40:41.560 error Cannot send message [chatId - 907966621]: Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org influxdb.0 2024-01-26 22:40:37.533 error RequestTimedOutError: Request timed out influxdb.1 2024-01-26 22:40:21.245 error RequestTimedOutError: Request timed out influxdb.0 2024-01-26 22:40:19.709 error RequestTimedOutError: Request timed out telegram.0 2024-01-26 22:40:17.593 error Cannot send message [chatId - 907966621]: Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org influxdb.0 2024-01-26 22:40:09.706 warn Error on writePoint("{"value":755.95,"time":"2024-01-26T21:39:39.701Z","from":"system.adapter.shelly.0","q":0,"ack":true}): RequestTimedOutError: Request timed out / "Request timed out"" influxdb.0 2024-01-26 22:40:09.706 warn Point could not be written to database: iobroker influxdb.0 2024-01-26 22:40:09.658 warn Error on writePoint("{"value":3.58,"time":"2024-01-26T21:39:39.654Z","from":"system.adapter.shelly.0","q":0,"ack":true}): RequestTimedOutError: Request timed out / "Request timed out"" influxdb.0 2024-01-26 22:40:09.657 warn Point could not be written to database: iobroker influxdb.0 2024-01-26 22:40:09.610 warn Error on writePoint("{"value":14743296.8,"time":"2024-01-26T21:39:39.605Z","from":"system.adapter.shelly.0","q":0,"ack":true}): RequestTimedOutError: Request timed out / "Request timed out"" influxdb.0 2024-01-26 22:40:09.610 warn Point could not be written to database: iobroker influxdb.0 2024-01-26 22:40:08.874 warn Error on writePoint("{"value":753,"time":"2024-01-26T21:39:38.867Z","from":"system.adapter.javascript.0","q":0,"ack":true}): RequestTimedOutError: Request timed out / "Request timed out"" influxdb.0 2024-01-26 22:40:08.873 warn Point could not be written to database: iobroker influxdb.0 2024-01-26 22:40:08.869 warn Error on writePoint("{"value":-753,"time":"2024-01-26T21:39:38.861Z","from":"system.adapter.javascript.0","q":0,"ack":true}): RequestTimedOutError: Request timed out / "Request timed out"" influxdb.0 2024-01-26 22:40:08.868 warn Point could not be written to database: iobroker influxdb.0 2024-01-26 22:40:08.719 warn Error on writePoint("{"value":26.2,"time":"2024-01-26T21:39:08.709Z","from":"system.adapter.shelly.0","q":0,"ack":true}): RequestTimedOutError: Request timed out / "Request timed out"" influxdb.0 2024-01-26 22:40:08.717 warn Point could not be written to database: iobroker influxdb.0 2024-01-26 22:40:08.656 warn Error on writePoint("{"value":750,"time":"2024-01-26T21:39:08.638Z","from":"system.adapter.javascript.0","q":0,"ack":true}): RequestTimedOutError: Request timed out / "Request timed out"" influxdb.0 2024-01-26 22:40:08.656 warn Point could not be written to database: iobroker influxdb.0 2024-01-26 22:40:08.646 warn Error on writePoint("{"value":-750,"time":"2024-01-26T21:39:08.632Z","from":"system.adapter.javascript.0","q":0,"ack":true}): RequestTimedOutError: Request timed out / "Request timed out"" influxdb.0 2024-01-26 22:40:08.644 warn Point could not be written to database: iobroker influxdb.0 2024-01-26 22:40:07.618 warn Error on writePoint("{"value":758,"time":"2024-01-26T21:39:37.610Z","from":"system.adapter.javascript.0","q":0,"ack":true}): RequestTimedOutError: Request timed out / "Request timed out"" influxdb.0 2024-01-26 22:40:07.618 warn Point could not be written to database: iobroker influxdb.0 2024-01-26 22:40:07.611 warn Error on writePoint("{"value":-758,"time":"2024-01-26T21:39:37.603Z","from":"system.adapter.javascript.0","q":0,"ack":true}): RequestTimedOutError: Request timed out / "Request timed out"" influxdb.0 2024-01-26 22:40:07.611 warn Point could not be written to database: iobroker influxdb.0 2024-01-26 22:40:07.441 warn Error on writePoint("{"value":757,"time":"2024-01-26T21:39:07.427Z","from":"system.adapter.javascript.0","q":0,"ack":true}): RequestTimedOutError: Request timed out / "Request timed out"" influxdb.0 2024-01-26 22:40:07.439 warn Point could not be written to database: iobroker influxdb.0 2024-01-26 22:40:07.368 warn Error on writePoint("{"value":6.002,"time":"2024-01-26T21:39:07.353Z","from":"system.adapter.javascript.0","q":0,"ack":true}): RequestTimedOutError: Request timed out / "Request timed out"" influxdb.0 2024-01-26 22:40:07.367 warn Point could not be written to database: iobroker influxdb.0 2024-01-26 22:40:06.402 warn Error on writePoint("{"value":754,"time":"2024-01-26T21:39:36.394Z","from":"system.adapter.javascript.0","q":0,"ack":true}): RequestTimedOutError: Request timed out / "Request timed out"" influxdb.0 2024-01-26 22:40:06.401 warn Point could not be written to database: iobroker influxdb.0 2024-01-26 22:40:06.397 warn Error on writePoint("{"value":-754,"time":"2024-01-26T21:39:36.389Z","from":"system.adapter.javascript.0","q":0,"ack":true}): RequestTimedOutError: Request timed out / "Request timed out"" influxdb.0 2024-01-26 22:40:06.396 warn Point could not be written to database: iobroker influxdb.0 2024-01-26 22:40:06.338 warn Error on writePoint("{"value":6.008,"time":"2024-01-26T21:39:36.329Z","from":"system.adapter.javascript.0","q":0,"ack":true}): RequestTimedOutError: Request timed out / "Request timed out"" influxdb.0 2024-01-26 22:40:06.337 warn Point could not be written to database: iobroker influxdb.0 2024-01-26 22:40:06.266 warn Error on writePoint("{"value":-752,"time":"2024-01-26T21:39:06.250Z","from":"system.adapter.javascript.0","q":0,"ack":true}): RequestTimedOutError: Request timed out / "Request timed out"" influxdb.0 2024-01-26 22:40:06.263 warn Point could not be written to database: iobroker influxdb.0 2024-01-26 22:40:05.221 warn Error on writePoint("{"value":753,"time":"2024-01-26T21:39:35.213Z","from":"system.adapter.javascript.0","q":0,"ack":true}): RequestTimedOutError: Request timed out / "Request timed out"" influxdb.0 2024-01-26 22:40:05.221 warn Point could not be written to database: iobroker influxdb.0 2024-01-26 22:40:05.216 warn Error on writePoint("{"value":-753,"time":"2024-01-26T21:39:35.208Z","from":"system.adapter.javascript.0","q":0,"ack":true}): RequestTimedOutError: Request timed out / "Request timed out"" -
@cainam sagte in ioBroker sehr träg und langsam:
Error: getaddrinfo EAI_AGAIN api.telegram.org
2024-01-26 22:44:02.892 warn script.js.Informationen.Influx_offline: telegram: InfluxDB hat einen Fehler und ist OFFLINE!!!!!
influxdb.1
2024-01-26 22:41:01.250 error RequestTimedOutError: Request timed out
influxdb.0
2024-01-26 22:40:37.533 error RequestTimedOutError: Request timed outeher ein Netzwerkproblem
-
Zeige mal :
@thomas-braun sagte in ioBroker sehr träg und langsam:
Bitte die Langfassung von
iob diag -
-
@cainam sagte in ioBroker sehr träg und langsam:
VM über Proxmox
Hast du kein Backup ( backitup ) , da es eh eine VM ist .
Neue VM .. ioBroker aufsetzen , Backup rein ! -
@glasfaser
doch backup habe ich schon.. .aber wenn ich das 1:1 zurückspiele bin ich ja gleich weit -
@cainam sagte in ioBroker sehr träg und langsam:
1:1 zurückspiele bin ich ja gleich weit
???
ich meine kein VM Snapshot , ein richtiges Backup mit dem Backitup Adapter. -
erm.. ja doch nur dummerweise habe ich heute viele neue javascripts gemacht....
hier noch das diag, sieht man da etwas?
======== Start marking the full check here =========
Skript v.2023-10-10 *** BASE SYSTEM *** Static hostname: ioBroker Icon name: computer-vm Chassis: vm Virtualization: kvm Operating System: Debian GNU/Linux 10 (buster) Kernel: Linux 4.19.0-26-amd64 Architecture: x86-64 model name : Common KVM processor Docker : false Virtualization : kvm Kernel : x86_64 Userland : amd64 Systemuptime and Load: 23:10:52 up 3 min, 1 user, load average: 3.75, 1.17, 0.41 CPU threads: 4 *** Time and Time Zones *** Local time: Fri 2024-01-26 23:10:53 CET Universal time: Fri 2024-01-26 22:10:53 UTC RTC time: Fri 2024-01-26 22:10:54 Time zone: Europe/Zurich (CET, +0100) System clock synchronized: yes NTP service: active RTC in local TZ: no *** User and Groups *** rapha /home/rapha rapha adm cdrom floppy sudo audio dip video plugdev netdev iobroker *** X-Server-Setup *** X-Server: false Desktop: Terminal: tty Boot Target: graphical.target *** MEMORY *** total used free shared buff/cache available Mem: 5.8G 2.2G 3.3G 7.0M 317M 3.4G Swap: 0B 0B 0B Total: 5.8G 2.2G 3.3G 5820 M total memory 2183 M used memory 2179 M active memory 159 M inactive memory 3319 M free memory 51 M buffer memory 265 M swap cache 0 M total swap 0 M used swap 0 M free swap *** FAILED SERVICES *** 0 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 2.9G 0 2.9G 0% /dev tmpfs tmpfs 583M 7.7M 575M 2% /run /dev/sda1 ext4 14G 9.7G 3.3G 75% / tmpfs tmpfs 2.9G 0 2.9G 0% /dev/shm tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs tmpfs 2.9G 0 2.9G 0% /sys/fs/cgroup tmpfs tmpfs 583M 0 583M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Fri Jan 26 23:07:45 2024] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [Fri Jan 26 23:07:46 2024] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro Show mounted filesystems \(real ones only\): TARGET SOURCE FSTYPE OPTIONS / /dev/sda1 ext4 rw,relatime,errors=remount-ro `-/sys/fs/bpf bpf bpf rw,nosuid,nodev,noexec,relatime,mode=700 Files in neuralgic directories: /var: 321M /var/ 157M /var/lib 142M /var/cache 135M /var/cache/apt 125M /var/lib/apt/lists Archived and active journals take up 7.2M in the file system. /opt/iobroker/backups: 2.5G /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 912M /opt/iobroker/iobroker-data/ 563M /opt/iobroker/iobroker-data/files 198M /opt/iobroker/iobroker-data/backup-objects 72M /opt/iobroker/iobroker-data/files/telegram.admin 67M /opt/iobroker/iobroker-data/files/javascript.admin The five largest files in iobroker-data are: 35M /opt/iobroker/iobroker-data/files/devices.admin/static/js/main.24f2bb56.js.map 25M /opt/iobroker/iobroker-data/states.jsonl 24M /opt/iobroker/iobroker-data/objects.jsonl 22M /opt/iobroker/iobroker-data/files/modbus.admin/static/js/main.b5f6766c.js.map 21M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.edf7552a.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.17.1 /usr/bin/node v18.17.1 /usr/bin/npm 9.6.7 /usr/bin/npx 9.6.7 /usr/bin/corepack 0.18.0 nodejs: Installed: 18.17.1-deb-1nodesource1 Candidate: 18.17.1-deb-1nodesource1 Version table: *** 18.17.1-deb-1nodesource1 500 500 https://deb.nodesource.com/node_18.x buster/main amd64 Packages 100 /var/lib/dpkg/status 10.24.0~dfsg-1~deb10u3 500 500 http://security.debian.org/debian-security buster/updates/main amd64 Packages 10.24.0~dfsg-1~deb10u1 500 500 http://deb.debian.org/debian buster/main amd64 Packages 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.17 admin: 6.12.0 javascript: 7.1.6 Adapters from github: 1 Adapter State + system.adapter.admin.0 : admin : ioBroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.backitup.0 : backitup : ioBroker - enabled system.adapter.chromecast.0 : chromecast : ioBroker - disabled system.adapter.cloud.0 : cloud : ioBroker - disabled + system.adapter.deconz.0 : deconz : ioBroker - enabled, port: 80 system.adapter.devices.0 : devices : ioBroker - disabled system.adapter.discovery.0 : discovery : ioBroker - disabled system.adapter.ds18b20.0 : ds18b20 : ioBroker - disabled + system.adapter.echarts.0 : echarts : ioBroker - enabled system.adapter.email.0 : email : ioBroker - disabled system.adapter.epson_stylus_px830.0 : epson_stylus_px830 : ioBroker - disabled system.adapter.flot.0 : flot : ioBroker - disabled + system.adapter.followthesun.0 : followthesun : ioBroker - enabled system.adapter.habpanel.0 : habpanel : ioBroker - disabled + system.adapter.history.0 : history : ioBroker - enabled + system.adapter.influxdb.0 : influxdb : ioBroker - enabled, port: 8086 + system.adapter.influxdb.1 : influxdb : ioBroker - enabled, port: 8086 system.adapter.info.0 : info : ioBroker - disabled system.adapter.iot.0 : iot : ioBroker - disabled system.adapter.iqontrol.0 : iqontrol : ioBroker - disabled + system.adapter.javascript.0 : javascript : ioBroker - enabled + system.adapter.lgtv11.0 : lgtv11 : ioBroker - enabled, port: 8080 system.adapter.lovelace.0 : lovelace : ioBroker - disabled, port: 8091, bind: 0.0.0.0, run as: admin system.adapter.meteoalarm.0 : meteoalarm : ioBroker - disabled system.adapter.mielecloudservice.0 : mielecloudservice : ioBroker - disabled + system.adapter.modbus.0 : modbus : ioBroker - enabled system.adapter.mqtt-client.0 : mqtt-client : ioBroker - disabled, port: 1883 + system.adapter.mqtt.0 : mqtt : ioBroker - enabled, port: 1884, bind: 0.0.0.0 system.adapter.onvif.0 : onvif : ioBroker - disabled, port: 2020, 80, 7575, 8000, 8080, 8081, 8899 system.adapter.openweathermap.0 : openweathermap : ioBroker - disabled system.adapter.ping.0 : ping : ioBroker - disabled system.adapter.proxmox.0 : proxmox : ioBroker - disabled, port: 8006 system.adapter.pvforecast.0 : pvforecast : ioBroker - disabled system.adapter.radar2.0 : radar2 : ioBroker - disabled system.adapter.roomba.0 : roomba : ioBroker - disabled system.adapter.sayit.0 : sayit : ioBroker - disabled, port: 0 system.adapter.scenes.0 : scenes : ioBroker - disabled + system.adapter.shelly.0 : shelly : ioBroker - enabled, port: 1882, bind: 0.0.0.0 system.adapter.shuttercontrol.0 : shuttercontrol : ioBroker - disabled system.adapter.simple-api.0 : simple-api : ioBroker - disabled, port: 8087, bind: 0.0.0.0, run as: admin system.adapter.snmp.0 : snmp : ioBroker - disabled system.adapter.sonoff.0 : sonoff : ioBroker - disabled, port: 1883, bind: 0.0.0.0 system.adapter.sonos.0 : sonos : ioBroker - disabled + system.adapter.sourceanalytix.0 : sourceanalytix : ioBroker - enabled system.adapter.spotify-premium.0 : spotify-premium : ioBroker - disabled + system.adapter.statistics.0 : statistics : ioBroker - enabled system.adapter.swiss-weather-api.0 : swiss-weather-api : ioBroker - disabled system.adapter.synology.0 : synology : ioBroker - disabled, port: 5001 system.adapter.tapo.0 : tapo : ioBroker - disabled + system.adapter.telegram.0 : telegram : ioBroker - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.text2command.0 : text2command : ioBroker - enabled + system.adapter.tuya.0 : tuya : ioBroker - enabled system.adapter.upnp.0 : upnp : ioBroker - disabled system.adapter.vis-bars.0 : vis-bars : ioBroker - disabled system.adapter.vis-history.0 : vis-history : ioBroker - disabled system.adapter.vis-hqwidgets.0 : vis-hqwidgets : ioBroker - disabled system.adapter.vis-jqui-mfd.0 : vis-jqui-mfd : ioBroker - enabled system.adapter.vis-material-webfont.0 : vis-material-webfont : ioBroker - disabled system.adapter.vis-material.0 : vis-material : ioBroker - disabled system.adapter.vis-materialdesign.0 : vis-materialdesign : ioBroker - disabled system.adapter.vis-timeandweather.0 : vis-timeandweather : ioBroker - disabled system.adapter.vis-weather.0 : vis-weather : ioBroker - disabled system.adapter.vis.0 : vis : ioBroker - disabled + system.adapter.web.0 : web : ioBroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin system.adapter.whatsapp-cmb.0 : whatsapp-cmb : ioBroker - disabled system.adapter.wifilight.0 : wifilight : ioBroker - disabled + system.adapter.worx.0 : worx : ioBroker - enabled + system.adapter.yahka.0 : yahka : ioBroker - enabled system.adapter.zigbee.0 : zigbee : ioBroker - disabled, port: 80 + 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.deconz.0 : deconz : ioBroker - enabled, port: 80 + system.adapter.influxdb.0 : influxdb : ioBroker - enabled, port: 8086 + system.adapter.influxdb.1 : influxdb : ioBroker - enabled, port: 8086 + system.adapter.lgtv11.0 : lgtv11 : ioBroker - enabled, port: 8080 + system.adapter.mqtt.0 : mqtt : ioBroker - enabled, port: 1884, bind: 0.0.0.0 + system.adapter.shelly.0 : shelly : ioBroker - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.telegram.0 : telegram : ioBroker - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.web.0 : web : ioBroker - enabled, port: 8082, 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.12.0 , installed 6.12.0 Adapter "alexa2" : 3.26.3 , installed 3.26.3 Adapter "backitup" : 2.9.8 , installed 2.9.8 Adapter "bring" : 1.8.4 , installed 1.8.1 [Updatable] Adapter "broadlink2" : 2.1.5 , installed 2.1.5 Adapter "chromecast" : 3.0.3 , installed 3.0.3 Adapter "cloud" : 4.4.1 , installed 4.4.1 Adapter "daswetter" : 3.1.12 , installed 3.1.10 [Updatable] Adapter "deconz" : 1.3.23 , installed 1.3.21 [Updatable] Adapter "devices" : 1.1.5 , installed 1.1.5 Adapter "discovery" : 4.2.0 , installed 3.1.0 [Updatable] Adapter "ds18b20" : 2.0.5 , installed 1.6.1 [Updatable] Adapter "echarts" : 1.7.2 , installed 1.5.1 [Updatable] Adapter "email" : 1.2.2 , installed 1.2.0 [Updatable] Adapter "epson_stylus_px830": 0.2.1, installed 0.2.1 Adapter "flot" : 1.12.0 , installed 1.12.0 Adapter "followthesun" : 0.5.0 , installed 0.5.0 Adapter "habpanel" : 0.5.0 , installed 0.5.0 Adapter "ham" : 5.3.1 , installed 5.3.1 Adapter "heizoel" : 1.0.3 , installed 1.0.3 Adapter "history" : 3.0.1 , installed 2.2.6 [Updatable] Adapter "homekit-controller": 0.5.9, installed 0.5.9 Adapter "influxdb" : 3.2.0 , installed 3.2.0 Adapter "info" : 2.0.0 , installed 2.0.0 Adapter "iot" : 2.0.11 , installed 1.14.5 [Updatable] Adapter "iqontrol" : 2.3.0 , installed 2.3.0 Adapter "javascript" : 7.1.6 , installed 7.1.6 Controller "js-controller": 5.0.17 , installed 5.0.17 Adapter "lgtv" : 2.1.2 , installed 2.1.2 Adapter "lgtv-rs" : 0.1.1 , installed 0.1.1 Adapter "lgtv11" : 1.0.5 , installed 1.0.5 Adapter "linkeddevices": 1.5.5 , installed 1.5.5 Adapter "lovelace" : 3.0.1 , installed 3.0.1 Adapter "meteoalarm" : 2.3.7 , installed 2.3.7 Adapter "miele" : 0.1.5 , installed 0.1.5 Adapter "mielecloudservice": 6.5.4, installed 6.5.4 Adapter "modbus" : 6.0.1 , installed 6.0.1 Adapter "mqtt" : 5.1.0 , installed 5.1.0 Adapter "mqtt-client" : 1.7.0 , installed 1.6.5 [Updatable] Adapter "onvif" : 1.1.1 , installed 1.1.1 Adapter "openweathermap": 1.0.4 , installed 1.0.4 Adapter "paw" : 0.3.2 , installed 0.3.2 Adapter "ping" : 1.6.2 , installed 1.6.2 Adapter "proxmox" : 2.2.2 , installed 2.2.1 [Updatable] Adapter "pushover" : 3.0.6 , installed 3.0.3 [Updatable] Adapter "pvforecast" : 2.9.1 , installed 2.9.1 Adapter "radar2" : 2.1.0 , installed 2.0.7 [Updatable] Adapter "roomba" : 1.2.2 , installed 1.2.2 Adapter "rpi2" : 1.3.2 , installed 1.3.2 Adapter "sayit" : 3.0.5 , installed 3.0.5 Adapter "scenes" : 2.3.9 , installed 2.3.9 Adapter "shelly" : 6.6.1 , installed 6.6.1 Adapter "shuttercontrol": 1.6.3 , installed 1.6.2 [Updatable] Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "snmp" : 3.1.0 , installed 2.4.11 [Updatable] Adapter "socketio" : 6.6.0 , installed 6.5.5 [Updatable] Adapter "sonoff" : 3.0.3 , installed 3.0.3 Adapter "sonos" : 3.0.0 , installed 3.0.0 Adapter "sony-bravia" : 1.0.9 , installed 1.0.9 Adapter "spotify-premium": 1.3.1 , installed 1.2.2 [Updatable] Adapter "statistics" : 2.4.0 , installed 2.3.0 [Updatable] Adapter "swiss-weather-api": 2.0.3, installed 2.0.3 Adapter "synology" : 3.0.1 , installed 3.0.0 [Updatable] Adapter "tapo" : 0.0.8 , installed 0.0.8 Adapter "telegram" : 3.0.1 , installed 1.16.0 [Updatable] Adapter "text2command" : 3.0.2 , installed 3.0.2 Adapter "tuya" : 3.15.0 , installed 3.15.0 Adapter "upnp" : 1.0.21 , installed 1.0.21 Adapter "vis" : 1.5.4 , installed 1.4.16 [Updatable] Adapter "vis-bars" : 0.1.4 , installed 0.1.4 Adapter "vis-history" : 1.0.0 , installed 1.0.0 Adapter "vis-hqwidgets": 1.4.0 , installed 1.4.0 Adapter "vis-jqui-mfd" : 1.0.12 , installed 1.0.12 Adapter "vis-material" : 0.1.3 , installed 0.1.3 Adapter "vis-materialdesign": 0.5.9, installed 0.3.19 [Updatable] Adapter "vis-timeandweather": 1.2.2, installed 1.2.2 Adapter "vis-weather" : 2.5.6 , installed 2.5.6 Adapter "web" : 6.1.10 , installed 6.1.2 [Updatable] Adapter "whatsapp-cmb" : 0.2.3 , installed 0.2.3 Adapter "wifilight" : 1.1.4 , installed 1.1.4 Adapter "worx" : 2.3.4 , installed 2.3.4 Adapter "ws" : 2.5.8 , installed 2.5.5 [Updatable] Adapter "yahka" : 1.0.3 , installed 1.0.3 Adapter "zigbee" : 1.10.1 , installed 1.10.1 Objects and States Please stand by - This may take a while Objects: 19522 States: 12892 *** OS-Repositories and Updates *** Hit:1 http://deb.debian.org/debian buster InRelease Hit:2 http://security.debian.org/debian-security buster/updates InRelease Hit:3 http://deb.debian.org/debian buster-updates InRelease Get:4 https://deb.nodesource.com/node_18.x buster InRelease [4584 B] Fetched 4584 B in 1s (3366 B/s) 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 0.0.0.0:111 0.0.0.0:* LISTEN 0 9975 1/init tcp 0 0 127.0.0.1:37489 0.0.0.0:* LISTEN 1001 16740 779/io.yahka.0 tcp 0 0 0.0.0.0:35857 0.0.0.0:* LISTEN 1001 15356 779/io.yahka.0 tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 14353 486/sshd tcp 0 0 0.0.0.0:1884 0.0.0.0:* LISTEN 1001 15490 616/io.mqtt.0 tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 14031 478/iobroker.js-con tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 14384 478/iobroker.js-con tcp6 0 0 :::111 :::* LISTEN 0 10621 1/init tcp6 0 0 :::8081 :::* LISTEN 1001 14126 507/io.admin.0 tcp6 0 0 :::8082 :::* LISTEN 1001 15970 751/io.web.0 tcp6 0 0 :::22 :::* LISTEN 0 14364 486/sshd udp 0 0 0.0.0.0:1900 0.0.0.0:* 1001 15170 696/io.deconz.0 udp 0 0 0.0.0.0:6666 0.0.0.0:* 1001 15661 637/io.tuya.0 udp 0 0 0.0.0.0:6667 0.0.0.0:* 1001 15662 637/io.tuya.0 udp 0 0 0.0.0.0:111 0.0.0.0:* 0 9976 1/init udp 0 0 0.0.0.0:5353 0.0.0.0:* 1001 15353 779/io.yahka.0 udp 0 0 0.0.0.0:5683 0.0.0.0:* 1001 15399 597/io.shelly.0 udp6 0 0 :::1900 :::* 1001 15172 696/io.deconz.0 udp6 0 0 :::1900 :::* 1001 15171 696/io.deconz.0 udp6 0 0 :::111 :::* 0 10626 1/init *** Log File - Last 25 Lines *** 2024-01-26 23:10:57.540 - warn: tuya.0 (637) bf0a6cadad47907ceb6ddu: Error on Reconnect (3): connect EHOSTUNREACH 192.168.0.55:6668 2024-01-26 23:11:00.556 - info: statistics.0 (842) starting. Version 2.3.0 in /opt/iobroker/node_modules/iobroker.statistics, node: v18.17.1, js-controller: 5.0.17 2024-01-26 23:11:00.954 - info: statistics.0 (842) [SETUP] enabled statistics for 0_userdata.0.Water.Wasser_pro_Verbrauch 2024-01-26 23:11:02.594 - warn: worx.0 (829) INFORMATION - Change common: worx.0.2021302671010083888B.mower.batteryState 2024-01-26 23:11:02.914 - info: worx.0 (829) Multi-ZoneKeeper found! Create State : zoneKeeper 2024-01-26 23:11:02.914 - info: lgtv11.0 (853) starting. Version 1.0.5 in /opt/iobroker/node_modules/iobroker.lgtv11, node: v18.17.1, js-controller: 5.0.17 2024-01-26 23:11:02.993 - warn: worx.0 (829) INFORMATION - Change common: worx.0.2021302671010083888B.mower.totalBladeTime 2024-01-26 23:11:03.013 - info: lgtv11.0 (853) Ready. Configured LG TV IP: 192.168.0.107, Port: 8080, Pairing Key: 938887 2024-01-26 23:11:03.136 - warn: worx.0 (829) INFORMATION - Change common: worx.0.2021302671010083888B.mower.totalDistance 2024-01-26 23:11:03.229 - warn: worx.0 (829) INFORMATION - Change common: worx.0.2021302671010083888B.mower.totalTime 2024-01-26 23:11:04.084 - info: worx.0 (829) DoubleShedule found, create states... 2024-01-26 23:11:05.018 - info: worx.0 (829) OneTimeShedule found, create states... 2024-01-26 23:11:05.453 - info: worx.0 (829) Firmware found, create states... 2024-01-26 23:11:06.208 - info: worx.0 (829) Create product folder and states for WR167E 2024-01-26 23:11:12.282 - info: worx.0 (829) Torque control found, create states... 2024-01-26 23:11:12.515 - info: worx.0 (829) ACS Module found! Create State : US 2024-01-26 23:11:12.580 - info: worx.0 (829) ACS Module found! Create State : US.ACS 2024-01-26 23:11:12.609 - info: worx.0 (829) ACS Module found! Create State : US.ACS_Status 2024-01-26 23:11:12.698 - info: statistics.0 (842) [SETUP] observing 1 values after startup 2024-01-26 23:11:12.977 - info: worx.0 (829) Autolock found! Create State : AutoLock 2024-01-26 23:11:13.004 - info: worx.0 (829) Autolock found! Create State : AutoLockTimer 2024-01-26 23:11:13.730 - info: worx.0 (829) Start MQTT connection 2024-01-26 23:11:14.919 - info: worx.0 (829) Request Counter: 1 2024-01-26 23:11:40.606 - warn: tuya.0 (637) bf0a6cadad47907ceb6ddu: Error on Reconnect (5): connect EHOSTUNREACH 192.168.0.55:6668 2024-01-26 23:12:43.679 - warn: tuya.0 (637) bf0a6cadad47907ceb6ddu: Error on Reconnect (7): connect EHOSTUNREACH 192.168.0.55:6668============ Mark until here for C&P =============
-
@cainam sagte in ioBroker sehr träg und langsam:
Operating System: Debian GNU/Linux 10 (buster)
Als VM ( auch sonst ) ... schon Steinzeit / Antik
/usr/bin/nodejs v18.17.1
/usr/bin/node v18.17.1
/usr/bin/npm 9.6.7
/usr/bin/npx 9.6.7
/usr/bin/corepack 0.18.0nicht aktuell
-
@glasfaser
ja habe mich davor gescheut alles upzudaten da es bisher problemlos lief... nach dem motto "never change a winning horse..."würdest du buster updaten und die nodes etc.. (wie mache ich das mit iob update)?
-
@cainam sagte in ioBroker sehr träg und langsam:
nach dem motto "never change a winning horse..."
Falsches vorgehen !!!
würdest du buster updaten ...
Nein !
Neue VM mit Bookworm aufsetzen , Backup rein ... Fertig !
-
das tönt so simple... aber ich kenne das, da bin ich die halbe nacht dran bis das dann alles wieder läuft... update ist nicht gut? besser neue VM mit bookworm und das Backup (backitup) zurückspielen? (was muss alles in backitup gesichert werden damit es 1:1 wieder läuft wie bisher...
