Weihnachtsangebot 2025! 🎄

[wendy2702]

@markphilip erster Versuch wäre das:

iobroker stop
iobroker fix
iobroker restart

[Meister Mopper]

@markphilip

Zeig bitte mal die Langfassung.

[markphilip]

@meister-mopper

Script v.2024-10-19

*** BASE SYSTEM ***
 Static hostname: IoBroker
       Icon name: computer-vm
         Chassis: vm 🖴
  Virtualization: kvm
Operating System: Debian GNU/Linux 12 (bookworm)
          Kernel: Linux 6.1.0-23-amd64
    Architecture: x86-64
 Hardware Vendor: QEMU
  Hardware Model: Standard PC _i440FX + PIIX, 1996_
Firmware Version: rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org
OS is similar to:

model name      : Common KVM processor
Docker          : false
Virtualization  : kvm
Kernel          : x86_64
Userland        : 64 bit

Systemuptime and Load:
 18:33:40 up  5:09,  3 users,  load average: 0.08, 0.09, 0.09
CPU threads: 2


*** LIFE CYCLE STATUS ***
Operating System is the current Debian stable version codenamed 'bookworm'!

*** TIME AND TIMEZONES ***
               Local time: Sat 2025-01-04 18:33:40 CET
           Universal time: Sat 2025-01-04 17:33:40 UTC
                 RTC time: Sat 2025-01-04 17:33:40
                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':
mark
HOME=/home/mark
GROUPS=mark cdrom floppy sudo audio dip video plugdev netdev iobroker

User that is running 'js-controller':
js-controller is not running

*** DISPLAY-SERVER SETUP ***
Display-Server: false
Desktop:
Terminal:       tty

*** MEMORY ***
               total        used        free      shared  buff/cache   available
Mem:            3.1G        346M        344M        704K        2.6G        2.8G
Swap:           3.2G         21M        3.2G
Total:          6.3G        367M        3.5G

Active iob-Instances:   0

         2972 M total memory
          330 M used memory
          638 M active memory
         1496 M inactive memory
          328 M free memory
          163 M buffer memory
         2337 M swap cache
         3069 M total swap
           20 M used swap
         3049 M free swap

*** top - Table Of Processes  ***
top - 18:33:40 up  5:09,  3 users,  load average: 0.08, 0.09, 0.09
Tasks:  95 total,   1 running,  94 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.0 us,100.0 sy,  0.0 ni,  0.0 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
MiB Mem :   2972.2 total,    328.1 free,    330.8 used,   2501.4 buff/cache
MiB Swap:   3070.0 total,   3049.6 free,     20.4 used.   2641.4 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  1.5G     0  1.5G   0% /dev
tmpfs          tmpfs     298M  556K  297M   1% /run
/dev/sda1      ext4       29G   20G  7.9G  71% /
tmpfs          tmpfs     1.5G     0  1.5G   0% /dev/shm
tmpfs          tmpfs     5.0M     0  5.0M   0% /run/lock
tmpfs          tmpfs     298M     0  298M   0% /run/user/1000

Messages concerning ext4 filesystem in dmesg:
[Sat Jan  4 13:23:55 2025] EXT4-fs (sda1): mounted filesystem with ordered data mode. Quota mode: none.
[Sat Jan  4 13:23:56 2025] 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:
979M    /var/
542M    /var/log
516M    /var/log/journal/c4e4bfe1d7c94199919f017b537b1ac0
516M    /var/log/journal
235M    /var/cache

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 38.8M in the file system.

/opt/iobroker/backups:
115M    /opt/iobroker/backups/

/opt/iobroker/iobroker-data:
1.6G    /opt/iobroker/iobroker-data/
1.4G    /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
27M     /opt/iobroker/iobroker-data/files/material/static/js/2.73100bd6.chunk.js.map
24M     /opt/iobroker/iobroker-data/files/web.admin/static/js/main.135279a0.js.map
24M     /opt/iobroker/iobroker-data/files/vis-2/static/js/main.f305bc29.js.map
24M     /opt/iobroker/iobroker-data/files/vis-2/static/js/main.8e80ccb0.js.map

