Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. mihome-vacuum stürtzt ab (terminated due to SIGSEGV)

    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

    mihome-vacuum stürtzt ab (terminated due to SIGSEGV)

    This topic has been deleted. Only users with topic management privileges can see it.
    • Thomas Braun
      Thomas Braun Most Active @dali3 last edited by Thomas Braun

      @dali3 sagte in mihome-vacuum stürtzt ab (terminated due to SIGSEGV):

      Während dem Betrieb auf einem NUC mit Proxmox hatte ich das Problem nicht,
      erst seit es auf dem Raspi 4 läuft.

      Auf meinem Raspberry 4 (8GB) läuft der Adapter einwandfrei. Allerdings habe ich den Sauger der ersten Generation.

      D 1 Reply Last reply Reply Quote 1
      • D
        dali3 @Thomas Braun last edited by

        @thomas-braun

        Oder habe ich die falsche Version installiert bei der Neuinstallation?
        v12.22.8
        6.14.15

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

          @dali3

          Empfohlen wird Stand heute nodeJS14.

          Siehe meine Signatur wenn es um node-Installationen geht.

          D 1 Reply Last reply Reply Quote 1
          • D
            dali3 @Thomas Braun last edited by

            @thomas-braun

            update ist gemacht:

            v14.18.2
            v14.18.2
            6.14.15

            hier das Resultat:

            
            mihome-vacuum.0
            2021-12-27 15:59:34.178	info	create state for carpet_mode
            
            mihome-vacuum.0
            2021-12-27 15:59:30.347	warn	State "mihome-vacuum.0.cleanmap.mapStatus" has no existing object, this might lead to an error in future versions
            
            javascript.0
            2021-12-27 15:59:30.293	info	script.js.Diverses.Robi_Fehlermeldungen: telegram: Iobroker: Robi - Kein Fehler
            
            mihome-vacuum.0
            2021-12-27 15:59:30.277	warn	State "mihome-vacuum.0.cleanmap.actualMap" has no existing object, this might lead to an error in future versions
            
            javascript.0
            2021-12-27 15:59:30.246	info	script.js.Diverses.Robi_Zustandsmeldung: telegram: Iobroker: Robi - Laden
            
            mihome-vacuum.0
            2021-12-27 15:59:30.214	info	create states for water box
            
            mihome-vacuum.0
            2021-12-27 15:59:30.189	info	change states from State control.fan_power
            
            mihome-vacuum.0
            2021-12-27 15:58:56.336	info	settest next timer: not available
            
            mihome-vacuum.0
            2021-12-27 15:58:56.112	info	Map not selected delete states...
            
            mihome-vacuum.0
            2021-12-27 15:58:55.743	info	select standard vacuum protocol....
            
            mihome-vacuum.0
            2021-12-27 15:58:55.710	warn	No Answer for DeviceModel use model from Config
            
            mihome-vacuum.0
            2021-12-27 15:58:32.969	info	IOT enabled, create state
            
            mihome-vacuum.0
            2021-12-27 15:58:32.897	info	starting. Version 3.3.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.18.2, js-controller: 3.3.22
            
            mihome-vacuum.0
            2021-12-27 15:58:32.829	info	Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system
            host.raspberrypi4
            2021-12-27 15:58:30.147	info	instance system.adapter.mihome-vacuum.0 started with pid 5790
            host.raspberrypi4
            2021-12-27 15:58:28.695	info	instance system.adapter.mihome-vacuum.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
            
            mihome-vacuum.0
            2021-12-27 15:58:28.012	info	Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
            
            mihome-vacuum.0
            2021-12-27 15:58:28.004	error	Socket Close
            host.raspberrypi4
            2021-12-27 15:58:28.001	info	stopInstance system.adapter.mihome-vacuum.0 killing pid 5589
            
            mihome-vacuum.0
            2021-12-27 15:58:27.579	info	IOT enabled, create state
            
            mihome-vacuum.0
            2021-12-27 15:58:27.506	info	starting. Version 3.3.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.18.2, js-controller: 3.3.22
            
            mihome-vacuum.0
            2021-12-27 15:58:27.438	info	Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system
            host.raspberrypi4
            2021-12-27 15:58:26.998	info	stopInstance system.adapter.mihome-vacuum.0 send kill signal
            host.raspberrypi4
            2021-12-27 15:58:26.849	info	stopInstance system.adapter.mihome-vacuum.0 (force=false, process=true)
            host.raspberrypi4
            2021-12-27 14:58:12.647	info	instance system.adapter.mihome-vacuum.0 started with pid 55892
            host.raspberrypi4
            2021-12-27 14:57:50.863	info	Restart adapter system.adapter.mihome-vacuum.0 because enabled
            host.raspberrypi4
            2021-12-27 14:57:50.862	info	instance system.adapter.mihome-vacuum.0 terminated with code NaN ()
            host.raspberrypi4
            2021-12-27 14:57:50.861	warn	instance system.adapter.mihome-vacuum.0 terminated due to SIGSEGV
            
            mihome-vacuum.0
            2021-12-27 14:57:50.687	info	starting. Version 3.3.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.18.2, js-controller: 3.3.22
            
            mihome-vacuum.0
            2021-12-27 14:57:50.604	info	Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system
            
            1 Reply Last reply Reply Quote 0
            • Thomas Braun
              Thomas Braun Most Active last edited by Thomas Braun

              @dali3 sagte in mihome-vacuum stürtzt ab (terminated due to SIGSEGV):

              whoami
              who -r
              
              D 1 Reply Last reply Reply Quote 1
              • D
                dali3 @Thomas Braun last edited by

                @thomas-braun sagte in mihome-vacuum stürtzt ab (terminated due to SIGSEGV):

                whoami
                who -r

                pi@raspberrypi4:~ $ whoami
                pi
                pi@raspberrypi4:~ $ who -r
                         run-level 5  2021-12-24 09:42
                pi@raspberrypi4:~ $
                

                Habe gemerkt das der Adapter nur abstürzt wenn ich folgendes aktiviere: "enable Map from xiaomi cloud"

                M 1 Reply Last reply Reply Quote 0
                • M
                  Maxim-777 @dali3 last edited by Maxim-777

                  @dali3
                  Genau das gleiche Problem. Neu auf raspi installiert, immer wieder stürzt ab wenn ich "enable Map from xiaomi cloud" aktiviere.

                  host.SERVER
                  	2022-01-11 21:41:56.787	warn	instance system.adapter.mihome-vacuum.1 terminated due to SIGSEGV
                  host.SERVER
                  	2022-01-11 21:41:51.522	info	instance system.adapter.mihome-vacuum.1 started with pid 31143
                  host.SERVER
                  	2022-01-11 21:41:21.476	info	Restart adapter system.adapter.mihome-vacuum.1 because enabled
                  host.SERVER
                  	2022-01-11 21:41:21.475	info	instance system.adapter.mihome-vacuum.1 terminated with code NaN ()
                  host.SERVER
                  	2022-01-11 21:41:21.474	warn	instance system.adapter.mihome-vacuum.1 terminated due to SIGSEGV
                  

                  mihome-vacuum. v3.3.1

                  Thomas Braun 1 Reply Last reply Reply Quote 0
                  • Thomas Braun
                    Thomas Braun Most Active @Maxim-777 last edited by

                    @maxim-777

                    Hm. Hier nicht:

                    2022-01-11 21:56:33.988  - info: mihome-vacuum.0 (65601) starting. Version 3.3.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v17.3.1, js-controller: 3.3.22
                    2022-01-11 21:56:34.397  - info: mihome-vacuum.0 (65601) IOT enabled, create state
                    2022-01-11 21:56:34.512  - info: mihome-vacuum.0 (65601) select standard vacuum protocol....
                    2022-01-11 21:56:35.042  - info: mihome-vacuum.0 (65601) settest next timer: not available
                    2022-01-11 21:56:35.605  - info: mihome-vacuum.0 (65601) Map selected create states...
                    2022-01-11 21:56:35.776  - info: mihome-vacuum.0 (65601) create state for carpet_mode
                    2022-01-11 21:56:33.988  - info: mihome-vacuum.0 (65601) starting. Version 3.3.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v17.3.1, js-controller: 3.3.22
                    2022-01-11 21:56:34.397  - info: mihome-vacuum.0 (65601) IOT enabled, create state
                    2022-01-11 21:56:34.512  - info: mihome-vacuum.0 (65601) select standard vacuum protocol....
                    2022-01-11 21:56:35.042  - info: mihome-vacuum.0 (65601) settest next timer: not available
                    2022-01-11 21:56:35.605  - info: mihome-vacuum.0 (65601) Map selected create states...
                    2022-01-11 21:56:35.776  - info: mihome-vacuum.0 (65601) create state for carpet_mode
                    
                    M 1 Reply Last reply Reply Quote 0
                    • M
                      Maxim-777 @Thomas Braun last edited by

                      @thomas-braun
                      hier auch nicht: (alte version von Mihome roboter)

                      mihome-vacuum.0 2022-01-11 21:59:58.064	info	create state for carpet_mode
                      mihome-vacuum.0 2022-01-11 21:59:57.552	info	Map selected create states...
                      mihome-vacuum.0 2022-01-11 21:59:57.425	info	settest next timer: not available
                      mihome-vacuum.0 2022-01-11 21:59:56.885	info	select standard vacuum protocol....
                      mihome-vacuum.0 2022-01-11 21:59:56.777	info	IOT enabled, create state
                      mihome-vacuum.0 2022-01-11 21:59:56.666	info	starting. Version 3.3.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.18.2, js-controller: 3.3.22
                      mihome-vacuum.0 2022-01-11 21:59:50.085	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                      mihome-vacuum.0 2022-01-11 21:59:50.083	info	terminating
                      

                      Aber beim neue Modell S7, sobald er die Karte holt, stürzt immer wieder ab.

                      Thomas Braun 1 Reply Last reply Reply Quote 0
                      • Thomas Braun
                        Thomas Braun Most Active @Maxim-777 last edited by

                        @maxim-777

                        Gut, bei mir ist das auch der S1 oder wie die erste Generation sich schimpfte.

                        M 1 Reply Last reply Reply Quote 0
                        • M
                          Maxim-777 @Thomas Braun last edited by

                          @thomas-braun
                          Ich war so froh wo ich es hinbekommen, dass die Karte wieder ladet. Sobald der Roboter beim Laden steht funktioniert alles einwandfrei, Adapter läuft ohne Probleme, aber wenn man der Roboter startet und er holt die Karte, stürzt er ab jede 5. Sekunde. So ein misst. Raspi komplett neu + Iobroker mit SSD-USB

                          RAM-7.71 GB
                          System-Betriebszeit-1 T. 00:05:49
                          Node.js-v14.18.2
                          NPM-6.14.15
                          Datenträgergröße-117.16 GB

                          1 Reply Last reply Reply Quote 0
                          • B
                            Beowolf last edited by

                            Hat sich hier eigentlöich etwas getan?

                            Ich habe auch den Sauger der "ersten" Generation. Vacuum S1.

                            Das gleiche Problem. Karte an - kommt die Meldung.

                            Karte aus ist Ruhe.

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

                            Support us

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

                            887
                            Online

                            31.9k
                            Users

                            80.1k
                            Topics

                            1.3m
                            Posts

                            5
                            16
                            1193
                            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