Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. hm-rpc.0 terminated

    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

    SOLVED hm-rpc.0 terminated

    This topic has been deleted. Only users with topic management privileges can see it.
    • R
      Ragnar-Lodbrok last edited by

      Hi zusammen,
      hatte hier ein riesen Problem mit dem Philips Hue Bridge, nach dem ich ein Update fuhr und den alten js-controll noch drauf hatte.
      Es ging nichts mehr un dich musste den Philips Hue Bridge löschen, dann auf js-controll 2.2.9 upgedatet und den Node auf V10.19.0.
      Den Philips Hue Bridge wieder drauf, Version 3.2.3, und alles läuft wieder bis auf die Meldung im LOG jede Minute:

      instance system.adapter.hm-rpc.0 terminated with code 156 (156)

      Gruß

      foxriver76 1 Reply Last reply Reply Quote 0
      • foxriver76
        foxriver76 Developer @Ragnar-Lodbrok last edited by foxriver76

        @Ragnar-Lodbrok 156 ist der Exit Code für einen geplanten Neustart. Schau mal im Admin Tab 'Instanzen' -> oben sicherstellen, dass Expertenmodus an ist, dann gibt es eine Spalte Zeitplanung bei den Instanzen, evtl ist hier ein minütlicher Restart für hm-rpc.0 eingetragen.

        Ah, .. wenn der Bug den ich gestern gefixt habe, auch in der 2.2.9 war, dann kann es auch sein, dass es gar kein scheduled restart war und irrütmlicherweise der Exit Code genommen wird. Also falls es das oben beschriebene nicht ist, müsste evtl noch mehr im Log stehen.

        1 Reply Last reply Reply Quote 0
        • R
          Ragnar-Lodbrok last edited by

          Ne, daran lag es nicht, es ist kein Restart hinterlegt. Mittlerweile ist es auch nicht mehr minütlich sondern eher spontan. Dann wohl normal, oder ?

          Hier mal das Log, hoffe das hilf Dir.

          hm-rpc.0	2020-03-13 05:59:04.716	info	(13583) Connected
          hm-rpc.0	2020-03-13 05:59:04.476	info	(13583) binrpc -> 133 devices
          hm-rpc.0	2020-03-13 05:59:04.347	info	(13583) binrpc <- listDevices ["hm-rpc.0"]
          hm-rpc.0	2020-03-13 05:59:04.333	info	(13583) binrpc <- system.listMethods ["hm-rpc.0"]
          hm-rpc.0	2020-03-13 05:59:04.304	info	(13583) binrpc client is trying to connect to 192.168.178.38:2001/ with ["xmlrpc_bin://192.168.178.67:2001","hm-rpc.0"]
          hm-rpc.0	2020-03-13 05:59:04.303	info	(13583) binrpc server is trying to listen on 192.168.178.67:2001
          mihome.0	2020-03-13 05:59:03.356	info	(13577) Change connection status: true
          mihome.0	2020-03-13 05:59:03.300	info	(13577) Change connection status: false
          hm-rpc.0	2020-03-13 05:59:03.260	info	(13583) starting. Version 1.12.6 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v10.19.0
          mihome.0	2020-03-13 05:59:03.140	info	(13577) starting. Version 1.2.5 in /opt/iobroker/node_modules/iobroker.mihome, node: v10.19.0
          host.debian-iobrocker	2020-03-13 05:59:01.592	info	instance system.adapter.hm-rpc.0 started with pid 13583
          host.debian-iobrocker	2020-03-13 05:59:01.580	info	instance system.adapter.mihome.0 started with pid 13577
          host.debian-iobrocker	2020-03-13 05:59:00.561	info	Restart adapter system.adapter.hm-rpc.0 because enabled
          host.debian-iobrocker	2020-03-13 05:59:00.561	error	instance system.adapter.hm-rpc.0 terminated with code 156 (156)
          host.debian-iobrocker	2020-03-13 05:59:00.561	info	Restart adapter system.adapter.mihome.0 because enabled
          host.debian-iobrocker	2020-03-13 05:59:00.560	error	instance system.adapter.mihome.0 terminated with code 156 (156)
          hm-rpc.0	2020-03-13 05:59:00.024	info	(13549) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
          hm-rpc.0	2020-03-13 05:59:00.023	info	(13549) terminating
          mihome.0	2020-03-13 05:59:00.020	info	(13543) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
          hm-rpc.0	2020-03-13 05:59:00.020	info	(13549) Disconnected
          mihome.0	2020-03-13 05:59:00.018	info	(13543) terminating
          hm-rpc.0	2020-03-13 05:59:00.014	info	(13549) binrpc -> 192.168.178.38:2001/ init ["xmlrpc_bin://192.168.178.67:2001",""]
          mihome.0	2020-03-13 05:59:00.014	info	(13543) Scheduled restart.
          hm-rpc.0	2020-03-13 05:59:00.012	info	(13549) Scheduled restart.
          hm-rpc.0	2020-03-13 05:58:04.763	info	(13549) Connected
          hm-rpc.0	2020-03-13 05:58:04.526	info	(13549) binrpc -> 133 devices
          hm-rpc.0	2020-03-13 05:58:04.423	info	(13549) binrpc <- listDevices ["hm-rpc.0"]
          hm-rpc.0	2020-03-13 05:58:04.415	info	(13549) binrpc <- system.listMethods ["hm-rpc.0"]
          hm-rpc.0	2020-03-13 05:58:04.371	info	(13549) binrpc client is trying to connect to 192.168.178.38:2001/ with ["xmlrpc_bin://192.168.178.67:2001","hm-rpc.0"]
          hm-rpc.0	2020-03-13 05:58:04.369	info	(13549) binrpc server is trying to listen on 192.168.178.67:2001
          mihome.0	2020-03-13 05:58:03.389	info	(13543) Change connection status: true
          mihome.0	2020-03-13 05:58:03.287	info	(13543) Change connection status: false
          
          
          
          
          hm-rpc.0	2020-03-13 14:01:05.075	info	(17231) Connected
          hm-rpc.0	2020-03-13 14:01:04.839	info	(17231) binrpc -> 133 devices
          hm-rpc.0	2020-03-13 14:01:04.742	info	(17231) binrpc <- listDevices ["hm-rpc.0"]
          hm-rpc.0	2020-03-13 14:01:04.726	info	(17231) binrpc <- system.listMethods ["hm-rpc.0"]
          hm-rpc.0	2020-03-13 14:01:04.701	info	(17231) binrpc client is trying to connect to 192.168.178.38:2001/ with ["xmlrpc_bin://192.168.178.67:2001","hm-rpc.0"]
          hm-rpc.0	2020-03-13 14:01:04.700	info	(17231) binrpc server is trying to listen on 192.168.178.67:2001
          hm-rpc.0	2020-03-13 14:01:03.268	info	(17231) starting. Version 1.12.6 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v10.19.0
          host.debian-iobrocker	2020-03-13 14:01:01.577	info	instance system.adapter.hm-rpc.0 started with pid 17231
          host.debian-iobrocker	2020-03-13 14:01:00.555	info	Restart adapter system.adapter.hm-rpc.0 because enabled
          host.debian-iobrocker	2020-03-13 14:01:00.554	error	instance system.adapter.hm-rpc.0 terminated with code 156 (156)
          hm-rpc.0	2020-03-13 14:01:00.025	info	(17213) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
          hm-rpc.0	2020-03-13 14:01:00.023	info	(17213) terminating
          hm-rpc.0	2020-03-13 14:01:00.021	info	(17213) Disconnected
          hm-rpc.0	2020-03-13 14:01:00.013	info	(17213) binrpc -> 192.168.178.38:2001/ init ["xmlrpc_bin://192.168.178.67:2001",""]
          hm-rpc.0	2020-03-13 14:01:00.011	info	(17213) Scheduled restart.
          hm-rpc.0	2020-03-13 14:00:05.116	info	(17213) Connected
          hm-rpc.0	2020-03-13 14:00:04.877	info	(17213) binrpc -> 133 devices
          hm-rpc.0	2020-03-13 14:00:04.791	info	(17213) binrpc <- listDevices ["hm-rpc.0"]
          hm-rpc.0	2020-03-13 14:00:04.783	info	(17213) binrpc <- system.listMethods ["hm-rpc.0"]
          hm-rpc.0	2020-03-13 14:00:04.751	info	(17213) binrpc client is trying to connect to 192.168.178.38:2001/ with ["xmlrpc_bin://192.168.178.67:2001","hm-rpc.0"]
          hm-rpc.0	2020-03-13 14:00:04.749	info	(17213) binrpc server is trying to listen on 192.168.178.67:2001
          hm-rpc.0	2020-03-13 14:00:03.263	info	(17213) starting. Version 1.12.6 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v10.19.0
          host.debian-iobrocker	2020-03-13 14:00:01.568	info	instance system.adapter.hm-rpc.0 started with pid 17213
          host.debian-iobrocker	2020-03-13 14:00:00.551	info	Restart adapter system.adapter.hm-rpc.0 because enabled
          host.debian-iobrocker	2020-03-13 14:00:00.550	error	instance system.adapter.hm-rpc.0 terminated with code 156 (156)
          
          foxriver76 1 Reply Last reply Reply Quote 0
          • foxriver76
            foxriver76 Developer @Ragnar-Lodbrok last edited by

            @Ragnar-Lodbrok sagte in hm-rpc.0 terminated:

            mihome.0 2020-03-13 05:59:00.014 info (13543) Scheduled restart.
            hm-rpc.0 2020-03-13 05:59:00.012 info (13549) Scheduled restart.

            Sicher, dass da kein Schedule hinterlegt ist? 😉

            1 Reply Last reply Reply Quote 0
            • R
              Ragnar-Lodbrok last edited by

              shit 🙄

              Ist mir echt durch gegangen 🙂

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

              Support us

              ioBroker
              Community Adapters
              Donate

              954
              Online

              31.9k
              Users

              80.1k
              Topics

              1.3m
              Posts

              hm-rpc.0 terminated
              2
              5
              337
              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