iobroker Probleme nach Stop oder ähnlichen
-
@tmartin sagte in iobroker Probleme nach Stop oder ähnlichen:
Operating System codenamed 'focal' is an aging Ubuntu release! Please upgrade to the latest LTS release 'noble' in due time!
Solltest du in Bälde angehen. Ich würde auch auf einem Server eher zur 'Mutter' Debian raten.
Dann wirst du nämlich auch diese Prozesse los:/dev/loop1 squashfs 64M 64M 0 100% /snap/core20/2434 /dev/loop0 squashfs 104M 104M 0 100% /snap/core/16928 /dev/loop2 squashfs 64M 64M 0 100% /snap/core20/2379 /dev/loop3 squashfs 105M 105M 0 100% /snap/core/17200 /dev/loop5 squashfs 92M 92M 0 100% /snap/lxd/29619 /dev/loop4 squashfs 92M 92M 0 100% /snap/lxd/24061Was ist das?
tcp6 0 0 :::9995 :::* LISTEN 0 3567166 1337346/node /opt/o tcp6 0 0 :::9996 :::* LISTEN 0 3567346 1337346/node /opt/o tcp6 0 0 :::9997 :::* LISTEN 0 3568423 1337346/node /opt/o tcp6 0 0 :::9998 :::* LISTEN 0 3566468 1337346/node /opt/oDa läuft ein node-Prozess paralell zum ioBroker, würde ich behaupten.
ls -la /opt/sagt?
Ansonsten schaut das aber gut aus.
wir würden auch ungerne den iobroker neu installieren
Du solltest aber immer diese Option mitdenken und dir eine worst-case-Strategie überlegen. Es kann ja z. B. auch die Hardware mal abrauchen.
| | | | | `-- reconnect-core@0.0.1 invalid: "https://github.com/dodo/reconnect-core/tarball/merged" from node_modules/node-xmpp-core
Das Modul liegt in der vierten Unterebene. Schau dir an welches Modul der Ursprung ist:
cd /opt/iobroker npm ls reconnect-core -
tcp6 0 0 :::9995 :::* LISTEN 0 3567166 1337346/node /opt/o tcp6 0 0 :::9996 :::* LISTEN 0 3567346 1337346/node /opt/o tcp6 0 0 :::9997 :::* LISTEN 0 3568423 1337346/node /opt/o tcp6 0 0 :::9998 :::* LISTEN 0 3566468 1337346/node /opt/oDa läuft unser Kamera-Service mit 4 Kameras unseres Gebäudes, welche ein Stream aufbauen, grundsätzlich nichts weiter mit dem iobroker zu tun, außer das wir dort die Werte abspeichern.
npm ls reconnect-coreKommt anscheinend von unserem Deebot-Adapter, welchen wir für unseren Staubsauger nutzen.
tmartin@pfitiob01:/opt/iobroker$ npm ls reconnect-core iobroker.inst@2.0.3 /opt/iobroker └─┬ iobroker.ecovacs-deebot@1.4.15 └─┬ ecovacs-deebot@0.9.6-beta.3 └─┬ simple-xmpp@2.3.1 └─┬ node-xmpp-client@3.2.0 └─┬ node-xmpp-core@5.0.9 └── reconnect-core@0.0.1 -
Ansonsten sehe ich da groß keine Auffälligkeiten.
Bring doch mal den js-controller auf den aktuellen Stand.
Per Kommandozeile, vielleicht sieht man da was. -
Update hat sehr lange gebraucht aber keine Auffälligkeiten außer
Server Configured backup period 7200000 is larger than the supported maximum of 35791 minutes. Defaulting to 120 minutes.mache ich dann einen iob start sieht auch erstmal alles okay aus, nach kurzer Zeit dann den befehl "iob status" und wieder folgender Fehler:
tmartin@pfitiob01:/opt/iobroker$ iob status node:internal/modules/cjs/loader:1228 throw err; ^ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' at Module._resolveFilename (node:internal/modules/cjs/loader:1225:15) at Module._load (node:internal/modules/cjs/loader:1051:27) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:173:12) at node:internal/main/run_main_module:28:49 { code: 'MODULE_NOT_FOUND', requireStack: [] } Node.js v20.18.1In den iobroker-logs folgende Fehler:
2024-12-04 09:51:40.362 - error: host.pfitiob01 uncaught exception: Could not determine controller directory 2024-12-04 09:51:40.362 - error: host.pfitiob01 Error: Could not determine controller directory at getControllerDir (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/esm/lib/common/tools.js:1833:11) at Module.getAdapterDir (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/esm/lib/common/tools.js:1306:37) -
iob diag full
Script v.2024-10-19 *** BASE SYSTEM *** Static hostname: pfitiob01 Icon name: computer-vm Chassis: vm Virtualization: kvm Operating System: Ubuntu 20.04.6 LTS Kernel: Linux 5.4.0-200-generic Architecture: x86-64 OS is similar to: debian model name : Common KVM processor Docker : false Virtualization : kvm Kernel : x86_64 Userland : 64 bit Systemuptime and Load: 09:53:17 up 1 day, 18:50, 1 user, load average: 1.15, 1.23, 0.73 CPU threads: 8 *** LIFE CYCLE STATUS *** Operating System codenamed 'focal' is an aging Ubuntu release! Please upgrade to the latest LTS release 'noble' in due time! *** TIME AND TIMEZONES *** Local time: Wed 2024-12-04 09:53:17 CET Universal time: Wed 2024-12-04 08:53:17 UTC RTC time: Wed 2024-12-04 08:53:19 Time zone: Europe/Berlin (CET, +0100) System clock synchronized: yes NTP service: n/a RTC in local TZ: no *** Users and Groups *** User that called 'iob diag': tmartin HOME=/home/tmartin GROUPS=users adm sudo iobroker sshuser User that is running 'js-controller': iobroker HOME=/home/iobroker GROUPS=iobroker tty dialout audio video plugdev redis *** DISPLAY-SERVER SETUP *** Display-Server: false Desktop: Terminal: tty *** MEMORY *** total used free shared buff/cache available Mem: 7.9G 2.4G 2.2G 1.0M 3.4G 5.2G Swap: 4.1G 5.0M 4.1G Total: 12G 2.4G 6.2G Active iob-Instances: 18 7945 M total memory 2388 M used memory 3307 M active memory 1893 M inactive memory 2157 M free memory 414 M buffer memory 2984 M swap cache 4095 M total swap 5 M used swap 4090 M free swap *** top - Table Of Processes *** top - 09:53:18 up 1 day, 18:50, 1 user, load average: 1.14, 1.23, 0.73 Tasks: 193 total, 1 running, 192 sleeping, 0 stopped, 0 zombie %Cpu(s): 3.2 us, 1.6 sy, 0.0 ni, 95.2 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 7945.3 total, 2154.9 free, 2391.0 used, 3399.5 buff/cache MiB Swap: 4096.0 total, 4090.5 free, 5.5 used. 5242.1 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** DMESG CRITICAL ERRORS *** No critical errors detected *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 3.9G 0 3.9G 0% /dev tmpfs tmpfs 795M 1.3M 794M 1% /run /dev/sda2 ext4 63G 27G 33G 45% / tmpfs tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup /dev/loop1 squashfs 64M 64M 0 100% /snap/core20/2434 /dev/loop0 squashfs 104M 104M 0 100% /snap/core/16928 /dev/loop2 squashfs 64M 64M 0 100% /snap/core20/2379 /dev/loop3 squashfs 105M 105M 0 100% /snap/core/17200 /dev/loop5 squashfs 92M 92M 0 100% /snap/lxd/29619 /dev/loop4 squashfs 92M 92M 0 100% /snap/lxd/24061 tmpfs tmpfs 795M 0 795M 0% /run/user/2005 Messages concerning ext4 filesystem in dmesg: [Mon Dec 2 15:03:08 2024] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null) [Mon Dec 2 15:03:09 2024] EXT4-fs (sda2): re-mounted. Opts: (null) Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/sda2 ext4 rw,relatime |-/sys/kernel/tracing tracefs tracefs rw,nosuid,nodev,noexec,relatime |-/snap/core20/2434 /dev/loop1 squashfs ro,nodev,relatime |-/snap/core/16928 /dev/loop0 squashfs ro,nodev,relatime |-/snap/core20/2379 /dev/loop2 squashfs ro,nodev,relatime |-/snap/core/17200 /dev/loop3 squashfs ro,nodev,relatime |-/snap/lxd/29619 /dev/loop5 squashfs ro,nodev,relatime |-/snap/lxd/24061 /dev/loop4 squashfs ro,nodev,relatime `-/var/lib/lxcfs lxcfs fuse.lxcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other Files in neuralgic directories: /var: 2.1G /var/ 1.4G /var/lib 742M /var/lib/snapd 520M /var/lib/snapd/snaps 432M /var/mail Archived and active journals take up 80.0M in the file system. /opt/iobroker/backups: 4.0K /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 1.8G /opt/iobroker/iobroker-data/ 1.6G /opt/iobroker/iobroker-data/files 946M /opt/iobroker/iobroker-data/files/images 617M /opt/iobroker/iobroker-data/files/javascript.admin 560M /opt/iobroker/iobroker-data/files/javascript.admin/static The five largest files in iobroker-data are: 31M /opt/iobroker/iobroker-data/objects.jsonl 24M /opt/iobroker/iobroker-data/files/modbus.admin/static/js/main.6a71b34c.js.map 9.7M /opt/iobroker/iobroker-data/objects.json.bak.migrated 9.3M /opt/iobroker/iobroker-data/files/modbus.admin/static/js/main.6a71b34c.js 8.7M /opt/iobroker/iobroker-data/files/javascript.admin/static/js/838.0aa41cb0.chunk.js.map USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': /dev/serial/by-id/usb-0658_0200-if00 *** NodeJS-Installation *** /usr/bin/nodejs v20.18.1 /usr/bin/node v20.18.1 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.29.4 nodejs: Installed: 20.18.1-1nodesource1 Candidate: 20.18.1-1nodesource1 Version table: *** 20.18.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 20.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.15.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.13.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.12.2-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.12.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.11.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.8.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.6.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.5.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.3.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 10.19.0~dfsg-3ubuntu1.6 500 500 http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-security/universe amd64 Packages 10.19.0~dfsg-3ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: redis Hosts: pfitiob01 pfitiob01 (version: 7.0.3, hostname: pfitiob01 , alive, uptime: 76) Core adapters versions js-controller: 7.0.3 admin: 7.1.5 javascript: 8.8.3 nodejs modules from github: 1 | | | | | `-- reconnect-core@0.0.1 invalid: "https://github.com/dodo/reconnect-core/tarball/merged" from node_modules/node-xmpp-core Adapter State + system.adapter.admin.1 : admin : pfitiob01 - enabled, port: 8180, bind: 0.0.0.0 (SSL), run as: admin + system.adapter.discovery.0 : discovery : pfitiob01 - enabled system.adapter.doorbird.0 : doorbird : pfitiob01 - enabled + system.adapter.ecovacs-deebot.0 : ecovacs-deebot : pfitiob01 - enabled + system.adapter.email.0 : email : pfitiob01 - enabled + system.adapter.email.1 : email : pfitiob01 - enabled + system.adapter.history.0 : history : pfitiob01 - enabled + system.adapter.hue.0 : hue : pfitiob01 - enabled, port: 443 + system.adapter.javascript.0 : javascript : pfitiob01 - enabled + system.adapter.lovelace.0 : lovelace : pfitiob01 - enabled, port: 8091, bind: 0.0.0.0, run as: admin + system.adapter.modbus.0 : modbus : pfitiob01 - enabled + system.adapter.modbus.1 : modbus : pfitiob01 - enabled + system.adapter.modbus.2 : modbus : pfitiob01 - enabled + system.adapter.mqtt.0 : mqtt : pfitiob01 - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.rest-api.0 : rest-api : pfitiob01 - enabled, port: 8093, bind: 0.0.0.0, run as: admin + system.adapter.simple-api.0 : simple-api : pfitiob01 - enabled, port: 8087, bind: 0.0.0.0, run as: admin + system.adapter.socketio.0 : socketio : pfitiob01 - enabled, port: 8084, bind: 0.0.0.0 (SSL), run as: admin + system.adapter.zwave2.1 : zwave2 : pfitiob01 - enabled + instance is alive Enabled adapters with bindings + system.adapter.admin.1 : admin : pfitiob01 - enabled, port: 8180, bind: 0.0.0.0 (SSL), run as: admin + system.adapter.hue.0 : hue : pfitiob01 - enabled, port: 443 + system.adapter.lovelace.0 : lovelace : pfitiob01 - enabled, port: 8091, bind: 0.0.0.0, run as: admin + system.adapter.mqtt.0 : mqtt : pfitiob01 - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.rest-api.0 : rest-api : pfitiob01 - enabled, port: 8093, bind: 0.0.0.0, run as: admin + system.adapter.simple-api.0 : simple-api : pfitiob01 - enabled, port: 8087, bind: 0.0.0.0, run as: admin + system.adapter.socketio.0 : socketio : pfitiob01 - enabled, port: 8084, bind: 0.0.0.0 (SSL), run as: admin ioBroker-Repositories ┌─────────┬────────────────────┬─────────────────────────────────────────────────────────┬──────────────┐ │ (index) │ name │ url │ auto upgrade │ ├─────────┼────────────────────┼─────────────────────────────────────────────────────────┼──────────────┤ │ 0 │ 'Stable (default)' │ 'http://download.iobroker.net/sources-dist.json' │ false │ │ 1 │ 'Beta (latest)' │ 'http://download.iobroker.net/sources-dist-latest.json' │ false │ └─────────┴────────────────────┴─────────────────────────────────────────────────────────┴──────────────┘ Active repo(s): Stable (default) Upgrade policy: none Installed ioBroker-Instances Used repository: Stable (default) Adapter "admin" : 7.1.5 , installed 7.1.5 Adapter "discovery" : 5.0.0 , installed 5.0.0 Adapter "doorbird" : 2.0.0 , installed 2.0.0 Adapter "ecovacs-deebot": 1.4.15 , installed 1.4.15 Adapter "email" : 1.3.1 , installed 1.3.1 Adapter "history" : 3.0.1 , installed 3.0.1 Adapter "hue" : 3.13.1 , installed 3.13.1 Adapter "javascript" : 8.8.3 , installed 8.8.3 Controller "js-controller": 7.0.3 , installed 7.0.3 Adapter "lovelace" : 4.1.10 , installed 4.1.10 Adapter "modbus" : 6.3.2 , installed 6.3.2 Adapter "mqtt" : 6.1.2 , installed 6.1.2 Adapter "rest-api" : 2.0.3 , installed 2.0.3 Adapter "simple-api" : 2.8.0 , installed 2.8.0 Adapter "socketio" : 6.7.1 , installed 6.7.1 Adapter "sql" : 3.0.1 , installed 3.0.1 Adapter "zwave2" : 3.1.0 , installed 3.1.0 Objects and States Please stand by - This may take a while Objects: 6177 States: 4973 *** OS-Repositories and Updates *** Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease Hit:2 http://archive.ubuntu.com/ubuntu focal-updates InRelease Hit:3 http://archive.ubuntu.com/ubuntu focal-backports InRelease Hit:4 https://deb.nodesource.com/node_20.x nodistro InRelease Hit:5 http://archive.ubuntu.com/ubuntu focal-security 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.53:53 0.0.0.0:* LISTEN 101 19450 662/systemd-resolve tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 0 24124 1826/master tcp 0 0 0.0.0.0:1882 0.0.0.0:* LISTEN 1001 3757645 1403213/io.mqtt.0 tcp 0 0 0.0.0.0:52220 0.0.0.0:* LISTEN 0 26310 766/sshd: /usr/sbin tcp 0 0 192.168.51.101:8100 0.0.0.0:* LISTEN 1001 3761221 1403865/io.doorbird tcp 0 0 127.0.0.1:33060 0.0.0.0:* LISTEN 113 24088 941/mysqld tcp 0 0 0.0.0.0:9001 0.0.0.0:* LISTEN 1001 3754701 1403062/iobroker.js tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN 113 24093 941/mysqld tcp 0 0 127.0.0.1:6379 0.0.0.0:* LISTEN 111 26350 907/redis-server 12 tcp6 0 0 :::4433 :::* LISTEN 0 3568349 1337346/node /opt/o tcp6 0 0 :::465 :::* LISTEN 0 3568348 1337346/node /opt/o tcp6 0 0 :::8084 :::* LISTEN 1001 3756784 1403421/io.socketio tcp6 0 0 :::8180 :::* LISTEN 1001 3756574 1403080/io.admin.1 tcp6 0 0 :::8087 :::* LISTEN 1001 3757003 1403723/io.simple-a tcp6 0 0 :::25 :::* LISTEN 0 24125 1826/master tcp6 0 0 :::8091 :::* LISTEN 1001 3757722 1403328/io.lovelace tcp6 0 0 :::6556 :::* LISTEN 997 26927 684/cmk-agent-ctl tcp6 0 0 :::52220 :::* LISTEN 0 26312 766/sshd: /usr/sbin tcp6 0 0 :::8093 :::* LISTEN 1001 3758057 1403796/io.rest-api tcp6 0 0 :::9995 :::* LISTEN 0 3567166 1337346/node /opt/o tcp6 0 0 :::9996 :::* LISTEN 0 3567346 1337346/node /opt/o tcp6 0 0 :::9997 :::* LISTEN 0 3568423 1337346/node /opt/o tcp6 0 0 :::9998 :::* LISTEN 0 3566468 1337346/node /opt/o tcp6 0 0 :::80 :::* LISTEN 0 26951 842/apache2 udp 0 0 0.0.0.0:43640 0.0.0.0:* 112 23439 680/avahi-daemon: r udp 0 0 0.0.0.0:48451 0.0.0.0:* 102 26793 721/rsyslogd udp 0 0 127.0.0.53:53 0.0.0.0:* 101 19449 662/systemd-resolve udp 0 0 192.168.51.101:123 0.0.0.0:* 0 26295 763/ntpd udp 0 0 127.0.0.1:123 0.0.0.0:* 0 26293 763/ntpd udp 0 0 0.0.0.0:123 0.0.0.0:* 0 26287 763/ntpd udp 0 0 0.0.0.0:5353 0.0.0.0:* 112 23347 680/avahi-daemon: r udp6 0 0 fe80::98c0:f3ff:fe4:123 :::* 0 26299 763/ntpd udp6 0 0 ::1:123 :::* 0 26297 763/ntpd udp6 0 0 :::123 :::* 0 26284 763/ntpd udp6 0 0 :::41674 :::* 112 23440 680/avahi-daemon: r udp6 0 0 :::5353 :::* 112 23348 680/avahi-daemon: r *** Log File - Last 25 Lines *** 2024-12-04 09:53:12.420 - info: zwave2.1 (1403775) Node 145: ready to use 2024-12-04 09:53:12.504 - info: zwave2.1 (1403775) Node 146: ready to use 2024-12-04 09:53:12.775 - info: host.pfitiob01 instance system.adapter.doorbird.0 in version "2.0.0" started with pid 1403865 2024-12-04 09:53:12.795 - info: zwave2.1 (1403775) Node 147: ready to use 2024-12-04 09:53:12.850 - info: zwave2.1 (1403775) Node 150: ready to use 2024-12-04 09:53:12.925 - info: zwave2.1 (1403775) Node 176: ready to use 2024-12-04 09:53:13.005 - info: zwave2.1 (1403775) Node 178: ready to use 2024-12-04 09:53:13.049 - info: zwave2.1 (1403775) Node 185: ready to use 2024-12-04 09:53:13.076 - info: zwave2.1 (1403775) Node 187: ready to use 2024-12-04 09:53:13.134 - info: zwave2.1 (1403775) Node 188: ready to use 2024-12-04 09:53:13.167 - info: zwave2.1 (1403775) Node 189: ready to use 2024-12-04 09:53:13.243 - info: zwave2.1 (1403775) Node 192: ready to use 2024-12-04 09:53:13.303 - info: zwave2.1 (1403775) Node 194: ready to use 2024-12-04 09:53:13.330 - info: modbus.2 (1403298) Disconnected from slave 192.168.51.98 2024-12-04 09:53:13.386 - info: zwave2.1 (1403775) Node 195: ready to use 2024-12-04 09:53:13.451 - info: zwave2.1 (1403775) Node 199: ready to use 2024-12-04 09:53:13.477 - info: zwave2.1 (1403775) Node 201: ready to use 2024-12-04 09:53:13.528 - info: zwave2.1 (1403775) Node 204: ready to use 2024-12-04 09:53:13.580 - info: zwave2.1 (1403775) Node 205: ready to use 2024-12-04 09:53:13.586 - info: doorbird.0 (1403865) starting. Version 2.0.0 in /opt/iobroker/node_modules/iobroker.doorbird, node: v20.18.1, js-controller: 7.0.3 2024-12-04 09:53:13.611 - info: zwave2.1 (1403775) Node 206: ready to use 2024-12-04 09:53:13.756 - info: zwave2.1 (1403775) Node 211: ready to use 2024-12-04 09:53:13.853 - info: zwave2.1 (1403775) State value to set for "zwave2.1.Node_211.Climate_Control_Schedule.overrideState" has to be type "number" but received type "string" 2024-12-04 09:53:23.332 - info: modbus.2 (1403298) Connected to slave 192.168.51.98 2024-12-04 09:53:33.532 - warn: modbus.2 (1403298) [DevID_1] Poll error count: 3 code: "App Timeout"Und die Summary
======================= SUMMARY ======================= v.2024-10-19 Static hostname: pfitiob01 Icon name: computer-vm Chassis: vm Virtualization: kvm Operating System: Ubuntu 20.04.6 LTS Kernel: Linux 5.4.0-200-generic Architecture: x86-64 Installation: kvm Kernel: x86_64 Userland: 64 bit Timezone: Europe/Berlin (CET, +0100) User-ID: 2005 Display-Server: false Boot Target: multi-user.target Pending OS-Updates: 0 Pending iob updates: 0 Nodejs-Installation: /usr/bin/nodejs v20.18.1 /usr/bin/node v20.18.1 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.29.4 Recommended versions are nodejs 20.18.1 and npm 10.8.2 nodeJS installation is correct MEMORY: total used free shared buff/cache available Mem: 7.9G 4.0G 137M 1.0M 3.8G 3.7G Swap: 4.1G 6.0M 4.1G Total: 12G 4.0G 4.2G Active iob-Instances: 18 Upgrade policy: none ioBroker Core: js-controller 7.0.3 admin 7.1.5 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: redis Status admin and web instance: + system.adapter.admin.1 : admin : pfitiob01 - enabled, port: 8180, bind: 0.0.0.0 (SSL), run as: admin Objects: 6177 States: 4973 Size of iob-Database: 31M /opt/iobroker/iobroker-data/objects.jsonl 9.7M /opt/iobroker/iobroker-data/objects.json.bak.migrated 528K /opt/iobroker/iobroker-data/states.json.bak 528K /opt/iobroker/iobroker-data/states.json Operating System codenamed 'focal' is an aging Ubuntu release! Please upgrade to the latest LTS release 'noble' in due time! =================== END OF SUMMARY ==================== -
@tmartin Habe jetzt nochmal einen iob start u. iob start admin gemacht, sowie gleichzeitig das iobroker.current.log überwacht. Soweit alles OK, auch Zugriff auf die Admin-Oberfläche möglich.
Manchmal hatte ich auch das gefühl, dass der iobroker die Verbindung verliert, wenn ich auf der admin fläche aktiv bin und klicke
-
-
iobroker.service - ioBroker Server Loaded: loaded (/lib/systemd/system/iobroker.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2024-12-04 09:52:03 CET; 11min ago Docs: http://iobroker.net Main PID: 1403062 (iobroker.js-con) Tasks: 209 (limit: 9424) Memory: 2.2G CGroup: /system.slice/iobroker.service ├─1403062 iobroker.js-controller ├─1403080 io.admin.1 ├─1403126 io.email.0 ├─1403141 io.javascript.0 ├─1403168 io.history.0 ├─1403183 io.email.1 ├─1403198 io.hue.0 ├─1403213 io.mqtt.0 ├─1403268 io.modbus.0 ├─1403283 io.modbus.1 ├─1403313 io.discovery.0 ├─1403328 io.lovelace.0 ├─1403421 io.socketio.0 ├─1403723 io.simple-api.0 ├─1403756 io.ecovacs-deebot.0 ├─1403775 io.zwave2.1 ├─1403796 io.rest-api.0 ├─1403865 io.doorbird.0 └─1408356 io.modbus.2 Dez 04 09:52:06 pfitiob01 sudo[1403122]: pam_unix(sudo:session): session closed for user root Dez 04 09:58:54 pfitiob01 bash[1403062]: Unknown request: {"type":"repairs/list_issues","id":17} Dez 04 09:58:54 pfitiob01 bash[1403062]: Unknown request: {"type":"recorder/info","id":18} Dez 04 09:59:21 pfitiob01 bash[1403062]: ================================== > LOG REDIRECT system.adapter.admin.1 => true [system.adapter.admin.1.logging] Dez 04 09:59:21 pfitiob01 sudo[1409455]: iobroker : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/apt -v Dez 04 09:59:21 pfitiob01 sudo[1409455]: pam_unix(sudo:session): session opened for user root by (uid=0) Dez 04 09:59:21 pfitiob01 sudo[1409455]: pam_unix(sudo:session): session closed for user root Dez 04 09:59:21 pfitiob01 sudo[1409460]: iobroker : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/apt list --upgradeable Dez 04 09:59:21 pfitiob01 sudo[1409460]: pam_unix(sudo:session): session opened for user root by (uid=0) Dez 04 09:59:22 pfitiob01 sudo[1409460]: pam_unix(sudo:session): session closed for user rootmich wundert, dass dort root steht? Bin ja logischerweise nicht mit root drin, sondern meinen eigenen user
-
Aber
aptmuss vom root ausgeführt werden, das ist also i. O. -
@thomas-braun Warum auch immer er jetzt läuft, ich hatte das Upgrade vom JS-Controller bereits am Montag probiert, danach lief absolut gar nichts mehr auch nach warten etc.
Ich würde den Beitrag erstmal auf Gelöst setzen, sofern jetzt nichts weiter passiert.
-
@tmartin Okay ne, nach erneuten restart weil ich meinen slave nun endlich mal mit dem master verbinden wollte, kracht er weiterhin mit dem gleichen fehler.
Im slave dann außerdem noch folgender Fehler:
Error: No configuration received! at file:///opt/iobroker/node_modules/@iobroker/js-controller-cli/src/lib/setup/setupMultihost.ts:311:26 at onFinished (file:///opt/iobroker/node_modules/@iobroker/js-controller-cli/src/lib/setup/multihostClient.ts:266:21) at Timeout.<anonymous> (file:///opt/iobroker/node_modules/@iobroker/js-controller-cli/src/lib/setup/multihostClient.ts:98:17) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)Sicherlich weil der Master die ganze Zeit neustartet.
