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. ioBroker Allgemein
  4. Iobroker stürzt nach Update auf 1.4.2 regelmäßig ab

NEWS

  • Monatsrückblick Januar/Februar 2026 ist online!
    BluefoxB
    Bluefox
    17
    1
    490

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    17
    1
    5.2k

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    13
    1
    1.4k

Iobroker stürzt nach Update auf 1.4.2 regelmäßig ab

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
12 Beiträge 5 Kommentatoren 871 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.
  • F Offline
    F Offline
    fortschritt311
    schrieb am zuletzt editiert von
    #1

    Hallo Zusammen,

    ich hoffe mir kann jemand bei meinem Problem helfen. Vorab die "technischen Daten" :

    Aktuelle Versionsnummern :

    Node : 6.16.0

    NPM : 3.10.10

    iobroker : 1.4.2

    admin : 3.5.10

    hm-rega : 2.0.0

    hm-rpc : 1.8.2 (2 Instanzen rfd & wired)

    javascript : 3.6.4

    owfs : 0.50

    viessmann : 0.84

    simple API : 2.0.0

    socket.io : 2.11

    web server : 2.4.1

    sql : 1.9.2

    • vis, mobile ui, flot

    Ich bin am 01.01.2019 von iobroker 1.2.3 auf 1.4.2 hoch gegangen. Im diesem Zuge wurden sämtliche Adapter mit auf die neuste verfügbare Version (siehe oben) aktualisiert. Nun ist in den vergangenen 12 Tagen iobroker bereits 4x komplett verreckt. Anfangs dachte ich, da ich das sql-logging enorm erweitert hatte, das der Ram voll läuft und die Kiste abschmiert. Nachdem ich das logging für sämtliche Datenpunkte herausgenommen habe und den sql-Adapter deaktiviert habe, blieb das Verhalten aber gleich. iobroker schmiert trotzdem ab.

    Im Anhang das Logfile von heute früh. Um 9:xxUhr habe ich die Kiste neu gestartet. Ansonsten sehe ich da das ab 3:29 Uhr hm-rpc1 einen Ping Error hatte und die Connection verloren hat. Danach versuchen irgendwie die Adapter sich dauern neu zu starten.

    Hier das Logfile. Ich musste das etwas kürzen wegen den max. 10000 Zeichen eines Post.

    2019-01-12 01:54:22.999 - warn: owfs.0 Cannot read value of /mnt/1wire/FF.6C0800000100/gpio.0: Error: ENOENT: no such file or directory, read
    2019-01-12 01:59:48.464 - warn: owfs.0 Cannot read value of /mnt/1wire/FF.6C0800000100/gpio.0: Error: EPERM: operation not permitted, read
    2019-01-12 01:59:48.468 - warn: owfs.0 Cannot read value of /mnt/1wire/FF.6C0800000100/gpio.1: Error: ENOENT: no such file or directory, read
    2019-01-12 03:29:54.303 - error: hm-rpc.1 Ping error: Error: response timeout
    2019-01-12 03:29:54.588 - info: hm-rpc.1 Disconnected
    2019-01-12 03:29:54.840 - error: hm-rpc.1 websocket error
    2019-01-12 03:29:54.993 - error: hm-rpc.1 Error: websocket error
    at WS.Transport.onError (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transport.js:64:13)
    at WebSocket.ws.onerror (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transports/websocket.js:150:10)
    at WebSocket.onError (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/EventTarget.js:109:16)
    at emitOne (events.js:96:13)
    at WebSocket.emit (events.js:188:7)
    at WebSocket.finalize (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/WebSocket.js:182:41)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at onwriteError (_stream_writable.js:345:10)
    at onwrite (_stream_writable.js:363:5)
    2019-01-12 03:29:55.543 - info: hm-rpc.1 Connected
    2019-01-12 03:30:00.121 - warn: hm-rpc.1 Reconnection to DB.
    2019-01-12 03:30:00.250 - warn: hm-rpc.1 Reconnection to DB.
    2019-01-12 03:30:02.215 - info: hm-rpc.1 starting. Version 1.8.2 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v6.16.0
    2019-01-12 03:30:02.741 - info: hm-rpc.1 starting. Version 1.8.2 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v6.16.0
    2019-01-12 03:30:16.331 - info: hm-rpc.1 binrpc server is trying to listen on 192.168.123.150:2002
    2019-01-12 03:30:16.345 - info: hm-rpc.1 binrpc client is trying to connect to 192.168.123.151:2000/ with ["xmlrpc_bin://192.168.123.150:2002","hm-rpc.1"]
    2019-01-12 03:30:16.553 - info: hm-rpc.1 binrpc server is trying to listen on 192.168.123.150:2003
    2019-01-12 03:30:16.562 - info: hm-rpc.1 binrpc client is trying to connect to 192.168.123.151:2000/ with ["xmlrpc_bin://192.168.123.150:2003","hm-rpc.1"]
    2019-01-12 04:43:26.732 - error: hm-rpc.1 Ping error: Error: response timeout
    2019-01-12 04:43:26.749 - info: hm-rpc.1 Disconnected
    2019-01-12 04:43:26.846 - error: hm-rpc.1 websocket error
    2019-01-12 04:43:26.879 - error: hm-rpc.1 Error: websocket error
    at WS.Transport.onError (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transport.js:64:13)
    at WebSocket.ws.onerror (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transports/websocket.js:150:10)
    at WebSocket.onError (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/EventTarget.js:109:16)
    at emitOne (events.js:96:13)
    at WebSocket.emit (events.js:188:7)
    at WebSocket.finalize (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/WebSocket.js:182:41)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at onwriteError (_stream_writable.js:345:10)
    at onwrite (_stream_writable.js:363:5)
    2019-01-12 04:43:27.043 - info: hm-rpc.1 Connected
    2019-01-12 04:43:28.460 - warn: hm-rpc.1 Reconnection to DB.
    2019-01-12 04:43:28.609 - warn: hm-rpc.1 Reconnection to DB.
    2019-01-12 04:43:30.110 - info: hm-rpc.1 starting. Version 1.8.2 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v6.16.0
    2019-01-12 04:43:30.310 - info: hm-rpc.1 starting. Version 1.8.2 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v6.16.0
    2019-01-12 04:43:44.582 - info: hm-rpc.1 binrpc server is trying to listen on 192.168.123.150:2004
    2019-01-12 04:43:44.621 - info: hm-rpc.1 binrpc client is trying to connect to 192.168.123.151:2000/ with ["xmlrpc_bin://192.168.123.150:2004","hm-rpc.1"]
    2019-01-12 04:43:44.746 - info: hm-rpc.1 binrpc <- listDevices ["hm-rpc.1"]
    2019-01-12 04:43:44.793 - info: hm-rpc.1 binrpc server is trying to listen on 192.168.123.150:2005
    2019-01-12 04:43:44.801 - info: hm-rpc.1 binrpc client is trying to connect to 192.168.123.151:2000/ with ["xmlrpc_bin://192.168.123.150:2005","hm-rpc.1"]
    2019-01-12 04:43:45.467 - info: hm-rpc.1 binrpc -> 299 devices
    2019-01-12 04:43:50.810 - error: hm-rpc.1 init error: Error: response timeout
    2019-01-12 04:43:52.114 - info: hm-rpc.1 binrpc <- system.listMethods ["hm-rpc.1"]
    2019-01-12 04:43:52.196 - info: hm-rpc.1 binrpc <- listDevices ["hm-rpc.1"]
    2019-01-12 04:43:52.826 - info: hm-rpc.1 binrpc -> 299 devices
    2019-01-12 04:57:48.858 - warn: viessmann.0 Timeout error connection!
    2019-01-12 04:57:49.526 - info: viessmann.0 Connection with Viessmann system disconnected!
    2019-01-12 04:58:02.443 - warn: viessmann.0 Malfunction connection--> Error: connect EHOSTUNREACH 192.168.123.121:3002
    2019-01-12 04:58:02.468 - warn: viessmann.0 Malfunction connection--> Error: connect EHOSTUNREACH 192.168.123.121:3002
    2019-01-12 04:58:02.481 - info: viessmann.0 Connection with Viessmann system disconnected!
    2019-01-12 04:58:02.491 - info: viessmann.0 Connection with Viessmann system disconnected!
    2019-01-12 05:04:43.982 - warn: javascript.0 Reconnection to DB.
    2019-01-12 05:04:44.313 - warn: javascript.0 Reconnection to DB.
    2019-01-12 05:05:03.811 - warn: viessmann.0 Reconnection to DB.
    2019-01-12 05:05:04.317 - warn: hm-rpc.1 Reconnection to DB.
    2019-01-12 05:05:04.099 - warn: viessmann.0 Reconnection to DB.
    2019-01-12 05:05:04.944 - error: viessmann.0 already running
    2019-01-12 05:05:04.826 - warn: hm-rpc.1 Reconnection to DB.
    2019-01-12 05:05:04.606 - warn: web.0 Reconnection to DB.
    2019-01-12 05:05:04.927 - warn: web.0 Reconnection to DB.
    2019-01-12 05:05:05.400 - error: host.odroid instance system.adapter.viessmann.0 terminated with code 7 (Adapter already running)
    2019-01-12 05:05:05.491 - info: host.odroid Restart adapter system.adapter.viessmann.0 because enabled
    2019-01-12 05:05:06.031 - error: web.0 already running
    2019-01-12 05:05:06.502 - error: host.odroid instance system.adapter.web.0 terminated with code 7 (Adapter already running)
    2019-01-12 05:05:05.879 - warn: admin.0 Reconnection to DB.
    2019-01-12 05:05:06.238 - warn: admin.0 Reconnection to DB.
    2019-01-12 05:05:06.514 - info: host.odroid Restart adapter system.adapter.web.0 because enabled
    2019-01-12 05:05:07.008 - error: admin.0 already running
    2019-01-12 05:05:07.486 - error: host.odroid instance system.adapter.admin.0 terminated with code 7 (Adapter already running)
    2019-01-12 05:05:07.496 - info: host.odroid Restart adapter system.adapter.admin.0 because enabled
    2019-01-12 05:05:36.265 - info: host.odroid instance system.adapter.viessmann.0 started with pid 26807
    2019-01-12 05:05:36.922 - info: host.odroid instance system.adapter.web.0 started with pid 26813
    2019-01-12 05:05:37.674 - info: host.odroid instance system.adapter.admin.0 started with pid 26820
    2019-01-12 05:06:06.829 - error: admin.0 setObject id missing!!
    2019-01-12 05:06:07.064 - info: admin.0 starting. Version 3.5.10 in /opt/iobroker/node_modules/iobroker.admin, node: v6.16.0
    2019-01-12 05:06:07.565 - info: admin.0 requesting all states
    2019-01-12 05:06:07.611 - info: admin.0 requesting all objects
    2019-01-12 05:06:07.640 - info: admin.0 Request actual repository...
    2019-01-12 05:06:16.579 - error: viessmann.0 no connection to objects DB
    2019-01-12 05:06:18.845 - error: web.0 no connection to objects DB
    2019-01-12 05:06:41.720 - warn: hm-rpc.1 Reconnection to DB.
    2019-01-12 05:06:41.802 - warn: hm-rpc.1 Reconnection to DB.
    2019-01-12 05:06:42.049 - warn: admin.0 Reconnection to DB.
    2019-01-12 05:06:42.111 - warn: admin.0 Reconnection to DB.
    2019-01-12 05:06:43.552 - warn: javascript.0 Reconnection to DB.
    2019-01-12 05:06:44.159 - error: javascript.0 already running
    2019-01-12 05:06:42.043 - warn: hm-rega.0 Reconnection to DB.
    2019-01-12 05:06:43.210 - warn: hm-rega.0 Reconnection to DB.
    2019-01-12 05:06:45.084 - error: host.odroid instance system.adapter.javascript.0 terminated with code 7 (Adapter already running)
    2019-01-12 05:06:45.102 - info: host.odroid Restart adapter system.adapter.javascript.0 because enabled
    2019-01-12 05:06:45.420 - error: admin.0 already running
    2019-01-12 05:06:43.176 - warn: hm-rpc.0 Reconnection to DB.
    2019-01-12 05:06:44.680 - warn: hm-rpc.0 Reconnection to DB.
    2019-01-12 05:06:46.162 - error: hm-rpc.1 already running
    2019-01-12 05:06:46.719 - error: host.odroid instance system.adapter.hm-rpc.1 terminated with code 7 (Adapter already running)
    2019-01-12 05:06:46.727 - info: host.odroid Restart adapter system.adapter.hm-rpc.1 because enabled
    2019-01-12 05:06:46.867 - error: host.odroid instance system.adapter.admin.0 terminated with code 7 (Adapter already running)
    2019-01-12 05:06:46.874 - info: host.odroid Restart adapter system.adapter.admin.0 because enabled
    2019-01-12 05:06:47.644 - error: hm-rega.0 already running
    2019-01-12 05:06:48.268 - error: host.odroid instance system.adapter.hm-rega.0 terminated with code 7 (Adapter already running)
    2019-01-12 05:06:48.277 - info: host.odroid Restart adapter system.adapter.hm-rega.0 because enabled
    2019-01-12 05:06:48.662 - info: viessmann.0 starting. Version 0.8.4 in /opt/iobroker/node_modules/iobroker.viessmann, node: v6.16.0
    2019-01-12 05:06:49.437 - info: hm-rpc.0 starting. Version 1.8.2 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v6.16.0
    2019-01-12 05:06:49.869 - info: hm-rpc.0 starting. Version 1.8.2 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v6.16.0
    2019-01-12 05:06:53.800 - warn: viessmann.0 Malfunction connection--> Error: connect EHOSTUNREACH 192.168.123.121:3002
    2019-01-12 05:06:53.830 - info: viessmann.0 Connection with Viessmann system disconnected!
    2019-01-12 05:06:54.993 - error: web.0 setObject id missing!!
    2019-01-12 05:06:55.286 - info: web.0 starting. Version 2.4.1 in /opt/iobroker/node_modules/iobroker.web, node: v6.16.0
    2019-01-12 05:07:02.603 - info: hm-rpc.0 binrpc server is trying to listen on 192.168.123.150:2002
    2019-01-12 05:07:02.619 - info: hm-rpc.0 binrpc client is trying to connect to 192.168.123.151:2001/ with ["xmlrpc_bin://192.168.123.150:2002","hm-rpc.0"]
    2019-01-12 05:07:04.044 - info: hm-rpc.0 binrpc server is trying to listen on 192.168.123.150:2003
    2019-01-12 05:07:04.052 - info: hm-rpc.0 binrpc client is trying to connect to 192.168.123.151:2001/ with ["xmlrpc_bin://192.168.123.150:2003","hm-rpc.0"]
    2019-01-12 05:07:04.174 - info: hm-rpc.0 binrpc <- listDevices ["hm-rpc.0"]
    2019-01-12 05:07:04.909 - info: hm-rpc.0 binrpc -> 147 devices
    2019-01-12 05:07:07.504 - info: web.0 socket.io server listening on port 8082
    2019-01-12 05:07:07.625 - info: web.0 http server listening on port 8082
    2019-01-12 05:07:15.625 - info: host.odroid instance system.adapter.javascript.0 started with pid 26846
    2019-01-12 05:07:17.214 - info: host.odroid instance system.adapter.hm-rpc.1 started with pid 26852
    2019-01-12 05:07:17.691 - info: host.odroid instance system.adapter.admin.0 started with pid 26858
    2019-01-12 05:07:18.466 - info: host.odroid instance system.adapter.hm-rega.0 started with pid 26864
    2019-01-12 05:07:43.257 - info: hm-rega.0 starting. Version 2.0.0 in /opt/iobroker/node_modules/iobroker.hm-rega, node: v6.16.0
    2019-01-12 05:07:43.574 - info: hm-rega.0 subscribe hm-rpc.0.BidCoS-RF.50.PRESS_SHORT
    2019-01-12 05:07:44.868 - info: hm-rega.0 ReGaHSS 192.168.123.151 up
    2019-01-12 05:07:45.438 - info: hm-rega.0 time difference local-ccu 0s
    2019-01-12 05:07:46.016 - info: hm-rega.0 added/updated 0 favorites to enum.favorites
    2019-01-12 05:07:46.813 - info: hm-rega.0 added/updated functions to enum.functions
    2019-01-12 05:07:47.366 - info: hm-rega.0 added/updated rooms to enum.rooms
    2019-01-12 05:07:53.604 - info: hm-rpc.1 starting. Version 1.8.2 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v6.16.0
    2019-01-12 05:07:57.516 - info: hm-rpc.1 binrpc server is trying to listen on 192.168.123.150:2000
    2019-01-12 05:07:57.953 - info: hm-rega.0 got 4 programs
    2019-01-12 05:07:57.582 - info: hm-rpc.1 binrpc client is trying to connect to 192.168.123.151:2000/ with ["xmlrpc_bin://192.168.123.150:2000","hm-rpc.1"]
    2019-01-12 05:07:58.263 - info: hm-rega.0 added/updated 7 programs
    2019-01-12 05:07:58.577 - info: hm-rpc.1 binrpc <- system.listMethods ["hm-rpc.1"]
    2019-01-12 05:07:58.270 - info: hm-rega.0 deleted 0 programs
    2019-01-12 05:07:58.904 - info: hm-rpc.1 binrpc <- listDevices ["hm-rpc.1"]
    2019-01-12 05:07:59.153 - info: hm-rega.0 got 6 variables
    2019-01-12 05:07:59.321 - info: hm-rpc.1 binrpc -> 299 devices
    2019-01-12 05:07:59.480 - info: hm-rega.0 added/updated 6 variables
    2019-01-12 05:07:59.489 - info: hm-rega.0 deleted 0 variables
    2019-01-12 05:07:59.507 - info: hm-rega.0 request state values
    2019-01-12 05:08:03.363 - info: hm-rega.0 got state values
    2019-01-12 05:08:06.309 - error: hm-rpc.1 init error: Error: response timeout
    2019-01-12 05:08:16.713 - warn: hm-rega.0 Reconnection to DB.
    2019-01-12 05:08:16.879 - warn: hm-rega.0 Reconnection to DB.
    2019-01-12 05:08:21.104 - error: admin.0 setObject id missing!!
    2019-01-12 05:08:21.615 - info: admin.0 starting. Version 3.5.10 in /opt/iobroker/node_modules/iobroker.admin, node: v6.16.0
    2019-01-12 05:08:21.988 - info: admin.0 requesting all states
    2019-01-12 05:08:22.056 - info: admin.0 requesting all objects
    2019-01-12 05:08:22.101 - info: admin.0 Request actual repository...
    2019-01-12 05:08:28.075 - info: hm-rpc.1 binrpc <- system.listMethods ["hm-rpc.1"]
    2019-01-12 05:08:28.149 - info: hm-rpc.1 binrpc <- listDevices ["hm-rpc.1"]
    2019-01-12 05:08:32.983 - error: hm-rpc.1 init error: Error: response timeout
    2019-01-12 05:08:45.599 - warn: viessmann.0 Reconnection to DB.
    2019-01-12 05:08:45.813 - info: hm-rpc.1 binrpc -> 299 devices
    2019-01-12 05:08:45.867 - warn: hm-rpc.0 Reconnection to DB.
    2019-01-12 05:08:45.872 - warn: web.0 Reconnection to DB.
    2019-01-12 05:08:45.650 - warn: viessmann.0 Reconnection to DB.
    2019-01-12 05:08:45.919 - warn: hm-rpc.0 Reconnection to DB.
    2019-01-12 05:08:45.922 - warn: web.0 Reconnection to DB.
    2019-01-12 05:08:50.661 - error: javascript.0 no connection to objects DB
    2019-01-12 05:08:50.924 - error: web.0 already running
    2019-01-12 05:08:51.414 - error: viessmann.0 already running
    2019-01-12 05:08:52.373 - error: hm-rpc.0 already running
    2019-01-12 05:08:52.552 - error: host.odroid instance system.adapter.viessmann.0 terminated with code 7 (Adapter already running)
    2019-01-12 05:08:52.568 - info: host.odroid Restart adapter system.adapter.viessmann.0 because enabled
    2019-01-12 05:08:52.683 - error: host.odroid instance system.adapter.web.0 terminated with code 7 (Adapter already running)
    2019-01-12 05:08:52.690 - info: host.odroid Restart adapter system.adapter.web.0 because enabled
    2019-01-12 05:08:52.981 - error: host.odroid instance system.adapter.hm-rpc.0 terminated with code 7 (Adapter already running)
    2019-01-12 05:08:52.991 - info: host.odroid Restart adapter system.adapter.hm-rpc.0 because enabled
    2019-01-12 05:08:54.500 - info: admin.0 received all states
    2019-01-12 05:08:55.986 - info: javascript.0 starting. Version 3.6.4 in /opt/iobroker/node_modules/iobroker.javascript, node: v6.16.0
    2019-01-12 05:08:56.314 - info: javascript.0 requesting all states
    2019-01-12 05:08:56.388 - info: javascript.0 requesting all objects
    2019-01-12 05:08:58.174 - info: hm-rpc.1 binrpc <- system.listMethods ["hm-rpc.1"]
    2019-01-12 05:08:58.325 - info: hm-rpc.1 binrpc <- listDevices ["hm-rpc.1"]
    2019-01-12 05:09:03.035 - error: hm-rpc.1 init error: Error: response timeout
    2019-01-12 05:09:19.002 - warn: hm-rega.0 Reconnection to DB.
    2019-01-12 05:09:19.066 - warn: admin.0 Reconnection to DB.
    2019-01-12 05:09:19.227 - warn: hm-rpc.1 Reconnection to DB.
    2019-01-12 05:09:19.233 - warn: admin.0 Reconnection to DB.
    2019-01-12 05:09:19.053 - warn: hm-rega.0 Reconnection to DB.
    2019-01-12 05:09:19.301 - warn: hm-rpc.1 Reconnection to DB.
    2019-01-12 05:09:23.644 - info: host.odroid instance system.adapter.viessmann.0 started with pid 26948
    2019-01-12 05:09:24.267 - info: host.odroid instance system.adapter.web.0 started with pid 26954
    2019-01-12 05:09:24.877 - info: host.odroid instance system.adapter.hm-rpc.0 started with pid 26960
    2019-01-12 05:09:25.309 - error: hm-rpc.1 already running
    2019-01-12 05:09:25.355 - error: admin.0 already running
    2019-01-12 05:09:25.728 - info: hm-rega.0 starting. Version 2.0.0 in /opt/iobroker/node_modules/iobroker.hm-rega, node: v6.16.0
    2019-01-12 05:09:25.749 - error: host.odroid instance system.adapter.hm-rpc.1 terminated with code 7 (Adapter already running)
    2019-01-12 05:09:25.757 - info: host.odroid Restart adapter system.adapter.hm-rpc.1 because enabled
    2019-01-12 05:09:26.279 - error: host.odroid instance system.adapter.admin.0 terminated with code 7 (Adapter already running)
    2019-01-12 05:09:26.286 - info: host.odroid Restart adapter system.adapter.admin.0 because enabled
    2019-01-12 05:09:26.419 - info: hm-rega.0 starting. Version 2.0.0 in /opt/iobroker/node_modules/iobroker.hm-rega, node: v6.16.0
    2019-01-12 05:09:26.461 - info: hm-rega.0 subscribe hm-rpc.0.BidCoS-RF.50.PRESS_SHORT
    2019-01-12 05:09:26.769 - info: hm-rega.0 subscribe hm-rpc.0.BidCoS-RF.50.PRESS_SHORT
    2019-01-12 05:09:27.376 - info: hm-rega.0 ReGaHSS 192.168.123.151 up
    2019-01-12 05:09:27.410 - info: hm-rega.0 time difference local-ccu NaNs
    2019-01-12 05:09:27.548 - error: hm-rega.0 Cannot parse answer for favorites: undefined
    2019-01-12 05:09:27.578 - info: hm-rega.0 ReGaHSS 192.168.123.151 up
    2019-01-12 05:09:27.807 - info: hm-rega.0 time difference local-ccu 1s
    2019-01-12 05:09:28.755 - info: hm-rega.0 added/updated functions to enum.functions
    2019-01-12 05:09:28.651 - error: javascript.0 already running
    2019-01-12 05:09:29.394 - error: host.odroid instance system.adapter.javascript.0 terminated with code 7 (Adapter already running)
    2019-01-12 05:09:29.401 - info: host.odroid Restart adapter system.adapter.javascript.0 because enabled
    2019-01-12 05:09:30.851 - info: hm-rega.0 added/updated rooms to enum.rooms
    2019-01-12 05:09:36.126 - info: hm-rega.0 got 7 programs
    2019-01-12 05:09:36.218 - info: hm-rega.0 added/updated 7 programs
    2019-01-12 05:09:36.224 - info: hm-rega.0 deleted 0 programs
    2019-01-12 05:09:36.418 - info: hm-rega.0 got 6 variables
    2019-01-12 05:09:36.555 - info: hm-rega.0 added/updated 6 variables
    2019-01-12 05:09:36.560 - info: hm-rega.0 deleted 0 variables
    2019-01-12 05:09:36.565 - info: hm-rega.0 request state values
    2019-01-12 05:09:38.208 - info: hm-rega.0 got state values
    2019-01-12 05:09:56.092 - info: host.odroid instance system.adapter.hm-rpc.1 started with pid 26969
    2019-01-12 05:09:56.806 - info: host.odroid instance system.adapter.admin.0 started with pid 26975
    2019-01-12 05:09:59.699 - info: host.odroid instance system.adapter.javascript.0 started with pid 26981
    2019-01-12 05:10:00.869 - info: hm-rpc.0 starting. Version 1.8.2 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v6.16.0
    2019-01-12 05:10:07.281 - info: hm-rpc.0 binrpc server is trying to listen on 192.168.123.150:2001
    2019-01-12 05:10:07.360 - info: hm-rpc.0 binrpc client is trying to connect to 192.168.123.151:2001/ with ["xmlrpc_bin://192.168.123.150:2001","hm-rpc.0"]
    2019-01-12 05:10:07.217 - info: viessmann.0 starting. Version 0.8.4 in /opt/iobroker/node_modules/iobroker.viessmann, node: v6.16.0
    2019-01-12 05:10:08.560 - info: hm-rpc.0 binrpc <- system.listMethods ["hm-rpc.0"]
    2019-01-12 05:10:08.940 - info: hm-rpc.0 binrpc <- listDevices ["hm-rpc.0"]
    2019-01-12 05:10:09.861 - info: hm-rpc.0 binrpc -> 147 devices
    2019-01-12 05:10:10.696 - error: web.0 setObject id missing!!
    2019-01-12 05:10:11.206 - info: web.0 starting. Version 2.4.1 in /opt/iobroker/node_modules/iobroker.web, node: v6.16.0
    2019-01-12 05:10:13.563 - error: hm-rpc.0 init error: Error: response timeout
    2019-01-12 05:10:15.284 - warn: viessmann.0 Malfunction connection--> Error: connect EHOSTUNREACH 192.168.123.121:3002
    2019-01-12 05:10:15.336 - info: viessmann.0 Connection with Viessmann system disconnected!
    2019-01-12 05:10:15.585 - info: hm-rpc.0 Connected
    2019-01-12 05:10:17.532 - info: hm-rpc.1 starting. Version 1.8.2 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v6.16.0
    2019-01-12 05:10:22.272 - info: hm-rpc.1 binrpc server is trying to listen on 192.168.123.150:2000
    2019-01-12 05:10:22.315 - info: hm-rpc.1 binrpc client is trying to connect to 192.168.123.151:2000/ with ["xmlrpc_bin://192.168.123.150:2000","hm-rpc.1"]
    2019-01-12 05:10:22.819 - info: hm-rpc.1 binrpc <- system.listMethods ["hm-rpc.1"]
    2019-01-12 05:10:22.990 - info: hm-rpc.1 binrpc <- listDevices ["hm-rpc.1"]
    2019-01-12 05:10:23.424 - info: hm-rpc.1 binrpc -> 299 devices
    2019-01-12 05:10:23.556 - info: web.0 socket.io server listening on port 8082
    2019-01-12 05:10:23.703 - info: web.0 http server listening on port 8082
    2019-01-12 05:10:27.617 - error: hm-rpc.1 init error: Error: response timeout
    2019-01-12 05:10:48.311 - info: javascript.0 starting. Version 3.6.4 in /opt/iobroker/node_modules/iobroker.javascript, node: v6.16.0
    2019-01-12 05:10:48.876 - info: javascript.0 requesting all states
    2019-01-12 05:10:48.970 - info: javascript.0 requesting all objects
    2019-01-12 05:10:52.776 - info: hm-rpc.1 binrpc <- system.listMethods ["hm-rpc.1"]
    2019-01-12 05:10:52.941 - info: hm-rpc.1 binrpc <- listDevices ["hm-rpc.1"]
    2019-01-12 05:10:57.623 - error: hm-rpc.1 init error: Error: response timeout
    2019-01-12 05:10:59.956 - error: admin.0 no connection to objects DB
    2019-01-12 05:11:13.773 - warn: web.0 Reconnection to DB.
    2019-01-12 05:11:13.775 - warn: viessmann.0 Reconnection to DB.
    2019-01-12 05:11:13.794 - warn: hm-rega.0 Reconnection to DB.
    2019-01-12 05:11:13.916 - warn: hm-rpc.1 Reconnection to DB.
    2019-01-12 05:11:13.857 - warn: viessmann.0 Reconnection to DB.
    2019-01-12 05:11:13.841 - warn: hm-rega.0 Reconnection to DB.
    2019-01-12 05:11:13.822 - warn: web.0 Reconnection to DB.
    2019-01-12 05:11:14.004 - warn: hm-rpc.1 Reconnection to DB.
    2019-01-12 05:11:16.438 - error: hm-rpc.1 already running
    2019-01-12 05:11:16.577 - error: hm-rega.0 already running
    2019-01-12 05:11:16.847 - error: web.0 already running
    2019-01-12 05:11:16.871 - error: hm-rpc.0 already running
    2019-01-12 05:11:17.074 - error: viessmann.0 already running
    2019-01-12 05:11:17.773 - error: host.odroid instance system.adapter.hm-rega.0 terminated with code 7 (Adapter already running)
    2019-01-12 05:11:17.791 - info: host.odroid Restart adapter system.adapter.hm-rega.0 because enabled
    2019-01-12 05:11:17.949 - error: host.odroid instance system.adapter.viessmann.0 terminated with code 7 (Adapter already running)
    2019-01-12 05:11:17.956 - info: host.odroid Restart adapter system.adapter.viessmann.0 because enabled
    2019-01-12 05:11:18.069 - error: host.odroid instance system.adapter.web.0 terminated with code 7 (Adapter already running)
    2019-01-12 05:11:18.077 - info: host.odroid Restart adapter system.adapter.web.0 because enabled
    2019-01-12 05:11:18.230 - error: host.odroid instance system.adapter.hm-rpc.0 terminated with code 7 (Adapter already running)
    2019-01-12 05:11:18.238 - info: host.odroid Restart adapter system.adapter.hm-rpc.0 because enabled
    2019-01-12 05:11:18.349 - error: host.odroid instance system.adapter.hm-rpc.1 terminated with code 7 (Adapter already running)
    2019-01-12 05:11:18.356 - info: host.odroid Restart adapter system.adapter.hm-rpc.1 because enabled
    2019-01-12 05:11:19.164 - warn: javascript.0 Reconnection to DB.
    2019-01-12 05:11:19.341 - warn: javascript.0 Reconnection to DB.
    2019-01-12 05:11:21.296 - error: admin.0 setObject id missing!!
    2019-01-12 05:11:21.587 - info: admin.0 starting. Version 3.5.10 in /opt/iobroker/node_modules/iobroker.admin, node: v6.16.0
    2019-01-12 05:11:21.970 - info: admin.0 requesting all states
    2019-01-12 05:11:22.049 - info: admin.0 requesting all objects
    2019-01-12 05:11:22.096 - info: admin.0 Request actual repository...
    2019-01-12 05:11:48.858 - info: host.odroid instance system.adapter.hm-rega.0 started with pid 27022
    2019-01-12 05:11:49.425 - info: host.odroid instance system.adapter.viessmann.0 started with pid 27028
    2019-01-12 05:11:49.983 - info: host.odroid instance system.adapter.web.0 started with pid 27034
    2019-01-12 05:11:50.213 - info: host.odroid instance system.adapter.hm-rpc.0 started with pid 27035
    2019-01-12 05:11:50.477 - info: host.odroid instance system.adapter.hm-rpc.1 started with pid 27046
    2019-01-12 05:11:51.926 - info: admin.0 received all states
    2019-01-12 05:11:52.335 - error: javascript.0 already running
    2019-01-12 05:11:53.033 - error: host.odroid instance system.adapter.javascript.0 terminated with code 7 (Adapter already running)
    2019-01-12 05:11:53.045 - info: host.odroid Restart adapter system.adapter.javascript.0 because enabled
    2019-01-12 05:12:09.201 - info: admin.0 received all objects
    2019-01-12 05:12:12.195 - info: admin.0 http server listening on port 8081
    2019-01-12 05:12:12.203 - info: admin.0 Use link "http://localhost:8081" to configure.
    2019-01-12 05:12:12.737 - info: hm-rpc.1 starting. Version 1.8.2 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v6.16.0
    2019-01-12 05:12:16.793 - info: host.odroid Update repository "default" under "http://download.iobroker.net/sources-dist.json"
    2019-01-12 05:12:20.200 - info: hm-rpc.0 starting. Version 1.8.2 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v6.16.0
    2019-01-12 05:12:23.059 - info: hm-rpc.1 binrpc server is trying to listen on 192.168.123.150:2000
    2019-01-12 05:12:23.371 - info: host.odroid instance system.adapter.javascript.0 started with pid 27064
    2019-01-12 05:12:23.115 - info: hm-rpc.1 binrpc client is trying to connect to 192.168.123.151:2000/ with ["xmlrpc_bin://192.168.123.150:2000","hm-rpc.1"]
    2019-01-12 05:12:23.758 - info: hm-rpc.1 binrpc <- system.listMethods ["hm-rpc.1"]
    2019-01-12 05:12:24.006 - info: hm-rpc.1 binrpc <- listDevices ["hm-rpc.1"]
    2019-01-12 05:12:24.164 - info: viessmann.0 starting. Version 0.8.4 in /opt/iobroker/node_modules/iobroker.viessmann, node: v6.16.0
    2019-01-12 05:12:28.476 - error: hm-rpc.1 init error: Error: response timeout
    2019-01-12 05:12:31.087 - warn: host.odroid warning: Cannot read "http://download.iobroker.net/sources-dist.json"
    2019-01-12 05:12:31.201 - info: admin.0 Repository received successfully.
    2019-01-12 05:12:32.605 - info: hm-rpc.1 binrpc -> 299 devices
    2019-01-12 05:12:32.751 - info: hm-rpc.0 binrpc server is trying to listen on 192.168.123.150:2001
    2019-01-12 05:12:32.806 - info: hm-rpc.0 binrpc client is trying to connect to 192.168.123.151:2001/ with ["xmlrpc_bin://192.168.123.150:2001","hm-rpc.0"]
    2019-01-12 05:12:33.399 - info: hm-rpc.0 binrpc <- system.listMethods ["hm-rpc.0"]
    2019-01-12 05:12:33.631 - info: hm-rpc.0 binrpc <- listDevices ["hm-rpc.0"]
    2019-01-12 05:12:33.886 - info: hm-rpc.0 binrpc -> 147 devices
    2019-01-12 05:12:37.786 - info: hm-rpc.0 Connected
    2019-01-12 05:12:37.851 - warn: viessmann.0 Malfunction connection--> Error: connect EHOSTUNREACH 192.168.123.121:3002
    2019-01-12 05:12:37.898 - info: viessmann.0 Connection with Viessmann system disconnected!
    2019-01-12 05:12:38.269 - error: hm-rpc.0 init error: Error: response timeout
    2019-01-12 05:12:39.533 - error: web.0 setObject id missing!!
    2019-01-12 05:12:40.046 - info: web.0 starting. Version 2.4.1 in /opt/iobroker/node_modules/iobroker.web, node: v6.16.0
    2019-01-12 05:12:52.589 - info: web.0 socket.io server listening on port 8082
    2019-01-12 05:12:52.716 - info: web.0 http server listening on port 8082
    2019-01-12 05:12:51.751 - info: hm-rega.0 starting. Version 2.0.0 in /opt/iobroker/node_modules/iobroker.hm-rega, node: v6.16.0
    2019-01-12 05:12:52.155 - info: hm-rega.0 subscribe hm-rpc.0.BidCoS-RF.50.PRESS_SHORT
    2019-01-12 05:12:53.638 - info: hm-rega.0 ReGaHSS 192.168.123.151 up
    2019-01-12 05:12:53.650 - info: hm-rpc.1 binrpc <- system.listMethods ["hm-rpc.1"]
    2019-01-12 05:12:53.824 - info: hm-rpc.1 binrpc <- listDevices ["hm-rpc.1"]
    2019-01-12 05:12:54.163 - info: hm-rega.0 time difference local-ccu 1s
    2019-01-12 05:12:54.690 - info: hm-rega.0 added/updated 0 favorites to enum.favorites
    2019-01-12 05:12:55.159 - info: hm-rpc.1 binrpc -> 299 devices
    2019-01-12 05:12:55.462 - info: hm-rega.0 added/updated functions to enum.functions
    2019-01-12 05:12:56.717 - info: hm-rega.0 added/updated rooms to enum.rooms
    2019-01-12 05:12:58.486 - error: hm-rpc.1 init error: Error: response timeout
    2019-01-12 05:13:11.156 - info: javascript.0 starting. Version 3.6.4 in /opt/iobroker/node_modules/iobroker.javascript, node: v6.16.0
    2019-01-12 05:13:11.716 - info: javascript.0 requesting all states
    2019-01-12 05:13:11.808 - info: javascript.0 requesting all objects
    2019-01-12 05:13:20.076 - warn: hm-rega.0 Reconnection to DB.
    2019-01-12 05:13:20.243 - warn: hm-rega.0 Reconnection to DB.
    2019-01-12 05:13:23.521 - error: hm-rega.0 already running
    2019-01-12 05:13:23.626 - info: hm-rpc.1 binrpc <- system.listMethods ["hm-rpc.1"]
    2019-01-12 05:13:23.718 - info: hm-rpc.1 binrpc <- listDevices ["hm-rpc.1"]
    2019-01-12 05:13:24.735 - error: host.odroid instance system.adapter.hm-rega.0 terminated with code 7 (Adapter already running)
    2019-01-12 05:13:24.753 - info: host.odroid Restart adapter system.adapter.hm-rega.0 because enabled
    2019-01-12 05:13:25.029 - info: hm-rpc.1 binrpc -> 299 devices
    2019-01-12 05:13:25.333 - info: javascript.0 received all states
    2019-01-12 05:13:27.657 - info: hm-rpc.1 Connected
    2019-01-12 05:13:45.088 - info: javascript.0 received all objects
    2019-01-12 05:13:47.530 - warn: javascript.0 Reconnection to DB.
    2019-01-12 05:13:47.858 - warn: javascript.0 Reconnection to DB.
    2019-01-12 05:13:55.265 - info: host.odroid instance system.adapter.hm-rega.0 started with pid 27095
    2019-01-12 05:14:49.609 - info: hm-rega.0 starting. Version 2.0.0 in /opt/iobroker/node_modules/iobroker.hm-rega, node: v6.16.0
    2019-01-12 05:14:50.239 - info: hm-rega.0 subscribe hm-rpc.0.BidCoS-RF.50.PRESS_SHORT
    2019-01-12 05:14:52.082 - info: hm-rega.0 ReGaHSS 192.168.123.151 up
    2019-01-12 05:14:52.663 - info: hm-rega.0 time difference local-ccu 1s
    2019-01-12 05:14:53.103 - info: hm-rega.0 added/updated 0 favorites to enum.favorites
    2019-01-12 05:14:54.766 - info: hm-rega.0 added/updated functions to enum.functions
    2019-01-12 05:14:55.528 - info: hm-rega.0 added/updated rooms to enum.rooms
    2019-01-12 05:15:16.363 - info: hm-rega.0 got 7 programs
    2019-01-12 05:15:16.671 - info: hm-rega.0 added/updated 7 programs
    2019-01-12 05:15:16.677 - info: hm-rega.0 deleted 0 programs
    2019-01-12 05:15:18.075 - info: hm-rega.0 got 6 variables
    2019-01-12 05:15:18.563 - info: hm-rega.0 added/updated 6 variables
    2019-01-12 05:15:18.574 - info: hm-rega.0 deleted 0 variables
    2019-01-12 05:15:18.603 - info: hm-rega.0 request state values
    2019-01-12 05:15:26.120 - info: hm-rega.0 got state values
    2019-01-12 05:15:46.429 - warn: web.0 Reconnection to DB.
    2019-01-12 05:15:46.476 - warn: admin.0 Reconnection to DB.
    2019-01-12 05:15:46.506 - warn: web.0 Reconnection to DB.
    2019-01-12 05:15:46.682 - warn: admin.0 Reconnection to DB.
    2019-01-12 05:15:46.919 - warn: hm-rpc.1 Reconnection to DB.
    2019-01-12 05:15:47.093 - warn: hm-rpc.0 Reconnection to DB.
    2019-01-12 05:15:47.291 - warn: javascript.0 Reconnection to DB.
    2019-01-12 05:15:47.219 - warn: hm-rpc.0 Reconnection to DB.
    2019-01-12 05:15:47.259 - warn: hm-rpc.1 Reconnection to DB.
    2019-01-12 05:15:47.672 - warn: viessmann.0 Reconnection to DB.
    2019-01-12 05:15:47.809 - error: web.0 already running
    2019-01-12 05:15:47.839 - warn: hm-rega.0 Reconnection to DB.
    2019-01-12 05:15:47.920 - warn: viessmann.0 Reconnection to DB.
    2019-01-12 05:15:47.957 - warn: hm-rega.0 Reconnection to DB.
    2019-01-12 05:15:48.059 - warn: javascript.0 Reconnection to DB.
    2019-01-12 05:15:48.297 - error: host.odroid instance system.adapter.web.0 terminated with code 7 (Adapter already running)
    2019-01-12 05:15:48.314 - info: host.odroid Restart adapter system.adapter.web.0 because enabled
    2019-01-12 05:15:48.721 - error: javascript.0 already running
    2019-01-12 05:15:49.026 - error: host.odroid instance system.adapter.javascript.0 terminated with code 7 (Adapter already running)
    2019-01-12 05:15:49.035 - info: host.odroid Restart adapter system.adapter.javascript.0 because enabled
    2019-01-12 05:16:18.765 - info: host.odroid instance system.adapter.web.0 started with pid 27114
    2019-01-12 05:16:19.450 - info: host.odroid instance system.adapter.javascript.0 started with pid 27120
    2019-01-12 05:16:59.394 - error: web.0 setObject id missing!!
    2019-01-12 05:16:59.897 - info: web.0 starting. Version 2.4.1 in /opt/iobroker/node_modules/iobroker.web, node: v6.16.0
    2019-01-12 05:17:12.379 - info: web.0 socket.io server listening on port 8082
    2019-01-12 05:17:12.501 - info: web.0 http server listening on port 8082
    2019-01-12 05:17:53.927 - info: javascript.0 starting. Version 3.6.4 in /opt/iobroker/node_modules/iobroker.javascript, node: v6.16.0
    2019-01-12 05:17:54.474 - info: javascript.0 requesting all states
    2019-01-12 05:17:54.564 - info: javascript.0 requesting all objects
    2019-01-12 05:18:17.537 - error: admin.0 already running
    2019-01-12 05:18:17.906 - error: hm-rpc.1 already running
    2019-01-12 05:18:18.119 - error: host.odroid instance system.adapter.admin.0 terminated with code 7 (Adapter already running)
    2019-01-12 05:18:18.138 - info: host.odroid Restart adapter system.adapter.admin.0 because enabled
    2019-01-12 05:18:18.592 - error: host.odroid instance system.adapter.hm-rpc.1 terminated with code 7 (Adapter already running)
    2019-01-12 05:18:18.598 - info: host.odroid Restart adapter system.adapter.hm-rpc.1 because enabled
    2019-01-12 05:18:19.093 - info: javascript.0 received all states
    2019-01-12 05:18:34.951 - info: javascript.0 received all objects
    2019-01-12 05:18:37.026 - info: javascript.0 Start javascript script.js.uhc2.uhc2_bw
    2019-01-12 05:18:38.276 - info: javascript.0 script.js.uhc2.uhc2_bw: registered 0 subscriptions and 1 schedule
    2019-01-12 05:18:38.313 - info: javascript.0 Start javascript script.js.uhc2.uhc2_hk_bms
    2019-01-12 05:18:38.644 - info: javascript.0 script.js.uhc2.uhc2_hk_bms: registered 0 subscriptions and 1 schedule
    2019-01-12 05:18:38.672 - info: javascript.0 Start javascript script.js.uhc2.uhc2_hk
    2019-01-12 05:18:38.815 - info: javascript.0 script.js.uhc2.uhc2_hk: registered 0 subscriptions and 1 schedule
    2019-01-12 05:18:38.836 - info: javascript.0 Start javascript script.js.uhc2.uhc2_vs
    2019-01-12 05:18:39.156 - info: javascript.0 script.js.uhc2.uhc2_vs: registered 0 subscriptions and 1 schedule
    2019-01-12 05:18:39.181 - info: javascript.0 Start javascript script.js.uhc2.uhc2_zp
    2019-01-12 05:18:39.328 - info: javascript.0 script.js.uhc2.uhc2_zp: registered 0 subscriptions and 1 schedule
    2019-01-12 05:18:39.355 - info: javascript.0 Start javascript script.js.uhc2.uhc2_lp
    2019-01-12 05:18:39.503 - info: javascript.0 script.js.uhc2.uhc2_lp: registered 0 subscriptions and 1 schedule
    2019-01-12 05:18:39.523 - info: javascript.0 Start javascript script.js.uhc2.uhc2_oel
    2019-01-12 05:18:39.668 - info: javascript.0 script.js.uhc2.uhc2_oel: registered 0 subscriptions and 1 schedule
    2019-01-12 05:18:39.731 - info: javascript.0 Start javascript script.js.uhc2.uhc2_fbh_kueche
    2019-01-12 05:18:39.978 - info: javascript.0 script.js.uhc2.uhc2_fbh_kueche: registered 2 subscriptions and 0 schedules
    2019-01-12 05:18:39.998 - info: javascript.0 Start javascript script.js.uhc2.uhc2_fbh_bad
    2019-01-12 05:18:40.116 - info: javascript.0 script.js.uhc2.uhc2_fbh_bad: registered 2 subscriptions and 0 schedules
    2019-01-12 05:18:40.137 - info: javascript.0 Start javascript script.js.uhc2.uhc2_fbh_flur
    2019-01-12 05:18:40.248 - info: javascript.0 script.js.uhc2.uhc2_fbh_flur: registered 2 subscriptions and 0 schedules
    2019-01-12 05:18:40.271 - info: javascript.0 Start javascript script.js.owfs.owfs_lcd_holzvergaser
    2019-01-12 05:18:40.742 - info: javascript.0 script.js.owfs.owfs_lcd_holzvergaser: registered 3 subscriptions and 0 schedules
    2019-01-12 05:18:48.618 - info: host.odroid instance system.adapter.admin.0 started with pid 27158
    2019-01-12 05:18:49.038 - info: host.odroid instance system.adapter.hm-rpc.1 started with pid 27164
    2019-01-12 05:19:23.188 - info: hm-rpc.1 starting. Version 1.8.2 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v6.16.0
    2019-01-12 05:19:29.728 - info: hm-rpc.1 binrpc server is trying to listen on 192.168.123.150:2000
    2019-01-12 05:19:29.792 - info: hm-rpc.1 binrpc client is trying to connect to 192.168.123.151:2000/ with ["xmlrpc_bin://192.168.123.150:2000","hm-rpc.1"]
    2019-01-12 05:19:30.768 - info: hm-rpc.1 binrpc <- system.listMethods ["hm-rpc.1"]
    2019-01-12 05:19:31.077 - info: hm-rpc.1 binrpc <- listDevices ["hm-rpc.1"]
    2019-01-12 05:19:31.752 - info: hm-rpc.1 binrpc -> 299 devices
    2019-01-12 05:19:38.406 - error: hm-rpc.1 init error: Error: response timeout
    2019-01-12 05:19:52.604 - error: admin.0 setObject id missing!!
    2019-01-12 05:19:53.133 - info: admin.0 starting. Version 3.5.10 in /opt/iobroker/node_modules/iobroker.admin, node: v6.16.0
    2019-01-12 05:19:53.478 - info: admin.0 requesting all states
    2019-01-12 05:19:53.547 - info: admin.0 requesting all objects
    2019-01-12 05:19:53.591 - info: admin.0 Request actual repository...
    2019-01-12 05:20:00.375 - info: hm-rpc.1 binrpc <- system.listMethods ["hm-rpc.1"]
    2019-01-12 05:20:00.553 - info: hm-rpc.1 binrpc <- listDevices ["hm-rpc.1"]
    2019-01-12 05:20:05.213 - error: hm-rpc.1 init error: Error: response timeout
    2019-01-12 05:20:10.110 - warn: viessmann.0 Reconnection to DB.
    2019-01-12 05:20:10.114 - warn: hm-rega.0 Reconnection to DB.
    2019-01-12 05:20:10.141 - warn: hm-rpc.0 Reconnection to DB.
    2019-01-12 05:20:10.173 - warn: viessmann.0 Reconnection to DB.
    2019-01-12 05:20:10.291 - warn: web.0 Reconnection to DB.
    2019-01-12 05:20:10.206 - warn: hm-rpc.0 Reconnection to DB.
    2019-01-12 05:20:10.402 - info: hm-rpc.1 binrpc -> 299 devices
    2019-01-12 05:20:10.511 - warn: web.0 Reconnection to DB.
    2019-01-12 05:20:10.254 - warn: hm-rega.0 Reconnection to DB.
    2019-01-12 05:20:15.558 - error: javascript.0 already running
    2019-01-12 05:20:16.503 - error: host.odroid instance system.adapter.javascript.0 terminated with code 7 (Adapter already running)
    2019-01-12 05:20:16.521 - info: host.odroid Restart adapter system.adapter.javascript.0 because enabled
    2019-01-12 05:20:16.828 - error: hm-rega.0 already running
    2019-01-12 05:20:17.336 - error: web.0 already running
    2019-01-12 05:20:17.394 - error: hm-rpc.0 already running
    2019-01-12 05:20:17.837 - error: host.odroid instance system.adapter.hm-rpc.0 terminated with code 7 (Adapter already running)
    2019-01-12 05:20:17.846 - info: host.odroid Restart adapter system.adapter.hm-rpc.0 because enabled
    2019-01-12 05:20:17.959 - error: host.odroid instance system.adapter.hm-rega.0 terminated with code 7 (Adapter already running)
    2019-01-12 05:20:17.965 - info: host.odroid Restart adapter system.adapter.hm-rega.0 because enabled
    2019-01-12 05:20:18.076 - error: host.odroid instance system.adapter.web.0 terminated with code 7 (Adapter already running)
    2019-01-12 05:20:18.082 - info: host.odroid Restart adapter system.adapter.web.0 because enabled
    2019-01-12 05:20:18.567 - info: viessmann.0 starting. Version 0.8.4 in /opt/iobroker/node_modules/iobroker.viessmann, node: v6.16.0
    2019-01-12 05:20:19.311 - info: viessmann.0 starting. Version 0.8.4 in /opt/iobroker/node_modules/iobroker.viessmann, node: v6.16.0
    2019-01-12 05:20:19.467 - warn: viessmann.0 Malfunction connection--> Error: connect EALREADY 192.168.123.121:3002 - Local (192.168.123.150:54342)
    2019-01-12 05:20:19.481 - warn: viessmann.0 Malfunction connection--> Error: connect EALREADY 192.168.123.121:3002 - Local (192.168.123.150:54342)
    2019-01-12 05:20:19.491 - warn: viessmann.0 Malfunction connection--> Error: connect EALREADY 192.168.123.121:3002 - Local (192.168.123.150:54342)
    2019-01-12 05:20:19.519 - info: viessmann.0 Connection with Viessmann system disconnected!
    2019-01-12 05:20:19.530 - info: viessmann.0 Connection with Viessmann system disconnected!
    2019-01-12 05:20:19.540 - info: viessmann.0 Connection with Viessmann system disconnected!
    2019-01-12 05:20:20.254 - info: admin.0 received all states
    2019-01-12 05:20:20.409 - warn: admin.0 Reconnection to DB.
    2019-01-12 05:20:20.553 - warn: admin.0 Reconnection to DB.
    2019-01-12 05:20:30.443 - info: hm-rpc.1 binrpc <- system.listMethods ["hm-rpc.1"]
    2019-01-12 05:20:30.590 - info: hm-rpc.1 binrpc <- listDevices ["hm-rpc.1"]
    2019-01-12 05:20:31.292 - info: hm-rpc.1 binrpc -> 299 devices
    2019-01-12 05:20:35.881 - error: hm-rpc.1 init error: Error: response timeout
    2019-01-12 05:20:47.184 - info: host.odroid instance system.adapter.javascript.0 started with pid 27212
    2019-01-12 05:20:48.258 - info: host.odroid instance system.adapter.hm-rpc.0 started with pid 27218
    2019-01-12 05:20:48.670 - info: host.odroid instance system.adapter.hm-rega.0 started with pid 27224
    2019-01-12 05:20:48.843 - info: host.odroid instance system.adapter.web.0 started with pid 27225
    2019-01-12 05:21:00.442 - info: hm-rpc.1 binrpc <- system.listMethods ["hm-rpc.1"]
    2019-01-12 05:21:00.507 - info: hm-rpc.1 binrpc <- listDevices ["hm-rpc.1"]
    2019-01-12 05:21:00.748 - info: hm-rpc.1 binrpc -> 299 devices
    2019-01-12 05:21:05.070 - info: hm-rpc.1 Connected
    2019-01-12 05:21:10.751 - error: web.0 setObject id missing!!
    2019-01-12 05:21:11.090 - info: web.0 starting. Version 2.4.1 in /opt/iobroker/node_modules/iobroker.web, node: v6.16.0
    2019-01-12 05:21:22.687 - info: web.0 socket.io server listening on port 8082
    2019-01-12 05:21:22.818 - info: web.0 http server listening on port 8082
    2019-01-12 05:21:23.346 - info: hm-rpc.0 starting. Version 1.8.2 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v6.16.0
    2019-01-12 05:21:29.586 - info: hm-rega.0 starting. Version 2.0.0 in /opt/iobroker/node_modules/iobroker.hm-rega, node: v6.16.0
    2019-01-12 05:21:29.978 - info: hm-rega.0 subscribe hm-rpc.0.BidCoS-RF.50.PRESS_SHORT
    2019-01-12 05:21:30.946 - info: hm-rega.0 ReGaHSS 192.168.123.151 up
    2019-01-12 05:21:31.383 - info: hm-rega.0 time difference local-ccu 0s
    2019-01-12 05:21:31.736 - info: hm-rega.0 added/updated 0 favorites to enum.favorites
    2019-01-12 05:21:31.915 - info: hm-rpc.0 binrpc server is trying to listen on 192.168.123.150:2001
    2019-01-12 05:21:32.255 - info: hm-rega.0 added/updated functions to enum.functions
    2019-01-12 05:21:31.981 - info: hm-rpc.0 binrpc client is trying to connect to 192.168.123.151:2001/ with ["xmlrpc_bin://192.168.123.150:2001","hm-rpc.0"]
    2019-01-12 05:21:32.811 - info: hm-rega.0 added/updated rooms to enum.rooms
    2019-01-12 05:21:33.025 - info: hm-rpc.0 binrpc <- system.listMethods ["hm-rpc.0"]
    2019-01-12 05:21:33.353 - info: hm-rpc.0 binrpc <- listDevices ["hm-rpc.0"]
    2019-01-12 05:21:34.215 - info: hm-rpc.0 binrpc -> 147 devices
    2019-01-12 05:21:37.927 - error: hm-rpc.0 init error: Error: response timeout
    
    

    Vorher lief alles sehr stabil. Zur Not muss ich wieder zurück auf 1.2.3. Aber leider weiß ich die Adapter-Versionen der alten Installation nicht mehr :cry:

    Wenn mehr Informationen benötigt werden, sagt Bescheid.

    Danke & Gruß Maik

    1 Antwort Letzte Antwort
    0
    • wendy2702W Online
      wendy2702W Online
      wendy2702
      schrieb am zuletzt editiert von
      #2

      Was für ein System?

      Wie angebunden LAN/WLAN?

      Hast du auch Node/NPM mit upgegraded?

      Bitte keine Fragen per PN, die gehören ins Forum!

      Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

      1 Antwort Letzte Antwort
      0
      • F Offline
        F Offline
        fortschritt311
        schrieb am zuletzt editiert von
        #3

        Hi.

        Hardware : odroid XU4

        System : Ubuntu 16.04.5 LTS

        Angebunden per LAN.

        Nein NPM und Node sind noch von "damals" von der 1.2.3 Installation.

        1 Antwort Letzte Antwort
        0
        • eric2905E Offline
          eric2905E Offline
          eric2905
          schrieb am zuletzt editiert von
          #4

          Npm 3 ist etwas alt …

          Geh mal auf Node 8 und npm 6.

          Gruß,

          Eric

          Roses are red, violets are blue,

          if I listen to metal, my neighbours do too

          1 Antwort Letzte Antwort
          0
          • wendy2702W Online
            wendy2702W Online
            wendy2702
            schrieb am zuletzt editiert von
            #5

            Diese NPM/Node Versionen laufen bei mir noch Problemlos. Was aber nicht heißt das es in Verbindung mit dem ein oder anderen Adapter der aktualisiert wurde Probleme gibt.

            Was nutzt der Odroid als Speichermedium?

            Hast du mal in das Syslog geschaut zu den Zeiten an denen es Probleme gibt?

            Bitte keine Fragen per PN, die gehören ins Forum!

            Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

            1 Antwort Letzte Antwort
            0
            • F Offline
              F Offline
              fortschritt311
              schrieb am zuletzt editiert von
              #6

              Als Speichermedium nutze ich ein eMMC.Modul mit 16GB.

              Hier der Auszug aus dem Syslog vom Neustart gestern ca. 16:30 Uhr. In der Nacht war er dann wierder weg. Was ich da erkenne ist das owserver anscheinend dauern die Verbindung verliert.

              Jan 11 17:27:01 odroid owserver[1327]: DEFAULT: ow_serial_open.c:(38) [No such file or directory] Cannot open port: /dev/owbus Permissions problem?
              Jan 11 17:27:01 odroid kernel: [ 3530.778201] usb 3-1.1: new full-speed USB device number 5 using xhci-hcd
              Jan 11 17:27:01 odroid owserver[1327]: message repeated 9 times: [ DEFAULT: ow_serial_open.c:(38) [No such file or directory] Cannot open port: /dev/owbus Permissions problem?]
              Jan 11 17:27:01 odroid owserver[1327]: DEFAULT: ow_reconnect.c:(70) Failed to reconnect LINK(emulate mode) bus master!
              Jan 11 17:27:01 odroid owserver[1327]: DEFAULT: ow_serial_open.c:(38) [No such file or directory] Cannot open port: /dev/owbus Permissions problem?
              Jan 11 17:27:01 odroid kernel: [ 3530.889393] usb 3-1.1: Manufacturer: FTDI
              Jan 11 17:27:01 odroid owserver[1327]: message repeated 9 times: [ DEFAULT: ow_serial_open.c:(38) [No such file or directory] Cannot open port: /dev/owbus Permissions problem?]
              Jan 11 17:27:01 odroid mtp-probe: checking bus 3, device 5: "/sys/devices/platform/soc:/soc:usb3-0:/12000000.dwc3:/xhci-hcd.2.auto/usb3/3-1/3-1.1"
              Jan 11 17:27:01 odroid mtp-probe: bus: 3, device: 5 was not an MTP device
              Jan 11 17:27:01 odroid owserver[1327]: DEFAULT: ow_reconnect.c:(70) Failed to reconnect LINK(emulate mode) bus master!
              Jan 11 17:27:57 odroid owserver[1327]: DEFAULT: ow_reconnect.c:(72) LINK(emulate mode) bus master reconnected
              Jan 11 17:27:58 odroid owserver[1327]: message repeated 4 times: [ DEFAULT: ow_reconnect.c:(72) LINK(emulate mode) bus master reconnected]
              Jan 11 17:37:20 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 17:38:50 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 17:37:21 odroid systemd[1]: Created slice User Slice of root.
              Jan 11 17:37:21 odroid systemd[1]: Starting User Manager for UID 0...
              Jan 11 17:37:21 odroid systemd[1]: Started Session c3 of user root.
              Jan 11 17:37:21 odroid systemd[2316]: Reached target Timers.
              Jan 11 17:37:21 odroid systemd[2316]: Reached target Paths.
              Jan 11 17:37:21 odroid systemd[2316]: Reached target Sockets.
              Jan 11 17:37:21 odroid systemd[2316]: Reached target Basic System.
              Jan 11 17:37:21 odroid systemd[2316]: Reached target Default.
              Jan 11 17:37:21 odroid systemd[2316]: Startup finished in 247ms.
              Jan 11 17:37:21 odroid systemd[1]: Started User Manager for UID 0.
              Jan 11 17:39:01 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 17:40:31 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 17:39:01 odroid CRON[3261]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
              Jan 11 17:40:01 odroid CRON[3772]: (smmsp) CMD (test -x /etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x /usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
              Jan 11 17:40:07 odroid sm-msp-queue[3791]: My unqualified host name (odroid) unknown; sleeping for retry
              Jan 11 17:41:12 odroid sm-msp-queue[3791]: unable to qualify my own domain name (odroid) -- using short name
              Jan 11 17:41:12 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 17:42:42 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 18:00:01 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 18:01:31 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 18:00:01 odroid CRON[12760]: (smmsp) CMD (test -x /etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x /usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
              Jan 11 18:00:06 odroid sm-msp-queue[12779]: My unqualified host name (odroid) unknown; sleeping for retry
              Jan 11 18:01:11 odroid sm-msp-queue[12779]: unable to qualify my own domain name (odroid) -- using short name
              Jan 11 18:09:01 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 18:10:31 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 18:09:01 odroid CRON[16797]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
              Jan 11 18:17:01 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 18:18:31 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 18:17:01 odroid CRON[20383]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
              Jan 11 18:20:01 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 18:21:31 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 18:20:01 odroid CRON[21723]: (smmsp) CMD (test -x /etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x /usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
              Jan 11 18:20:06 odroid sm-msp-queue[21742]: My unqualified host name (odroid) unknown; sleeping for retry
              Jan 11 18:21:11 odroid sm-msp-queue[21742]: unable to qualify my own domain name (odroid) -- using short name
              Jan 11 18:34:52 odroid systemd[1]: Stopping MySQL Community Server...
              Jan 11 18:34:52 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 18:36:22 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 18:34:54 odroid systemd[1]: Stopped MySQL Community Server.
              Jan 11 18:35:03 odroid systemd[1]: Starting MySQL Community Server...
              Jan 11 18:35:06 odroid systemd[1]: Started MySQL Community Server.
              Jan 11 18:35:41 odroid systemd[1]: Stopping MySQL Community Server...
              Jan 11 18:35:42 odroid systemd[1]: Stopped MySQL Community Server.
              Jan 11 18:39:01 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 18:40:31 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 18:39:01 odroid CRON[30407]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
              Jan 11 18:40:01 odroid CRON[30910]: (smmsp) CMD (test -x /etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x /usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
              Jan 11 18:40:07 odroid sm-msp-queue[30930]: My unqualified host name (odroid) unknown; sleeping for retry
              Jan 11 18:41:12 odroid sm-msp-queue[30930]: unable to qualify my own domain name (odroid) -- using short name
              Jan 11 18:41:12 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 18:42:42 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 18:45:43 odroid systemd[1]: Starting MySQL Community Server...
              Jan 11 18:45:43 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 18:47:13 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 18:45:45 odroid systemd[1]: Started MySQL Community Server.
              Jan 11 18:48:47 odroid systemd[1]: Stopping MySQL Community Server...
              Jan 11 18:48:47 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 18:50:17 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 18:48:49 odroid systemd[1]: Stopped MySQL Community Server.
              Jan 11 18:57:13 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 18:58:43 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 18:57:13 odroid systemd[1]: Stopping User Manager for UID 1000...
              Jan 11 18:57:13 odroid systemd[10620]: Stopped target Default.
              Jan 11 18:57:13 odroid systemd[10620]: Reached target Shutdown.
              Jan 11 18:57:13 odroid systemd[10620]: Starting Exit the Session...
              Jan 11 18:57:13 odroid systemd[10620]: Stopped target Basic System.
              Jan 11 18:57:13 odroid systemd[10620]: Stopped target Paths.
              Jan 11 18:57:13 odroid systemd[10620]: Stopped target Sockets.
              Jan 11 18:57:13 odroid systemd[10620]: Stopped target Timers.
              Jan 11 18:57:13 odroid systemd[10620]: Received SIGRTMIN+24 from PID 6572 (kill).
              Jan 11 18:57:13 odroid systemd[1]: Stopped User Manager for UID 1000.
              Jan 11 18:57:13 odroid systemd[1]: Removed slice User Slice of odroid.
              Jan 11 19:00:01 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 19:01:31 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 19:00:01 odroid CRON[7872]: (smmsp) CMD (test -x /etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x /usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
              Jan 11 19:00:06 odroid sm-msp-queue[7891]: My unqualified host name (odroid) unknown; sleeping for retry
              Jan 11 19:01:11 odroid sm-msp-queue[7891]: unable to qualify my own domain name (odroid) -- using short name
              Jan 11 19:09:01 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 19:10:31 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 19:09:01 odroid CRON[12068]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
              Jan 11 19:17:01 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 19:18:31 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 19:17:01 odroid CRON[15785]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
              Jan 11 19:20:01 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 19:21:31 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 19:20:01 odroid CRON[17178]: (smmsp) CMD (test -x /etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x /usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
              Jan 11 19:20:06 odroid sm-msp-queue[17197]: My unqualified host name (odroid) unknown; sleeping for retry
              Jan 11 19:21:11 odroid sm-msp-queue[17197]: unable to qualify my own domain name (odroid) -- using short name
              Jan 11 19:39:01 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 19:40:31 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 19:39:01 odroid CRON[26017]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
              Jan 11 19:40:02 odroid CRON[26518]: (smmsp) CMD (test -x /etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x /usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
              Jan 11 19:40:07 odroid sm-msp-queue[26537]: My unqualified host name (odroid) unknown; sleeping for retry
              Jan 11 19:41:12 odroid sm-msp-queue[26537]: unable to qualify my own domain name (odroid) -- using short name
              Jan 11 19:41:12 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 19:42:42 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 19:47:05 odroid systemd[1]: Starting Daily apt download activities...
              Jan 11 19:47:05 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 19:48:35 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 19:47:07 odroid systemd[1]: Started Daily apt download activities.
              Jan 11 20:00:01 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 20:01:31 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 20:00:01 odroid CRON[3635]: (smmsp) CMD (test -x /etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x /usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
              Jan 11 20:00:06 odroid sm-msp-queue[3660]: My unqualified host name (odroid) unknown; sleeping for retry
              Jan 11 20:01:11 odroid sm-msp-queue[3660]: unable to qualify my own domain name (odroid) -- using short name
              Jan 11 20:09:01 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 20:10:31 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 20:09:01 odroid CRON[7843]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
              Jan 11 20:17:01 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 20:18:31 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 20:17:01 odroid CRON[11697]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
              Jan 11 20:20:01 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 20:21:31 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 20:20:01 odroid CRON[13090]: (smmsp) CMD (test -x /etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x /usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
              Jan 11 20:20:06 odroid sm-msp-queue[13109]: My unqualified host name (odroid) unknown; sleeping for retry
              Jan 11 20:21:11 odroid sm-msp-queue[13109]: unable to qualify my own domain name (odroid) -- using short name
              Jan 11 20:39:01 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 20:40:31 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 20:39:01 odroid CRON[21863]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
              Jan 11 20:40:01 odroid CRON[22392]: (smmsp) CMD (test -x /etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x /usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
              Jan 11 20:40:06 odroid sm-msp-queue[22411]: My unqualified host name (odroid) unknown; sleeping for retry
              Jan 11 20:41:11 odroid sm-msp-queue[22411]: unable to qualify my own domain name (odroid) -- using short name
              Jan 11 20:41:11 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 20:42:41 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 20:50:01 odroid kernel: [15710.514092] usb 3-1.1: USB disconnect, device number 5
              Jan 11 20:50:01 odroid kernel: [15710.515958] ftdi_sio 3-1.1:1.0: device disconnected
              Jan 11 20:50:01 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 20:51:31 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 20:50:01 odroid kernel: [15710.741448] usb 3-1.1: new full-speed USB device number 6 using xhci-hcd
              Jan 11 20:50:01 odroid kernel: [15710.847688] usb 3-1.1: New USB device found, idVendor=0403, idProduct=6001
              Jan 11 20:50:01 odroid kernel: [15710.847698] usb 3-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
              Jan 11 20:50:01 odroid kernel: [15710.847705] usb 3-1.1: Product: FT232R USB UART
              Jan 11 20:50:01 odroid kernel: [15710.847711] usb 3-1.1: Manufacturer: FTDI
              Jan 11 20:50:01 odroid kernel: [15710.851575] ftdi_sio 3-1.1:1.0: FTDI USB Serial Device converter detected
              Jan 11 20:50:01 odroid kernel: [15710.851766] usb 3-1.1: Detected FT232RL
              Jan 11 20:50:01 odroid kernel: [15710.852388] usb 3-1.1: FTDI USB Serial Device converter now attached to ttyUSB1
              Jan 11 20:50:01 odroid mtp-probe: checking bus 3, device 6: "/sys/devices/platform/soc:/soc:usb3-0:/12000000.dwc3:/xhci-hcd.2.auto/usb3/3-1/3-1.1"
              Jan 11 20:50:01 odroid mtp-probe: bus: 3, device: 6 was not an MTP device
              Jan 11 20:50:42 odroid owserver[1327]: DEFAULT: ow_reconnect.c:(72) LINK(emulate mode) bus master reconnected
              Jan 11 20:58:01 odroid kernel: [16190.507126] usb 3-1-port1: disabled by hub (EMI?), re-enabling...
              Jan 11 20:58:01 odroid kernel: [16190.512128] usb 3-1.1: USB disconnect, device number 6
              Jan 11 20:58:01 odroid kernel: [16190.513390] ftdi_sio ttyUSB1: FTDI USB Serial Device converter now disconnected from ttyUSB1
              Jan 11 20:58:01 odroid kernel: [16190.513470] ftdi_sio 3-1.1:1.0: device disconnected
              Jan 11 20:58:01 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 20:59:31 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 20:58:01 odroid kernel: [16190.736164] usb 3-1.1: new full-speed USB device number 7 using xhci-hcd
              Jan 11 20:58:01 odroid kernel: [16190.842510] usb 3-1.1: New USB device found, idVendor=0403, idProduct=6001
              Jan 11 20:58:01 odroid kernel: [16190.842521] usb 3-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
              Jan 11 20:58:01 odroid kernel: [16190.842530] usb 3-1.1: Product: FT232R USB UART
              Jan 11 20:58:01 odroid kernel: [16190.842538] usb 3-1.1: Manufacturer: FTDI
              Jan 11 20:58:01 odroid kernel: [16190.842545] usb 3-1.1: SerialNumber: A900fwyb
              Jan 11 20:58:01 odroid kernel: [16190.845873] ftdi_sio 3-1.1:1.0: FTDI USB Serial Device converter detected
              Jan 11 20:50:42 odroid owserver[1327]: DEFAULT: ow_reconnect.c:(72) LINK(emulate mode) bus master reconnected
              Jan 11 20:58:01 odroid owserver[1327]: DEFAULT: ow_serial_open.c:(38) [No such file or directory] Cannot open port: /dev/owbus Permissions problem?
              Jan 11 20:58:01 odroid owserver[1327]: message repeated 9 times: [ DEFAULT: ow_serial_open.c:(38) [No such file or directory] Cannot open port: /dev/owbus Permissions problem?]
              Jan 11 20:58:01 odroid mtp-probe: checking bus 3, device 7: "/sys/devices/platform/soc:/soc:usb3-0:/12000000.dwc3:/xhci-hcd.2.auto/usb3/3-1/3-1.1"
              Jan 11 20:58:01 odroid mtp-probe: bus: 3, device: 7 was not an MTP device
              Jan 11 20:58:01 odroid owserver[1327]: DEFAULT: ow_reconnect.c:(70) Failed to reconnect LINK(emulate mode) bus master!
              Jan 11 20:58:42 odroid owserver[1327]: DEFAULT: ow_reconnect.c:(72) LINK(emulate mode) bus master reconnected
              Jan 11 20:58:43 odroid owserver[1327]: message repeated 2 times: [ DEFAULT: ow_reconnect.c:(72) LINK(emulate mode) bus master reconnected]
              Jan 11 21:00:01 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 21:01:31 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 21:00:01 odroid CRON[31493]: (smmsp) CMD (test -x /etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x /usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
              Jan 11 21:00:06 odroid sm-msp-queue[31514]: My unqualified host name (odroid) unknown; sleeping for retry
              Jan 11 21:01:11 odroid sm-msp-queue[31514]: unable to qualify my own domain name (odroid) -- using short name
              Jan 11 21:09:01 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 21:10:31 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 21:09:02 odroid CRON[3534]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
              Jan 11 21:17:01 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 21:18:31 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 21:17:01 odroid CRON[7320]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
              Jan 11 21:20:01 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 21:21:31 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 21:20:01 odroid CRON[8669]: (smmsp) CMD (test -x /etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x /usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
              Jan 11 21:20:06 odroid sm-msp-queue[8688]: My unqualified host name (odroid) unknown; sleeping for retry
              Jan 11 21:21:11 odroid sm-msp-queue[8688]: unable to qualify my own domain name (odroid) -- using short name
              Jan 11 21:39:01 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 21:40:31 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 21:39:01 odroid CRON[17264]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
              Jan 11 21:40:01 odroid CRON[17742]: (smmsp) CMD (test -x /etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x /usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
              Jan 11 21:40:06 odroid sm-msp-queue[17761]: My unqualified host name (odroid) unknown; sleeping for retry
              Jan 11 21:41:11 odroid sm-msp-queue[17761]: unable to qualify my own domain name (odroid) -- using short name
              Jan 11 21:41:11 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 21:42:41 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 22:00:01 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 22:01:31 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 22:00:01 odroid CRON[26743]: (smmsp) CMD (test -x /etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x /usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
              Jan 11 22:00:06 odroid sm-msp-queue[26762]: My unqualified host name (odroid) unknown; sleeping for retry
              Jan 11 22:01:11 odroid sm-msp-queue[26762]: unable to qualify my own domain name (odroid) -- using short name
              Jan 11 22:09:01 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 22:10:31 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 22:09:02 odroid CRON[30817]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
              Jan 11 22:17:01 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 22:18:31 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 22:17:01 odroid CRON[2095]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
              Jan 11 22:20:01 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 22:21:31 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 22:20:01 odroid CRON[3567]: (smmsp) CMD (test -x /etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x /usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
              Jan 11 22:20:06 odroid sm-msp-queue[3586]: My unqualified host name (odroid) unknown; sleeping for retry
              Jan 11 22:21:11 odroid sm-msp-queue[3586]: unable to qualify my own domain name (odroid) -- using short name
              Jan 11 22:39:01 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 22:40:31 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 22:39:01 odroid CRON[12106]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
              Jan 11 22:40:01 odroid CRON[12602]: (smmsp) CMD (test -x /etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x /usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
              Jan 11 22:40:06 odroid sm-msp-queue[12621]: My unqualified host name (odroid) unknown; sleeping for retry
              Jan 11 22:41:11 odroid sm-msp-queue[12621]: unable to qualify my own domain name (odroid) -- using short name
              Jan 11 22:41:11 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 22:42:41 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 22:53:04 odroid owserver[1327]: DEFAULT: ow_serial_open.c:(38) [No such device] Cannot open port: /dev/owbus Permissions problem?
              Jan 11 22:53:04 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 22:54:34 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 22:53:04 odroid owserver[1327]: DEFAULT: ow_serial_open.c:(38) [No such file or directory] Cannot open port: /dev/owbus Permissions problem?
              Jan 11 22:53:04 odroid owserver[1327]: message repeated 7 times: [ DEFAULT: ow_serial_open.c:(38) [No such file or directory] Cannot open port: /dev/owbus Permissions problem?]
              Jan 11 22:53:04 odroid owserver[1327]: DEFAULT: ow_reconnect.c:(70) Failed to reconnect LINK(emulate mode) bus master!
              Jan 11 22:53:04 odroid owserver[1327]: DEFAULT: ow_serial_open.c:(38) [No such file or directory] Cannot open port: /dev/owbus Permissions problem?
              Jan 11 22:53:04 odroid kernel: [23094.286727] usb 3-1.1: new full-speed USB device number 8 using xhci-hcd
              Jan 11 22:53:04 odroid kernel: [23094.393165] usb 3-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
              Jan 11 22:53:04 odroid kernel: [23094.393179] usb 3-1.1: Manufacturer: FTDI
              Jan 11 22:53:04 odroid owserver[1327]: message repeated 9 times: [ DEFAULT: ow_serial_open.c:(38) [No such file or directory] Cannot open port: /dev/owbus Permissions problem?]
              Jan 11 22:53:04 odroid mtp-probe: checking bus 3, device 8: "/sys/devices/platform/soc:/soc:usb3-0:/12000000.dwc3:/xhci-hcd.2.auto/usb3/3-1/3-1.1"
              Jan 11 22:53:04 odroid mtp-probe: bus: 3, device: 8 was not an MTP device
              Jan 11 22:53:05 odroid owserver[1327]: DEFAULT: ow_reconnect.c:(70) Failed to reconnect LINK(emulate mode) bus master!
              Jan 11 22:54:16 odroid owserver[1327]: DEFAULT: ow_reconnect.c:(72) LINK(emulate mode) bus master reconnected
              Jan 11 22:54:16 odroid owserver[1327]: message repeated 5 times: [ DEFAULT: ow_reconnect.c:(72) LINK(emulate mode) bus master reconnected]
              Jan 11 23:00:01 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 23:01:31 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 23:00:01 odroid CRON[21724]: (smmsp) CMD (test -x /etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x /usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
              Jan 11 23:00:06 odroid sm-msp-queue[21743]: My unqualified host name (odroid) unknown; sleeping for retry
              Jan 11 23:01:11 odroid sm-msp-queue[21743]: unable to qualify my own domain name (odroid) -- using short name
              Jan 11 23:09:01 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 23:10:31 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 23:09:01 odroid CRON[25753]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
              Jan 11 23:10:01 odroid kernel: [24110.570455] ftdi_sio ttyUSB0: usb_serial_generic_write_bulk_callback - nonzero urb status: -71
              Jan 11 23:10:01 odroid kernel: [24110.578391] ftdi_sio ttyUSB0: failed to get modem status: -71
              Jan 11 23:10:01 odroid kernel: [24110.644780] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
              Jan 11 23:10:01 odroid kernel: [24110.644994] ftdi_sio 3-1.1:1.0: device disconnected
              Jan 11 23:10:01 odroid owserver[1327]: DEFAULT: ow_serial_open.c:(38) [No such device] Cannot open port: /dev/owbus Permissions problem?
              Jan 11 23:10:01 odroid owserver[1327]: DEFAULT: ow_serial_open.c:(38) [No such file or directory] Cannot open port: /dev/owbus Permissions problem?
              Jan 11 23:10:01 odroid owserver[1327]: message repeated 10 times: [ DEFAULT: ow_serial_open.c:(38) [No such file or directory] Cannot open port: /dev/owbus Permissions problem?]
              Jan 11 23:10:01 odroid owserver[1327]: DEFAULT: ow_reconnect.c:(70) Failed to reconnect LINK(emulate mode) bus master!
              Jan 11 23:10:01 odroid owserver[1327]: DEFAULT: ow_reconnect.c:(72) LINK(emulate mode) bus master reconnected
              Jan 11 23:10:01 odroid owserver[1327]: DEFAULT: ow_serial_open.c:(38) [No such file or directory] Cannot open port: /dev/owbus Permissions problem?
              Jan 11 23:10:01 odroid kernel: [24110.982057] usb 3-1.1: FTDI USB Serial Device converter now attached to ttyUSB0
              Jan 11 23:10:01 odroid owserver[1327]: message repeated 12 times: [ DEFAULT: ow_serial_open.c:(38) [No such file or directory] Cannot open port: /dev/owbus Permissions problem?]
              Jan 11 23:10:01 odroid mtp-probe: checking bus 3, device 9: "/sys/devices/platform/soc:/soc:usb3-0:/12000000.dwc3:/xhci-hcd.2.auto/usb3/3-1/3-1.1"
              Jan 11 23:10:01 odroid mtp-probe: bus: 3, device: 9 was not an MTP device
              Jan 11 23:10:01 odroid owserver[1327]: DEFAULT: ow_reconnect.c:(70) Failed to reconnect LINK(emulate mode) bus master!
              Jan 11 23:10:01 odroid owserver[1327]: DEFAULT: ow_reconnect.c:(72) LINK(emulate mode) bus master reconnected
              Jan 11 23:10:57 odroid owserver[1327]: message repeated 5 times: [ DEFAULT: ow_reconnect.c:(72) LINK(emulate mode) bus master reconnected]
              Jan 11 23:17:01 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 23:18:31 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 23:17:01 odroid CRON[29360]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
              Jan 11 23:20:01 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 23:21:31 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 23:20:01 odroid CRON[30661]: (smmsp) CMD (test -x /etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x /usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
              Jan 11 23:20:06 odroid sm-msp-queue[30680]: My unqualified host name (odroid) unknown; sleeping for retry
              Jan 11 23:21:11 odroid sm-msp-queue[30680]: unable to qualify my own domain name (odroid) -- using short name
              Jan 11 23:39:01 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 23:40:31 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 11 23:39:01 odroid CRON[6921]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
              Jan 11 23:40:01 odroid CRON[7417]: (smmsp) CMD (test -x /etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x /usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
              Jan 11 23:40:06 odroid sm-msp-queue[7436]: My unqualified host name (odroid) unknown; sleeping for retry
              Jan 11 23:41:11 odroid sm-msp-queue[7436]: unable to qualify my own domain name (odroid) -- using short name
              Jan 11 23:41:11 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Fri Jan 11 23:42:41 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 12 00:00:01 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Sat Jan 12 00:01:31 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 12 00:00:01 odroid CRON[16275]: (smmsp) CMD (test -x /etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x /usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
              Jan 12 00:00:06 odroid sm-msp-queue[16294]: My unqualified host name (odroid) unknown; sleeping for retry
              Jan 12 00:01:11 odroid sm-msp-queue[16294]: unable to qualify my own domain name (odroid) -- using short name
              Jan 12 00:09:01 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Sat Jan 12 00:10:31 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 12 00:09:01 odroid CRON[20334]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
              Jan 12 00:17:01 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Sat Jan 12 00:18:31 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 12 00:17:01 odroid CRON[23917]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
              Jan 12 00:20:01 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Sat Jan 12 00:21:31 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 12 00:20:01 odroid CRON[25243]: (smmsp) CMD (test -x /etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x /usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
              Jan 12 00:20:06 odroid sm-msp-queue[25262]: My unqualified host name (odroid) unknown; sleeping for retry
              Jan 12 00:21:11 odroid sm-msp-queue[25262]: unable to qualify my own domain name (odroid) -- using short name
              Jan 12 00:39:02 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Sat Jan 12 00:40:32 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 12 00:39:02 odroid CRON[1314]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
              Jan 12 00:40:01 odroid CRON[1862]: (smmsp) CMD (test -x /etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x /usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
              Jan 12 00:40:06 odroid sm-msp-queue[1881]: My unqualified host name (odroid) unknown; sleeping for retry
              Jan 12 00:41:11 odroid sm-msp-queue[1881]: unable to qualify my own domain name (odroid) -- using short name
              Jan 12 00:41:11 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Sat Jan 12 00:42:41 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 12 00:58:30 odroid rsyslogd-2007: action 'action 10' suspended, next retry is Sat Jan 12 01:00:00 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
              Jan 12 00:58:30 odroid systemd[1]: Stopping User Manager for UID 0...
              Jan 12 00:58:30 odroid systemd[2316]: Reached target Shutdown.
              Jan 12 00:58:30 odroid systemd[2316]: Stopped target Default.
              Jan 12 00:58:30 odroid systemd[2316]: Stopped target Basic System.
              Jan 12 00:58:30 odroid systemd[2316]: Stopped target Sockets.
              Jan 12 00:58:30 odroid systemd[2316]: Stopped target Paths.
              Jan 12 00:58:30 odroid systemd[2316]: Stopped target Timers.
              Jan 12 00:58:30 odroid systemd[2316]: Starting Exit the Session...
              Jan 12 00:58:30 odroid systemd[2316]: Received SIGRTMIN+24 from PID 10460 (kill).
              Jan 12 00:58:30 odroid systemd[1]: Stopped User Manager for UID 0.
              Jan 12 00:58:30 odroid systemd[1]: Removed slice User Slice of root.
              
              
              1 Antwort Letzte Antwort
              0
              • HomoranH Nicht stören
                HomoranH Nicht stören
                Homoran
                Global Moderator Administrators
                schrieb am zuletzt editiert von
                #7

                @fortschritt311:

                Was ich da erkenne ist das owserver anscheinend dauern die Verbindung verliert. `

                Dann stürzt nicht ioBroker ab - sondern dein OW-Server reisst den Odroid runter (… auf dem AUCH ioBroker läuft)

                Gruß

                Rainer

                kein Support per PN! - Fragen im Forum stellen -
                Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
                Das Forum freut sich über eine Spende. Benutzt dazu den Spendenbutton im Header. Danke!
                der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

                1 Antwort Letzte Antwort
                0
                • F Offline
                  F Offline
                  fortschritt311
                  schrieb am zuletzt editiert von
                  #8

                  Hm..der owfs-Adapter wurde von 0.41 auf 0.50 geupdatet.

                  Am owserver bzw. owfs-Package wurde nichts geändert. Der lief ja vorher auch schon da drauf. :?

                  1 Antwort Letzte Antwort
                  0
                  • wendy2702W Online
                    wendy2702W Online
                    wendy2702
                    schrieb am zuletzt editiert von
                    #9

                    Kannst doch zum Testen den OW Adapter mal stoppen und schauen was dann passiert.

                    Bitte keine Fragen per PN, die gehören ins Forum!

                    Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

                    1 Antwort Letzte Antwort
                    0
                    • apollon77A Offline
                      apollon77A Offline
                      apollon77
                      schrieb am zuletzt editiert von
                      #10

                      Node 6 hat ein memory leak.

                      @Homoran: postest du bitte mal die Details um mem Limit zu setzen.

                      Ja in dem Fall wäre ein node Update auf >8.11 sinnvoll aber das mem Limit sollte schon helfen.

                      Gesendet vom Handy …

                      Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                      • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                      • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                      1 Antwort Letzte Antwort
                      0
                      • HomoranH Nicht stören
                        HomoranH Nicht stören
                        Homoran
                        Global Moderator Administrators
                        schrieb am zuletzt editiert von
                        #11

                        @apollon77:

                        @Homoran: postest du bitte mal die Details um mem Limit zu setzen. `

                        Bitte hier lesen:

                        viewtopic.php?f=8&t=20059&hilit=RasPi+r … 20#p211448

                        Gruß

                        Rainer

                        kein Support per PN! - Fragen im Forum stellen -
                        Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
                        Das Forum freut sich über eine Spende. Benutzt dazu den Spendenbutton im Header. Danke!
                        der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

                        1 Antwort Letzte Antwort
                        0
                        • F Offline
                          F Offline
                          fortschritt311
                          schrieb am zuletzt editiert von
                          #12

                          @wendy2702

                          Abschalten geht leider nicht im Winter, dann geht die Heizung nicht mehr. Habe alles über iobroker laufen.

                          @Hormoran

                          Danke für den Tip. Das Problem sitzt immer vor dem Rechner. :oops: Ich denke das es am owserver liegt. Er legt den kompletten odroid lahm.

                          Ich hatte vergessen, das ich zusätzlich zu den Updates auch noch ein 1-Wire LCD Controller samt Display an den Bus gehangen habe. Um dort etwas anzuzeigen nutze ich die GPIOs des LCD Controllers (An/Aus, Vor/Zurück) in der Scriptengine. Dazu hatte ich das Polling für die 3 GPIOs auf 1s gestellt. Habe die GPIOs jetzt mal rausgenommen, und seit dem kommen keine Lesefehler mehr im iobroker und auch im syslog kam seit dem kein Fehler mehr. Ich werde das mal weiter beobachten.

                          Könnte ja das Thema jetzt "Hohes owfs-Pollingintervall lässt System abstürzen" heißen :roll:

                          Gibts da eine Möglichkeit die Dinger sauber zu pollen?

                          Das mit dem Memory Leak schau ich mir auf jeden Fall an. :D

                          Danke & Gruß

                          Maik

                          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
                          FAQ Cloud / IOT
                          HowTo: Node.js-Update
                          HowTo: Backup/Restore
                          Downloads
                          BLOG

                          510

                          Online

                          32.7k

                          Benutzer

                          82.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