Neuer ioBroker-Blog online: Monatsrückblick März/April 2026

[tiobb]

@thomas-braun sagte in HILFE, kein Zugriff auf IOBroker:

@tiobb sagte in HILFE, kein Zugriff auf IOBroker:

Über die Remotedesktop Verbindung kann ich auf das abgestürzte System zugreifen

Das solltest du gar nicht können, weil auf einem gescheiten System erst gar kein Desktop läuft...

iob diag

sagt? Langfassung.

Mag sein das es nicht gescheit war (ist) aber es lief zwei Jahre ohne Probleme, und ich konnte wunderbar am PC Scripte mit dem IoBroker erstellen. Hast Du eine Idee wie ich das ganze wieder zum laufen bekomme?

[Thomas Braun]

@tiobb sagte in HILFE, kein Zugriff auf IOBroker:

Hast Du eine Idee wie ich das ganze wieder zum laufen bekomme?

Ohne deine Mithilfe in Form der Langfassung von

iob diag

nicht.

[Thomas Braun]

@tiobb sagte in HILFE, kein Zugriff auf IOBroker:

Mag sein das es nicht gescheit war (ist) aber es lief zwei Jahre ohne Probleme, und ich konnte wunderbar am PC Scripte mit dem IoBroker erstellen.

Es 'lief doch immer' ist halt keine sinnvolle Aussage. Jetzt läuft es aber nicht mehr, egal wie lange das im Vorfeld irgendwie mithumpelte. Und Skripte kann man natürlich auch ohne Desktop-Environment erstellen. Gibt ja zig Editoren für sowas.

[tiobb]

@thomas-braun sagte in HILFE, kein Zugriff auf IOBroker:

iob diag

Wie komme ich an die Langfassung? Ich hatte vor 2 Jahren gerade alles mit eurer Hilfe hinbekommen, bin aber wieder total raus aus der Materie. Ih stehe also wieder am Anfang. Hab bitte Geduld mit mir, ich bin also wieder absoluter Newbee.

[Thomas Braun]

@tiobb

iob diag

in dein Terminal hacken, Ausgabe hier rein kopieren.

[emil70]

Hier dazu sehen
https://forum.iobroker.net/topic/59549/iob-diag-skript

[tiobb]

@thomas-braun

pi@raspberrypi:~ $ iob diag
iobroker [command]

Commands:
  iobroker setup                                               Setup ioBroker
  iobroker start                                               Starts the js-controller
  iobroker stop                                                stops the js-controller
  iobroker restart                                             Restarts js-controller
  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
  iobroker install <adapter>                                   Installs a specified adapter
  iobroker rebuild <adapter>|self                              Rebuilds a specified adapter
  iobroker url <url> [<name>]                                  Install adapter from specified url, e.g. GitHub
  iobroker del <adapter>                                       Remove adapter from system
  iobroker del <adapter>.<instance>                            Remove adapter instance
  iobroker update [<repositoryUrl>]                            Update repository and list adapters
  iobroker upgrade                                             Upgrade management
  iobroker upload                                              Upload management
  iobroker object                                              Object management
  iobroker state                                               State management
  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
  iobroker repo [<name>]                                       Show repo information
  iobroker uuid                                                Show uuid of the installation
  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

Options:
      --help     Show help  [boolean]
  -v, --version  Show version  [boolean]
pi@raspberrypi:~ $ ^C

[Thomas Braun]

@tiobb

iob stop
iob fix
iob start
iob diag

[tiobb]

@thomas-braun

Skript v.2023-10-10

*** BASE SYSTEM ***
   Static hostname: raspberrypi
         Icon name: computer
  Operating System: Raspbian GNU/Linux 10 (buster)
            Kernel: Linux 5.10.52-v7l+
      Architecture: arm

Model		: Raspberry Pi 4 Model B Rev 1.4
Docker          : false
Virtualization  : none
Kernel          : armv7l
Userland        : armhf

Systemuptime and Load:
 15:52:50 up  2:11,  1 user,  load average: 0.99, 1.10, 1.15
CPU threads: 4


*** RASPBERRY THROTTLING ***
Current issues:
No throttling issues detected.

Previously detected issues:
No throttling issues detected.

*** Time and Time Zones ***
               Local time: Thu 2023-11-02 15:52:51 CET
           Universal time: Thu 2023-11-02 14:52:51 UTC
                 RTC time: n/a
                Time zone: Europe/Berlin (CET, +0100)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

