Yahka Adapter in iobroker im Docker Container
-
@glasfaser sagte in Yahka Adapter in iobroker im Docker Container:
iob logs --watch
ist der schon durch? im moment kommt das weiter nix mehr ... müsste da nicht auch drin stehen das der jetzt die adapter installiert?
root@iobroker:/opt/iobroker# iob logs --watch 2023-05-07 19:19:33.517 - info: host.iobroker iobroker.js-controller version 4.0.24 js-controller starting 2023-05-07 19:19:33.523 - info: host.iobroker Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-05-07 19:19:33.524 - info: host.iobroker hostname: iobroker, node: v18.16.0 2023-05-07 19:19:33.525 - info: host.iobroker ip addresses: 192.168.7.39 2a01:598:b1ae:5fa:cda9:f7e8:4f52:b0ae fe80::d1ed:ac40:eb70:1818 172.17.0.1 fe80::42:ff:fea8:f9dc 169.254.109.96 fe80::dc28:b3ff:fe26:53e2 169.254.233.119 fe80::6111:bcc0:a1c7:a2b1 169.254.246.52 fe80::88ee:4aff:fed1:1f0e 2023-05-07 19:19:33.950 - info: host.iobroker connected to Objects and States 2023-05-07 19:19:33.980 - info: host.iobroker Node.js version has changed from unknown to 18.16.0 2023-05-07 19:19:34.039 - warn: host.iobroker Error while trying to update capabilities after detecting new Node.js version: Command failed: sudo setcap cap_net_bind_service,cap_net_raw+epi /usr/bin/node sudo: /etc/sudo.conf is world writable sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set 2023-05-07 19:19:34.057 - info: host.iobroker added notifications configuration of host 2023-05-07 19:19:34.349 - info: host.iobroker 3 instances found 2023-05-07 19:19:34.360 - info: host.iobroker starting 3 instances 2023-05-07 19:19:34.428 - info: host.iobroker instance system.adapter.admin.0 started with pid 1828 2023-05-07 19:19:36.707 - info: admin.0 (1828) starting. Version 6.3.5 in /opt/iobroker/node_modules/iobroker.admin, node: v18.16.0, js-controller: 4.0.24 2023-05-07 19:19:36.770 - info: admin.0 (1828) requesting all states 2023-05-07 19:19:36.771 - info: admin.0 (1828) requesting all objects 2023-05-07 19:19:36.948 - info: admin.0 (1828) received all objects 2023-05-07 19:19:36.973 - info: admin.0 (1828) Request actual repository... 2023-05-07 19:19:36.990 - info: host.iobroker Updating repository "stable" under "http://download.iobroker.net/sources-dist.json" 2023-05-07 19:19:36.995 - info: admin.0 (1828) http server listening on port 8081 2023-05-07 19:19:36.996 - info: admin.0 (1828) Use link "http://localhost:8081" to configure. 2023-05-07 19:19:37.006 - info: admin.0 (1828) socket.io server listening on port 8081 2023-05-07 19:19:37.166 - warn: admin.0 (1828) Repository cannot be read: Active repo - stable 2023-05-07 19:19:37.169 - warn: admin.0 (1828) Active repository "stable" cannot be read 2023-05-07 19:19:38.396 - info: host.iobroker instance system.adapter.discovery.0 started with pid 1851 2023-05-07 19:19:40.681 - info: discovery.0 (1851) starting. Version 3.1.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v18.16.0, js-controller: 4.0.24 2023-05-07 19:19:42.860 - info: host.iobroker instance system.adapter.backitup.0 started with pid 1870 2023-05-07 19:19:42.944 - info: admin.0 (1828) Repository received successfully. 2023-05-07 19:19:47.040 - info: backitup.0 (1870) starting. Version 2.6.19 in /opt/iobroker/node_modules/iobroker.backitup, node: v18.16.0, js-controller: 4.0.24 2023-05-07 19:19:47.154 - info: backitup.0 (1870) [iobroker] backup will be activated at 02:40 every 1 day(s) 2023-05-07 19:20:12.573 - info: admin.0 (1828) ==> Connected system.user.admin from ::ffff:192.168.7.1 2023-05-07 19:20:12.929 - info: admin.0 (1828) ==> Connected system.user.admin from ::ffff:192.168.7.1 2023-05-07 19:27:02.612 - info: admin.0 (1828) <== Disconnect system.user.admin from ::ffff:192.168.7.1 admin 2023-05-07 19:27:02.966 - info: admin.0 (1828) <== Disconnect system.user.admin from ::ffff:192.168.7.1 admin 2023-05-07 19:31:54.131 - info: admin.0 (1828) ==> Connected system.user.admin from ::ffff:192.168.7.1 2023-05-07 19:31:54.216 - info: admin.0 (1828) ==> Connected system.user.admin from ::ffff:192.168.7.1 2023-05-07 19:31:59.225 - info: admin.0 (1828) <== Disconnect system.user.admin from ::ffff:192.168.7.1 admin 2023-05-07 19:32:01.820 - info: admin.0 (1828) ==> Connected system.user.admin from ::ffff:192.168.7.1 2023-05-07 19:33:18.830 - info: admin.0 (1828) ==> Connected system.user.admin from ::ffff:192.168.7.1 2023-05-07 19:37:01.987 - info: admin.0 (1828) <== Disconnect system.user.admin from ::ffff:192.168.7.1da steht doch garnix davon drin das sind doch die logins von vor dem restore oder? 19:37 ...
-
-
@djmarc75 der ist ruhig läuft deutlich unter 10% CPU Last
-
@tomme sagte in Yahka Adapter in iobroker im Docker Container:
2023-05-07 19:19:37.166 - warn: admin.0 (1828) Repository cannot be read: Active repo - stable
Da ist nichts passiert !
Nimm mal zum Test einen anderen Browser ( dann Restore über Backitup ) , eventuell ein Popup Blocker !?
-
@tomme sagte in Yahka Adapter in iobroker im Docker Container:
der ist ruhig läuft deutlich unter 10% CPU Las
das meine ich nicht. Du kannst da auch sehen ob Adapter installiert werden. In Deinem Screenshot (Momentaufnahme) ist aber alles durch
-
@glasfaser sagte in Yahka Adapter in iobroker im Docker Container:
anderen Browser ( dann Restore über Backitup ) , eventuell ein Popup Blocker !?
nö das fenster war da hat auch die ersten zeilen gemacht und dann kam das was ich gepostet habe ... ich machs nochmal war gestern auch so ... dachte nur ich habs beeinflusst weil ich ziemlich schnell nachgeschaut hatte
-
so sieht das zu anfang aus und dann kommt wieder die meldung
htop sieht jetzt so aus
ins log schaue ich gleich
2023-05-07 20:04:36.654 - info: admin.0 (1828) <== Disconnect system.user.admin from ::ffff:192.168.7.1 admin 2023-05-07 20:04:36.654 - info: admin.0 (1828) <== Disconnect system.user.admin from ::ffff:192.168.7.1 admin 2023-05-07 20:04:38.839 - info: admin.0 (1828) ==> Connected system.user.admin from ::ffff:192.168.7.1 2023-05-07 20:04:38.839 - info: admin.0 (1828) ==> Connected system.user.admin from ::ffff:192.168.7.1 2023-05-07 20:04:41.241 - info: admin.0 (1828) ==> Connected system.user.admin from ::ffff:192.168.7.1 2023-05-07 20:04:41.241 - info: admin.0 (1828) ==> Connected system.user.admin from ::ffff:192.168.7.1 2023-05-07 20:04:44.688 - info: admin.0 (1828) <== Disconnect system.user.admin from ::ffff:192.168.7.1 2023-05-07 20:04:44.688 - info: admin.0 (1828) <== Disconnect system.user.admin from ::ffff:192.168.7.1 2023-05-07 20:04:48.298 - info: admin.0 (1828) ==> Connected system.user.admin from ::ffff:192.168.7.1 2023-05-07 20:04:48.298 - info: admin.0 (1828) ==> Connected system.user.admin from ::ffff:192.168.7.1 2023-05-07 20:05:12.805 - info: admin.0 (1828) <== Disconnect system.user.admin from ::ffff:192.168.7.1 2023-05-07 20:05:12.805 - info: admin.0 (1828) <== Disconnect system.user.admin from ::ffff:192.168.7.1 -
Eine allgemeine Frage von mir ... was ich niergens hier von dir erlese ..
Hast du Buster oder bullseye
-
@glasfaser das neueste bullseye von vorgestern das image das neue
-
@tomme sagte in Yahka Adapter in iobroker im Docker Container:
das neueste bullseye von vorgestern das image das neue
zeig mal
iob diagbitte aber in Codetags
-
root@iobroker:/opt/iobroker# iob diag sudo: /etc/sudo.conf is world writable sudo: /etc/sudo.conf is world writable sudo: error in /etc/sudo.conf, line 0 while loading plugin "sudoers_policy" sudo: /usr/lib/sudo/sudoers.so must be only be writable by owner sudo: fatal error, unable to load plugins root@iobroker:/opt/iobroker# -
@tomme Docker kenn ich mich nicht aus - ob da root sinnvoll ist - kein Plan... aber teste mal
iob stop iob fix iob start iob diag -
@djmarc75 iob stop geht nicht da nehme ich das pkill ja
-
@tomme sagte in Yahka Adapter in iobroker im Docker Container:
@djmarc75 iob stop geht nicht da nehme ich das pkill ja
richtig ... setze es um auf Docker !
-
@djmarc75 sagte in Yahka Adapter in iobroker im Docker Container:
ob da root sinnvoll ist
Ist kein root im Sinne .. (Docker)
ich habe keine Ahnung was bei Ihm los ist ... ist von anfang an der Fehler mit sudo .
-
@glasfaser wenn ich in portainer ein terminal öffne ist das root bei mir
-
@tomme sagte in Yahka Adapter in iobroker im Docker Container:
@glasfaser wenn ich in portainer ein terminal öffne ist das root bei mir
Alles gut !
-
root@iobroker:/opt/iobroker# pkill -u iobroker iob fix iob start iob diag library: loaded Library version=2022-12-09 ========================================================================== Welcome to the ioBroker installation fixer! Script version: 2023-04-02 ========================================================================== ========================================================================== Installing prerequisites (1/5) ========================================================================== Get:1 http://deb.debian.org/debian bullseye InRelease [116 kB] Get:2 https://deb.nodesource.com/node_18.x bullseye InRelease [4.586 B] Get:3 http://deb.debian.org/debian-security bullseye-security InRelease [48,4 kB] Get:4 http://deb.debian.org/debian bullseye-updates InRelease [44,1 kB] Get:5 http://deb.debian.org/debian bullseye/main arm64 Packages [8.071 kB] Get:6 https://deb.nodesource.com/node_18.x bullseye/main arm64 Packages [776 B] Get:7 http://deb.debian.org/debian-security bullseye-security/main arm64 Packages [235 kB] Get:8 http://deb.debian.org/debian bullseye-updates/main arm64 Packages [12,0 kB] Fetched 8.531 kB in 12s (722 kB/s) Reading package lists... Done Installed gcc-c++ Docker detected! If you have any adapters that need the CAP_NET_ADMIN capability, you need to start the docker container with the option --cap-add=NET_ADMIN and manually add that capability to node ========================================================================== Checking ioBroker user and directory permissions (2/5) ========================================================================== visudo: /etc/sudo.conf is world writable Created /etc/sudoers.d/iobroker sudo: /etc/sudo.conf is world writable sudo: /etc/sudo.conf is world writable sudo: error in /etc/sudo.conf, line 0 while loading plugin "sudoers_policy" sudo: /usr/lib/sudo/sudoers.so must be only be writable by owner sudo: fatal error, unable to load plugins sudo: /etc/sudo.conf is world writable sudo: /etc/sudo.conf is world writable sudo: error in /etc/sudo.conf, line 0 while loading plugin "sudoers_policy" sudo: /usr/lib/sudo/sudoers.so must be only be writable by owner sudo: fatal error, unable to load plugins Fixing directory permissions... ========================================================================== Check and cleanup npm temporary directories (3/5) ========================================================================== Done. ========================================================================== Database maintenance (4/5) ========================================================================== Checking for uncompressed JSONL databases... This might take a while! sudo: /etc/sudo.conf is world writable sudo: /etc/sudo.conf is world writable sudo: error in /etc/sudo.conf, line 0 while loading plugin "sudoers_policy" sudo: /usr/lib/sudo/sudoers.so must be only be writable by owner sudo: fatal error, unable to load plugins main: line 12: [: -lt: unary operator expected sudo: /etc/sudo.conf is world writable sudo: /etc/sudo.conf is world writable sudo: error in /etc/sudo.conf, line 0 while loading plugin "sudoers_policy" sudo: /usr/lib/sudo/sudoers.so must be only be writable by owner sudo: fatal error, unable to load plugins ========================================================================== Checking autostart (5/5) ========================================================================== Unsupported init system, cannot enable autostart! ========================================================================== Your installation was fixed successfully Run iobroker start to start ioBroker again! ========================================================================== sudo: /etc/sudo.conf is world writable sudo: /etc/sudo.conf is world writable sudo: error in /etc/sudo.conf, line 0 while loading plugin "sudoers_policy" sudo: /usr/lib/sudo/sudoers.so must be only be writable by owner sudo: fatal error, unable to load plugins sudo: /etc/sudo.conf is world writable sudo: /etc/sudo.conf is world writable sudo: error in /etc/sudo.conf, line 0 while loading plugin "sudoers_policy" sudo: /usr/lib/sudo/sudoers.so must be only be writable by owner sudo: fatal error, unable to load plugins root@iobroker:/opt/iobroker#diag kommt gleich ... nur die zusammenfassung oder auch das davor?
-
root@iobroker:/opt/iobroker# iob start iob diag sudo: /etc/sudo.conf is world writable sudo: /etc/sudo.conf is world writable sudo: error in /etc/sudo.conf, line 0 while loading plugin "sudoers_policy" sudo: /usr/lib/sudo/sudoers.so must be only be writable by owner sudo: fatal error, unable to load plugins sudo: /etc/sudo.conf is world writable sudo: /etc/sudo.conf is world writable sudo: error in /etc/sudo.conf, line 0 while loading plugin "sudoers_policy" sudo: /usr/lib/sudo/sudoers.so must be only be writable by owner sudo: fatal error, unable to load plugins root@iobroker:/opt/iobroker# -
@tomme sagte in Yahka Adapter in iobroker im Docker Container:
root@iobroker:/opt/iobroker# iob start
Alles umsetzten auf Docker
pkill -u iobrokeriob fixContainer neu starten über Portainer ..dann
iob diagkein start und stop im Container !
