Uralt System Updaten ohne Expertenwissen

MAHRULEZ

======== Start marking the full check here =========

Skript v.2023-10-10

*** BASE SYSTEM ***
   Static hostname: MAHTV
         Icon name: computer
  Operating System: Raspbian GNU/Linux 9 (stretch)
            Kernel: Linux 4.19.66-v7+
      Architecture: arm

model name      : ARMv7 Processor rev 4 (v7l)
Docker          : false
Virtualization  : none
Kernel          : armv7l
Userland        : armhf

Systemuptime and Load:
 11:42:10 up 37 min,  2 users,  load average: 0.72, 1.71, 1.18
CPU threads: 4


*** RASPBERRY THROTTLING ***
Current issues:
~ Under-voltage detected

Previously detected issues:
~ Under-voltage has occurred

*** Time and Time Zones ***
      Local time: Tue 2023-12-05 11:42:10 CET
  Universal time: Tue 2023-12-05 10:42:10 UTC
        RTC time: n/a
       Time zone: Europe/Berlin (CET, +0100)
 Network time on: yes
NTP synchronized: yes
 RTC in local TZ: no

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

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

*** MEMORY ***
              total        used        free      shared  buff/cache   available
Mem:           895M        549M         64M         10M        281M        309M
Swap:          102M        102M         24K
Total:         997M        651M         64M

          874 M total memory
          536 M used memory
          344 M active memory
          401 M inactive memory
           63 M free memory
            9 M buffer memory
          265 M swap cache
           99 M total swap
           99 M used swap
            0 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 ***

0 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       28G  9.5G   17G  37% /
devtmpfs       devtmpfs  433M     0  433M   0% /dev
tmpfs          tmpfs     438M   12K  438M   1% /dev/shm
tmpfs          tmpfs     438M  6.0M  432M   2% /run
tmpfs          tmpfs     5.0M  4.0K  5.0M   1% /run/lock
tmpfs          tmpfs     438M     0  438M   0% /sys/fs/cgroup
/dev/mmcblk0p6 vfat       66M   23M   44M  35% /boot
tmpfs          tmpfs      88M     0   88M   0% /run/user/1000
/dev/sda7      ext4       28G  9.0G   17G  35% /media/pi/root
/dev/sda6      vfat       66M   23M   44M  35% /media/pi/boot
/dev/sda5      ext4       30M  802K   27M   3% /media/pi/SETTINGS2
/dev/mmcblk0p5 ext4       30M  802K   27M   3% /media/pi/SETTINGS3

Messages concerning ext4 filesystem in dmesg:
[Tue Dec  5 11:04:29 2023] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 bcm2708_fb.fbwidth=1920 bcm2708_fb.fbheight=1080 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=/dev/mmcblk0p7 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
[Tue Dec  5 11:04:30 2023] EXT4-fs (mmcblk0p7): mounted filesystem with ordered data mode. Opts: (null)
[Tue Dec  5 11:04:30 2023] VFS: Mounted root (ext4 filesystem) readonly on device 179:7.
[Tue Dec  5 11:04:32 2023] EXT4-fs (mmcblk0p7): re-mounted. Opts: (null)
[Tue Dec  5 11:04:48 2023] EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: errors=remount-ro
[Tue Dec  5 11:04:49 2023] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: errors=remount-ro
[Tue Dec  5 11:04:49 2023] EXT4-fs (mmcblk0p5): mounted filesystem with ordered data mode. Opts: errors=remount-ro

Show mounted filesystems \(real ones only\):
findmnt: unrecognized option '--real'

Usage:
 findmnt [options]
 findmnt [options] <device> | <mountpoint>
 findmnt [options] <device> <mountpoint>
 findmnt [options] [--source <device>] [--target <path> | --mountpoint <dir>]

Find a (mounted) filesystem.