USB-Devices by-id:
USB-Sticks -  Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id':

No Devices found 'by-id'

*** NodeJS-Installation ***

/usr/bin/nodejs         v20.18.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 stable/main amd64 Packages
     18.19.0+dfsg-6~deb12u1 500
        500 http://security.debian.org/debian-security stable-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
file:///opt/iobroker/node_modules/@iobroker/js-controller-cli/build/esm/lib/setup/setupBackup.js:5
import tar from 'tar';
       ^^^
SyntaxError: The requested module 'tar' does not provide an export named 'default'
    at ModuleJob._instantiate (node:internal/modules/esm/module_job:146:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:229:5)
    at async ModuleLoader.import (node:internal/modules/esm/loader:473:24)

Node.js v20.18.1

Hosts:
file:///opt/iobroker/node_modules/@iobroker/js-controller-cli/build/esm/lib/setup/setupBackup.js:5
import tar from 'tar';
       ^^^
SyntaxError: The requested module 'tar' does not provide an export named 'default'
    at ModuleJob._instantiate (node:internal/modules/esm/module_job:146:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:229:5)
    at async ModuleLoader.import (node:internal/modules/esm/loader:473:24)

Node.js v20.18.1

Core adapters versions
file:///opt/iobroker/node_modules/@iobroker/js-controller-cli/build/esm/lib/setup/setupBackup.js:5
import tar from 'tar';
       ^^^
SyntaxError: The requested module 'tar' does not provide an export named 'default'
    at ModuleJob._instantiate (node:internal/modules/esm/module_job:146:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:229:5)
    at async ModuleLoader.import (node:internal/modules/esm/loader:473:24)

Node.js v20.18.1
js-controller:
file:///opt/iobroker/node_modules/@iobroker/js-controller-cli/build/esm/lib/setup/setupBackup.js:5
import tar from 'tar';
       ^^^
SyntaxError: The requested module 'tar' does not provide an export named 'default'
    at ModuleJob._instantiate (node:internal/modules/esm/module_job:146:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:229:5)
    at async ModuleLoader.import (node:internal/modules/esm/loader:473:24)

Node.js v20.18.1
admin:
file:///opt/iobroker/node_modules/@iobroker/js-controller-cli/build/esm/lib/setup/setupBackup.js:5
import tar from 'tar';
       ^^^
SyntaxError: The requested module 'tar' does not provide an export named 'default'
    at ModuleJob._instantiate (node:internal/modules/esm/module_job:146:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:229:5)
    at async ModuleLoader.import (node:internal/modules/esm/loader:473:24)

Node.js v20.18.1
javascript:

