Teilweise über 200% CPU Auslastung im Docker
-
-
-
Schaue einmal in den Container mit top, welche Prozesse da mit Volllast laufen.
-
@djmarc75 sagte in Teilweise über 200% CPU Auslastung im Docker:
@dr-pie Sind da Skripte im Amokmodus ?
Zeige bitte
iob diagDas ist eine gute Frage. iob diag läuft schon
@codierknecht sagte in Teilweise über 200% CPU Auslastung im Docker:
@dr-pie
Zusätzlich zu dem was @DJMarc75 schreibt:
Was ist das für eine Synology?
Wie ist die ausgestattet? Was läuft da sonst noch?Hier die Daten:
DSM 7.2.1-69057 Update 3
DS1019+
INTEL Celeron J3455
1.5 GHz@oliverio sagte in Teilweise über 200% CPU Auslastung im Docker:
Schaue einmal in den Container mit top, welche Prozesse da mit Volllast laufen.
Wie komme ich dort hin ?
-
Auf den iob komme ich nicht mehr.
Nur in den Editor und auf die Vis. -
@dr-pie sagte in Teilweise über 200% CPU Auslastung im Docker:
iob diag läuft schon
und die Ausgabe in Codetags wäre interessant zu sehen
-
@djmarc75 ```
Copy text starting here:======================= SUMMARY ======================= v.2023-10-10 model name : Intel(R) Celeron(R) CPU J3455 @ 1.50GHz Kernel : x86_64 Userland : amd64 Docker : v8.0.1 Installation: Docker Kernel: x86_64 Userland: amd64 Timezone: Etc/UTC User-ID: 0 X-Server: false Pending OS-Updates: 28 /opt/iobroker/node_modules/standard-as-callback/built/index.js:6 throw e; ^ Error: Connection is 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:629:26) at Socket.emit (node:events:514:28) at TCP.<anonymous> (node:net:323:12) Emitted 'error' event on ScanStream instance at: at /opt/iobroker/node_modules/ioredis/built/ScanStream.js:38:22 at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:12:23) at /opt/iobroker/node_modules/standard-as-callback/built/index.js:33:51 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) Node.js v18.17.1 Pending iob updates: 0 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 Recommended versions are nodejs 18.19.1 and npm 10.2.4 Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 7.8G 5.4G 539M 119M 1.9G 2.0G Swap: 6.7G 34M 6.7G Total: 14G 5.4G 7.2G Uncaught Rejection: Error: Objects DB is not allowed to start in the current Multihost environment at Redis.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-objects-redis/build/lib/objects/objectsInRedisClient.js:493:23) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) Active iob-Instances: 0 Uncaught Rejection: Error: Objects DB is not allowed to start in the current Multihost environment at Redis.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-objects-redis/build/lib/objects/objectsInRedisClient.js:493:23) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) Unable to subscribe to meta namespace "meta." changes: Connection is closed. ioBroker Core: js-controller 5.0.17 admin 6.13.16 Uncaught Rejection: Error: Objects DB is not allowed to start in the current Multihost environment at Redis.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-objects-redis/build/lib/objects/objectsInRedisClient.js:493:23) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) ioBroker Status: Connection is closed. Unable to subscribe to evicted Keyspace events from Redis Server: Connection is closed. Unable to subscribe to meta namespace "meta." changes: Connection is closed. Status admin and web instance: Uncaught Rejection: Error: Objects DB is not allowed to start in the current Multihost environment at Redis.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-objects-redis/build/lib/objects/objectsInRedisClient.js:493:23) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) Objects: 0 States: 0 Size of iob-Database: 26M /opt/iobroker/iobroker-data/objects.jsonl 4.5M /opt/iobroker/iobroker-data/states.jsonl =================== END OF SUMMARY ====================Die lange Version ginge natürlich auch ... hab ich aber verpasst
-
@dr-pie sagte in Teilweise über 200% CPU Auslastung im Docker:
Die lange Version ginge natürlich auch
und die wäre schön zu sehen
Mach halt nochmal - und am Ende keine Taste drücken
-
@dr-pie
Du kannst top auch auf der console aufrufen.
Also dort wo du auch iob diag eingegeben hast -
@oliverio sagte in Teilweise über 200% CPU Auslastung im Docker:
@dr-pie
Du kannst top auch auf der console aufrufen.
Also dort wo du auch iob diag eingegeben hasttop - 15:47:27 up 20:46, 0 users, load average: 2,47, 2,94, 2,96 Tasks: 25 total, 2 running, 23 sleeping, 0 stopped, 0 zombie %Cpu(s): 51,3 us, 5,0 sy, 0,0 ni, 42,9 id, 0,0 wa, 0,0 hi, 0,8 si, 0,0 st MiB Mem : 7802,0 total, 408,3 free, 5502,6 used, 1891,1 buff/cache MiB Swap: 6731,9 total, 6697,0 free, 34,9 used. 1883,2 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 174 iobroker 20 0 11,6g 804244 46096 R 96,3 10,1 1261:46 iobroker.js-con 679 iobroker 20 0 1944184 1,1g 40092 S 94,0 14,8 717:46.89 io.device-watch 450 iobroker 20 0 1718048 887868 39948 S 9,3 11,1 156:07.51 io.shelly.1 366 iobroker 20 0 1002892 147496 39836 S 8,0 1,8 52:05.24 io.shelly.0 224 iobroker 20 0 1184844 346172 45832 S 3,7 4,3 53:28.79 io.javascript.0 262 iobroker 20 0 967956 113200 39712 S 1,7 1,4 21:30.92 io.influxdb.0 196 iobroker 20 0 1089088 215252 46868 S 0,7 2,7 10:16.87 iobroker.js-con 29287 iobroker 20 0 948668 85048 45784 S 0,7 1,1 0:05.22 io.fullybrowser 243 iobroker 20 0 991452 104484 38776 S 0,3 1,3 4:07.28 io.sql.0 492 iobroker 20 0 20,9g 104416 46372 S 0,3 1,3 0:37.12 io.backitup.0 565 iobroker 20 0 955132 89356 39968 S 0,3 1,1 2:52.76 io.denon.0 610 iobroker 20 0 10,9g 108868 39816 S 0,3 1,4 6:46.13 io.heos.0 668 iobroker 20 0 10,9g 122508 40756 S 0,3 1,5 9:36.75 io.fb-checkpres 1 root 20 0 7364 3120 3120 S 0,0 0,0 0:00.04 bash 381 iobroker 20 0 10,9g 103092 40088 S 0,0 1,3 1:24.17 io.synology.1 392 iobroker 20 0 10,9g 102880 40320 S 0,0 1,3 1:26.84 io.synology.2 407 iobroker 20 0 831736 103904 45672 S 0,0 1,3 7:35.23 io.tr-064.0 435 iobroker 20 0 832248 106664 45752 S 0,0 1,3 19:54.27 io.tr-064.1 465 iobroker 20 0 821636 82804 39872 S 0,0 1,0 0:34.42 io.discovery.0 507 iobroker 20 0 1024264 164200 40988 S 0,0 2,1 8:10.61 io.web.0 595 iobroker 20 0 960016 84900 39880 S 0,0 1,1 0:51.34 io.harmony.0 634 iobroker 20 0 1088292 235916 40952 S 0,0 3,0 1:17.81 io.tankerkoenig 653 iobroker 20 0 971976 116388 45876 S 0,0 1,5 1:43.31 io.wled.0 32314 root 20 0 7496 3840 3408 S 0,0 0,0 0:00.00 bash 32329 root 20 0 10296 3584 3112 R 0,0 0,0 0:00.03 top -
@djmarc75 sagte in Teilweise über 200% CPU Auslastung im Docker:
@dr-pie sagte in Teilweise über 200% CPU Auslastung im Docker:
Die lange Version ginge natürlich auch
und die wäre schön zu sehen
Mach halt nochmal - und am Ende keine Taste drücken
Skript v.2023-10-10 *** BASE SYSTEM *** Hardware Vendor : Synology Kernel : x86_64 Userland : amd64 Docker : v8.0.1 Virtualization : Docker Kernel : x86_64 Userland : amd64 Systemuptime and Load: 15:50:36 up 20:49, 0 users, load average: 3.28, 3.01, 2.98 CPU threads: 4 *** Time and Time Zones *** Thu Feb 22 14:50:36 UTC 2024 Thu Feb 22 15:50:36 CET 2024 CET +0100 Etc/UTC *** User and Groups *** root /root root *** X-Server-Setup *** X-Server: false Desktop: Terminal: *** MEMORY *** total used free shared buff/cache available Mem: 7.8G 5.3G 590M 120M 1.9G 2.1G Swap: 6.7G 34M 6.7G Total: 14G 5.4G 7.3G 7802 M total memory 5319 M used memory 4777 M active memory 1528 M inactive memory 590 M free memory 38 M buffer memory 1854 M swap cache 6731 M total swap 34 M used swap 6697 M free swap *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/cachedev_4 btrfs 3.5T 2.0T 1.6T 56% / tmpfs tmpfs 64M 0 64M 0% /dev tmpfs tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup shm tmpfs 64M 0 64M 0% /dev/shm /dev/mapper/cachedev_4 btrfs 3.5T 2.0T 1.6T 56% /opt/iobroker /dev/mapper/cachedev_4 btrfs 3.5T 2.0T 1.6T 56% /etc/hosts tmpfs tmpfs 3.9G 0 3.9G 0% /proc/acpi tmpfs tmpfs 3.9G 0 3.9G 0% /proc/scsi tmpfs tmpfs 3.9G 0 3.9G 0% /sys/firmware Messages concerning ext4 filesystem in dmesg: sudo: unable to resolve host iobroker: Name or service not known [Wed Feb 21 19:01:19 2024] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [Wed Feb 21 19:01:19 2024] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [Wed Feb 21 19:01:19 2024] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [Wed Feb 21 19:01:19 2024] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: barrier=1 [Wed Feb 21 19:01:25 2024] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [Wed Feb 21 19:01:25 2024] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [Wed Feb 21 19:01:25 2024] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [Wed Feb 21 19:01:25 2024] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: barrier=1 Show mounted filesystems \(real ones only\): TARGET SOURCE FSTYPE OPTIONS / /dev/mapper/cachedev_4[/@syno/@docker/btrfs/subvolumes/2082bc39f93f33f788e3c7fa290317a1b738ac8cf85a4217a83d22a38aceec36] btrfs rw,nodev,relatime,relatime_period=30,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,syno_allocator,subvolid=724572,subvol=/@syno/@docker/btrfs/subvolumes/2082bc39f93f33f788e3c7fa290317a1b738ac8cf85a4217a83d22a38aceec36 |-/opt/iobroker /dev/mapper/cachedev_4[/@syno/docker/iobroker] btrfs rw,nodev,relatime,relatime_period=30,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,syno_allocator,subvolid=724400,subvol=/@syno/docker |-/etc/resolv.conf /dev/mapper/cachedev_4[/@syno/@docker/containers/0450185fc3ce5afab5101aa2eabbba0a1f80981592975fc06d13c4fc7271dbd6/resolv.conf] btrfs rw,nodev,relatime,relatime_period=30,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,syno_allocator,subvolid=257,subvol=/@syno |-/etc/hostname /dev/mapper/cachedev_4[/@syno/@docker/containers/0450185fc3ce5afab5101aa2eabbba0a1f80981592975fc06d13c4fc7271dbd6/hostname] btrfs rw,nodev,relatime,relatime_period=30,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,syno_allocator,subvolid=257,subvol=/@syno `-/etc/hosts /dev/mapper/cachedev_4[/@syno/@docker/containers/0450185fc3ce5afab5101aa2eabbba0a1f80981592975fc06d13c4fc7271dbd6/hosts] btrfs rw,nodev,relatime,relatime_period=30,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,syno_allocator,subvolid=257,subvol=/@syno Files in neuralgic directories: /var: sudo: unable to resolve host iobroker: Name or service not known 33M /var/ 31M /var/lib 18M /var/lib/apt/lists 18M /var/lib/apt 13M /var/lib/dpkg /opt/iobroker/backups: 3.2G /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 498M /opt/iobroker/iobroker-data/ 363M /opt/iobroker/iobroker-data/files 137M /opt/iobroker/iobroker-data/files/vis-2 94M /opt/iobroker/iobroker-data/backup-objects 78M /opt/iobroker/iobroker-data/files/vis-2/static The five largest files in iobroker-data are: 26M /opt/iobroker/iobroker-data/objects.jsonl 22M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.c05ba1d3.js.map 18M /opt/iobroker/iobroker-data/files/vis-2/static/js/main.e642d05b.js.map 18M /opt/iobroker/iobroker-data/files/vis-2/static/js/main.2b7aff38.js.map 18M /opt/iobroker/iobroker-data/files/vis-2/customWidgets.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 bullseye/main amd64 Packages 100 /var/lib/dpkg/status 12.22.12~dfsg-1~deb11u4 500 500 http://deb.debian.org/debian bullseye/main amd64 Packages 500 http://deb.debian.org/debian-security bullseye-security/main amd64 Packages Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: *** ioBroker-Installation *** ioBroker Status Cannot determine Lua scripts strategy: Connection is closed. ["cfg.o.system.host.iobroker"] No connection to databases possible ... Core adapters versions js-controller: 5.0.17 admin: 6.13.16 javascript: 7.8.0 Adapters from github: 3 Adapter State Cannot determine Lua scripts strategy: Connection is closed. ["cfg.o.system.host.iobroker"] No connection to databases possible ... Enabled adapters with bindings /opt/iobroker/node_modules/standard-as-callback/built/index.js:6 throw e; ^ Error: Connection is 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:629:26) at Socket.emit (node:events:514:28) at TCP.<anonymous> (node:net:323:12) Emitted 'error' event on ScanStream instance at: at /opt/iobroker/node_modules/ioredis/built/ScanStream.js:38:22 at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:12:23) at /opt/iobroker/node_modules/standard-as-callback/built/index.js:33:51 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) Node.js v18.17.1 ioBroker-Repositories /opt/iobroker/node_modules/standard-as-callback/built/index.js:6 throw e; ^ Error: Connection is 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:629:26) at Socket.emit (node:events:514:28) at TCP.<anonymous> (node:net:323:12) Emitted 'error' event on ScanStream instance at: at /opt/iobroker/node_modules/ioredis/built/ScanStream.js:38:22 at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:12:23) at /opt/iobroker/node_modules/standard-as-callback/built/index.js:33:51 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) Node.js v18.17.1 Installed ioBroker-Instances Cannot determine Lua scripts strategy: Connection is closed. ["cfg.o.system.host.iobroker"] No connection to databases possible ... Objects and States Please stand by - This may take a while Objects: 3 States: 3 *** OS-Repositories and Updates *** sudo: unable to resolve host iobroker: Name or service not known sudo: unable to resolve host iobroker: Name or service not known Hit:1 http://deb.debian.org/debian bullseye InRelease Hit:2 http://deb.debian.org/debian-security bullseye-security InRelease Hit:3 http://deb.debian.org/debian bullseye-updates InRelease Hit:4 https://deb.nodesource.com/node_18.x bullseye InRelease Reading package lists... Pending Updates: 28 *** Listening Ports *** sudo: unable to resolve host iobroker: Name or service not known Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 192.168.178.203:8081 0.0.0.0:* LISTEN 1000 134867 - tcp 0 0 127.0.0.1:32401 0.0.0.0:* LISTEN 297536 82661 - tcp 0 0 192.168.178.203:8082 0.0.0.0:* LISTEN 1000 145247 - tcp 0 0 172.17.0.1:53 0.0.0.0:* LISTEN 115492 103340 - tcp 0 0 172.17.0.1:53 0.0.0.0:* LISTEN 115492 103339 - tcp 0 0 172.17.0.1:53 0.0.0.0:* LISTEN 115492 103338 - tcp 0 0 172.17.0.1:53 0.0.0.0:* LISTEN 115492 103337 - tcp 0 0 169.254.241.18:53 0.0.0.0:* LISTEN 115492 76525 - tcp 0 0 169.254.241.18:53 0.0.0.0:* LISTEN 115492 76524 - tcp 0 0 169.254.241.18:53 0.0.0.0:* LISTEN 115492 76523 - tcp 0 0 169.254.241.18:53 0.0.0.0:* LISTEN 115492 76522 - tcp 0 0 192.168.178.203:53 0.0.0.0:* LISTEN 115492 76517 - tcp 0 0 192.168.178.203:53 0.0.0.0:* LISTEN 115492 76516 - tcp 0 0 192.168.178.203:53 0.0.0.0:* LISTEN 115492 76515 - tcp 0 0 192.168.178.203:53 0.0.0.0:* LISTEN 115492 76514 - tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 115492 78686 - tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 115492 78688 - tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 115492 78687 - tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 115492 78685 - tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN 0 54769 - tcp 0 0 0.0.0.0:662 0.0.0.0:* LISTEN 0 36461 - tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 31027 - tcp 0 0 127.0.0.1:40247 0.0.0.0:* LISTEN 297536 97536 - tcp 0 0 0.0.0.0:631 0.0.0.0:* LISTEN 0 59416 - tcp 0 0 127.0.0.1:38008 0.0.0.0:* LISTEN 0 110742 - tcp 0 0 127.0.0.1:32600 0.0.0.0:* LISTEN 297536 98173 - tcp 0 0 127.0.0.1:5432 0.0.0.0:* LISTEN 55 71637 - tcp 0 0 127.0.0.1:33304 0.0.0.0:* LISTEN 0 34158 - tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN 115492 78695 - tcp 0 0 0.0.0.0:1882 0.0.0.0:* LISTEN 1000 145106 - tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 0 47395 - tcp 0 0 0.0.0.0:892 0.0.0.0:* LISTEN 0 36195 - tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 0 53837 - tcp 0 0 127.0.0.1:512 0.0.0.0:* LISTEN 0 114413 - tcp 0 0 0.0.0.0:2049 0.0.0.0:* LISTEN 0 55954 - tcp 0 0 127.0.0.1:161 0.0.0.0:* LISTEN 0 45472 - tcp 0 0 0.0.0.0:6690 0.0.0.0:* LISTEN 0 106312 - tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1000 135803 - tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1000 131823 - tcp 0 0 0.0.0.0:873 0.0.0.0:* LISTEN 0 54571 - tcp 0 0 0.0.0.0:5001 0.0.0.0:* LISTEN 0 47391 - tcp 0 0 127.0.0.1:38443 0.0.0.0:* LISTEN 0 110744 - tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 0 53838 - tcp 0 0 0.0.0.0:5003 0.0.0.0:* LISTEN 0 47389 - tcp 0 0 0.0.0.0:4045 0.0.0.0:* LISTEN 0 55976 - tcp 0 0 0.0.0.0:5357 0.0.0.0:* LISTEN 0 49341 - tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 0 22207 - tcp 0 0 0.0.0.0:32400 0.0.0.0:* LISTEN 297536 82659 - tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 0 47393 - tcp6 0 0 2a02:8109:2740:2e30::53 :::* LISTEN 115492 172337 - tcp6 0 0 2a02:8109:2740:2e30::53 :::* LISTEN 115492 172336 - tcp6 0 0 2a02:8109:2740:2e30::53 :::* LISTEN 115492 172335 - tcp6 0 0 2a02:8109:2740:2e30::53 :::* LISTEN 115492 172334 - tcp6 0 0 fe80::211:32ff:fe9b::53 :::* LISTEN 115492 78692 - tcp6 0 0 fe80::211:32ff:fe9b::53 :::* LISTEN 115492 78691 - tcp6 0 0 fe80::211:32ff:fe9b::53 :::* LISTEN 115492 78690 - tcp6 0 0 fe80::211:32ff:fe9b::53 :::* LISTEN 115492 78689 - tcp6 0 0 ::1:53 :::* LISTEN 115492 76533 - tcp6 0 0 ::1:53 :::* LISTEN 115492 76532 - tcp6 0 0 ::1:53 :::* LISTEN 115492 76531 - tcp6 0 0 ::1:53 :::* LISTEN 115492 76530 - tcp6 0 0 :::21 :::* LISTEN 0 54770 - tcp6 0 0 :::8086 :::* LISTEN 1000 130412 - tcp6 0 0 :::662 :::* LISTEN 0 36466 - tcp6 0 0 :::22 :::* LISTEN 0 31034 - tcp6 0 0 :::631 :::* LISTEN 0 59417 - tcp6 0 0 :::3000 :::* LISTEN 472 124181 - tcp6 0 0 ::1:38008 :::* LISTEN 0 110743 - tcp6 0 0 :::443 :::* LISTEN 0 47396 - tcp6 0 0 :::892 :::* LISTEN 0 36199 - tcp6 0 0 :::445 :::* LISTEN 0 53835 - tcp6 0 0 :::3261 :::* LISTEN 0 48771 - tcp6 0 0 :::5566 :::* LISTEN 0 77124 - tcp6 0 0 :::3263 :::* LISTEN 0 49871 - tcp6 0 0 :::3264 :::* LISTEN 0 49873 - tcp6 0 0 :::2049 :::* LISTEN 0 55966 - tcp6 0 0 :::3265 :::* LISTEN 0 51895 - tcp6 0 0 :::6690 :::* LISTEN 0 106313 - tcp6 0 0 :::515 :::* LISTEN 0 58487 - tcp6 0 0 :::61991 :::* LISTEN 1000 148897 - tcp6 0 0 :::6281 :::* LISTEN 0 90992 - tcp6 0 0 :::873 :::* LISTEN 0 54572 - tcp6 0 0 :::5001 :::* LISTEN 0 47392 - tcp6 0 0 ::1:38443 :::* LISTEN 0 110745 - tcp6 0 0 :::139 :::* LISTEN 0 53836 - tcp6 0 0 :::5003 :::* LISTEN 0 47390 - tcp6 0 0 :::4045 :::* LISTEN 0 55978 - tcp6 0 0 :::5357 :::* LISTEN 0 49342 - tcp6 0 0 :::111 :::* LISTEN 0 22210 - tcp6 0 0 :::80 :::* LISTEN 0 47394 - udp 0 0 0.0.0.0:55696 0.0.0.0:* 1000 151886 - udp 0 0 127.0.0.1:55957 0.0.0.0:* 297536 96010 - udp 0 0 0.0.0.0:56016 0.0.0.0:* 1000 142224 - udp 0 0 0.0.0.0:56346 0.0.0.0:* 0 22206 - udp 0 0 0.0.0.0:44094 0.0.0.0:* 1000 141012 - udp 0 0 0.0.0.0:56769 0.0.0.0:* 1000 136498 - udp 0 0 0.0.0.0:3702 0.0.0.0:* 99 36872 - udp 0 0 0.0.0.0:32410 0.0.0.0:* 297536 96004 - udp 0 0 0.0.0.0:32412 0.0.0.0:* 297536 96005 - udp 0 0 0.0.0.0:32413 0.0.0.0:* 297536 96006 - udp 0 0 0.0.0.0:32414 0.0.0.0:* 297536 96003 - udp 0 0 0.0.0.0:44880 0.0.0.0:* 1000 138310 - udp 0 0 0.0.0.0:53169 0.0.0.0:* 0 35295 - udp 0 0 0.0.0.0:4045 0.0.0.0:* 0 55975 - udp 0 0 0.0.0.0:49146 0.0.0.0:* 1000 135059 - udp 0 0 172.17.0.1:53 0.0.0.0:* 115492 103335 - udp 0 0 172.17.0.1:53 0.0.0.0:* 115492 103336 - udp 0 0 172.17.0.1:53 0.0.0.0:* 115492 103334 - udp 0 0 172.17.0.1:53 0.0.0.0:* 115492 103333 - udp 0 0 169.254.241.18:53 0.0.0.0:* 115492 76521 - udp 0 0 169.254.241.18:53 0.0.0.0:* 115492 76520 - udp 0 0 169.254.241.18:53 0.0.0.0:* 115492 76519 - udp 0 0 169.254.241.18:53 0.0.0.0:* 115492 76518 - udp 0 0 192.168.178.203:53 0.0.0.0:* 115492 76513 - udp 0 0 192.168.178.203:53 0.0.0.0:* 115492 76512 - udp 0 0 192.168.178.203:53 0.0.0.0:* 115492 76511 - udp 0 0 192.168.178.203:53 0.0.0.0:* 115492 76510 - udp 0 0 127.0.0.1:53 0.0.0.0:* 115492 78684 - udp 0 0 127.0.0.1:53 0.0.0.0:* 115492 78683 - udp 0 0 127.0.0.1:53 0.0.0.0:* 115492 78682 - udp 0 0 127.0.0.1:53 0.0.0.0:* 115492 78681 - udp 0 0 0.0.0.0:68 0.0.0.0:* 0 29720 - udp 0 0 0.0.0.0:111 0.0.0.0:* 0 22205 - udp 0 0 0.0.0.0:123 0.0.0.0:* 0 36521 - udp 0 0 192.168.178.255:137 0.0.0.0:* 0 170893 - udp 0 0 192.168.178.203:137 0.0.0.0:* 0 170892 - udp 0 0 0.0.0.0:137 0.0.0.0:* 0 171950 - udp 0 0 192.168.178.255:138 0.0.0.0:* 0 170895 - udp 0 0 192.168.178.203:138 0.0.0.0:* 0 170894 - udp 0 0 0.0.0.0:138 0.0.0.0:* 0 171951 - udp 0 0 127.0.0.1:161 0.0.0.0:* 0 45471 - udp 0 0 127.0.0.1:323 0.0.0.0:* 0 36519 - udp 0 0 192.168.178.203:49483 0.0.0.0:* 297536 96008 - udp 0 0 0.0.0.0:41316 0.0.0.0:* 1000 145040 - udp 0 0 0.0.0.0:49618 0.0.0.0:* 1000 145934 - udp 0 0 0.0.0.0:61991 0.0.0.0:* 1000 148908 - udp 0 0 169.254.241.18:49723 0.0.0.0:* 297536 96015 - udp 0 0 127.0.0.1:619 0.0.0.0:* 0 36388 - udp 0 0 0.0.0.0:41620 0.0.0.0:* 1000 149081 - udp 0 0 0.0.0.0:662 0.0.0.0:* 0 36457 - udp 0 0 0.0.0.0:892 0.0.0.0:* 0 36193 - udp 0 0 169.254.241.18:37759 0.0.0.0:* 297536 96009 - udp 0 0 192.168.178.203:33717 0.0.0.0:* 297536 96014 - udp 0 0 0.0.0.0:41941 0.0.0.0:* 1000 149120 - udp 0 0 0.0.0.0:5353 0.0.0.0:* 1000 151729 - udp 0 0 192.168.178.203:5353 0.0.0.0:* 1000 143158 - udp 0 0 192.168.178.203:5353 0.0.0.0:* 1000 143641 - udp 0 0 0.0.0.0:5353 0.0.0.0:* 0 35293 - udp 0 0 127.0.0.1:54514 0.0.0.0:* 297536 96007 - udp 0 0 0.0.0.0:58694 0.0.0.0:* 1000 146404 - udp 0 0 0.0.0.0:38214 0.0.0.0:* 1000 135736 - udp 0 0 0.0.0.0:42386 0.0.0.0:* 1000 131903 - udp 0 0 0.0.0.0:42458 0.0.0.0:* 1000 147997 - udp 0 0 0.0.0.0:54762 0.0.0.0:* 1000 144365 - udp 0 0 0.0.0.0:42518 0.0.0.0:* 1000 139000 - udp 0 0 0.0.0.0:5683 0.0.0.0:* 1000 141042 - udp 0 0 0.0.0.0:54877 0.0.0.0:* 1000 150072 - udp 0 0 0.0.0.0:34406 0.0.0.0:* 1000 134738 - udp 0 0 0.0.0.0:34425 0.0.0.0:* 1000 151824 - udp 0 0 0.0.0.0:38577 0.0.0.0:* 1000 148893 - udp 0 0 0.0.0.0:34528 0.0.0.0:* 1000 6247571 - udp 0 0 192.168.178.203:46830 0.0.0.0:* 297536 96011 - udp 0 0 0.0.0.0:9997 0.0.0.0:* 0 29938 - udp 0 0 0.0.0.0:9998 0.0.0.0:* 0 29937 - udp 0 0 0.0.0.0:9999 0.0.0.0:* 0 29936 - udp 0 0 0.0.0.0:1900 0.0.0.0:* 0 49219 - udp 0 0 0.0.0.0:1901 0.0.0.0:* 297536 96013 - udp 0 0 0.0.0.0:51087 0.0.0.0:* 1000 139389 - udp 0 0 169.254.241.18:42991 0.0.0.0:* 297536 96012 - udp 0 0 0.0.0.0:2049 0.0.0.0:* 0 55965 - udp 0 0 0.0.0.0:51385 0.0.0.0:* 1000 141194 - udp 0 0 0.0.0.0:55516 0.0.0.0:* 1000 154626 - udp 0 0 0.0.0.0:43312 0.0.0.0:* 1000 142990 - udp6 0 0 :::3702 :::* 99 36874 - udp6 0 0 :::4045 :::* 0 55977 - udp6 0 0 2a02:8109:2740:2e30::53 :::* 115492 172333 - udp6 0 0 2a02:8109:2740:2e30::53 :::* 115492 172332 - udp6 0 0 2a02:8109:2740:2e30::53 :::* 115492 172331 - udp6 0 0 2a02:8109:2740:2e30::53 :::* 115492 172330 - udp6 0 0 fe80::211:32ff:fe9b::53 :::* 115492 76537 - udp6 0 0 fe80::211:32ff:fe9b::53 :::* 115492 76536 - udp6 0 0 fe80::211:32ff:fe9b::53 :::* 115492 76535 - udp6 0 0 fe80::211:32ff:fe9b::53 :::* 115492 76534 - udp6 0 0 ::1:53 :::* 115492 76529 - udp6 0 0 ::1:53 :::* 115492 76528 - udp6 0 0 ::1:53 :::* 115492 76527 - udp6 0 0 ::1:53 :::* 115492 76526 - udp6 0 0 :::111 :::* 0 22208 - udp6 0 0 :::123 :::* 0 36522 - udp6 0 0 ::1:323 :::* 0 36520 - udp6 0 0 :::37315 :::* 0 35296 - udp6 0 0 :::662 :::* 0 36464 - udp6 0 0 :::892 :::* 0 36197 - udp6 0 0 :::5353 :::* 0 35294 - udp6 0 0 :::58682 :::* 0 22209 - udp6 0 0 :::2049 :::* 0 55967 - *** Log File - Last 25 Lines *** 2024-02-22 15:53:42.856 - info: shelly.1 (450) [MQTT] Device with client id "shellyplus1pm-0cdc7ef62c9c" connected! 2024-02-22 15:53:47.028 - info: shelly.1 (450) [MQTT] Device with client id "shellyplus1pm-0cdc7ef5afd0" connected! 2024-02-22 15:53:47.028 - info: shelly.1 (450) [MQTT] Device with client id "shellyplus1pm-0cdc7ef5afd0" connected! 2024-02-22 15:53:49.586 - info: shelly.1 (450) [MQTT] Client Close: (shellyplus1pm / shellyplus1pm-4855199c1ee8 / shellyplus1pm#4855199c1ee8#1) (false) 2024-02-22 15:53:49.586 - info: shelly.1 (450) [MQTT] Client Close: (shellyplus1pm / shellyplus1pm-4855199c1ee8 / shellyplus1pm#4855199c1ee8#1) (false) 2024-02-22 15:53:52.654 - info: shelly.1 (450) [MQTT] Client Close: (shellyplus1pm / shellyplus1pm-0cdc7ef6696c / shellyplus1pm#0cdc7ef6696c#1) (false) 2024-02-22 15:53:52.654 - info: shelly.1 (450) [MQTT] Client Close: (shellyplus1pm / shellyplus1pm-0cdc7ef6696c / shellyplus1pm#0cdc7ef6696c#1) (false) 2024-02-22 15:53:52.679 - info: shelly.1 (450) [MQTT] Device with client id "shellyplus1pm-4855199d205c" connected! 2024-02-22 15:53:52.679 - info: shelly.1 (450) [MQTT] Device with client id "shellyplus1pm-4855199d205c" connected! 2024-02-22 15:53:52.854 - info: shelly.1 (450) [MQTT] Client Close: (shellyplus1pm / shellyplus1pm-0cdc7ef62c9c / shellyplus1pm#0cdc7ef62c9c#1) (false) 2024-02-22 15:53:52.854 - info: shelly.1 (450) [MQTT] Client Close: (shellyplus1pm / shellyplus1pm-0cdc7ef62c9c / shellyplus1pm#0cdc7ef62c9c#1) (false) 2024-02-22 15:53:54.229 - info: shelly.1 (450) [MQTT] Device with client id "shellyplus1pm-4855199d1ee8" connected! 2024-02-22 15:53:54.229 - info: shelly.1 (450) [MQTT] Device with client id "shellyplus1pm-4855199d1ee8" connected! 2024-02-22 15:53:56.551 - info: shelly.1 (450) [MQTT] Device with client id "shellyplus1pm-0cdc7ef62910" connected! 2024-02-22 15:53:56.551 - info: shelly.1 (450) [MQTT] Device with client id "shellyplus1pm-0cdc7ef62910" connected! 2024-02-22 15:53:57.025 - info: shelly.1 (450) [MQTT] Client Close: (shellyplus1pm / shellyplus1pm-0cdc7ef5afd0 / shellyplus1pm#0cdc7ef5afd0#1) (false) 2024-02-22 15:53:57.025 - info: shelly.1 (450) [MQTT] Client Close: (shellyplus1pm / shellyplus1pm-0cdc7ef5afd0 / shellyplus1pm#0cdc7ef5afd0#1) (false) 2024-02-22 15:53:57.950 - info: shelly.1 (450) [MQTT] Device with client id "shellyplus1pm-0cdc7ef5a954" connected! 2024-02-22 15:53:57.950 - info: shelly.1 (450) [MQTT] Device with client id "shellyplus1pm-0cdc7ef5a954" connected! 2024-02-22 15:54:01.850 - info: shelly.1 (450) [MQTT] Device with client id "shellyplus1pm-0cdc7ef62cbc" connected! 2024-02-22 15:54:01.850 - info: shelly.1 (450) [MQTT] Device with client id "shellyplus1pm-0cdc7ef62cbc" connected! 2024-02-22 15:54:02.131 - info: shelly.1 (450) [MQTT] Device with client id "shellyplus1pm-4855199cfa60" connected! 2024-02-22 15:54:02.131 - info: shelly.1 (450) [MQTT] Device with client id "shellyplus1pm-4855199cfa60" connected! 2024-02-22 15:54:02.670 - info: shelly.1 (450) [MQTT] Client Close: (shellyplus1pm / shellyplus1pm-4855199d205c / shellyplus1pm#4855199d205c#1) (false) 2024-02-22 15:54:02.670 - info: shelly.1 (450) [MQTT] Client Close: (shellyplus1pm / shellyplus1pm-4855199d205c / shellyplus1pm#4855199d205c#1) (false) -
@dr-pie
Ich tippe mal ein Problem mit dem device watcher.
Lese mal hier.
https://github.com/ciddi89/ioBroker.device-watcher/issues/283Stoppe mal den Adapter ob sich dann die Auslastung normalisiert.
-
@oliverio sagte in Teilweise über 200% CPU Auslastung im Docker:
@dr-pie
Ich tippe mal ein Problem mit dem device watcher.
Lese mal hier.
https://github.com/ciddi89/ioBroker.device-watcher/issues/283Stoppe mal den Adapter ob sich dann die Auslastung normalisiert.
Ich komme ja nicht auf die iob-Oberfläche.
Der Editor funktioniert nach ca. 15 Minuten. Auch die Vis ist verfügbar.Jeder klick in der Vis bedeutet aber waaaaarten -
@oliverio sagte in Teilweise über 200% CPU Auslastung im Docker:
@dr-pie
Ich tippe mal ein Problem mit dem device watcher.Stoppe mal den Adapter ob sich dann die Auslastung normalisiert.
In einer Millisekunde konnte ich auf den iob kommen.
Habe dann den "device watcher" angehalten ... und siehe da ...die CPU Auslastung normalisierte sich wieder. -
@dr-pie
Man kann Adapter auch über console Befehle starten und stoppen -
@oliverio sagte in Teilweise über 200% CPU Auslastung im Docker:
@dr-pie
Man kann Adapter auch über console Befehle starten und stoppenHab ich gerade raus gefunden.
-
@dr-pie sagte in Teilweise über 200% CPU Auslastung im Docker:
Docker : v8.0.1
/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.0nodejs:
Installed: 18.17.1-deb-1nodesource1
Candidate: 18.17.1-deb-1nodesource1Docker Image ist alt und du bleibst auf der nodejs Version stehen .
-
@glasfaser sagte in Teilweise über 200% CPU Auslastung im Docker:
@dr-pie sagte in Teilweise über 200% CPU Auslastung im Docker:
Docker : v8.0.1
/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.0nodejs:
Installed: 18.17.1-deb-1nodesource1
Candidate: 18.17.1-deb-1nodesource1Docker Image ist alt und du bleibst auf der nodejs Version stehen .
Liegt vielleicht daran dass ich nicht wirklich weiss wie
-
hach, wenn es nur eine beschreibung dafür geben würde, wo das alles genauch beschrieben ist.
huch
https://docs.buanet.de/de/iobroker-docker-image/docs/#hochrustung-upgradeoder alternativ die ältere doku für portainer
https://smarthome.buanet.de/2020/10/iobroker-docker-container-updates-upgrades/ -
@dr-pie sagte in Teilweise über 200% CPU Auslastung im Docker:
Liegt vielleicht daran
Jein ...
Aber @OliverIO hat dir schon ein Tip zur Auslastung von einem bestimmten Adapter genannt , der hier bei vielen Probleme macht !
Und das mit der Synology Anzeige / Diagramm ist ein Schätzeisen ...
aber das Thema haben ich und @OliverIO schon mehrmals hier im Forum durchgekaut .
