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

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

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Error/Bug
  4. IoBroker startete nicht nach sudo reboot

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.7k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    2.2k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    16
    1
    3.1k

IoBroker startete nicht nach sudo reboot

Geplant Angeheftet Gesperrt Verschoben Error/Bug
1 Beiträge 1 Kommentatoren 230 Aufrufe
  • Ä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.
  • RummelmugR Offline
    RummelmugR Offline
    Rummelmug
    schrieb am zuletzt editiert von
    #1

    Moin zusammen, ich hab auf meinem raspi einen cronjob laufen, der den Befehl sudo reboot jeden Morgen um 4 Uhr ausführt. Klappt seid Wochen wunderbar.

    Heute morgen lief zwar der raspi aber es war keine ioBroker Instanz am Laufen. Nach einem weiteren reboot läuft nun alles wieder.

    Ich werde allerdings aus dem Log nicht ganz schlau, wo der Grund für den Absturz liegt. Wird hier einer von euch draus schlau?

    ! 2019-01-11 04:00:00.061 - [32minfo[39m: host.ioBroker-RasPi instance system.adapter.ical.0 started with pid 14936
    ! 2019-01-11 04:00:00.114 - [32minfo[39m: host.ioBroker-RasPi instance system.adapter.ical.1 started with pid 14941
    ! 2019-01-11 04:00:01.974 - [32minfo[39m: ical.0 States connected to redis: 127.0.0.1:6379
    ! 2019-01-11 04:00:02.047 - [32minfo[39m: ical.1 States connected to redis: 127.0.0.1:6379
    ! 2019-01-11 04:00:02.204 - [32minfo[39m: ical.0 starting. Version 1.6.6 in /opt/iobroker/node_modules/iobroker.ical, node: v8.14.0
    ! 2019-01-11 04:00:02.299 - [32minfo[39m: ical.1 starting. Version 1.6.6 in /opt/iobroker/node_modules/iobroker.ical, node: v8.14.0
    ! 2019-01-11 04:00:02.839 - [32minfo[39m: ical.1 processing URL: 01 http://…/Abfuhrkalender-Dillenburg-2019.ics
    ! 2019-01-11 04:00:03.212 - [32minfo[39m: ical.0 processing URL: Abfuhrkalender-1Tag http://.../Abfuhrkalender-Dillenburg-2019-1Tag.ics
    ! 2019-01-11 04:00:03.417 - [32minfo[39m: ical.0 processing URL: Abfuhrkalender http://.../Abfuhrkalender-Dillenburg-2019.ics
    ! 2019-01-11 04:00:05.297 - [33mwarn[39m: hs100.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.299 - [33mwarn[39m: hs100.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.300 - [33mwarn[39m: hs100.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.300 - [33mwarn[39m: hs100.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.301 - [33mwarn[39m: hs100.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.301 - [33mwarn[39m: hs100.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.321 - [33mwarn[39m: hm-rpc.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.322 - [33mwarn[39m: hm-rpc.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.323 - [33mwarn[39m: hm-rpc.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.323 - [33mwarn[39m: hm-rpc.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.323 - [33mwarn[39m: hm-rpc.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.324 - [33mwarn[39m: hm-rpc.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.324 - [33mwarn[39m: hm-rpc.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.325 - [33mwarn[39m: hm-rpc.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.357 - [33mwarn[39m: botvac.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.386 - [33mwarn[39m: ping.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.389 - [33mwarn[39m: javascript.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.394 - [33mwarn[39m: javascript.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.396 - [33mwarn[39m: javascript.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.398 - [33mwarn[39m: javascript.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.399 - [33mwarn[39m: javascript.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.388 - [33mwarn[39m: ping.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.389 - [33mwarn[39m: ping.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.390 - [33mwarn[39m: ping.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.391 - [33mwarn[39m: ping.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.392 - [33mwarn[39m: ping.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.393 - [33mwarn[39m: ping.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.393 - [33mwarn[39m: ping.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.364 - [33mwarn[39m: botvac.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.365 - [33mwarn[39m: botvac.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.366 - [33mwarn[39m: botvac.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.367 - [33mwarn[39m: botvac.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.369 - [33mwarn[39m: botvac.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.369 - [33mwarn[39m: botvac.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.370 - [33mwarn[39m: botvac.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.493 - [31merror[39m: sayit.0 uncaught exception: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
    ! 2019-01-11 04:00:05.494 - [31merror[39m: sayit.0 Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
    ! at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)
    ! 2019-01-11 04:00:05.496 - [32minfo[39m: sayit.0 stopping…
    ! 2019-01-11 04:00:05.599 - [31merror[39m: web.0 uncaught exception: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
    ! 2019-01-11 04:00:05.599 - [31merror[39m: web.0 Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
    ! at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)
    ! 2019-01-11 04:00:05.638 - [32minfo[39m: web.0 terminating http server on port 8082
    ! 2019-01-11 04:00:05.639 - [32minfo[39m: web.0 terminated http server on port 8082
    ! 2019-01-11 04:00:05.691 - [33mwarn[39m: scenes.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.692 - [33mwarn[39m: scenes.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.708 - [33mwarn[39m: scenes.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.709 - [33mwarn[39m: scenes.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.709 - [33mwarn[39m: scenes.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.710 - [33mwarn[39m: scenes.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.710 - [33mwarn[39m: scenes.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.711 - [33mwarn[39m: scenes.0 AbortError: Redis connection lost and command aborted. It might have been processed.
    ! 2019-01-11 04:00:05.841 - [31merror[39m: sayit.0 uncaught exception: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
    ! 2019-01-11 04:00:05.841 - [31merror[39m: sayit.0 Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
    ! at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)
    ! 2019-01-11 04:00:05.841 - [32minfo[39m: sayit.0 stopping…
    ! 2019-01-11 04:00:06.020 - [31merror[39m: web.0 uncaught exception: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
    ! 2019-01-11 04:00:06.021 - [31merror[39m: web.0 Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
    ! at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)
    ! 2019-01-11 04:00:06.022 - [32minfo[39m: web.0 terminating http server on port 8082
    ! 2019-01-11 04:00:06.022 - [32minfo[39m: web.0 terminated http server on port 8082
    ! 2019-01-11 04:00:06.425 - [31merror[39m: sayit.0 uncaught exception: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
    ! 2019-01-11 04:00:06.426 - [31merror[39m: sayit.0 Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
    ! at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)
    ! 2019-01-11 04:00:06.426 - [32minfo[39m: sayit.0 stopping…
    ! 2019-01-11 04:00:06.498 - [32minfo[39m: sayit.0 stopping...
    ! 2019-01-11 04:00:06.519 - [31merror[39m: Caught by controller[0]: { Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
    ! 2019-01-11 04:00:06.520 - [31merror[39m: Caught by controller[0]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)
    ! 2019-01-11 04:00:06.520 - [31merror[39m: Caught by controller[0]: errno: 'ECONNREFUSED',
    ! 2019-01-11 04:00:06.520 - [31merror[39m: Caught by controller[0]: code: 'ECONNREFUSED',
    ! 2019-01-11 04:00:06.520 - [31merror[39m: Caught by controller[0]: syscall: 'connect',
    ! 2019-01-11 04:00:06.521 - [31merror[39m: Caught by controller[0]: address: '127.0.0.1',
    ! 2019-01-11 04:00:06.521 - [31merror[39m: Caught by controller[0]: port: 6379 }
    ! 2019-01-11 04:00:06.521 - [31merror[39m: Caught by controller[1]: { Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
    ! 2019-01-11 04:00:06.521 - [31merror[39m: Caught by controller[1]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)
    ! 2019-01-11 04:00:06.521 - [31merror[39m: Caught by controller[1]: errno: 'ECONNREFUSED',
    ! 2019-01-11 04:00:06.521 - [31merror[39m: Caught by controller[1]: code: 'ECONNREFUSED',
    ! 2019-01-11 04:00:06.521 - [31merror[39m: Caught by controller[1]: syscall: 'connect',
    ! 2019-01-11 04:00:06.521 - [31merror[39m: Caught by controller[1]: address: '127.0.0.1',
    ! 2019-01-11 04:00:06.522 - [31merror[39m: Caught by controller[1]: port: 6379 }
    ! 2019-01-11 04:00:06.522 - [31merror[39m: Caught by controller[2]: { Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
    ! 2019-01-11 04:00:06.522 - [31merror[39m: Caught by controller[2]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)
    ! 2019-01-11 04:00:06.522 - [31merror[39m: Caught by controller[2]: errno: 'ECONNREFUSED',
    ! 2019-01-11 04:00:06.522 - [31merror[39m: Caught by controller[2]: code: 'ECONNREFUSED',
    ! 2019-01-11 04:00:06.522 - [31merror[39m: Caught by controller[2]: syscall: 'connect',
    ! 2019-01-11 04:00:06.522 - [31merror[39m: Caught by controller[2]: address: '127.0.0.1',
    ! 2019-01-11 04:00:06.522 - [31merror[39m: Caught by controller[2]: port: 6379 }
    ! 2019-01-11 04:00:06.523 - [31merror[39m: host.ioBroker-RasPi instance system.adapter.sayit.0 terminated with code 0 (OK)
    ! 2019-01-11 04:00:06.523 - [32minfo[39m: host.ioBroker-RasPi Restart adapter system.adapter.sayit.0 because enabled
    ! 2019-01-11 04:00:06.552 - [32minfo[39m: host.ioBroker-RasPi received SIGTERM
    ! 2019-01-11 04:00:06.564 - [32minfo[39m: admin.0 terminating http server on port 8081
    ! 2019-01-11 04:00:06.568 - [32minfo[39m: web.0 terminating http server on port 8082
    ! 2019-01-11 04:00:06.569 - [32minfo[39m: web.0 terminated http server on port 8082
    ! 2019-01-11 04:00:06.599 - [32minfo[39m: amazon-dash.0 cleaned everything up…
    ! 2019-01-11 04:00:06.557 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.admin.0
    ! 2019-01-11 04:00:06.557 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.admin.0 killing pid 806
    ! 2019-01-11 04:00:06.558 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.discovery.0
    ! 2019-01-11 04:00:06.559 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.discovery.0 killing pid 828
    ! 2019-01-11 04:00:06.560 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.web.0
    ! 2019-01-11 04:00:06.561 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.web.0 killing pid 838
    ! 2019-01-11 04:00:06.562 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.javascript.0
    ! 2019-01-11 04:00:06.563 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.javascript.0 killing pid 848
    ! 2019-01-11 04:00:06.564 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.cloud.0
    ! 2019-01-11 04:00:06.565 - [33mwarn[39m: host.ioBroker-RasPi stopInstance system.adapter.cloud.0 not running
    ! 2019-01-11 04:00:06.565 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.botvac.0
    ! 2019-01-11 04:00:06.566 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.botvac.0 killing pid 858
    ! 2019-01-11 04:00:06.566 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.scenes.0
    ! 2019-01-11 04:00:06.566 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.scenes.0 killing pid 868
    ! 2019-01-11 04:00:06.567 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.cloud.1
    ! 2019-01-11 04:00:06.568 - [33mwarn[39m: host.ioBroker-RasPi stopInstance system.adapter.cloud.1 not running
    ! 2019-01-11 04:00:06.568 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.pushsafer.0
    ! 2019-01-11 04:00:06.569 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.pushsafer.0 killing pid 879
    ! 2019-01-11 04:00:06.570 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.ical.0
    ! 2019-01-11 04:00:06.576 - [32minfo[39m: host.ioBroker-RasPi stopInstance canceled schedule system.adapter.ical.0
    ! 2019-01-11 04:00:06.576 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.g-homa.0
    ! 2019-01-11 04:00:06.577 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.g-homa.0 killing pid 904
    ! 2019-01-11 04:00:06.578 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.ical.1
    ! 2019-01-11 04:00:06.578 - [32minfo[39m: host.ioBroker-RasPi stopInstance canceled schedule system.adapter.ical.1
    ! 2019-01-11 04:00:06.579 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.backitup.0
    ! 2019-01-11 04:00:06.579 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.backitup.0 killing pid 924
    ! 2019-01-11 04:00:06.579 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.ping.0
    ! 2019-01-11 04:00:06.580 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.ping.0 killing pid 935
    ! 2019-01-11 04:00:06.580 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.hm-rpc.0
    ! 2019-01-11 04:00:06.581 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.hm-rpc.2
    ! 2019-01-11 04:00:06.582 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.hm-rega.0
    ! 2019-01-11 04:00:06.582 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.hm-rega.0 killing pid 973
    ! 2019-01-11 04:00:06.582 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.weatherunderground.0
    ! 2019-01-11 04:00:06.583 - [32minfo[39m: host.ioBroker-RasPi stopInstance canceled schedule system.adapter.weatherunderground.0
    ! 2019-01-11 04:00:06.584 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.vis.0
    ! 2019-01-11 04:00:06.584 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.vis-bars.0
    ! 2019-01-11 04:00:06.584 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.vis-canvas-gauges.0
    ! 2019-01-11 04:00:06.584 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.vis-colorpicker.0
    ! 2019-01-11 04:00:06.584 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.vis-fancyswitch.0
    ! 2019-01-11 04:00:06.585 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.vis-hqwidgets.0
    ! 2019-01-11 04:00:06.585 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.vis-jqui-mfd.0
    ! 2019-01-11 04:00:06.585 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.vis-justgage.0
    ! 2019-01-11 04:00:06.585 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.vis-keyboard.0
    ! 2019-01-11 04:00:06.585 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.vis-metro.0
    ! 2019-01-11 04:00:06.585 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.vis-timeandweather.0
    ! 2019-01-11 04:00:06.586 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.vis-weather.0
    ! 2019-01-11 04:00:06.586 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.hue.0
    ! 2019-01-11 04:00:06.586 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.hue.0 killing pid 32111
    ! 2019-01-11 04:00:06.587 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.chromecast.0
    ! 2019-01-11 04:00:06.587 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.chromecast.0 killing pid 1082
    ! 2019-01-11 04:00:06.587 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.hs100.0
    ! 2019-01-11 04:00:06.588 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.hs100.0 killing pid 1092
    ! 2019-01-11 04:00:06.590 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.simple-api.0
    ! 2019-01-11 04:00:06.594 - [33mwarn[39m: host.ioBroker-RasPi stopInstance system.adapter.simple-api.0 not running
    ! 2019-01-11 04:00:06.595 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.socketio.0
    ! 2019-01-11 04:00:06.595 - [32minfo[39m: host.ioBroker-RasPi stopInstance system.adapter.socketio.0 killing pid 1102[/spoiler]

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


    Support us

    ioBroker
    Community Adapters
    Donate

    706

    Online

    32.4k

    Benutzer

    81.5k

    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