nodejs modules from github:     1
|   `-- xmlbuilder@0.4.2 invalid: "https://github.com/hobbyquaker/xmlbuilder-js/tarball/29fe5030dc6852007dc8d1bfd5109d75f8da58d5" from node_modules/homematic-xmlrpc

Adapter State


Enabled adapters with bindings

ioBroker-Repositories
file:///opt/iobroker/node_modules/@iobroker/js-controller-cli/build/esm/lib/setup/setupBackup.js:5
import tar from 'tar';
       ^^^
SyntaxError: The requested module 'tar' does not provide an export named 'default'
    at ModuleJob._instantiate (node:internal/modules/esm/module_job:146:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:229:5)
    at async ModuleLoader.import (node:internal/modules/esm/loader:473:24)

Node.js v20.18.1

Installed ioBroker-Instances
file:///opt/iobroker/node_modules/@iobroker/js-controller-cli/build/esm/lib/setup/setupBackup.js:5
import tar from 'tar';
       ^^^
SyntaxError: The requested module 'tar' does not provide an export named 'default'
    at ModuleJob._instantiate (node:internal/modules/esm/module_job:146:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:229:5)
    at async ModuleLoader.import (node:internal/modules/esm/loader:473:24)

Node.js v20.18.1

Objects and States
Please stand by - This may take a while
Objects:        0
States:         0

*** OS-Repositories and Updates ***
Hit:1 http://security.debian.org/debian-security stable-security InRelease
Hit:2 http://deb.debian.org/debian stable InRelease
Hit:3 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:22              0.0.0.0:*               LISTEN      0          15654      515/sshd: /usr/sbin
tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN      0          12762      1/systemd
tcp        0      0 0.0.0.0:9418            0.0.0.0:*               LISTEN      110        103270     23071/git-daemon
tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN      0          103234     22998/exim4
tcp        0      0 127.0.0.1:6379          0.0.0.0:*               LISTEN      108        15827      476/redis-server 12
tcp6       0      0 :::22                   :::*                    LISTEN      0          15664      515/sshd: /usr/sbin
tcp6       0      0 :::111                  :::*                    LISTEN      0          12768      1/systemd
tcp6       0      0 :::80                   :::*                    LISTEN      0          102711     22610/apache2
tcp6       0      0 :::9418                 :::*                    LISTEN      110        103271     23071/git-daemon
tcp6       0      0 ::1:6379                :::*                    LISTEN      108        15828      476/redis-server 12
tcp6       0      0 ::1:25                  :::*                    LISTEN      0          103235     22998/exim4
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           107        15554      465/avahi-daemon: r
udp        0      0 0.0.0.0:36253           0.0.0.0:*                           107        15556      465/avahi-daemon: r
udp        0      0 0.0.0.0:68              0.0.0.0:*                           0          14024      349/dhclient
udp        0      0 0.0.0.0:111             0.0.0.0:*                           0          12765      1/systemd
udp6       0      0 :::56189                :::*                                107        15557      465/avahi-daemon: r
udp6       0      0 :::5353                 :::*                                107        15555      465/avahi-daemon: r
udp6       0      0 :::111                  :::*                                0          12771      1/systemd

*** Log File - Last 25 Lines ***

2025-01-04 12:46:02.255  - debug: daswetter.0 (3742622) exit, all done
2025-01-04 12:46:02.255  - debug: daswetter.0 (3742622) timer killed
2025-01-04 12:46:02.255  - debug: daswetter.0 (3742622) Plugin sentry destroyed
2025-01-04 12:46:02.255  - info: daswetter.0 (3742622) Terminated (ADAPTER_REQUESTED_TERMINATION): All data handled, adapter stopped until next scheduled moment
2025-01-04 12:46:02.760  - info: daswetter.0 (3742622) cleaned everything up...
2025-01-04 12:46:02.768  - info: host.IoBroker instance system.adapter.daswetter.0 having pid 3742622 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2025-01-04 12:48:46.617  - warn: javascript.0 (1458350) You are assigning a number to the state "Meine_Geräte.0.Photovoltaik.VerfügbareLeistung" which expects a string. Please fix your code to use a string or change the state type to number. This warning might become an error in future versions.
2025-01-04 12:48:46.622  - warn: javascript.0 (1458350)     at setState (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:2090:20)
2025-01-04 12:48:46.625  - warn: javascript.0 (1458350)     at Object.<anonymous> (script.js.Meine_Geräte.Photovoltaik.Verfügbare_Leistung:3:3)
2025-01-04 12:48:46.625  - warn: javascript.0 (1458350)     at Object.callback (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1452:38)
2025-01-04 12:48:46.626  - warn: javascript.0 (1458350)     at Object.stateChange (/opt/iobroker/node_modules/iobroker.javascript/main.js:645:29)
2025-01-04 12:48:46.626  - warn: javascript.0 (1458350)     at Immediate._onImmediate (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:11048:62)
2025-01-04 12:48:46.626  - warn: javascript.0 (1458350)     at processImmediate (node:internal/timers:483:21)
2025-01-04 12:48:46.626  - warn: javascript.0 (1458350) You are assigning a number to the state "Meine_Geräte.0.Photovoltaik.VerfügbareLeistung" which expects a string. Please fix your code to use a string or change the state type to number. This warning might become an error in future versions.
2025-01-04 12:48:46.626  - warn: javascript.0 (1458350)     at setState (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:2090:20)
2025-01-04 12:48:46.626  - warn: javascript.0 (1458350)     at Object.<anonymous> (script.js.Meine_Geräte.Photovoltaik.Verfügbare_Leistung:3:3)
2025-01-04 12:48:46.626  - warn: javascript.0 (1458350)     at Object.callback (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1452:38)
2025-01-04 12:48:46.626  - warn: javascript.0 (1458350)     at Object.stateChange (/opt/iobroker/node_modules/iobroker.javascript/main.js:645:29)
2025-01-04 12:48:46.626  - warn: javascript.0 (1458350)     at Immediate._onImmediate (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:11048:62)
2025-01-04 12:48:46.626  - warn: javascript.0 (1458350)     at processImmediate (node:internal/timers:483:21)
2025-01-04 12:48:46.641  - info: javascript.0 (1458350) State value to set for "Meine_Geräte.0.Photovoltaik.VerfügbareLeistung" has to be type "string" but received type "number"
2025-01-04 12:48:46.642  - info: javascript.0 (1458350) State value to set for "Meine_Geräte.0.Photovoltaik.VerfügbareLeistung" has to be type "string" but received type "number"
2025-01-04 12:49:02.295  - error: hm-rpc.1 (1458491) Cannot call listDevices: socket hang up
2025-01-04 12:49:04.231  - info: sonoff.0 (1458585) Client [Absaugung] connection closed: closed

[markphilip]

@wendy2702

iobroker fixer läuft durch ändert allerdings nichts. Der Fehler bleibt der gleiche.

Der Syntax Fehler erscheint auch wenn ich Versuche JS Controller neu zu installieren.

[wendy2702]

@markphilip Dann zeige uns deinen Versuch den JS Controller neu zu installieren mal als log komplett mit ein und Ausgabe der Konsole

[markphilip]

@wendy2702 Ich hoffe das ist so richtig

mark@IoBroker:/opt/iobroker$ sudo -H -u iobroker npm install iobroker.js-controller
npm warn skipping integrity check for git dependency ssh://git@github.com/klein0r/ioBroker.comfoairq.git
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 @npmcli/move-file@1.1.2: This functionality has been moved to @npmcli/fs
npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
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 npmlog@6.0.2: This package is no longer supported.
npm warn deprecated @humanwhocodes/config-array@0.13.0: Use @eslint/config-array instead
npm warn deprecated har-validator@5.1.5: this library is no longer supported
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated are-we-there-yet@3.0.1: This package is no longer supported.
npm warn deprecated @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead
npm warn deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@8.1.0: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@8.1.0: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
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 deprecated google-p12-pem@4.0.1: Package is no longer maintained
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 gauge@4.0.4: This package is no longer supported.
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 deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm warn deprecated xmldom@0.1.16: Deprecated due to CVE-2021-21366 resolved in 0.5.0
npm warn deprecated sinon@15.2.0: 16.1.1
npm warn deprecated eslint@8.57.1: This version is no longer supported. Please see https://eslint.org/version-support for other options.
npm error code 1
npm error path /opt/iobroker/node_modules/iobroker.js-controller
npm error command failed
npm error command sh -c node iobroker.js setup first
npm error file:///opt/iobroker/node_modules/@iobroker/js-controller-cli/build/esm/lib/setup/setupBackup.js:5
npm error import tar from 'tar';
npm error        ^^^
npm error SyntaxError: The requested module 'tar' does not provide an export named 'default'
npm error     at ModuleJob._instantiate (node:internal/modules/esm/module_job:146:21)
npm error     at async ModuleJob.run (node:internal/modules/esm/module_job:229:5)
npm error     at async ModuleLoader.import (node:internal/modules/esm/loader:473:24)
npm error
npm error Node.js v20.18.1
npm error A complete log of this run can be found in: /home/iobroker/.npm/_logs/2025-01-04T17_51_36_141Z-debug-0.log

mark@IoBroker:/opt/iobroker$ /home/iobroker/.npm/_logs/2025-01-04T17_51_36_141Z-debug-0.log
-bash: /home/iobroker/.npm/_logs/2025-01-04T17_51_36_141Z-debug-0.log: Keine Berechtigung

[wendy2702]

Hm,

Fällt mir auf die schnelle nichts zu ein.

Vielleicht hat @Thomas-Braun eine Idee.

[Homoran]

@markphilip sagte in Syntax Error seit Stromausfall:

Der Syntax Fehler erscheint auch wenn ich Versuche JS Controller neu zu installieren

welcher Syntaxfehler?

[markphilip]

@homoran hi oben im ersten Post im Code:

 SyntaxError: The requested module 'tar' does not provide an export named 'default'
    at ModuleJob._instantiate (node:internal/modules/esm/module_job:146:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:229:5)
    at async ModuleLoader.import (node:internal/modules/esm/loader:473:24)

MOD-EDIT: Code in code-tags gesetzt!

[Homoran]

@markphilip
Achso, im iob diag.
Hatte ich mir gar nicht angesehen weil nur Summary.

laut letztem debug-log ist da noch einiges mehr kaputt, und diese Meldung wohl nur eine Folge davon

[markphilip]

@homoran ok eine Idee was ich machen kann oder soll ich das System einmal neu aufsetzen?

[Homoran]

@markphilip sagte in Syntax Error seit Stromausfall:

eine Idee was ich machen kann

leider nein, das ist weit über meinen skills.

@markphilip sagte in Syntax Error seit Stromausfall:

soll ich das System einmal neu aufsetzen?

das würde ich jetzt machen, aber vielleicht hat @thomas-braun eine Idee, oder gar Lust das zu fixen, wenn möglich.

[Ein ehemaliger Benutzer]

@markphilip

da das ne VM ist, wuerd ich einfach das letzte Backup der VM wieder einspielen.

Da hats was in deinem System geschossen.. hoffentlich ist nicht die Platte im Eimer.. hast du noch mehr VM's laufen?

[arteck]

@ALLE

liest doch mal ALLE das diag richtig

Status admin and web instance:


Objects:                0

States:                 0

da ist NIX an objekten und states.. was soll dann da laufen

@markphilip
hoffe du hast ein backup.. sonst schaumal in den iobroker-data ordner da sollte eine objects.bak und eine states.bak liegen.. und die sollten grösser sein als die entsprechenden jsonl's

sonst hilft dir nur backup zurück

[wendy2702]

@arteck soll das jetzt die Erklärung für den Syntax Fehler sein oder was?

[Ein ehemaliger Benutzer]

@wendy2702

Schlechte Laune? Geh mal an die Luft... :)

Wenn du weiter liest, siehst du, was passiert ist und warum das so ist.

[wendy2702]

@ilovegym keine schlechte Laune.

Hätte es nur gerne vernünftig erklärt wenn man schon schreibt wir würden alle nicht richtig lesen.

Vor allem warum es beim Versuch den Controller neu zu installieren immer noch zum Syntax Fehler kommt.

[Ein ehemaliger Benutzer]

@wendy2702

Nehme an, dass es das Dateisystem zerrissen hat..
das kann uns aber auch nur der TE erklären..

Vielleicht war auch schon vorher was krumm und jetzt ist es endgültig durch…

[Homoran]

@ilovegym sagte in Syntax Error seit Stromausfall:

Nehme an, dass es das Dateisystem zerrissen hat..

ich auch
Deswegen war meine Meinung

@homoran sagte in Syntax Error seit Stromausfall:

laut letztem debug-log ist da noch einiges mehr kaputt, und diese Meldung wohl nur eine Folge davon

[wendy2702]

Ja,

Dateisystem zerrissen ist gut möglich und wahrscheinlich. Mir erschließt sich nur gerade nicht wie man das an dem Status: "Objects & States" fest machen kann und was der Status "Objects & States" an der Stelle mit dem Syntax error zu tun hat.

Aber ist jetzt auch egal. Ich hoffe der TE hat ein Backup.