Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. Backitup Mount Error Synology NAS

NEWS

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    16
    1
    1.7k

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    13
    1
    870

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    25
    1
    2.1k

Backitup Mount Error Synology NAS

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
34 Beiträge 6 Kommentatoren 3.4k Aufrufe 5 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • RoddiEFR RoddiEF

    In den Einstellungen vom Adapter einfach mal nur iobroker einstellen. Ohne /volume1/Backupio/
    Auch kein "/" am Anfang von Verzeichniss iobroker.
    Bei mir heisst das Verzeichniss nur Backups auf der Synology und funktioniert mit CIFS und SMB3.0.

    backupiobroker.PNG
    backupiobrokerpfad.PNG

    HomoranH Offline
    HomoranH Offline
    Homoran
    Global Moderator Administrators
    schrieb am zuletzt editiert von
    #5

    @roddief sagte in Backitup Mount Error Synology NAS:

    Bei mir heisst das Verzeichniss nur Backups auf der Synology und funktioniert mit CIFS und SMB3.0.

    dann ist Backups auch dein Freigabename!

    @habi989
    wie sieht denn deine Freigabe auf der Syno aus?

    kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

    Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

    der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

    H 1 Antwort Letzte Antwort
    0
    • H habi989

      @glasfaser

      Hi,

      das hat leider nichts gebracht. Nun habe ich folgendes Ergebnis:

      Started iobroker ...
      [DEBUG] [mount] start with {"mountType":"CIFS","type":"storage","source":"cifs","mount":"//192.168.178.2","debugging":true,"fileDir":"/opt/iobroker/node_modules/iobroker.backitup","wakeOnLAN":false,"macAd":"20:DE:20:DE:20:DE","wolTime":"25","smb":"vers=3.0","sudo":true,"cifsDomain":"","clientInodes":false,"deleteOldBackup":true,"ownDir":true,"dir":"Backupio/iobroker","dirMinimal":"Backupio/iobroker","user":"backitup","pass":"****"}
      [DEBUG] [mount] - noserverino option: false
      [DEBUG] [mount] - cifs-mount command: "sudo mount -t cifs -o username=backitup,password=****,rw,file_mode=0777,dir_mode=0777,vers=3.0 //192.168.178.2/Backupio/iobroker /opt/iobroker/backups"
      [DEBUG] [mount] - mount successfully completed
      [DEBUG] [mount] - done
      [DEBUG] [iobroker] start with {"type":"creator","time":"02:40","debugging":true,"slaveBackup":"Single","everyXDays":"1","deleteBackupAfter":0,"cifs":{"enabled":true,"mountType":"CIFS","type":"storage","source":"cifs","mount":"//192.168.178.2","debugging":true,"fileDir":"/opt/iobroker/node_modules/iobroker.backitup","wakeOnLAN":false,"macAd":"20:DE:20:DE:20:DE","wolTime":"25","smb":"vers=3.0","sudo":true,"cifsDomain":"","clientInodes":false,"deleteOldBackup":true,"ownDir":true,"dir":"/Backupio/iobroker","dirMinimal":"Backupio/iobroker","user":"backitup","pass":"****","context":{"fileNames":[],"errors":{},"done":["mount"],"types":[]},"adapter":null,"influxDBEvents":[],"mySqlEvents":[],"pgSqlEvents":[]},"dir":"/opt/iobroker","javascripts":{"enabled":true,"type":"creator","ftp":{"enabled":false,"type":"storage","source":"cifs","host":"192.168.178.2","debugging":true,"deleteOldBackup":true,"ownDir":false,"dir":"/Backupio/iobroker","dirMinimal":"/backupDir/iobroker","user":"backitup","pass":"****","port":"21"},"cifs":{"enabled":true,"mountType":"CIFS","type":"storage","source":"cifs","mount":"192.168.178.2","debugging":true,"fileDir":"/opt/iobroker/node_modules/iobroker.backitup","wakeOnLAN":false,"macAd":"20:DE:20:DE:20:DE","wolTime":"25","smb":"vers=3.0","sudo":true,"cifsDomain":"","clientInodes":false,"deleteOldBackup":true,"ownDir":true,"dir":"Backupio/iobroker","dirMinimal":"Backupio/iobroker","user":"backitup","pass":"****"},"dropbox":{"enabled":false,"type":"storage","source":"cifs","debugging":true,"deleteOldBackup":false,"accessToken":"****","ownDir":false,"dir":"/backupDir","dirMinimal":"/backupDir/iobroker"},"webdav":{"enabled":false,"type":"storage","source":"cifs","debugging":true,"deleteOldBackup":false,"username":"username","pass":"****","url":"https://example.com/remote.php/dav/files/username/","ownDir":false,"dir":"/backupDir","dirMinimal":"/backupDir/iobroker","signedCertificates":true},"googledrive":{"enabled":false,"type":"storage","source":"cifs","debugging":true,"deleteOldBackup":false,"accessJson":"****","ownDir":false,"dir":"/backupDir","dirMinimal":"/backupDir/iobroker"},"slaveSuffix":"","hostType":"Single","nameSuffix":""},"historyHTML":{"enabled":true,"type":"message","entriesNumber":"25","systemLang":"de"},"historyJSON":{"enabled":true,"type":"message","entriesNumber":"25","systemLang":"de"},"telegram":{"enabled":true,"notificationsType":"WhatsApp","type":"message","instance":"","SilentNotice":false,"NoticeType":"longTelegramNotice","User":"none","onlyError":false,"telegramWaiting":0,"hostName":"","systemLang":"de"},"email":{"enabled":true,"notificationsType":"WhatsApp","type":"message","instance":"","NoticeType":"longEmailNotice","emailReceiver":"xxx@xxx.com","emailSender":"xxx@xxx.com","onlyError":false,"emailWaiting":0,"hostName":"","systemLang":"de"},"pushover":{"enabled":true,"notificationsType":"WhatsApp","type":"message","instance":"","SilentNotice":false,"NoticeType":"longPushoverNotice","deviceID":"","onlyError":false,"pushoverWaiting":0,"hostName":"","systemLang":"de"},"whatsapp":{"enabled":true,"notificationsType":"WhatsApp","type":"message","instance":"whatsapp-cmb.0","NoticeType":"longWhatsappNotice","onlyError":false,"whatsappWaiting":0,"hostName":"","systemLang":"de"},"backupDir":"/opt/iobroker/backups"}
      [DEBUG] [iobroker] - host.raspberrypi 4630 states saved
      
      [DEBUG] [iobroker] - host.raspberrypi 5267 objects saved
      

      hat noch jemand eine Idee?

      Danke

      Thomas BraunT Online
      Thomas BraunT Online
      Thomas Braun
      Most Active
      schrieb am zuletzt editiert von
      #6

      @habi989 sagte in Backitup Mount Error Synology NAS:

      [DEBUG] [mount] - mount successfully completed           
      [DEBUG] [mount] - done
      

      Passt doch.

      Linux-Werkzeugkasten:
      https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
      NodeJS Fixer Skript:
      https://forum.iobroker.net/topic/68035/iob-node-fix-skript
      iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

      HomoranH 1 Antwort Letzte Antwort
      0
      • Thomas BraunT Thomas Braun

        @habi989 sagte in Backitup Mount Error Synology NAS:

        [DEBUG] [mount] - mount successfully completed           
        [DEBUG] [mount] - done
        

        Passt doch.

        HomoranH Offline
        HomoranH Offline
        Homoran
        Global Moderator Administrators
        schrieb am zuletzt editiert von
        #7

        @thomas-braun sagte in Backitup Mount Error Synology NAS:

        Passt doch.

        :see_no_evil:

        kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

        Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

        der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

        1 Antwort Letzte Antwort
        0
        • HomoranH Homoran

          @roddief sagte in Backitup Mount Error Synology NAS:

          Bei mir heisst das Verzeichniss nur Backups auf der Synology und funktioniert mit CIFS und SMB3.0.

          dann ist Backups auch dein Freigabename!

          @habi989
          wie sieht denn deine Freigabe auf der Syno aus?

          H Offline
          H Offline
          habi989
          schrieb am zuletzt editiert von habi989
          #8

          @homoran

          Naja also ich habe einen gemeinsamen Ordner erstellt und diesen wie auf den Bildern zu sehen freigegeben.

          Bildschirmfoto 2022-02-01 um 16.24.19.png
          Bildschirmfoto 2022-02-01 um 16.23.00.png Bildschirmfoto 2022-02-01 um 16.21.04.png
          Bildschirmfoto 2022-02-01 um 16.20.49.png
          Bildschirmfoto 2022-02-01 um 16.20.35.png
          Bildschirmfoto 2022-02-01 um 16.20.11.png

          Die IP 192.168.178.98 ist logischerweise der IOBroker....
          Das Einzige, was in diesem Ordner auf der NAS jemals erstellt wurde ist ein Ordner namens tmpscripts. dieser ist leer.

          Das wundert mich so. Er sagt completed, aber erstellt wurde auf der NAS nichts...

          HomoranH 1 Antwort Letzte Antwort
          0
          • H habi989

            @homoran

            Naja also ich habe einen gemeinsamen Ordner erstellt und diesen wie auf den Bildern zu sehen freigegeben.

            Bildschirmfoto 2022-02-01 um 16.24.19.png
            Bildschirmfoto 2022-02-01 um 16.23.00.png Bildschirmfoto 2022-02-01 um 16.21.04.png
            Bildschirmfoto 2022-02-01 um 16.20.49.png
            Bildschirmfoto 2022-02-01 um 16.20.35.png
            Bildschirmfoto 2022-02-01 um 16.20.11.png

            Die IP 192.168.178.98 ist logischerweise der IOBroker....
            Das Einzige, was in diesem Ordner auf der NAS jemals erstellt wurde ist ein Ordner namens tmpscripts. dieser ist leer.

            Das wundert mich so. Er sagt completed, aber erstellt wurde auf der NAS nichts...

            HomoranH Offline
            HomoranH Offline
            Homoran
            Global Moderator Administrators
            schrieb am zuletzt editiert von
            #9

            @habi989 sagte in Backitup Mount Error Synology NAS:

            Er sagt completed, aber erstellt wurde auf der NAS nichts...

            completed ist der Mount, nicht das Backup.

            Also stimmt schon mal die Freigabe

            Dann stell die Instanz auf debug und sieh nach neuen Fehlermeldungen

            kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

            Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

            der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

            H 1 Antwort Letzte Antwort
            0
            • HomoranH Homoran

              @habi989 sagte in Backitup Mount Error Synology NAS:

              Er sagt completed, aber erstellt wurde auf der NAS nichts...

              completed ist der Mount, nicht das Backup.

              Also stimmt schon mal die Freigabe

              Dann stell die Instanz auf debug und sieh nach neuen Fehlermeldungen

              H Offline
              H Offline
              habi989
              schrieb am zuletzt editiert von
              #10

              @homoran

              was ich komisch finde: Ich habe mir ein Tutorial auf Youtube angesehen um es zu vergleichen. Bei dem sieht man dann, wie der Adapter Backitup die Daten hochlädt, also wie viel MB schon hochgeladen wurden.

              Bei mir bleibt es ja bei den States stehen...

              hier mal der Log, nachdem ich es erneut versucht habe:

              Bildschirmfoto 2022-02-01 um 19.53.06.png Bildschirmfoto 2022-02-01 um 19.52.51.png

              Thomas BraunT HomoranH 2 Antworten Letzte Antwort
              0
              • H habi989

                @homoran

                was ich komisch finde: Ich habe mir ein Tutorial auf Youtube angesehen um es zu vergleichen. Bei dem sieht man dann, wie der Adapter Backitup die Daten hochlädt, also wie viel MB schon hochgeladen wurden.

                Bei mir bleibt es ja bei den States stehen...

                hier mal der Log, nachdem ich es erneut versucht habe:

                Bildschirmfoto 2022-02-01 um 19.53.06.png Bildschirmfoto 2022-02-01 um 19.52.51.png

                Thomas BraunT Online
                Thomas BraunT Online
                Thomas Braun
                Most Active
                schrieb am zuletzt editiert von
                #11

                @habi989

                Bitte keine Screenshots, LogFile aus der Konsole posten.

                iobroker logs --watch
                

                hilft.

                Linux-Werkzeugkasten:
                https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                NodeJS Fixer Skript:
                https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                1 Antwort Letzte Antwort
                0
                • H habi989

                  @homoran

                  was ich komisch finde: Ich habe mir ein Tutorial auf Youtube angesehen um es zu vergleichen. Bei dem sieht man dann, wie der Adapter Backitup die Daten hochlädt, also wie viel MB schon hochgeladen wurden.

                  Bei mir bleibt es ja bei den States stehen...

                  hier mal der Log, nachdem ich es erneut versucht habe:

                  Bildschirmfoto 2022-02-01 um 19.53.06.png Bildschirmfoto 2022-02-01 um 19.52.51.png

                  HomoranH Offline
                  HomoranH Offline
                  Homoran
                  Global Moderator Administrators
                  schrieb am zuletzt editiert von
                  #12

                  @habi989 sagte in Backitup Mount Error Synology NAS:

                  Ich habe mir ein Tutorial auf Youtube angesehen

                  war schon mal der erste Fehler :-)

                  @habi989 sagte in Backitup Mount Error Synology NAS:

                  wie der Adapter Backitup die Daten hochlädt, also wie viel MB schon hochgeladen wurden.
                  Bei mir bleibt es ja bei den States stehen...

                  Lesen hätte gereicht. geht schneller als ein Video ansehen.

                  @homoran sagte in Backitup Mount Error Synology NAS:

                  completed ist der Mount, nicht das Backup.

                  und dann:
                  @homoran sagte in Backitup Mount Error Synology NAS:

                  stell die Instanz auf debug und sieh nach neuen Fehlermeldungen

                  Wo ist das debug log?
                  bitte nicht als Screenshot,, sondern als Text in code-tags.

                  kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

                  Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

                  der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

                  H 1 Antwort Letzte Antwort
                  0
                  • HomoranH Homoran

                    @habi989 sagte in Backitup Mount Error Synology NAS:

                    Ich habe mir ein Tutorial auf Youtube angesehen

                    war schon mal der erste Fehler :-)

                    @habi989 sagte in Backitup Mount Error Synology NAS:

                    wie der Adapter Backitup die Daten hochlädt, also wie viel MB schon hochgeladen wurden.
                    Bei mir bleibt es ja bei den States stehen...

                    Lesen hätte gereicht. geht schneller als ein Video ansehen.

                    @homoran sagte in Backitup Mount Error Synology NAS:

                    completed ist der Mount, nicht das Backup.

                    und dann:
                    @homoran sagte in Backitup Mount Error Synology NAS:

                    stell die Instanz auf debug und sieh nach neuen Fehlermeldungen

                    Wo ist das debug log?
                    bitte nicht als Screenshot,, sondern als Text in code-tags.

                    H Offline
                    H Offline
                    habi989
                    schrieb am zuletzt editiert von Homoran
                    #13

                    @homoran
                    so jetzt aber :D

                    
                    2022-02-01 18:00:11.207  - info: ical.0 (3551) processing URL: Müllkalender https://calendar.google.com/privat/basic.ics
                    
                    2022-02-01 18:30:10.553  - info: ical.0 (4838) starting. Version 1.11.4 in /opt/iobroker/node_modules/iobroker.ical, node: v14.18.3, js-controller: 3.3.22
                    2022-02-01 18:30:11.121  - info: ical.0 (4838) processing URL: Müllkalender https://calendar.google.com/calendar/ical/privat/basic.ics
                    
                    2022-02-01 18:48:31.475  - info: host.raspberrypi stopInstance system.adapter.backitup.0 (force=false, process=true)
                    2022-02-01 18:48:31.489  - info: backitup.0 (2180) Got terminate signal TERMINATE_YOURSELF
                    2022-02-01 18:48:31.493  - info: host.raspberrypi stopInstance system.adapter.backitup.0 send kill signal
                    2022-02-01 18:48:31.491  - info: backitup.0 (2180) cleaned everything up...
                    2022-02-01 18:48:31.493  - info: backitup.0 (2180) terminating
                    2022-02-01 18:48:31.495  - info: backitup.0 (2180) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                    2022-02-01 18:48:32.064  - info: host.raspberrypi instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                    2022-02-01 18:48:34.569  - info: host.raspberrypi instance system.adapter.backitup.0 started with pid 5682
                    2022-02-01 18:48:36.217  - info: backitup.0 (5682) starting. Version 2.2.3 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.3, js-controller: 3.3.22
                    2022-02-01 18:48:36.284  - info: backitup.0 (5682) [iobroker] backup was activated at 02:40 every 1 day(s)
                    2022-02-01 18:49:39.271  - warn: host.raspberrypi-Server Cannot read file ring.0 / doorbell_86292617/livestream86292617_1638876876746.mp4: Array buffer allocation failed
                    2022-02-01 18:49:41.569  - error: fullybrowser.0 (2135) States database error: read ECONNRESET
                    2022-02-01 18:49:41.561  - error: whatsapp-cmb.0 (2207) States database error: read ECONNRESET
                    2022-02-01 18:49:41.578  - error: shelly.0 (2165) States database error: read ECONNRESET
                    2022-02-01 18:49:41.579  - error: sonos.0 (2108) States database error: read ECONNRESET
                    2022-02-01 18:49:41.582  - error: shelly.0 (2165) Objects database error: read ECONNRESET
                    2022-02-01 18:49:41.588  - error: web.0 (2082) States database error: read ECONNRESET
                    2022-02-01 18:49:41.590  - error: alexa2.0 (2006) States database error: read ECONNRESET
                    2022-02-01 18:49:41.595  - error: trashschedule.0 (2150) States database error: read ECONNRESET
                    2022-02-01 18:49:41.575  - error: backitup.0 (5682) States database error: read ECONNRESET
                    2022-02-01 18:49:41.629  - info: trashschedule.0 (2150) cleaned everything up...
                    2022-02-01 18:49:41.631  - info: backitup.0 (5682) cleaned everything up...
                    2022-02-01 18:49:41.634  - info: fullybrowser.0 (2135) cleaned everything up...
                    2022-02-01 18:49:41.615  - error: ping.0 (1958) States database error: read ECONNRESET
                    2022-02-01 18:49:41.583  - error: discovery.0 (2056) States database error: read ECONNRESET
                    2022-02-01 18:49:41.612  - error: javascript.0 (1947) States database error: read ECONNRESET
                    2022-02-01 18:49:41.609  - error: admin.0 (1881) States database error: read ECONNRESET
                    2022-02-01 18:49:41.622  - info: sonos.0 (2108) terminating
                    2022-02-01 18:49:41.642  - error: javascript.0 (1947) Objects database error: read ECONNRESET
                    2022-02-01 18:49:41.653  - info: web.0 (2082) terminated http server on port 8082
                    2022-02-01 18:49:41.643  - info: shelly.0 (2165) Closing Adapter
                    2022-02-01 18:49:41.655  - info: admin.0 (1881) terminating http server on port 8081
                    2022-02-01 18:49:41.651  - info: javascript.0 (1947) Stop script script.js.Eigene_Skripte.Batterie_Laden
                    2022-02-01 18:49:43.134  - info: alexa2.0 (2006) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                    2022-02-01 18:49:43.136  - info: trashschedule.0 (2150) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                    2022-02-01 18:49:43.137  - info: backitup.0 (5682) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                    2022-02-01 18:49:43.140  - info: fullybrowser.0 (2135) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                    2022-02-01 18:49:43.140  - info: whatsapp-cmb.0 (2207) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                    2022-02-01 18:49:43.146  - info: ping.0 (1958) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                    2022-02-01 18:49:43.152  - info: javascript.0 (1947) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                    2022-02-01 18:49:43.156  - info: web.0 (2082) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                    2022-02-01 18:49:43.157  - info: sonos.0 (2108) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                    2022-02-01 18:49:43.159  - info: discovery.0 (2056) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                    2022-02-01 18:49:43.161  - info: shelly.0 (2165) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                    2022-02-01 18:49:43.163  - info: admin.0 (1881) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                    2022-02-01 18:49:46.590  - warn: fullybrowser.0 (2135) get state error: DB closed
                    2022-02-01 18:49:46.593  - error: shelly.0 (2165) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                    2022-02-01 18:49:46.601  - warn: alexa2.0 (2006) get state error: DB closed
                    2022-02-01 18:49:46.602  - warn: sonos.0 (2108) get state error: DB closed
                    2022-02-01 18:49:46.604  - warn: web.0 (2082) get state error: DB closed
                    2022-02-01 18:49:46.611  - error: whatsapp-cmb.0 (2207) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                    2022-02-01 18:49:46.658  - warn: discovery.0 (2056) get state error: DB closed
                    2022-02-01 18:49:46.680  - error: backitup.0 (5682) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                    2022-02-01 18:49:46.669  - error: ping.0 (1958) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                    2022-02-01 18:49:46.675  - error: admin.0 (1881) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                    2022-02-01 18:49:46.689  - error: trashschedule.0 (2150) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                    2022-02-01 18:49:46.592  - warn: fullybrowser.0 (2135) get state error: DB closed
                    2022-02-01 18:49:46.608  - warn: fullybrowser.0 (2135) get state error: DB closed
                    2022-02-01 18:49:46.610  - warn: fullybrowser.0 (2135) get state error: DB closed
                    2022-02-01 18:49:46.611  - warn: fullybrowser.0 (2135) get state error: DB closed
                    2022-02-01 18:49:46.613  - warn: fullybrowser.0 (2135) get state error: DB closed
                    2022-02-01 18:49:46.614  - warn: fullybrowser.0 (2135) get state error: DB closed
                    2022-02-01 18:49:46.616  - warn: fullybrowser.0 (2135) get state error: DB closed
                    2022-02-01 18:49:46.624  - warn: fullybrowser.0 (2135) get state error: DB closed
                    2022-02-01 18:49:46.630  - warn: fullybrowser.0 (2135) get state error: DB closed
                    2022-02-01 18:49:46.635  - warn: fullybrowser.0 (2135) get state error: DB closed
                    2022-02-01 18:49:46.640  - warn: fullybrowser.0 (2135) get state error: DB closed
                    2022-02-01 18:49:46.641  - warn: fullybrowser.0 (2135) get state error: DB closed
                    2022-02-01 18:49:46.643  - warn: fullybrowser.0 (2135) get state error: DB closed
                    2022-02-01 18:49:46.644  - warn: fullybrowser.0 (2135) get state error: DB closed
                    2022-02-01 18:49:46.645  - warn: fullybrowser.0 (2135) get state error: DB closed
                    2022-02-01 18:49:46.646  - warn: fullybrowser.0 (2135) get state error: DB closed
                    2022-02-01 18:49:46.648  - warn: fullybrowser.0 (2135) get state error: DB closed
                    2022-02-01 18:49:46.649  - warn: fullybrowser.0 (2135) get state error: DB closed
                    2022-02-01 18:49:46.686  - warn: fullybrowser.0 (2135) get state error: DB closed
                    2022-02-01 18:49:46.687  - warn: fullybrowser.0 (2135) get state error: DB closed
                    2022-02-01 18:49:46.688  - warn: fullybrowser.0 (2135) get state error: DB closed
                    2022-02-01 18:49:46.688  - warn: fullybrowser.0 (2135) get state error: DB closed
                    2022-02-01 18:49:46.689  - warn: fullybrowser.0 (2135) get state error: DB closed
                    2022-02-01 18:49:46.690  - warn: fullybrowser.0 (2135) get state error: DB closed
                    2022-02-01 18:49:46.690  - warn: fullybrowser.0 (2135) get state error: DB closed
                    2022-02-01 18:49:46.706  - warn: fullybrowser.0 (2135) get state error: DB closed
                    2022-02-01 18:49:46.707  - warn: fullybrowser.0 (2135) get state error: DB closed
                    2022-02-01 18:49:46.707  - warn: fullybrowser.0 (2135) get state error: DB closed
                    2022-02-01 18:49:46.708  - warn: fullybrowser.0 (2135) get state error: DB closed
                    2022-02-01 18:49:46.708  - warn: fullybrowser.0 (2135) get state error: DB closed
                    2022-02-01 18:49:46.709  - warn: fullybrowser.0 (2135) get state error: DB closed
                    2022-02-01 18:49:46.709  - warn: fullybrowser.0 (2135) get state error: DB closed
                    2022-02-01 18:49:46.710  - warn: fullybrowser.0 (2135) get state error: DB closed
                    2022-02-01 18:49:46.710  - warn: fullybrowser.0 (2135) get state error: DB closed
                    2022-02-01 18:49:46.617  - warn: sonos.0 (2108) get state error: DB closed
                    2022-02-01 18:49:46.619  - warn: sonos.0 (2108) get state error: DB closed
                    2022-02-01 18:49:46.621  - warn: sonos.0 (2108) get state error: DB closed
                    2022-02-01 18:49:46.622  - warn: sonos.0 (2108) get state error: DB closed
                    2022-02-01 18:49:46.623  - warn: sonos.0 (2108) get state error: DB closed
                    2022-02-01 18:49:46.625  - warn: sonos.0 (2108) get state error: DB closed
                    2022-02-01 18:49:46.636  - warn: sonos.0 (2108) get state error: DB closed
                    2022-02-01 18:49:46.637  - warn: sonos.0 (2108) get state error: DB closed
                    2022-02-01 18:49:46.639  - warn: sonos.0 (2108) get state error: DB closed
                    2022-02-01 18:49:46.640  - warn: sonos.0 (2108) get state error: DB closed
                    2022-02-01 18:49:46.666  - warn: sonos.0 (2108) get state error: DB closed
                    2022-02-01 18:49:46.667  - warn: sonos.0 (2108) get state error: DB closed
                    2022-02-01 18:49:46.668  - warn: sonos.0 (2108) get state error: DB closed
                    2022-02-01 18:49:46.668  - warn: sonos.0 (2108) get state error: DB closed
                    2022-02-01 18:49:46.669  - warn: sonos.0 (2108) get state error: DB closed
                    2022-02-01 18:49:46.670  - warn: sonos.0 (2108) get state error: DB closed
                    2022-02-01 18:49:46.670  - warn: sonos.0 (2108) get state error: DB closed
                    2022-02-01 18:49:46.671  - warn: sonos.0 (2108) get state error: DB closed
                    2022-02-01 18:49:46.671  - warn: sonos.0 (2108) get state error: DB closed
                    2022-02-01 18:49:46.672  - warn: sonos.0 (2108) get state error: DB closed
                    2022-02-01 18:49:46.673  - warn: sonos.0 (2108) get state error: DB closed
                    2022-02-01 18:49:46.673  - warn: sonos.0 (2108) get state error: DB closed
                    2022-02-01 18:49:46.674  - warn: sonos.0 (2108) get state error: DB closed
                    2022-02-01 18:49:46.674  - warn: sonos.0 (2108) get state error: DB closed
                    2022-02-01 18:49:46.675  - warn: sonos.0 (2108) get state error: DB closed
                    2022-02-01 18:49:46.675  - warn: sonos.0 (2108) get state error: DB closed
                    2022-02-01 18:49:46.687  - warn: sonos.0 (2108) get state error: DB closed
                    2022-02-01 18:49:46.688  - warn: sonos.0 (2108) get state error: DB closed
                    2022-02-01 18:49:46.689  - warn: sonos.0 (2108) get state error: DB closed
                    2022-02-01 18:49:46.689  - warn: sonos.0 (2108) get state error: DB closed
                    2022-02-01 18:49:46.690  - warn: sonos.0 (2108) get state error: DB closed
                    2022-02-01 18:49:46.690  - warn: sonos.0 (2108) get state error: DB closed
                    2022-02-01 18:49:46.716  - warn: sonos.0 (2108) get state error: DB closed
                    2022-02-01 18:49:46.717  - warn: sonos.0 (2108) get state error: DB closed
                    2022-02-01 18:49:46.726  - error: javascript.0 (1947) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                    2022-02-01 18:49:46.719  - warn: backitup.0 (5682) get state error: DB closed
                    2022-02-01 18:49:46.720  - warn: backitup.0 (5682) get state error: DB closed
                    2022-02-01 18:49:46.721  - warn: backitup.0 (5682) get state error: DB closed
                    2022-02-01 18:49:46.729  - warn: backitup.0 (5682) get state error: DB closed
                    2022-02-01 18:49:46.729  - warn: backitup.0 (5682) get state error: DB closed
                    2022-02-01 18:49:46.730  - warn: backitup.0 (5682) get state error: DB closed
                    2022-02-01 18:49:46.731  - warn: backitup.0 (5682) get state error: DB closed
                    2022-02-01 18:49:46.732  - warn: backitup.0 (5682) get state error: DB closed
                    2022-02-01 18:49:46.732  - warn: backitup.0 (5682) get state error: DB closed
                    2022-02-01 18:49:46.733  - warn: backitup.0 (5682) get state error: DB closed
                    2022-02-01 18:49:46.734  - warn: backitup.0 (5682) get state error: DB closed
                    2022-02-01 18:49:46.734  - warn: backitup.0 (5682) get state error: DB closed
                    2022-02-01 18:49:46.735  - warn: backitup.0 (5682) get state error: DB closed
                    2022-02-01 18:49:46.736  - warn: backitup.0 (5682) get state error: DB closed
                    2022-02-01 18:49:46.767  - warn: backitup.0 (5682) get state error: DB closed
                    2022-02-01 18:49:46.767  - warn: backitup.0 (5682) get state error: DB closed
                    2022-02-01 18:49:46.768  - warn: backitup.0 (5682) get state error: DB closed
                    2022-02-01 18:49:46.769  - warn: backitup.0 (5682) get state error: DB closed
                    2022-02-01 18:49:46.770  - warn: backitup.0 (5682) get state error: DB closed
                    2022-02-01 18:49:46.770  - warn: backitup.0 (5682) get state error: DB closed
                    2022-02-01 18:49:46.771  - warn: backitup.0 (5682) get state error: DB closed
                    2022-02-01 18:49:46.772  - warn: backitup.0 (5682) get state error: DB closed
                    2022-02-01 18:49:46.772  - warn: backitup.0 (5682) get state error: DB closed
                    2022-02-01 18:49:46.773  - warn: backitup.0 (5682) get state error: DB closed
                    2022-02-01 18:49:46.774  - warn: backitup.0 (5682) get state error: DB closed
                    2022-02-01 18:49:46.774  - warn: backitup.0 (5682) get state error: DB closed
                    2022-02-01 18:49:46.775  - warn: backitup.0 (5682) get state error: DB closed
                    2022-02-01 18:49:46.775  - warn: backitup.0 (5682) get state error: DB closed
                    2022-02-01 18:49:46.801  - warn: backitup.0 (5682) get state error: DB closed
                    2022-02-01 18:49:46.801  - warn: backitup.0 (5682) get state error: DB closed
                    2022-02-01 18:49:46.802  - warn: backitup.0 (5682) get state error: DB closed
                    2022-02-01 18:49:46.803  - warn: backitup.0 (5682) get state error: DB closed
                    2022-02-01 18:49:46.804  - warn: backitup.0 (5682) get state error: DB closed
                    2022-02-01 18:49:46.804  - warn: backitup.0 (5682) get state error: DB closed
                    2022-02-01 18:49:46.805  - warn: backitup.0 (5682) get state error: DB closed
                    2022-02-01 18:49:51.731  - error: backitup.0 (5682) Cannot find view "system" for search "script" : Connection is closed.
                    
                    2022-02-01 18:51:23.411  - info: host.raspberrypi instance system.adapter.backitup.0 started with pid 6157
                    2022-02-01 18:51:25.254  - info: backitup.0 (6157) starting. Version 2.2.3 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.3, js-controller: 3.3.22
                    2022-02-01 18:51:25.323  - info: backitup.0 (6157) [iobroker] backup was activated at 02:40 every 1 day(s)
                    
                    
                    Thomas BraunT HomoranH 2 Antworten Letzte Antwort
                    0
                    • H habi989

                      @homoran
                      so jetzt aber :D

                      
                      2022-02-01 18:00:11.207  - info: ical.0 (3551) processing URL: Müllkalender https://calendar.google.com/privat/basic.ics
                      
                      2022-02-01 18:30:10.553  - info: ical.0 (4838) starting. Version 1.11.4 in /opt/iobroker/node_modules/iobroker.ical, node: v14.18.3, js-controller: 3.3.22
                      2022-02-01 18:30:11.121  - info: ical.0 (4838) processing URL: Müllkalender https://calendar.google.com/calendar/ical/privat/basic.ics
                      
                      2022-02-01 18:48:31.475  - info: host.raspberrypi stopInstance system.adapter.backitup.0 (force=false, process=true)
                      2022-02-01 18:48:31.489  - info: backitup.0 (2180) Got terminate signal TERMINATE_YOURSELF
                      2022-02-01 18:48:31.493  - info: host.raspberrypi stopInstance system.adapter.backitup.0 send kill signal
                      2022-02-01 18:48:31.491  - info: backitup.0 (2180) cleaned everything up...
                      2022-02-01 18:48:31.493  - info: backitup.0 (2180) terminating
                      2022-02-01 18:48:31.495  - info: backitup.0 (2180) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                      2022-02-01 18:48:32.064  - info: host.raspberrypi instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                      2022-02-01 18:48:34.569  - info: host.raspberrypi instance system.adapter.backitup.0 started with pid 5682
                      2022-02-01 18:48:36.217  - info: backitup.0 (5682) starting. Version 2.2.3 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.3, js-controller: 3.3.22
                      2022-02-01 18:48:36.284  - info: backitup.0 (5682) [iobroker] backup was activated at 02:40 every 1 day(s)
                      2022-02-01 18:49:39.271  - warn: host.raspberrypi-Server Cannot read file ring.0 / doorbell_86292617/livestream86292617_1638876876746.mp4: Array buffer allocation failed
                      2022-02-01 18:49:41.569  - error: fullybrowser.0 (2135) States database error: read ECONNRESET
                      2022-02-01 18:49:41.561  - error: whatsapp-cmb.0 (2207) States database error: read ECONNRESET
                      2022-02-01 18:49:41.578  - error: shelly.0 (2165) States database error: read ECONNRESET
                      2022-02-01 18:49:41.579  - error: sonos.0 (2108) States database error: read ECONNRESET
                      2022-02-01 18:49:41.582  - error: shelly.0 (2165) Objects database error: read ECONNRESET
                      2022-02-01 18:49:41.588  - error: web.0 (2082) States database error: read ECONNRESET
                      2022-02-01 18:49:41.590  - error: alexa2.0 (2006) States database error: read ECONNRESET
                      2022-02-01 18:49:41.595  - error: trashschedule.0 (2150) States database error: read ECONNRESET
                      2022-02-01 18:49:41.575  - error: backitup.0 (5682) States database error: read ECONNRESET
                      2022-02-01 18:49:41.629  - info: trashschedule.0 (2150) cleaned everything up...
                      2022-02-01 18:49:41.631  - info: backitup.0 (5682) cleaned everything up...
                      2022-02-01 18:49:41.634  - info: fullybrowser.0 (2135) cleaned everything up...
                      2022-02-01 18:49:41.615  - error: ping.0 (1958) States database error: read ECONNRESET
                      2022-02-01 18:49:41.583  - error: discovery.0 (2056) States database error: read ECONNRESET
                      2022-02-01 18:49:41.612  - error: javascript.0 (1947) States database error: read ECONNRESET
                      2022-02-01 18:49:41.609  - error: admin.0 (1881) States database error: read ECONNRESET
                      2022-02-01 18:49:41.622  - info: sonos.0 (2108) terminating
                      2022-02-01 18:49:41.642  - error: javascript.0 (1947) Objects database error: read ECONNRESET
                      2022-02-01 18:49:41.653  - info: web.0 (2082) terminated http server on port 8082
                      2022-02-01 18:49:41.643  - info: shelly.0 (2165) Closing Adapter
                      2022-02-01 18:49:41.655  - info: admin.0 (1881) terminating http server on port 8081
                      2022-02-01 18:49:41.651  - info: javascript.0 (1947) Stop script script.js.Eigene_Skripte.Batterie_Laden
                      2022-02-01 18:49:43.134  - info: alexa2.0 (2006) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                      2022-02-01 18:49:43.136  - info: trashschedule.0 (2150) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                      2022-02-01 18:49:43.137  - info: backitup.0 (5682) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                      2022-02-01 18:49:43.140  - info: fullybrowser.0 (2135) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                      2022-02-01 18:49:43.140  - info: whatsapp-cmb.0 (2207) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                      2022-02-01 18:49:43.146  - info: ping.0 (1958) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                      2022-02-01 18:49:43.152  - info: javascript.0 (1947) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                      2022-02-01 18:49:43.156  - info: web.0 (2082) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                      2022-02-01 18:49:43.157  - info: sonos.0 (2108) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                      2022-02-01 18:49:43.159  - info: discovery.0 (2056) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                      2022-02-01 18:49:43.161  - info: shelly.0 (2165) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                      2022-02-01 18:49:43.163  - info: admin.0 (1881) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                      2022-02-01 18:49:46.590  - warn: fullybrowser.0 (2135) get state error: DB closed
                      2022-02-01 18:49:46.593  - error: shelly.0 (2165) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                      2022-02-01 18:49:46.601  - warn: alexa2.0 (2006) get state error: DB closed
                      2022-02-01 18:49:46.602  - warn: sonos.0 (2108) get state error: DB closed
                      2022-02-01 18:49:46.604  - warn: web.0 (2082) get state error: DB closed
                      2022-02-01 18:49:46.611  - error: whatsapp-cmb.0 (2207) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                      2022-02-01 18:49:46.658  - warn: discovery.0 (2056) get state error: DB closed
                      2022-02-01 18:49:46.680  - error: backitup.0 (5682) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                      2022-02-01 18:49:46.669  - error: ping.0 (1958) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                      2022-02-01 18:49:46.675  - error: admin.0 (1881) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                      2022-02-01 18:49:46.689  - error: trashschedule.0 (2150) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                      2022-02-01 18:49:46.592  - warn: fullybrowser.0 (2135) get state error: DB closed
                      2022-02-01 18:49:46.608  - warn: fullybrowser.0 (2135) get state error: DB closed
                      2022-02-01 18:49:46.610  - warn: fullybrowser.0 (2135) get state error: DB closed
                      2022-02-01 18:49:46.611  - warn: fullybrowser.0 (2135) get state error: DB closed
                      2022-02-01 18:49:46.613  - warn: fullybrowser.0 (2135) get state error: DB closed
                      2022-02-01 18:49:46.614  - warn: fullybrowser.0 (2135) get state error: DB closed
                      2022-02-01 18:49:46.616  - warn: fullybrowser.0 (2135) get state error: DB closed
                      2022-02-01 18:49:46.624  - warn: fullybrowser.0 (2135) get state error: DB closed
                      2022-02-01 18:49:46.630  - warn: fullybrowser.0 (2135) get state error: DB closed
                      2022-02-01 18:49:46.635  - warn: fullybrowser.0 (2135) get state error: DB closed
                      2022-02-01 18:49:46.640  - warn: fullybrowser.0 (2135) get state error: DB closed
                      2022-02-01 18:49:46.641  - warn: fullybrowser.0 (2135) get state error: DB closed
                      2022-02-01 18:49:46.643  - warn: fullybrowser.0 (2135) get state error: DB closed
                      2022-02-01 18:49:46.644  - warn: fullybrowser.0 (2135) get state error: DB closed
                      2022-02-01 18:49:46.645  - warn: fullybrowser.0 (2135) get state error: DB closed
                      2022-02-01 18:49:46.646  - warn: fullybrowser.0 (2135) get state error: DB closed
                      2022-02-01 18:49:46.648  - warn: fullybrowser.0 (2135) get state error: DB closed
                      2022-02-01 18:49:46.649  - warn: fullybrowser.0 (2135) get state error: DB closed
                      2022-02-01 18:49:46.686  - warn: fullybrowser.0 (2135) get state error: DB closed
                      2022-02-01 18:49:46.687  - warn: fullybrowser.0 (2135) get state error: DB closed
                      2022-02-01 18:49:46.688  - warn: fullybrowser.0 (2135) get state error: DB closed
                      2022-02-01 18:49:46.688  - warn: fullybrowser.0 (2135) get state error: DB closed
                      2022-02-01 18:49:46.689  - warn: fullybrowser.0 (2135) get state error: DB closed
                      2022-02-01 18:49:46.690  - warn: fullybrowser.0 (2135) get state error: DB closed
                      2022-02-01 18:49:46.690  - warn: fullybrowser.0 (2135) get state error: DB closed
                      2022-02-01 18:49:46.706  - warn: fullybrowser.0 (2135) get state error: DB closed
                      2022-02-01 18:49:46.707  - warn: fullybrowser.0 (2135) get state error: DB closed
                      2022-02-01 18:49:46.707  - warn: fullybrowser.0 (2135) get state error: DB closed
                      2022-02-01 18:49:46.708  - warn: fullybrowser.0 (2135) get state error: DB closed
                      2022-02-01 18:49:46.708  - warn: fullybrowser.0 (2135) get state error: DB closed
                      2022-02-01 18:49:46.709  - warn: fullybrowser.0 (2135) get state error: DB closed
                      2022-02-01 18:49:46.709  - warn: fullybrowser.0 (2135) get state error: DB closed
                      2022-02-01 18:49:46.710  - warn: fullybrowser.0 (2135) get state error: DB closed
                      2022-02-01 18:49:46.710  - warn: fullybrowser.0 (2135) get state error: DB closed
                      2022-02-01 18:49:46.617  - warn: sonos.0 (2108) get state error: DB closed
                      2022-02-01 18:49:46.619  - warn: sonos.0 (2108) get state error: DB closed
                      2022-02-01 18:49:46.621  - warn: sonos.0 (2108) get state error: DB closed
                      2022-02-01 18:49:46.622  - warn: sonos.0 (2108) get state error: DB closed
                      2022-02-01 18:49:46.623  - warn: sonos.0 (2108) get state error: DB closed
                      2022-02-01 18:49:46.625  - warn: sonos.0 (2108) get state error: DB closed
                      2022-02-01 18:49:46.636  - warn: sonos.0 (2108) get state error: DB closed
                      2022-02-01 18:49:46.637  - warn: sonos.0 (2108) get state error: DB closed
                      2022-02-01 18:49:46.639  - warn: sonos.0 (2108) get state error: DB closed
                      2022-02-01 18:49:46.640  - warn: sonos.0 (2108) get state error: DB closed
                      2022-02-01 18:49:46.666  - warn: sonos.0 (2108) get state error: DB closed
                      2022-02-01 18:49:46.667  - warn: sonos.0 (2108) get state error: DB closed
                      2022-02-01 18:49:46.668  - warn: sonos.0 (2108) get state error: DB closed
                      2022-02-01 18:49:46.668  - warn: sonos.0 (2108) get state error: DB closed
                      2022-02-01 18:49:46.669  - warn: sonos.0 (2108) get state error: DB closed
                      2022-02-01 18:49:46.670  - warn: sonos.0 (2108) get state error: DB closed
                      2022-02-01 18:49:46.670  - warn: sonos.0 (2108) get state error: DB closed
                      2022-02-01 18:49:46.671  - warn: sonos.0 (2108) get state error: DB closed
                      2022-02-01 18:49:46.671  - warn: sonos.0 (2108) get state error: DB closed
                      2022-02-01 18:49:46.672  - warn: sonos.0 (2108) get state error: DB closed
                      2022-02-01 18:49:46.673  - warn: sonos.0 (2108) get state error: DB closed
                      2022-02-01 18:49:46.673  - warn: sonos.0 (2108) get state error: DB closed
                      2022-02-01 18:49:46.674  - warn: sonos.0 (2108) get state error: DB closed
                      2022-02-01 18:49:46.674  - warn: sonos.0 (2108) get state error: DB closed
                      2022-02-01 18:49:46.675  - warn: sonos.0 (2108) get state error: DB closed
                      2022-02-01 18:49:46.675  - warn: sonos.0 (2108) get state error: DB closed
                      2022-02-01 18:49:46.687  - warn: sonos.0 (2108) get state error: DB closed
                      2022-02-01 18:49:46.688  - warn: sonos.0 (2108) get state error: DB closed
                      2022-02-01 18:49:46.689  - warn: sonos.0 (2108) get state error: DB closed
                      2022-02-01 18:49:46.689  - warn: sonos.0 (2108) get state error: DB closed
                      2022-02-01 18:49:46.690  - warn: sonos.0 (2108) get state error: DB closed
                      2022-02-01 18:49:46.690  - warn: sonos.0 (2108) get state error: DB closed
                      2022-02-01 18:49:46.716  - warn: sonos.0 (2108) get state error: DB closed
                      2022-02-01 18:49:46.717  - warn: sonos.0 (2108) get state error: DB closed
                      2022-02-01 18:49:46.726  - error: javascript.0 (1947) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                      2022-02-01 18:49:46.719  - warn: backitup.0 (5682) get state error: DB closed
                      2022-02-01 18:49:46.720  - warn: backitup.0 (5682) get state error: DB closed
                      2022-02-01 18:49:46.721  - warn: backitup.0 (5682) get state error: DB closed
                      2022-02-01 18:49:46.729  - warn: backitup.0 (5682) get state error: DB closed
                      2022-02-01 18:49:46.729  - warn: backitup.0 (5682) get state error: DB closed
                      2022-02-01 18:49:46.730  - warn: backitup.0 (5682) get state error: DB closed
                      2022-02-01 18:49:46.731  - warn: backitup.0 (5682) get state error: DB closed
                      2022-02-01 18:49:46.732  - warn: backitup.0 (5682) get state error: DB closed
                      2022-02-01 18:49:46.732  - warn: backitup.0 (5682) get state error: DB closed
                      2022-02-01 18:49:46.733  - warn: backitup.0 (5682) get state error: DB closed
                      2022-02-01 18:49:46.734  - warn: backitup.0 (5682) get state error: DB closed
                      2022-02-01 18:49:46.734  - warn: backitup.0 (5682) get state error: DB closed
                      2022-02-01 18:49:46.735  - warn: backitup.0 (5682) get state error: DB closed
                      2022-02-01 18:49:46.736  - warn: backitup.0 (5682) get state error: DB closed
                      2022-02-01 18:49:46.767  - warn: backitup.0 (5682) get state error: DB closed
                      2022-02-01 18:49:46.767  - warn: backitup.0 (5682) get state error: DB closed
                      2022-02-01 18:49:46.768  - warn: backitup.0 (5682) get state error: DB closed
                      2022-02-01 18:49:46.769  - warn: backitup.0 (5682) get state error: DB closed
                      2022-02-01 18:49:46.770  - warn: backitup.0 (5682) get state error: DB closed
                      2022-02-01 18:49:46.770  - warn: backitup.0 (5682) get state error: DB closed
                      2022-02-01 18:49:46.771  - warn: backitup.0 (5682) get state error: DB closed
                      2022-02-01 18:49:46.772  - warn: backitup.0 (5682) get state error: DB closed
                      2022-02-01 18:49:46.772  - warn: backitup.0 (5682) get state error: DB closed
                      2022-02-01 18:49:46.773  - warn: backitup.0 (5682) get state error: DB closed
                      2022-02-01 18:49:46.774  - warn: backitup.0 (5682) get state error: DB closed
                      2022-02-01 18:49:46.774  - warn: backitup.0 (5682) get state error: DB closed
                      2022-02-01 18:49:46.775  - warn: backitup.0 (5682) get state error: DB closed
                      2022-02-01 18:49:46.775  - warn: backitup.0 (5682) get state error: DB closed
                      2022-02-01 18:49:46.801  - warn: backitup.0 (5682) get state error: DB closed
                      2022-02-01 18:49:46.801  - warn: backitup.0 (5682) get state error: DB closed
                      2022-02-01 18:49:46.802  - warn: backitup.0 (5682) get state error: DB closed
                      2022-02-01 18:49:46.803  - warn: backitup.0 (5682) get state error: DB closed
                      2022-02-01 18:49:46.804  - warn: backitup.0 (5682) get state error: DB closed
                      2022-02-01 18:49:46.804  - warn: backitup.0 (5682) get state error: DB closed
                      2022-02-01 18:49:46.805  - warn: backitup.0 (5682) get state error: DB closed
                      2022-02-01 18:49:51.731  - error: backitup.0 (5682) Cannot find view "system" for search "script" : Connection is closed.
                      
                      2022-02-01 18:51:23.411  - info: host.raspberrypi instance system.adapter.backitup.0 started with pid 6157
                      2022-02-01 18:51:25.254  - info: backitup.0 (6157) starting. Version 2.2.3 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.3, js-controller: 3.3.22
                      2022-02-01 18:51:25.323  - info: backitup.0 (6157) [iobroker] backup was activated at 02:40 every 1 day(s)
                      
                      
                      Thomas BraunT Online
                      Thomas BraunT Online
                      Thomas Braun
                      Most Active
                      schrieb am zuletzt editiert von
                      #14

                      @habi989

                      iobroker status
                      

                      Linux-Werkzeugkasten:
                      https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                      NodeJS Fixer Skript:
                      https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                      iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                      1 Antwort Letzte Antwort
                      0
                      • H habi989

                        @homoran
                        so jetzt aber :D

                        
                        2022-02-01 18:00:11.207  - info: ical.0 (3551) processing URL: Müllkalender https://calendar.google.com/privat/basic.ics
                        
                        2022-02-01 18:30:10.553  - info: ical.0 (4838) starting. Version 1.11.4 in /opt/iobroker/node_modules/iobroker.ical, node: v14.18.3, js-controller: 3.3.22
                        2022-02-01 18:30:11.121  - info: ical.0 (4838) processing URL: Müllkalender https://calendar.google.com/calendar/ical/privat/basic.ics
                        
                        2022-02-01 18:48:31.475  - info: host.raspberrypi stopInstance system.adapter.backitup.0 (force=false, process=true)
                        2022-02-01 18:48:31.489  - info: backitup.0 (2180) Got terminate signal TERMINATE_YOURSELF
                        2022-02-01 18:48:31.493  - info: host.raspberrypi stopInstance system.adapter.backitup.0 send kill signal
                        2022-02-01 18:48:31.491  - info: backitup.0 (2180) cleaned everything up...
                        2022-02-01 18:48:31.493  - info: backitup.0 (2180) terminating
                        2022-02-01 18:48:31.495  - info: backitup.0 (2180) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                        2022-02-01 18:48:32.064  - info: host.raspberrypi instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                        2022-02-01 18:48:34.569  - info: host.raspberrypi instance system.adapter.backitup.0 started with pid 5682
                        2022-02-01 18:48:36.217  - info: backitup.0 (5682) starting. Version 2.2.3 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.3, js-controller: 3.3.22
                        2022-02-01 18:48:36.284  - info: backitup.0 (5682) [iobroker] backup was activated at 02:40 every 1 day(s)
                        2022-02-01 18:49:39.271  - warn: host.raspberrypi-Server Cannot read file ring.0 / doorbell_86292617/livestream86292617_1638876876746.mp4: Array buffer allocation failed
                        2022-02-01 18:49:41.569  - error: fullybrowser.0 (2135) States database error: read ECONNRESET
                        2022-02-01 18:49:41.561  - error: whatsapp-cmb.0 (2207) States database error: read ECONNRESET
                        2022-02-01 18:49:41.578  - error: shelly.0 (2165) States database error: read ECONNRESET
                        2022-02-01 18:49:41.579  - error: sonos.0 (2108) States database error: read ECONNRESET
                        2022-02-01 18:49:41.582  - error: shelly.0 (2165) Objects database error: read ECONNRESET
                        2022-02-01 18:49:41.588  - error: web.0 (2082) States database error: read ECONNRESET
                        2022-02-01 18:49:41.590  - error: alexa2.0 (2006) States database error: read ECONNRESET
                        2022-02-01 18:49:41.595  - error: trashschedule.0 (2150) States database error: read ECONNRESET
                        2022-02-01 18:49:41.575  - error: backitup.0 (5682) States database error: read ECONNRESET
                        2022-02-01 18:49:41.629  - info: trashschedule.0 (2150) cleaned everything up...
                        2022-02-01 18:49:41.631  - info: backitup.0 (5682) cleaned everything up...
                        2022-02-01 18:49:41.634  - info: fullybrowser.0 (2135) cleaned everything up...
                        2022-02-01 18:49:41.615  - error: ping.0 (1958) States database error: read ECONNRESET
                        2022-02-01 18:49:41.583  - error: discovery.0 (2056) States database error: read ECONNRESET
                        2022-02-01 18:49:41.612  - error: javascript.0 (1947) States database error: read ECONNRESET
                        2022-02-01 18:49:41.609  - error: admin.0 (1881) States database error: read ECONNRESET
                        2022-02-01 18:49:41.622  - info: sonos.0 (2108) terminating
                        2022-02-01 18:49:41.642  - error: javascript.0 (1947) Objects database error: read ECONNRESET
                        2022-02-01 18:49:41.653  - info: web.0 (2082) terminated http server on port 8082
                        2022-02-01 18:49:41.643  - info: shelly.0 (2165) Closing Adapter
                        2022-02-01 18:49:41.655  - info: admin.0 (1881) terminating http server on port 8081
                        2022-02-01 18:49:41.651  - info: javascript.0 (1947) Stop script script.js.Eigene_Skripte.Batterie_Laden
                        2022-02-01 18:49:43.134  - info: alexa2.0 (2006) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                        2022-02-01 18:49:43.136  - info: trashschedule.0 (2150) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                        2022-02-01 18:49:43.137  - info: backitup.0 (5682) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                        2022-02-01 18:49:43.140  - info: fullybrowser.0 (2135) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                        2022-02-01 18:49:43.140  - info: whatsapp-cmb.0 (2207) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                        2022-02-01 18:49:43.146  - info: ping.0 (1958) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                        2022-02-01 18:49:43.152  - info: javascript.0 (1947) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                        2022-02-01 18:49:43.156  - info: web.0 (2082) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                        2022-02-01 18:49:43.157  - info: sonos.0 (2108) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                        2022-02-01 18:49:43.159  - info: discovery.0 (2056) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                        2022-02-01 18:49:43.161  - info: shelly.0 (2165) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                        2022-02-01 18:49:43.163  - info: admin.0 (1881) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                        2022-02-01 18:49:46.590  - warn: fullybrowser.0 (2135) get state error: DB closed
                        2022-02-01 18:49:46.593  - error: shelly.0 (2165) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                        2022-02-01 18:49:46.601  - warn: alexa2.0 (2006) get state error: DB closed
                        2022-02-01 18:49:46.602  - warn: sonos.0 (2108) get state error: DB closed
                        2022-02-01 18:49:46.604  - warn: web.0 (2082) get state error: DB closed
                        2022-02-01 18:49:46.611  - error: whatsapp-cmb.0 (2207) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                        2022-02-01 18:49:46.658  - warn: discovery.0 (2056) get state error: DB closed
                        2022-02-01 18:49:46.680  - error: backitup.0 (5682) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                        2022-02-01 18:49:46.669  - error: ping.0 (1958) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                        2022-02-01 18:49:46.675  - error: admin.0 (1881) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                        2022-02-01 18:49:46.689  - error: trashschedule.0 (2150) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                        2022-02-01 18:49:46.592  - warn: fullybrowser.0 (2135) get state error: DB closed
                        2022-02-01 18:49:46.608  - warn: fullybrowser.0 (2135) get state error: DB closed
                        2022-02-01 18:49:46.610  - warn: fullybrowser.0 (2135) get state error: DB closed
                        2022-02-01 18:49:46.611  - warn: fullybrowser.0 (2135) get state error: DB closed
                        2022-02-01 18:49:46.613  - warn: fullybrowser.0 (2135) get state error: DB closed
                        2022-02-01 18:49:46.614  - warn: fullybrowser.0 (2135) get state error: DB closed
                        2022-02-01 18:49:46.616  - warn: fullybrowser.0 (2135) get state error: DB closed
                        2022-02-01 18:49:46.624  - warn: fullybrowser.0 (2135) get state error: DB closed
                        2022-02-01 18:49:46.630  - warn: fullybrowser.0 (2135) get state error: DB closed
                        2022-02-01 18:49:46.635  - warn: fullybrowser.0 (2135) get state error: DB closed
                        2022-02-01 18:49:46.640  - warn: fullybrowser.0 (2135) get state error: DB closed
                        2022-02-01 18:49:46.641  - warn: fullybrowser.0 (2135) get state error: DB closed
                        2022-02-01 18:49:46.643  - warn: fullybrowser.0 (2135) get state error: DB closed
                        2022-02-01 18:49:46.644  - warn: fullybrowser.0 (2135) get state error: DB closed
                        2022-02-01 18:49:46.645  - warn: fullybrowser.0 (2135) get state error: DB closed
                        2022-02-01 18:49:46.646  - warn: fullybrowser.0 (2135) get state error: DB closed
                        2022-02-01 18:49:46.648  - warn: fullybrowser.0 (2135) get state error: DB closed
                        2022-02-01 18:49:46.649  - warn: fullybrowser.0 (2135) get state error: DB closed
                        2022-02-01 18:49:46.686  - warn: fullybrowser.0 (2135) get state error: DB closed
                        2022-02-01 18:49:46.687  - warn: fullybrowser.0 (2135) get state error: DB closed
                        2022-02-01 18:49:46.688  - warn: fullybrowser.0 (2135) get state error: DB closed
                        2022-02-01 18:49:46.688  - warn: fullybrowser.0 (2135) get state error: DB closed
                        2022-02-01 18:49:46.689  - warn: fullybrowser.0 (2135) get state error: DB closed
                        2022-02-01 18:49:46.690  - warn: fullybrowser.0 (2135) get state error: DB closed
                        2022-02-01 18:49:46.690  - warn: fullybrowser.0 (2135) get state error: DB closed
                        2022-02-01 18:49:46.706  - warn: fullybrowser.0 (2135) get state error: DB closed
                        2022-02-01 18:49:46.707  - warn: fullybrowser.0 (2135) get state error: DB closed
                        2022-02-01 18:49:46.707  - warn: fullybrowser.0 (2135) get state error: DB closed
                        2022-02-01 18:49:46.708  - warn: fullybrowser.0 (2135) get state error: DB closed
                        2022-02-01 18:49:46.708  - warn: fullybrowser.0 (2135) get state error: DB closed
                        2022-02-01 18:49:46.709  - warn: fullybrowser.0 (2135) get state error: DB closed
                        2022-02-01 18:49:46.709  - warn: fullybrowser.0 (2135) get state error: DB closed
                        2022-02-01 18:49:46.710  - warn: fullybrowser.0 (2135) get state error: DB closed
                        2022-02-01 18:49:46.710  - warn: fullybrowser.0 (2135) get state error: DB closed
                        2022-02-01 18:49:46.617  - warn: sonos.0 (2108) get state error: DB closed
                        2022-02-01 18:49:46.619  - warn: sonos.0 (2108) get state error: DB closed
                        2022-02-01 18:49:46.621  - warn: sonos.0 (2108) get state error: DB closed
                        2022-02-01 18:49:46.622  - warn: sonos.0 (2108) get state error: DB closed
                        2022-02-01 18:49:46.623  - warn: sonos.0 (2108) get state error: DB closed
                        2022-02-01 18:49:46.625  - warn: sonos.0 (2108) get state error: DB closed
                        2022-02-01 18:49:46.636  - warn: sonos.0 (2108) get state error: DB closed
                        2022-02-01 18:49:46.637  - warn: sonos.0 (2108) get state error: DB closed
                        2022-02-01 18:49:46.639  - warn: sonos.0 (2108) get state error: DB closed
                        2022-02-01 18:49:46.640  - warn: sonos.0 (2108) get state error: DB closed
                        2022-02-01 18:49:46.666  - warn: sonos.0 (2108) get state error: DB closed
                        2022-02-01 18:49:46.667  - warn: sonos.0 (2108) get state error: DB closed
                        2022-02-01 18:49:46.668  - warn: sonos.0 (2108) get state error: DB closed
                        2022-02-01 18:49:46.668  - warn: sonos.0 (2108) get state error: DB closed
                        2022-02-01 18:49:46.669  - warn: sonos.0 (2108) get state error: DB closed
                        2022-02-01 18:49:46.670  - warn: sonos.0 (2108) get state error: DB closed
                        2022-02-01 18:49:46.670  - warn: sonos.0 (2108) get state error: DB closed
                        2022-02-01 18:49:46.671  - warn: sonos.0 (2108) get state error: DB closed
                        2022-02-01 18:49:46.671  - warn: sonos.0 (2108) get state error: DB closed
                        2022-02-01 18:49:46.672  - warn: sonos.0 (2108) get state error: DB closed
                        2022-02-01 18:49:46.673  - warn: sonos.0 (2108) get state error: DB closed
                        2022-02-01 18:49:46.673  - warn: sonos.0 (2108) get state error: DB closed
                        2022-02-01 18:49:46.674  - warn: sonos.0 (2108) get state error: DB closed
                        2022-02-01 18:49:46.674  - warn: sonos.0 (2108) get state error: DB closed
                        2022-02-01 18:49:46.675  - warn: sonos.0 (2108) get state error: DB closed
                        2022-02-01 18:49:46.675  - warn: sonos.0 (2108) get state error: DB closed
                        2022-02-01 18:49:46.687  - warn: sonos.0 (2108) get state error: DB closed
                        2022-02-01 18:49:46.688  - warn: sonos.0 (2108) get state error: DB closed
                        2022-02-01 18:49:46.689  - warn: sonos.0 (2108) get state error: DB closed
                        2022-02-01 18:49:46.689  - warn: sonos.0 (2108) get state error: DB closed
                        2022-02-01 18:49:46.690  - warn: sonos.0 (2108) get state error: DB closed
                        2022-02-01 18:49:46.690  - warn: sonos.0 (2108) get state error: DB closed
                        2022-02-01 18:49:46.716  - warn: sonos.0 (2108) get state error: DB closed
                        2022-02-01 18:49:46.717  - warn: sonos.0 (2108) get state error: DB closed
                        2022-02-01 18:49:46.726  - error: javascript.0 (1947) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                        2022-02-01 18:49:46.719  - warn: backitup.0 (5682) get state error: DB closed
                        2022-02-01 18:49:46.720  - warn: backitup.0 (5682) get state error: DB closed
                        2022-02-01 18:49:46.721  - warn: backitup.0 (5682) get state error: DB closed
                        2022-02-01 18:49:46.729  - warn: backitup.0 (5682) get state error: DB closed
                        2022-02-01 18:49:46.729  - warn: backitup.0 (5682) get state error: DB closed
                        2022-02-01 18:49:46.730  - warn: backitup.0 (5682) get state error: DB closed
                        2022-02-01 18:49:46.731  - warn: backitup.0 (5682) get state error: DB closed
                        2022-02-01 18:49:46.732  - warn: backitup.0 (5682) get state error: DB closed
                        2022-02-01 18:49:46.732  - warn: backitup.0 (5682) get state error: DB closed
                        2022-02-01 18:49:46.733  - warn: backitup.0 (5682) get state error: DB closed
                        2022-02-01 18:49:46.734  - warn: backitup.0 (5682) get state error: DB closed
                        2022-02-01 18:49:46.734  - warn: backitup.0 (5682) get state error: DB closed
                        2022-02-01 18:49:46.735  - warn: backitup.0 (5682) get state error: DB closed
                        2022-02-01 18:49:46.736  - warn: backitup.0 (5682) get state error: DB closed
                        2022-02-01 18:49:46.767  - warn: backitup.0 (5682) get state error: DB closed
                        2022-02-01 18:49:46.767  - warn: backitup.0 (5682) get state error: DB closed
                        2022-02-01 18:49:46.768  - warn: backitup.0 (5682) get state error: DB closed
                        2022-02-01 18:49:46.769  - warn: backitup.0 (5682) get state error: DB closed
                        2022-02-01 18:49:46.770  - warn: backitup.0 (5682) get state error: DB closed
                        2022-02-01 18:49:46.770  - warn: backitup.0 (5682) get state error: DB closed
                        2022-02-01 18:49:46.771  - warn: backitup.0 (5682) get state error: DB closed
                        2022-02-01 18:49:46.772  - warn: backitup.0 (5682) get state error: DB closed
                        2022-02-01 18:49:46.772  - warn: backitup.0 (5682) get state error: DB closed
                        2022-02-01 18:49:46.773  - warn: backitup.0 (5682) get state error: DB closed
                        2022-02-01 18:49:46.774  - warn: backitup.0 (5682) get state error: DB closed
                        2022-02-01 18:49:46.774  - warn: backitup.0 (5682) get state error: DB closed
                        2022-02-01 18:49:46.775  - warn: backitup.0 (5682) get state error: DB closed
                        2022-02-01 18:49:46.775  - warn: backitup.0 (5682) get state error: DB closed
                        2022-02-01 18:49:46.801  - warn: backitup.0 (5682) get state error: DB closed
                        2022-02-01 18:49:46.801  - warn: backitup.0 (5682) get state error: DB closed
                        2022-02-01 18:49:46.802  - warn: backitup.0 (5682) get state error: DB closed
                        2022-02-01 18:49:46.803  - warn: backitup.0 (5682) get state error: DB closed
                        2022-02-01 18:49:46.804  - warn: backitup.0 (5682) get state error: DB closed
                        2022-02-01 18:49:46.804  - warn: backitup.0 (5682) get state error: DB closed
                        2022-02-01 18:49:46.805  - warn: backitup.0 (5682) get state error: DB closed
                        2022-02-01 18:49:51.731  - error: backitup.0 (5682) Cannot find view "system" for search "script" : Connection is closed.
                        
                        2022-02-01 18:51:23.411  - info: host.raspberrypi instance system.adapter.backitup.0 started with pid 6157
                        2022-02-01 18:51:25.254  - info: backitup.0 (6157) starting. Version 2.2.3 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.3, js-controller: 3.3.22
                        2022-02-01 18:51:25.323  - info: backitup.0 (6157) [iobroker] backup was activated at 02:40 every 1 day(s)
                        
                        
                        HomoranH Offline
                        HomoranH Offline
                        Homoran
                        Global Moderator Administrators
                        schrieb am zuletzt editiert von
                        #15

                        @habi989 sagte in Backitup Mount Error Synology NAS:

                        so jetzt aber

                        was ist das?
                        Hat mein Tablet lahmgelegt.
                        Seitenweise info, warn und error die nix mit dem backitup zu tun haben, aber kein backitup debug

                        kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

                        Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

                        der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

                        H 1 Antwort Letzte Antwort
                        0
                        • HomoranH Homoran

                          @habi989 sagte in Backitup Mount Error Synology NAS:

                          so jetzt aber

                          was ist das?
                          Hat mein Tablet lahmgelegt.
                          Seitenweise info, warn und error die nix mit dem backitup zu tun haben, aber kein backitup debug

                          H Offline
                          H Offline
                          habi989
                          schrieb am zuletzt editiert von
                          #16

                          @homoran

                          Hi, sorry das walnatürlich nicht meine Absicht.

                          Ich habe das Log nun gesäubert und alle anderen Warnungen etc. herausgelöscht. Hier nun was der Backitup Adapter meldet.

                          2022-02-02 09:49:41.089  - error: host.raspberrypi uncaught exception: Array buffer allocation failed
                          2022-02-02 09:49:42.635  - error: backitup.0 (25330) States database error: read ECONNRESET
                          2022-02-02 09:49:42.660  - info: backitup.0 (25330) cleaned everything up...
                          2022-02-02 09:49:42.635  - error: backitup.0 (25330) States database error: read ECONNRESET
                          2022-02-02 09:49:42.660  - info: backitup.0 (25330) cleaned everything up...
                          2022-02-02 09:49:44.171  - info: backitup.0 (25330) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                          2022-02-02 09:49:44.171  - info: backitup.0 (25330) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                          2022-02-02 09:49:47.653  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.655  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.657  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.660  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.663  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.664  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.667  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.669  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.670  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.672  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.674  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.676  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.677  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.679  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.680  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.681  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.683  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.698  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.698  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.699  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.707  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.708  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.709  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.710  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.711  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.712  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.713  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.716  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.717  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.717  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.718  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.719  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.719  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.720  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.721  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.653  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.655  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.657  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.660  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.663  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.664  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.667  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.669  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.670  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.672  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.674  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.676  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.677  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.679  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.680  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.681  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.683  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.698  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.698  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.699  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.707  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.708  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.709  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.710  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.711  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.712  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.713  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.716  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.717  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.717  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.718  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.719  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.719  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.720  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:49:47.721  - warn: backitup.0 (25330) get state error: DB closed
                          2022-02-02 09:50:53.250  - error: backitup.0 (10769) backitup.0 already running
                          2022-02-02 09:50:53.255  - warn: backitup.0 (10769) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                          2022-02-02 09:50:53.250  - error: backitup.0 (10769) backitup.0 already running
                          2022-02-02 09:50:53.255  - warn: backitup.0 (10769) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                          2022-02-02 09:51:25.869  - info: backitup.0 (10871) starting. Version 2.2.3 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.3, js-controller: 3.3.22
                          2022-02-02 09:51:25.933  - info: backitup.0 (10871) [iobroker] backup was activated at 02:40 every 1 day(s)
                          2022-02-02 09:51:25.869  - info: backitup.0 (10871) starting. Version 2.2.3 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.3, js-controller: 3.3.22
                          2022-02-02 09:51:25.933  - info: backitup.0 (10871) [iobroker] backup was activated at 02:40 every 1 day(s)
                          
                          
                          HomoranH 1 Antwort Letzte Antwort
                          0
                          • H habi989

                            @homoran

                            Hi, sorry das walnatürlich nicht meine Absicht.

                            Ich habe das Log nun gesäubert und alle anderen Warnungen etc. herausgelöscht. Hier nun was der Backitup Adapter meldet.

                            2022-02-02 09:49:41.089  - error: host.raspberrypi uncaught exception: Array buffer allocation failed
                            2022-02-02 09:49:42.635  - error: backitup.0 (25330) States database error: read ECONNRESET
                            2022-02-02 09:49:42.660  - info: backitup.0 (25330) cleaned everything up...
                            2022-02-02 09:49:42.635  - error: backitup.0 (25330) States database error: read ECONNRESET
                            2022-02-02 09:49:42.660  - info: backitup.0 (25330) cleaned everything up...
                            2022-02-02 09:49:44.171  - info: backitup.0 (25330) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                            2022-02-02 09:49:44.171  - info: backitup.0 (25330) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                            2022-02-02 09:49:47.653  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.655  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.657  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.660  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.663  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.664  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.667  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.669  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.670  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.672  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.674  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.676  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.677  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.679  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.680  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.681  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.683  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.698  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.698  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.699  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.707  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.708  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.709  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.710  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.711  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.712  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.713  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.716  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.717  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.717  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.718  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.719  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.719  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.720  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.721  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.653  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.655  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.657  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.660  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.663  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.664  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.667  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.669  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.670  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.672  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.674  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.676  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.677  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.679  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.680  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.681  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.683  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.698  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.698  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.699  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.707  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.708  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.709  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.710  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.711  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.712  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.713  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.716  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.717  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.717  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.718  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.719  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.719  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.720  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:49:47.721  - warn: backitup.0 (25330) get state error: DB closed
                            2022-02-02 09:50:53.250  - error: backitup.0 (10769) backitup.0 already running
                            2022-02-02 09:50:53.255  - warn: backitup.0 (10769) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                            2022-02-02 09:50:53.250  - error: backitup.0 (10769) backitup.0 already running
                            2022-02-02 09:50:53.255  - warn: backitup.0 (10769) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                            2022-02-02 09:51:25.869  - info: backitup.0 (10871) starting. Version 2.2.3 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.3, js-controller: 3.3.22
                            2022-02-02 09:51:25.933  - info: backitup.0 (10871) [iobroker] backup was activated at 02:40 every 1 day(s)
                            2022-02-02 09:51:25.869  - info: backitup.0 (10871) starting. Version 2.2.3 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.3, js-controller: 3.3.22
                            2022-02-02 09:51:25.933  - info: backitup.0 (10871) [iobroker] backup was activated at 02:40 every 1 day(s)
                            
                            
                            HomoranH Offline
                            HomoranH Offline
                            Homoran
                            Global Moderator Administrators
                            schrieb am zuletzt editiert von Homoran
                            #17

                            @habi989 sagte in Backitup Mount Error Synology NAS:

                            Hier nun was der Backitup Adapter meldet.

                            das ist immer noch kein debug-log!
                            hast du die Instanz auch auf Logstufe debug gestellt?

                            Bin mal am PC und habe deinen letzten Riesen-log mal etwas gekürzt.

                            Dabei habe ich eine Zeile gesehen, die mich stutzig macht:

                            @habi989 sagte in Backitup Mount Error Synology NAS:

                            warn: host.raspberrypi-Server Cannot read file ring.0 / doorbell_86292617/livestream86292617_1638876876746.mp4:

                            hast du etwa tausende MB an Videos im Backup?

                            kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

                            Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

                            der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

                            H 2 Antworten Letzte Antwort
                            0
                            • HomoranH Homoran

                              @habi989 sagte in Backitup Mount Error Synology NAS:

                              Hier nun was der Backitup Adapter meldet.

                              das ist immer noch kein debug-log!
                              hast du die Instanz auch auf Logstufe debug gestellt?

                              Bin mal am PC und habe deinen letzten Riesen-log mal etwas gekürzt.

                              Dabei habe ich eine Zeile gesehen, die mich stutzig macht:

                              @habi989 sagte in Backitup Mount Error Synology NAS:

                              warn: host.raspberrypi-Server Cannot read file ring.0 / doorbell_86292617/livestream86292617_1638876876746.mp4:

                              hast du etwa tausende MB an Videos im Backup?

                              H Offline
                              H Offline
                              habi989
                              schrieb am zuletzt editiert von
                              #18

                              @homoran

                              ach jetzt habe ich kapiert was du mir sagen wolltest. So habe es auf debug gestellt. so wie ich das sehe findet er kein backup?

                              2022-02-02 13:56:53.835  - debug: backitup.0 (22002) Redis Objects: Use Redis connection: 127.0.0.1:9001
                              2022-02-02 13:56:53.934  - debug: backitup.0 (22002) Objects client ready ... initialize now
                              2022-02-02 13:56:53.937  - debug: backitup.0 (22002) Objects create System PubSub Client
                              2022-02-02 13:56:53.939  - debug: backitup.0 (22002) Objects create User PubSub Client
                              2022-02-02 13:56:53.941  - debug: backitup.0 (22002) Objects client initialize lua scripts
                              2022-02-02 13:56:53.956  - debug: backitup.0 (22002) Objects connected to redis: 127.0.0.1:9001
                              2022-02-02 13:56:53.965  - debug: backitup.0 (22002) objectDB connected
                              2022-02-02 13:56:53.967  - debug: backitup.0 (22002) Redis States: Use Redis connection: 127.0.0.1:9000
                              2022-02-02 13:56:53.976  - debug: backitup.0 (22002) States create System PubSub Client
                              2022-02-02 13:56:53.978  - debug: backitup.0 (22002) States create User PubSub Client
                              2022-02-02 13:56:53.988  - debug: backitup.0 (22002) States connected to redis: 127.0.0.1:9000
                              2022-02-02 13:56:53.989  - debug: backitup.0 (22002) statesDB connected
                              2022-02-02 13:56:54.283  - debug: backitup.0 (22002) Plugin sentry Initialize Plugin (enabled=true)
                              2022-02-02 13:56:54.495  - info: backitup.0 (22002) starting. Version 2.2.3 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.3, js-controller: 3.3.22
                              2022-02-02 13:56:54.540  - debug: backitup.0 (22002) Backitup has recognized a linux system
                              2022-02-02 13:56:54.646  - debug: backitup.0 (22002) [iobroker] 10 40 02 */1 * * 
                              2022-02-02 13:56:54.668  - debug: backitup.0 (22002) noserverino option: true
                              2022-02-02 13:56:54.669  - debug: backitup.0 (22002) cifs-mount command: "sudo mount -t cifs -o username=backitup,password=****,noserverino,rw,file_mode=0777,dir_mode=0777,vers=3.0 //192.168.178.2Backupio/iobroker /opt/iobroker/backups"
                              2022-02-02 13:56:54.745  - debug: backitup.0 (22002) first mount attempt with smb option failed. try next mount attempt without smb option ...
                              2022-02-02 13:56:54.746  - debug: backitup.0 (22002) cifs-mount command: "sudo mount -t cifs -o username=backitup,password=****,noserverino,rw,file_mode=0777,dir_mode=0777 //192.168.178.2Backupio/iobroker /opt/iobroker/backups"
                              2022-02-02 13:56:54.833  - debug: backitup.0 (22002) mount successfully completed
                              2022-02-02 13:56:56.843  - debug: backitup.0 (22002) No backup file was found
                              2022-02-02 13:56:56.843  - debug: backitup.0 (22002) No backup file was found
                              2022-02-02 13:57:04.585  - debug: backitup.0 (22002) mount activ... umount in 2 Seconds!!
                              2022-02-02 13:57:04.585  - debug: backitup.0 (22002) mount activ... umount in 2 Seconds!!
                              2022-02-02 13:57:06.685  - debug: backitup.0 (22002) umount successfully completed
                              2022-02-02 13:57:06.685  - debug: backitup.0 (22002) umount successfully completed
                              
                              HomoranH Thomas BraunT 2 Antworten Letzte Antwort
                              0
                              • HomoranH Homoran

                                @habi989 sagte in Backitup Mount Error Synology NAS:

                                Hier nun was der Backitup Adapter meldet.

                                das ist immer noch kein debug-log!
                                hast du die Instanz auch auf Logstufe debug gestellt?

                                Bin mal am PC und habe deinen letzten Riesen-log mal etwas gekürzt.

                                Dabei habe ich eine Zeile gesehen, die mich stutzig macht:

                                @habi989 sagte in Backitup Mount Error Synology NAS:

                                warn: host.raspberrypi-Server Cannot read file ring.0 / doorbell_86292617/livestream86292617_1638876876746.mp4:

                                hast du etwa tausende MB an Videos im Backup?

                                H Offline
                                H Offline
                                habi989
                                schrieb am zuletzt editiert von
                                #19

                                @homoran

                                Hi,

                                ja die Video der Ring werden auf der sd karte abgelegt... etwa 20gb ohne jetzt genau nachzusehen...

                                GlasfaserG 1 Antwort Letzte Antwort
                                0
                                • H habi989

                                  @homoran

                                  ach jetzt habe ich kapiert was du mir sagen wolltest. So habe es auf debug gestellt. so wie ich das sehe findet er kein backup?

                                  2022-02-02 13:56:53.835  - debug: backitup.0 (22002) Redis Objects: Use Redis connection: 127.0.0.1:9001
                                  2022-02-02 13:56:53.934  - debug: backitup.0 (22002) Objects client ready ... initialize now
                                  2022-02-02 13:56:53.937  - debug: backitup.0 (22002) Objects create System PubSub Client
                                  2022-02-02 13:56:53.939  - debug: backitup.0 (22002) Objects create User PubSub Client
                                  2022-02-02 13:56:53.941  - debug: backitup.0 (22002) Objects client initialize lua scripts
                                  2022-02-02 13:56:53.956  - debug: backitup.0 (22002) Objects connected to redis: 127.0.0.1:9001
                                  2022-02-02 13:56:53.965  - debug: backitup.0 (22002) objectDB connected
                                  2022-02-02 13:56:53.967  - debug: backitup.0 (22002) Redis States: Use Redis connection: 127.0.0.1:9000
                                  2022-02-02 13:56:53.976  - debug: backitup.0 (22002) States create System PubSub Client
                                  2022-02-02 13:56:53.978  - debug: backitup.0 (22002) States create User PubSub Client
                                  2022-02-02 13:56:53.988  - debug: backitup.0 (22002) States connected to redis: 127.0.0.1:9000
                                  2022-02-02 13:56:53.989  - debug: backitup.0 (22002) statesDB connected
                                  2022-02-02 13:56:54.283  - debug: backitup.0 (22002) Plugin sentry Initialize Plugin (enabled=true)
                                  2022-02-02 13:56:54.495  - info: backitup.0 (22002) starting. Version 2.2.3 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.3, js-controller: 3.3.22
                                  2022-02-02 13:56:54.540  - debug: backitup.0 (22002) Backitup has recognized a linux system
                                  2022-02-02 13:56:54.646  - debug: backitup.0 (22002) [iobroker] 10 40 02 */1 * * 
                                  2022-02-02 13:56:54.668  - debug: backitup.0 (22002) noserverino option: true
                                  2022-02-02 13:56:54.669  - debug: backitup.0 (22002) cifs-mount command: "sudo mount -t cifs -o username=backitup,password=****,noserverino,rw,file_mode=0777,dir_mode=0777,vers=3.0 //192.168.178.2Backupio/iobroker /opt/iobroker/backups"
                                  2022-02-02 13:56:54.745  - debug: backitup.0 (22002) first mount attempt with smb option failed. try next mount attempt without smb option ...
                                  2022-02-02 13:56:54.746  - debug: backitup.0 (22002) cifs-mount command: "sudo mount -t cifs -o username=backitup,password=****,noserverino,rw,file_mode=0777,dir_mode=0777 //192.168.178.2Backupio/iobroker /opt/iobroker/backups"
                                  2022-02-02 13:56:54.833  - debug: backitup.0 (22002) mount successfully completed
                                  2022-02-02 13:56:56.843  - debug: backitup.0 (22002) No backup file was found
                                  2022-02-02 13:56:56.843  - debug: backitup.0 (22002) No backup file was found
                                  2022-02-02 13:57:04.585  - debug: backitup.0 (22002) mount activ... umount in 2 Seconds!!
                                  2022-02-02 13:57:04.585  - debug: backitup.0 (22002) mount activ... umount in 2 Seconds!!
                                  2022-02-02 13:57:06.685  - debug: backitup.0 (22002) umount successfully completed
                                  2022-02-02 13:57:06.685  - debug: backitup.0 (22002) umount successfully completed
                                  
                                  HomoranH Offline
                                  HomoranH Offline
                                  Homoran
                                  Global Moderator Administrators
                                  schrieb am zuletzt editiert von
                                  #20

                                  @habi989 sagte in Backitup Mount Error Synology NAS:

                                  so wie ich das sehe findet er kein backup?

                                  was hast du denn gemacht, damit er danach sucht?

                                  Hast du dazu noch eine Antwort?

                                  @homoran sagte in Backitup Mount Error Synology NAS:

                                  Dabei habe ich eine Zeile gesehen, die mich stutzig macht:
                                  @habi989 sagte in Backitup Mount Error Synology NAS:

                                  warn: host.raspberrypi-Server Cannot read file ring.0 / doorbell_86292617/livestream86292617_1638876876746.mp4:

                                  hast du etwa tausende MB an Videos im Backup?

                                  kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

                                  Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

                                  der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

                                  1 Antwort Letzte Antwort
                                  0
                                  • H habi989

                                    @homoran

                                    Hi,

                                    ja die Video der Ring werden auf der sd karte abgelegt... etwa 20gb ohne jetzt genau nachzusehen...

                                    GlasfaserG Offline
                                    GlasfaserG Offline
                                    Glasfaser
                                    schrieb am zuletzt editiert von
                                    #21

                                    @habi989

                                    Zeige mal die Ausgabe von :

                                    du -hs /opt/iobroker/iobroker-data/files/*
                                    

                                    Synology 918+ 16GB - ioBroker in Docker v9 , VISO auf Trekstor Primebook C13 13,3" , Hikvision Domkameras mit Surveillance Station .. CCU RaspberryMatic in Synology VM .. Zigbee CC2538+CC2592 .. Sonoff .. KNX .. Modbus ..

                                    H 1 Antwort Letzte Antwort
                                    0
                                    • H habi989

                                      @homoran

                                      ach jetzt habe ich kapiert was du mir sagen wolltest. So habe es auf debug gestellt. so wie ich das sehe findet er kein backup?

                                      2022-02-02 13:56:53.835  - debug: backitup.0 (22002) Redis Objects: Use Redis connection: 127.0.0.1:9001
                                      2022-02-02 13:56:53.934  - debug: backitup.0 (22002) Objects client ready ... initialize now
                                      2022-02-02 13:56:53.937  - debug: backitup.0 (22002) Objects create System PubSub Client
                                      2022-02-02 13:56:53.939  - debug: backitup.0 (22002) Objects create User PubSub Client
                                      2022-02-02 13:56:53.941  - debug: backitup.0 (22002) Objects client initialize lua scripts
                                      2022-02-02 13:56:53.956  - debug: backitup.0 (22002) Objects connected to redis: 127.0.0.1:9001
                                      2022-02-02 13:56:53.965  - debug: backitup.0 (22002) objectDB connected
                                      2022-02-02 13:56:53.967  - debug: backitup.0 (22002) Redis States: Use Redis connection: 127.0.0.1:9000
                                      2022-02-02 13:56:53.976  - debug: backitup.0 (22002) States create System PubSub Client
                                      2022-02-02 13:56:53.978  - debug: backitup.0 (22002) States create User PubSub Client
                                      2022-02-02 13:56:53.988  - debug: backitup.0 (22002) States connected to redis: 127.0.0.1:9000
                                      2022-02-02 13:56:53.989  - debug: backitup.0 (22002) statesDB connected
                                      2022-02-02 13:56:54.283  - debug: backitup.0 (22002) Plugin sentry Initialize Plugin (enabled=true)
                                      2022-02-02 13:56:54.495  - info: backitup.0 (22002) starting. Version 2.2.3 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.3, js-controller: 3.3.22
                                      2022-02-02 13:56:54.540  - debug: backitup.0 (22002) Backitup has recognized a linux system
                                      2022-02-02 13:56:54.646  - debug: backitup.0 (22002) [iobroker] 10 40 02 */1 * * 
                                      2022-02-02 13:56:54.668  - debug: backitup.0 (22002) noserverino option: true
                                      2022-02-02 13:56:54.669  - debug: backitup.0 (22002) cifs-mount command: "sudo mount -t cifs -o username=backitup,password=****,noserverino,rw,file_mode=0777,dir_mode=0777,vers=3.0 //192.168.178.2Backupio/iobroker /opt/iobroker/backups"
                                      2022-02-02 13:56:54.745  - debug: backitup.0 (22002) first mount attempt with smb option failed. try next mount attempt without smb option ...
                                      2022-02-02 13:56:54.746  - debug: backitup.0 (22002) cifs-mount command: "sudo mount -t cifs -o username=backitup,password=****,noserverino,rw,file_mode=0777,dir_mode=0777 //192.168.178.2Backupio/iobroker /opt/iobroker/backups"
                                      2022-02-02 13:56:54.833  - debug: backitup.0 (22002) mount successfully completed
                                      2022-02-02 13:56:56.843  - debug: backitup.0 (22002) No backup file was found
                                      2022-02-02 13:56:56.843  - debug: backitup.0 (22002) No backup file was found
                                      2022-02-02 13:57:04.585  - debug: backitup.0 (22002) mount activ... umount in 2 Seconds!!
                                      2022-02-02 13:57:04.585  - debug: backitup.0 (22002) mount activ... umount in 2 Seconds!!
                                      2022-02-02 13:57:06.685  - debug: backitup.0 (22002) umount successfully completed
                                      2022-02-02 13:57:06.685  - debug: backitup.0 (22002) umount successfully completed
                                      
                                      Thomas BraunT Online
                                      Thomas BraunT Online
                                      Thomas Braun
                                      Most Active
                                      schrieb am zuletzt editiert von
                                      #22

                                      @habi989 sagte in Backitup Mount Error Synology NAS:

                                      192.168.178.2Backupio/iobroker

                                      Da fehlt ein /
                                      Zeigmal die Pfad in den Einstellungen für das NAS.
                                      Ist das eine FritzBox da?

                                      Die 20GB Hollywood-Filme dürften dir das Genick brechen, wenn die Backup-Pfad liegen.

                                      Linux-Werkzeugkasten:
                                      https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                                      NodeJS Fixer Skript:
                                      https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                                      iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                                      H 1 Antwort Letzte Antwort
                                      0
                                      • GlasfaserG Glasfaser

                                        @habi989

                                        Zeige mal die Ausgabe von :

                                        du -hs /opt/iobroker/iobroker-data/files/*
                                        
                                        H Offline
                                        H Offline
                                        habi989
                                        schrieb am zuletzt editiert von
                                        #23

                                        @glasfaser

                                        pi@raspberrypi:/opt/iobroker $ du -hs /opt/iobroker/iobroker-data/files/*
                                        252K	/opt/iobroker/iobroker-data/files/admin.admin
                                        1.2M	/opt/iobroker/iobroker-data/files/alexa2.admin
                                        368K	/opt/iobroker/iobroker-data/files/backitup.admin
                                        4.9M	/opt/iobroker/iobroker-data/files/daswetter.admin
                                        640K	/opt/iobroker/iobroker-data/files/discovery.admin
                                        100K	/opt/iobroker/iobroker-data/files/dwd.admin
                                        28K	/opt/iobroker/iobroker-data/files/fullybrowser.admin
                                        52K	/opt/iobroker/iobroker-data/files/gruenbeck.admin
                                        88K	/opt/iobroker/iobroker-data/files/ical.admin
                                        20M	/opt/iobroker/iobroker-data/files/icons-icons8
                                        12K	/opt/iobroker/iobroker-data/files/icons-icons8.admin
                                        16K	/opt/iobroker/iobroker-data/files/icons-mfd-png.admin
                                        6.8M	/opt/iobroker/iobroker-data/files/icons-ultimate-png
                                        20K	/opt/iobroker/iobroker-data/files/icons-ultimate-png.admin
                                        27M	/opt/iobroker/iobroker-data/files/javascript.admin
                                        124K	/opt/iobroker/iobroker-data/files/ping.admin
                                        5.1G	/opt/iobroker/iobroker-data/files/ring.0
                                        40K	/opt/iobroker/iobroker-data/files/ring.admin
                                        204K	/opt/iobroker/iobroker-data/files/shelly.admin
                                        48K	/opt/iobroker/iobroker-data/files/sonos.admin
                                        176K	/opt/iobroker/iobroker-data/files/synology.admin
                                        76K	/opt/iobroker/iobroker-data/files/tr-064.admin
                                        216K	/opt/iobroker/iobroker-data/files/trashschedule.admin
                                        15M	/opt/iobroker/iobroker-data/files/vis
                                        8.8M	/opt/iobroker/iobroker-data/files/vis.0
                                        48K	/opt/iobroker/iobroker-data/files/vis.admin
                                        24K	/opt/iobroker/iobroker-data/files/vis-hqwidgets.admin
                                        12K	/opt/iobroker/iobroker-data/files/vis-jqui-mfd.admin
                                        36K	/opt/iobroker/iobroker-data/files/vis-metro.admin
                                        68K	/opt/iobroker/iobroker-data/files/vis-players.admin
                                        20K	/opt/iobroker/iobroker-data/files/vis-timeandweather.admin
                                        36K	/opt/iobroker/iobroker-data/files/vis-weather.admin
                                        7.9M	/opt/iobroker/iobroker-data/files/web
                                        9.4M	/opt/iobroker/iobroker-data/files/web.admin
                                        88K	/opt/iobroker/iobroker-data/files/whatsapp-cmb.admin
                                        
                                        HomoranH 1 Antwort Letzte Antwort
                                        0
                                        • Thomas BraunT Thomas Braun

                                          @habi989 sagte in Backitup Mount Error Synology NAS:

                                          192.168.178.2Backupio/iobroker

                                          Da fehlt ein /
                                          Zeigmal die Pfad in den Einstellungen für das NAS.
                                          Ist das eine FritzBox da?

                                          Die 20GB Hollywood-Filme dürften dir das Genick brechen, wenn die Backup-Pfad liegen.

                                          H Offline
                                          H Offline
                                          habi989
                                          schrieb am zuletzt editiert von
                                          #24

                                          @thomas-braun

                                          meinst du diese Pfade?

                                          Bildschirmfoto 2022-02-02 um 15.27.28.png

                                          Thomas BraunT 1 Antwort Letzte Antwort
                                          0
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen


                                          Support us

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

                                          337

                                          Online

                                          32.6k

                                          Benutzer

                                          82.1k

                                          Themen

                                          1.3m

                                          Beiträge
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Anmelden

                                          • Du hast noch kein Konto? Registrieren

                                          • Anmelden oder registrieren, um zu suchen
                                          • Erster Beitrag
                                            Letzter Beitrag
                                          0
                                          • Home
                                          • Aktuell
                                          • Tags
                                          • Ungelesen 0
                                          • Kategorien
                                          • Unreplied
                                          • Beliebt
                                          • GitHub
                                          • Docu
                                          • Hilfe