Weiter zum Inhalt
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Hell
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dunkel
  • 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. iobroker stürzt ab, MISCONF Redis is configured to save RDB

NEWS

  • Neues YouTube-Video: Visualisierung im Devices-Adapter
    BluefoxB
    Bluefox
    11
    1
    328

  • Neuer ioBroker-Blog online: Monatsrückblick März/April 2026
    BluefoxB
    Bluefox
    8
    1
    1.9k

  • Verwendung von KI bitte immer deutlich kennzeichnen
    HomoranH
    Homoran
    11
    1
    793

iobroker stürzt ab, MISCONF Redis is configured to save RDB

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
iobrokerhostredis
19 Beiträge 4 Kommentatoren 1.5k Aufrufe 4 Beobachtet
  • Ä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.
  • coyoteC coyote

    @wendy2702 ich habe nochmal nachgeschaut, Redis läuft auf dem gleichen Server wie iobroker.

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

    @coyote

    Könnte mit den Rechten zusammenhängen. Ist der iobroker in der redis-Gruppe drin?

    sudo -u iobroker groups
    

    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

    coyoteC 1 Antwort Letzte Antwort
    0
    • Thomas BraunT Thomas Braun

      @coyote

      Könnte mit den Rechten zusammenhängen. Ist der iobroker in der redis-Gruppe drin?

      sudo -u iobroker groups
      
      coyoteC Offline
      coyoteC Offline
      coyote
      Most Active
      schrieb am zuletzt editiert von
      #6

      @thomas-braun japp, ist drin.

      iobroker tty dialout audio video redis bluetooth
      
      
      Thomas BraunT 1 Antwort Letzte Antwort
      0
      • coyoteC coyote

        @thomas-braun japp, ist drin.

        iobroker tty dialout audio video redis bluetooth
        
        
        Thomas BraunT Online
        Thomas BraunT Online
        Thomas Braun
        Most Active
        schrieb am zuletzt editiert von
        #7

        @coyote
        Und was steht im redis-log?

        cat /var/log/redis/redis-server.log
        

        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

        coyoteC 1 Antwort Letzte Antwort
        0
        • Thomas BraunT Thomas Braun

          @coyote
          Und was steht im redis-log?

          cat /var/log/redis/redis-server.log
          
          coyoteC Offline
          coyoteC Offline
          coyote
          Most Active
          schrieb am zuletzt editiert von
          #8

          @thomas-braun ich habe mal das rausgesucht von dem Tag. Ich seh da nix, außer die Unterbrechung um 18:58 Uhr am 16 April

          redis-server.log.1

          Thomas BraunT 1 Antwort Letzte Antwort
          0
          • coyoteC coyote

            @thomas-braun ich habe mal das rausgesucht von dem Tag. Ich seh da nix, außer die Unterbrechung um 18:58 Uhr am 16 April

            redis-server.log.1

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

            @coyote

            Immer wieder

            10000 changes in 60 seconds.
            

            mir scheint da irgendwas aus dem Ruder zu laufen und 10000 ist der Deckel.
            Ich denke aber auch das 10000 Änderungen in 60 Sekunden ungewöhnlich viel ist. Was hast du denn da laufen, was so viele Änderungen auslöst?

            Also bei mir schaut das wesentlich entspannter aus:

            519:M 21 Apr 2021 17:40:30.142 * Background saving terminated with success
            519:M 21 Apr 2021 17:45:31.001 * 10 changes in 300 seconds. Saving...
            519:M 21 Apr 2021 17:45:31.003 * Background saving started by pid 19801
            19801:C 21 Apr 2021 17:45:31.158 * DB saved on disk
            19801:C 21 Apr 2021 17:45:31.161 * RDB: 0 MB of memory used by copy-on-write
            519:M 21 Apr 2021 17:45:31.204 * Background saving terminated with success
            519:M 21 Apr 2021 17:50:32.021 * 10 changes in 300 seconds. Saving...
            519:M 21 Apr 2021 17:50:32.023 * Background saving started by pid 20001
            20001:C 21 Apr 2021 17:50:32.149 * DB saved on disk
            20001:C 21 Apr 2021 17:50:32.151 * RDB: 0 MB of memory used by copy-on-write
            519:M 21 Apr 2021 17:50:32.225 * Background saving terminated with success
            

            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

            coyoteC 1 Antwort Letzte Antwort
            0
            • Thomas BraunT Thomas Braun

              @coyote

              Immer wieder

              10000 changes in 60 seconds.
              

              mir scheint da irgendwas aus dem Ruder zu laufen und 10000 ist der Deckel.
              Ich denke aber auch das 10000 Änderungen in 60 Sekunden ungewöhnlich viel ist. Was hast du denn da laufen, was so viele Änderungen auslöst?

              Also bei mir schaut das wesentlich entspannter aus:

              519:M 21 Apr 2021 17:40:30.142 * Background saving terminated with success
              519:M 21 Apr 2021 17:45:31.001 * 10 changes in 300 seconds. Saving...
              519:M 21 Apr 2021 17:45:31.003 * Background saving started by pid 19801
              19801:C 21 Apr 2021 17:45:31.158 * DB saved on disk
              19801:C 21 Apr 2021 17:45:31.161 * RDB: 0 MB of memory used by copy-on-write
              519:M 21 Apr 2021 17:45:31.204 * Background saving terminated with success
              519:M 21 Apr 2021 17:50:32.021 * 10 changes in 300 seconds. Saving...
              519:M 21 Apr 2021 17:50:32.023 * Background saving started by pid 20001
              20001:C 21 Apr 2021 17:50:32.149 * DB saved on disk
              20001:C 21 Apr 2021 17:50:32.151 * RDB: 0 MB of memory used by copy-on-write
              519:M 21 Apr 2021 17:50:32.225 * Background saving terminated with success
              
              coyoteC Offline
              coyoteC Offline
              coyote
              Most Active
              schrieb am zuletzt editiert von coyote
              #10

              @thomas-braun

              ok, gut. Das habe ich auch gesehen, mich eben nur gewundert, dass es tagelang so läuft.
              Das ist in jedem Log so.
              Aber ok, du hast schon recht, dass ist schon viel.
              Gute Frage was das ist, was so viele Änderungen macht. Ne Idee wo ich da nachsehen könnte?

              Du hast aber auch objects und states aud Redis?

              Thomas BraunT 1 Antwort Letzte Antwort
              0
              • coyoteC coyote

                @thomas-braun

                ok, gut. Das habe ich auch gesehen, mich eben nur gewundert, dass es tagelang so läuft.
                Das ist in jedem Log so.
                Aber ok, du hast schon recht, dass ist schon viel.
                Gute Frage was das ist, was so viele Änderungen macht. Ne Idee wo ich da nachsehen könnte?

                Du hast aber auch objects und states aud Redis?

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

                @coyote

                pi@raspberrypi:~ $ iobroker status
                iobroker is running on this host.
                
                Objects type: file
                States  type: redis
                

                Von den Objects wurde mal irgendwann abgeraten die in redis zu packen. Ich weiß aber nicht mehr wo ich das gelesen habe.

                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

                coyoteC 1 Antwort Letzte Antwort
                0
                • Thomas BraunT Thomas Braun

                  @coyote

                  pi@raspberrypi:~ $ iobroker status
                  iobroker is running on this host.
                  
                  Objects type: file
                  States  type: redis
                  

                  Von den Objects wurde mal irgendwann abgeraten die in redis zu packen. Ich weiß aber nicht mehr wo ich das gelesen habe.

                  coyoteC Offline
                  coyoteC Offline
                  coyote
                  Most Active
                  schrieb am zuletzt editiert von
                  #12

                  @thomas-braun ah ok, vllt liegt da das Problem.
                  Ich hatte ganz am Anfang in der Testphase schon komplett umgestellt. Ich schau mal, ob ich das ohne Problem wieder umstellen kann auf nur "states"

                  1 Antwort Letzte Antwort
                  0
                  • coyoteC coyote

                    Hey,

                    sporadisch stürzt bei mir iobroker mal ab. Laut LOG sieht es so aus, als könnte REDIS nicht schreiben. Nach manuellem starten des iobroker hosts läuft alles wieder ohne Probleme.
                    Jemand ne Idee wo ich da suchen könnte?

                    objects/states laufen beide mit REDIS

                    Hier noch das LOG dazu:

                    2021-04-16 18:54:45.897  - info: javascript.0 (14631) script.js.Fenster_offen_mit_Drehgriff: Anzahl Fenster: 25 - davon Fenster auf: 4
                    2021-04-16 18:54:46.336  - info: linux-control.0 (14783) getting data from ZoneminderVM (192.168.66.145:22)
                    2021-04-16 18:54:46.841  - info: linux-control.0 (14783) [getConnection] Host 'RepetierPi' (192.168.66.204:22) seems not to be online
                    2021-04-16 18:54:49.430  - info: linux-control.0 (14783) [getConnection] Host 'ZoneminderVM' (192.168.66.145:22) seems not to be online
                    2021-04-16 18:55:00.056  - info: host.debian instance system.adapter.dwd.0 started with pid 17111
                    2021-04-16 18:55:13.097  - info: linux-control.0 (14783) getting data from ioBrokerVM (192.168.66.68:22)
                    2021-04-16 18:56:27.004  - info: mqtt.0 (15883) Client [MHI_Wintergarten] connection closed: timeout
                    2021-04-16 18:56:27.020  - info: mqtt.0 (15883) Client [MHI_Schlafzimmer] connection closed: timeout
                    2021-04-16 18:56:27.020  - info: mqtt.0 (15883) Client [mqttjs_9e5ebda7] connection closed: timeout
                    2021-04-16 18:56:27.323  - info: mqtt.0 (15883) Client [MHI_Schlafzimmer] connected with secret 1618592187048_4949
                    2021-04-16 18:56:27.314  - info: harmony.0 (28479) [CONNECT] lost Connection to CoyoteHarmonyHub (192.168.66.51)
                    2021-04-16 18:56:27.547  - info: mqtt.0 (15883) Client [MHI_Wintergarten] connected with secret 1618592187232_9902
                    2021-04-16 18:56:27.550  - info: mqtt.0 (15883) Client [MHI_Schlafzimmer] reconnected. Old secret 1618592187048_4949. New secret 1618592187240_3111
                    2021-04-16 18:56:27.556  - info: mqtt.0 (15883) Client [MHI_Wintergarten] reconnected. Old secret 1618592187232_9902. New secret 1618592187241_9511
                    2021-04-16 18:56:27.564  - info: mqtt.0 (15883) Client [wasser] reconnected. Old secret 1618584213554_4427. New secret 1618592187241_9273
                    2021-04-16 18:56:27.576  - info: mqtt.0 (15883) Client [MHI_Schlafzimmer] reconnected. Old secret 1618592187240_3111. New secret 1618592187253_5446
                    2021-04-16 18:56:27.603  - info: mqtt.0 (15883) Client [MHI_Wintergarten] reconnected. Old secret 1618592187241_9511. New secret 1618592187254_7745
                    2021-04-16 18:56:27.695  - info: mqtt.0 (15883) Client [MHI_Schlafzimmer] subscribes on "MHI_Schlafzimmer/set/#" with regex /^MHI_Schlafzimmer\.set\..*/
                    2021-04-16 18:56:27.700  - info: mqtt.0 (15883) Client [MHI_Schlafzimmer] subscribes on "MHI_Schlafzimmer/set/#"  with regex /^mqtt\.0\.MHI_Schlafzimmer\.set\..*/
                    2021-04-16 18:56:27.710  - info: mqtt.0 (15883) Client [MHI_Wintergarten] subscribes on "MHI_Wintergarten/set/#" with regex /^MHI_Wintergarten\.set\..*/
                    2021-04-16 18:56:27.711  - info: mqtt.0 (15883) Client [MHI_Wintergarten] subscribes on "MHI_Wintergarten/set/#"  with regex /^mqtt\.0\.MHI_Wintergarten\.set\..*/
                    2021-04-16 18:56:28.479  - info: sonoff.0 (15298) Client [Sonoff4ch_2] connection closed: closed
                    2021-04-16 18:56:28.958  - info: sonoff.0 (15298) Client [Sonoff4ch_1] reconnected. Old secret 1618588294997_8126. New secret 1618592188219_9040
                    2021-04-16 18:56:28.984  - info: sonoff.0 (15298) Client [Sonoff4ch_2] connected with secret 1618592188266_7142
                    2021-04-16 18:56:28.986  - info: sonoff.0 (15298) Client [Sonoff4ch_1] reconnected. Old secret 1618592188219_9040. New secret 1618592188278_3421
                    2021-04-16 18:56:28.987  - info: sonoff.0 (15298) Client [Sonoff4ch_2] reconnected. Old secret 1618592188266_7142. New secret 1618592188296_5223
                    2021-04-16 18:56:28.990  - info: sonoff.0 (15298) Client [Sonoff_DualR2] reconnected. Old secret 1618584205950_8197. New secret 1618592188383_7159
                    2021-04-16 18:56:29.001  - info: sonoff.0 (15298) Client [Ultraschall] reconnected. Old secret 1618584207538_5573. New secret 1618592188396_16
                    2021-04-16 18:56:29.007  - info: sonoff.0 (15298) Client [Gosund_SP111_2] reconnected. Old secret 1618584203033_6209. New secret 1618592188398_5824
                    2021-04-16 18:56:29.007  - info: sonoff.0 (15298) Client [Sonoff4ch_1] reconnected. Old secret 1618592188278_3421. New secret 1618592188413_5550
                    2021-04-16 18:56:29.008  - info: sonoff.0 (15298) Client [Sonoff4ch_2] reconnected. Old secret 1618592188296_5223. New secret 1618592188424_8847
                    2021-04-16 18:56:29.136  - info: sonoff.0 (15298) Client [Gosund_SP111_2] connection closed: closed
                    2021-04-16 18:56:29.140  - info: sonoff.0 (15298) Client [Ultraschall] connection closed: closed
                    2021-04-16 18:56:29.140  - info: sonoff.0 (15298) Client [Sonoff_DualR2] connection closed: closed
                    2021-04-16 18:56:29.859  - info: sonoff.0 (15298) Client [Sonoff_DualR2] connected with secret 1618592189734_4668
                    2021-04-16 18:56:30.577  - info: iot.0 (14981) Connection changed: disconnect
                    2021-04-16 18:56:30.827  - info: iot.0 (14981) Connection lost
                    2021-04-16 18:56:30.964  - error: unifi.0 (15238) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                    2021-04-16 18:56:30.964  - error: unifi.0 (15238) unhandled promise rejection: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:56:30.985  - error: unifi.0 (15238) ReplyError: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                        at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)
                        at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
                    2021-04-16 18:56:30.986  - error: unifi.0 (15238) MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:56:31.036  - error: unifi.0 (15238) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                    2021-04-16 18:56:31.036  - error: unifi.0 (15238) unhandled promise rejection: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:56:31.036  - error: unifi.0 (15238) ReplyError: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                        at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)
                        at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
                    2021-04-16 18:56:31.037  - error: unifi.0 (15238) MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:56:31.037  - error: unifi.0 (15238) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                    2021-04-16 18:56:31.037  - error: unifi.0 (15238) unhandled promise rejection: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:56:31.038  - error: unifi.0 (15238) ReplyError: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                        at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)
                        at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
                    2021-04-16 18:56:31.038  - error: unifi.0 (15238) MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:56:31.038  - error: unifi.0 (15238) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                    2021-04-16 18:56:31.038  - error: unifi.0 (15238) unhandled promise rejection: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:56:31.038  - error: unifi.0 (15238) ReplyError: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                        at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)
                        at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
                    2021-04-16 18:56:31.039  - error: unifi.0 (15238) MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:56:31.039  - error: unifi.0 (15238) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                    2021-04-16 18:56:31.039  - error: unifi.0 (15238) unhandled promise rejection: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:56:31.040  - error: unifi.0 (15238) ReplyError: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                        at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)
                        at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
                    2021-04-16 18:56:31.040  - error: unifi.0 (15238) MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:56:31.040  - error: unifi.0 (15238) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                    2021-04-16 18:56:31.040  - error: unifi.0 (15238) unhandled promise rejection: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:56:31.041  - error: unifi.0 (15238) ReplyError: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                        at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)
                        at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
                    2021-04-16 18:56:31.041  - error: unifi.0 (15238) MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:56:31.042  - error: unifi.0 (15238) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                    2021-04-16 18:56:31.042  - error: unifi.0 (15238) unhandled promise rejection: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:56:31.042  - error: unifi.0 (15238) ReplyError: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                        at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)
                        at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
                    2021-04-16 18:56:31.043  - error: unifi.0 (15238) MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:56:31.043  - error: unifi.0 (15238) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                    2021-04-16 18:56:31.043  - error: unifi.0 (15238) unhandled promise rejection: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:56:31.043  - error: unifi.0 (15238) ReplyError: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                        at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)
                        at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
                    2021-04-16 18:56:31.044  - error: unifi.0 (15238) MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:56:31.044  - error: unifi.0 (15238) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                    2021-04-16 18:56:31.044  - error: unifi.0 (15238) unhandled promise rejection: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:56:31.045  - error: unifi.0 (15238) ReplyError: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                        at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)
                        at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
                    2021-04-16 18:56:31.045  - error: unifi.0 (15238) MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:56:31.046  - error: unifi.0 (15238) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                    2021-04-16 18:56:31.046  - error: unifi.0 (15238) unhandled promise rejection: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:56:31.046  - error: unifi.0 (15238) ReplyError: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                        at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)
                        at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
                    2021-04-16 18:56:31.046  - error: unifi.0 (15238) MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:56:31.069  - error: unifi.0 (15238) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                    2021-04-16 18:56:31.069  - error: unifi.0 (15238) unhandled promise rejection: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:56:31.071  - error: unifi.0 (15238) ReplyError: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                        at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)
                        at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
                    2021-04-16 18:56:31.071  - error: unifi.0 (15238) MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:56:31.167  - error: mqtt.0 (15883) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                    2021-04-16 18:56:31.609  - error: unifi.0 (15238) [applyJsonLogic] error: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error., stack: ReplyError: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                        at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)
                        at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
                    2021-04-16 18:56:31.796  - error: sonoff.0 (15298) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                    2021-04-16 18:56:30.513  - info: web.0 (18099) ==>Connected system.user.admin from 192.168.66.235
                    2021-04-16 18:56:32.363  - error: unifi.0 (15238) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                    2021-04-16 18:56:32.363  - error: unifi.0 (15238) unhandled promise rejection: Cannot read property 'captureException' of undefined
                    2021-04-16 18:56:32.498  - error: unifi.0 (15238) TypeError: Cannot read property 'captureException' of undefined
                        at Unifi.errorHandling (/opt/iobroker/node_modules/iobroker.unifi/main.js:216:53)
                        at Unifi.applyJsonLogic (/opt/iobroker/node_modules/iobroker.unifi/main.js:1271:18)
                    2021-04-16 18:56:32.504  - error: unifi.0 (15238) Cannot read property 'captureException' of undefined
                    2021-04-16 18:56:32.516  - error: harmony.0 (28479) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                    2021-04-16 18:56:31.801  - error: sonoff.0 (15298) unhandled promise rejection: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:56:31.996  - error: sonoff.0 (15298) ReplyError: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                        at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)
                        at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
                    2021-04-16 18:56:31.997  - error: sonoff.0 (15298) MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:56:32.230  - error: sonoff.0 (15298) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                    2021-04-16 18:56:32.230  - error: sonoff.0 (15298) unhandled promise rejection: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:56:32.231  - error: sonoff.0 (15298) ReplyError: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                        at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)
                        at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
                    2021-04-16 18:56:32.231  - error: sonoff.0 (15298) MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:56:32.245  - error: sonoff.0 (15298) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                    2021-04-16 18:56:32.246  - error: sonoff.0 (15298) unhandled promise rejection: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:56:32.249  - error: sonoff.0 (15298) ReplyError: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                        at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)
                        at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
                    2021-04-16 18:56:32.249  - error: sonoff.0 (15298) MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:56:32.249  - error: sonoff.0 (15298) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                    2021-04-16 18:56:32.249  - error: sonoff.0 (15298) unhandled promise rejection: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:56:32.250  - error: sonoff.0 (15298) ReplyError: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                        at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)
                        at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
                    2021-04-16 18:56:32.250  - error: sonoff.0 (15298) MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:56:32.250  - error: sonoff.0 (15298) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                    2021-04-16 18:56:32.251  - error: sonoff.0 (15298) unhandled promise rejection: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:56:32.251  - error: sonoff.0 (15298) ReplyError: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                        at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)
                        at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
                    2021-04-16 18:56:32.251  - error: sonoff.0 (15298) MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:56:32.251  - error: sonoff.0 (15298) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                    2021-04-16 18:56:32.332  - error: sonoff.0 (15298) unhandled promise rejection: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:56:32.333  - error: sonoff.0 (15298) ReplyError: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                        at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)
                        at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
                    2021-04-16 18:56:32.334  - error: sonoff.0 (15298) MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:56:32.334  - error: sonoff.0 (15298) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                    2021-04-16 18:56:32.335  - error: sonoff.0 (15298) unhandled promise rejection: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:56:32.335  - error: sonoff.0 (15298) ReplyError: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                        at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)
                        at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
                    2021-04-16 18:56:32.335  - error: sonoff.0 (15298) MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:56:32.336  - error: sonoff.0 (15298) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                    ......
                    2021-04-16 18:57:32.600  - error: web.0 (18099) unhandled promise rejection: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:57:32.600  - error: web.0 (18099) ReplyError: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                        at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)
                        at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
                    2021-04-16 18:57:32.601  - error: web.0 (18099) MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:57:32.959  - info: web.0 (18099) <==Disconnect system.user.admin from 192.168.66.235 vis.0
                    2021-04-16 18:57:38.112  - info: host.debian iobroker.js-controller version 3.2.16 js-controller starting
                    2021-04-16 18:57:38.116  - info: host.debian Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
                    2021-04-16 18:57:38.117  - info: host.debian hostname: debian, node: v12.22.1
                    2021-04-16 18:57:38.117  - info: host.debian ip addresses: 192.168.66.68 fe80::6407:9eff:feb9:ec35
                    2021-04-16 18:57:38.304  - info: host.debian connected to Objects and States
                    2021-04-16 18:57:38.374  - error: host.debian uncaught exception: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:57:39.330  - info: host.debian iobroker.js-controller version 3.2.16 js-controller starting
                    2021-04-16 18:57:39.334  - info: host.debian Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
                    2021-04-16 18:57:39.334  - info: host.debian hostname: debian, node: v12.22.1
                    2021-04-16 18:57:39.335  - info: host.debian ip addresses: 192.168.66.68 fe80::6407:9eff:feb9:ec35
                    2021-04-16 18:57:39.417  - info: host.debian connected to Objects and States
                    2021-04-16 18:57:39.458  - error: host.debian uncaught exception: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:57:40.187  - info: host.debian iobroker.js-controller version 3.2.16 js-controller starting
                    2021-04-16 18:57:40.189  - info: host.debian Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
                    2021-04-16 18:57:40.190  - info: host.debian hostname: debian, node: v12.22.1
                    2021-04-16 18:57:40.190  - info: host.debian ip addresses: 192.168.66.68 fe80::6407:9eff:feb9:ec35
                    2021-04-16 18:57:40.283  - info: host.debian connected to Objects and States
                    2021-04-16 18:57:40.326  - error: host.debian uncaught exception: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:57:41.191  - info: host.debian iobroker.js-controller version 3.2.16 js-controller starting
                    2021-04-16 18:57:41.194  - info: host.debian Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
                    2021-04-16 18:57:41.195  - info: host.debian hostname: debian, node: v12.22.1
                    2021-04-16 18:57:41.195  - info: host.debian ip addresses: 192.168.66.68 fe80::6407:9eff:feb9:ec35
                    2021-04-16 18:57:41.272  - info: host.debian connected to Objects and States
                    2021-04-16 18:57:41.314  - error: host.debian uncaught exception: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    2021-04-16 18:57:41.978  - info: host.debian iobroker.js-controller version 3.2.16 js-controller starting
                    2021-04-16 18:57:41.982  - info: host.debian Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
                    2021-04-16 18:57:41.983  - info: host.debian hostname: debian, node: v12.22.1
                    2021-04-16 18:57:41.983  - info: host.debian ip addresses: 192.168.66.68 fe80::6407:9eff:feb9:ec35
                    2021-04-16 18:57:42.078  - info: host.debian connected to Objects and States
                    2021-04-16 18:57:42.123  - error: host.debian uncaught exception: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
                    
                    Neustart:
                    
                    2021-04-16 19:17:46.319  - info: host.debian iobroker.js-controller version 3.2.16 js-controller starting
                    2021-04-16 19:17:46.322  - info: host.debian Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
                    2021-04-16 19:17:46.322  - info: host.debian hostname: debian, node: v12.22.1
                    2021-04-16 19:17:46.322  - info: host.debian ip addresses: 192.168.66.68 fe80::6407:9eff:feb9:ec35
                    2021-04-16 19:17:46.395  - info: host.debian connected to Objects and States
                    2021-04-16 19:17:46.427  - info: host.debian added notifications configuration of host
                    2021-04-16 19:17:47.762  - info: host.debian Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system
                    2021-04-16 19:17:49.737  - info: host.debian 79 instances found
                    2021-04-16 19:17:49.864  - info: host.debian starting 61 instances
                    2021-04-16 19:17:50.335  - info: host.debian instance system.adapter.admin.0 started with pid 17379
                    2021-04-16 19:17:54.505  - info: host.debian instance system.adapter.deconz.0 started with pid 17386
                    2021-04-16 19:17:55.813  - info: admin.0 (17379) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system
                    2021-04-16 19:17:55.820  - info: admin.0 (17379) starting. Version 4.2.1 in /opt/iobroker/node_modules/iobroker.admin, node: v12.22.1, js-controller: 3.2.16
                    2021-04-16 19:17:55.843  - info: admin.0 (17379) requesting all states
                    2021-04-16 19:17:55.844  - info: admin.0 (17379) requesting all objects
                    2021-04-16 19:17:56.574  - info: deconz.0 (17386) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system
                    2021-04-16 19:17:56.581  - info: deconz.0 (17386) starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.deconz, node: v12.22.1, js-controller: 3.2.16
                    2021-04-16 19:17:56.603  - info: deconz.0 (17386) Please wait while adapter is starting
                    2021-04-16 19:17:56.726  - info: deconz.0 (17386) deConz Version: 2.10.2; API version: 1.16.0
                    2021-04-16 19:17:57.843  - info: admin.0 (17379) received all objects
                    2021-04-16 19:17:58.263  - info: host.debian instance scheduled system.adapter.dwd.0 */5 * * * *
                    2021-04-16 19:17:58.284  - info: host.debian instance system.adapter.dwd.0 started with pid 17419
                    2021-04-16 19:17:59.582  - info: dwd.0 (17419) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system
                    2021-04-16 19:17:59.592  - info: dwd.0 (17419) starting. Version 2.7.5 in /opt/iobroker/node_modules/iobroker.dwd, node: v12.22.1, js-controller: 3.2.16
                    2021-04-16 19:18:00.817  - info: dwd.0 (17419) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                    2021-04-16 19:18:02.156  - info: host.debian instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                    2021-04-16 19:18:02.852  - info: admin.0 (17379) http server listening on port 8081
                    
                    crunchipC Abwesend
                    crunchipC Abwesend
                    crunchip
                    Forum Testing Most Active Developer
                    schrieb am zuletzt editiert von
                    #13

                    @coyote glaub eher das zuvor eher ein Netzwerk Problem vorliegt, aufgrund deiner reconnects

                    umgestiegen von Proxmox auf Unraid

                    coyoteC 1 Antwort Letzte Antwort
                    0
                    • crunchipC crunchip

                      @coyote glaub eher das zuvor eher ein Netzwerk Problem vorliegt, aufgrund deiner reconnects

                      coyoteC Offline
                      coyoteC Offline
                      coyote
                      Most Active
                      schrieb am zuletzt editiert von
                      #14

                      @crunchip hm, auch noch ne Idee, aber das sind alles WLAN Geräte.
                      Habe leider noch keinen richtigen Zusammenhang finden können bzw. wann genau das Problem auftritt

                      crunchipC 1 Antwort Letzte Antwort
                      0
                      • coyoteC coyote

                        @crunchip hm, auch noch ne Idee, aber das sind alles WLAN Geräte.
                        Habe leider noch keinen richtigen Zusammenhang finden können bzw. wann genau das Problem auftritt

                        crunchipC Abwesend
                        crunchipC Abwesend
                        crunchip
                        Forum Testing Most Active Developer
                        schrieb am zuletzt editiert von
                        #15

                        @coyote sagte in iobroker stürzt ab, MISCONF Redis is configured to save RDB:

                        alles WLAN Geräte

                        Eben, verbinden sich neu , z.b nem anderen Kanal

                        umgestiegen von Proxmox auf Unraid

                        coyoteC 1 Antwort Letzte Antwort
                        0
                        • crunchipC crunchip

                          @coyote sagte in iobroker stürzt ab, MISCONF Redis is configured to save RDB:

                          alles WLAN Geräte

                          Eben, verbinden sich neu , z.b nem anderen Kanal

                          coyoteC Offline
                          coyoteC Offline
                          coyote
                          Most Active
                          schrieb am zuletzt editiert von
                          #16

                          @crunchip seltsamerweise aber "nur" 10 Geräte von min 20 🤔
                          Blöd irgendwie festzustellen, was genau das ist

                          crunchipC 1 Antwort Letzte Antwort
                          0
                          • coyoteC coyote

                            @crunchip seltsamerweise aber "nur" 10 Geräte von min 20 🤔
                            Blöd irgendwie festzustellen, was genau das ist

                            crunchipC Abwesend
                            crunchipC Abwesend
                            crunchip
                            Forum Testing Most Active Developer
                            schrieb am zuletzt editiert von
                            #17

                            @coyote kann am schlechten wlan signal liegen.
                            Kenn deine Gegebenheiten nicht.

                            umgestiegen von Proxmox auf Unraid

                            coyoteC 1 Antwort Letzte Antwort
                            0
                            • crunchipC crunchip

                              @coyote kann am schlechten wlan signal liegen.
                              Kenn deine Gegebenheiten nicht.

                              coyoteC Offline
                              coyoteC Offline
                              coyote
                              Most Active
                              schrieb am zuletzt editiert von
                              #18

                              @crunchip Naja, deshalb sag ich ja, schwer zu sagen. Habe 4 Unifi APs im Haus und einen Outdoor.
                              Die Geräte sind auch noch mit unterschiedlichen APs verbunden.

                              crunchipC 1 Antwort Letzte Antwort
                              0
                              • coyoteC coyote

                                @crunchip Naja, deshalb sag ich ja, schwer zu sagen. Habe 4 Unifi APs im Haus und einen Outdoor.
                                Die Geräte sind auch noch mit unterschiedlichen APs verbunden.

                                crunchipC Abwesend
                                crunchipC Abwesend
                                crunchip
                                Forum Testing Most Active Developer
                                schrieb am zuletzt editiert von
                                #19

                                @coyote so wie bei mir, allerdings nur 2 AP's innen, 1er aussen.
                                Hatte auch ne zeitlang gekämpft mit den ständigen reconnects, Handy ständig neu verbunden...etc.
                                Mittlerweile läuft es aber ganz gut.

                                umgestiegen von Proxmox auf Unraid

                                1 Antwort Letzte Antwort
                                0

                                Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.

                                Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.

                                Mit deinem Input könnte dieser Beitrag noch besser werden 💗

                                Registrieren Anmelden
                                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

                                501

                                Online

                                32.9k

                                Benutzer

                                83.0k

                                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