NEWS
gelöst: ioBroker startet nicht mehr
Installation
55
Beiträge
6
Kommentatoren
5.8k
Aufrufe
6
Watching
-
Seit gestern habe ich das Problem, dass ioBroker nach einem Reboot des Hosts (Debian-Installation im Proxmox CT) nicht mehr von alleine startet.
Meine Konfig:
Plattform: linux Betriebssystem: linux Architektur: x64 CPUs: 2 Geschwindigkeit: 3169 MHz Modell: Intel(R) Core(TM) i5-6600T CPU @ 2.70GHz RAM: 8 GB System-Betriebszeit: 00:08:00 Node.js: v18.17.0 time: 1690558665263 timeOffset: -120 Adapter-Anzahl: 484 NPM: v9.6.7 Datenträgergröße: 7.8 GB Freier Festplattenspeicher: 4.2 GB Betriebszeit: 00:04:10 Aktive Instanzen: 22 Pfad: /opt/iobroker/ aktiv:Ich kann normal auf die Konsole, die Abfrage "iobroker status" bringt nur Folgendes:
root@iobroker:~# iobroker status node: OpenSSL configuration error: C0070E31147F0000:error:8000000D:system library:BIO_new_file:Permission denied:../deps/openssl/openssl/crypto/bio/bss_file.c:67:calling fopen(/etc/ssl/openssl.cnf, rb)Folgende Dienste (?) laufen:
root@iobroker:~# ps -A PID TTY TIME CMD 1 ? 00:00:00 systemd 50 ? 00:00:00 systemd-journal 89 ? 00:00:00 systemd-network 107 ? 00:00:00 rpcbind 115 ? 00:00:00 dbus-daemon 119 ? 00:00:00 systemd-logind 120 ? 00:00:00 cron 130 pts/0 00:00:00 agetty 131 pts/1 00:00:00 login 132 pts/2 00:00:00 agetty 137 ? 00:00:00 sshd 284 ? 00:00:00 master 285 ? 00:00:00 pickup 286 ? 00:00:00 qmgr 297 pts/1 00:00:00 bash 343 pts/1 00:00:00 psDer Befehl "iobroker start" bleibt ohne Reaktion. Wenn ich "node node_modules/iobroker.js-controller/controller.js --logs" eingebe, kommt folgendes und ioBroker ist nach kurzer Zeit übers Web-Interface erreichbar:
root@iobroker:/opt/iobroker# node node_modules/iobroker.js-controller/controller.js --logs 2023-07-28 17:33:35.634 - info: host.iobroker iobroker.js-controller version 4.0.24 js-controller starting 2023-07-28 17:33:35.636 - info: host.iobroker Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-07-28 17:33:35.636 - info: host.iobroker hostname: iobroker, node: v18.17.0 2023-07-28 17:33:35.637 - info: host.iobroker ip addresses: 192.168.0.205 fe80::b819:b1ff:fe68:233d 2023-07-28 17:33:36.431 - info: host.iobroker connected to Objects and States 2023-07-28 17:33:36.447 - info: host.iobroker added notifications configuration of host ================================== > LOG REDIRECT system.adapter.admin.0 => true [starting] 2023-07-28 17:33:36.812 - info: host.iobroker Delete state "system.host.iobroker.versions.nodeCurrent" 2023-07-28 17:33:36.813 - info: host.iobroker 25 instances found host.iobroker check instance "system.adapter.admin.0" for host "iobroker" host.iobroker check instance "system.adapter.javascript.0" for host "iobroker" host.iobroker check instance "system.adapter.influxdb.0" for host "iobroker" host.iobroker check instance "system.adapter.pushover.0" for host "iobroker" host.iobroker check instance "system.adapter.synology.0" for host "iobroker" host.iobroker check instance "system.adapter.alexa2.0" for host "iobroker" host.iobroker check instance "system.adapter.meross.0" for host "iobroker" host.iobroker check instance "system.adapter.mqtt.0" for host "iobroker" host.iobroker check instance "system.adapter.shelly.0" for host "iobroker" host.iobroker check instance "system.adapter.sonoff.0" for host "iobroker" host.iobroker check instance "system.adapter.tuya.0" for host "iobroker" host.iobroker check instance "system.adapter.tr-064.0" for host "iobroker" host.iobroker check instance "system.adapter.nut.0" for host "iobroker" host.iobroker check instance "system.adapter.discovery.0" for host "iobroker" host.iobroker check instance "system.adapter.backitup.0" for host "iobroker" host.iobroker check instance "system.adapter.web.0" for host "iobroker" host.iobroker check instance "system.adapter.vis.0" for host "iobroker" host.iobroker check instance "system.adapter.iot.0" for host "iobroker" host.iobroker check instance "system.adapter.cloud.0" for host "iobroker" host.iobroker check instance "system.adapter.net-tools.0" for host "iobroker" host.iobroker check instance "system.adapter.fritzdect.0" for host "iobroker" host.iobroker check instance "system.adapter.sourceanalytix.0" for host "iobroker" host.iobroker check instance "system.adapter.energiefluss.0" for host "iobroker" host.iobroker check instance "system.adapter.echarts.0" for host "iobroker" 2023-07-28 17:33:36.825 - info: host.iobroker starting 23 instances 2023-07-28 17:33:36.849 - info: host.iobroker Delete state "system.host.iobroker.versions.nodeNewest" 2023-07-28 17:33:36.905 - info: host.iobroker instance system.adapter.admin.0 started with pid 474 2023-07-28 17:33:36.908 - info: host.iobroker Delete state "system.host.iobroker.versions.nodeNewestNext" 2023-07-28 17:33:36.952 - info: host.iobroker Delete state "system.host.iobroker.versions.npmCurrent" 2023-07-28 17:33:36.996 - info: host.iobroker Delete state "system.host.iobroker.versions.npmNewest" 2023-07-28 17:33:37.044 - info: host.iobroker Delete state "system.host.iobroker.versions.npmNewestNext" 2023-07-28 17:33:37.088 - info: host.iobroker Some obsolete host states deleted. ================================== > LOG REDIRECT system.adapter.admin.0 => false [Process stopped] 2023-07-28 17:33:38.050 - error: host.iobroker instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:33:38.050 - info: host.iobroker Restart adapter system.adapter.admin.0 because enabled ================================== > LOG REDIRECT system.adapter.admin.0 => false [system.adapter.admin.0.logging] 2023-07-28 17:33:40.853 - info: host.iobroker instance system.adapter.javascript.0 started with pid 489 ================================== > LOG REDIRECT system.adapter.javascript.0 => false [Process stopped] 2023-07-28 17:33:42.309 - error: host.iobroker instance system.adapter.javascript.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:33:42.309 - info: host.iobroker Restart adapter system.adapter.javascript.0 because enabled ================================== > LOG REDIRECT system.adapter.javascript.0 => false [system.adapter.javascript.0.logging] 2023-07-28 17:33:44.854 - info: host.iobroker instance system.adapter.influxdb.0 started with pid 502 2023-07-28 17:33:45.964 - error: host.iobroker instance system.adapter.influxdb.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:33:45.964 - info: host.iobroker Restart adapter system.adapter.influxdb.0 because enabled 2023-07-28 17:33:48.853 - info: host.iobroker instance system.adapter.pushover.0 started with pid 515 2023-07-28 17:33:49.872 - error: host.iobroker instance system.adapter.pushover.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:33:49.872 - info: host.iobroker Restart adapter system.adapter.pushover.0 because enabled 2023-07-28 17:33:52.854 - info: host.iobroker instance system.adapter.alexa2.0 started with pid 528 2023-07-28 17:33:53.894 - error: host.iobroker instance system.adapter.alexa2.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:33:53.894 - info: host.iobroker Restart adapter system.adapter.alexa2.0 because enabled 2023-07-28 17:33:56.853 - info: host.iobroker instance system.adapter.meross.0 started with pid 541 2023-07-28 17:33:58.040 - error: host.iobroker instance system.adapter.meross.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:33:58.040 - info: host.iobroker Restart adapter system.adapter.meross.0 because enabled 2023-07-28 17:34:00.855 - info: host.iobroker instance system.adapter.mqtt.0 started with pid 556 2023-07-28 17:34:01.843 - error: host.iobroker instance system.adapter.mqtt.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:34:01.844 - info: host.iobroker Restart adapter system.adapter.mqtt.0 because enabled 2023-07-28 17:34:04.855 - info: host.iobroker instance system.adapter.shelly.0 started with pid 569 2023-07-28 17:34:06.008 - error: host.iobroker instance system.adapter.shelly.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:34:06.008 - info: host.iobroker Restart adapter system.adapter.shelly.0 because enabled 2023-07-28 17:34:08.074 - info: host.iobroker instance system.adapter.admin.0 started with pid 582 2023-07-28 17:34:08.854 - info: host.iobroker instance system.adapter.sonoff.0 started with pid 597 Send diag info: {"uuid":"85d8f1fb-160c-b65c-6b05-8a392268bcae","language":"de","country":"Germany","hosts":[{"version":"4.0.24","platform":"Javascript/Node.js","type":"linux"}],"node":"v18.17.0","arch":"x64","docker":false,"adapters":{"admin":{"version":"6.3.5","platform":"Javascript/Node.js"},"discovery":{"version":"3.1.0","platform":"Javascript/Node.js"},"backitup":{"version":"2.6.23","platform":"Javascript/Node.js"},"synology":{"version":"2.1.13","platform":"Javascript/Node.js"},"web":{"version":"4.3.0","platform":"Javascript/Node.js"},"history":{"version":"2.2.4","platform":"Javascript/Node.js"},"javascript":{"version":"7.0.3","platform":"Javascript/Node.js"},"vis":{"version":"1.4.16","platform":"Javascript/Node.js"},"alexa2":{"version":"3.23.2","platform":"Javascript/Node.js"},"alias-manager":{"version":"1.2.4","platform":"Javascript/Node.js"},"apcups":{"version":"1.0.15","platform":"Javascript/Node.js"},"iot":{"version":"1.14.5","platform":"Javascript/Node.js"},"cloud":{"version":"4.4.1","platform":"Javascript/Node.js"},"influxdb":{"version":"3.2.0","platform":"Javascript/Node.js"},"meross":{"version":"1.15.1","platform":"Javascript/Node.js"},"mqtt":{"version":"4.1.1","platform":"Javascript/Node.js"},"net-tools":{"version":"0.2.0","platform":"Javascript/Node.js"},"pushover":{"version":"3.0.3","platform":"Javascript/Node.js"},"shelly":{"version":"6.4.1","platform":"Javascript/Node.js"},"sonoff":{"version":"2.5.3","platform":"Javascript/Node.js"},"tuya":{"version":"3.14.2","platform":"Javascript/Node.js"},"fritzdect":{"version":"2.3.1","platform":"Javascript/Node.js"},"tr-064":{"version":"4.2.18","platform":"Javascript/Node.js"},"nut":{"version":"1.6.0","platform":"Javascript/Node.js"},"sourceanalytix":{"version":"0.4.14","platform":"Javascript/Node.js"},"energiefluss":{"version":"3.6.0","platform":"Javascript/Node.js"},"echarts":{"version":"1.5.1","platform":"Javascript/Node.js"}},"statesType":"jsonl","objectsType":"jsonl","noInstances":25,"compactMode":false,"noCompactInstances":0,"model":"Intel(R) Core(TM) i5-6600T CPU @ 2.70GHz","cpus":2,"mem":8589934592,"ostype":"Linux","city":"xxx","vis":6} 2023-07-28 17:34:10.121 - info: host.iobroker Updating repository "stable" under "http://download.iobroker.net/sources-dist.json" 2023-07-28 17:34:10.203 - error: host.iobroker instance system.adapter.sonoff.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:34:10.203 - info: host.iobroker Restart adapter system.adapter.sonoff.0 because enabled 2023-07-28 17:34:12.341 - info: host.iobroker instance system.adapter.javascript.0 started with pid 622 2023-07-28 17:34:12.876 - info: host.iobroker instance system.adapter.tuya.0 started with pid 629 2023-07-28 17:34:14.273 - error: host.iobroker instance system.adapter.tuya.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:34:14.273 - info: host.iobroker Restart adapter system.adapter.tuya.0 because enabled 2023-07-28 17:34:15.998 - info: host.iobroker instance system.adapter.influxdb.0 started with pid 650 2023-07-28 17:34:16.865 - info: host.iobroker instance system.adapter.tr-064.0 started with pid 667 2023-07-28 17:34:18.026 - error: host.iobroker instance system.adapter.tr-064.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:34:18.027 - info: host.iobroker Restart adapter system.adapter.tr-064.0 because enabled 2023-07-28 17:34:19.907 - info: host.iobroker instance system.adapter.pushover.0 started with pid 680 2023-07-28 17:34:20.863 - info: host.iobroker instance system.adapter.nut.0 started with pid 695 2023-07-28 17:34:21.856 - error: host.iobroker instance system.adapter.nut.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:34:21.856 - info: host.iobroker Restart adapter system.adapter.nut.0 because enabled 2023-07-28 17:34:23.929 - info: host.iobroker instance system.adapter.alexa2.0 started with pid 708 2023-07-28 17:34:24.866 - info: host.iobroker instance system.adapter.discovery.0 started with pid 723 2023-07-28 17:34:25.867 - error: host.iobroker instance system.adapter.discovery.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:34:25.868 - info: host.iobroker Restart adapter system.adapter.discovery.0 because enabled 2023-07-28 17:34:27.701 - info: host.iobroker stopInstance system.adapter.alexa2.0 (force=false, process=true) 2023-07-28 17:34:27.703 - info: host.iobroker stopInstance system.adapter.alexa2.0 send kill signal 2023-07-28 17:34:28.078 - info: host.iobroker instance system.adapter.meross.0 started with pid 736 2023-07-28 17:34:28.242 - info: host.iobroker instance system.adapter.alexa2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-07-28 17:34:28.868 - info: host.iobroker instance system.adapter.backitup.0 started with pid 747 2023-07-28 17:34:29.977 - error: host.iobroker instance system.adapter.backitup.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:34:29.977 - info: host.iobroker Restart adapter system.adapter.backitup.0 because enabled 2023-07-28 17:34:30.740 - info: host.iobroker instance system.adapter.alexa2.0 started with pid 764 2023-07-28 17:34:31.880 - info: host.iobroker instance system.adapter.mqtt.0 started with pid 779 2023-07-28 17:34:32.867 - info: host.iobroker instance system.adapter.web.0 started with pid 796 2023-07-28 17:34:33.959 - error: host.iobroker instance system.adapter.web.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:34:33.959 - info: host.iobroker Restart adapter system.adapter.web.0 because enabled 2023-07-28 17:34:36.046 - info: host.iobroker instance system.adapter.shelly.0 started with pid 809 2023-07-28 17:34:38.925 - info: host.iobroker instance system.adapter.vis.0 terminated while should be started once 2023-07-28 17:34:40.237 - info: host.iobroker instance system.adapter.sonoff.0 started with pid 841 2023-07-28 17:34:40.885 - info: host.iobroker instance system.adapter.iot.0 started with pid 852 ================================== > LOG REDIRECT system.adapter.iot.0 => false [Process stopped] 2023-07-28 17:34:42.165 - error: host.iobroker instance system.adapter.iot.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:34:42.165 - info: host.iobroker Restart adapter system.adapter.iot.0 because enabled ================================== > LOG REDIRECT system.adapter.iot.0 => false [system.adapter.iot.0.logging] 2023-07-28 17:34:44.308 - info: host.iobroker instance system.adapter.tuya.0 started with pid 869 2023-07-28 17:34:44.873 - info: host.iobroker instance system.adapter.cloud.0 started with pid 880 ================================== > LOG REDIRECT system.adapter.cloud.0 => false [Process stopped] 2023-07-28 17:34:46.076 - error: host.iobroker instance system.adapter.cloud.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:34:46.076 - info: host.iobroker Restart adapter system.adapter.cloud.0 because enabled ================================== > LOG REDIRECT system.adapter.cloud.0 => false [system.adapter.cloud.0.logging] 2023-07-28 17:34:48.061 - info: host.iobroker instance system.adapter.tr-064.0 started with pid 899 2023-07-28 17:34:48.865 - info: host.iobroker instance system.adapter.net-tools.0 started with pid 910 2023-07-28 17:34:50.052 - error: host.iobroker instance system.adapter.net-tools.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:34:50.052 - info: host.iobroker Restart adapter system.adapter.net-tools.0 because enabled 2023-07-28 17:34:51.891 - info: host.iobroker instance system.adapter.nut.0 started with pid 927 2023-07-28 17:34:52.867 - info: host.iobroker instance system.adapter.fritzdect.0 started with pid 944 2023-07-28 17:34:53.952 - error: host.iobroker instance system.adapter.fritzdect.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:34:53.952 - info: host.iobroker Restart adapter system.adapter.fritzdect.0 because enabled 2023-07-28 17:34:55.905 - info: host.iobroker instance system.adapter.discovery.0 started with pid 957 2023-07-28 17:34:56.863 - info: host.iobroker instance system.adapter.sourceanalytix.0 started with pid 972 2023-07-28 17:34:57.873 - error: host.iobroker instance system.adapter.sourceanalytix.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:34:57.873 - info: host.iobroker Restart adapter system.adapter.sourceanalytix.0 because enabled 2023-07-28 17:35:00.016 - info: host.iobroker instance system.adapter.backitup.0 started with pid 985 2023-07-28 17:35:00.891 - info: host.iobroker instance system.adapter.energiefluss.0 started with pid 996 2023-07-28 17:35:02.024 - error: host.iobroker instance system.adapter.energiefluss.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:35:02.024 - info: host.iobroker Restart adapter system.adapter.energiefluss.0 because enabled 2023-07-28 17:35:03.993 - info: host.iobroker instance system.adapter.web.0 started with pid 1013 2023-07-28 17:35:04.857 - info: host.iobroker instance system.adapter.echarts.0 started with pid 1024 2023-07-28 17:35:06.015 - error: host.iobroker instance system.adapter.echarts.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:35:06.015 - info: host.iobroker Restart adapter system.adapter.echarts.0 because enabled 2023-07-28 17:35:12.200 - info: host.iobroker instance system.adapter.iot.0 started with pid 1045 2023-07-28 17:35:16.106 - info: host.iobroker instance system.adapter.cloud.0 started with pid 1062 2023-07-28 17:35:20.105 - info: host.iobroker instance system.adapter.net-tools.0 started with pid 1079 2023-07-28 17:35:23.981 - info: host.iobroker instance system.adapter.fritzdect.0 started with pid 1099 2023-07-28 17:35:27.901 - info: host.iobroker instance system.adapter.sourceanalytix.0 started with pid 1116 2023-07-28 17:35:32.051 - info: host.iobroker instance system.adapter.energiefluss.0 started with pid 1135 2023-07-28 17:35:36.034 - info: host.iobroker instance system.adapter.echarts.0 started with pid 1152Die Konsole bleibt aber irgendwie tot:
Was kann ich machen, damit a) mein ioBroker nach einem Neustart der Maschine wieder normal anspringt?
-
Seit gestern habe ich das Problem, dass ioBroker nach einem Reboot des Hosts (Debian-Installation im Proxmox CT) nicht mehr von alleine startet.
Meine Konfig:
Plattform: linux Betriebssystem: linux Architektur: x64 CPUs: 2 Geschwindigkeit: 3169 MHz Modell: Intel(R) Core(TM) i5-6600T CPU @ 2.70GHz RAM: 8 GB System-Betriebszeit: 00:08:00 Node.js: v18.17.0 time: 1690558665263 timeOffset: -120 Adapter-Anzahl: 484 NPM: v9.6.7 Datenträgergröße: 7.8 GB Freier Festplattenspeicher: 4.2 GB Betriebszeit: 00:04:10 Aktive Instanzen: 22 Pfad: /opt/iobroker/ aktiv:Ich kann normal auf die Konsole, die Abfrage "iobroker status" bringt nur Folgendes:
root@iobroker:~# iobroker status node: OpenSSL configuration error: C0070E31147F0000:error:8000000D:system library:BIO_new_file:Permission denied:../deps/openssl/openssl/crypto/bio/bss_file.c:67:calling fopen(/etc/ssl/openssl.cnf, rb)Folgende Dienste (?) laufen:
root@iobroker:~# ps -A PID TTY TIME CMD 1 ? 00:00:00 systemd 50 ? 00:00:00 systemd-journal 89 ? 00:00:00 systemd-network 107 ? 00:00:00 rpcbind 115 ? 00:00:00 dbus-daemon 119 ? 00:00:00 systemd-logind 120 ? 00:00:00 cron 130 pts/0 00:00:00 agetty 131 pts/1 00:00:00 login 132 pts/2 00:00:00 agetty 137 ? 00:00:00 sshd 284 ? 00:00:00 master 285 ? 00:00:00 pickup 286 ? 00:00:00 qmgr 297 pts/1 00:00:00 bash 343 pts/1 00:00:00 psDer Befehl "iobroker start" bleibt ohne Reaktion. Wenn ich "node node_modules/iobroker.js-controller/controller.js --logs" eingebe, kommt folgendes und ioBroker ist nach kurzer Zeit übers Web-Interface erreichbar:
root@iobroker:/opt/iobroker# node node_modules/iobroker.js-controller/controller.js --logs 2023-07-28 17:33:35.634 - info: host.iobroker iobroker.js-controller version 4.0.24 js-controller starting 2023-07-28 17:33:35.636 - info: host.iobroker Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-07-28 17:33:35.636 - info: host.iobroker hostname: iobroker, node: v18.17.0 2023-07-28 17:33:35.637 - info: host.iobroker ip addresses: 192.168.0.205 fe80::b819:b1ff:fe68:233d 2023-07-28 17:33:36.431 - info: host.iobroker connected to Objects and States 2023-07-28 17:33:36.447 - info: host.iobroker added notifications configuration of host ================================== > LOG REDIRECT system.adapter.admin.0 => true [starting] 2023-07-28 17:33:36.812 - info: host.iobroker Delete state "system.host.iobroker.versions.nodeCurrent" 2023-07-28 17:33:36.813 - info: host.iobroker 25 instances found host.iobroker check instance "system.adapter.admin.0" for host "iobroker" host.iobroker check instance "system.adapter.javascript.0" for host "iobroker" host.iobroker check instance "system.adapter.influxdb.0" for host "iobroker" host.iobroker check instance "system.adapter.pushover.0" for host "iobroker" host.iobroker check instance "system.adapter.synology.0" for host "iobroker" host.iobroker check instance "system.adapter.alexa2.0" for host "iobroker" host.iobroker check instance "system.adapter.meross.0" for host "iobroker" host.iobroker check instance "system.adapter.mqtt.0" for host "iobroker" host.iobroker check instance "system.adapter.shelly.0" for host "iobroker" host.iobroker check instance "system.adapter.sonoff.0" for host "iobroker" host.iobroker check instance "system.adapter.tuya.0" for host "iobroker" host.iobroker check instance "system.adapter.tr-064.0" for host "iobroker" host.iobroker check instance "system.adapter.nut.0" for host "iobroker" host.iobroker check instance "system.adapter.discovery.0" for host "iobroker" host.iobroker check instance "system.adapter.backitup.0" for host "iobroker" host.iobroker check instance "system.adapter.web.0" for host "iobroker" host.iobroker check instance "system.adapter.vis.0" for host "iobroker" host.iobroker check instance "system.adapter.iot.0" for host "iobroker" host.iobroker check instance "system.adapter.cloud.0" for host "iobroker" host.iobroker check instance "system.adapter.net-tools.0" for host "iobroker" host.iobroker check instance "system.adapter.fritzdect.0" for host "iobroker" host.iobroker check instance "system.adapter.sourceanalytix.0" for host "iobroker" host.iobroker check instance "system.adapter.energiefluss.0" for host "iobroker" host.iobroker check instance "system.adapter.echarts.0" for host "iobroker" 2023-07-28 17:33:36.825 - info: host.iobroker starting 23 instances 2023-07-28 17:33:36.849 - info: host.iobroker Delete state "system.host.iobroker.versions.nodeNewest" 2023-07-28 17:33:36.905 - info: host.iobroker instance system.adapter.admin.0 started with pid 474 2023-07-28 17:33:36.908 - info: host.iobroker Delete state "system.host.iobroker.versions.nodeNewestNext" 2023-07-28 17:33:36.952 - info: host.iobroker Delete state "system.host.iobroker.versions.npmCurrent" 2023-07-28 17:33:36.996 - info: host.iobroker Delete state "system.host.iobroker.versions.npmNewest" 2023-07-28 17:33:37.044 - info: host.iobroker Delete state "system.host.iobroker.versions.npmNewestNext" 2023-07-28 17:33:37.088 - info: host.iobroker Some obsolete host states deleted. ================================== > LOG REDIRECT system.adapter.admin.0 => false [Process stopped] 2023-07-28 17:33:38.050 - error: host.iobroker instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:33:38.050 - info: host.iobroker Restart adapter system.adapter.admin.0 because enabled ================================== > LOG REDIRECT system.adapter.admin.0 => false [system.adapter.admin.0.logging] 2023-07-28 17:33:40.853 - info: host.iobroker instance system.adapter.javascript.0 started with pid 489 ================================== > LOG REDIRECT system.adapter.javascript.0 => false [Process stopped] 2023-07-28 17:33:42.309 - error: host.iobroker instance system.adapter.javascript.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:33:42.309 - info: host.iobroker Restart adapter system.adapter.javascript.0 because enabled ================================== > LOG REDIRECT system.adapter.javascript.0 => false [system.adapter.javascript.0.logging] 2023-07-28 17:33:44.854 - info: host.iobroker instance system.adapter.influxdb.0 started with pid 502 2023-07-28 17:33:45.964 - error: host.iobroker instance system.adapter.influxdb.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:33:45.964 - info: host.iobroker Restart adapter system.adapter.influxdb.0 because enabled 2023-07-28 17:33:48.853 - info: host.iobroker instance system.adapter.pushover.0 started with pid 515 2023-07-28 17:33:49.872 - error: host.iobroker instance system.adapter.pushover.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:33:49.872 - info: host.iobroker Restart adapter system.adapter.pushover.0 because enabled 2023-07-28 17:33:52.854 - info: host.iobroker instance system.adapter.alexa2.0 started with pid 528 2023-07-28 17:33:53.894 - error: host.iobroker instance system.adapter.alexa2.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:33:53.894 - info: host.iobroker Restart adapter system.adapter.alexa2.0 because enabled 2023-07-28 17:33:56.853 - info: host.iobroker instance system.adapter.meross.0 started with pid 541 2023-07-28 17:33:58.040 - error: host.iobroker instance system.adapter.meross.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:33:58.040 - info: host.iobroker Restart adapter system.adapter.meross.0 because enabled 2023-07-28 17:34:00.855 - info: host.iobroker instance system.adapter.mqtt.0 started with pid 556 2023-07-28 17:34:01.843 - error: host.iobroker instance system.adapter.mqtt.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:34:01.844 - info: host.iobroker Restart adapter system.adapter.mqtt.0 because enabled 2023-07-28 17:34:04.855 - info: host.iobroker instance system.adapter.shelly.0 started with pid 569 2023-07-28 17:34:06.008 - error: host.iobroker instance system.adapter.shelly.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:34:06.008 - info: host.iobroker Restart adapter system.adapter.shelly.0 because enabled 2023-07-28 17:34:08.074 - info: host.iobroker instance system.adapter.admin.0 started with pid 582 2023-07-28 17:34:08.854 - info: host.iobroker instance system.adapter.sonoff.0 started with pid 597 Send diag info: {"uuid":"85d8f1fb-160c-b65c-6b05-8a392268bcae","language":"de","country":"Germany","hosts":[{"version":"4.0.24","platform":"Javascript/Node.js","type":"linux"}],"node":"v18.17.0","arch":"x64","docker":false,"adapters":{"admin":{"version":"6.3.5","platform":"Javascript/Node.js"},"discovery":{"version":"3.1.0","platform":"Javascript/Node.js"},"backitup":{"version":"2.6.23","platform":"Javascript/Node.js"},"synology":{"version":"2.1.13","platform":"Javascript/Node.js"},"web":{"version":"4.3.0","platform":"Javascript/Node.js"},"history":{"version":"2.2.4","platform":"Javascript/Node.js"},"javascript":{"version":"7.0.3","platform":"Javascript/Node.js"},"vis":{"version":"1.4.16","platform":"Javascript/Node.js"},"alexa2":{"version":"3.23.2","platform":"Javascript/Node.js"},"alias-manager":{"version":"1.2.4","platform":"Javascript/Node.js"},"apcups":{"version":"1.0.15","platform":"Javascript/Node.js"},"iot":{"version":"1.14.5","platform":"Javascript/Node.js"},"cloud":{"version":"4.4.1","platform":"Javascript/Node.js"},"influxdb":{"version":"3.2.0","platform":"Javascript/Node.js"},"meross":{"version":"1.15.1","platform":"Javascript/Node.js"},"mqtt":{"version":"4.1.1","platform":"Javascript/Node.js"},"net-tools":{"version":"0.2.0","platform":"Javascript/Node.js"},"pushover":{"version":"3.0.3","platform":"Javascript/Node.js"},"shelly":{"version":"6.4.1","platform":"Javascript/Node.js"},"sonoff":{"version":"2.5.3","platform":"Javascript/Node.js"},"tuya":{"version":"3.14.2","platform":"Javascript/Node.js"},"fritzdect":{"version":"2.3.1","platform":"Javascript/Node.js"},"tr-064":{"version":"4.2.18","platform":"Javascript/Node.js"},"nut":{"version":"1.6.0","platform":"Javascript/Node.js"},"sourceanalytix":{"version":"0.4.14","platform":"Javascript/Node.js"},"energiefluss":{"version":"3.6.0","platform":"Javascript/Node.js"},"echarts":{"version":"1.5.1","platform":"Javascript/Node.js"}},"statesType":"jsonl","objectsType":"jsonl","noInstances":25,"compactMode":false,"noCompactInstances":0,"model":"Intel(R) Core(TM) i5-6600T CPU @ 2.70GHz","cpus":2,"mem":8589934592,"ostype":"Linux","city":"xxx","vis":6} 2023-07-28 17:34:10.121 - info: host.iobroker Updating repository "stable" under "http://download.iobroker.net/sources-dist.json" 2023-07-28 17:34:10.203 - error: host.iobroker instance system.adapter.sonoff.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:34:10.203 - info: host.iobroker Restart adapter system.adapter.sonoff.0 because enabled 2023-07-28 17:34:12.341 - info: host.iobroker instance system.adapter.javascript.0 started with pid 622 2023-07-28 17:34:12.876 - info: host.iobroker instance system.adapter.tuya.0 started with pid 629 2023-07-28 17:34:14.273 - error: host.iobroker instance system.adapter.tuya.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:34:14.273 - info: host.iobroker Restart adapter system.adapter.tuya.0 because enabled 2023-07-28 17:34:15.998 - info: host.iobroker instance system.adapter.influxdb.0 started with pid 650 2023-07-28 17:34:16.865 - info: host.iobroker instance system.adapter.tr-064.0 started with pid 667 2023-07-28 17:34:18.026 - error: host.iobroker instance system.adapter.tr-064.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:34:18.027 - info: host.iobroker Restart adapter system.adapter.tr-064.0 because enabled 2023-07-28 17:34:19.907 - info: host.iobroker instance system.adapter.pushover.0 started with pid 680 2023-07-28 17:34:20.863 - info: host.iobroker instance system.adapter.nut.0 started with pid 695 2023-07-28 17:34:21.856 - error: host.iobroker instance system.adapter.nut.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:34:21.856 - info: host.iobroker Restart adapter system.adapter.nut.0 because enabled 2023-07-28 17:34:23.929 - info: host.iobroker instance system.adapter.alexa2.0 started with pid 708 2023-07-28 17:34:24.866 - info: host.iobroker instance system.adapter.discovery.0 started with pid 723 2023-07-28 17:34:25.867 - error: host.iobroker instance system.adapter.discovery.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:34:25.868 - info: host.iobroker Restart adapter system.adapter.discovery.0 because enabled 2023-07-28 17:34:27.701 - info: host.iobroker stopInstance system.adapter.alexa2.0 (force=false, process=true) 2023-07-28 17:34:27.703 - info: host.iobroker stopInstance system.adapter.alexa2.0 send kill signal 2023-07-28 17:34:28.078 - info: host.iobroker instance system.adapter.meross.0 started with pid 736 2023-07-28 17:34:28.242 - info: host.iobroker instance system.adapter.alexa2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-07-28 17:34:28.868 - info: host.iobroker instance system.adapter.backitup.0 started with pid 747 2023-07-28 17:34:29.977 - error: host.iobroker instance system.adapter.backitup.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:34:29.977 - info: host.iobroker Restart adapter system.adapter.backitup.0 because enabled 2023-07-28 17:34:30.740 - info: host.iobroker instance system.adapter.alexa2.0 started with pid 764 2023-07-28 17:34:31.880 - info: host.iobroker instance system.adapter.mqtt.0 started with pid 779 2023-07-28 17:34:32.867 - info: host.iobroker instance system.adapter.web.0 started with pid 796 2023-07-28 17:34:33.959 - error: host.iobroker instance system.adapter.web.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:34:33.959 - info: host.iobroker Restart adapter system.adapter.web.0 because enabled 2023-07-28 17:34:36.046 - info: host.iobroker instance system.adapter.shelly.0 started with pid 809 2023-07-28 17:34:38.925 - info: host.iobroker instance system.adapter.vis.0 terminated while should be started once 2023-07-28 17:34:40.237 - info: host.iobroker instance system.adapter.sonoff.0 started with pid 841 2023-07-28 17:34:40.885 - info: host.iobroker instance system.adapter.iot.0 started with pid 852 ================================== > LOG REDIRECT system.adapter.iot.0 => false [Process stopped] 2023-07-28 17:34:42.165 - error: host.iobroker instance system.adapter.iot.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:34:42.165 - info: host.iobroker Restart adapter system.adapter.iot.0 because enabled ================================== > LOG REDIRECT system.adapter.iot.0 => false [system.adapter.iot.0.logging] 2023-07-28 17:34:44.308 - info: host.iobroker instance system.adapter.tuya.0 started with pid 869 2023-07-28 17:34:44.873 - info: host.iobroker instance system.adapter.cloud.0 started with pid 880 ================================== > LOG REDIRECT system.adapter.cloud.0 => false [Process stopped] 2023-07-28 17:34:46.076 - error: host.iobroker instance system.adapter.cloud.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:34:46.076 - info: host.iobroker Restart adapter system.adapter.cloud.0 because enabled ================================== > LOG REDIRECT system.adapter.cloud.0 => false [system.adapter.cloud.0.logging] 2023-07-28 17:34:48.061 - info: host.iobroker instance system.adapter.tr-064.0 started with pid 899 2023-07-28 17:34:48.865 - info: host.iobroker instance system.adapter.net-tools.0 started with pid 910 2023-07-28 17:34:50.052 - error: host.iobroker instance system.adapter.net-tools.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:34:50.052 - info: host.iobroker Restart adapter system.adapter.net-tools.0 because enabled 2023-07-28 17:34:51.891 - info: host.iobroker instance system.adapter.nut.0 started with pid 927 2023-07-28 17:34:52.867 - info: host.iobroker instance system.adapter.fritzdect.0 started with pid 944 2023-07-28 17:34:53.952 - error: host.iobroker instance system.adapter.fritzdect.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:34:53.952 - info: host.iobroker Restart adapter system.adapter.fritzdect.0 because enabled 2023-07-28 17:34:55.905 - info: host.iobroker instance system.adapter.discovery.0 started with pid 957 2023-07-28 17:34:56.863 - info: host.iobroker instance system.adapter.sourceanalytix.0 started with pid 972 2023-07-28 17:34:57.873 - error: host.iobroker instance system.adapter.sourceanalytix.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:34:57.873 - info: host.iobroker Restart adapter system.adapter.sourceanalytix.0 because enabled 2023-07-28 17:35:00.016 - info: host.iobroker instance system.adapter.backitup.0 started with pid 985 2023-07-28 17:35:00.891 - info: host.iobroker instance system.adapter.energiefluss.0 started with pid 996 2023-07-28 17:35:02.024 - error: host.iobroker instance system.adapter.energiefluss.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:35:02.024 - info: host.iobroker Restart adapter system.adapter.energiefluss.0 because enabled 2023-07-28 17:35:03.993 - info: host.iobroker instance system.adapter.web.0 started with pid 1013 2023-07-28 17:35:04.857 - info: host.iobroker instance system.adapter.echarts.0 started with pid 1024 2023-07-28 17:35:06.015 - error: host.iobroker instance system.adapter.echarts.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-07-28 17:35:06.015 - info: host.iobroker Restart adapter system.adapter.echarts.0 because enabled 2023-07-28 17:35:12.200 - info: host.iobroker instance system.adapter.iot.0 started with pid 1045 2023-07-28 17:35:16.106 - info: host.iobroker instance system.adapter.cloud.0 started with pid 1062 2023-07-28 17:35:20.105 - info: host.iobroker instance system.adapter.net-tools.0 started with pid 1079 2023-07-28 17:35:23.981 - info: host.iobroker instance system.adapter.fritzdect.0 started with pid 1099 2023-07-28 17:35:27.901 - info: host.iobroker instance system.adapter.sourceanalytix.0 started with pid 1116 2023-07-28 17:35:32.051 - info: host.iobroker instance system.adapter.energiefluss.0 started with pid 1135 2023-07-28 17:35:36.034 - info: host.iobroker instance system.adapter.echarts.0 started with pid 1152Die Konsole bleibt aber irgendwie tot:
Was kann ich machen, damit a) mein ioBroker nach einem Neustart der Maschine wieder normal anspringt?
@markus-7 sagte in ioBroker startet nicht mehr:
root@iobroker
Ist schon mal grundsätzlich falsch im Container.
Auch da hampelt man nicht als root umher... -
@markus-7 sagte in ioBroker startet nicht mehr:
root@iobroker
Ist schon mal grundsätzlich falsch im Container.
Auch da hampelt man nicht als root umher...Danke für deinen Ratschlag, das werde ich beheben, sobald ich wieder ein funktionsfähiges System habe.
Kannst du mir denn sagen, was es damit auf sich haben könnte?
node: OpenSSL configuration error: C0D7023FDE7F0000:error:8000000D:system library:BIO_new_file:Permission denied:../deps/openssl/openssl/crypto/bio/bss_file.c:67:calling fopen(/etc/ssl/openssl.cnf, rb) -
Danke für deinen Ratschlag, das werde ich beheben, sobald ich wieder ein funktionsfähiges System habe.
Kannst du mir denn sagen, was es damit auf sich haben könnte?
node: OpenSSL configuration error: C0D7023FDE7F0000:error:8000000D:system library:BIO_new_file:Permission denied:../deps/openssl/openssl/crypto/bio/bss_file.c:67:calling fopen(/etc/ssl/openssl.cnf, rb)@markus-7 sagte in ioBroker startet nicht mehr:
Permission denied
Rechte verfummelt.
Kööööönnnnnnnnte mit root@iobroker in Verbindung stehen... -
Danke für deinen Ratschlag, das werde ich beheben, sobald ich wieder ein funktionsfähiges System habe.
Kannst du mir denn sagen, was es damit auf sich haben könnte?
node: OpenSSL configuration error: C0D7023FDE7F0000:error:8000000D:system library:BIO_new_file:Permission denied:../deps/openssl/openssl/crypto/bio/bss_file.c:67:calling fopen(/etc/ssl/openssl.cnf, rb) -
@markus-7 Wie wäre es wenn Du mal dieses Video anschaust und auch verinnerlichst ?!
https://www.youtube.com/watch?v=p6XmgzhH0Ow&t=279s
Da wird auch das ROOT erklärt !
-
@djmarc75
Sehr gutes Video, genau nach dem Video habe ich auch mein System installiert. Nur eben den root habe ich noch nicht gefixt.Wie kann ich mein Problem in den Griff bekommen? Neu-installation?
Da stimmt mit irgendwelchen Zertifikaten was nicht.
iobroker mit Lets-Encrypt aufgesetzt? -
Da stimmt mit irgendwelchen Zertifikaten was nicht.
iobroker mit Lets-Encrypt aufgesetzt? -
Nope, keine Zertifikate installiert.
-
@djmarc75
Sehr gutes Video, genau nach dem Video habe ich auch mein System installiert. Nur eben den root habe ich noch nicht gefixt.Wie kann ich mein Problem in den Griff bekommen? Neu-installation?
-
Danke für deinen Ratschlag, das werde ich beheben, sobald ich wieder ein funktionsfähiges System habe.
Kannst du mir denn sagen, was es damit auf sich haben könnte?
node: OpenSSL configuration error: C0D7023FDE7F0000:error:8000000D:system library:BIO_new_file:Permission denied:../deps/openssl/openssl/crypto/bio/bss_file.c:67:calling fopen(/etc/ssl/openssl.cnf, rb)@markus-7 sagte in ioBroker startet nicht mehr:
/etc/ssl/openssl.cnf
Moin,
wie sehen denn die Rechte der Datei aus, denn da kann ja jemand keinen
fopen = File opendarauf machen.ls -la /etc/ssl/openssl.cnf`Spuckt das bei mir aus
dp20eic@iobroker:~$ ls -la /etc/ssl/openssl.cnf -rw-r--r-- 1 root root 11118 Apr 20 2020 /etc/ssl/openssl.cnfVG
BerndP.S.: @Thomas-Braun war schneller :)
-
Problem: meine Konsole ist nach dem "Start" über "node node_modules/iobroker.js-controller/controller.js --logs" tot:
@djmarc75 said in ioBroker startet nicht mehr:
@markus-7 sagte in ioBroker startet nicht mehr:
Nur eben den root habe ich noch nicht gefixt
Das wird ja in dem Video auch genau beschrieben.
Ja, ich erstelle mir asap einen anderen Benutzer auf meinen Kisten - versprochen ;-)
-
Problem: meine Konsole ist nach dem "Start" über "node node_modules/iobroker.js-controller/controller.js --logs" tot:
@djmarc75 said in ioBroker startet nicht mehr:
@markus-7 sagte in ioBroker startet nicht mehr:
Nur eben den root habe ich noch nicht gefixt
Das wird ja in dem Video auch genau beschrieben.
Ja, ich erstelle mir asap einen anderen Benutzer auf meinen Kisten - versprochen ;-)
@markus-7 sagte in ioBroker startet nicht mehr:
meine Konsole ist nach dem "Start" über "node node_modules/iobroker.js-controller/controller.js --logs" tot:
Und mit einem richtigen Terminal?
-
Problem: meine Konsole ist nach dem "Start" über "node node_modules/iobroker.js-controller/controller.js --logs" tot:
@djmarc75 said in ioBroker startet nicht mehr:
@markus-7 sagte in ioBroker startet nicht mehr:
Nur eben den root habe ich noch nicht gefixt
Das wird ja in dem Video auch genau beschrieben.
Ja, ich erstelle mir asap einen anderen Benutzer auf meinen Kisten - versprochen ;-)
@markus-7 sagte in ioBroker startet nicht mehr:
Problem: meine Konsole ist nach dem "Start" über "node node_modules/iobroker.js-controller/controller.js --logs" tot:
Moin,
log dich mal mittels
puttyoder einem anderen Linux auf die Kiste ein, dann dort weiter arbeiten, und den hängenden Prozess killen.VG
BerndP.S.: @Thomas-Braun war schon wieder schneller :)
P.P.S.: kann ja auch nicht weiter kaputtgehen, einfach noch mal den LXC Container Booten :) -
@markus-7 sagte in ioBroker startet nicht mehr:
Problem: meine Konsole ist nach dem "Start" über "node node_modules/iobroker.js-controller/controller.js --logs" tot:
Moin,
log dich mal mittels
puttyoder einem anderen Linux auf die Kiste ein, dann dort weiter arbeiten, und den hängenden Prozess killen.VG
BerndP.S.: @Thomas-Braun war schon wieder schneller :)
P.P.S.: kann ja auch nicht weiter kaputtgehen, einfach noch mal den LXC Container Booten :) -
@markus-7 sagte in ioBroker startet nicht mehr:
/etc/ssl/openssl.cnf
Moin,
wie sehen denn die Rechte der Datei aus, denn da kann ja jemand keinen
fopen = File opendarauf machen.ls -la /etc/ssl/openssl.cnf`Spuckt das bei mir aus
dp20eic@iobroker:~$ ls -la /etc/ssl/openssl.cnf -rw-r--r-- 1 root root 11118 Apr 20 2020 /etc/ssl/openssl.cnfVG
BerndP.S.: @Thomas-Braun war schneller :)
-
@dp20eic
Klemmt heute überall: Putty meint beim Login mit meinem neuen User "Access denied" ... wie auch mit dem Login als root :-(
(Der neue User lässt sich auf der lokalen Konsole einloggen)Port 22 müsste ja passen, oder?
@markus-7 sagte in ioBroker startet nicht mehr:
Port 22 müsste ja passen, oder?
Moin,
ja, das ist der Standard Port.
Sorry, da ist dann wohl noch mehr nicht korrekt eingerichtet, laufen denn die Dienste?systemctl status sshd.service systemctl status ssh.serviceWas kommt denn bei
dp20eic@iobroker:~$ id iobrokerWie sehen die allg. Rechte unter
/opt/iobrokerausls -lah /opt/ lslah /opt/iobrokerGehe auch davon aus, dass die Rechte verschroben sind, ob da jetzt ein
fixhilft kann ich nicht sagen, wenn Du ein Backup, derioBrokerInstallation hastBackitUp, dann würde ich neu, richtig, ohnerootinstallieren und das Backup einspielen, ist vielleicht mit weniger Kopfschmerzen verbunden.VG
Bernd -
@markus-7 sagte in ioBroker startet nicht mehr:
Port 22 müsste ja passen, oder?
Moin,
ja, das ist der Standard Port.
Sorry, da ist dann wohl noch mehr nicht korrekt eingerichtet, laufen denn die Dienste?systemctl status sshd.service systemctl status ssh.serviceWas kommt denn bei
dp20eic@iobroker:~$ id iobrokerWie sehen die allg. Rechte unter
/opt/iobrokerausls -lah /opt/ lslah /opt/iobrokerGehe auch davon aus, dass die Rechte verschroben sind, ob da jetzt ein
fixhilft kann ich nicht sagen, wenn Du ein Backup, derioBrokerInstallation hastBackitUp, dann würde ich neu, richtig, ohnerootinstallieren und das Backup einspielen, ist vielleicht mit weniger Kopfschmerzen verbunden.VG
Bernd@dp20eic
Wollte gerade eine neuen Maschine aufsetzen - da bekomme ich ganz andere Probleme:
root@debian-1:~# apt-get install sudo Reading package lists... Done Building dependency tree... Done The following NEW packages will be installed: sudo 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 1889 kB of archives. After this operation, 6199 kB of additional disk space will be used. Ign:1 http://deb.debian.org/debian bookworm/main amd64 sudo amd64 1.9.13p3-1 Ign:1 http://deb.debian.org/debian bookworm/main amd64 sudo amd64 1.9.13p3-1 Ign:1 http://deb.debian.org/debian bookworm/main amd64 sudo amd64 1.9.13p3-1 Err:1 http://deb.debian.org/debian bookworm/main amd64 sudo amd64 1.9.13p3-1 Temporary failure resolving 'deb.debian.org' E: Failed to fetch http://deb.debian.org/debian/pool/main/s/sudo/sudo_1.9.13p3-1_amd64.deb Temporary failure resolving 'deb.debian.org' E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?root@debian-1:~# ping deb.debian.org ping: deb.debian.org: Temporary failure in name resolution root@debian-1:~#Bah ... so langsam wäre es jetzt auch mal gut mit meinen Problemen :slightly_frowning_face:
-
@markus-7 sagte in ioBroker startet nicht mehr:
Port 22 müsste ja passen, oder?
Moin,
ja, das ist der Standard Port.
Sorry, da ist dann wohl noch mehr nicht korrekt eingerichtet, laufen denn die Dienste?systemctl status sshd.service systemctl status ssh.serviceWas kommt denn bei
dp20eic@iobroker:~$ id iobrokerWie sehen die allg. Rechte unter
/opt/iobrokerausls -lah /opt/ lslah /opt/iobrokerGehe auch davon aus, dass die Rechte verschroben sind, ob da jetzt ein
fixhilft kann ich nicht sagen, wenn Du ein Backup, derioBrokerInstallation hastBackitUp, dann würde ich neu, richtig, ohnerootinstallieren und das Backup einspielen, ist vielleicht mit weniger Kopfschmerzen verbunden.VG
Bernd@dp20eic
Die Rechte sehen so aus:
I have no name!@iobroker:/opt/iobroker$ ls -lah /opt/ total 12K drwxr-xr-x 3 0 0 4.0K Jul 20 15:16 . drwxr-xr-x 19 0 0 4.0K Jul 28 17:32 .. drwxrwxr-x+ 6 1000 1000 4.0K Jul 20 15:17 iobroker I have no name!@iobroker:/opt/iobroker$ ls -lah /opt/iobroker total 484K drwxrwxr-x+ 6 1000 1000 4.0K Jul 20 15:17 . drwxr-xr-x 3 0 0 4.0K Jul 20 15:16 .. -rw-rwxr--+ 1 1000 1000 155 Jul 20 15:16 .npmrc -rwxrwxrwx+ 1 1000 1000 133 Jul 20 15:17 INSTALLER_INFO.txt drwxrwxr-x+ 2 1000 1000 4.0K Jul 28 17:14 backups lrwxrwxrwx 1 1000 1000 22 Jul 20 15:17 iob -> /opt/iobroker/iobroker -rwxrwxr-x+ 1 1000 1000 512 Jul 20 15:17 iobroker drwxrwxr-x+ 7 1000 1000 4.0K Jul 28 17:15 iobroker-data drwxrwxr-x+ 2 1000 1000 4.0K Jul 28 17:12 log drwxrwxr-x+ 688 1000 1000 20K Jul 22 14:50 node_modules -rw-rwxr--+ 1 1000 1000 428K Jul 22 14:50 package-lock.json -rw-rwxr--+ 1 1000 1000 985 Jul 22 14:50 package.json I have no name!@iobroker:/opt/iobroker$und der id-Befehl funzt nicht
I have no name!@iobroker:/opt/iobroker$ id iobroker id: 'iobroker': no such user I have no name!@iobroker:/opt/iobroker$ -
@dp20eic
Die Rechte sehen so aus:
I have no name!@iobroker:/opt/iobroker$ ls -lah /opt/ total 12K drwxr-xr-x 3 0 0 4.0K Jul 20 15:16 . drwxr-xr-x 19 0 0 4.0K Jul 28 17:32 .. drwxrwxr-x+ 6 1000 1000 4.0K Jul 20 15:17 iobroker I have no name!@iobroker:/opt/iobroker$ ls -lah /opt/iobroker total 484K drwxrwxr-x+ 6 1000 1000 4.0K Jul 20 15:17 . drwxr-xr-x 3 0 0 4.0K Jul 20 15:16 .. -rw-rwxr--+ 1 1000 1000 155 Jul 20 15:16 .npmrc -rwxrwxrwx+ 1 1000 1000 133 Jul 20 15:17 INSTALLER_INFO.txt drwxrwxr-x+ 2 1000 1000 4.0K Jul 28 17:14 backups lrwxrwxrwx 1 1000 1000 22 Jul 20 15:17 iob -> /opt/iobroker/iobroker -rwxrwxr-x+ 1 1000 1000 512 Jul 20 15:17 iobroker drwxrwxr-x+ 7 1000 1000 4.0K Jul 28 17:15 iobroker-data drwxrwxr-x+ 2 1000 1000 4.0K Jul 28 17:12 log drwxrwxr-x+ 688 1000 1000 20K Jul 22 14:50 node_modules -rw-rwxr--+ 1 1000 1000 428K Jul 22 14:50 package-lock.json -rw-rwxr--+ 1 1000 1000 985 Jul 22 14:50 package.json I have no name!@iobroker:/opt/iobroker$und der id-Befehl funzt nicht
I have no name!@iobroker:/opt/iobroker$ id iobroker id: 'iobroker': no such user I have no name!@iobroker:/opt/iobroker$@markus-7 sagte in ioBroker startet nicht mehr:
'iobroker': no such user
Da wundert es auch nicht, wenn da nichts mehr funktioniert.
cat /etc/passwdspuckt was aus?
Support us
510
Online32.5k
Benutzer81.9k
Themen1.3m
Beiträge