*** User and Groups ***
pi
/home/pi
pi adm dialout cdrom sudo audio video plugdev games users input netdev lpadmin gpio i2c spi iobroker

*** X-Server-Setup ***
X-Server: 	true
Desktop: 	LXDE-pi
Terminal: 	x11
Boot Target: 	graphical.target

*** MEMORY ***
              total        used        free      shared  buff/cache   available
Mem:           7.9G        209M        6.9G         57M        755M        7.4G
Swap:           99M          0B         99M
Total:         8.0G        209M        7.0G

         7898 M total memory
          208 M used memory
          367 M active memory
          414 M inactive memory
         6935 M free memory
          140 M buffer memory
          614 M swap cache
           99 M total swap
            0 M used swap
           99 M free swap

Raspberry only:
oom events: 0
lifetime oom required: 0 Mbytes
total time in oom handler: 0 ms
max time spent in oom handler: 0 ms

*** FAILED SERVICES ***

  UNIT            LOAD   ACTIVE SUB    DESCRIPTION          
* lightdm.service loaded failed failed Light Display Manager

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.

1 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

*** FILESYSTEM ***
Filesystem     Type      Size  Used Avail Use% Mounted on
/dev/root      ext4       29G   13G   16G  45% /
devtmpfs       devtmpfs  3.7G     0  3.7G   0% /dev
tmpfs          tmpfs     3.9G     0  3.9G   0% /dev/shm
tmpfs          tmpfs     3.9G   41M  3.9G   2% /run
tmpfs          tmpfs     5.0M  4.0K  5.0M   1% /run/lock
tmpfs          tmpfs     3.9G     0  3.9G   0% /sys/fs/cgroup
/dev/mmcblk0p1 vfat      253M   49M  205M  20% /boot
tmpfs          tmpfs     790M  4.0K  790M   1% /run/user/1000

Messages concerning ext4 filesystem in dmesg:
[Thu Nov  2 13:41:15 2023] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1  smsc95xx.macaddr=E4:5F:01:35:E0:6E vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  console=ttyS0,115200 console=tty1 root=PARTUUID=5168531a-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
[Thu Nov  2 13:41:16 2023] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[Thu Nov  2 13:41:16 2023] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[Thu Nov  2 13:41:18 2023] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)

