(gelöst)IoBroker über Webinterface nicht erreichbar (Frage)
-
Hallo, ich habe einen Rasberry 3 mit einem Loxberry Image. Habe darauf Docker installiert mit portainer.io
Über den Portainer habe ich den buanet/iobroker installiert.
Der Iobroker habe ich gestartet und läuft auch. Leider kann ich den nicht über das Webinterface erreichen. (10.0.0.11:8081)
Bei Published Port steht auch nichts drin bei portainer.io
Ich bitte um Hilfe, damit ich das Webinterface erreichen kann. -
Ich kann gerne noch weitere Informationen noch hochladen um das ganze klarer darzustellen.
root@75749fbeed2c:/opt/iobroker# cat log/iobroker.2020-11-09.log 2020-11-09 22:53:34.362 - info: host.75749fbeed2c iobroker.js-controller version 3.1.6 js-controller starting 2020-11-09 22:53:34.372 - info: host.75749fbeed2c Copyright (c) 2014-2020 bluefox, 2014 hobbyquaker 2020-11-09 22:53:34.373 - info: host.75749fbeed2c hostname: 75749fbeed2c, node: v12.19.0 2020-11-09 22:53:34.376 - info: host.75749fbeed2c ip addresses: 172.17.0.3 2020-11-09 22:53:34.583 - info: host.75749fbeed2c connected to Objects and States 2020-11-09 22:53:35.233 - info: host.75749fbeed2c 3 instances found 2020-11-09 22:53:35.263 - info: host.75749fbeed2c starting 3 instances 2020-11-09 22:53:35.309 - info: host.75749fbeed2c instance system.adapter.admin.0 started with pid 221 2020-11-09 22:53:39.283 - info: host.75749fbeed2c instance system.adapter.discovery.0 started with pid 244 2020-11-09 22:53:39.539 - info: admin.0 (221) starting. Version 4.0.10 in /opt/iobroker/node_modules/iobroker.admin, node: v12.19.0, js-controller: 3.1.6 2020-11-09 22:53:39.673 - info: admin.0 (221) requesting all states 2020-11-09 22:53:39.678 - info: admin.0 (221) requesting all objects 2020-11-09 22:53:39.780 - info: admin.0 (221) received all objects 2020-11-09 22:53:39.799 - warn: admin.0 (221) Repository cannot be read 2020-11-09 22:53:39.834 - info: admin.0 (221) http server listening on port 8081 2020-11-09 22:53:39.836 - info: admin.0 (221) Use link "http://localhost:8081" to configure. 2020-11-09 22:53:42.542 - info: discovery.0 (244) starting. Version 2.3.7 in /opt/iobroker/node_modules/iobroker.discovery, node: v12.19.0, js-controller: 3.1.6 2020-11-09 22:53:43.283 - info: host.75749fbeed2c instance system.adapter.info.0 started with pid 263 2020-11-09 22:53:52.261 - info: info.0 (263) starting. Version 1.7.2 in /opt/iobroker/node_modules/iobroker.info, node: v12.19.0, js-controller: 3.1.6 2020-11-09 22:53:54.535 - warn: info.0 (263) Object info.0.sysinfo.disks.blockDevices.dev0.group is invalid: obj.common.type has an invalid value (undefined) but has to be one of number, string, boolean, array, object, mixed, file, json 2020-11-09 22:53:54.537 - warn: info.0 (263) This object will not be created in future versions. Please report this to the developer. 2020-11-09 22:53:54.543 - warn: info.0 (263) Object info.0.sysinfo.disks.blockDevices.dev1.group is invalid: obj.common.type has an invalid value (undefined) but has to be one of number, string, boolean, array, object, mixed, file, json 2020-11-09 22:53:54.544 - warn: info.0 (263) This object will not be created in future versions. Please report this to the developer. 2020-11-09 22:53:54.548 - warn: info.0 (263) Object info.0.sysinfo.disks.blockDevices.dev2.group is invalid: obj.common.type has an invalid value (undefined) but has to be one of number, string, boolean, array, object, mixed, file, json 2020-11-09 22:53:54.550 - warn: info.0 (263) This object will not be created in future versions. Please report this to the developer. 2020-11-09 22:53:54.554 - warn: info.0 (263) Object info.0.sysinfo.disks.blockDevices.dev3.group is invalid: obj.common.type has an invalid value (undefined) but has to be one of number, string, boolean, array, object, mixed, file, json 2020-11-09 22:53:54.555 - warn: info.0 (263) This object will not be created in future versions. Please report this to the developer. 2020-11-09 22:53:54.560 - warn: info.0 (263) Object info.0.sysinfo.disks.blockDevices.dev4.group is invalid: obj.common.type has an invalid value (undefined) but has to be one of number, string, boolean, array, object, mixed, file, json 2020-11-09 22:53:54.561 - warn: info.0 (263) This object will not be created in future versions. Please report this to the developer. 2020-11-09 22:53:54.565 - warn: info.0 (263) Object info.0.sysinfo.disks.blockDevices.dev5.group is invalid: obj.common.type has an invalid value (undefined) but has to be one of number, string, boolean, array, object, mixed, file, json 2020-11-09 22:53:54.566 - warn: info.0 (263) This object will not be created in future versions. Please report this to the developer. 2020-11-09 22:53:55.379 - info: info.0 (263) Popup news was read... 2020-11-09 22:58:33.341 - info: host.75749fbeed2c iobroker.js-controller version 3.1.6 js-controller starting 2020-11-09 22:58:33.350 - info: host.75749fbeed2c Copyright (c) 2014-2020 bluefox, 2014 hobbyquaker 2020-11-09 22:58:33.351 - info: host.75749fbeed2c hostname: 75749fbeed2c, node: v12.19.0 2020-11-09 22:58:33.354 - info: host.75749fbeed2c ip addresses: 172.17.0.3 2020-11-09 22:58:33.577 - info: host.75749fbeed2c connected to Objects and States 2020-11-09 22:58:34.404 - info: host.75749fbeed2c 3 instances found 2020-11-09 22:58:34.435 - info: host.75749fbeed2c starting 3 instances 2020-11-09 22:58:34.480 - info: host.75749fbeed2c instance system.adapter.admin.0 started with pid 121 2020-11-09 22:58:38.454 - info: host.75749fbeed2c instance system.adapter.discovery.0 started with pid 132 2020-11-09 22:58:39.323 - info: admin.0 (121) starting. Version 4.0.10 in /opt/iobroker/node_modules/iobroker.admin, node: v12.19.0, js-controller: 3.1.6 2020-11-09 22:58:39.512 - info: admin.0 (121) requesting all states 2020-11-09 22:58:39.515 - info: admin.0 (121) requesting all objects 2020-11-09 22:58:39.862 - info: admin.0 (121) received all objects 2020-11-09 22:58:39.877 - warn: admin.0 (121) Repository cannot be read 2020-11-09 22:58:40.017 - info: admin.0 (121) http server listening on port 8081 2020-11-09 22:58:40.019 - info: admin.0 (121) Use link "http://localhost:8081" to configure. 2020-11-09 22:58:42.457 - info: host.75749fbeed2c instance system.adapter.info.0 started with pid 147 2020-11-09 22:58:42.470 - info: discovery.0 (132) starting. Version 2.3.7 in /opt/iobroker/node_modules/iobroker.discovery, node: v12.19.0, js-controller: 3.1.6 2020-11-09 22:58:51.301 - info: info.0 (147) starting. Version 1.7.2 in /opt/iobroker/node_modules/iobroker.info, node: v12.19.0, js-controller: 3.1.6 2020-11-09 22:58:53.795 - info: info.0 (147) Popup news was read... 2020-11-09 23:09:56.815 - info: host.75749fbeed2c iobroker.js-controller version 3.1.6 js-controller starting 2020-11-09 23:09:56.824 - info: host.75749fbeed2c Copyright (c) 2014-2020 bluefox, 2014 hobbyquaker 2020-11-09 23:09:56.826 - info: host.75749fbeed2c hostname: 75749fbeed2c, node: v12.19.0 2020-11-09 23:09:56.829 - info: host.75749fbeed2c ip addresses: 172.17.0.3 2020-11-09 23:09:56.917 - info: host.75749fbeed2c Error inMem-objects listening on port 9001 2020-11-09 23:09:56.944 - info: host.75749fbeed2c Error inMem-states listening on port 9000 2020-11-09 23:09:57.057 - info: host.75749fbeed2c connected to Objects and States 2020-11-09 23:09:57.696 - info: host.75749fbeed2c 3 instances found 2020-11-09 23:09:57.724 - info: host.75749fbeed2c starting 3 instances 2020-11-09 23:09:57.762 - info: host.75749fbeed2c instance system.adapter.admin.0 started with pid 1062 2020-11-09 23:10:00.320 - error: admin.0 (1062) admin.0 invalid process id scenario 121 vs. own ID 1062. Stopping 2020-11-09 23:10:00.325 - info: admin.0 (1062) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2020-11-09 23:10:00.857 - error: host.75749fbeed2c instance system.adapter.admin.0 terminated by request of the instance itself and will not be restarted, before user restarts it. 2020-11-09 23:10:00.858 - info: host.75749fbeed2c Do not restart adapter system.adapter.admin.0 because desired by instance 2020-11-09 23:10:01.750 - info: host.75749fbeed2c instance system.adapter.discovery.0 started with pid 1073 2020-11-09 23:10:03.500 - error: discovery.0 (1073) discovery.0 invalid process id scenario 132 vs. own ID 1073. Stopping 2020-11-09 23:10:03.506 - info: discovery.0 (1073) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2020-11-09 23:10:04.055 - error: host.75749fbeed2c instance system.adapter.discovery.0 terminated by request of the instance itself and will not be restarted, before user restarts it. 2020-11-09 23:10:04.058 - info: host.75749fbeed2c Do not restart adapter system.adapter.discovery.0 because desired by instance 2020-11-09 23:10:05.753 - info: host.75749fbeed2c instance system.adapter.info.0 started with pid 1086 2020-11-09 23:10:08.945 - error: info.0 (1086) info.0 invalid process id scenario 147 vs. own ID 1086. Stopping 2020-11-09 23:10:08.951 - info: info.0 (1086) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2020-11-09 23:10:09.493 - error: host.75749fbeed2c instance system.adapter.info.0 terminated by request of the instance itself and will not be restarted, before user restarts it. 2020-11-09 23:10:09.496 - info: host.75749fbeed2c Do not restart adapter system.adapter.info.0 because desired by instance 2020-11-09 23:11:56.349 - info: host.75749fbeed2c iobroker.js-controller version 3.1.6 js-controller starting 2020-11-09 23:11:56.362 - info: host.75749fbeed2c Copyright (c) 2014-2020 bluefox, 2014 hobbyquaker 2020-11-09 23:11:56.363 - info: host.75749fbeed2c hostname: 75749fbeed2c, node: v12.19.0 2020-11-09 23:11:56.368 - info: host.75749fbeed2c ip addresses: 172.17.0.3 2020-11-09 23:11:56.453 - info: host.75749fbeed2c Error inMem-objects listening on port 9001 2020-11-09 23:11:56.483 - info: host.75749fbeed2c Error inMem-states listening on port 9000 2020-11-09 23:11:56.543 - info: host.75749fbeed2c connected to Objects and States 2020-11-09 23:11:57.092 - info: host.75749fbeed2c 3 instances found 2020-11-09 23:11:57.141 - info: host.75749fbeed2c starting 3 instances 2020-11-09 23:11:57.188 - info: host.75749fbeed2c instance system.adapter.admin.0 started with pid 1212 2020-11-09 23:11:59.844 - error: admin.0 (1212) admin.0 invalid process id scenario 121 vs. own ID 1212. Stopping 2020-11-09 23:11:59.849 - info: admin.0 (1212) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2020-11-09 23:12:00.381 - error: host.75749fbeed2c instance system.adapter.admin.0 terminated by request of the instance itself and will not be restarted, before user restarts it. 2020-11-09 23:12:00.384 - info: host.75749fbeed2c Do not restart adapter system.adapter.admin.0 because desired by instance 2020-11-09 23:12:01.161 - info: host.75749fbeed2c instance system.adapter.discovery.0 started with pid 1223 2020-11-09 23:12:03.022 - error: discovery.0 (1223) discovery.0 invalid process id scenario 132 vs. own ID 1223. Stopping 2020-11-09 23:12:03.027 - info: discovery.0 (1223) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2020-11-09 23:12:03.550 - error: host.75749fbeed2c instance system.adapter.discovery.0 terminated by request of the instance itself and will not be restarted, before user restarts it. 2020-11-09 23:12:03.552 - info: host.75749fbeed2c Do not restart adapter system.adapter.discovery.0 because desired by instance 2020-11-09 23:12:05.171 - info: host.75749fbeed2c instance system.adapter.info.0 started with pid 1234 2020-11-09 23:12:08.296 - error: info.0 (1234) info.0 invalid process id scenario 147 vs. own ID 1234. Stopping 2020-11-09 23:12:08.303 - info: info.0 (1234) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2020-11-09 23:12:08.846 - error: host.75749fbeed2c instance system.adapter.info.0 terminated by request of the instance itself and will not be restarted, before user restarts it. 2020-11-09 23:12:08.849 - info: host.75749fbeed2c Do not restart adapter system.adapter.info.0 because desired by instance 2020-11-09 23:14:15.849 - info: host.75749fbeed2c iobroker.js-controller version 3.1.6 js-controller starting 2020-11-09 23:14:15.861 - info: host.75749fbeed2c Copyright (c) 2014-2020 bluefox, 2014 hobbyquaker 2020-11-09 23:14:15.863 - info: host.75749fbeed2c hostname: 75749fbeed2c, node: v12.19.0 2020-11-09 23:14:15.867 - info: host.75749fbeed2c ip addresses: 172.17.0.3 2020-11-09 23:14:15.954 - info: host.75749fbeed2c Error inMem-objects listening on port 9001 2020-11-09 23:14:15.983 - info: host.75749fbeed2c Error inMem-states listening on port 9000 2020-11-09 23:14:16.050 - info: host.75749fbeed2c connected to Objects and States 2020-11-09 23:14:16.593 - info: host.75749fbeed2c 3 instances found 2020-11-09 23:14:16.626 - info: host.75749fbeed2c starting 3 instances 2020-11-09 23:14:16.672 - info: host.75749fbeed2c instance system.adapter.admin.0 started with pid 1380 2020-11-09 23:14:19.283 - error: admin.0 (1380) admin.0 invalid process id scenario 121 vs. own ID 1380. Stopping 2020-11-09 23:14:19.289 - info: admin.0 (1380) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2020-11-09 23:14:19.850 - error: host.75749fbeed2c instance system.adapter.admin.0 terminated by request of the instance itself and will not be restarted, before user restarts it. 2020-11-09 23:14:19.853 - info: host.75749fbeed2c Do not restart adapter system.adapter.admin.0 because desired by instance 2020-11-09 23:14:20.654 - info: host.75749fbeed2c instance system.adapter.discovery.0 started with pid 1391 2020-11-09 23:14:22.392 - error: discovery.0 (1391) discovery.0 invalid process id scenario 132 vs. own ID 1391. Stopping 2020-11-09 23:14:22.398 - info: discovery.0 (1391) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2020-11-09 23:14:22.925 - error: host.75749fbeed2c instance system.adapter.discovery.0 terminated by request of the instance itself and will not be restarted, before user restarts it. 2020-11-09 23:14:22.929 - info: host.75749fbeed2c Do not restart adapter system.adapter.discovery.0 because desired by instance 2020-11-09 23:14:24.656 - info: host.75749fbeed2c instance system.adapter.info.0 started with pid 1402 2020-11-09 23:14:27.837 - error: info.0 (1402) info.0 invalid process id scenario 147 vs. own ID 1402. Stopping 2020-11-09 23:14:27.842 - info: info.0 (1402) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2020-11-09 23:14:28.367 - error: host.75749fbeed2c instance system.adapter.info.0 terminated by request of the instance itself and will not be restarted, before user restarts it. 2020-11-09 23:14:28.369 - info: host.75749fbeed2c Do not restart adapter system.adapter.info.0 because desired by instance 2020-11-09 23:15:45.367 - info: host.75749fbeed2c iobroker.js-controller version 3.1.6 js-controller starting 2020-11-09 23:15:45.379 - info: host.75749fbeed2c Copyright (c) 2014-2020 bluefox, 2014 hobbyquaker 2020-11-09 23:15:45.381 - info: host.75749fbeed2c hostname: 75749fbeed2c, node: v12.19.0 2020-11-09 23:15:45.385 - info: host.75749fbeed2c ip addresses: 172.17.0.3 2020-11-09 23:15:45.471 - info: host.75749fbeed2c Error inMem-objects listening on port 9001 2020-11-09 23:15:45.501 - info: host.75749fbeed2c Error inMem-states listening on port 9000 2020-11-09 23:15:45.560 - info: host.75749fbeed2c connected to Objects and States 2020-11-09 23:15:46.098 - info: host.75749fbeed2c 3 instances found 2020-11-09 23:15:46.144 - info: host.75749fbeed2c starting 3 instances 2020-11-09 23:15:46.190 - info: host.75749fbeed2c instance system.adapter.admin.0 started with pid 1503 2020-11-09 23:15:48.839 - error: admin.0 (1503) admin.0 invalid process id scenario 121 vs. own ID 1503. Stopping 2020-11-09 23:15:48.844 - info: admin.0 (1503) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2020-11-09 23:15:49.375 - error: host.75749fbeed2c instance system.adapter.admin.0 terminated by request of the instance itself and will not be restarted, before user restarts it. 2020-11-09 23:15:49.377 - info: host.75749fbeed2c Do not restart adapter system.adapter.admin.0 because desired by instance 2020-11-09 23:15:50.170 - info: host.75749fbeed2c instance system.adapter.discovery.0 started with pid 1525 2020-11-09 23:15:51.921 - error: discovery.0 (1525) discovery.0 invalid process id scenario 132 vs. own ID 1525. Stopping 2020-11-09 23:15:51.926 - info: discovery.0 (1525) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2020-11-09 23:15:52.465 - error: host.75749fbeed2c instance system.adapter.discovery.0 terminated by request of the instance itself and will not be restarted, before user restarts it. 2020-11-09 23:15:52.468 - info: host.75749fbeed2c Do not restart adapter system.adapter.discovery.0 because desired by instance 2020-11-09 23:15:54.173 - info: host.75749fbeed2c instance system.adapter.info.0 started with pid 1536 2020-11-09 23:15:57.279 - error: info.0 (1536) info.0 invalid process id scenario 147 vs. own ID 1536. Stopping 2020-11-09 23:15:57.287 - info: info.0 (1536) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2020-11-09 23:15:57.810 - error: host.75749fbeed2c instance system.adapter.info.0 terminated by request of the instance itself and will not be restarted, before user restarts it. 2020-11-09 23:15:57.811 - info: host.75749fbeed2c Do not restart adapter system.adapter.info.0 because desired by instance 2020-11-09 23:28:18.050 - info: host.75749fbeed2c received SIGTERM 2020-11-09 23:28:18.055 - info: host.75749fbeed2c stopInstance system.adapter.admin.0 (force=false, process=false) 2020-11-09 23:28:18.056 - info: host.75749fbeed2c stopInstance system.adapter.discovery.0 (force=false, process=false) 2020-11-09 23:28:18.057 - info: host.75749fbeed2c stopInstance system.adapter.info.0 (force=false, process=false) 2020-11-09 23:28:24.059 - info: host.75749fbeed2c received SIGTERM 2020-11-09 23:28:24.061 - info: host.75749fbeed2c stopInstance system.adapter.admin.0 (force=false, process=false) 2020-11-09 23:28:24.061 - info: host.75749fbeed2c stopInstance system.adapter.discovery.0 (force=false, process=false) 2020-11-09 23:28:24.062 - info: host.75749fbeed2c stopInstance system.adapter.info.0 (force=false, process=false) 2020-11-09 23:28:30.064 - info: host.75749fbeed2c received SIGTERM 2020-11-09 23:28:30.066 - info: host.75749fbeed2c stopInstance system.adapter.admin.0 (force=false, process=false) 2020-11-09 23:28:30.067 - info: host.75749fbeed2c stopInstance system.adapter.discovery.0 (force=false, process=false) 2020-11-09 23:28:30.068 - info: host.75749fbeed2c stopInstance system.adapter.info.0 (force=false, process=false) 2020-11-09 23:28:33.066 - info: host.75749fbeed2c force terminating 2020-11-09 23:28:51.683 - info: info.0 (147) Popup news was read... 2020-11-09 23:30:23.664 - info: host.75749fbeed2c iobroker.js-controller version 3.1.6 js-controller starting 2020-11-09 23:30:23.673 - info: host.75749fbeed2c Copyright (c) 2014-2020 bluefox, 2014 hobbyquaker 2020-11-09 23:30:23.674 - info: host.75749fbeed2c hostname: 75749fbeed2c, node: v12.19.0 2020-11-09 23:30:23.677 - info: host.75749fbeed2c ip addresses: 172.17.0.3 2020-11-09 23:30:23.762 - info: host.75749fbeed2c Error inMem-objects listening on port 9001 2020-11-09 23:30:23.789 - info: host.75749fbeed2c Error inMem-states listening on port 9000 2020-11-09 23:30:23.907 - info: host.75749fbeed2c connected to Objects and States 2020-11-09 23:30:24.459 - info: host.75749fbeed2c 3 instances found 2020-11-09 23:30:24.496 - info: host.75749fbeed2c starting 3 instances 2020-11-09 23:30:24.535 - info: host.75749fbeed2c instance system.adapter.admin.0 started with pid 2379 2020-11-09 23:30:27.104 - error: admin.0 (2379) admin.0 invalid process id scenario 121 vs. own ID 2379. Stopping 2020-11-09 23:30:27.110 - info: admin.0 (2379) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2020-11-09 23:30:27.641 - error: host.75749fbeed2c instance system.adapter.admin.0 terminated by request of the instance itself and will not be restarted, before user restarts it. 2020-11-09 23:30:27.642 - info: host.75749fbeed2c Do not restart adapter system.adapter.admin.0 because desired by instance 2020-11-09 23:30:28.525 - info: host.75749fbeed2c instance system.adapter.discovery.0 started with pid 2402 2020-11-09 23:30:30.268 - error: discovery.0 (2402) discovery.0 invalid process id scenario 132 vs. own ID 2402. Stopping 2020-11-09 23:30:30.273 - info: discovery.0 (2402) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2020-11-09 23:30:30.804 - error: host.75749fbeed2c instance system.adapter.discovery.0 terminated by request of the instance itself and will not be restarted, before user restarts it. 2020-11-09 23:30:30.806 - info: host.75749fbeed2c Do not restart adapter system.adapter.discovery.0 because desired by instance 2020-11-09 23:30:32.527 - info: host.75749fbeed2c instance system.adapter.info.0 started with pid 2413 2020-11-09 23:30:35.716 - error: info.0 (2413) info.0 invalid process id scenario 147 vs. own ID 2413. Stopping 2020-11-09 23:30:35.722 - info: info.0 (2413) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2020-11-09 23:30:36.252 - error: host.75749fbeed2c instance system.adapter.info.0 terminated by request of the instance itself and will not be restarted, before user restarts it. 2020-11-09 23:30:36.253 - info: host.75749fbeed2c Do not restart adapter system.adapter.info.0 because desired by instance 2020-11-09 23:31:35.194 - info: host.75749fbeed2c iobroker.js-controller version 3.1.6 js-controller starting 2020-11-09 23:31:35.207 - info: host.75749fbeed2c Copyright (c) 2014-2020 bluefox, 2014 hobbyquaker 2020-11-09 23:31:35.209 - info: host.75749fbeed2c hostname: 75749fbeed2c, node: v12.19.0 2020-11-09 23:31:35.213 - info: host.75749fbeed2c ip addresses: 172.17.0.3 2020-11-09 23:31:35.297 - info: host.75749fbeed2c Error inMem-objects listening on port 9001 2020-11-09 23:31:35.327 - info: host.75749fbeed2c Error inMem-states listening on port 9000 2020-11-09 23:31:35.388 - info: host.75749fbeed2c connected to Objects and States 2020-11-09 23:31:35.934 - info: host.75749fbeed2c 3 instances found 2020-11-09 23:31:35.965 - info: host.75749fbeed2c starting 3 instances 2020-11-09 23:31:36.012 - info: host.75749fbeed2c instance system.adapter.admin.0 started with pid 2498 2020-11-09 23:31:38.618 - error: admin.0 (2498) admin.0 invalid process id scenario 121 vs. own ID 2498. Stopping 2020-11-09 23:31:38.624 - info: admin.0 (2498) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2020-11-09 23:31:39.155 - error: host.75749fbeed2c instance system.adapter.admin.0 terminated by request of the instance itself and will not be restarted, before user restarts it. 2020-11-09 23:31:39.157 - info: host.75749fbeed2c Do not restart adapter system.adapter.admin.0 because desired by instance 2020-11-09 23:31:39.993 - info: host.75749fbeed2c instance system.adapter.discovery.0 started with pid 2509 2020-11-09 23:31:41.767 - error: discovery.0 (2509) discovery.0 invalid process id scenario 132 vs. own ID 2509. Stopping 2020-11-09 23:31:41.773 - info: discovery.0 (2509) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2020-11-09 23:31:42.297 - error: host.75749fbeed2c instance system.adapter.discovery.0 terminated by request of the instance itself and will not be restarted, before user restarts it. 2020-11-09 23:31:42.298 - info: host.75749fbeed2c Do not restart adapter system.adapter.discovery.0 because desired by instance 2020-11-09 23:31:43.996 - info: host.75749fbeed2c instance system.adapter.info.0 started with pid 2520 2020-11-09 23:31:47.145 - error: info.0 (2520) info.0 invalid process id scenario 147 vs. own ID 2520. Stopping 2020-11-09 23:31:47.150 - info: info.0 (2520) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2020-11-09 23:31:47.699 - error: host.75749fbeed2c instance system.adapter.info.0 terminated by request of the instance itself and will not be restarted, before user restarts it. 2020-11-09 23:31:47.702 - info: host.75749fbeed2c Do not restart adapter system.adapter.info.0 because desired by instance root@75749fbeed2c:/opt/iobroker# -
@reimai loxberry? Das sind doch die Typen die total verfrickelte Grundinstallationen in ihrem System haben und das auch noch super finden?
iobroker sollte jedenfalls nicht als root laufen, sondern als eigener user. Ich weiß, die Loxberry-Heinis finden das zu kompliziert. Das lässt allerdings tief blicken. -
@Thomas-Braun Loxberry hat es für mich ermöglich ein paar Plugins zum installieren und mit Loxone leicht zu verbinden. Was dahinter steckt weiß ich nicht. Aber ich hab letzte Woche es geschafft über FHEM Plugin meine Samsung Klimaanlage über MQTT Gateway Plugin auf Loxone laufen zu lassen. Jetzt möchte ich gerne Daten von meinen E Golf in Loxone zu bekommen aber ich schaffe es nicht das Interface zu bekommen. Vielleicht kannst Du mir da helfen?
-
@reimai Ich kapier schon nicht den komischen Ansatz mit dem iobroker als Docker.
-
Möchte das Laufen lassen link text
-
@reimai
Ich würde da ja ioBroker autark laufen lassen. Einen. Adapter für loxone gibt es ja.Loxberry ist 'broken by design', meiner Meinung nach.
-
Muss ich da einen neuen Rasberry kaufen? Siehst Du da keine Möglichkeit das zum laufen zu bekommen?
-
@reimai Alles strubbelig, wenn das auf dem windigen loxberry auf setzen soll. Wofür brauchst du das überhaupt?
-
Wie oben beschrieben FHEM, MQTT Gateway, Wetterdaten, Samsung Klimagerät
-
@reimai Und über ein System geht das nicht? Müsste auch alles über den ioBroker machbar sein.
-
Ich würde es gerne mit dem Loxberry probieren und dem Docker Plugin. Wenn es nicht geht kaufe ich nochmal einen neuen Rasberry und gebe dann nur den IoBroker drauf.
-
@reimai Du baust dir da ein System from hell zusammen.
-
Ich brauche nur noch mein Elektroauto in Loxone drinnen, dann wäre ich schon zufrieden. Wenns nicht geht wie gesagt dann ein Neuer Pie
-
@Thomas-Braun sagte in IoBroker über Webinterface nicht erreichbar (Frage):
@reimai Du baust dir da ein System from hell zusammen.
Da muss ich jetzt mal deutlich widersprechen! Nur weil die Lernkurve bei Docker etwas steiler ist, heisst das nicht, dass es nicht eine gute Lösung für ioBroker ist. Bei mir laufen vier produktive Instanzen von ioBroker in Docker (respektive Balena, was auch Docker ist) je auf einem Raspi.
Die Idee von @reimai ist super: wenn du Dinge sauber trennen willst (und das macht bei Loxberry scheinbar Sinn), ist Docker die perfekte Lösung. Versuche ja nicht mehrere Applikationen auf einem Raspi zum laufen zu bringen, die unterschiedliche Abhängigkeiten haben, die sich vielleicht sogar in die Quere kommen. Das gibt dann ein "System from Hell".
@reimai Nun zu deinem Problem: du musst dich entscheiden, ob du Host Network willst oder nicht: soll der Container (und damit ioBroker) nur über den Admin Port erreichbar sein und in seinem eigenen Netzwerk leben oder soll er auf das Netzwerk des Raspi zugreifen können (kann sinnvoll sein, wenn du spezielle Adapter brauchst). Im Normalfall genügt es, die Portfreigabe zu konfigurieren (das kannst du auch in Portainer machen) - von selbst wird nämlich Port 8081 nicht freigegeben. Wie die Kommandozeile korrekt aussieht, findest du hier: https://github.com/buanet/docker-iobroker#running-from-command-line (die Portainer Konfiguration kannst du davon ableiten).
-
Bei mir laufen vier produktive Instanzen von ioBroker in Docker (respektive Balena, was auch Docker ist) je auf einem Raspi.
Kann man ja machen. Aber nicht auf einem System basierend, das aus Bequemlichkeit (oder Ahnungslosigkeit /Unfähigkeit) auf die Trennung von root / user verzichtet, wie es loxberry in ihren Images anlegt. Wenn ich das Zeug einsetzen müsste, dann würde ich den windigen Kram wegkapseln.
Und eigentlich vermute ich, dass man die ganze Konstruktion auch in einem ioBroker abbilden könnte, ohne loxberry und dann da noch irgendwelche Klamotten aus FHEM reinzuziehen und zu guter Letzt dann auch noch einen ioBroker anzudocken.
Aber jeder wie er meint.
-
@UncleSam sagte in IoBroker über Webinterface nicht erreichbar (Frage):
Die Idee von @reimai ist super: wenn du Dinge sauber trennen willst (und das macht bei Loxberry scheinbar Sinn), ist Docker die perfekte Lösung.
aber doch nicht auf 1GB RAM!
- ioBroker
- Loxone
- Docker
- X-irgendwas
- ....
-
@Homoran sagte in IoBroker über Webinterface nicht erreichbar (Frage):
aber doch nicht auf 1GB RAM!
Klar muss man das im Griff haben, aber ist absolut machbar. Docker selber braucht kaum RAM und dann kommt es nicht zuletzt auf die Anzahl Adapter an, die in ioBroker laufen (und ob man evtl Compact Mode verwendet).
Vier meiner Raspis sind 3b, nur einer ein 4b.
Beruflich hatten wir auf einem Raspi 3 sieben Container am laufen, zwei davon .NET Core Applikationen und auch eine NoSQL Datenbank. Es lief (inklusive zeitkritischer Echtzeit Kommunikation mit Hardware) einwandfrei.
Aber ja: Docker aus "Faulheit" zu verwenden wäre definitv falsch, dafür ist es doch zu komplex.
-
@UncleSam
Nur weil es machbar ist, ist es noch lange nicht gut und der Pi3 war bei mir mit IOBroker alleine schon nahe an seiner Grenze mit 1GB RAM
-
Ich habe es jetzt hinbekommen. Das Problem war wie oben von @UncleSam schon erklärt wurde, die Portweiterleitung. Habe jetzt eine IP Adresse über macvlan vergeben. Es gibt eine super Anleitung hier. link text link text
Das ganze läuft über Loxberry. So jetzt gehts an die Adapter.
Danke nochmals für Eure Hilfe und Informationen