Options:
 -s, --fstab            search in static table of filesystems
 -m, --mtab             search in table of mounted filesystems
 -k, --kernel           search in kernel table of mounted
                          filesystems (default)

 -p, --poll[=<list>]    monitor changes in table of mounted filesystems
 -w, --timeout <num>    upper limit in milliseconds that --poll will block

 -A, --all              disable all built-in filters, print all filesystems
 -a, --ascii            use ASCII chars for tree formatting
 -b, --bytes            print sizes in bytes rather than in human readable format
 -C, --nocanonicalize   don't canonicalize when comparing paths
 -c, --canonicalize     canonicalize printed paths
 -D, --df               imitate the output of df(1)
 -d, --direction <word> direction of search, 'forward' or 'backward'
 -e, --evaluate         convert tags (LABEL,UUID,PARTUUID,PARTLABEL)
                          to device names
 -F, --tab-file <path>  alternative file for -s, -m or -k options
 -f, --first-only       print the first found filesystem only
 -i, --invert           invert the sense of matching
 -J, --json             use JSON output format
 -l, --list             use list format output
 -N, --task <tid>       use alternative namespace (/proc/<tid>/mountinfo file)
 -n, --noheadings       don't print column headings
 -O, --options <list>   limit the set of filesystems by mount options
 -o, --output <list>    the output columns to be shown
 -P, --pairs            use key="value" output format
 -R, --submounts        print all submounts for the matching filesystems
 -r, --raw              use raw output format
 -S, --source <string>  the device to mount (by name, maj:min,
                          LABEL=, UUID=, PARTUUID=, PARTLABEL=)
 -T, --target <path>    the path to the filesystem to use
 -M, --mountpoint <dir> the mountpoint directory
 -t, --types <list>     limit the set of filesystems by FS types
 -U, --uniq             ignore filesystems with duplicate target
 -u, --notruncate       don't truncate text in columns
 -v, --nofsroot         don't print [/dir] for bind or btrfs mounts

 -x, --verify           verify mount table content (default is fstab)
     --verbose          print more details


 -h, --help     display this help and exit
 -V, --version  output version information and exit

Available columns:
      SOURCE  source device
      TARGET  mountpoint
      FSTYPE  filesystem type
     OPTIONS  all mount options
 VFS-OPTIONS  VFS specific mount options
  FS-OPTIONS  FS specific mount options
       LABEL  filesystem label
        UUID  filesystem UUID
   PARTLABEL  partition label
    PARTUUID  partition UUID
     MAJ:MIN  major:minor device number
      ACTION  action detected by --poll
  OLD-TARGET  old mountpoint saved by --poll
 OLD-OPTIONS  old mount options saved by --poll
        SIZE  filesystem size
       AVAIL  filesystem size available
        USED  filesystem size used
        USE%  filesystem use percentage
      FSROOT  filesystem root
         TID  task ID
          ID  mount ID
  OPT-FIELDS  optional mount fields
 PROPAGATION  VFS propagation flags
        FREQ  dump(8) period in days [fstab only]
      PASSNO  pass number on parallel fsck(8) [fstab only]

For more details see findmnt(8).

Files in neuralgic directories:

/var:
2.1G    /var/
1.5G    /var/cache/apt/archives
1.5G    /var/cache/apt
1.5G    /var/cache
234M    /var/log

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

/opt/iobroker/backups:
47M     /opt/iobroker/backups/

/opt/iobroker/iobroker-data:
526M    /opt/iobroker/iobroker-data/
408M    /opt/iobroker/iobroker-data/node-red
405M    /opt/iobroker/iobroker-data/node-red/node_modules
90M     /opt/iobroker/iobroker-data/node-red/node_modules/electron
89M     /opt/iobroker/iobroker-data/node-red/node_modules/electron/dist

The five largest files in iobroker-data are:
50M     /opt/iobroker/iobroker-data/node-red/node_modules/electron/dist/electron
14M     /opt/iobroker/iobroker-data/objects.jsonl
14M     /opt/iobroker/iobroker-data/node-red/node_modules/electron/dist/libnode.so
9.9M    /opt/iobroker/iobroker-data/node-red/node_modules/electron/dist/content_shell.pak
9.7M    /opt/iobroker/iobroker-data/node-red/node_modules/electron/dist/icudtl.dat

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

