Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. Ring Adapter steigt aus beim ziehen von Snapshots.

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    UNSOLVED Ring Adapter steigt aus beim ziehen von Snapshots.

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

      @Stuebi Bei der Abfrage bekomme ioch folgendes Ergebnis:

      root@iobroker:~# ps -ef | grep ring
      iobroker 11391 400 1 14:11 ? 00:00:30 io.ring.0
      root 13413 13409 0 14:49 pts/0 00:00:00 grep ring

      Stuebi 1 Reply Last reply Reply Quote 0
      • Stuebi
        Stuebi @MKMM98 last edited by

        @MKMM98 sagte in Ring Adapter steigt aus beim ziehen von Snapshots.:

        @Stuebi Bei der Abfrage bekomme ioch folgendes Ergebnis:

        root@iobroker:~# ps -ef | grep ring
        iobroker 11391 400 1 14:11 ? 00:00:30 io.ring.0
        root 13413 13409 0 14:49 pts/0 00:00:00 grep ring

        das sieht gut aus! Ich habe da leider auch keine Idee auf Anhieb

        1 Reply Last reply Reply Quote 0
        • M
          MKMM98 last edited by

          @Stuebi Habe schon alles durch komme da nicht weiter.
          Meine erste Vermutung war das der Port evtl schon belegt ist konnte aber nichts finden.
          Soweit funktioniert der Adapter ja, wenn es klingelt bekomme ich im log noch die Meldung:
          2020-10-17 13:30:46.812 - info: ring.0 (17538) Ding Dong for Id 52XXXXX58 (ding, ringing)
          Danach steigt er aus .
          Dann muss ich wohl noch etwas weiter suchen 😥

          Thomas Braun 1 Reply Last reply Reply Quote 0
          • Thomas Braun
            Thomas Braun Most Active @MKMM98 last edited by

            @MKMM98

            root@iobroker

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

              @Thomas-Braun root@iobroker Stimmt etwas damit nicht?
              Bin als root angemeldet.

              Thomas Braun 1 Reply Last reply Reply Quote 0
              • M
                MKMM98 last edited by

                @Stuebi Habe den Ring Adapter gelöscht und neu installiert. Das Binding Problem ist jetzt nicht mehr da.
                Jedoch steigt er immer noch beim Snapshot aus.

                2020-10-19 15:31:28.512 - info: host.iobroker "system.adapter.ring.0" disabled
                2020-10-19 15:31:28.513 - info: host.iobroker stopInstance system.adapter.ring.0 (force=false, process=true)
                2020-10-19 15:31:28.514 - info: host.iobroker stopInstance system.adapter.ring.0 send kill signal
                2020-10-19 15:31:28.517 - info: ring.0 (2213) Got terminate signal TERMINATE_YOURSELF
                2020-10-19 15:31:28.518 - info: ring.0 (2213) Closing Adapter
                2020-10-19 15:31:28.519 - info: ring.0 (2213) terminating
                2020-10-19 15:31:28.521 - info: ring.0 (2213) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                2020-10-19 15:31:29.050 - info: host.iobroker instance system.adapter.ring.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                2020-10-19 15:32:12.018 - info: host.iobroker "system.adapter.ring.0" enabled
                2020-10-19 15:32:12.039 - info: host.iobroker instance system.adapter.ring.0 started with pid 2269
                2020-10-19 15:32:14.980 - info: ring.0 (2269) starting. Version 1.1.3 in /opt/iobroker/node_modules/iobroker.ring, node: v10.19.0, js-controller: 3.1.6
                2020-10-19 15:32:15.014 - info: ring.0 (2269) Starting Adapter ring.0 in version 1.1.3
                2020-10-19 15:32:16.767 - info: ring.0 (2269) Starting Ring Device for Id 52xxxx58
                2020-10-19 15:33:08.828 - info: ring.0 (2269) Ding Dong for Id 52xxxx58 (ding, ringing)
                2020-10-19 15:33:08.898 - info: ring.0 (2269) Starting creating snapshot
                2020-10-19 15:33:08.902 - error: ring.0 (2269) Error: Error setSanpshot()): Error: Could not create Snapshot for 52xxxx58 in getSnapshot(). Error: Motion detection is disabled for Haustür, which prevents snapshots from this camera. This can be caused by Modes settings or by turning off the Record Motion setting.
                2020-10-19 15:33:08.908 - info: ring.0 (2269) Starting creating livestream with recording time 10 sec.
                2020-10-19 15:33:09.067 - error: ring.0 (2269) uncaught exception: spawn ffmpeg ENOENT
                2020-10-19 15:33:09.068 - error: ring.0 (2269) Error: spawn ffmpeg ENOENT
                at Process.ChildProcess._handle.onexit (internal/child_process.js:240:19)
                at onErrorNT (internal/child_process.js:415:16)
                at process._tickCallback (internal/process/next_tick.js:63:19)
                2020-10-19 15:33:09.069 - info: ring.0 (2269) Closing Adapter
                2020-10-19 15:33:09.100 - error: 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().
                2020-10-19 15:33:09.101 - error: ring.0 (2269) unhandled promise rejection: Cannot call write after a stream was destroyed
                2020-10-19 15:33:09.105 - error: ring.0 (2269) Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
                at doWrite (_stream_writable.js:411:19)
                at writeOrBuffer (_stream_writable.js:399:5)
                at Socket.Writable.write (_stream_writable.js:299:11)
                at FfmpegProcess.start (/opt/iobroker/node_modules/iobroker.ring/node_modules/ring-client-api/lib/api/ffmpeg.js:76:23)
                at SipSession. (/opt/iobroker/node_modules/iobroker.ring/node_modules/ring-client-api/lib/api/sip-session.js:125:16)
                at Generator.next ()
                at fulfilled (/opt/iobroker/node_modules/iobroker.ring/node_modules/ring-client-api/lib/api/sip-session.js:5:58)
                at process._tickCallback (internal/process/next_tick.js:68:7)
                2020-10-19 15:33:09.116 - info: ring.0 (2269) terminating
                2020-10-19 15:33:09.118 - info: ring.0 (2269) Terminated (NO_ERROR): Without reason
                2020-10-19 15:33:09.397 - error: host.iobroker Caught by controller[0]: Error: spawn ffmpeg ENOENT
                2020-10-19 15:33:09.398 - error: host.iobroker Caught by controller[0]: at Process.ChildProcess._handle.onexit (internal/child_process.js:240:19)
                2020-10-19 15:33:09.398 - error: host.iobroker Caught by controller[0]: at onErrorNT (internal/child_process.js:415:16)
                2020-10-19 15:33:09.398 - error: host.iobroker Caught by controller[0]: at process._tickCallback (internal/process/next_tick.js:63:19)
                2020-10-19 15:33:09.398 - error: host.iobroker Caught by controller[1]: 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(). The promise rejected with the reason:
                2020-10-19 15:33:09.399 - error: host.iobroker Caught by controller[2]: Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
                2020-10-19 15:33:09.399 - error: host.iobroker Caught by controller[2]: at doWrite (_stream_writable.js:411:19)
                2020-10-19 15:33:09.399 - error: host.iobroker Caught by controller[2]: at writeOrBuffer (_stream_writable.js:399:5)
                2020-10-19 15:33:09.399 - error: host.iobroker Caught by controller[2]: at Socket.Writable.write (_stream_writable.js:299:11)
                2020-10-19 15:33:09.399 - error: host.iobroker Caught by controller[2]: at FfmpegProcess.start (/opt/iobroker/node_modules/iobroker.ring/node_modules/ring-client-api/lib/api/ffmpeg.js:76:23)
                2020-10-19 15:33:09.399 - error: host.iobroker Caught by controller[2]: at SipSession. (/opt/iobroker/node_modules/iobroker.ring/node_modules/ring-client-api/lib/api/sip-session.js:125:16)
                2020-10-19 15:33:09.399 - error: host.iobroker Caught by controller[2]: at Generator.next ()
                2020-10-19 15:33:09.399 - error: host.iobroker Caught by controller[2]: at fulfilled (/opt/iobroker/node_modules/iobroker.ring/node_modules/ring-client-api/lib/api/sip-session.js:5:58)
                2020-10-19 15:33:09.400 - error: host.iobroker Caught by controller[2]: at process._tickCallback (internal/process/next_tick.js:68:7)
                2020-10-19 15:33:09.400 - error: host.iobroker instance system.adapter.ring.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
                2020-10-19 15:33:09.400 - info: host.iobroker Restart adapter system.adapter.ring.0 because enabled
                2020-10-19 15:33:19.336 - debug: openligadb.0 (1456) system.adapter.admin.0: logging true
                2020-10-19 15:33:39.423 - info: host.iobroker instance system.adapter.ring.0 started with pid 2326
                2020-10-19 15:33:42.228 - info: ring.0 (2326) starting. Version 1.1.3 in /opt/iobroker/node_modules/iobroker.ring, node: v10.19.0, js-controller: 3.1.6
                2020-10-19 15:33:42.260 - info: ring.0 (2326) Starting Adapter ring.0 in version 1.1.3
                2020-10-19 15:33:44.056 - info: ring.0 (2326) Starting Ring Device for Id 52xxxx58
                

                Könnte es etwas mit ffmpeg zu tuen haben?
                Vielleicht kann mir ja bei diesem Fehler ein Tip geben.

                Danke
                Gruß
                Karsten

                Stuebi 1 Reply Last reply Reply Quote 0
                • Thomas Braun
                  Thomas Braun Most Active @MKMM98 last edited by Thomas Braun

                  @MKMM98
                  Man meldet sich nicht als root an.
                  (Außer auf Systemen, wo das nicht anders geht, Docker auf Synology z. B.)

                  Und ich würde auf node12 gehen.

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

                    @Thomas-Braun ok danke, dann werde ich das mal ändern.

                    Thomas Braun 1 Reply Last reply Reply Quote 0
                    • Thomas Braun
                      Thomas Braun Most Active @MKMM98 last edited by

                      @MKMM98
                      Wenn du als USER (mit sudo-Rechten) dann wirf noch ein

                      iobroker fix
                      

                      hinterher. Und node12 nicht vergessen...

                      1 Reply Last reply Reply Quote 0
                      • Stuebi
                        Stuebi @MKMM98 last edited by

                        @MKMM98 sagte in Ring Adapter steigt aus beim ziehen von Snapshots.:

                        @Stuebi Habe den Ring Adapter gelöscht und neu installiert. Das Binding Problem ist jetzt nicht mehr da.
                        Jedoch steigt er immer noch beim Snapshot aus.

                        2020-10-19 15:31:28.512 - info: host.iobroker "system.adapter.ring.0" disabled
                        2020-10-19 15:31:28.513 - info: host.iobroker stopInstance system.adapter.ring.0 (force=false, process=true)
                        2020-10-19 15:31:28.514 - info: host.iobroker stopInstance system.adapter.ring.0 send kill signal
                        2020-10-19 15:31:28.517 - info: ring.0 (2213) Got terminate signal TERMINATE_YOURSELF
                        2020-10-19 15:31:28.518 - info: ring.0 (2213) Closing Adapter
                        2020-10-19 15:31:28.519 - info: ring.0 (2213) terminating
                        2020-10-19 15:31:28.521 - info: ring.0 (2213) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                        2020-10-19 15:31:29.050 - info: host.iobroker instance system.adapter.ring.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                        2020-10-19 15:32:12.018 - info: host.iobroker "system.adapter.ring.0" enabled
                        2020-10-19 15:32:12.039 - info: host.iobroker instance system.adapter.ring.0 started with pid 2269
                        2020-10-19 15:32:14.980 - info: ring.0 (2269) starting. Version 1.1.3 in /opt/iobroker/node_modules/iobroker.ring, node: v10.19.0, js-controller: 3.1.6
                        2020-10-19 15:32:15.014 - info: ring.0 (2269) Starting Adapter ring.0 in version 1.1.3
                        2020-10-19 15:32:16.767 - info: ring.0 (2269) Starting Ring Device for Id 52xxxx58
                        2020-10-19 15:33:08.828 - info: ring.0 (2269) Ding Dong for Id 52xxxx58 (ding, ringing)
                        2020-10-19 15:33:08.898 - info: ring.0 (2269) Starting creating snapshot
                        2020-10-19 15:33:08.902 - error: ring.0 (2269) Error: Error setSanpshot()): Error: Could not create Snapshot for 52xxxx58 in getSnapshot(). Error: Motion detection is disabled for Haustür, which prevents snapshots from this camera. This can be caused by Modes settings or by turning off the Record Motion setting.
                        2020-10-19 15:33:08.908 - info: ring.0 (2269) Starting creating livestream with recording time 10 sec.
                        2020-10-19 15:33:09.067 - error: ring.0 (2269) uncaught exception: spawn ffmpeg ENOENT
                        2020-10-19 15:33:09.068 - error: ring.0 (2269) Error: spawn ffmpeg ENOENT
                        at Process.ChildProcess._handle.onexit (internal/child_process.js:240:19)
                        at onErrorNT (internal/child_process.js:415:16)
                        at process._tickCallback (internal/process/next_tick.js:63:19)
                        2020-10-19 15:33:09.069 - info: ring.0 (2269) Closing Adapter
                        2020-10-19 15:33:09.100 - error: 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().
                        2020-10-19 15:33:09.101 - error: ring.0 (2269) unhandled promise rejection: Cannot call write after a stream was destroyed
                        2020-10-19 15:33:09.105 - error: ring.0 (2269) Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
                        at doWrite (_stream_writable.js:411:19)
                        at writeOrBuffer (_stream_writable.js:399:5)
                        at Socket.Writable.write (_stream_writable.js:299:11)
                        at FfmpegProcess.start (/opt/iobroker/node_modules/iobroker.ring/node_modules/ring-client-api/lib/api/ffmpeg.js:76:23)
                        at SipSession. (/opt/iobroker/node_modules/iobroker.ring/node_modules/ring-client-api/lib/api/sip-session.js:125:16)
                        at Generator.next ()
                        at fulfilled (/opt/iobroker/node_modules/iobroker.ring/node_modules/ring-client-api/lib/api/sip-session.js:5:58)
                        at process._tickCallback (internal/process/next_tick.js:68:7)
                        2020-10-19 15:33:09.116 - info: ring.0 (2269) terminating
                        2020-10-19 15:33:09.118 - info: ring.0 (2269) Terminated (NO_ERROR): Without reason
                        2020-10-19 15:33:09.397 - error: host.iobroker Caught by controller[0]: Error: spawn ffmpeg ENOENT
                        2020-10-19 15:33:09.398 - error: host.iobroker Caught by controller[0]: at Process.ChildProcess._handle.onexit (internal/child_process.js:240:19)
                        2020-10-19 15:33:09.398 - error: host.iobroker Caught by controller[0]: at onErrorNT (internal/child_process.js:415:16)
                        2020-10-19 15:33:09.398 - error: host.iobroker Caught by controller[0]: at process._tickCallback (internal/process/next_tick.js:63:19)
                        2020-10-19 15:33:09.398 - error: host.iobroker Caught by controller[1]: 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(). The promise rejected with the reason:
                        2020-10-19 15:33:09.399 - error: host.iobroker Caught by controller[2]: Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
                        2020-10-19 15:33:09.399 - error: host.iobroker Caught by controller[2]: at doWrite (_stream_writable.js:411:19)
                        2020-10-19 15:33:09.399 - error: host.iobroker Caught by controller[2]: at writeOrBuffer (_stream_writable.js:399:5)
                        2020-10-19 15:33:09.399 - error: host.iobroker Caught by controller[2]: at Socket.Writable.write (_stream_writable.js:299:11)
                        2020-10-19 15:33:09.399 - error: host.iobroker Caught by controller[2]: at FfmpegProcess.start (/opt/iobroker/node_modules/iobroker.ring/node_modules/ring-client-api/lib/api/ffmpeg.js:76:23)
                        2020-10-19 15:33:09.399 - error: host.iobroker Caught by controller[2]: at SipSession. (/opt/iobroker/node_modules/iobroker.ring/node_modules/ring-client-api/lib/api/sip-session.js:125:16)
                        2020-10-19 15:33:09.399 - error: host.iobroker Caught by controller[2]: at Generator.next ()
                        2020-10-19 15:33:09.399 - error: host.iobroker Caught by controller[2]: at fulfilled (/opt/iobroker/node_modules/iobroker.ring/node_modules/ring-client-api/lib/api/sip-session.js:5:58)
                        2020-10-19 15:33:09.400 - error: host.iobroker Caught by controller[2]: at process._tickCallback (internal/process/next_tick.js:68:7)
                        2020-10-19 15:33:09.400 - error: host.iobroker instance system.adapter.ring.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
                        2020-10-19 15:33:09.400 - info: host.iobroker Restart adapter system.adapter.ring.0 because enabled
                        2020-10-19 15:33:19.336 - debug: openligadb.0 (1456) system.adapter.admin.0: logging true
                        2020-10-19 15:33:39.423 - info: host.iobroker instance system.adapter.ring.0 started with pid 2326
                        2020-10-19 15:33:42.228 - info: ring.0 (2326) starting. Version 1.1.3 in /opt/iobroker/node_modules/iobroker.ring, node: v10.19.0, js-controller: 3.1.6
                        2020-10-19 15:33:42.260 - info: ring.0 (2326) Starting Adapter ring.0 in version 1.1.3
                        2020-10-19 15:33:44.056 - info: ring.0 (2326) Starting Ring Device for Id 52xxxx58
                        

                        Könnte es etwas mit ffmpeg zu tuen haben?
                        Vielleicht kann mir ja bei diesem Fehler ein Tip geben.

                        Danke
                        Gruß
                        Karsten

                        hast du ffmpeg installiert? das geht mit apt-get install ffmpeg. Die Snapshot Funktionalität ist mega buggy. Bei mir funktioniert das nur sporadisch, die letzten Wochen überhaupt nicht.

                        1 Reply Last reply Reply Quote 0
                        • M
                          MKMM98 last edited by

                          @Stuebi Danke für deine schnelle Hilfe.
                          ffmpeg hat gefehlt, jetzt läuft alles.

                          Danke
                          MKMM

                          1 Reply Last reply Reply Quote 0
                          • J
                            Juri88 last edited by

                            Hallo, ich habe seit 2 Tagen das gleiche Problem.

                            (11204) Error: Error setSanpshot()): Error: Could not create Snapshot for 29750268 in getSnapshot(). Error: Snapshot failed to refresh after 40 attempts

                            Node ist aktuell, ffmpeg ist auch aktuell. Eine Neuinstallation brachte auch keinen Erfolg. Könnte ich nochwas probieren?

                            Stuebi 1 Reply Last reply Reply Quote 0
                            • Stuebi
                              Stuebi @Juri88 last edited by

                              @Juri88 sagte in Ring Adapter steigt aus beim ziehen von Snapshots.:

                              Hallo, ich habe seit 2 Tagen das gleiche Problem.

                              (11204) Error: Error setSanpshot()): Error: Could not create Snapshot for 29750268 in getSnapshot(). Error: Snapshot failed to refresh after 40 attempts

                              Node ist aktuell, ffmpeg ist auch aktuell. Eine Neuinstallation brachte auch keinen Erfolg. Könnte ich nochwas probieren?

                              Leider gibt es dafür keine Lösung. Mal geht's, mal nicht 😞 Da werde ich auch leider nichts dran ändern können.

                              1 Reply Last reply Reply Quote 0
                              • Agria4800
                                Agria4800 @Stuebi last edited by

                                @stuebi : Ist zwar nicht der exakte Titel, aber die Suche hat leider keinen besseren Treffer gefunden:
                                Du hast doch den Ring Adapter entwickelt, oder ?

                                Könntest du im Adapter evtl. den Speicherort von Snapshot und Livestream getrennt angeben ?
                                Aktuell besteht ja nur die Möglichkeit, Bilder und Video´s in einem Ordner abzulegen, was für mich umständlich ist, da ich nur die Video´s sehen möchte und mein Script da ab und zu ein Foto erwischt...

                                Mein Vorschlag:
                                für Foto´s: /opt/iobroker/node_modules/iobroker.ring/snapshot/
                                für Video´s: /opt/iobroker/node_modules/iobroker.ring/livestream/

                                Vielleicht könnte man noch die Anzahl angeben, wieviel gespeichert werden soll.

                                Ansonsten, super Adapter, vielen Dank dafür 👍

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

                                Support us

                                ioBroker
                                Community Adapters
                                Donate

                                421
                                Online

                                31.9k
                                Users

                                80.1k
                                Topics

                                1.3m
                                Posts

                                ring adapter
                                6
                                19
                                1897
                                Loading More Posts
                                • Oldest to Newest
                                • Newest to Oldest
                                • Most Votes
                                Reply
                                • Reply as topic
                                Log in to reply
                                Community
                                Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                The ioBroker Community 2014-2023
                                logo