NEWS
Alexa Adapter startet nicht adäquat
Error/Bug
17
Beiträge
6
Kommentatoren
1.3k
Aufrufe
4
Watching
-
Hey, leider funktioniert der Alexa-Adapter bei mir schon seit Wochen/Monaten nicht mehr zuverlässig. Wenn ich die Hardware neu starte oder der morgendliche Neustart vom ioBroker ansteht, startet der Alexa Adapter leider nicht mit. Weiter unten stehen die Logeinträge nach Neustart.
Wenn ich den Adapter dann manuell neu starte geht er dann auch wieder. Ab und an reicht das auch nicht, so dass ich ihn pausieren muss und dann neustarte, was dann aber auch wieder zum Erfolg führt. Laut Log scheint die Authentikation nicht zu funktionieren. Wieso geht es dann später manuell?!
Vielleicht hat ja einer eine Idee.- Adaptername: Alexa-Adapter
- Adapterversion: v3.26.5
- js-controller Version: 7.0.6
- Admin Version: v7.1.5
- Hardwaresystem: ThinkCentre M910
- Arbeitsspeicher: 8 GB
- Festplattenart: NVME
iob diag:
Script v.2024-10-19 *** BASE SYSTEM *** Static hostname: smarthome Icon name: computer-vm Chassis: vm 🖴 Virtualization: kvm Operating System: Debian GNU/Linux 12 (bookworm) Kernel: Linux 6.1.0-28-amd64 Architecture: x86-64 Hardware Vendor: QEMU Hardware Model: Standard PC _i440FX + PIIX, 1996_ Firmware Version: rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org OS is similar to: model name : QEMU Virtual CPU version 2.5+ Docker : false Virtualization : kvm Kernel : x86_64 Userland : 64 bit Systemuptime and Load: 11:59:08 up 6 min, 2 users, load average: 0.28, 0.38, 0.19 CPU threads: 4 *** LIFE CYCLE STATUS *** Operating System is the current Debian stable version codenamed 'bookworm'! *** TIME AND TIMEZONES *** Local time: Sun 2024-12-29 11:59:08 CET Universal time: Sun 2024-12-29 10:59:08 UTC RTC time: Sun 2024-12-29 10:59:08 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': Name HOME=/home/Name GROUPS=Name adm sudo 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: tty *** MEMORY *** total used free shared buff/cache available Mem: 6.2G 2.1G 3.9G 602K 428M 4.1G Swap: 1.0G 0B 1.0G Total: 7.2G 2.1G 4.9G Active iob-Instances: 28 5924 M total memory 2008 M used memory 197 M active memory 1775 M inactive memory 3738 M free memory 48 M buffer memory 359 M swap cache 974 M total swap 0 M used swap 974 M free swap *** top - Table Of Processes *** top - 11:59:08 up 6 min, 2 users, load average: 0.28, 0.38, 0.19 Tasks: 137 total, 1 running, 136 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 0.0 sy, 0.0 ni,100.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 5924.7 total, 3738.2 free, 2008.8 used, 408.8 buff/cache MiB Swap: 975.0 total, 975.0 free, 0.0 used. 3915.9 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 2.9G 0 2.9G 0% /dev tmpfs tmpfs 593M 588K 592M 1% /run /dev/sda1 ext4 31G 7.9G 21G 28% / tmpfs tmpfs 2.9G 0 2.9G 0% /dev/shm tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs tmpfs 593M 0 593M 0% /run/user/1002 Messages concerning ext4 filesystem in dmesg: [Sun Dec 29 11:52:56 2024] EXT4-fs (sda1): mounted filesystem with ordered data mode. Quota mode: none. [Sun Dec 29 11:52:56 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: 792M /var/ 310M /var/log 305M /var/cache 298M /var/cache/apt 295M /var/log/journal/f7c9af7eca8b4fd0b22b92ca0066d615 Archived and active journals take up 294.0M in the file system. /opt/iobroker/backups: 539M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 1.2G /opt/iobroker/iobroker-data/ 887M /opt/iobroker/iobroker-data/files 617M /opt/iobroker/iobroker-data/files/javascript.admin 560M /opt/iobroker/iobroker-data/files/javascript.admin/static 558M /opt/iobroker/iobroker-data/files/javascript.admin/static/js The five largest files in iobroker-data are: 38M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.d3d286bd.js.map 31M /opt/iobroker/iobroker-data/objects.jsonl 27M /opt/iobroker/iobroker-data/files/tankerkoenig.admin/build/index.js.map 24M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.135279a0.js.map 19M /opt/iobroker/iobroker-data/files/text2command.admin/static/js/main.02fc3820.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-Texas_Instruments_CC2538_USB_CDC-if00 HINT: Your zigbee.0 COM-Port is NOT matching 'by-id'. Please check your setting: /dev/ttyACM0 *** 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 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: smarthome smarthome (version: 7.0.6, hostname: smarthome , alive, uptime: 362) Core adapters versions js-controller: 7.0.6 admin: 7.1.5 javascript: 8.8.3 nodejs modules from github: 1 +-- iobroker.iosapp@1.0.3 (git+ssh://git@github.com/DNAngelX/ioBroker.iosapp.git#2426c0437a01144218cbd0d79228494bac41b9c0) Adapter State + system.adapter.admin.0 : admin : smarthome - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.alexa2.0 : alexa2 : smarthome - enabled + system.adapter.awtrix-light.0 : awtrix-light : smarthome - enabled + system.adapter.backitup.0 : backitup : smarthome - enabled + system.adapter.ble.0 : ble : smarthome - enabled system.adapter.cloud.0 : cloud : smarthome - disabled system.adapter.daswetter.0 : daswetter : smarthome - enabled system.adapter.dwd.0 : dwd : smarthome - enabled + system.adapter.fullybrowser.0 : fullybrowser : smarthome - enabled + system.adapter.ham.0 : ham : smarthome - enabled + system.adapter.history.0 : history : smarthome - enabled system.adapter.ical.0 : ical : smarthome - enabled + system.adapter.influxdb.0 : influxdb : smarthome - enabled, port: 8086 + system.adapter.iosapp.0 : iosapp : smarthome - enabled + system.adapter.iot.0 : iot : smarthome - enabled + system.adapter.jarvis.0 : jarvis : smarthome - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.javascript.0 : javascript : smarthome - enabled + system.adapter.lgtv.0 : lgtv : smarthome - enabled system.adapter.linux-control.0 : linux-control : smarthome - disabled + system.adapter.mqtt.0 : mqtt : smarthome - enabled, port: 1885, bind: 0.0.0.0 + system.adapter.proxmox.0 : proxmox : smarthome - enabled, port: 8006 + system.adapter.shelly.0 : shelly : smarthome - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.simple-api.0 : simple-api : smarthome - enabled, port: 8087, bind: 0.0.0.0, run as: admin system.adapter.snmp.0 : snmp : smarthome - disabled + system.adapter.sonoff.0 : sonoff : smarthome - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.spotify-premium.0 : spotify-premium : smarthome - enabled + system.adapter.tankerkoenig.0 : tankerkoenig : smarthome - enabled + system.adapter.telegram.0 : telegram : smarthome - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.text2command.0 : text2command : smarthome - enabled + system.adapter.tr-064.0 : tr-064 : smarthome - enabled + system.adapter.trashschedule.0 : trashschedule : smarthome - enabled + system.adapter.web.0 : web : smarthome - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.wled.0 : wled : smarthome - enabled + system.adapter.zigbee.0 : zigbee : smarthome - enabled, port: /dev/ttyACM0 + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : smarthome - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.influxdb.0 : influxdb : smarthome - enabled, port: 8086 + system.adapter.jarvis.0 : jarvis : smarthome - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.mqtt.0 : mqtt : smarthome - enabled, port: 1885, bind: 0.0.0.0 + system.adapter.proxmox.0 : proxmox : smarthome - enabled, port: 8006 + system.adapter.shelly.0 : shelly : smarthome - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.simple-api.0 : simple-api : smarthome - enabled, port: 8087, bind: 0.0.0.0, run as: admin + system.adapter.sonoff.0 : sonoff : smarthome - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.telegram.0 : telegram : smarthome - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.web.0 : web : smarthome - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.zigbee.0 : zigbee : smarthome - enabled, port: /dev/ttyACM0 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 "alexa2" : 3.26.5 , installed 3.26.5 Adapter "awtrix-light" : 1.4.1 , installed 1.4.1 Adapter "backitup" : 3.0.25 , installed 3.0.25 Adapter "ble" : 0.14.0 , installed 0.14.0 Adapter "cloud" : 5.0.1 , installed 5.0.1 Adapter "daswetter" : 3.2.2 , installed 3.2.2 Adapter "dwd" : 2.8.5 , installed 2.8.5 Adapter "fullybrowser" : 3.0.12 , installed 3.0.12 Adapter "ham" : 5.3.1 , installed 5.3.1 Adapter "history" : 3.0.1 , installed 3.0.1 Adapter "ical" : 1.16.1 , installed 1.16.1 Adapter "influxdb" : 4.0.2 , installed 4.0.2 Adapter "iot" : 3.3.0 , installed 3.3.0 Adapter "jarvis" : 3.1.8 , installed 3.1.8 Adapter "javascript" : 8.8.3 , installed 8.8.3 Controller "js-controller": 7.0.6 , installed 7.0.6 Adapter "lgtv" : 2.3.1 , installed 2.3.1 Adapter "linux-control": 1.1.5 , installed 1.1.5 Adapter "mqtt" : 6.1.2 , installed 6.1.2 Adapter "proxmox" : 2.3.0 , installed 2.3.0 Adapter "shelly" : 8.2.1 , installed 8.2.1 Adapter "simple-api" : 2.8.0 , installed 2.8.0 Adapter "snmp" : 3.2.0 , installed 3.2.0 Adapter "socketio" : 6.7.1 , installed 6.7.1 Adapter "sonoff" : 3.1.2 , installed 3.1.2 Adapter "spotify-premium": 1.5.0 , installed 1.5.0 Adapter "tankerkoenig" : 3.4.0 , installed 3.4.0 Adapter "telegram" : 3.9.0 , installed 3.9.0 Adapter "text2command" : 3.0.3 , installed 3.0.3 Adapter "tr-064" : 4.3.0 , installed 4.3.0 Adapter "trashschedule": 3.3.0 , installed 3.3.0 Adapter "vis" : 1.5.6 , installed 1.5.6 Adapter "web" : 6.2.5 , installed 6.2.5 Adapter "wled" : 0.7.2 , installed 0.7.2 Adapter "ws" : 2.6.2 , installed 2.6.2 Adapter "zigbee" : 1.10.3 , installed 1.9.5 [Updatable] Objects and States Please stand by - This may take a while Objects: 9561 States: 8344 *** OS-Repositories and Updates *** Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://security.debian.org/debian-security bookworm-security InRelease Hit:3 http://deb.debian.org/debian bookworm-updates InRelease Hit:4 https://deb.nodesource.com/node_20.x nodistro InRelease Reading package lists... Pending Updates: 0 *** Listening Ports *** Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN 1001 18719 944/io.sonoff.0 tcp 0 0 0.0.0.0:1885 0.0.0.0:* LISTEN 1001 16803 871/io.mqtt.0 tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 16534 548/iobroker.js-con tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 17764 548/iobroker.js-con tcp 0 0 0.0.0.0:8400 0.0.0.0:* LISTEN 1001 18891 1117/io.jarvis.0 tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 17747 561/sshd: /usr/sbin tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 0 13463 1/init tcp6 0 0 :::9192 :::* LISTEN 1001 19599 1222/io.iosapp.0 tcp6 0 0 :::22 :::* LISTEN 0 17749 561/sshd: /usr/sbin tcp6 0 0 :::111 :::* LISTEN 0 13279 1/init tcp6 0 0 :::8082 :::* LISTEN 1001 19552 1192/io.web.0 tcp6 0 0 :::8081 :::* LISTEN 1001 13881 588/io.admin.0 tcp6 0 0 :::8087 :::* LISTEN 1001 18902 1132/io.simple-api. udp 0 0 0.0.0.0:5353 0.0.0.0:* 1001 19566 1207/io.wled.0 udp 0 0 192.168.178.101:5353 0.0.0.0:* 1001 16923 974/io.tr-064.0 udp 0 0 0.0.0.0:5683 0.0.0.0:* 1001 16843 916/io.shelly.0 udp 0 0 0.0.0.0:68 0.0.0.0:* 0 1022 511/dhclient udp 0 0 0.0.0.0:111 0.0.0.0:* 0 15090 1/init udp6 0 0 :::111 :::* 0 13464 1/init *** Log File - Last 25 Lines *** 2024-12-29 11:54:50.334 - info: trashschedule.0 (1177) [ical] configured ical preview is 32 days (until 30.01.2025) - increase this value to find more events in the future 2024-12-29 11:54:51.048 - info: influxdb.0 (673) Connecting http://192.168.178.104:8086/ ... 2024-12-29 11:54:51.048 - info: influxdb.0 (673) Influx DB Version used: 2.x 2024-12-29 11:54:51.063 - info: influxdb.0 (673) Applying retention policy for iobroker to 31536000 seconds. Shard Group Duration (calculated): 604800 seconds 2024-12-29 11:54:51.088 - info: influxdb.0 (673) Connected! 2024-12-29 11:54:53.388 - info: host.smarthome instance system.adapter.web.0 in version "6.2.5" started with pid 1192 2024-12-29 11:54:54.222 - info: web.0 (1192) starting. Version 6.2.5 in /opt/iobroker/node_modules/iobroker.web, node: v20.18.1, js-controller: 7.0.6 2024-12-29 11:54:54.342 - info: web.0 (1192) socket.io server listening on port 8082 2024-12-29 11:54:54.349 - info: web.0 (1192) http server listening on port 8082 2024-12-29 11:54:57.381 - info: host.smarthome instance system.adapter.wled.0 in version "0.7.2" started with pid 1207 2024-12-29 11:55:01.382 - info: host.smarthome instance system.adapter.iosapp.0 in version "1.0.3" (non-npm: DNAngelX/ioBroker.iosapp#2426c0437a01144218cbd0d79228494bac41b9c0) started with pid 1222 2024-12-29 11:55:02.123 - info: iosapp.0 (1222) starting. Version 1.0.3 (non-npm: DNAngelX/ioBroker.iosapp#2426c0437a01144218cbd0d79228494bac41b9c0) in /opt/iobroker/node_modules/iobroker.iosapp, node: v20.18.1, js-controller: 7.0.6 2024-12-29 11:55:02.134 - info: iosapp.0 (1222) WebSocket server listening on port 9192 2024-12-29 11:55:18.008 - info: host.smarthome instance system.adapter.dwd.0 in version "2.8.5" started with pid 1237 2024-12-29 11:55:18.204 - error: daswetter.0 (1057) force terminate 2024-12-29 11:55:18.205 - warn: daswetter.0 (1057) Terminated (UNKNOWN_ERROR): Without reason 2024-12-29 11:55:18.711 - info: daswetter.0 (1057) cleaned everything up... 2024-12-29 11:55:18.748 - error: host.smarthome instance system.adapter.daswetter.0 terminated with code 15 (UNKNOWN_ERROR) 2024-12-29 11:55:18.875 - info: dwd.0 (1237) starting. Version 2.8.5 in /opt/iobroker/node_modules/iobroker.dwd, node: v20.18.1, js-controller: 7.0.6 2024-12-29 11:55:19.239 - info: dwd.0 (1237) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2024-12-29 11:55:19.755 - info: host.smarthome instance system.adapter.dwd.0 having pid 1237 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2024-12-29 11:56:11.010 - info: influxdb.0 (673) Store 33 buffered influxDB history points 2024-12-29 11:56:29.370 - info: admin.0 (588) ==> Connected system.user.admin from ::ffff:192.168.178.63 2024-12-29 11:56:39.435 - info: admin.0 (588) <== Disconnect system.user.admin from ::ffff:192.168.178.63 2024-12-29 11:59:11.013 - info: influxdb.0 (673) Store 14 buffered influxDB history pointsalexa2.0 2024-12-29 11:53:55.969 info Terminated (ADAPTER_REQUESTED_TERMINATION): without reason alexa2.0 2024-12-29 11:53:55.969 debug Plugin sentry destroyed alexa2.0 2024-12-29 11:53:54.967 error Adapter seems to have issues and crashed three times in a row. Disabling!! Please start again and check logs. alexa2.0 2024-12-29 11:53:54.960 info Starting Alexa2 adapter ... it can take several minutes to initialize all data. Please be patient! A done message is logged. alexa2.0 2024-12-29 11:53:54.941 info starting. Version 3.26.5 in /opt/iobroker/node_modules/iobroker.alexa2, node: v20.18.1, js-controller: 7.0.6 alexa2.0 2024-12-29 11:53:54.795 debug Plugin sentry Initialize Plugin (enabled=true) alexa2.0 2024-12-29 11:53:52.244 info Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason alexa2.0 2024-12-29 11:53:52.244 debug Plugin sentry destroyed alexa2.0 2024-12-29 11:53:52.243 error Error: Error while checking Authentication: Error: getaddrinfo EAI_AGAIN alexa.amazon.de alexa2.0 2024-12-29 11:53:52.243 debug Error from Alexa init: Error while checking Authentication: Error: getaddrinfo EAI_AGAIN alexa.amazon.de alexa2.0 2024-12-29 11:53:52.243 debug Alexa-Remote: Response: Error: Error: getaddrinfo EAI_AGAIN alexa.amazon.de alexa2.0 2024-12-29 11:53:47.191 debug Alexa-Remote: Sending Request with {"host":"alexa.amazon.de","path":"/api/bootstrap?version=0","method":"GET","timeout":10000,"headers":{"Accept-Language":"de-DE"}} alexa2.0 2024-12-29 11:53:47.191 debug Alexa-Remote: cookie was provided alexa2.0 2024-12-29 11:53:47.189 debug Alexa-Remote: Use as Base-URL: alexa.amazon.de alexa2.0 2024-12-29 11:53:47.189 debug Alexa-Remote: Use as Login-Amazon-URL: amazon.de alexa2.0 2024-12-29 11:53:47.189 debug Alexa-Remote: Use as API User-Agent Postfix: iBrokAlxa2/3.26.5 alexa2.0 2024-12-29 11:53:47.189 debug Alexa-Remote: Use as User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 alexa2.0 2024-12-29 11:53:47.188 debug Update Devices Configuration Interval: 3604s alexa2.0 2024-12-29 11:53:47.188 debug Update Device State Interval: 315s alexa2.0 2024-12-29 11:53:47.188 debug Update History Interval: 300s alexa2.0 2024-12-29 11:53:47.187 info Proxy IP not set, use first network interface (192.168.178.101) instead alexa2.0 2024-12-29 11:53:47.186 info Starting Alexa2 adapter ... it can take several minutes to initialize all data. Please be patient! A done message is logged. alexa2.0 2024-12-29 11:53:47.163 info starting. Version 3.26.5 in /opt/iobroker/node_modules/iobroker.alexa2, node: v20.18.1, js-controller: 7.0.6 alexa2.0 2024-12-29 11:53:46.985 debug Plugin sentry Initialize Plugin (enabled=true) alexa2.0 2024-12-29 11:53:44.390 debug Alexa-Remote: Response: Error: Error: getaddrinfo EAI_AGAIN alexa.amazon.de alexa2.0 2024-12-29 11:53:44.381 info Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason alexa2.0 2024-12-29 11:53:44.381 debug Plugin sentry destroyed alexa2.0 2024-12-29 11:53:44.381 error Error: Error while checking Authentication: Error: Timeout alexa2.0 2024-12-29 11:53:44.381 debug Error from Alexa init: Error while checking Authentication: Error: Timeout alexa2.0 2024-12-29 11:53:44.380 debug Alexa-Remote: Response: Timeout alexa2.0 2024-12-29 11:53:34.335 debug Alexa-Remote: Sending Request with {"host":"alexa.amazon.de","path":"/api/bootstrap?version=0","method":"GET","timeout":10000,"headers":{"Accept-Language":"de-DE"}} alexa2.0 2024-12-29 11:53:34.334 debug Alexa-Remote: cookie was provided alexa2.0 2024-12-29 11:53:34.333 debug Alexa-Remote: Use as Base-URL: alexa.amazon.de alexa2.0 2024-12-29 11:53:34.333 debug Alexa-Remote: Use as Login-Amazon-URL: amazon.de alexa2.0 2024-12-29 11:53:34.333 debug Alexa-Remote: Use as API User-Agent Postfix: iBrokAlxa2/3.26.5 alexa2.0 2024-12-29 11:53:34.333 debug Alexa-Remote: Use as User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 alexa2.0 2024-12-29 11:53:34.332 debug Update Devices Configuration Interval: 3606s alexa2.0 2024-12-29 11:53:34.332 debug Update Device State Interval: 309s alexa2.0 2024-12-29 11:53:34.332 debug Update History Interval: 300s alexa2.0 2024-12-29 11:53:34.331 info Proxy IP not set, use first network interface (192.168.178.101) instead alexa2.0 2024-12-29 11:53:34.330 info Starting Alexa2 adapter ... it can take several minutes to initialize all data. Please be patient! A done message is logged. alexa2.0 2024-12-29 11:53:34.304 info starting. Version 3.26.5 in /opt/iobroker/node_modules/iobroker.alexa2, node: v20.18.1, js-controller: 7.0.6 alexa2.0 2024-12-29 11:53:34.132 debug Plugin sentry Initialize Plugin (enabled=true) alexa2.0 2024-12-29 11:53:31.335 info Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason alexa2.0 2024-12-29 11:53:31.335 debug Plugin sentry destroyed alexa2.0 2024-12-29 11:53:31.334 error Error: Error while checking Authentication: Error: getaddrinfo EAI_AGAIN alexa.amazon.de alexa2.0 2024-12-29 11:53:31.334 debug Error from Alexa init: Error while checking Authentication: Error: getaddrinfo EAI_AGAIN alexa.amazon.de alexa2.0 2024-12-29 11:53:31.334 debug Alexa-Remote: Response: Error: Error: getaddrinfo EAI_AGAIN alexa.amazon.de alexa2.0 2024-12-29 11:53:26.289 debug Alexa-Remote: Sending Request with {"host":"alexa.amazon.de","path":"/api/bootstrap?version=0","method":"GET","timeout":10000,"headers":{"Accept-Language":"de-DE"}} alexa2.0 2024-12-29 11:53:26.288 debug Alexa-Remote: cookie was provided alexa2.0 2024-12-29 11:53:26.288 debug Alexa-Remote: Use as Base-URL: alexa.amazon.de alexa2.0 2024-12-29 11:53:26.287 debug Alexa-Remote: Use as Login-Amazon-URL: amazon.de alexa2.0 2024-12-29 11:53:26.287 debug Alexa-Remote: Use as API User-Agent Postfix: iBrokAlxa2/3.26.5 alexa2.0 2024-12-29 11:53:26.287 debug Alexa-Remote: Use as User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 alexa2.0 2024-12-29 11:53:26.287 debug Update Devices Configuration Interval: 3603s alexa2.0 2024-12-29 11:53:26.286 debug Update Device State Interval: 301s alexa2.0 2024-12-29 11:53:26.286 debug Update History Interval: 300s alexa2.0 2024-12-29 11:53:26.286 info Proxy IP not set, use first network interface (192.168.178.101) instead alexa2.0 2024-12-29 11:53:26.285 info Starting Alexa2 adapter ... it can take several minutes to initialize all data. Please be patient! A done message is logged. alexa2.0 2024-12-29 11:53:26.265 info starting. Version 3.26.5 in /opt/iobroker/node_modules/iobroker.alexa2, node: v20.18.1, js-controller: 7.0.6 alexa2.0 2024-12-29 11:53:26.063 debug Plugin sentry Initialize Plugin (enabled=true) alexa2.0 2024-12-29 11:51:32.077 info terminating alexa2.0 2024-12-29 11:51:31.700 info Got terminate signal TERMINATE_YOURSELF alexa2.0 2024-12-29 11:51:31.694 info Terminated (NO_ERROR): Without reason alexa2.0 2024-12-29 11:51:31.694 debug Plugin sentry destroyed alexa2.0 2024-12-29 11:51:31.692 info terminating alexa2.0 2024-12-29 11:51:18.701 debug Message: {"command":"getStatusInfo","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":18,"ack":false,"time":1735469478684},"_id":51760385}@smarthome2020 sagte in Alexa Adapter startet nicht adäquat:
Error: getaddrinfo EAI_AGAIN
deutet auf ein Problem mit der Namensauflösung hin.
ist der DNS erreichbar? -
@smarthome2020 sagte in Alexa Adapter startet nicht adäquat:
Error: getaddrinfo EAI_AGAIN
deutet auf ein Problem mit der Namensauflösung hin.
ist der DNS erreichbar?@homoran sagte in Alexa Adapter startet nicht adäquat:
@smarthome2020 sagte in Alexa Adapter startet nicht adäquat:
Error: getaddrinfo EAI_AGAIN
deutet auf ein Problem mit der Namensauflösung hin.
ist der DNS erreichbar?Das kann es sein. Nutze den ioBroker auf einem Proxmox-System. Startet die Hardware neu, dann auch PiHole, was installiert ist. Kann sein, dass PiHole da im Wege steht. Das Problem müssten dann ja mehrere Leute haben?!
-
@homoran sagte in Alexa Adapter startet nicht adäquat:
@smarthome2020 sagte in Alexa Adapter startet nicht adäquat:
Error: getaddrinfo EAI_AGAIN
deutet auf ein Problem mit der Namensauflösung hin.
ist der DNS erreichbar?Das kann es sein. Nutze den ioBroker auf einem Proxmox-System. Startet die Hardware neu, dann auch PiHole, was installiert ist. Kann sein, dass PiHole da im Wege steht. Das Problem müssten dann ja mehrere Leute haben?!
@smarthome2020 sagte in Alexa Adapter startet nicht adäquat:
Das Problem müssten dann ja mehrere Leute haben?!
aber nur, wenn jemand die selbe Konstellation hat.
-
@smarthome2020 sagte in Alexa Adapter startet nicht adäquat:
Das Problem müssten dann ja mehrere Leute haben?!
aber nur, wenn jemand die selbe Konstellation hat.
Was kann ich dagegen machen? Hast du ne Idee? Sonst müsste ich PiHole aus dem System werfen. Weiß ehrlich gesagt eh nicht, ob das so viel taugt. Blockt meiner Frau jedenfalls die Google-Werbeangebote. Hab leider noch keine Statistik, ob es auch finanziell was gebracht hat :grin:
-
Was kann ich dagegen machen? Hast du ne Idee? Sonst müsste ich PiHole aus dem System werfen. Weiß ehrlich gesagt eh nicht, ob das so viel taugt. Blockt meiner Frau jedenfalls die Google-Werbeangebote. Hab leider noch keine Statistik, ob es auch finanziell was gebracht hat :grin:
@smarthome2020 sagte in Alexa Adapter startet nicht adäquat:
ich PiHole aus dem System werfen. Weiß ehrlich gesagt eh nicht,
dann schaue die das Log in der GUI von PiHole an und konfiguriere entsprechend (Whitelist).
Ro75.
-
Was kann ich dagegen machen? Hast du ne Idee? Sonst müsste ich PiHole aus dem System werfen. Weiß ehrlich gesagt eh nicht, ob das so viel taugt. Blockt meiner Frau jedenfalls die Google-Werbeangebote. Hab leider noch keine Statistik, ob es auch finanziell was gebracht hat :grin:
@smarthome2020 Stell halt in proxmox ein, dass zuerst Pi-hole startet und dann mit einer gewissen Verzögerung iobroker und der Rest.
BTW, warum „der morgendliche Neustart von iobroker“? Bei mir läuft der, inklusve aller Proxmox-Hosts und darauf laufender LXC und VMs 24/7.Gruss, Jürgen
-
Danke für die Ratschläge. Ich werde sie morgen versuchen umzusetzen. Ich hoffe es gelingt mir 😂
-
Danke für die Ratschläge. Ich werde sie morgen versuchen umzusetzen. Ich hoffe es gelingt mir 😂
Womit Du nicht beantwortet hast, wieso Du den Iobroker jeden Morgen neu startest?!
-
Danke für die Ratschläge. Ich werde sie morgen versuchen umzusetzen. Ich hoffe es gelingt mir 😂
@haselchen sagte in Alexa Adapter startet nicht adäquat:
Womit Du nicht beantwortet hast, wieso Du den Iobroker jeden Morgen neu startest?!
Eben! So ein Server läuft in der Regel 24/7.
Sollte der Neustart aufgrund eines (wie auch immer gearteten) anderen Problems "nötig" sein, sollte zuerst versucht werden, das zu lösen. -
Der ioBroker startet sich selber um 05:00 Uhr. Dauert nur paar Sekunden, ist in den Einstellungen vom ioBroker damals mal vorgenommen worden und besteht seitdem. Das sollte ja kein primären Problem sein oder seht ihr da eines?
-
Also irgendwas stimmt dennoch nicht.
Habe PiHole nun mal ausgelassen. Wenn ich nun die ioBroker VM neu starte, dann startet der Alexa Adapter dennoch nicht. Wenn ich ihn dann aber manuell neu starte unter "Instanzen", dann geht es ohne Probleme.alexa2.0 2024-12-30 18:45:39.472 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason alexa2.0 2024-12-30 18:45:39.472 debug Plugin sentry destroyed alexa2.0 2024-12-30 18:45:38.471 error Adapter seems to have issues and crashed three times in a row. Disabling!! Please start again and check logs. alexa2.0 2024-12-30 18:45:38.463 info Starting Alexa2 adapter ... it can take several minutes to initialize all data. Please be patient! A done message is logged. alexa2.0 2024-12-30 18:45:38.442 info starting. Version 3.26.5 in /opt/iobroker/node_modules/iobroker.alexa2, node: v20.18.1, js-controller: 7.0.6 alexa2.0 2024-12-30 18:45:38.289 debug Plugin sentry Initialize Plugin (enabled=true) alexa2.0 2024-12-30 18:45:38.272 debug States connected to redis: 127.0.0.1:9000 alexa2.0 2024-12-30 18:45:38.217 debug States create User PubSub Client alexa2.0 2024-12-30 18:45:38.216 debug States create System PubSub Client alexa2.0 2024-12-30 18:45:38.210 debug Redis States: Use Redis connection: 127.0.0.1:9000 alexa2.0 2024-12-30 18:45:38.196 debug Objects connected to redis: 127.0.0.1:9001 alexa2.0 2024-12-30 18:45:38.193 debug Objects client initialize lua scripts alexa2.0 2024-12-30 18:45:38.173 debug Objects create User PubSub Client alexa2.0 2024-12-30 18:45:38.172 debug Objects create System PubSub Client alexa2.0 2024-12-30 18:45:38.172 debug Objects client ready ... initialize now alexa2.0 2024-12-30 18:45:38.157 debug Redis Objects: Use Redis connection: 127.0.0.1:9001 alexa2.0 2024-12-30 18:45:36.069 debug Alexa-Remote: Response: Error: Error: getaddrinfo EAI_AGAIN alexa.amazon.de alexa2.0 2024-12-30 18:45:35.758 info Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason alexa2.0 2024-12-30 18:45:35.758 debug Plugin sentry destroyed alexa2.0 2024-12-30 18:45:35.757 error Error: Error while checking Authentication: Error: Timeout alexa2.0 2024-12-30 18:45:35.757 debug Error from Alexa init: Error while checking Authentication: Error: Timeout alexa2.0 2024-12-30 18:45:35.756 debug Alexa-Remote: Response: Timeout alexa2.0 2024-12-30 18:45:25.715 debug Alexa-Remote: Sending Request with {"host":"alexa.amazon.de","path":"/api/bootstrap?version=0","method":"GET","timeout":10000,"headers":{"Accept-Language":"de-DE"}} alexa2.0 2024-12-30 18:45:25.715 debug Alexa-Remote: cookie was provided alexa2.0 2024-12-30 18:45:25.714 debug Alexa-Remote: Use as Base-URL: alexa.amazon.de alexa2.0 2024-12-30 18:45:25.713 debug Alexa-Remote: Use as Login-Amazon-URL: amazon.de alexa2.0 2024-12-30 18:45:25.713 debug Alexa-Remote: Use as API User-Agent Postfix: iBrokAlxa2/3.26.5 alexa2.0 2024-12-30 18:45:25.713 debug Alexa-Remote: Use as User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 alexa2.0 2024-12-30 18:45:25.713 debug Update Devices Configuration Interval: 3602s alexa2.0 2024-12-30 18:45:25.713 debug Update Device State Interval: 314s alexa2.0 2024-12-30 18:45:25.712 debug Update History Interval: 300s alexa2.0 2024-12-30 18:45:25.712 info Proxy IP not set, use first network interface (192.168.178.101) instead alexa2.0 2024-12-30 18:45:25.704 info Starting Alexa2 adapter ... it can take several minutes to initialize all data. Please be patient! A done message is logged. alexa2.0 2024-12-30 18:45:25.686 info starting. Version 3.26.5 in /opt/iobroker/node_modules/iobroker.alexa2, node: v20.18.1, js-controller: 7.0.6 alexa2.0 2024-12-30 18:45:25.542 debug Plugin sentry Initialize Plugin (enabled=true) alexa2.0 2024-12-30 18:45:25.524 debug States connected to redis: 127.0.0.1:9000 alexa2.0 2024-12-30 18:45:25.469 debug States create User PubSub Client alexa2.0 2024-12-30 18:45:25.468 debug States create System PubSub Client alexa2.0 2024-12-30 18:45:25.461 debug Redis States: Use Redis connection: 127.0.0.1:9000 alexa2.0 2024-12-30 18:45:25.446 debug Objects connected to redis: 127.0.0.1:9001 alexa2.0 2024-12-30 18:45:25.443 debug Objects client initialize lua scripts alexa2.0 2024-12-30 18:45:25.423 debug Objects create User PubSub Client alexa2.0 2024-12-30 18:45:25.422 debug Objects create System PubSub Client alexa2.0 2024-12-30 18:45:25.421 debug Objects client ready ... initialize now alexa2.0 2024-12-30 18:45:25.405 debug Redis Objects: Use Redis connection: 127.0.0.1:9001 -
Der ioBroker startet sich selber um 05:00 Uhr. Dauert nur paar Sekunden, ist in den Einstellungen vom ioBroker damals mal vorgenommen worden und besteht seitdem. Das sollte ja kein primären Problem sein oder seht ihr da eines?
Von Haus aus ist da Dein kein Cronjob festgelegt , also WARUM startest Du Deine VM jeden Morgen neu?
-
Von Haus aus ist da Dein kein Cronjob festgelegt , also WARUM startest Du Deine VM jeden Morgen neu?
Die VM startet nicht neu. Der ioBroker stoppt und startet neu.
Jedenfalls bekomme ich morgens um 5 Uhr ca ne Nachricht bei Telegram . -
Die VM startet nicht neu. Der ioBroker stoppt und startet neu.
Jedenfalls bekomme ich morgens um 5 Uhr ca ne Nachricht bei Telegram .Bist Du Dir sicher das der Iobroker neu startet und nicht nur die Telegram Instanz?
Denn da wurde mal ein Cronjob von Haus aus bei der Installation festgelegt.
Ich meine 4 oder 5 Uhr war das. -
Bist Du Dir sicher das der Iobroker neu startet und nicht nur die Telegram Instanz?
Denn da wurde mal ein Cronjob von Haus aus bei der Installation festgelegt.
Ich meine 4 oder 5 Uhr war das.@haselchen
Das kann auch so sein. Schaue ich gleich nochmal nach. Die VM läuft sonst aber weiter. -
Also, ich habe nun einiges probiert. Weder Bootreihenfolge der VMs/LXCs in Proxmox hat etwas gebracht, noch das Pausieren von PiHole, noch Änderungen der Whitelist,etc. Ich hab den Alexa-Adapter einfach runtergeworfen und neu aufgesetzt. Das hat das Problem irgendwie behoben.
Support us
716
Online32.6k
Benutzer82.2k
Themen1.3m
Beiträge