Nach einer Recherche gerade gefunden: Scheint mit einer DDOS-Atacke auf den Pushover-Service zusammenzuhängen. Dieser ist daher momentan nicht zuverlässig erreichbar. Deshalb der Fehler im LOG.
M
Best posts made by MarkusP
-
RE: Plötzlich Probleme mit Pushoverposted in Error/Bug
-
RE: Pushover geht plötzlich nicht mehrposted in ioBroker Allgemein
Habe hier was auf der Webseite von Pushover gefunden:
https://blog.pushover.net/posts/2019/10/october-24-25-ddos-attack
Vielleicht hängt das damit zusammen.
Habe jetzt noch einige Male versucht Messages zu senden. Ab und zu funktioniert es, meistens aber nicht.
Latest posts made by MarkusP
-
RE: Javascript Adapter - kein Skriptimportposted in Error/Bug
@thomas-braun Danke für die schnelle Antwort. Beide Kisten auf dem gleichen / ähnlichen Stand zu haben hat doch aber nichts damit zu tun, dass auf dem neuen System die Importfunktion nicht funktioniert. Ich kann ja die exportierte Datei garnicht erst in ein Fenster ziehen.
-
RE: Javascript Adapter - kein Skriptimportposted in Error/Bug
@mcm1957 Danke, habe ich gemacht. Ändert leider nichts.
-
Javascript Adapter - kein Skriptimportposted in Error/Bug
Bitte in der nachfolgenden Übersicht die mit ... bzw x gekennzeichneten Felder ausfüllen und im Anschluss an die Tabelle auf Linux Systemen den Output des Commands iob diag einfügen.
Hinweis: Das Eröffnen eines Issues hier ersetzt NICHT das Anlegen eine Issues im Repository des Adapters. Fehlerbehebungen werden ausschließlich über Issues getrackt.
DANKE
Bitte ausfüllen:
- Adaptername: Javascript
- Link zu Adapterrepository:
- Adapterversion: 8.7.6
- js-controller Version: 6.0.9
- Admin Version: 7.0.22
- Hardwaresystem: NUC
- Arbeitsspeicher: 16 GB
- Festplattenart: SSD
- Betriebssystem: Linux Debian Bookworm
- Nodejs-Version: 20.16.0
- NPM-Version: 10.8.1
- Installationsart: Skript
- Image, Docker genutzt: Nein
- Ort, Name der Imagedatei:
Hallo zusammen,
ich habe neben meinem ioBroker Hauptsystem ein Testsystem auf einem anderen Rechner installiert. Leider lassen sich die Skripte auf dem Testystem nicht importieren. Wenn ich auf "Skripte importieren" klicke wird mir der Bereich nicht angezeigt, in den man die ZIP-Datei ziehen kann. Habe einfach nur eine leere Seite.
Im Log erscheint auch oft:
host.ioBroker 2024-08-03 09:22:01.531 error cannot call visUtils: Not existsErstes Bild: neues Testsystem
Zweites Bild: HauptsystemVielleicht kann mir hier jemand weiterhelfen. Vielen Danke und Grüße
Markus
iob diag:
Skript v.2024-05-22 *** BASE SYSTEM *** Static hostname: ioBroker Icon name: computer-desktop Chassis: desktop 🖥️ Operating System: Debian GNU/Linux 12 (bookworm) Kernel: Linux 6.1.0-23-amd64 Architecture: x86-64 Hardware Vendor: Trigkey Hardware Model: S5 Firmware Version: FP655U508 model name : AMD Ryzen 5 5560U with Radeon Graphics Docker : false Virtualization : none Kernel : x86_64 Userland : 64 bit Systemuptime and Load: 09:21:50 up 51 min, 2 users, load average: 0.21, 0.12, 0.10 CPU threads: 12 *** Time and Time Zones *** Local time: Sat 2024-08-03 09:21:50 CEST Universal time: Sat 2024-08-03 07:21:50 UTC RTC time: Sat 2024-08-03 07:21:50 Time zone: Europe/Berlin (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no *** Users and Groups *** User that called 'iob diag': markuspollich JAVA_HOME=/usr/lib/jvm/java-17-openjdk-amd64 HOME=/home/markuspollich GROUPS=markuspollich 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 *** Display-Server-Setup *** Display-Server: true Desktop: Terminal: tty Boot Target: graphical.target *** MEMORY *** total used free shared buff/cache available Mem: 13G 2.1G 8.1G 1.4M 3.7G 11G Swap: 1.0G 0B 1.0G Total: 14G 2.1G 9.1G Active iob-Instances: 2 12889 M total memory 2015 M used memory 1111 M active memory 3664 M inactive memory 7701 M free memory 121 M buffer memory 3369 M swap cache 975 M total swap 0 M used swap 975 M free swap *** top - Table Of Processes *** top - 09:21:51 up 51 min, 2 users, load average: 0.21, 0.12, 0.10 Tasks: 209 total, 1 running, 207 sleeping, 0 stopped, 1 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 : 12889.3 total, 7700.4 free, 2016.9 used, 3490.4 buff/cache MiB Swap: 976.0 total, 976.0 free, 0.0 used. 10872.4 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 6.3G 0 6.3G 0% /dev tmpfs tmpfs 1.3G 996K 1.3G 1% /run /dev/sda2 ext4 456G 7.1G 426G 2% / tmpfs tmpfs 6.3G 0 6.3G 0% /dev/shm tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock /dev/sda1 vfat 511M 5.9M 506M 2% /boot/efi tmpfs tmpfs 1.3G 0 1.3G 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Sat Aug 3 08:30:21 2024] EXT4-fs (sda2): mounted filesystem with ordered data mode. Quota mode: none. [Sat Aug 3 08:30:22 2024] EXT4-fs (sda2): re-mounted. Quota mode: none. Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/sda2 ext4 rw,relatime,errors=remount-ro |-/sys sysfs sysfs rw,nosuid,nodev,noexec,relatime | |-/sys/kernel/security securityfs securityfs rw,nosuid,nodev,noexec,relatime | |-/sys/fs/cgroup cgroup2 cgroup2 rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot | |-/sys/fs/pstore pstore pstore rw,nosuid,nodev,noexec,relatime | |-/sys/firmware/efi/efivars efivarfs efivarfs rw,nosuid,nodev,noexec,relatime | |-/sys/fs/bpf bpf bpf rw,nosuid,nodev,noexec,relatime,mode=700 | |-/sys/kernel/debug debugfs debugfs rw,nosuid,nodev,noexec,relatime | |-/sys/kernel/tracing tracefs tracefs rw,nosuid,nodev,noexec,relatime | |-/sys/fs/fuse/connections fusectl fusectl rw,nosuid,nodev,noexec,relatime | `-/sys/kernel/config configfs configfs rw,nosuid,nodev,noexec,relatime |-/proc proc proc rw,nosuid,nodev,noexec,relatime | `-/proc/sys/fs/binfmt_misc systemd-1 autofs rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=21924 | `-/proc/sys/fs/binfmt_misc binfmt_misc binfmt_misc rw,nosuid,nodev,noexec,relatime |-/dev udev devtmpfs rw,nosuid,relatime,size=6580172k,nr_inodes=1645043,mode=755,inode64 | |-/dev/pts devpts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 | |-/dev/shm tmpfs tmpfs rw,nosuid,nodev,inode64 | |-/dev/mqueue mqueue mqueue rw,nosuid,nodev,noexec,relatime | `-/dev/hugepages hugetlbfs hugetlbfs rw,relatime,pagesize=2M |-/run tmpfs tmpfs rw,nosuid,nodev,noexec,relatime,size=1319864k,mode=755,inode64 | |-/run/lock tmpfs tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k,inode64 | |-/run/credentials/systemd-sysctl.service ramfs ramfs ro,nosuid,nodev,noexec,relatime,mode=700 | |-/run/credentials/systemd-sysusers.service ramfs ramfs ro,nosuid,nodev,noexec,relatime,mode=700 | |-/run/credentials/systemd-tmpfiles-setup-dev.service ramfs ramfs ro,nosuid,nodev,noexec,relatime,mode=700 | |-/run/credentials/systemd-tmpfiles-setup.service ramfs ramfs ro,nosuid,nodev,noexec,relatime,mode=700 | |-/run/rpc_pipefs sunrpc rpc_pipefs rw,relatime | `-/run/user/1000 tmpfs tmpfs rw,nosuid,nodev,relatime,size=1319860k,nr_inodes=329965,mode=700,uid=1000,gid=1000,inode64 `-/boot/efi /dev/sda1 vfat rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro Files in neuralgic directories: /var: 926M /var/ 491M /var/lib 395M /var/cache 372M /var/cache/apt 306M /var/lib/unifi/db 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 8.0M in the file system. /opt/iobroker/backups: 1.6M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 758M /opt/iobroker/iobroker-data/ 746M /opt/iobroker/iobroker-data/files 441M /opt/iobroker/iobroker-data/files/javascript.admin 409M /opt/iobroker/iobroker-data/files/javascript.admin/static 408M /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 26M /opt/iobroker/iobroker-data/files/scenes.admin/static/js/main.8947f24d.js.map 24M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.135279a0.js.map 19M /opt/iobroker/iobroker-data/files/vis-2/static/js/main.e7bb655f.js.map 19M /opt/iobroker/iobroker-data/files/vis-2/static/js/main.368dc292.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.16.0 /usr/bin/node v20.16.0 /usr/bin/npm 10.8.1 /usr/bin/npx 10.8.1 /usr/bin/corepack 0.28.2 nodejs: Installed: 20.16.0-1nodesource1 Candidate: 20.16.0-1nodesource1 Version table: *** 20.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 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 500 https://deb.debian.org/debian-security bookworm-security/main amd64 Packages Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: redis Core adapters versions js-controller: 6.0.9 admin: 7.0.22 javascript: 8.7.6 nodejs modules from github: 0 Adapter State + system.adapter.admin.0 : admin : ioBroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.alexa2.0 : alexa2 : ioBroker - disabled system.adapter.alias-manager.0 : alias-manager : ioBroker - enabled system.adapter.backitup.0 : backitup : ioBroker - disabled system.adapter.cloud.0 : cloud : ioBroker - disabled system.adapter.discovery.0 : discovery : ioBroker - disabled system.adapter.fritzbox.0 : fritzbox : ioBroker - disabled system.adapter.fullybrowser.0 : fullybrowser : ioBroker - disabled system.adapter.govee-local.0 : govee-local : ioBroker - disabled system.adapter.harmony.0 : harmony : ioBroker - disabled system.adapter.history.0 : history : ioBroker - disabled system.adapter.hm-rega.0 : hm-rega : ioBroker - disabled system.adapter.hm-rpc.0 : hm-rpc : ioBroker - disabled, port: 0 system.adapter.hm-rpc.1 : hm-rpc : ioBroker - disabled, port: 0 system.adapter.iot.0 : iot : ioBroker - disabled system.adapter.javascript.0 : javascript : ioBroker - disabled system.adapter.lovelace.0 : lovelace : ioBroker - disabled, port: 8091, bind: 0.0.0.0, run as: admin system.adapter.mihome-vacuum.0 : mihome-vacuum : ioBroker - disabled, port: 54321 system.adapter.mihome-vacuum.1 : mihome-vacuum : ioBroker - disabled, port: 54321 system.adapter.mihome-vacuum.2 : mihome-vacuum : ioBroker - disabled, port: 54321 system.adapter.nanoleaf-lightpanels.0 : nanoleaf-lightpanels : ioBroker - disabled, port: 16021 system.adapter.node-red.0 : node-red : ioBroker - disabled, port: 1880, bind: 0.0.0.0 system.adapter.nuki.0 : nuki : ioBroker - disabled system.adapter.pushover.0 : pushover : ioBroker - disabled system.adapter.scenes.0 : scenes : ioBroker - disabled system.adapter.sonoff.0 : sonoff : ioBroker - disabled, port: 1883, bind: 0.0.0.0 system.adapter.tradfri.0 : tradfri : ioBroker - disabled system.adapter.vis-2.0 : vis-2 : ioBroker - disabled system.adapter.web.0 : web : ioBroker - disabled, port: 8082, bind: 0.0.0.0, run as: admin + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : ioBroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin 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.0.22 , installed 7.0.22 Adapter "alexa2" : 3.26.5 , installed 3.26.5 Adapter "alias-manager": 1.2.6 , installed 1.2.6 Adapter "backitup" : 2.11.0 , installed 2.11.0 Adapter "cloud" : 5.0.1 , installed 5.0.1 Adapter "discovery" : 4.5.0 , installed 4.5.0 Adapter "fritzbox" : 0.6.0 , installed 0.6.0 Adapter "fullybrowser" : 3.0.12 , installed 3.0.12 Adapter "govee-local" : 0.2.6 , installed 0.2.6 Adapter "harmony" : 1.4.0 , installed 1.4.0 Adapter "history" : 3.0.1 , installed 3.0.1 Adapter "hm-rega" : 4.0.0 , installed 4.0.0 Adapter "hm-rpc" : 1.17.0 , installed 1.17.0 Adapter "iot" : 3.3.0 , installed 3.3.0 Adapter "javascript" : 8.7.6 , installed 8.7.6 Controller "js-controller": 6.0.9 , installed 6.0.9 Adapter "lovelace" : 4.1.10 , installed 4.1.10 Adapter "mihome-vacuum": 4.2.0 , installed 4.2.0 Adapter "nanoleaf-lightpanels": 1.4.0, installed 1.4.0 Adapter "node-red" : 5.2.1 , installed 5.2.1 Adapter "nuki" : 2.0.0 , installed 2.0.0 Adapter "pushover" : 3.0.6 , installed 3.0.6 Adapter "scenes" : 3.0.4 , installed 3.0.4 Adapter "simple-api" : 2.8.0 , installed 2.8.0 Adapter "socketio" : 6.7.0 , installed 6.7.0 Adapter "sonoff" : 3.1.0 , installed 3.1.0 Adapter "tradfri" : 3.1.3 , installed 3.1.3 Adapter "vis-2" : 2.9.32 , installed 2.9.32 Adapter "web" : 6.2.5 , installed 6.2.5 Adapter "ws" : 2.6.1 , installed 2.6.1 Objects and States Please stand by - This may take a while Objects: 806 States: 264 *** 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.debian.org/debian-security bookworm-security InRelease Ign:5 https://repo.mongodb.org/apt/debian bookworm/mongodb-org/7.0 InRelease Hit:6 https://deb.nodesource.com/node_20.x nodistro InRelease Hit:8 https://repo.mongodb.org/apt/debian bookworm/mongodb-org/7.0 Release Get:9 https://packages.adoptium.net/artifactory/deb bookworm InRelease [7517 B] Hit:7 https://dl.ui.com/unifi/debian unifi-8.2 InRelease Fetched 7517 B in 1s (12.6 kB/s) Reading package lists... Pending Updates: 0 *** Listening Ports *** Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 127.0.0.1:6379 0.0.0.0:* LISTEN 104 814 680/redis-server 12 tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 15507 759/iobroker.js-con tcp 0 0 127.0.0.1:3551 0.0.0.0:* LISTEN 0 12590 702/apcupsd tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 0 14664 1/init tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 15502 784/sshd: /usr/sbin tcp 0 0 127.0.0.1:27117 0.0.0.0:* LISTEN 106 27217 885/bin/mongod tcp6 0 0 :::8080 :::* LISTEN 106 10985 753/java tcp6 0 0 :::8081 :::* LISTEN 1001 74999 3126/io.admin.0 tcp6 0 0 :::6789 :::* LISTEN 106 18637 753/java tcp6 0 0 ::1:6379 :::* LISTEN 104 815 680/redis-server 12 tcp6 0 0 :::8843 :::* LISTEN 106 10988 753/java tcp6 0 0 :::8880 :::* LISTEN 106 10986 753/java tcp6 0 0 :::80 :::* LISTEN 0 13815 789/apache2 tcp6 0 0 :::111 :::* LISTEN 0 17351 1/init tcp6 0 0 :::22 :::* LISTEN 0 15504 784/sshd: /usr/sbin tcp6 0 0 :::8443 :::* LISTEN 106 10987 753/java udp 0 0 0.0.0.0:68 0.0.0.0:* 0 14875 661/dhclient udp 0 0 0.0.0.0:111 0.0.0.0:* 0 10817 1/init udp6 0 0 :::3478 :::* 106 14928 753/java udp6 0 0 :::5514 :::* 106 25392 753/java udp6 0 0 :::111 :::* 0 12491 1/init udp6 0 0 192.168.178.140:41177 :::* 106 25395 753/java udp6 0 0 :::10001 :::* 106 25396 753/java *** Log File - Last 25 Lines *** 2024-08-03 09:14:44.661 - info: host.ioBroker iobroker Installing iobroker.ws@2.6.1... (System call) 2024-08-03 09:14:46.518 - info: host.ioBroker iobroker added 1 package, and changed 1 package in 2s 2024-08-03 09:14:46.519 - info: host.ioBroker iobroker 139 packages are looking for funding run `npm fund` for details 2024-08-03 09:14:46.572 - info: host.ioBroker iobroker upload [11] ws.admin /opt/iobroker/node_modules/iobroker.ws/admin/i18n/de/translations.json i18n/de/translations.json application/json 2024-08-03 09:14:46.574 - info: host.ioBroker iobroker upload [10] ws.admin /opt/iobroker/node_modules/iobroker.ws/admin/i18n/en/translations.json i18n/en/translations.json application/json 2024-08-03 09:14:46.576 - info: host.ioBroker iobroker upload [9] ws.admin /opt/iobroker/node_modules/iobroker.ws/admin/i18n/es/translations.json i18n/es/translations.json application/json 2024-08-03 09:14:46.577 - info: host.ioBroker iobroker upload [8] ws.admin /opt/iobroker/node_modules/iobroker.ws/admin/i18n/fr/translations.json i18n/fr/translations.json application/json 2024-08-03 09:14:46.579 - info: host.ioBroker iobroker upload [7] ws.admin /opt/iobroker/node_modules/iobroker.ws/admin/i18n/it/translations.json i18n/it/translations.json application/json 2024-08-03 09:14:46.580 - info: host.ioBroker iobroker upload [6] ws.admin /opt/iobroker/node_modules/iobroker.ws/admin/i18n/nl/translations.json i18n/nl/translations.json application/json 2024-08-03 09:14:46.582 - info: host.ioBroker iobroker upload [5] ws.admin /opt/iobroker/node_modules/iobroker.ws/admin/i18n/pl/translations.json i18n/pl/translations.json application/json 2024-08-03 09:14:46.583 - info: host.ioBroker iobroker upload [4] ws.admin /opt/iobroker/node_modules/iobroker.ws/admin/i18n/pt/translations.json i18n/pt/translations.json application/json 2024-08-03 09:14:46.584 - info: host.ioBroker iobroker upload [3] ws.admin /opt/iobroker/node_modules/iobroker.ws/admin/i18n/ru/translations.json i18n/ru/translations.json application/json 2024-08-03 09:14:46.586 - info: host.ioBroker iobroker upload [2] ws.admin /opt/iobroker/node_modules/iobroker.ws/admin/i18n/zh-cn/translations.json i18n/zh-cn/translations.json application/json 2024-08-03 09:14:46.587 - info: host.ioBroker iobroker upload [1] ws.admin /opt/iobroker/node_modules/iobroker.ws/admin/jsonConfig.json jsonConfig.json application/json 2024-08-03 09:14:46.588 - info: host.ioBroker iobroker upload [0] ws.admin /opt/iobroker/node_modules/iobroker.ws/admin/ws.png ws.png image/png 2024-08-03 09:14:47.610 - info: host.ioBroker iobroker exit 0 2024-08-03 09:14:59.649 - info: admin.0 (3126) ==> Connected system.user.admin from ::ffff:192.168.178.53 2024-08-03 09:15:08.377 - info: admin.0 (3126) <== Disconnect system.user.admin from ::ffff:192.168.178.53 javascript 2024-08-03 09:15:08.513 - error: host.ioBroker cannot call visUtils: Not exists 2024-08-03 09:18:40.996 - info: admin.0 (3126) <== Disconnect system.user.admin from ::ffff:192.168.178.53 admin 2024-08-03 09:18:41.029 - info: admin.0 (3126) ==> Connected system.user.admin from ::ffff:192.168.178.53 2024-08-03 09:18:41.049 - info: admin.0 (3126) <== Disconnect system.user.admin from ::ffff:192.168.178.53 admin 2024-08-03 09:18:41.362 - info: admin.0 (3126) ==> Connected system.user.admin from ::ffff:192.168.178.53 2024-08-03 09:18:41.518 - error: host.ioBroker cannot call visUtils: Not exists 2024-08-03 09:22:01.531 - error: host.ioBroker cannot call visUtils: Not exists -
RE: Keine Updates nach Nodejs Updateposted in Error/Bug
ich habe jetzt mal über das Wochenende den ioBroker auf einen aktuelleren Mac mini mit OSX 10.15 gezogen und Node 18 installiert. Leider kann ich aber noch immer keine Adapter aktualisieren. Diesmal wird der Prozess mit Code 1 beendet:
$ iobroker upgrade admin@6.10.1 node:internal/bootstrap/switches/does_own_process_state:126 cachedCwd = rawMethods.cwd(); ^Error: ENOENT: no such file or directory, uv_cwd at process.wrappedCwd (node:internal/bootstrap/switches/does_own_process_state:126:28) at process.cwd (/Users/ioBroker/Documents/iobroker/node_modules/graceful-fs/polyfills.js:10:19) at ue.Yargs (/Users/ioBroker/Documents/iobroker/node_modules/iobroker.js-controller/node_modules/yargs/build/index.cjs:1:61943) at Argv (/Users/ioBroker/Documents/iobroker/node_modules/iobroker.js-controller/node_modules/yargs/index.cjs:12:16) at Object.<anonymous> (/Users/ioBroker/Documents/iobroker/node_modules/iobroker.js-controller/node_modules/yargs/index.cjs:7:1) at Module._compile (node:internal/modules/cjs/loader:1256:14) at Module._extensions..js (node:internal/modules/cjs/loader:1310:10) at Module.load (node:internal/modules/cjs/loader:1119:32) at Module._load (node:internal/modules/cjs/loader:960:12) at Module .require (node:internal/modules/cjs/loader:1143:19) { errno: -2, code: 'ENOENT', syscall: 'uv_cwd'}Node.js v18.18.2 ERROR: Process exited with code 1 -
RE: Keine Updates nach Nodejs Updateposted in Error/Bug
Habe nun 18 installiert. Jetzt startet der ioBroker nicht mehr:
ioBrokerHost-2:iobroker ioBroker$ ./iobroker start dyld: lazy symbol binding failed: Symbol not found: ____chkstk_darwin Referenced from: /usr/local/bin/node (which was built for Mac OS X 10.15) Expected in: /usr/lib/libSystem.B.dylib dyld: Symbol not found: ____chkstk_darwin Referenced from: /usr/local/bin/node (which was built for Mac OS X 10.15) Expected in: /usr/lib/libSystem.B.dylib ./iobroker: line 1: 435 Abort trap: 6 node node_modules/iobroker.js-controller/iobroker.js $1 $2 $3 $4 $5Scheint erst mit Mac OS X 10.15 zu laufen. Habe aber 10.13. Höher geht mit dem Mac nicht.
-
RE: Keine Updates nach Nodejs Updateposted in Error/Bug
Habe hier mal versucht den Alexa-Adapter upzudaten:
Would you like to upgrade alexa2 from @3.24.1 to @3.25.2 now? [(y)es, (n)o]: y Update alexa2 from @3.24.1 to @3.25.2 NPM version: 8.19.4 Installing iobroker.alexa2@3.25.2... (System call) npm WARN tar zlib: incorrect data check npm WARN tarball cached data for node-red-node-email@https://registry.npmjs.org/node-red-node-email/-/node-red-node-email-1.18.4.tgz (sha512-Qu5r/g+g91UBmVBz8aSyof9v79PTvUNqa7KDgoPPJSb6ZwZtswV7orQil2Oio9ZChaejp3GG63LoLyqaPeU53Q==) seems to be corrupted. Refreshing cache. npm WARN tarball tarball data for node-red-node-email@https://registry.npmjs.org/node-red-node-email/-/node-red-node-email-1.18.4.tgz (sha512-Qu5r/g+g91UBmVBz8aSyof9v79PTvUNqa7KDgoPPJSb6ZwZtswV7orQil2Oio9ZChaejp3GG63LoLyqaPeU53Q==) seems to be corrupted. Trying again. npm WARN tar zlib: incorrect data check npm WARN tarball cached data for @aws-crypto/sha256-js@https://registry.npmjs.org/@aws-crypto/sha256-js/-/sha256-js-3.0.0.tgz (sha512-PnNN7os0+yd1XvXAy23CFOmTbMaDxgxXtTKHybrJ39Y8kGzBATgBFibWJKH6BhytLI/Zyszs87xCOBNyBig6vQ==) seems to be corrupted. Refreshing cache. npm WARN tar zlib: incorrect data check npm WARN tarball cached data for iobroker.scenes@https://registry.npmjs.org/iobroker.scenes/-/iobroker.scenes-2.3.9.tgz (sha512-81ONrG/7FK31NxZmojaDcdwKpkaLutHKMpcvODydcWVoJEJosIatoP4nBaTAqqC76BB55J9g1v94RhU5YYwhbg==) seems to be corrupted. Refreshing cache. npm WARN tar zlib: incorrect data check npm WARN tarball cached data for iobroker.iot@https://registry.npmjs.org/iobroker.iot/-/iobroker.iot-1.14.2.tgz (sha512-dtkyMR0x+MSw1UUMVhlwjjMXjNIa39Q5wjiSxcZlspgrQSlDxo4mjLk4xYLLNpK7AtV4kD0rF/k2gzLzfGpdJw==) seems to be corrupted. Refreshing cache. npm WARN tar zlib: incorrect data check npm WARN tarball cached data for iobroker.javascript@https://registry.npmjs.org/iobroker.javascript/-/iobroker.javascript-5.7.0.tgz (sha512-otJGEYWrPmGPci+pRJfK2k0ahwLoI9Rc/+5skuAPQ/8Mr00eZuwWpRZ/gMy1flBG76erKHLkeLq2tmnlpm/8aA==) seems to be corrupted. Refreshing cache. npm WARN tar zlib: incorrect data check npm WARN tarball cached data for iobroker.icons-mfd-png@https://registry.npmjs.org/iobroker.icons-mfd-png/-/iobroker.icons-mfd-png-1.1.0.tgz (sha512-TSp3FT7T5dAvfwKFRnzi0si6SHoxI1b3DfT0qmsL1FYQ8DXFpdNnhVm/M/vfyo4/7MogkwKGRbEq9qvnK9vRZA==) seems to be corrupted. Refreshing cache. npm WARN tar zlib: incorrect data check npm WARN tarball cached data for iobroker.flot@https://registry.npmjs.org/iobroker.flot/-/iobroker.flot-1.11.0.tgz (sha512-8g2LG9M3TMCdo8KpjPriYhsuhC9x2oYVrcK4NnGQMtoG+IosJQN+tnHkOOJluWOYqVaoqu1Udc+6Gvxnx1gkjg==) seems to be corrupted. Refreshing cache. npm WARN tar zlib: incorrect data check npm WARN tarball cached data for iobroker.cloud@https://registry.npmjs.org/iobroker.cloud/-/iobroker.cloud-4.3.0.tgz (sha512-GZqj38EmaqwhYoi0dNn2a/eCv78Aeueh6PPbd5HeGqXiyI5MJ5q7Wh8zOoDfhZvycJzdVlfLWeaWJ+dmLfuQ1w==) seems to be corrupted. Refreshing cache. npm WARN tar zlib: incorrect data check npm WARN tarball cached data for iobroker.device-reminder@https://registry.npmjs.org/iobroker.device-reminder/-/iobroker.device-reminder-1.2.9.tgz (sha512-WeDmGm9R1DGw8E1g04MYVCmHahTVN/q1LUC4aFtFnznHB/CK6es5sX4jG1ydEKARtmWd+Z2mmhxCWe1xy+gh+g==) seems to be corrupted. Refreshing cache. npm WARN tar zlib: incorrect data check npm WARN tarball cached data for iobroker.admin@https://registry.npmjs.org/iobroker.admin/-/iobroker.admin-5.3.8.tgz (sha512-2Cs/p9fjRf8jyVwY7fU+ESqLfc+8MCvy5fkX7wk4UVLssHCtpujhpQcgwiepDwN/qLzbu3Mvpc2qhAlmLXZ2pw==) seems to be corrupted. Refreshing cache. npm WARN tar zlib: incorrect data check npm WARN tarball cached data for bson@https://registry.npmjs.org/bson/-/bson-4.7.2.tgz (sha512-Ry9wCtIZ5kGqkJoi6aD8KjxFZEx78guTQDnpXWiNthsxzrxAK/i8E6pCHAIZTbaEFWcOCvbecMukfK7XUvyLpQ==) seems to be corrupted. Refreshing cache. npm WARN tar zlib: incorrect data check npm WARN tarball cached data for moment-timezone@https://registry.npmjs.org/moment-timezone/-/moment-timezone-0.5.34.tgz (sha512-3zAEHh2hKUs3EXLESx/wsgw6IQdusOT8Bxm3D9UrHPQR7zlMmzwybC8zHEM1tQ4LJwP7fcxrWr8tuBg05fFCbg==) seems to be corrupted. Refreshing cache. npm WARN tar zlib: incorrect data check npm WARN tarball cached data for rrule@https://registry.npmjs.org/rrule/-/rrule-2.6.4.tgz (sha512-sLdnh4lmjUqq8liFiOUXD5kWp/FcnbDLPwq5YAc/RrN6120XOPb86Ae5zxF7ttBVq8O3LxjjORMEit1baluahA==) seems to be corrupted. Refreshing cache. npm WARN tar zlib: incorrect data check npm WARN tarball cached data for rrule@https://registry.npmjs.org/rrule/-/rrule-2.6.4.tgz (sha512-sLdnh4lmjUqq8liFiOUXD5kWp/FcnbDLPwq5YAc/RrN6120XOPb86Ae5zxF7ttBVq8O3LxjjORMEit1baluahA==) seems to be corrupted. Refreshing cache. npm WARN deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies. npm WARN deprecated request-promise-native@1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142 npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3 npm WARN deprecated querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. npm WARN deprecated node-inspect@2.0.0: This module is part of Node.js core and does not need to be installed separately. It is now unmaintained. npm WARN tarball tarball data for @sentry/utils@https://registry.npmjs.org/@sentry/utils/-/utils-6.19.7.tgz (sha512-z95ECmE3i9pbWoXQrD/7PgkBAzJYR+iXtPuTkpBjDKs86O3mT+PXOT3BAn79w2wkn7/i3vOGD2xVr1uiMl26dA==) seems to be corrupted. Trying again. npm WARN tarball tarball data for @sentry/utils@https://registry.npmjs.org/@sentry/utils/-/utils-6.19.7.tgz (sha512-z95ECmE3i9pbWoXQrD/7PgkBAzJYR+iXtPuTkpBjDKs86O3mT+PXOT3BAn79w2wkn7/i3vOGD2xVr1uiMl26dA==) seems to be corrupted. Trying again. npm WARN deprecated multer@1.4.4: Multer 1.x is affected by CVE-2022-24434. This is fixed in v1.4.4-lts.1 which drops support for versions of Node.js before 6. Please upgrade to at least Node.js 6 and version 1.4.4-lts.1 of Multer. If you need support for older versions of Node.js, we are open to accepting patches that would fix the CVE on the main 1.x release line, whilst maintaining compatibility with Node.js 0.10. npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN tarball tarball data for @aws-crypto/sha256-js@https://registry.npmjs.org/@aws-crypto/sha256-js/-/sha256-js-3.0.0.tgz (sha512-PnNN7os0+yd1XvXAy23CFOmTbMaDxgxXtTKHybrJ39Y8kGzBATgBFibWJKH6BhytLI/Zyszs87xCOBNyBig6vQ==) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.scenes@https://registry.npmjs.org/iobroker.scenes/-/iobroker.scenes-2.3.9.tgz (sha512-81ONrG/7FK31NxZmojaDcdwKpkaLutHKMpcvODydcWVoJEJosIatoP4nBaTAqqC76BB55J9g1v94RhU5YYwhbg==) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.iot@https://registry.npmjs.org/iobroker.iot/-/iobroker.iot-1.14.2.tgz (sha512-dtkyMR0x+MSw1UUMVhlwjjMXjNIa39Q5wjiSxcZlspgrQSlDxo4mjLk4xYLLNpK7AtV4kD0rF/k2gzLzfGpdJw==) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.javascript@https://registry.npmjs.org/iobroker.javascript/-/iobroker.javascript-5.7.0.tgz (sha512-otJGEYWrPmGPci+pRJfK2k0ahwLoI9Rc/+5skuAPQ/8Mr00eZuwWpRZ/gMy1flBG76erKHLkeLq2tmnlpm/8aA==) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.flot@https://registry.npmjs.org/iobroker.flot/-/iobroker.flot-1.11.0.tgz (sha512-8g2LG9M3TMCdo8KpjPriYhsuhC9x2oYVrcK4NnGQMtoG+IosJQN+tnHkOOJluWOYqVaoqu1Udc+6Gvxnx1gkjg==) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.icons-mfd-png@https://registry.npmjs.org/iobroker.icons-mfd-png/-/iobroker.icons-mfd-png-1.1.0.tgz (sha512-TSp3FT7T5dAvfwKFRnzi0si6SHoxI1b3DfT0qmsL1FYQ8DXFpdNnhVm/M/vfyo4/7MogkwKGRbEq9qvnK9vRZA==) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.cloud@https://registry.npmjs.org/iobroker.cloud/-/iobroker.cloud-4.3.0.tgz (sha512-GZqj38EmaqwhYoi0dNn2a/eCv78Aeueh6PPbd5HeGqXiyI5MJ5q7Wh8zOoDfhZvycJzdVlfLWeaWJ+dmLfuQ1w==) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.device-reminder@https://registry.npmjs.org/iobroker.device-reminder/-/iobroker.device-reminder-1.2.9.tgz (sha512-WeDmGm9R1DGw8E1g04MYVCmHahTVN/q1LUC4aFtFnznHB/CK6es5sX4jG1ydEKARtmWd+Z2mmhxCWe1xy+gh+g==) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.admin@https://registry.npmjs.org/iobroker.admin/-/iobroker.admin-5.3.8.tgz (sha512-2Cs/p9fjRf8jyVwY7fU+ESqLfc+8MCvy5fkX7wk4UVLssHCtpujhpQcgwiepDwN/qLzbu3Mvpc2qhAlmLXZ2pw==) seems to be corrupted. Trying again. npm WARN tarball tarball data for bson@https://registry.npmjs.org/bson/-/bson-4.7.2.tgz (sha512-Ry9wCtIZ5kGqkJoi6aD8KjxFZEx78guTQDnpXWiNthsxzrxAK/i8E6pCHAIZTbaEFWcOCvbecMukfK7XUvyLpQ==) seems to be corrupted. Trying again. npm WARN tarball tarball data for moment-timezone@https://registry.npmjs.org/moment-timezone/-/moment-timezone-0.5.34.tgz (sha512-3zAEHh2hKUs3EXLESx/wsgw6IQdusOT8Bxm3D9UrHPQR7zlMmzwybC8zHEM1tQ4LJwP7fcxrWr8tuBg05fFCbg==) seems to be corrupted. Trying again. npm WARN tarball tarball data for rrule@https://registry.npmjs.org/rrule/-/rrule-2.6.4.tgz (sha512-sLdnh4lmjUqq8liFiOUXD5kWp/FcnbDLPwq5YAc/RrN6120XOPb86Ae5zxF7ttBVq8O3LxjjORMEit1baluahA==) seems to be corrupted. Trying again. npm WARN tarball tarball data for rrule@https://registry.npmjs.org/rrule/-/rrule-2.6.4.tgz (sha512-sLdnh4lmjUqq8liFiOUXD5kWp/FcnbDLPwq5YAc/RrN6120XOPb86Ae5zxF7ttBVq8O3LxjjORMEit1baluahA==) seems to be corrupted. Trying again. npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN tar zlib: incorrect data check npm WARN tarball tarball data for @aws-crypto/sha256-js@https://registry.npmjs.org/@aws-crypto/sha256-js/-/sha256-js-3.0.0.tgz (sha512-PnNN7os0+yd1XvXAy23CFOmTbMaDxgxXtTKHybrJ39Y8kGzBATgBFibWJKH6BhytLI/Zyszs87xCOBNyBig6vQ==) seems to be corrupted. Trying again. npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN deprecated vm2@3.9.19: The library contains critical security issues and should not be used for production! The maintenance of the project has been discontinued. Consider migrating your code to isolated-vm. npm WARN deprecated coffee-script@1.12.7: CoffeeScript on NPM has moved to "coffeescript" (no hyphen) npm WARN tar zlib: incorrect data check npm WARN tarball tarball data for sax@https://registry.npmjs.org/sax/-/sax-0.4.3.tgz (sha512-WvnHpLKMuEsJFV3LXuvxKY4sLdKev2tIeUxn+ljlQAhpx4ZEmJOW+nEa0uERX7XvfxoimvXvEqeo94p2jXoL6g==) seems to be corrupted. Trying again. npm WARN tar zlib: incorrect data check npm WARN tarball tarball data for iobroker.nanoleaf-lightpanels@https://registry.npmjs.org/iobroker.nanoleaf-lightpanels/-/iobroker.nanoleaf-lightpanels-1.3.1.tgz (sha512-ebRlnutlmQE/U0KhBJwPHJxRIZGb3gRmdlLPh9V6HZI+l5Szz5ERgxaRrpimyAiqMWiPjOLimrxPX/v7p4Q2pw==) seems to be corrupted. Trying again. npm WARN deprecated axios@0.27.0: Formdata complete broken, incorrect build size npm WARN tarball tarball data for sax@https://registry.npmjs.org/sax/-/sax-0.4.3.tgz (sha512-WvnHpLKMuEsJFV3LXuvxKY4sLdKev2tIeUxn+ljlQAhpx4ZEmJOW+nEa0uERX7XvfxoimvXvEqeo94p2jXoL6g==) seems to be corrupted. Trying again. npm WARN tar zlib: incorrect data check npm WARN tarball tarball data for iobroker.device-reminder@https://registry.npmjs.org/iobroker.device-reminder/-/iobroker.device-reminder-1.2.9.tgz (sha512-WeDmGm9R1DGw8E1g04MYVCmHahTVN/q1LUC4aFtFnznHB/CK6es5sX4jG1ydEKARtmWd+Z2mmhxCWe1xy+gh+g==) seems to be corrupted. Trying again. npm WARN tar zlib: incorrect data check npm WARN tarball tarball data for iobroker.nanoleaf-lightpanels@https://registry.npmjs.org/iobroker.nanoleaf-lightpanels/-/iobroker.nanoleaf-lightpanels-1.3.1.tgz (sha512-ebRlnutlmQE/U0KhBJwPHJxRIZGb3gRmdlLPh9V6HZI+l5Szz5ERgxaRrpimyAiqMWiPjOLimrxPX/v7p4Q2pw==) seems to be corrupted. Trying again. npm WARN tar zlib: incorrect data check npm WARN tarball tarball data for iobroker.paw@https://registry.npmjs.org/iobroker.paw/-/iobroker.paw-0.3.2.tgz (sha512-clqAMP/An8cXXQsJbFRQ+bCqhSX/I+4bF7i1phWX87iUCO8rfWDBvLF9u4HyRsUqwM51GOe77QlNzvIT6ArTIQ==) seems to be corrupted. Trying again. npm WARN tar zlib: incorrect data check npm WARN tarball tarball data for @sentry/utils@https://registry.npmjs.org/@sentry/utils/-/utils-6.19.7.tgz (sha512-z95ECmE3i9pbWoXQrD/7PgkBAzJYR+iXtPuTkpBjDKs86O3mT+PXOT3BAn79w2wkn7/i3vOGD2xVr1uiMl26dA==) seems to be corrupted. Trying again. npm WARN tar zlib: incorrect data check npm WARN tarball tarball data for iobroker.flot@https://registry.npmjs.org/iobroker.flot/-/iobroker.flot-1.11.0.tgz (sha512-8g2LG9M3TMCdo8KpjPriYhsuhC9x2oYVrcK4NnGQMtoG+IosJQN+tnHkOOJluWOYqVaoqu1Udc+6Gvxnx1gkjg==) seems to be corrupted. Trying again. npm WARN tar zlib: incorrect data check npm WARN tarball tarball data for iobroker.paw@https://registry.npmjs.org/iobroker.paw/-/iobroker.paw-0.3.2.tgz (sha512-clqAMP/An8cXXQsJbFRQ+bCqhSX/I+4bF7i1phWX87iUCO8rfWDBvLF9u4HyRsUqwM51GOe77QlNzvIT6ArTIQ==) seems to be corrupted. Trying again. npm WARN tar zlib: incorrect data check npm WARN tarball tarball data for @zxing/text-encoding@https://registry.npmjs.org/@zxing/text-encoding/-/text-encoding-0.9.0.tgz (sha512-U/4aVJ2mxI0aDNI8Uq0wEhMgY+u4CNtEb0om3+y3+niDAsoTCOB33UF0sxpzqzdqXLqmvc+vZyAt4O8pPdfkwA==) seems to be corrupted. Trying again. npm WARN tarball tarball data for @zxing/text-encoding@https://registry.npmjs.org/@zxing/text-encoding/-/text-encoding-0.9.0.tgz (sha512-U/4aVJ2mxI0aDNI8Uq0wEhMgY+u4CNtEb0om3+y3+niDAsoTCOB33UF0sxpzqzdqXLqmvc+vZyAt4O8pPdfkwA==) seems to be corrupted. Trying again. npm WARN tar zlib: incorrect data check npm WARN tarball tarball data for iobroker.daswetter@https://registry.npmjs.org/iobroker.daswetter/-/iobroker.daswetter-3.1.10.tgz (sha512-9ERjjR8FH7B2CQidvv1K0fN5cotD+lUhgODqDU7UdiymXhQ1TJRCSmrXaawbmIgFaAoWOc5k1Qu8fTwhgJKQJQ==) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.daswetter@https://registry.npmjs.org/iobroker.daswetter/-/iobroker.daswetter-3.1.10.tgz (sha512-9ERjjR8FH7B2CQidvv1K0fN5cotD+lUhgODqDU7UdiymXhQ1TJRCSmrXaawbmIgFaAoWOc5k1Qu8fTwhgJKQJQ==) seems to be corrupted. Trying again. npm WARN tar zlib: incorrect data check npm WARN tarball tarball data for iobroker.iot@https://registry.npmjs.org/iobroker.iot/-/iobroker.iot-1.14.2.tgz (sha512-dtkyMR0x+MSw1UUMVhlwjjMXjNIa39Q5wjiSxcZlspgrQSlDxo4mjLk4xYLLNpK7AtV4kD0rF/k2gzLzfGpdJw==) seems to be corrupted. Trying again. npm WARN tar zlib: incorrect data check npm WARN tarball tarball data for iobroker.javascript@https://registry.npmjs.org/iobroker.javascript/-/iobroker.javascript-5.7.0.tgz (sha512-otJGEYWrPmGPci+pRJfK2k0ahwLoI9Rc/+5skuAPQ/8Mr00eZuwWpRZ/gMy1flBG76erKHLkeLq2tmnlpm/8aA==) seems to be corrupted. Trying again. npm WARN tar zlib: incorrect data check npm WARN tarball tarball data for iobroker.admin@https://registry.npmjs.org/iobroker.admin/-/iobroker.admin-5.3.8.tgz (sha512-2Cs/p9fjRf8jyVwY7fU+ESqLfc+8MCvy5fkX7wk4UVLssHCtpujhpQcgwiepDwN/qLzbu3Mvpc2qhAlmLXZ2pw==) seems to be corrupted. Trying again. npm ERR! code ENOENT npm ERR! syscall stat npm ERR! path /Users/ioBroker/.npm/_cacache/content-v2/sha512/5a/f9/c7a4b28cb84b09155dcb5eebf1298e2c2dd29ebf6b48794c67fa58e5400869c78644989396fa711ad2e1115fb5ef7f1a229af5ef12a7a8f78a768d7a0bea npm ERR! errno -2 npm ERR! enoent ENOENT: no such file or directory, stat '/Users/ioBroker/.npm/_cacache/content-v2/sha512/5a/f9/c7a4b28cb84b09155dcb5eebf1298e2c2dd29ebf6b48794c67fa58e5400869c78644989396fa711ad2e1115fb5ef7f1a229af5ef12a7a8f78a768d7a0bea' npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent npm ERR! A complete log of this run can be found in: npm ERR! /Users/ioBroker/.npm/_logs/2023-10-20T11_44_10_607Z-debug-0.log host.ioBrokerHost-2.fritz.box Cannot install iobroker.alexa2@3.25.2: 254 ioBrokerHost-2:iobroker ioBroker$open Request’s Past, Present and Future #3142
closed ReDos Vulnerability Regression Visibility Notice #797
closed ReDos Vulnerability Regression Visibility Notice #797
closed ReDos Vulnerability Regression Visibility Notice #797
open Request’s Past, Present and Future #3142
-
RE: Keine Updates nach Nodejs Updateposted in Error/Bug
Ja, habe länger nichts mehr an Upadtes gemacht. Gehe erstmal auf 16, da 18 auf os HighSierra nicht läuft und höher als High Sierra kann ich mit dem alten Mac leider nicht gehen.
-
RE: Keine Updates nach Nodejs Updateposted in Error/Bug
... dann kommt das. Werden ja nur mögliche Commands angezeigt oder?
ioBrokerHost-2:iobroker ioBroker$ ./iob diag iobroker [command] Commands: iobroker setup Setup ioBroker iobroker start [all|<adapter>.<instance>] Starts the js-controller or a specified adapter instance iobroker stop [<adapter>.<instance>] stops the js-controller or a specified adapter instance iobroker restart [<adapter>.<instance>] Restarts js-controller or a specified adapter instance [aliases: r] iobroker debug <adapter>[.<instance>] Starts a Node.js debugging session for the adapter instance iobroker info Shows the host info iobroker logs [<adapter>] Monitor log iobroker add <adapter> [desiredNumber] Add instance of adapter [aliases: a] iobroker install <adapter> Installs a specified adapter [aliases: i] iobroker rebuild [<module>] Rebuild all native modules or path iobroker url <url> [<name>] Install adapter from specified url, e.g. GitHub iobroker del <adapter> Remove adapter and all instances from this host [aliases: delete] iobroker del <adapter>.<instance> Remove adapter instance [aliases: delete] iobroker update [<repositoryUrl>] Update repository and list adapters iobroker upgrade Upgrade management iobroker upload [all|<adapter>] Upload management [aliases: u] iobroker object Object management [aliases: o] iobroker state State management [aliases: s] iobroker message <adapter>[.instance] <command> [<message>] Send message to adapter instance/s iobroker list <type> [<filter>] List all entries, like objects iobroker chmod <mode> <file> Change file rights iobroker chown <user> <group> <file> Change file ownership iobroker touch <file> Touch file iobroker rm <file> Remove file iobroker file File management iobroker user User commands iobroker group group management iobroker host <hostname> Set host to given hostname iobroker set <adapter>.<instance> Change settings of adapter config iobroker license <license.file or license.text> Update license by given file iobroker cert Certificate management iobroker clean <yes> Clears all objects and states iobroker backup Create backup iobroker restore <backup name or path> Restore a specified backup iobroker validate <backup name or path> Validate a specified backup iobroker status [all|<adapter>.<instance>] Status of ioBroker or adapter instance [aliases: isrun] iobroker repo [<name>] Show repo information iobroker uuid Show uuid of the installation [aliases: id] iobroker unsetup Reset license, installation secret and language iobroker fix Execute the installation fixer script, this updates your ioBroker installation iobroker multihost Multihost management iobroker compact compact group management iobroker plugin Plugin management iobroker version [<adapter>] Show version of js-controller or specified adapter [aliases: v] Options: --help Show help [boolean] -
Keine Updates nach Nodejs Updateposted in Error/Bug
Systemdata Hardwaresystem: macMini Arbeitsspeicher: 16GB Festplattenart: SSD Betriebssystem: Mac OS High Sierra Nodejs-Version: 16.20.2 NPM-Version: 8.19.4 Hallo zusammen,
ich hoffe ihr könnt mir hier weiterhelfen. Ich betreibe nun schon rund 4 Jahre den ioBroker auf einem Mac Mini ohne Probleme und habe auch schon mehrere NodeJS Updates hinter mir. Jetzt habe ich aktuell von Node JS 14 auf 16 upgedatet. Leider lassen sich nun keine Adapter mehr aktualisieren. Die Versuche brechen immer mit Code 25 ab.
Es wurde das NodeJS Installationspackage von der NodeJS Webseite für das Upadte verwendet (so wie bisher immer).Node und NPM Versionen ergeben:
ioBrokerHost-2:~ ioBroker$ node -v v16.20.2 ioBrokerHost-2:~ ioBroker$ npm -v 8.19.4 ioBrokerHost-2:~ ioBroker$Scheint soweit zu passen.
Adapter Updates brechen mit folgender Meldung ab (hier am Beispiel vom Alexa-Adapter):
$ iobroker upgrade alexa2@3.25.2 Update alexa2 from @3.24.1 to @3.25.2 NPM version: 8.19.4 Installing iobroker.alexa2@3.25.2... (System call) host.ioBrokerHost-2.fritz.box Cannot install iobroker.alexa2@3.25.2: 254 ERROR: Process exited with code 25Updateversuch über Terminal:
Would you like to upgrade vis-timeandweather from @1.1.7 to @1.2.2 now? [(y)es, (n)o]: y Update vis-timeandweather from @1.1.7 to @1.2.2 NPM version: 8.19.4 Installing iobroker.vis-timeandweather@1.2.2... (System call) host.ioBrokerHost-2.fritz.box Cannot install iobroker.vis-timeandweather@1.2.2: 254Die verschiedenen Posts im Forum zu dem Thema haben mich leider nicht weitergebracht. Wäre super wenn mir da jemand weiterhelfen könnte.
Viele Grüße
-
RE: trådfri nach Update Fehlermeldungen?posted in Error/Bug
v.2.7.0 funktioniert bei mir leider nicht. Erhalte die gleichen Warnmeldungen im Log und zusätzlich lassen sich die Lampen aber nicht mehr Schalten bzw. beim Versuch zu Schalten geht der Adapter auf gelb. Bin daher wieder auf v2.6.5 zurück. Seit dem gibt es aber auch keine Warnmeldungen mehr im Log.
