[gelöst] adapter.discovery Exception-Code: EADDRINUSE
-
In einer neuen ioBroker-Installation auf einem debian bookworm habe ich einen Fehler beim Ausführen von adapter.discovery:
Exception-Code: EADDRINUSE: addMembership EADDRINUSE
Welche IP oder welchen Port möchte discovery da verwenden und kann nicht?
Die Oberfläche unter http://kaczmarek.local:8081 ist erreichbar.
iob diag:
bash Script v.2024-10-19 *** BASE SYSTEM *** Static hostname: kaczmarek Icon name: computer-desktop Chassis: desktop 🖥 Operating System: Debian GNU/Linux 12 (bookworm) Kernel: Linux 6.1.0-26-amd64 Architecture: x86-64 Hardware Vendor: PC Engines Hardware Model: APU2 Firmware Version: 4.0.7 OS is similar to: model name : AMD GX-412TC SOC Docker : false Virtualization : none Kernel : x86_64 Userland : 64 bit Systemuptime and Load: 20:32:30 up 1:17, 3 users, load average: 0.46, 0.19, 0.20 CPU threads: 4 *** LIFE CYCLE STATUS *** Operating System is the current Debian stable version codenamed 'bookworm'! *** TIME AND TIMEZONES *** Local time: Tue 2024-11-05 20:32:30 CET Universal time: Tue 2024-11-05 19:32:30 UTC RTC time: Tue 2024-11-05 19:32:30 Time zone: Europe/Berlin (CET, +0100) System clock synchronized: yes NTP service: active RTC in local TZ: no *** Users and Groups *** User that called 'iob diag': faxel OPENHAB_HOME=/usr/share/openhab HOME=/home/faxel GROUPS=faxel cdrom floppy sudo audio dip video plugdev users netdev iobroker User that is running 'js-controller': iobroker HOME=/home/iobroker GROUPS=iobroker tty dialout audio video plugdev bluetooth *** DISPLAY-SERVER SETUP *** Display-Server: false Desktop: Terminal: *** MEMORY *** total used free shared buff/cache available Mem: 4.1G 902M 2.0G 3.5M 1.5G 3.2G Swap: 1.0G 0B 1.0G Total: 5.1G 902M 3.0G Active iob-Instances: 5 3898 M total memory 860 M used memory 439 M active memory 1358 M inactive memory 1879 M free memory 68 M buffer memory 1342 M swap cache 974 M total swap 0 M used swap 974 M free swap *** top - Table Of Processes *** top - 20:32:31 up 1:17, 3 users, load average: 0.46, 0.19, 0.20 Tasks: 135 total, 1 running, 134 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 25.0 sy, 0.0 ni, 75.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 3898.6 total, 1878.2 free, 862.1 used, 1410.6 buff/cache MiB Swap: 975.0 total, 975.0 free, 0.0 used. 3036.4 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION * openhab.service loaded failed failed openHAB - empowering the smart home LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. 1 loaded units listed. *** DMESG CRITICAL ERRORS *** 3 CRITICAL ERRORS DETECTED! Check 'sudo dmesg --level=emerg,alert,crit -T' for details *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 1.9G 0 1.9G 0% /dev tmpfs tmpfs 390M 944K 389M 1% /run /dev/sda1 ext4 58G 7.5G 48G 14% / tmpfs tmpfs 2.0G 0 2.0G 0% /dev/shm tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs tmpfs 390M 0 390M 0% /run/user/0 Messages concerning ext4 filesystem in dmesg: [Tue Nov 5 19:15:11 2024] EXT4-fs (sda1): mounted filesystem with ordered data mode. Quota mode: none. [Tue Nov 5 19:15:12 2024] EXT4-fs (sda1): re-mounted. Quota mode: none. Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/sda1 ext4 rw,relatime,errors=remount-ro Files in neuralgic directories: /var: 919M /var/ 394M /var/lib 245M /var/log 226M /var/log/journal/c78b9d697fbc44ff97e67909f99e0528 226M /var/log/journal Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. Archived and active journals take up 15.3M in the file system. /opt/iobroker/backups: 4.0K /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 71M /opt/iobroker/iobroker-data/ 60M /opt/iobroker/iobroker-data/files 31M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js 31M /opt/iobroker/iobroker-data/files/admin.admin/custom/static 31M /opt/iobroker/iobroker-data/files/admin.admin/custom The five largest files in iobroker-data are: 12M /opt/iobroker/iobroker-data/files/backitup.admin/static/js/main.bd24114f.js 10M /opt/iobroker/iobroker-data/objects.jsonl 7.0M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_mui_icons-material_esm_index_js.0c96b194.chunk.js.map 5.6M /opt/iobroker/iobroker-data/files/backitup.admin/custom/static/js/vendors-node_modules_file-saver_dist_FileSaver_min_js-node_modules_react-icons_di_index_mjs-n-f0ed96.6c33ff1f.chunk.js 5.5M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_d_ts-node_modules_io-2d33e4.42bb0640.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': No Devices found 'by-id' *** NodeJS-Installation *** /usr/bin/nodejs v20.18.0 /usr/bin/node v20.18.0 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.29.3 nodejs: Installed: 20.18.0-1nodesource1 Candidate: 20.18.0-1nodesource1 Version table: *** 20.18.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 20.17.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.16.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.15.1-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.15.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.14.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.13.1-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.13.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.12.2-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.12.1-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.12.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.11.1-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.11.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.10.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.9.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.8.1-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.8.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.7.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.6.1-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.6.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.5.1-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.5.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.4.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.3.1-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.3.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.2.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.1.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.0.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 18.19.0+dfsg-6~deb12u2 500 500 http://deb.debian.org/debian bookworm/main amd64 Packages 18.19.0+dfsg-6~deb12u1 500 500 http://security.debian.org/debian-security bookworm-security/main 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: jsonl Hosts: kaczmarek kaczmarek (version: 6.0.11, hostname: kaczmarek , alive, uptime: 3997) Core adapters versions js-controller: 6.0.11 admin: 7.1.5 javascript: "javascript" not found nodejs modules from github: 0 Adapter State + system.adapter.admin.0 : admin : kaczmarek - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.backitup.0 : backitup : kaczmarek - enabled + system.adapter.discovery.0 : discovery : kaczmarek - enabled + system.adapter.mqtt-client.0 : mqtt-client : kaczmarek - enabled, port: 1883 + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : kaczmarek - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.mqtt-client.0 : mqtt-client : kaczmarek - enabled, port: 1883 ioBroker-Repositories ┌─────────┬──────────┬─────────────────────────────────────────────────────────┬──────────────┐ │ (index) │ name │ url │ auto upgrade │ ├─────────┼──────────┼─────────────────────────────────────────────────────────┼──────────────┤ │ 0 │ 'stable' │ 'http://download.iobroker.net/sources-dist.json' │ false │ │ 1 │ 'beta' │ 'http://download.iobroker.net/sources-dist-latest.json' │ false │ └─────────┴──────────┴─────────────────────────────────────────────────────────┴──────────────┘ Active repo(s): stable Upgrade policy: none Installed ioBroker-Instances Used repository: stable Adapter "admin" : 7.1.5 , installed 7.1.5 Adapter "backitup" : 3.0.25 , installed 3.0.25 Adapter "discovery" : 5.0.0 , installed 5.0.0 Controller "js-controller": 6.0.11 , installed 6.0.11 Adapter "mqtt-client" : 2.0.0 , installed 2.0.0 Objects and States Please stand by - This may take a while Objects: 170 States: 126 *** 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 bookworm-backports InRelease Hit:4 http://security.debian.org/debian-security bookworm-security InRelease Hit:5 https://deb.nodesource.com/node_20.x nodistro InRelease Hit:6 https://openhab.jfrog.io/artifactory/openhab-linuxpkg stable 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 0.0.0.0:8089 0.0.0.0:* LISTEN 0 16881 512/node tcp 0 0 192.168.0.131:49152 0.0.0.0:* LISTEN 106 18614 607/gerbera tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN 105 690 522/mosquitto tcp 0 0 0.0.0.0:5355 0.0.0.0:* LISTEN 995 529 397/systemd-resolve tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 23211 3420/iobroker.js-co tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 23206 3420/iobroker.js-co tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 18122 521/sshd: /usr/sbin tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 0 339 1/init tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 0 18679 755/lighttpd tcp6 0 0 :::8081 :::* LISTEN 1001 26609 3662/io.admin.0 tcp6 0 0 :::1883 :::* LISTEN 105 691 522/mosquitto tcp6 0 0 :::5355 :::* LISTEN 995 537 397/systemd-resolve tcp6 0 0 fe80::f7d5:d386:e:49152 :::* LISTEN 106 18615 607/gerbera tcp6 0 0 :::22 :::* LISTEN 0 18133 521/sshd: /usr/sbin tcp6 0 0 :::111 :::* LISTEN 0 14596 1/init tcp6 0 0 :::80 :::* LISTEN 0 18678 755/lighttpd udp 0 0 0.0.0.0:1900 0.0.0.0:* 106 18619 607/gerbera udp 0 0 0.0.0.0:111 0.0.0.0:* 0 15446 1/init udp 0 0 127.0.0.1:58576 0.0.0.0:* 106 18616 607/gerbera udp 0 0 0.0.0.0:5353 0.0.0.0:* 102 16545 460/avahi-daemon: r udp 0 0 0.0.0.0:5355 0.0.0.0:* 995 528 397/systemd-resolve udp 0 0 0.0.0.0:44283 0.0.0.0:* 102 16547 460/avahi-daemon: r udp6 0 0 :::1900 :::* 106 18621 607/gerbera udp6 0 0 :::1900 :::* 106 18620 607/gerbera udp6 0 0 :::36957 :::* 102 16548 460/avahi-daemon: r udp6 0 0 :::111 :::* 0 15447 1/init udp6 0 0 fe80::f7d5:d386:e1c:546 :::* 0 18201 475/NetworkManager udp6 0 0 :::5353 :::* 102 16546 460/avahi-daemon: r udp6 0 0 :::5355 :::* 995 536 397/systemd-resolve udp6 0 0 :::30000 :::* 107 16640 505/minetestserver *** Log File - Last 25 Lines *** 2024-11-05 19:59:57.112 - info: discovery.0 (4153) Done discovering upnp devices. 49 packages received 2024-11-05 19:59:57.852 - info: discovery.0 (4153) Done discovering ping devices. 9 packages received 2024-11-05 19:59:57.879 - info: discovery.0 (4153) Found 15 addresses 2024-11-05 20:00:56.010 - error: discovery.0 (4153) uncaught exception: addMembership EADDRINUSE 2024-11-05 20:00:56.016 - error: discovery.0 (4153) Error: addMembership EADDRINUSE at Socket.addMembership (node:dgram:865:11) at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.discovery/lib/adapters/sma-em.js:94:20) at Socket.onListening (node:dgram:261:7) at Socket.emit (node:events:519:28) at startListening (node:dgram:184:10) at node:dgram:375:7 at process.processTicksAndRejections (node:internal/process/task_queues:83:21) 2024-11-05 20:00:56.018 - error: discovery.0 (4153) Exception-Code: EADDRINUSE: addMembership EADDRINUSE 2024-11-05 20:00:56.531 - info: discovery.0 (4153) terminating 2024-11-05 20:00:56.536 - warn: discovery.0 (4153) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-11-05 20:00:57.031 - info: discovery.0 (4153) terminating 2024-11-05 20:00:57.157 - error: host.kaczmarek instance system.adapter.discovery.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-11-05 20:00:57.162 - info: host.kaczmarek Restart adapter system.adapter.discovery.0 because enabled 2024-11-05 20:01:03.485 - info: admin.0 (3662) <== Disconnect system.user.admin from 2003:cb:5705:1500:3207:e648:b5a:191 admin 2024-11-05 20:01:03.534 - info: admin.0 (3662) ==> Connected system.user.admin from 2003:cb:5705:1500:3207:e648:b5a:191 2024-11-05 20:01:03.603 - info: admin.0 (3662) <== Disconnect system.user.admin from 2003:cb:5705:1500:3207:e648:b5a:191 admin 2024-11-05 20:01:04.089 - info: admin.0 (3662) ==> Connected system.user.admin from 2003:cb:5705:1500:3207:e648:b5a:191 2024-11-05 20:01:28.010 - info: host.kaczmarek instance system.adapter.discovery.0 in version "5.0.0" started with pid 4458 2024-11-05 20:01:32.239 - info: discovery.0 (4458) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system 2024-11-05 20:01:32.531 - info: discovery.0 (4458) starting. Version 5.0.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v20.18.0, js-controller: 6.0.11EADDRINUSE
-
@bornholm sagte in adapter.discovery Exception-Code: EADDRINUSE:
*** DMESG CRITICAL ERRORS ***
3 CRITICAL ERRORS DETECTED!
Check 'sudo dmesg --level=emerg,alert,crit -T' for detailsSchau dir diese Fehler genauer an.
-
@thomas-braun sagte in adapter.discovery Exception-Code: EADDRINUSE:
@bornholm sagte in adapter.discovery Exception-Code: EADDRINUSE:
*** DMESG CRITICAL ERRORS ***
3 CRITICAL ERRORS DETECTED!
Check 'sudo dmesg --level=emerg,alert,crit -T' for detailsSchau dir diese Fehler genauer an.
Danke für den Hinweis.
dmesg sagt da das Folgende:
[Di, 5. Nov 2024, 19:15:05] __common_interrupt: 1.55 No irq handler for vector [Di, 5. Nov 2024, 19:15:05] __common_interrupt: 2.55 No irq handler for vector [Di, 5. Nov 2024, 19:15:05] __common_interrupt: 3.55 No irq handler for vectorDiese Fehler kann man wohl ignorieren. Sie treten seit Jahren mit bestimmten AMD CPUs auf und haben laut diverser Netzfundstellen keine Auswirkungen.
-
Etwas mehr Logbuch:
2024-11-06 00:04:16.295 - error: discovery.0 (10404) Error: addMembership EADDRINUSE at Socket.addMembership (node:dgram:865:11) at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.discovery/lib/adapters/sma-em.js:94:20) at Socket.onListening (node:dgram:261:7) at Socket.emit (node:events:519:28) at startListening (node:dgram:184:10) at node:dgram:375:7 at process.processTicksAndRejections (node:internal/process/task_queues:83:21) 2024-11-06 00:04:16.297 - error: discovery.0 (10404) Exception-Code: EADDRINUSE: addMembership EADDRINUSEKann man den Loglevel eigentlich erhöhen um mehr zu sehen?
-
@bornholm sagte in adapter.discovery Exception-Code: EADDRINUSE:
Kann man den Loglevel eigentlich erhöhen um mehr zu sehen?
Ja, auf debug und als höchste Stufe noch auf silly.
Da scheint es aber bei sma-em zu haken. -
@thomas-braun sagte in adapter.discovery Exception-Code: EADDRINUSE:
@bornholm sagte in adapter.discovery Exception-Code: EADDRINUSE:
Kann man den Loglevel eigentlich erhöhen um mehr zu sehen?
Ja, auf debug und als höchste Stufe noch auf silly.
Wo denn ?
Da scheint es aber bei sma-em zu haken.
In sma-em.js:94 scheitert dann wohl ein client.addMembership
// Bind socket to the multicast address on all ipv4 devices except localhost client.bind(MULTICAST_PORT, () => { const addresses = tools.getIP4addresses(); for (const dev of addresses) { debug && options.log.debug(`Listen via UDP on Device ${dev.name} with IP ${dev.ip} on Port ${MULTICAST_PORT} for Multicast IP ${MULTICAST_IP}`); client.addMembership(MULTICAST_IP, dev.ip);Und bei "multicast" dachte ich: komisch, falsches Netzwerk? Und schaute in die Networkmanager Konfiguration, da schau her:
[ipv4] address1=192.168.0.131/32,192.168.0.10 address2=192.168.0.131/24Keine Ahnung wie der Unsinn da rein kommt, die APU Box hatte ich für verschiedenen Basteleien verwendet. War wahrscheinlich mal wieder zu spät
Nachdem das /24 richtig drin steht ist der discovery Fehler verschwunden.