find: '/dev/serial/by-id/': No such file or directory

*** NodeJS-Installation ***

/usr/bin/nodejs         v16.20.2
/usr/local/bin/node             v14.16.0
/usr/local/bin/npm              6.14.11
/usr/local/bin/npx              6.14.11
/usr/bin/corepack       0.17.0
*** nodejs is NOT correctly installed ***

nodejs:
  Installed: 16.20.2-1nodesource1
  Candidate: 16.20.2-1nodesource1
  Version table:
 *** 16.20.2-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages
        100 /var/lib/dpkg/status
     16.20.1-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages
     16.20.0-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages
     16.19.1-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages
     16.19.0-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages
     16.18.1-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages
     16.18.0-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages
     16.17.1-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages
     16.17.0-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages
     16.16.0-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages
     16.15.1-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages
     16.15.0-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages
     16.14.2-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages
     16.14.1-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages
     16.14.0-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages
     16.13.2-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages
     16.13.1-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages
     16.13.0-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages
     16.12.0-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages
     16.11.1-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages
     16.11.0-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages
     16.10.0-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages
     16.9.1-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages
     16.9.0-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages
     16.8.0-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages
     16.7.0-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages
     16.6.2-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages
     16.6.1-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages
     16.6.0-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages
     16.5.0-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages
     16.4.2-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages
     16.4.1-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages
     16.4.0-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages
     16.3.0-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages
     16.2.0-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages
     16.1.0-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages
     16.0.0-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages
     8.11.1~dfsg-2~bpo9+1 500
        500 http://archive.raspberrypi.org/debian stretch/main armhf Packages
     4.8.2~dfsg-1 500
        500 http://raspbian.raspberrypi.org/raspbian stretch/main armhf Packages
     4.8.2~dfsg-1 500
        500 http://archive.debian.org/debian stretch/main armhf 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:  4.0.21
admin:          5.3.1
javascript:     "javascript" not found

Adapters from github:   2

Adapter State
+ system.adapter.admin.0                  : admin                 : MAHTV                                    -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
+ system.adapter.alexa2.0                 : alexa2                : MAHTV                                    -  enabled
+ system.adapter.backitup.0               : backitup              : MAHTV                                    -  enabled
+ system.adapter.bring.0                  : bring                 : MAHTV                                    -  enabled
+ system.adapter.discovery.0              : discovery             : MAHTV                                    -  enabled
+ system.adapter.email.0                  : email                 : MAHTV                                    -  enabled
+ system.adapter.homepilot20.0            : homepilot20           : MAHTV                                    -  enabled
+ system.adapter.info.0                   : info                  : MAHTV                                    -  enabled
+ system.adapter.nina.0                   : nina                  : MAHTV                                    -  enabled
+ system.adapter.node-red.0               : node-red              : MAHTV                                    -  enabled, port: 1880, bind: 0.0.0.0
  system.adapter.tuya.0                   : tuya                  : MAHTV                                    - disabled

+ instance is alive

Enabled adapters with bindings
+ system.adapter.admin.0                  : admin                 : MAHTV                                    -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
+ system.adapter.node-red.0               : node-red              : MAHTV                                    -  enabled, port: 1880, bind: 0.0.0.0

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.12.0   , installed 5.3.1  [Updatable]
Adapter    "alexa2"       : 3.26.3   , installed 3.11.2 [Updatable]
Adapter    "backitup"     : 2.8.7    , installed 2.3.3  [Updatable]
Adapter    "bring"        : 1.8.4    , installed 1.7.13 [Updatable]
Adapter    "discovery"    : 4.2.0    , installed 2.7.5  [Updatable]
Adapter    "email"        : 1.2.0    , installed 1.0.10 [Updatable]
Adapter    "homepilot"    : 1.1.6    , installed 1.1.6
Adapter    "info"         : 2.0.0    , installed 1.9.8  [Updatable]
Controller "js-controller": 5.0.16   , installed 4.0.21 [Updatable]
Adapter    "netatmo"      : 3.1.0    , installed 3.1.0
Adapter    "nina"         : 0.0.25   , installed 0.0.25
Adapter    "node-red"     : 4.0.3    , installed 2.4.2  [Updatable]
Adapter    "tuya"         : 3.14.2   , installed 3.6.15 [Updatable]

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

