Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. BackItUp: Mount-Error, danach kein weiterer Backup-Versuch

    NEWS

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    BackItUp: Mount-Error, danach kein weiterer Backup-Versuch

    This topic has been deleted. Only users with topic management privileges can see it.
    • AlexAtHome
      AlexAtHome last edited by

      Ich habe gerade festgestellt, dass der BackItUp-Adapter am 05.12.23 beim Sichern aufs NAS auf einen Mount-Fehler gelaufen ist, und danach anscheinend die Arbeit eingestellt hat.
      Da leider die iobroker-Logs nur bis zum 11.12.23 zurückreichen, kann ich nicht nachsehen, was da passiert ist.

      Was mich sehr verwundert: es gab anschließend keinen weiteren Versuch mehr, ein Backup zu erstellen.
      Ich habe die verfügbaren zurückliegenden Logs durchsucht: es ist kein Eintrag des Adapters "backitup" vorhanden.
      Der Adapter selbst ist grün. Ein manuelles Backup-Schreiben via Adapter war vorhin problemlos möglich.

      Meine Erwartungshaltung ist, dass der Adapter zum nächsten anstehenden periodischen Backup-Zeitpunkt (bei mir alle 2 Tage) wieder ein Backup erstellt. Das wäre dann am 07.12.23 gewesen.

      Das ist das erste Mal, dass der Adapter auf ein Problem beim Sichern gelaufen ist, normalerweise funzt das alles sehr smooth.

      R 1 Reply Last reply Reply Quote 0
      • R
        reutli @AlexAtHome last edited by

        @alexathome

        Wenn Du hier Antworten haben möchtest, solltest Du schon ein bisschen mehr Infos liefern:

        • Einstellungen des Backitup Adapters (Bildschirmfotos)
        • Aktuelle Versionen des Adapters
        • Vielleicht ein iob diag in Langfassung
        • Mount point
          ...

        siehe auch https://forum.iobroker.net/topic/51555/hinweise-für-gute-forenbeiträge/1

        AlexAtHome 1 Reply Last reply Reply Quote 0
        • AlexAtHome
          AlexAtHome @reutli last edited by

          @reutli
          Vielen Dank für Deine schnelle Antwort!
          Ich bin davon ausgegangen, dass zur Beantwortung der Frage: müsste der Adapter nicht beim nächsten scheduled Backup-Zeitpunkt einen Backup-Versuch starten, nicht meine gesamte Konfig benötigt würde. Denn das war ja eher eine gerelle Frage.

          Aber es stimmt natürlich, um konkret zu meinem Fall Hilfe zu erhalten, sind Detail-Infos notwendig:

          BackItUp-Adapter-Version: 2.8.7

          Einstellungen:
          BackItUp_Config04.png BackItUp_Config03.png BackItUp_Config02.png BackItUp_Config01.png

          BackItUp-Info:
          BackItUp_Status.png

          Diag-Summary:

          • dazu folgende Anmerkung: ich habe vorhin ein Update des Systems durchgeführt:
            NodeJS von 18.18.2 auf 18.19.0, npm von 9.8.1 auf 10.2.3, JS-Controller von 5.0.16 auf 5.0.17.
            Zum Zeitpunkt des Problems waren also jew die vorherigen Versionen aktiv. Ich hoffe, das verhindert jetzt nicht die Diagnose.
          ======================= SUMMARY =======================
                                  v.2023-10-10
          
             Static hostname: iobroker-server
                   Icon name: computer-desktop
                     Chassis: desktop
            Operating System: Debian GNU/Linux 11 (bullseye)
                      Kernel: Linux 5.10.0-25-amd64
                Architecture: x86-64
          
          Installation:           native
          Kernel:                 x86_64
          Userland:               amd64
          Timezone:               Europe/Berlin (CET, +0100)
          User-ID:                1000
          X-Server:               true
          Boot Target:            graphical.target
          
          Pending OS-Updates:     0
          Pending iob updates:    0
          
          This system needs to be REBOOTED NOW!
          
          Nodejs-Installation:    /usr/bin/nodejs         v18.19.0
                                  /usr/bin/node           v18.19.0
                                  /usr/bin/npm            10.2.3
                                  /usr/bin/npx            10.2.3
                                  /usr/bin/corepack       0.22.0
          
          Recommended versions are nodejs 18.19.0 and npm 10.2.3
          Your nodejs installation is correct
          
          MEMORY:
                         total        used        free      shared  buff/cache   available
          Mem:            7.6G        1.3G        1.4G         17M        4.8G        5.9G
          Swap:           2.0G          0B        2.0G
          Total:          9.6G        1.3G        3.4G
          
          Active iob-Instances:   12
          Active repo(s): stable
          
          ioBroker Core:          js-controller           5.0.17
                                  admin                   6.12.0
          
          ioBroker Status:        iobroker is running on this host.
          
          Objects type: jsonl
          States  type: jsonl
          
          Status admin and web instance:
          + system.adapter.admin.0                  : admin                 : iobroker-server                          -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
          + system.adapter.web.0                    : web                   : iobroker-server                          -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
          
          Objects:                5406
          States:                 4309
          
          Size of iob-Database:
          
          11M     /opt/iobroker/iobroker-data/objects.jsonl
          4.9M    /opt/iobroker/iobroker-data/states.jsonl
          
          =================== END OF SUMMARY ====================
          

          Den im diag angemerkten Reboot mache ich jetzt noch.

          AlexAtHome 1 Reply Last reply Reply Quote 0
          • AlexAtHome
            AlexAtHome @AlexAtHome last edited by

            Diag-Langfassung nach Reboot:

            Skript v.2023-10-10
            
            *** BASE SYSTEM ***
               Static hostname: iobroker-server
                     Icon name: computer-desktop
                       Chassis: desktop
              Operating System: Debian GNU/Linux 11 (bullseye)
                        Kernel: Linux 5.10.0-26-amd64
                  Architecture: x86-64
            
            model name      : Intel(R) Pentium(R) CPU G3220 @ 3.00GHz
            Docker          : false
            Virtualization  : none
            Kernel          : x86_64
            Userland        : amd64
            
            Systemuptime and Load:
             13:09:44 up 5 min,  1 user,  load average: 0.03, 0.24, 0.15
            CPU threads: 2
            
            
            *** Time and Time Zones ***
                           Local time: Sun 2023-12-17 13:09:44 CET
                       Universal time: Sun 2023-12-17 12:09:44 UTC
                             RTC time: Sun 2023-12-17 12:09:44
                            Time zone: Europe/Berlin (CET, +0100)
            System clock synchronized: yes
                          NTP service: n/a
                      RTC in local TZ: no
            
            *** User and Groups ***
            iobuser
            /home/iobuser
            iobuser cdrom floppy sudo audio dip video plugdev netdev bluetooth lpadmin scanner iobroker
            
            *** X-Server-Setup ***
            X-Server:       true
            Desktop:
            Terminal:       tty
            Boot Target:    graphical.target
            
            *** MEMORY ***
                           total        used        free      shared  buff/cache   available
            Mem:            7.6G        1.1G        6.1G         17M        395M        6.2G
            Swap:           2.0G          0B        2.0G
            Total:          9.6G        1.1G        8.0G
            
                     7600 M total memory
                     1129 M used memory
                      144 M active memory
                     1191 M inactive memory
                     6075 M free memory
                       40 M buffer memory
                      355 M swap cache
                     1952 M total swap
                        0 M used swap
                     1952 M free swap
            
            *** FAILED SERVICES ***
            
              UNIT LOAD ACTIVE SUB DESCRIPTION
            0 loaded units listed.
            
            *** FILESYSTEM ***
            Filesystem                            Type      Size  Used Avail Use% Mounted on
            udev                                  devtmpfs  3.7G     0  3.7G   0% /dev
            tmpfs                                 tmpfs     761M  872K  760M   1% /run
            /dev/mapper/iobroker--server--vg-root ext4      274G  7.0G  253G   3% /
            tmpfs                                 tmpfs     3.8G     0  3.8G   0% /dev/shm
            tmpfs                                 tmpfs     5.0M  4.0K  5.0M   1% /run/lock
            /dev/sda2                             ext2      471M  114M  333M  26% /boot
            /dev/sda1                             vfat      511M  5.8M  506M   2% /boot/efi
            tmpfs                                 tmpfs     761M   36K  761M   1% /run/user/113
            tmpfs                                 tmpfs     761M   32K  761M   1% /run/user/1000
            
            Messages concerning ext4 filesystem in dmesg:
            [Sun Dec 17 13:04:18 2023] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
            [Sun Dec 17 13:04:21 2023] EXT4-fs (dm-0): re-mounted. Opts: errors=remount-ro
            [Sun Dec 17 13:04:24 2023] EXT4-fs (sda2): mounting ext2 file system using the ext4 subsystem
            [Sun Dec 17 13:04:24 2023] EXT4-fs (sda2): mounted filesystem without journal. Opts: (null)
            
            Show mounted filesystems \(real ones only\):
            TARGET        SOURCE                                FSTYPE OPTIONS
            /             /dev/mapper/iobroker--server--vg-root ext4   rw,relatime,errors=remount-ro
            `-/boot       /dev/sda2                             ext2   rw,relatime,stripe=4
              `-/boot/efi /dev/sda1                             vfat   rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro
            
            Files in neuralgic directories:
            
            /var:
            772M    /var/
            486M    /var/log
            449M    /var/log/journal/e4601f564dbf4c87945fd3ccb37ebd9a
            449M    /var/log/journal
            201M    /var/lib
            
            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 80.0M in the file system.
            
            /opt/iobroker/backups:
            10M     /opt/iobroker/backups/
            
            /opt/iobroker/iobroker-data:
            255M    /opt/iobroker/iobroker-data/
            191M    /opt/iobroker/iobroker-data/files
            67M     /opt/iobroker/iobroker-data/files/javascript.admin
            50M     /opt/iobroker/iobroker-data/backup-objects
            48M     /opt/iobroker/iobroker-data/files/javascript.admin/static
            
            The five largest files in iobroker-data are:
            33M     /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.1797d034.js.map
            21M     /opt/iobroker/iobroker-data/files/web.admin/static/js/main.aaea95f8.js.map
            13M     /opt/iobroker/iobroker-data/objects.jsonl
            8.5M    /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.1797d034.js
            8.3M    /opt/iobroker/iobroker-data/files/web.admin/static/js/main.aaea95f8.js
            
            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         v18.19.0
            /usr/bin/node           v18.19.0
            /usr/bin/npm            10.2.3
            /usr/bin/npx            10.2.3
            /usr/bin/corepack       0.22.0
            
            
            nodejs:
              Installed: 18.19.0-1nodesource1
              Candidate: 18.19.0-1nodesource1
              Version table:
             *** 18.19.0-1nodesource1 1001
                    500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
                    100 /var/lib/dpkg/status
                 18.18.2-1nodesource1 1001
                    500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
                 18.18.1-1nodesource1 1001
                    500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
                 18.18.0-1nodesource1 1001
                    500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
                 18.17.1-1nodesource1 1001
                    500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
                 18.17.0-1nodesource1 1001
                    500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
                 18.16.1-1nodesource1 1001
                    500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
                 18.16.0-1nodesource1 1001
                    500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
                 18.15.0-1nodesource1 1001
                    500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
                 18.14.2-1nodesource1 1001
                    500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
                 18.14.1-1nodesource1 1001
                    500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
                 18.14.0-1nodesource1 1001
                    500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
                 18.13.0-1nodesource1 1001
                    500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
                 18.12.0-1nodesource1 1001
                    500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
                 18.11.0-1nodesource1 1001
                    500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
                 18.10.0-1nodesource1 1001
                    500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
                 18.9.1-1nodesource1 1001
                    500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
                 18.9.0-1nodesource1 1001
                    500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
                 18.8.0-1nodesource1 1001
                    500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
                 18.7.0-1nodesource1 1001
                    500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
                 18.6.0-1nodesource1 1001
                    500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
                 18.5.0-1nodesource1 1001
                    500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
                 18.4.0-1nodesource1 1001
                    500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
                 18.3.0-1nodesource1 1001
                    500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
                 18.2.0-1nodesource1 1001
                    500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
                 18.1.0-1nodesource1 1001
                    500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
                 18.0.0-1nodesource1 1001
                    500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
                 12.22.12~dfsg-1~deb11u4 500
                    500 http://deb.debian.org/debian bullseye/main amd64 Packages
                    500 http://security.debian.org/debian-security bullseye-security/main amd64 Packages
            
            Temp directories causing npm8 problem: 0
            No problems detected
            
            Errors in npm tree:
            
            *** ioBroker-Installation ***
            
            ioBroker Status
            iobroker is running on this host.
            
            
            Objects type: jsonl
            States  type: jsonl
            
            Core adapters versions
            js-controller:  5.0.17
            admin:          6.12.0
            javascript:     7.1.6
            
            Adapters from github:   1
            
            Adapter State
            + system.adapter.admin.0                  : admin                 : iobroker-server                          -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
            + system.adapter.alexa2.0                 : alexa2                : iobroker-server                          -  enabled
              system.adapter.alias-manager.0          : alias-manager         : iobroker-server                          -  enabled
            + system.adapter.backitup.0               : backitup              : iobroker-server                          -  enabled
            + system.adapter.hmip.0                   : hmip                  : iobroker-server                          -  enabled
            + system.adapter.iot.0                    : iot                   : iobroker-server                          -  enabled
            + system.adapter.javascript.0             : javascript            : iobroker-server                          -  enabled
            + system.adapter.logparser.0              : logparser             : iobroker-server                          -  enabled
            + system.adapter.ping.0                   : ping                  : iobroker-server                          -  enabled
              system.adapter.vis-hqwidgets.0          : vis-hqwidgets         : iobroker-server                          -  enabled
            + system.adapter.vis-inventwo.0           : vis-inventwo          : iobroker-server                          -  enabled
              system.adapter.vis.0                    : vis                   : iobroker-server                          -  enabled
            + system.adapter.web.0                    : web                   : iobroker-server                          -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
            + system.adapter.zigbee.0                 : zigbee                : iobroker-server                          -  enabled, port: tcp://192.168.178.23:6638
              system.adapter.zigbee.1                 : zigbee                : iobroker-server                          - disabled, port: /dev/ttyACM0
            
            + instance is alive
            
            Enabled adapters with bindings
            + system.adapter.admin.0                  : admin                 : iobroker-server                          -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
            + system.adapter.web.0                    : web                   : iobroker-server                          -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
            + system.adapter.zigbee.0                 : zigbee                : iobroker-server                          -  enabled, port: tcp://192.168.178.23:6638
            
            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 6.12.0
            Adapter    "alexa2"       : 3.26.3   , installed 3.26.3
            Adapter    "alias-manager": 1.2.6    , installed 1.2.6
            Adapter    "backitup"     : 2.8.7    , installed 2.8.7
            Adapter    "hmip"         : 1.20.0   , installed 1.20.0
            Adapter    "iot"          : 2.0.11   , installed 2.0.11
            Adapter    "javascript"   : 7.1.6    , installed 7.1.6
            Controller "js-controller": 5.0.17   , installed 5.0.17
            Adapter    "logparser"    : 2.2.0    , installed 2.2.0
            Adapter    "ping"         : 1.6.2    , installed 1.6.2
            Adapter    "simple-api"   : 2.7.2    , installed 2.7.2
            Adapter    "socketio"     : 6.6.0    , installed 6.6.0
            Adapter    "vis"          : 1.5.4    , installed 1.5.4
            Adapter    "vis-hqwidgets": 1.4.0    , installed 1.4.0
            Adapter    "vis-inventwo" : 3.3.3    , installed 3.3.3
            Adapter    "web"          : 6.1.10   , installed 6.1.10
            Adapter    "ws"           : 2.5.8    , installed 2.5.8
            Adapter    "zigbee"       : 1.8.24   , installed 1.8.24
            
            Objects and States
            Please stand by - This may take a while
            Objects:        5770
            States:         4672
            
            *** OS-Repositories and Updates ***
            Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
            Hit:2 http://deb.debian.org/debian bullseye InRelease
            Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
            Hit:4 https://deb.nodesource.com/node_18.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 127.0.0.1:631           0.0.0.0:*               LISTEN      0          15586      476/cupsd
            tcp        0      0 127.0.0.1:9000          0.0.0.0:*               LISTEN      1001       16208      477/iobroker.js-con
            tcp        0      0 127.0.0.1:9001          0.0.0.0:*               LISTEN      1001       16201      477/iobroker.js-con
            tcp        0      0 0.0.0.0:36013           0.0.0.0:*               LISTEN      115        18261      833/rpc.statd
            tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN      0          11795      1/init
            tcp        0      0 127.0.0.1:53            0.0.0.0:*               LISTEN      0          14930      405/connmand
            tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      0          14906      556/sshd: /usr/sbin
            tcp6       0      0 ::1:631                 :::*                    LISTEN      0          15585      476/cupsd
            tcp6       0      0 :::59145                :::*                    LISTEN      115        18266      833/rpc.statd
            tcp6       0      0 :::111                  :::*                    LISTEN      0          11799      1/init
            tcp6       0      0 :::8081                 :::*                    LISTEN      1001       16271      691/io.admin.0
            tcp6       0      0 :::8082                 :::*                    LISTEN      1001       19645      920/io.web.0
            tcp6       0      0 ::1:53                  :::*                    LISTEN      0          14934      405/connmand
            tcp6       0      0 :::22                   :::*                    LISTEN      0          14908      556/sshd: /usr/sbin
            udp        0      0 0.0.0.0:56943           0.0.0.0:*                           0          15971      405/connmand
            udp        0      0 127.0.0.1:53            0.0.0.0:*                           0          14922      405/connmand
            udp        0      0 0.0.0.0:68              0.0.0.0:*                           0          14826      454/dhclient
            udp        0      0 0.0.0.0:111             0.0.0.0:*                           0          11796      1/init
            udp        0      0 0.0.0.0:631             0.0.0.0:*                           0          15875      564/cups-browsed
            udp        0      0 127.0.0.1:1009          0.0.0.0:*                           0          18255      833/rpc.statd
            udp        0      0 0.0.0.0:5353            0.0.0.0:*                           108        14839      402/avahi-daemon: r
            udp        0      0 0.0.0.0:47216           0.0.0.0:*                           115        18259      833/rpc.statd
            udp        0      0 0.0.0.0:59524           0.0.0.0:*                           108        14841      402/avahi-daemon: r
            udp6       0      0 :::57378                :::*                                108        14842      402/avahi-daemon: r
            udp6       0      0 ::1:53                  :::*                                0          14926      405/connmand
            udp6       0      0 :::111                  :::*                                0          11802      1/init
            udp6       0      0 :::49820                :::*                                115        18263      833/rpc.statd
            udp6       0      0 :::5353                 :::*                                108        14840      402/avahi-daemon: r
            
            *** Log File - Last 25 Lines ***
            
            2023-12-17 13:05:24.483  - info: vis.0 (900) starting. Version 1.5.4 in /opt/iobroker/node_modules/iobroker.vis, node: v18.19.0, js-controller: 5.0.17
            2023-12-17 13:05:25.593  - info: vis.0 (900) Terminated (NO_ERROR): Without reason
            2023-12-17 13:05:26.205  - info: host.iobroker-server instance system.adapter.vis.0 terminated while should be started once
            2023-12-17 13:05:27.801  - info: host.iobroker-server instance system.adapter.web.0 started with pid 920
            2023-12-17 13:05:28.682  - info: web.0 (920) starting. Version 6.1.10 in /opt/iobroker/node_modules/iobroker.web, node: v18.19.0, js-controller: 5.0.17
            2023-12-17 13:05:28.968  - info: web.0 (920) socket.io server listening on port 8082
            2023-12-17 13:05:28.971  - info: web.0 (920) http server listening on port 8082
            2023-12-17 13:05:31.929  - info: host.iobroker-server instance system.adapter.vis-inventwo.0 started with pid 935
            2023-12-17 13:05:32.529  - info: vis-inventwo.0 (935) starting. Version 3.3.3 in /opt/iobroker/node_modules/iobroker.vis-inventwo, node: v18.19.0, js-controller: 5.0.17
            2023-12-17 13:05:34.548  - info: javascript.0 (714) script.js.Wohnzimmer.NachHauseKommen_LeuchtenAn: *** Start Script NachHauseKommen; Trigger=AlexHandy - Wert=true
            2023-12-17 13:05:34.550  - info: javascript.0 (714) script.js.Wohnzimmer.NachHauseKommen_LeuchtenAn: *** Sonne ist noch nicht untergegangen
            2023-12-17 13:05:34.960  - warn: zigbee.0 (767) DeviceAvailability:Failed to ping 0x7cb03eaa0a06980d Plug 01
            2023-12-17 13:05:46.623  - info: javascript.0 (714) Stop script script.js.Sonstiges.BackItUp-Ueberwachung
            2023-12-17 13:05:47.358  - warn: zigbee.0 (767) DeviceAvailability:Failed to ping 0x7cb03eaa0a092d71 Plug 01
            2023-12-17 13:05:48.370  - info: alexa2.0 (725) No smart home devices to query
            2023-12-17 13:05:50.182  - info: alexa2.0 (725) Subscribing to states...
            2023-12-17 13:05:50.187  - info: alexa2.0 (725) Deleting the following states: ["Smart-Home-Devices.0d32852a-ff0a-442e-8e56-3d1afeb369dc","Smart-Home-Devices.194b284b-3c49-47ee-9b5d-69f51b2f4259","Smart-Home-Devices.1e537cbb-80e8-4ece-9fcb-6ae4a3b19892","Smart-Home-Devices.4cc2eb36-c835-488b-8aa7-f6512cb260a2","Smart-Home-Devices.4d9f8eba-1808-40c6-bb3b-a8d6d9062273","Smart-Home-Devices.4f91d8ca-d178-4d1b-84bc-481916bd0a2e","Smart-Home-Devices.502c28e1-04f2-4d83-8bcc-7641e899b030","Smart-Home-Devices.5a73eb76-329d-474c-a300-26cd03e720c2","Smart-Home-Devices.5b94a8f5-861f-402b-ac45-543154600b58","Smart-Home-Devices.5da2a85c-0698-4122-8d3e-4180c40f4455","Smart-Home-Devices.6e79fa2a-a57e-4bc3-bb50-f1ddb8017c86","Smart-Home-Devices.71f0e32e-bfb9-4ecf-a1e5-7e7f024181df","Smart-Home-Devices.7ac33c7f-3787-4c60-bdf3-295461c28077","Smart-Home-Devices.85b1811e-2f30-41a9-93cd-9c6fd72a2a60","Smart-Home-Devices.890b035e-80e4-452c-80c8-f0777c2a4bf5","Smart-Home-Devices.92dfd0be-b187-4dd9-b9ec-b0898993385f","Smart-Home-Devices.9e2f950a-e0fc-41fc-8554-b9e4dea4d191","Smart-Home-Devices.a000cc7e-ac77-4b9e-9a5f-ab433e8fb216","Smart-Home-Devices.ad2fa5da-5a3b-4e22-a62f-115345be83b4","Smart-Home-Devices.aded8dc5-0276-4b31-8668-1811a24ff4a3","Smart-Home-Devices.b43332bd-51cd-4f68-b68d-54fadde29229","Smart-Home-Devices.befc2137-c5e9-45d0-9d4e-a1e670423e78","Smart-Home-Devices.c26a07fa-8dea-4814-96d3-3e0f3c165561","Smart-Home-Devices.c4313c53-fbae-4614-bf62-175798240de9","Smart-Home-Devices.d1603500-1870-419e-a799-14047959d833","Smart-Home-Devices.e0636d46-9740-4c58-a9d6-8cf6e8b2f6ea","Smart-Home-Devices.e616b4a2-cea2-4c3c-a531-54db01380f14","Smart-Home-Devices.e99a9808-0e35-4488-a855-a96e8fe87e5f","Smart-Home-Devices.f1016ae0-99a0-46d7-8fb5-b12c1bbc19b3","Smart-Home-Devices.f77ccab8-a621-4cd9-bd99-f77885a4b4d8","Smart-Home-Devices.1f120d5b-6146-43f5-a997-fab5ad9d8443","Smart-Home-Devices.00402326-e834-491a-bfe1-5c8705bbb1cb","Smart-Home-Devices.151c2665-8904-44f8-9267-755a8bd4f211","Smart-Home-Devices.6f323bff-23b0-411d-be96-da0ab7634ebe","Smart-Home-Devices.1503e486-40a8-449b-91c9-f8ce9687211f","Smart-Home-Devices.e5d518a6-eaec-468b-8b11-7bc1e6ad0cf2","Smart-Home-Devices.ee47b4bc-7f15-4c6b-af0e-8861e5665c58","Smart-Home-Devices.b40fc1c9-b51a-47ef-a763-3ad853eebd6f","Smart-Home-Devices.0d32852a-ff0a-442e-8e56-3d1afeb369dc.#delete","Smart-Home-Devices.0d32852a-ff0a-442e-8e56-3d1afeb369dc.#enabled","Smart-Home-Devices.0d32852a-ff0a-442e-8e56-3d1afeb369dc.powerState","Smart-Home-Devices.194b284b-3c49-47ee-9b5d-69f51b2f4259.#delete","Smart-Home-Devices.194b284b-3c49-47ee-9b5d-69f51b2f4259.#enabled","Smart-Home-Devices.194b284b-3c49-47ee-9b5d-69f51b2f4259.powerState","Smart-Home-Devices.1e537cbb-80e8-4ece-9fcb-6ae4a3b19892.#delete","Smart-Home-Devices.1e537cbb-80e8-4ece-9fcb-6ae4a3b19892.#enabled","Smart-Home-Devices.1e537cbb-80e8-4ece-9fcb-6ae4a3b19892.color-brightness","Smart-Home-Devices.1e537cbb-80e8-4ece-9fcb-6ae4a3b19892.color-hue","Smart-Home-Devices.1e537cbb-80e8-4ece-9fcb-6ae4a3b19892.color-saturation","Smart-Home-Devices.1e537cbb-80e8-4ece-9fcb-6ae4a3b19892.colorName","Smart-Home-Devices.1e537cbb-80e8-4ece-9fcb-6ae4a3b19892.colorRgb","Smart-Home-Devices.1e537cbb-80e8-4ece-9fcb-6ae4a3b19892.percentage","Smart-Home-Devices.1e537cbb-80e8-4ece-9fcb-6ae4a3b19892.powerState","Smart-Home-Devices.4cc2eb36-c835-488b-8aa7-f6512cb260a2.#delete","Smart-Home-Devices.4cc2eb36-c835-488b-8aa7-f6512cb260a2.#enabled","Smart-Home-Devices.4cc2eb36-c835-488b-8aa7-f6512cb260a2.powerState","Smart-Home-Devices.4d9f8eba-1808-40c6-bb3b-a8d6d9062273.#delete","Smart-Home-Devices.4d9f8eba-1808-40c6-bb3b-a8d6d9062273.#enabled","Smart-Home-Devices.4d9f8eba-1808-40c6-bb3b-a8d6d9062273.powerState","Smart-Home-Devices.4f91d8ca-d178-4d1b-84bc-481916bd0a2e.#delete","Smart-Home-Devices.4f91d8ca-d178-4d1b-84bc-481916bd0a2e.#enabled","Smart-Home-Devices.4f91d8ca-d178-4d1b-84bc-481916bd0a2e.percentage","Smart-Home-Devices.4f91d8ca-d178-4d1b-84bc-481916bd0a2e.powerState","Smart-Home-Devices.502c28e1-04f2-4d83-8bcc-7641e899b030.#delete","Smart-Home-Devices.502c28e1-04f2-4d83-8bcc-7641e899b030.#enabled","Smart-Home-Devices.502c28e1-04f2-4d83-8bcc-7641e899b030.powerState","Smart-Home-Devices.5a73eb76-329d-474c-a300-26cd03e720c2.#delete","Smart-Home-Devices.5a73eb76-329d-474c-a300-26cd03e720c2.#enabled","Smart-Home-Devices.5a73eb76-329d-474c-a300-26cd03e720c2.powerState","Smart-Home-Devices.5b94a8f5-861f-402b-ac45-543154600b58.#delete","Smart-Home-Devices.5b94a8f5-861f-402b-ac45-543154600b58.#enabled","Smart-Home-Devices.5b94a8f5-861f-402b-ac45-543154600b58.powerState","Smart-Home-Devices.5da2a85c-0698-4122-8d3e-4180c40f4455.#delete","Smart-Home-Devices.5da2a85c-0698-4122-8d3e-4180c40f4455.#enabled","Smart-Home-Devices.5da2a85c-0698-4122-8d3e-4180c40f4455.color-brightness","Smart-Home-Devices.5da2a85c-0698-4122-8d3e-4180c40f4455.color-hue","Smart-Home-Devices.5da2a85c-0698-4122-8d3e-4180c40f4455.color-saturation","Smart-Home-Devices.5da2a85c-0698-4122-8d3e-4180c40f4455.colorName","Smart-Home-Devices.5da2a85c-0698-4122-8d3e-4180c40f4455.colorRgb","Smart-Home-Devices.5da2a85c-0698-4122-8d3e-4180c40f4455.percentage","Smart-Home-Devices.5da2a85c-0698-4122-8d3e-4180c40f4455.powerState","Smart-Home-Devices.6e79fa2a-a57e-4bc3-bb50-f1ddb8017c86.#delete","Smart-Home-Devices.6e79fa2a-a57e-4bc3-bb50-f1ddb8017c86.#enabled","Smart-Home-Devices.6e79fa2a-a57e-4bc3-bb50-f1ddb8017c86.powerState","Smart-Home-Devices.71f0e32e-bfb9-4ecf-a1e5-7e7f024181df.#delete","Smart-Home-Devices.71f0e32e-bfb9-4ecf-a1e5-7e7f024181df.#enabled","Smart-Home-Devices.71f0e32e-bfb9-4ecf-a1e5-7e7f024181df.powerState","Smart-Home-Devices.7ac33c7f-3787-4c60-bdf3-295461c28077.#delete","Smart-Home-Devices.7ac33c7f-3787-4c60-bdf3-295461c28077.#enabled","Smart-Home-Devices.7ac33c7f-3787-4c60-bdf3-295461c28077.powerState","Smart-Home-Devices.85b1811e-2f30-41a9-93cd-9c6fd72a2a60.#delete","Smart-Home-Devices.85b1811e-2f30-41a9-93cd-9c6fd72a2a60.#enabled","Smart-Home-Devices.85b1811e-2f30-41a9-93cd-9c6fd72a2a60.powerState","Smart-Home-Devices.890b035e-80e4-452c-80c8-f0777c2a4bf5.#delete","Smart-Home-Devices.890b035e-80e4-452c-80c8-f0777c2a4bf5.#enabled","Smart-Home-Devices.890b035e-80e4-452c-80c8-f0777c2a4bf5.powerState","Smart-Home-Devices.92dfd0be-b187-4dd9-b9ec-b0898993385f.#delete","Smart-Home-Devices.92dfd0be-b187-4dd9-b9ec-b0898993385f.#enabled","Smart-Home-Devices.92dfd0be-b187-4dd9-b9ec-b0898993385f.powerState","Smart-Home-Devices.9e2f950a-e0fc-41fc-8554-b9e4dea4d191.#delete","Smart-Home-Devices.9e2f950a-e0fc-41fc-8554-b9e4dea4d191.#enabled","Smart-Home-Devices.9e2f950a-e0fc-41fc-8554-b9e4dea4d191.color-brightness","Smart-Home-Devices.9e2f950a-e0fc-41fc-8554-b9e4dea4d191.color-hue","Smart-Home-Devices.9e2f950a-e0fc-41fc-8554-b9e4dea4d191.color-saturation","Smart-Home-Devices.9e2f950a-e0fc-41fc-8554-b9e4dea4d191.colorName","Smart-Home-Devices.9e2f950a-e0fc-41fc-8554-b9e4dea4d191.colorRgb","Smart-Home-Devices.9e2f950a-e0fc-41fc-8554-b9e4dea4d191.percentage","Smart-Home-Devices.9e2f950a-e0fc-41fc-8554-b9e4dea4d191.powerState","Smart-Home-Devices.a000cc7e-ac77-4b9e-9a5f-ab433e8fb216.#delete","Smart-Home-Devices.a000cc7e-ac77-4b9e-9a5f-ab433e8fb216.#enabled","Smart-Home-Devices.a000cc7e-ac77-4b9e-9a5f-ab433e8fb216.powerState","Smart-Home-Devices.ad2fa5da-5a3b-4e22-a62f-115345be83b4.#delete","Smart-Home-Devices.ad2fa5da-5a3b-4e22-a62f-115345be83b4.#enabled","Smart-Home-Devices.ad2fa5da-5a3b-4e22-a62f-115345be83b4.color-brightness","Smart-Home-Devices.ad2fa5da-5a3b-4e22-a62f-115345be83b4.color-hue","Smart-Home-Devices.ad2fa5da-5a3b-4e22-a62f-115345be83b4.color-saturation","Smart-Home-Devices.ad2fa5da-5a3b-4e22-a62f-115345be83b4.colorName","Smart-Home-Devices.ad2fa5da-5a3b-4e22-a62f-115345be83b4.colorRgb","Smart-Home-Devices.ad2fa5da-5a3b-4e22-a62f-115345be83b4.percentage","Smart-Home-Devices.ad2fa5da-5a3b-4e22-a62f-115345be83b4.powerState","Smart-Home-Devices.aded8dc5-0276-4b31-8668-1811a24ff4a3.#delete","Smart-Home-Devices.aded8dc5-0276-4b31-8668-1811a24ff4a3.#enabled","Smart-Home-Devices.aded8dc5-0276-4b31-8668-1811a24ff4a3.powerState","Smart-Home-Devices.b43332bd-51cd-4f68-b68d-54fadde29229.#delete","Smart-Home-Devices.b43332bd-51cd-4f68-b68d-54fadde29229.#enabled","Smart-Home-Devices.b43332bd-51cd-4f68-b68d-54fadde29229.powerState","Smart-Home-Devices.befc2137-c5e9-45d0-9d4e-a1e670423e78.#delete","Smart-Home-Devices.befc2137-c5e9-45d0-9d4e-a1e670423e78.#enabled","Smart-Home-Devices.befc2137-c5e9-45d0-9d4e-a1e670423e78.powerState","Smart-Home-Devices.c26a07fa-8dea-4814-96d3-3e0f3c165561.#delete","Smart-Home-Devices.c26a07fa-8dea-4814-96d3-3e0f3c165561.#enabled","Smart-Home-Devices.c26a07fa-8dea-4814-96d3-3e0f3c165561.powerState","Smart-Home-Devices.c4313c53-fbae-4614-bf62-175798240de9.#delete","Smart-Home-Devices.c4313c53-fbae-4614-bf62-175798240de9.#enabled","Smart-Home-Devices.c4313c53-fbae-4614-bf62-175798240de9.powerState","Smart-Home-Devices.d1603500-1870-419e-a799-14047959d833.#delete","Smart-Home-Devices.d1603500-1870-419e-a799-14047959d833.#enabled","Smart-Home-Devices.d1603500-1870-419e-a799-14047959d833.powerState","Smart-Home-Devices.e0636d46-9740-4c58-a9d6-8cf6e8b2f6ea.#delete","Smart-Home-Devices.e0636d46-9740-4c58-a9d6-8cf6e8b2f6ea.powerState","Smart-Home-Devices.e616b4a2-cea2-4c3c-a531-54db01380f14.#delete","Smart-Home-Devices.e616b4a2-cea2-4c3c-a531-54db01380f14.#enabled","Smart-Home-Devices.e616b4a2-cea2-4c3c-a531-54db01380f14.powerState","Smart-Home-Devices.e99a9808-0e35-4488-a855-a96e8fe87e5f.#delete","Smart-Home-Devices.e99a9808-0e35-4488-a855-a96e8fe87e5f.#enabled","Smart-Home-Devices.e99a9808-0e35-4488-a855-a96e8fe87e5f.powerState","Smart-Home-Devices.f1016ae0-99a0-46d7-8fb5-b12c1bbc19b3.#delete","Smart-Home-Devices.f1016ae0-99a0-46d7-8fb5-b12c1bbc19b3.#enabled","Smart-Home-Devices.f1016ae0-99a0-46d7-8fb5-b12c1bbc19b3.powerState","Smart-Home-Devices.f77ccab8-a621-4cd9-bd99-f77885a4b4d8.#delete","Smart-Home-Devices.f77ccab8-a621-4cd9-bd99-f77885a4b4d8.#enabled","Smart-Home-Devices.f77ccab8-a621-4cd9-bd99-f77885a4b4d8.powerState","Smart-Home-Devices.1f120d5b-6146-43f5-a997-fab5ad9d8443.#enabled","Smart-Home-Devices.1f120d5b-6146-43f5-a997-fab5ad9d8443.#delete","Smart-Home-Devices.1f120d5b-6146-43f5-a997-fab5ad9d8443.powerState","Smart-Home-Devices.00402326-e834-491a-bfe1-5c8705bbb1cb.#enabled","Smart-Home-Devices.00402326-e834-491a-bfe1-5c8705bbb1cb.#delete","Smart-Home-Devices.00402326-e834-491a-bfe1-5c8705bbb1cb.powerState","Smart-Home-Devices.151c2665-8904-44f8-9267-755a8bd4f211.#enabled","Smart-Home-Devices.151c2665-8904-44f8-9267-755a8bd4f211.#delete","Smart-Home-Devices.151c2665-8904-44f8-9267-755a8bd4f211.powerState","Smart-Home-Devices.151c2665-8904-44f8-9267-755a8bd4f211.colorName","Smart-Home-Devices.151c2665-8904-44f8-9267-755a8bd4f211.color-hue","Smart-Home-Devices.151c2665-8904-44f8-9267-755a8bd4f211.color-saturation","Smart-Home-Devices.151c2665-8904-44f8-9267-755a8bd4f211.color-brightness","Smart-Home-Devices.151c2665-8904-44f8-9267-755a8bd4f211.colorRgb","Smart-Home-Devices.151c2665-8904-44f8-9267-755a8bd4f211.percentage","Smart-Home-Devices.6f323bff-23b0-411d-be96-da0ab7634ebe.#enabled","Smart-Home-Devices.6f323bff-23b0-411d-be96-da0ab7634ebe.#delete","Smart-Home-Devices.6f323bff-23b0-411d-be96-da0ab7634ebe.powerState","Smart-Home-Devices.6f323bff-23b0-411d-be96-da0ab7634ebe.colorName","Smart-Home-Devices.6f323bff-23b0-411d-be96-da0ab7634ebe.color-hue","Smart-Home-Devices.6f323bff-23b0-411d-be96-da0ab7634ebe.color-saturation","Smart-Home-Devices.6f323bff-23b0-411d-be96-da0ab7634ebe.color-brightness","Smart-Home-Devices.6f323bff-23b0-411d-be96-da0ab7634ebe.colorRgb","Smart-Home-Devices.6f323bff-23b0-411d-be96-da0ab7634ebe.percentage","Smart-Home-Devices.1503e486-40a8-449b-91c9-f8ce9687211f.#enabled","Smart-Home-Devices.1503e486-40a8-449b-91c9-f8ce9687211f.#delete","Smart-Home-Devices.1503e486-40a8-449b-91c9-f8ce9687211f.powerState","Smart-Home-Devices.1503e486-40a8-449b-91c9-f8ce9687211f.colorName","Smart-Home-Devices.1503e486-40a8-449b-91c9-f8ce9687211f.color-hue","Smart-Home-Devices.1503e486-40a8-449b-91c9-f8ce9687211f.color-saturation","Smart-Home-Devices.1503e486-40a8-449b-91c9-f8ce9687211f.color-brightness","Smart-Home-Devices.1503e486-40a8-449b-91c9-f8ce9687211f.colorRgb","Smart-Home-Devices.1503e486-40a8-449b-91c9-f8ce9687211f.percentage","Smart-Home-Devices.e5d518a6-eaec-468b-8b11-7bc1e6ad0cf2.#enabled","Smart-Home-Devices.e5d518a6-eaec-468b-8b11-7bc1e6ad0cf2.#delete","Smart-Home-Devices.e5d518a6-eaec-468b-8b11-7bc1e6ad0cf2.powerState","Smart-Home-Devices.ee47b4bc-7f15-4c6b-af0e-8861e5665c58.#enabled","Smart-Home-Devices.ee47b4bc-7f15-4c6b-af0e-8861e5665c58.#delete","Smart-Home-Devices.ee47b4bc-7f15-4c6b-af0e-8861e5665c58.powerState","Smart-Home-Devices.b40fc1c9-b51a-47ef-a763-3ad853eebd6f.#enabled","Smart-Home-Devices.b40fc1c9-b51a-47ef-a763-3ad853eebd6f.#delete","Smart-Home-Devices.b40fc1c9-b51a-47ef-a763-3ad853eebd6f.powerState"]
            2023-12-17 13:05:52.036  - info: alexa2.0 (725) Alexa-Push-Connection (macDms = true) established. Disable Polling
            2023-12-17 13:05:59.500  - info: javascript.0 (714) Start javascript script.js.Sonstiges.BackItUp-Ueberwachung
            2023-12-17 13:05:59.507  - info: javascript.0 (714) script.js.Sonstiges.BackItUp-Ueberwachung: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions
            2023-12-17 13:06:14.154  - info: alexa2.0 (725) Initialization Done ...
            2023-12-17 13:06:43.093  - info: admin.0 (691) <== Disconnect system.user.admin from 2001:9e8:27a6:e000:98ef:bacc:1dc4:9162 javascript
            2023-12-17 13:06:43.095  - info: admin.0 (691) <== Disconnect system.user.admin from 2001:9e8:27a6:e000:98ef:bacc:1dc4:9162 admin
            2023-12-17 13:06:45.926  - info: web.0 (920) ==> Connected system.user.admin from 2001:9e8:27a6:e000:98ef:bacc:1dc4:9162
            2023-12-17 13:07:01.671  - info: admin.0 (691) <== Disconnect system.user.admin from 2001:9e8:27a6:e000:98ef:bacc:1dc4:9162 admin
            
            
            Thomas Braun 1 Reply Last reply Reply Quote 0
            • Thomas Braun
              Thomas Braun Most Active @AlexAtHome last edited by

              @alexathome

              Setz den 'iobuser' in die Gruppe 'adm'und schalt den Desktop aus.

              Zum Problem:
              Zeig mal das (Debug)-Log bei einem automatischen Backup.

              AlexAtHome 1 Reply Last reply Reply Quote 0
              • AlexAtHome
                AlexAtHome @Thomas Braun last edited by

                @thomas-braun
                Ersteres done.
                Zum Desktop: ich gehe gelegentlich auch mal direkt auf den Server, und dann bin ich froh, den Desktop zu haben.... ist das ein Security Thema? Denn die System-Ressourcen sollten doch reichen.

                Bzgl. Log: da muss ich bis morgen warten, dann ist das nächste fällig (habe den Zeitraum mal auf 1 Tag runtergesetzt).

                Aber könnte mal jemand sagen, ob meine Annahme denn nun richtig ist, dass der Adapter eigentlich seit dem fehlgeschlagenen Backup am 05.12. mal wieder Backups hätte durchführen müssen? (am 07.12., 09.12., 11.12., 13.12., 15.12....) Gerade nach einem fehlgeschlagenen Backup finde ich es umso wichtiger, dass ein neues Backup erstellt oder dies zumindest versucht wird.

                Thomas Braun Codierknecht 2 Replies Last reply Reply Quote 0
                • Thomas Braun
                  Thomas Braun Most Active @AlexAtHome last edited by

                  @alexathome sagte in BackItUp: Mount-Error, danach kein weiterer Backup-Versuch:

                  und dann bin ich froh, den Desktop zu haben.... ist das ein Security Thema? Denn die System-Ressourcen sollten doch reichen.

                  Wozu?
                  Ist sowohl ein Sicherheits wir rein Performance-Thema und nicht zuletzt ein Thema der Einfachheit. Ein GUI steht nur im Weg herum und macht das ganze System unnötig komplex.

                  Stell halt das Back up auf eine Zeit in Kürze, dann siehst du das doch.

                  1 Reply Last reply Reply Quote 0
                  • Codierknecht
                    Codierknecht Developer Most Active @AlexAtHome last edited by

                    @alexathome sagte in BackItUp: Mount-Error, danach kein weiterer Backup-Versuch:

                    Zum Desktop: ich gehe gelegentlich auch mal direkt auf den Server, und dann bin ich froh, den Desktop zu haben

                    Wenn ich an der Ecke auch noch meinen Senf dazugeben darf:

                    So ein Desktop ist bei einem Server-System nur unnötiger Ballast, der mehr Probleme macht als er etwas nützt.
                    Ich selbst bin in Sachen Linux ziemlich unbedarft und kenne nur eine handvoll Befehle auswendig. Den Rest muss ich nachschlagen. Trotzdem käme ich nicht auf die Idee, einen Desktop nutzen zu wollen.
                    Wenn ich an die Kiste will, nehme ich die PowerShell oder PuTTY und gehe da per SSH ran.

                    AlexAtHome 1 Reply Last reply Reply Quote 2
                    • AlexAtHome
                      AlexAtHome @Codierknecht last edited by

                      So, das Log nach dem letzten automatischen Backup im Debug-Loglevel lautet:

                      2023-12-18 10:30:10.042 - debug: backitup.0 (3866) The local storage check was completed successfully. On the host "iobroker-server" are currently 272473 MB free space available!
                      2023-12-18 10:30:10.088 - debug: backitup.0 (3866) Backup has started ...
                      2023-12-18 10:30:20.089 - debug: backitup.0 (3866) [iobroker/mount] nfs-mount command: "sudo mount mycloud:/nfs/iobroker /opt/iobroker/backups"
                      2023-12-18 10:30:20.121 - debug: backitup.0 (3866) [iobroker/mount] mount successfully completed
                      2023-12-18 10:30:20.121 - debug: backitup.0 (3866) [iobroker/mount] done
                      2023-12-18 10:30:21.236 - debug: backitup.0 (3866) [iobroker/iobroker] host.iobroker-server 4645 states saved
                      2023-12-18 10:30:21.390 - debug: backitup.0 (3866) [iobroker/iobroker] host.iobroker-server 5774 objects saved
                      2023-12-18 10:30:21.901 - debug: backitup.0 (3866) [iobroker/iobroker] Backup created: /opt/iobroker/backups/iobroker_2023_12_18-10_30_20_iobroker-server_backupiobroker.tar.gz
                      2023-12-18 10:30:21.903 - debug: backitup.0 (3866) [iobroker/iobroker] This backup can only be restored with js-controller version up from 4.1
                      2023-12-18 10:30:22.942 - debug: backitup.0 (3866) [iobroker/iobroker] done
                      2023-12-18 10:30:24.024 - debug: backitup.0 (3866) [iobroker/zigbee] found zigbee database: zigbee.0,zigbee.1
                      2023-12-18 10:30:24.025 - debug: backitup.0 (3866) [iobroker/zigbee] done
                      2023-12-18 10:30:25.531 - debug: backitup.0 (3866) [iobroker/cifs] used copy path: /nfs/iobroker
                      2023-12-18 10:30:25.532 - debug: backitup.0 (3866) [iobroker/cifs] done
                      2023-12-18 10:30:26.136 - debug: backitup.0 (3866) [iobroker/clean] delete /opt/iobroker/backups/iobroker_2023_11_19-02_40_20_iobroker-server_backupiobroker.tar.gz
                      2023-12-18 10:30:26.167 - debug: backitup.0 (3866) [iobroker/clean] delete /opt/iobroker/backups/zigbee.0_2023_11_19-02_40_29_iobroker-server_backupiobroker.tar.gz
                      2023-12-18 10:30:26.171 - debug: backitup.0 (3866) [iobroker/clean] delete /opt/iobroker/backups/zigbee.1_2023_11_19-02_40_29_iobroker-server_backupiobroker.tar.gz
                      2023-12-18 10:30:26.193 - debug: backitup.0 (3866) [iobroker/clean] done
                      2023-12-18 10:30:27.421 - debug: backitup.0 (3866) [iobroker/historyHTML] new history html values created
                      2023-12-18 10:30:27.514 - debug: backitup.0 (3866) [iobroker/historyHTML] done
                      2023-12-18 10:30:27.679 - debug: backitup.0 (3866) [iobroker/historyJSON] new history json values created
                      2023-12-18 10:30:27.679 - debug: backitup.0 (3866) [iobroker/historyJSON] done
                      2023-12-18 10:30:27.837 - debug: backitup.0 (3866) [iobroker/umount] mount activ, umount is started ...
                      2023-12-18 10:30:32.890 - debug: backitup.0 (3866) [iobroker/umount] umount successfully completed
                      2023-12-18 10:30:32.890 - debug: backitup.0 (3866) [iobroker/umount] done
                      2023-12-18 10:30:33.041 - debug: backitup.0 (3866) [iobroker] exec: done
                      

                      Sieht für mich unauffällig aus.

                      Homoran 1 Reply Last reply Reply Quote 0
                      • Homoran
                        Homoran Global Moderator Administrators @AlexAtHome last edited by Homoran

                        @alexathome sagte in BackItUp: Mount-Error, danach kein weiterer Backup-Versuch:

                        Sieht für mich unauffällig aus.

                        Ja!

                        und wo ist jetzt (10:30 gestern?) das aktuelle Problem?

                        AlexAtHome 1 Reply Last reply Reply Quote 0
                        • AlexAtHome
                          AlexAtHome @Homoran last edited by

                          @homoran Nirgendwo! Darum ging es mir auch nie, siehe erster Post.

                          Auf meine eigentliche Frage, ob nicht nach dem fehlgeschlagenen Backup neue Backups (bzw. -versuche) hätten stattfinden sollen, bekam ich leider nie eine Antwort.
                          Ich habe einfach nur die Nachfragen im Thread beantwortet, die IMHO an meiner eigentlichen Frage irgendwie vorbeigingen... aber ok, was weiß ich schon...

                          R Homoran 2 Replies Last reply Reply Quote 0
                          • R
                            reutli @AlexAtHome last edited by

                            @alexathome

                            @alexathome sagte in BackItUp: Mount-Error, danach kein weiterer Backup-Versuch:

                            Meine Erwartungshaltung ist, dass der Adapter zum nächsten anstehenden periodischen Backup-Zeitpunkt (bei mir alle 2 Tage) wieder ein Backup erstellt. Das wäre dann am 07.12.23 gewesen.

                            Das ist korrekt und sollte auch funktionieren. In allen anderen Fällen müssen man (zeitnah) im Log schauen, warum nicht.

                            1 Reply Last reply Reply Quote 0
                            • Homoran
                              Homoran Global Moderator Administrators @AlexAtHome last edited by

                              @alexathome sagte in BackItUp: Mount-Error, danach kein weiterer Backup-Versuch:

                              ob nicht nach dem fehlgeschlagenen Backup neue Backups (bzw. -versuche) hätten stattfinden sollen, bekam ich leider nie eine Antwort.

                              das sollte ja das Log zeigen

                              AlexAtHome 1 Reply Last reply Reply Quote 0
                              • AlexAtHome
                                AlexAtHome @Homoran last edited by

                                Im Log stand halt einfach nur -nichts-. Wenn es dort eine Fehlermeldung gegeben hätte, hätte ich ja darauf aufsetzen können. Aber der Adapter scheint sich im Fehlerfall einfach "schlafen zu legen" und nichts mehr zu tun.

                                Ich löse das Problem derzeit folgendermaßen, indem ich mir jeden Morgen eine Mail schicken lasse mit dem Ergebnis des letzten Backups (erfolgreich/ Fehler). Bisher ist es zu keinem weiteren Fehler gekommen.

                                1 Reply Last reply Reply Quote 0
                                • First post
                                  Last post

                                Support us

                                ioBroker
                                Community Adapters
                                Donate
                                FAQ Cloud / IOT
                                HowTo: Node.js-Update
                                HowTo: Backup/Restore
                                Downloads
                                BLOG

                                542
                                Online

                                31.7k
                                Users

                                79.7k
                                Topics

                                1.3m
                                Posts

                                5
                                14
                                412
                                Loading More Posts
                                • Oldest to Newest
                                • Newest to Oldest
                                • Most Votes
                                Reply
                                • Reply as topic
                                Log in to reply
                                Community
                                Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                The ioBroker Community 2014-2023
                                logo