Show mounted filesystems \(real ones only\):
TARGET                       SOURCE         FSTYPE            OPTIONS
/                            /dev/mmcblk0p2 ext4              rw,noatime
|-/sys/fs/bpf                none           bpf               rw,nosuid,nodev,noexec,relatime,mode=700
|-/run/user/1000/gvfs        gvfsd-fuse     fuse.gvfsd-fuse   rw,nosuid,nodev,relatime,user_id=1000,group_id=1000
|-/boot                      /dev/mmcblk0p1 vfat              rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro
`-/home/pi/thinclient_drives xrdp-chansrv   fuse.xrdp-chansrv rw,nosuid,nodev,relatime,user_id=1000,group_id=1000

Files in neuralgic directories:

/var:
1.9G	/var/
1.2G	/var/cache/apt
1.2G	/var/cache
1.1G	/var/cache/apt/archives
526M	/var/log

Archived and active journals take up 40.0M in the file system.

/opt/iobroker/backups:
54M	/opt/iobroker/backups/

/opt/iobroker/iobroker-data:
505M	/opt/iobroker/iobroker-data/
337M	/opt/iobroker/iobroker-data/history
146M	/opt/iobroker/iobroker-data/files
29M	/opt/iobroker/iobroker-data/files/javascript.admin
24M	/opt/iobroker/iobroker-data/files/vis

The five largest files in iobroker-data are:
11M	/opt/iobroker/iobroker-data/files/echarts/static/js/2.d8ebf8a2.chunk.js.map
11M	/opt/iobroker/iobroker-data/files/echarts.admin/chart/static/js/2.d8ebf8a2.chunk.js.map
9.5M	/opt/iobroker/iobroker-data/files/javascript.admin/static/js/2.0ffea560.chunk.js.map
7.0M	/opt/iobroker/iobroker-data/files/echarts.admin/static/js/2.9483ccfd.chunk.js.map
4.4M	/opt/iobroker/iobroker-data/files/iot.admin/static/js/2.934fa7ad.chunk.js.map

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

/dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B001CDD4A3A-if00

*** NodeJS-Installation ***

/usr/bin/nodejs 	v12.22.5
/usr/bin/node 		v12.22.5
/usr/bin/npm 		6.14.14
/usr/bin/npx 		6.14.14
/home/iobroker/.diag.sh: line 281: corepack: command not found
 	
*** nodejs is NOT correctly installed ***

nodejs:
  Installed: 12.22.5-1nodesource1
  Candidate: 12.22.12-deb-1nodesource1
  Version table:
     12.22.12-deb-1nodesource1 500
        500 https://deb.nodesource.com/node_12.x buster/main armhf Packages
 *** 12.22.5-1nodesource1 100
        100 /var/lib/dpkg/status
     10.24.0~dfsg-1~deb10u3 500
        500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages

Temp directories causing npm8 problem: 0
No problems detected

Errors in npm tree:
npm ERR! extraneous: @babel/cli@7.15.7 /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@babel/cli
npm ERR! extraneous: @babel/preset-env@7.15.6 /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@babel/preset-env
npm ERR! extraneous: @babel/preset-typescript@7.15.0 /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@babel/preset-typescript
npm ERR! extraneous: @types/debounce@1.2.1 /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@types/debounce
npm ERR! extraneous: @types/debug@4.1.7 /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@types/debug
npm ERR! extraneous: @types/jest@27.0.2 /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@types/jest
npm ERR! extraneous: @types/mz@2.7.4 /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@types/mz
npm ERR! extraneous: @types/nedb@1.8.12 /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@types/nedb
npm ERR! extraneous: @types/serialport@8.0.2 /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@types/serialport
npm ERR! extraneous: @typescript-eslint/eslint-plugin@4.31.2 /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@typescript-eslint/eslint-plugin
npm ERR! extraneous: @typescript-eslint/parser@4.31.2 /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@typescript-eslint/parser
npm ERR! extraneous: eslint@7.32.0 /opt/iobroker/node_modules/zigbee-herdsman/node_modules/eslint
npm ERR! extraneous: jest@27.2.2 /opt/iobroker/node_modules/zigbee-herdsman/node_modules/jest
npm ERR! extraneous: typedoc@0.22.4 /opt/iobroker/node_modules/zigbee-herdsman/node_modules/typedoc
npm ERR! extraneous: typedoc-plugin-markdown@3.11.2 /opt/iobroker/node_modules/zigbee-herdsman/node_modules/typedoc-plugin-markdown
npm ERR! extraneous: typedoc-plugin-no-inherit@1.3.0 /opt/iobroker/node_modules/zigbee-herdsman/node_modules/typedoc-plugin-no-inherit
npm ERR! extraneous: typedoc-plugin-sourcefile-url@1.0.6 /opt/iobroker/node_modules/zigbee-herdsman/node_modules/typedoc-plugin-sourcefile-url
npm ERR! extraneous: typescript@4.4.3 /opt/iobroker/node_modules/zigbee-herdsman/node_modules/typescript
npm ERR! extraneous: eslint@7.32.0 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/eslint
npm ERR! extraneous: eslint-config-google@0.14.0 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/eslint-config-google
npm ERR! extraneous: eslint-plugin-jest@24.4.2 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/eslint-plugin-jest
npm ERR! extraneous: jest@27.2.2 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/jest
npm ERR! extraneous: @babel/cli@7.15.4 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/@babel/cli
npm ERR! extraneous: @babel/preset-env@7.15.6 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/@babel/preset-env
npm ERR! extraneous: @babel/preset-typescript@7.15.0 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/@babel/preset-typescript
npm ERR! extraneous: @types/debounce@1.2.0 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/@types/debounce
npm ERR! extraneous: @types/debug@4.1.7 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/@types/debug
npm ERR! extraneous: @types/jest@27.0.1 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/@types/jest
npm ERR! extraneous: @types/mz@2.7.4 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/@types/mz
npm ERR! extraneous: @types/nedb@1.8.12 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/@types/nedb
npm ERR! extraneous: @types/serialport@8.0.2 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/@types/serialport
npm ERR! extraneous: @typescript-eslint/eslint-plugin@4.31.0 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/@typescript-eslint/eslint-plugin
npm ERR! extraneous: @typescript-eslint/parser@4.31.0 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/@typescript-eslint/parser
npm ERR! extraneous: eslint@7.32.0 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/eslint
npm ERR! extraneous: jest@27.1.1 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/jest
npm ERR! extraneous: typedoc@0.22.3 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/typedoc
npm ERR! extraneous: typedoc-plugin-markdown@3.10.4 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/typedoc-plugin-markdown
npm ERR! extraneous: typedoc-plugin-no-inherit@1.3.0 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/typedoc-plugin-no-inherit
npm ERR! extraneous: typedoc-plugin-sourcefile-url@1.0.6 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/typedoc-plugin-sourcefile-url
npm ERR! extraneous: typescript@4.4.3 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/typescript

*** ioBroker-Installation ***

ioBroker Status
 Cannot read system.config: null (OK when migrating or restoring)
 Cannot read system.config: null (OK when migrating or restoring)
iobroker is not running on this host.


Objects type: file
States  type: file

Core adapters versions
js-controller: 	3.3.15
admin: 		5.1.23
javascript: 	5.2.8

npm ERR! extraneous: @babel/cli@7.15.7 /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@babel/cli
npm ERR! extraneous: @babel/preset-env@7.15.6 /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@babel/preset-env
npm ERR! extraneous: @babel/preset-typescript@7.15.0 /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@babel/preset-typescript
npm ERR! extraneous: @types/debounce@1.2.1 /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@types/debounce
npm ERR! extraneous: @types/debug@4.1.7 /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@types/debug
npm ERR! extraneous: @types/jest@27.0.2 /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@types/jest
npm ERR! extraneous: @types/mz@2.7.4 /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@types/mz
npm ERR! extraneous: @types/nedb@1.8.12 /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@types/nedb
npm ERR! extraneous: @types/serialport@8.0.2 /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@types/serialport
npm ERR! extraneous: @typescript-eslint/eslint-plugin@4.31.2 /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@typescript-eslint/eslint-plugin
npm ERR! extraneous: @typescript-eslint/parser@4.31.2 /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@typescript-eslint/parser
npm ERR! extraneous: eslint@7.32.0 /opt/iobroker/node_modules/zigbee-herdsman/node_modules/eslint
npm ERR! extraneous: jest@27.2.2 /opt/iobroker/node_modules/zigbee-herdsman/node_modules/jest
npm ERR! extraneous: typedoc@0.22.4 /opt/iobroker/node_modules/zigbee-herdsman/node_modules/typedoc
npm ERR! extraneous: typedoc-plugin-markdown@3.11.2 /opt/iobroker/node_modules/zigbee-herdsman/node_modules/typedoc-plugin-markdown
npm ERR! extraneous: typedoc-plugin-no-inherit@1.3.0 /opt/iobroker/node_modules/zigbee-herdsman/node_modules/typedoc-plugin-no-inherit
npm ERR! extraneous: typedoc-plugin-sourcefile-url@1.0.6 /opt/iobroker/node_modules/zigbee-herdsman/node_modules/typedoc-plugin-sourcefile-url
npm ERR! extraneous: typescript@4.4.3 /opt/iobroker/node_modules/zigbee-herdsman/node_modules/typescript
npm ERR! extraneous: eslint@7.32.0 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/eslint
npm ERR! extraneous: eslint-config-google@0.14.0 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/eslint-config-google
npm ERR! extraneous: eslint-plugin-jest@24.4.2 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/eslint-plugin-jest
npm ERR! extraneous: jest@27.2.2 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/jest
npm ERR! extraneous: @babel/cli@7.15.4 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/@babel/cli
npm ERR! extraneous: @babel/preset-env@7.15.6 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/@babel/preset-env
npm ERR! extraneous: @babel/preset-typescript@7.15.0 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/@babel/preset-typescript
npm ERR! extraneous: @types/debounce@1.2.0 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/@types/debounce
npm ERR! extraneous: @types/debug@4.1.7 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/@types/debug
npm ERR! extraneous: @types/jest@27.0.1 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/@types/jest
npm ERR! extraneous: @types/mz@2.7.4 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/@types/mz
npm ERR! extraneous: @types/nedb@1.8.12 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/@types/nedb
npm ERR! extraneous: @types/serialport@8.0.2 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/@types/serialport
npm ERR! extraneous: @typescript-eslint/eslint-plugin@4.31.0 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/@typescript-eslint/eslint-plugin
npm ERR! extraneous: @typescript-eslint/parser@4.31.0 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/@typescript-eslint/parser
npm ERR! extraneous: eslint@7.32.0 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/eslint
npm ERR! extraneous: jest@27.1.1 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/jest
npm ERR! extraneous: typedoc@0.22.3 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/typedoc
npm ERR! extraneous: typedoc-plugin-markdown@3.10.4 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/typedoc-plugin-markdown
npm ERR! extraneous: typedoc-plugin-no-inherit@1.3.0 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/typedoc-plugin-no-inherit
npm ERR! extraneous: typedoc-plugin-sourcefile-url@1.0.6 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/typedoc-plugin-sourcefile-url
npm ERR! extraneous: typescript@4.4.3 /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/typescript
Adapters from github: 	4

Adapter State
 Cannot read system.config: null (OK when migrating or restoring)
 Cannot read system.config: null (OK when migrating or restoring)


+ instance is alive

Enabled adapters with bindings

ioBroker-Repositories
 Cannot read system.config: null (OK when migrating or restoring)
Cannot get list: undefined

Installed ioBroker-Instances
 Cannot read system.config: null (OK when migrating or restoring)
Error: Object "system.config" not found
 Cannot read system.config: null (OK when migrating or restoring)
 Cannot read system.config: null (OK when migrating or restoring)
 Cannot read system.config: null (OK when migrating or restoring)
 Cannot read system.config: null (OK when migrating or restoring)
 Cannot read system.config: null (OK when migrating or restoring)
 Cannot read system.config: null (OK when migrating or restoring)
 Cannot read system.config: null (OK when migrating or restoring)
 Cannot read system.config: null (OK when migrating or restoring)
 Cannot read system.config: null (OK when migrating or restoring)
 Cannot read system.config: null (OK when migrating or restoring)
 Cannot read system.config: null (OK when migrating or restoring)
 Cannot read system.config: null (OK when migrating or restoring)

Ab hier passiert immer das das gleiche "cannot read system.config

[Thomas Braun]

@tiobb sagte in HILFE, kein Zugriff auf IOBroker:

*** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION * lightdm.service loaded failed failed Light Display Manager

Der Fehler kann nur beim Desktop auftreten. Schalt dem Mumpitz aus!

sudo systemctl set-default multi-user.target
sudo reboot

Und dann per SSH auf die Kiste drauf.

[Thomas Braun]

@tiobb

nodejs is NOT correctly installed

Und STEINalt.

iob nodejs-update

[Thomas Braun]

@tiobb

js-controller: 	3.3.15

Noch viel älter...
Die Baustelle wird immer mehr zu: Abreißen, neubauen.

[Thomas Braun]

@tiobb

Jetzt hast du solange dein 'System never getatscht' bis da halt nix mehr 'runnt'.

Versuch ein Upgrade des js-controllers:

https://forum.iobroker.net/topic/68290/js-controller-5-0-x-jetzt-für-alle-user-im-stable

[tiobb]

@thomas-braun

Updates laufen.

Abgestürzt ist alles nach einem Stromausfall.

Gibt es eine Möglichkeit alles vom IoBroker irgendwie zu kopieren und in das Backup auf der anderen Speicherkarte zu übertragen?

[Thomas Braun]

@tiobb sagte in HILFE, kein Zugriff auf IOBroker:

Gibt es eine Möglichkeit alles vom IoBroker irgendwie zu kopieren und in das Backup auf der anderen Speicherkarte zu übertragen?

Nein. Jedenfalls nicht mit zu vertretenem Aufwand.

[tiobb]

@thomas-braun

Ok, hätte ja sein können das es einen "Ordner" gibt, in dem z.B. die Scripte abgelegt sind, und die man dann hätte per copy paste in das Backup einspielen können.

[Thomas Braun]

@tiobb sagte in HILFE, kein Zugriff auf IOBroker:

Da ich davon ausgehe, das du auch selbstverständlich kein Spiegelverzeichnis für die Skripte hast...

Es gibt ein Skript von @fastfoot , mit dem man Skripte rauskratzen kann. Ob das mit kaputten Installationen parat kommt weiß ich allerdings nicht.

[haselchen]

@thomas-braun

Ganz zu schweigen vom toten Buster OS

@tiobb

[Thomas Braun]

Updates und Backups sind immer nur für andere. Man selber braucht die nicht.

[tiobb]

@thomas-braun
@haselchen

Ich habe ja ein Backup, aber leider viel zu alt, da fehlen bestimmt 10 Scripte, von denen ich leider heute nicht mehr weiß wie ich sie neu schreiben soll