*** OS-Repositories and Updates ***
E: The repository 'http://raspbian.raspberrypi.org/raspbian stretch Release' does no longer have a Release file.
W: GPG error: http://archive.debian.org/debian stretch Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 04EE7237B7D453EC NO_PUBKEY 648ACFD622F3D138 NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY EF0F382A1A7B6500
W: The repository 'http://archive.debian.org/debian stretch Release' is not signed.
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:9000          0.0.0.0:*               LISTEN      1001       36240      4242/iobroker.js-co
tcp        0      0 127.0.0.1:9001          0.0.0.0:*               LISTEN      1001       32735      4242/iobroker.js-co
tcp        0      0 0.0.0.0:5900            0.0.0.0:*               LISTEN      0          14398      454/vncserver-x11-c
tcp        0      0 127.0.0.1:5940          0.0.0.0:*               LISTEN      0          13728      724/teamviewerd
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      0          12003      718/sshd
tcp        0      0 0.0.0.0:1880            0.0.0.0:*               LISTEN      1001       40234      4350/node-red
tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN      0          13093      750/exim4
tcp6       0      0 :::5900                 :::*                    LISTEN      0          14397      454/vncserver-x11-c
tcp6       0      0 :::8081                 :::*                    LISTEN      1001       37314      4297/io.admin.0
tcp6       0      0 :::22                   :::*                    LISTEN      0          12005      718/sshd
tcp6       0      0 ::1:25                  :::*                    LISTEN      0          13094      750/exim4
tcp6       0      0 :::1883                 :::*                    LISTEN      1001       41509      4350/node-red
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           108        11711      372/avahi-daemon: r
udp        0      0 0.0.0.0:46393           0.0.0.0:*                           108        11713      372/avahi-daemon: r
udp        0      0 0.0.0.0:68              0.0.0.0:*                           0          11932      398/dhcpcd
udp6       0      0 :::5353                 :::*                                108        11712      372/avahi-daemon: r
udp6       0      0 :::40863                :::*                                108        11714      372/avahi-daemon: r

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

2023-12-05 11:36:46.785  - warn: info.0 (4392) Object info.0.sysinfo.cpu.currentLoad.currentLoadUser is invalid: obj.common.min has an invalid type! Expected "number", received "string"
2023-12-05 11:36:46.787  - warn: info.0 (4392) This object will not be created in future versions. Please report this to the developer.
2023-12-05 11:36:46.880  - warn: info.0 (4392) Object info.0.sysinfo.cpu.currentLoad.currentLoadSystem is invalid: obj.common.min has an invalid type! Expected "number", received "string"
2023-12-05 11:36:46.882  - warn: info.0 (4392) This object will not be created in future versions. Please report this to the developer.
2023-12-05 11:36:46.968  - warn: info.0 (4392) Object info.0.sysinfo.cpu.currentLoad.currentLoadNice is invalid: obj.common.min has an invalid type! Expected "number", received "string"
2023-12-05 11:36:46.971  - warn: info.0 (4392) This object will not be created in future versions. Please report this to the developer.
2023-12-05 11:36:47.038  - warn: info.0 (4392) Object info.0.sysinfo.cpu.currentLoad.currentLoadIdle is invalid: obj.common.min has an invalid type! Expected "number", received "string"
2023-12-05 11:36:47.041  - warn: info.0 (4392) This object will not be created in future versions. Please report this to the developer.
2023-12-05 11:36:47.147  - warn: info.0 (4392) Object info.0.sysinfo.cpu.currentLoad.currentLoadIrq is invalid: obj.common.min has an invalid type! Expected "number", received "string"
2023-12-05 11:36:47.149  - warn: info.0 (4392) This object will not be created in future versions. Please report this to the developer.
2023-12-05 11:36:48.173  - info: host.MAHTV instance system.adapter.bring.0 started with pid 4478
2023-12-05 11:37:21.441  - warn: node-red.0 (4308) 5 Dec 11:37:21 - [warn] Projekte deaktiviert: editorTheme.projects.enabled=false

