NEWS
Javascript Adapter 7.8.0 stuerzt ab
-
@homoran mehrfach Instanz neu gestartet. Auch andere Instanzen/ Adapter deaktiviert. Bei Aktivierung von Javascript immer dasselbe verhalt: Absturz.
-
@hawkiobroker-0 sagte in Javascript Adapter 7.8.0 stuerzt ab:
Bei Aktivierung von Javascript immer dasselbe verhalt: Absturz.
Schau ins Log...
-
@thomas-braun Danke fuer den Hinweis. Das habe ich mir angeschaut. Ich bin bei weitem kein Experte und kann da nichts erkennen. Irgend eine Idee?
-
@hawkiobroker-0 sagte in Javascript Adapter 7.8.0 stuerzt ab:
kann da nichts erkennen. Irgend eine Idee?
Ich auch nicht. Scheint geheim zu sein.
-
@homoran Nur zur Vollstaendigkeit: Auch iobroker und den Synology Server habe ich beim troubleshooting mehrfach neu gestartet.
-
@thomas-braun Na dann trotzdem Danke fuer die Muehe.
-
Poste das geheime Log halt, dann kann man da vielleicht auch was sehen.
Alternativ die Langfassung voniob diag
halt.
-
@thomas-braun wie gesagt, ich bin kein Profi. In meinem orginaeren Post habe ich folgenden Log-Ausschitt mitgeliefert.
Was waere noch hilfreich (ausser der Langversion von iob diag. -
@hawkiobroker-0 sagte in Javascript Adapter 7.8.0 stuerzt ab:
Was waere noch hilfreich (ausser der Langversion von iob diag
nur diese Ausgabe in der Langfassung.
Ist doch kein Hexenwerk.
In der Konsolse
iob diag
eingeben und dann einfach alles in Codetags hier posten, dann kann man da besser helfen
-
@hawkiobroker-0 sagte in Javascript Adapter 7.8.0 stuerzt ab:
Log-Ausschitt mitgeliefert
Was ist das für ein Log?
Und als Screenshot kann man damit auch nix anfangen. -
@djmarc75 hier ist das Log aus iobroker und der output aus
iob diag
. Beides habe ich erstellt nach einem iobroker Neustart (davor javascript instance ausgeschaltet) und danach javascript Instanz wieder aktiviert.======== Start marking the full check here =========
Skript v.2023-10-10 *** BASE SYSTEM *** Hardware Vendor : Synology Kernel : x86_64 Userland : amd64 Docker : v9.1.1 Virtualization : Docker Kernel : x86_64 Userland : amd64 Systemuptime and Load: 20:22:29 up 2 days, 6:03, 0 user, load average: 3.04, 1.87, 1.65 CPU threads: 4 *** Time and Time Zones *** Mon Mar 11 19:22:29 UTC 2024 Mon Mar 11 20:22:29 CET 2024 CET +0100 Etc/UTC *** User and Groups *** root *** X-Server-Setup *** X-Server: false Desktop: Terminal: *** MEMORY *** total used free shared buff/cache available Mem: 16G 8.8G 1.8G 151M 6.6G 7.9G Swap: 12G 351M 11G Total: 28G 9.1G 13G 15854 M total memory 8359 M used memory 9125 M active memory 3649 M inactive memory 1681 M free memory 39 M buffer memory 6246 M swap cache 11563 M total swap 334 M used swap 11229 M free swap *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/cachedev_0 btrfs 7.0T 2.4T 4.7T 34% / tmpfs tmpfs 64M 0 64M 0% /dev tmpfs tmpfs 7.8G 0 7.8G 0% /sys/fs/cgroup shm tmpfs 64M 0 64M 0% /dev/shm /dev/mapper/cachedev_0 btrfs 7.0T 2.4T 4.7T 34% /opt/iobroker /dev/mapper/cachedev_0 btrfs 7.0T 2.4T 4.7T 34% /etc/hosts Messages concerning ext4 filesystem in dmesg: sudo: unable to resolve host iobrokerSchozach01: Name or service not known [Sat Mar 9 14:19:51 2024] EXT4-fs (md0): couldn't mount as ext3 due to feature [Sat Mar 9 14:19:51 2024] EXT4-fs (md0): mounted filesystem with ordered data m [Sat Mar 9 14:19:53 2024] EXT4-fs (md0): couldn't mount as ext3 due to feature [Sat Mar 9 14:19:53 2024] EXT4-fs (md0): mounted filesystem with ordered data m [Sat Mar 9 14:19:53 2024] EXT4-fs (loop0): couldn't mount as ext3 due to featur [Sat Mar 9 14:19:53 2024] EXT4-fs (loop0): mounted filesystem with ordered data [Sat Mar 9 14:19:57 2024] EXT4-fs (md0): couldn't mount as ext3 due to feature [Sat Mar 9 14:19:57 2024] EXT4-fs (md0): mounted filesystem with ordered data m [Sat Mar 9 14:19:58 2024] EXT4-fs (md0): couldn't mount as ext3 due to feature [Sat Mar 9 14:19:58 2024] EXT4-fs (md0): mounted filesystem with ordered data m [Sat Mar 9 14:20:25 2024] EXT4-fs (loop0): mounted filesystem with ordered data Show mounted filesystems \(real ones only\): TARGET SOURCE IONS / /dev/mapper/cachedev_0[/@syno/@docker/btrfs/subvolumes/7fc7ee nodev,relatime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,s 606484219300d6f0f94a804c3a4ccf9de8fa57950133361b70e104e |-/opt/iobroker /dev/mapper/cachedev_0[/@syno/docker/iobrokerSchozach01] nodev,relatime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,s |-/etc/resolv.conf /dev/mapper/cachedev_0[/@syno/@docker/containers/b7031f18c8ab nodev,relatime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,s 0577f801f8ba9fc9c72e03eb707055b3233e3162eacd3d52/resolv.conf |-/etc/hostname /dev/mapper/cachedev_0[/@syno/@docker/containers/b7031f18c8ab nodev,relatime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,s 0577f801f8ba9fc9c72e03eb707055b3233e3162eacd3d52/hostname `-/etc/hosts /dev/mapper/cachedev_0[/@syno/@docker/containers/b7031f18c8ab nodev,relatime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,s 0577f801f8ba9fc9c72e03eb707055b3233e3162eacd3d52/hosts Files in neuralgic directories: /var: sudo: unable to resolve host iobrokerSchozach01: Name or service not known 34M /var/ 32M /var/lib 19M /var/lib/apt/lists 19M /var/lib/apt 13M /var/lib/dpkg /opt/iobroker/backups: 14G /opt/iobroker/backups/ 0 /opt/iobroker/backups/redistmp /opt/iobroker/iobroker-data: 16G /opt/iobroker/iobroker-data/ 15G /opt/iobroker/iobroker-data/history 295M /opt/iobroker/iobroker-data/files 97M /opt/iobroker/iobroker-data/backup-objects 89M /opt/iobroker/iobroker-data/files/echarts.admin The five largest files in iobroker-data are: 130M /opt/iobroker/iobroker-data/objects.jsonl 24M /opt/iobroker/iobroker-data/files/echarts/static/js/main.2b7495c2.js.map 24M /opt/iobroker/iobroker-data/files/echarts.admin/chart/static/js/main.2b7 23M /opt/iobroker/iobroker-data/files/echarts.admin/static/js/main.245b61c0. 22M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.c05ba1d3.js.m USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/* in your adapter setups, please always find: '/dev/serial/by-id/': No such file or directory *** NodeJS-Installation *** /usr/bin/nodejs v18.19.1 /usr/bin/node v18.19.1 /usr/bin/npm 10.2.4 /usr/bin/npx 10.2.4 /usr/bin/corepack 0.22.0 nodejs: Installed: 18.19.1-1nodesource1 Candidate: 18.19.1-1nodesource1 Version table: *** 18.19.1-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 18.19.0+dfsg-6~deb12u1 500 500 http://deb.debian.org/debian-security bookworm-security/main amd64 P 18.19.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.2-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.1-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.17.1-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.17.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.1-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.15.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.2-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.1-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.13.0+dfsg1-1 500 500 http://deb.debian.org/debian bookworm/main amd64 Packages 18.13.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.12.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.11.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.10.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.1-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.8.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.7.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.6.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.5.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.4.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.3.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.2.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.1.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.0.0-1nodesource1 1001 1001 https://deb.nodesource.com/node_18.x nodistro/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: jsonl Core adapters versions js-controller: 5.0.19 admin: 6.13.16 javascript: 7.8.0 Adapters from github: 1 Adapter State + system.adapter.admin.0 : admin : iobrokerScho n as: admin + system.adapter.backitup.0 : backitup : iobrokerScho + system.adapter.bydhvs.0 : bydhvs : iobrokerScho + system.adapter.daikin.1 : daikin : iobrokerScho + system.adapter.daikin.2 : daikin : iobrokerScho + system.adapter.daikin.3 : daikin : iobrokerScho system.adapter.daswetter.1 : daswetter : iobrokerScho system.adapter.discovery.0 : discovery : iobrokerScho system.adapter.echarts.0 : echarts : iobrokerScho + system.adapter.email.0 : email : iobrokerScho system.adapter.flot.0 : flot : iobrokerScho system.adapter.fronius-solarweb.0 : fronius-solarweb : iobrokerScho + system.adapter.fronius.0 : fronius : iobrokerScho system.adapter.gruenbeck.0 : gruenbeck : iobrokerScho + system.adapter.history.0 : history : iobrokerScho + system.adapter.hmip.0 : hmip : iobrokerScho system.adapter.javascript.0 : javascript : iobrokerScho system.adapter.javascript.1 : javascript : iobrokerScho + system.adapter.modbus.0 : modbus : iobrokerScho + system.adapter.modbus.1 : modbus : iobrokerScho + system.adapter.modbus.2 : modbus : iobrokerScho system.adapter.modbus.3 : modbus : iobrokerScho + system.adapter.modbus.4 : modbus : iobrokerScho system.adapter.netatmo-crawler.0 : netatmo-crawler : iobrokerScho system.adapter.parser.0 : parser : iobrokerScho system.adapter.porsche.0 : porsche : iobrokerScho system.adapter.pvforecast.0 : pvforecast : iobrokerScho + system.adapter.sonoff.0 : sonoff : iobrokerScho system.adapter.statistics.0 : statistics : iobrokerScho system.adapter.weatherunderground.0 : weatherunderground : iobrokerScho + system.adapter.web.0 : web : iobrokerScho iobrokerhawk system.adapter.wmswebcontrol.0 : wmswebcontrol : iobrokerScho + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : iobrokerScho n as: admin + system.adapter.sonoff.0 : sonoff : iobrokerScho + system.adapter.web.0 : web : iobrokerScho iobrokerhawk ioBroker-Repositories stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json Active repo(s): stable Installed ioBroker-Instances Used repository: stable Adapter "admin" : 6.13.16 , installed 6.13.16 Adapter "backitup" : 2.10.11 , installed 2.10.11 Adapter "bydhvs" : 1.5.0 , installed 1.5.0 Adapter "daikin" : 1.4.2 , installed 1.4.2 Adapter "daswetter" : 3.1.13 , installed 3.1.13 Adapter "discovery" : 4.2.0 , installed 4.2.0 Adapter "echarts" : 1.7.2 , installed 1.7.2 Adapter "email" : 1.2.2 , installed 1.2.2 Adapter "flot" : 1.12.0 , installed 1.12.0 Adapter "fronius" : 2.0.2 , installed 2.0.2 Adapter "fronius-solarweb": 0.0.3 , installed 0.0.3 Adapter "gruenbeck" : 0.0.42 , installed 0.0.42 Adapter "history" : 3.0.1 , installed 3.0.1 Adapter "hmip" : 1.22.0 , installed 1.22.0 Adapter "javascript" : 7.8.0 , installed 7.8.0 Controller "js-controller": 5.0.19 , installed 5.0.19 Adapter "modbus" : 6.1.0 , installed 6.1.0 Adapter "netatmo-crawler": 0.8.1 , installed 0.8.1 Adapter "parser" : 2.1.0 , installed 2.1.0 Adapter "porsche" : 0.0.3 , installed 0.2.0 Adapter "pvforecast" : 2.9.1 , installed 2.9.1 Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "socketio" : 6.6.0 , installed 6.6.0 Adapter "sonoff" : 3.0.3 , installed 3.0.3 Adapter "statistics" : 2.4.0 , installed 2.4.0 Adapter "weatherunderground": 3.6.0, installed 3.6.0 Adapter "web" : 6.2.3 , installed 6.2.3 Adapter "wmswebcontrol": 0.0.5 , installed 0.0.5 Adapter "ws" : 2.5.10 , installed 2.5.10 Objects and States Please stand by - This may take a while Objects: 16479 States: 13775 *** OS-Repositories and Updates *** sudo: unable to resolve host iobrokerSchozach01: Name or service not known sudo: unable to resolve host iobrokerSchozach01: Name or service not known 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-security bookworm-security InRelease Hit:4 https://deb.nodesource.com/node_18.x nodistro InRelease Reading package lists... Pending Updates: 1 *** Listening Ports *** sudo: unable to resolve host iobrokerSchozach01: Name or service not known Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 127.0.0.1:512 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:161 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:6690 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:3493 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN tcp 0 0 192.168.178.5:49160 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:5000 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:5001 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:554 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:9900 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:9901 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:5357 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN tcp 0 0 192.168.178.5:50001 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:50002 0.0.0.0:* LISTEN tcp 0 0 192.168.178.5:49170 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:915 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:33300 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:725 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:3000 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:5432 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:3001 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:18617 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:6011 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:6012 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:6013 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:6014 0.0.0.0:* LISTEN tcp6 0 0 :::3264 :::* LISTEN tcp6 0 0 :::3265 :::* LISTEN tcp6 0 0 :::6690 :::* LISTEN tcp6 0 0 :::5000 :::* LISTEN tcp6 0 0 :::5001 :::* LISTEN tcp6 0 0 :::139 :::* LISTEN tcp6 0 0 :::9900 :::* LISTEN tcp6 0 0 :::9901 :::* LISTEN tcp6 0 0 :::5357 :::* LISTEN tcp6 0 0 :::1935 :::* LISTEN tcp6 0 0 :::80 :::* LISTEN tcp6 0 0 :::8081 :::* LISTEN tcp6 0 0 :::5201 :::* LISTEN tcp6 0 0 :::8082 :::* LISTEN tcp6 0 0 :::725 :::* LISTEN tcp6 0 0 :::443 :::* LISTEN tcp6 0 0 :::3261 :::* LISTEN tcp6 0 0 :::445 :::* LISTEN tcp6 0 0 :::3263 :::* LISTEN udp 0 0 0.0.0.0:35136 0.0.0.0:* udp 0 0 127.0.0.1:60185 0.0.0.0:* udp 0 0 0.0.0.0:19996 0.0.0.0:* udp 0 0 0.0.0.0:19997 0.0.0.0:* udp 0 0 0.0.0.0:19998 0.0.0.0:* udp 0 0 0.0.0.0:3702 0.0.0.0:* udp 0 0 0.0.0.0:3702 0.0.0.0:* udp 0 0 0.0.0.0:5353 0.0.0.0:* udp 0 0 192.168.178.5:55900 0.0.0.0:* udp 0 0 192.168.178.5:55901 0.0.0.0:* udp 0 0 192.168.178.5:55902 0.0.0.0:* udp 0 0 127.0.0.1:47750 0.0.0.0:* udp 0 0 172.17.0.1:123 0.0.0.0:* udp 0 0 192.168.178.10:123 0.0.0.0:* udp 0 0 192.168.178.5:123 0.0.0.0:* udp 0 0 127.0.0.1:123 0.0.0.0:* udp 0 0 0.0.0.0:123 0.0.0.0:* udp 0 0 192.168.178.255:137 0.0.0.0:* udp 0 0 192.168.178.5:137 0.0.0.0:* udp 0 0 192.168.178.255:137 0.0.0.0:* udp 0 0 192.168.178.10:137 0.0.0.0:* udp 0 0 0.0.0.0:137 0.0.0.0:* udp 0 0 192.168.178.255:138 0.0.0.0:* udp 0 0 192.168.178.5:138 0.0.0.0:* udp 0 0 192.168.178.255:138 0.0.0.0:* udp 0 0 192.168.178.10:138 0.0.0.0:* udp 0 0 0.0.0.0:138 0.0.0.0:* udp 0 0 127.0.0.1:161 0.0.0.0:* udp 0 0 127.0.0.1:58098 0.0.0.0:* udp 0 0 0.0.0.0:59087 0.0.0.0:* udp 0 0 0.0.0.0:9997 0.0.0.0:* udp 0 0 0.0.0.0:9998 0.0.0.0:* udp 0 0 0.0.0.0:9999 0.0.0.0:* udp 0 0 0.0.0.0:1900 0.0.0.0:* udp 0 0 0.0.0.0:1900 0.0.0.0:* udp 0 0 0.0.0.0:1900 0.0.0.0:* udp 0 0 0.0.0.0:1900 0.0.0.0:* udp6 0 0 :::3702 :::* udp6 0 0 :::3702 :::* udp6 0 0 :::5353 :::* udp6 0 0 :::38969 :::* udp6 0 0 2003:c9:6f14:6200:2:123 :::* udp6 0 0 2003:c9:6f14:6200:2:123 :::* udp6 0 0 fe80::6006:26ff:fea:123 :::* udp6 0 0 fe80::48d5:c1ff:fec:123 :::* udp6 0 0 fe80::10c3:75ff:fe5:123 :::* udp6 0 0 fe80::42:97ff:fe5f::123 :::* udp6 0 0 fe80::211:32ff:fea6:123 :::* udp6 0 0 fe80::211:32ff:fea6:123 :::* udp6 0 0 ::1:123 :::* udp6 0 0 :::123 :::* *** Log File - Last 25 Lines *** 2024-03-11 20:23:25.222 - silly: javascript.0 (1530) writeFile(filename: "node_ 2024-03-11 20:23:25.222 - silly: javascript.0 (1530) creating new file with v 2024-03-11 20:23:25.222 - silly: javascript.0 (1530) writeFile(filename: "node_ 2024-03-11 20:23:25.222 - silly: javascript.0 (1530) creating new file with v 2024-03-11 20:23:25.240 - silly: javascript.0 (1530) writeFile(filename: "node_ true 2024-03-11 20:23:25.241 - silly: javascript.0 (1530) creating new file with v 2024-03-11 20:23:25.241 - silly: javascript.0 (1530) writeFile(filename: "node_ 2024-03-11 20:23:25.241 - silly: javascript.0 (1530) creating new file with v 2024-03-11 20:23:25.241 - silly: javascript.0 (1530) writeFile(filename: "node_ e 2024-03-11 20:23:25.241 - silly: javascript.0 (1530) creating new file with v 2024-03-11 20:23:25.245 - debug: javascript.0 (1530) Loaded TypeScript definiti types/request/index.d.ts"] 2024-03-11 20:23:25.245 - silly: javascript.0 (1530) writeFile(filename: "node_ 2024-03-11 20:23:25.245 - silly: javascript.0 (1530) creating new file with v 2024-03-11 20:23:25.246 - silly: javascript.0 (1530) writeFile(filename: "node_ 2024-03-11 20:23:25.246 - silly: javascript.0 (1530) creating new file with v 2024-03-11 20:23:25.246 - silly: javascript.0 (1530) writeFile(filename: "node_ 2024-03-11 20:23:25.246 - silly: javascript.0 (1530) creating new file with v 2024-03-11 20:23:25.247 - silly: javascript.0 (1530) writeFile(filename: "node_ 2024-03-11 20:23:25.247 - silly: javascript.0 (1530) creating new file with v 2024-03-11 20:23:25.301 - silly: javascript.0 (1530) redis psubscribe cfg.o.* 2024-03-11 20:23:25.306 - silly: javascript.0 (1530) States system redis pmessa :{"val":"silly","ack":true,"ts":1710185005251,"q":0,"from":"system.adapter.javas 2024-03-11 20:23:25.410 - info: javascript.0 (1530) requesting all states 2024-03-11 20:23:25.411 - info: javascript.0 (1530) requesting all objects 2024-03-11 20:23:49.823 - silly: javascript.0 (1530) Objects user redis pmessag mmon":{"name":"Plugin States"},"native":{},"_id":"system.host.iobrokerSchozach01 em.user.admin","ownerGroup":"system.group.administrator"}} 2024-03-11 20:23:49.825 - silly: javascript.0 (1530) Objects user redis pmessag :{"val":"silly","ack":true,"ts":1710185005251,"q":0,"from":"system.adapter.javas 2024-03-11 20:23:25.410 - info: javascript.0 (1530) requesting all states 2024-03-11 20:23:25.411 - info: javascript.0 (1530) requesting all objects 2024-03-11 20:23:49.823 - silly: javascript.0 (1530) Objects user redis pmessag mmon":{"name":"Plugin States"},"native":{},"_id":"system.host.iobrokerSchozach01 em.user.admin","ownerGroup":"system.group.administrator"}} 2024-03-11 20:23:49.825 - silly: javascript.0 (1530) Objects user redis pmessag te","common":{"name":"Plugin - enabled","type":"boolean","read":true,"write":tru sentry.enabled","acl":{"object":1636,"state":1636,"file":1632,"owner":"system.us
============ Mark until here for C&P =============
-
@hawkiobroker-0 und hier der iobroker log Auszug von javascript nach Aktivierung.
240311 iobroker javascript log.txt -
2024-03-11 20:41:05.745 error Caught by controller[0]: FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
Da dürfte ein Skript schief sein.
-
die ganzen SILLY musste mal weg machen, das macht Dein System platt.
Stell das bitte auf mindestens INFO um -
@thomas-braun Danke! Warum habe ich Probleme, wenn ich alle Skripte deaktiviert habe?
-
Die skripte werden beim Start des Adapters kompiliert. Wird da schon hängen.
-
@djmarc75 Danke! Erledigt!
-
@thomas-braun ok. D.h., alle "neuen" Skripte loeschen?
-
Kannst du ja weg kopieren.
-
@thomas-braun ist das so richtig eingestellt?