2023-12-05 11:37:21.530  - warn: node-red.0 (4350) slow connection to objects DB. Still waiting ...
2023-12-05 11:37:31.315  - warn: node-red.0 (4308) 5 Dec 11:37:31 - [warn] [device-node:60c1c89a.a69148] Authentication Pending or error in user credentials. - On Startup

2023-12-05 11:37:31.320  - warn: node-red.0 (4308) 5 Dec 11:37:31 - [warn] [device-node:96c1f83d.c7b878] Authentication Pending or error in user credentials. - On Startup
Smartlife Air: Auth Object
{"apiKey":"AIzaSyBnbSCjJ9eQtAMl_CHRSJxelF5XG8UlLjU","authDomain":"smartlife-air.firebaseapp.com","appName":"[DEFAULT]","currentUser":null}

2023-12-05 11:37:40.936  - warn: node-red.0 (4350) slow connection to states DB. Still waiting ...
2023-12-05 11:42:29.268  - warn: node-red.0 (4308) 5 Dec 11:42:29 - [warn] [telegram sender:18568bfd.4012c4] msg.payload.type is empty

2023-12-05 11:42:29.275  - warn: node-red.0 (4308) 5 Dec 11:42:29 - [warn] [telegram sender:18568bfd.4012c4] msg.payload.type is empty

============ Mark until here for C&P =============

iob diag has finished.

Press any key for a summary
Copy text starting here:

======================= SUMMARY =======================
                        v.2023-10-10


   Static hostname: MAHTV
         Icon name: computer
  Operating System: Raspbian GNU/Linux 9 (stretch)
            Kernel: Linux 4.19.66-v7+
      Architecture: arm

Installation:           native
Kernel:                 armv7l
Userland:               armhf
Timezone:               rlin (CET, +0100)
User-ID:                1000
X-Server:               true
Boot Target:            graphical.target

Pending OS-Updates:     0
Pending iob updates:    10

Nodejs-Installation:    /usr/bin/nodejs         v16.20.2
                        /usr/local/bin/node             v14.16.0
                        /usr/local/bin/npm              6.14.11
                        /usr/local/bin/npx              6.14.11
                        /usr/bin/corepack       0.17.0

Recommended versions are nodejs No connection to databases possible ... and npm
*** nodejs is NOT correctly installed ***
Wrong installation path detected. This needs to be fixed.

Please check
https://forum.iobroker.net/topic/35090/howto-nodejs-installation-und-upgrades-unter-debian
for more information on how to fix these errors.

MEMORY:
              total        used        free      shared  buff/cache   available
Mem:           895M        560M         52M         10M        282M        282M
Swap:          102M        102M          0B
Total:         997M        662M         52M

Active iob-Instances:   11
Active repo(s): stable

ioBroker Core:          js-controller           4.0.21
                        admin                   5.3.1

ioBroker Status:        iobroker is running on this host.


Objects type: jsonl
States  type: jsonl

Status admin and web instance:
+ system.adapter.admin.0                  : admin                 : MAHTV                                    -  enabled, port: 8081, bind: 0.0.0.0, run as: admin

Objects:                8968
States:                 8292

Size of iob-Database:

14M     /opt/iobroker/iobroker-data/objects.jsonl
6.4M    /opt/iobroker/iobroker-data/objects.json.migrated
6.4M    /opt/iobroker/iobroker-data/objects.json.bak.migrated
4.0M    /opt/iobroker/iobroker-data/states.jsonl
1.6M    /opt/iobroker/iobroker-data/states.json.migrated
1.6M    /opt/iobroker/iobroker-data/states.json.bak.migrated



=================== END OF SUMMARY ====================

=== Mark text until here for copying ===

Thomas Braun

@mahrulez

iob nodejs-update 16

Was aktuelleres gibt es für Stretch nicht mehr.
Dann den ioBroker soweit wie es geht auf Stand bringen, Backup ziehen und mit dem Backup auf ein frisch installiertes Betriebssystem umziehen.

Codierknecht

@thomas-braun sagte in Uralt System Updaten ohne Expertenwissen:

auf ein frisch installiertes Betriebssystem umziehen

@MAHRULEZ
Kleine Ergänzung: Auf dem neuen OS keinen Desktop installieren!

Thomas Braun

@codierknecht

Das sowieso.

@MAHRULEZ

https://forum.iobroker.net/topic/51869/installation-auf-raspi-einfacher-geht-s-nicht

paul53

@thomas-braun sagte: ioBroker soweit wie es geht auf Stand bringen

Dann wird der RAM nicht mehr ausreichen.

Thomas Braun

@paul53

Wird eng. X-Server ausknipsen...
Auf der anderen Seite sind es nur 11 Instanzen.

Homoran

@paul53 10 Instanzen und ohne Desktop könnte gut gehen

Codierknecht

@homoran
Und "discovery" könnte man auch noch wegwerfen.
Ansonsten die eine oder andere Instanz noch stoppen.

@MAHRULEZ
Du solltest vielleicht auch die Anschaffung etwas potenterer Hardware in Betracht ziehen.

MAHRULEZ

@thomas-braun

Vielen Dank!
Das scheint funktioniert zu haben.
Leider kommt aber nun in der Konsole beim Aufruf von:
node -v
-bash: /usr/local/bin/node: Datei oder Verzeichnis nicht gefunden
Kann man das irgendwie noch fixen?

Für eine Rückmeldung bedanke ich mich schon jetzt!
BTW:
Ja potentere Hardware liegt bereit, leider fehlt momentan die Zeit alles von Grund auf neu einzurichten. Ob eine einfache Portierung von iobroker und nodered möglich ist (quasi kopieren) weiß ich nicht.

Thomas Braun

@mahrulez sagte in Uralt System Updaten ohne Expertenwissen:

Kann man das irgendwie noch fixen?

Starte mal sauber neu.

sudo reboot

Und ich würde da ein anderes Netzteil verwenden. Deines ist zu wackelig.

Thomas Braun

@mahrulez sagte in Uralt System Updaten ohne Expertenwissen:

Ob eine einfache Portierung von iobroker und nodered möglich ist (quasi kopieren) weiß ich nicht.

Dafür gibt es den Backitup-Adapter.
Bei NodeRed musste mal schauen wie man da ein Backup zieht.

Marc Berg

@thomas-braun sagte in Uralt System Updaten ohne Expertenwissen:

Dafür gibt es den Backitup-Adapter.

Angesichts der Ressourcenknappheit würde sich vielleicht eher die Kommadozeile anbieten, oder?

iob backup

iob restore <Dateiname>

Bei NodeRed musste mal schauen wie man da ein Backup zieht.

Die NodeRed Flows sind im normalen ioBroker Backup enthalten. Zusätzliche Module, die über die "Palette" hinzugefügt wurden, muss man ggf. manuell nochmals in Nodered installieren.

Thomas Braun

@marc-berg sagte in Uralt System Updaten ohne Expertenwissen:

Angesichts der Ressourcenknappheit würde sich vielleicht eher die Kommadozeile anbieten, oder?

Natürlich. Da wurde ich aber zunächst auch den ganzen X-Server inkl. VNC und Teamviewer kicken, was ja auf der Kiste gerade auch noch mitrumpelt.

Community Forum

NEWS

Uralt System Updaten ohne Expertenwissen

Support us

720

32.6k

82.2k

1.3m