NEWS
Admin startet nicht - buanet image[gelöst]
ioBroker Allgemein
55
Beiträge
2
Kommentatoren
4.1k
Aufrufe
3
Watching
-
Hallo ,
nach vielen Versuchen und Recherchen muss ich mich jetzt doch an das Forum wenden:
Ich habe hier eine DS713+, DSM 7.1.1 mit einer iobroker Installation von buanet als Docker Container.
Zugriff über Portainer, Port gemappt auf 8889.
Im iobroker Container ist der Port 8081:8081 gemapt, da der Container im Bridge Modus startet.
Der Zugriff auf die iobroker Weboberfläche funktioniert nicht.
Auffälligkeiten:- In der Docker App der Synology ist der iobroker Container nicht sichtbar (meine das war früher anders)
- Der Admin Adapter ist disabled, lässt sich aber in der Konsole nicht starten
- In Portainer steht der iobroker Container auf "healthy", nicht auf "running"
Gestartet hat dies nachdem ich den Admin Adapter in der Weboberfläche versehentlich gestoppt hatte
Hier die Antwort auf "list instances"
root@iobroker:/opt/iobroker# iobroker list instances
system.adapter.admin.0 : admin : iobroker - disabled, port: 8081, bind: 0.0.0.0, run as: admin
system.adapter.backitup.0 : backitup : iobroker - disabled- system.adapter.discovery.0 : discovery : iobroker - enabled
system.adapter.hm-rega.0 : hm-rega : iobroker - disabled
system.adapter.hm-rpc.0 : hm-rpc : iobroker - disabled, port: 0
system.adapter.hm-rpc.1 : hm-rpc : iobroker - disabled, port: 0
system.adapter.influxdb.0 : influxdb : iobroker - disabled, port: 8086
system.adapter.vis.0 : vis : iobroker - disabled
system.adapter.web.0 : web : iobroker - disabled, port: 8082, bind: 0.0.0.0, run as: admin
Danke für jeden Hinweis!
Synology 713+
IOBroker im Dockerumfeld auf Synology
Raspimatic -
Hallo ,
nach vielen Versuchen und Recherchen muss ich mich jetzt doch an das Forum wenden:
Ich habe hier eine DS713+, DSM 7.1.1 mit einer iobroker Installation von buanet als Docker Container.
Zugriff über Portainer, Port gemappt auf 8889.
Im iobroker Container ist der Port 8081:8081 gemapt, da der Container im Bridge Modus startet.
Der Zugriff auf die iobroker Weboberfläche funktioniert nicht.
Auffälligkeiten:- In der Docker App der Synology ist der iobroker Container nicht sichtbar (meine das war früher anders)
- Der Admin Adapter ist disabled, lässt sich aber in der Konsole nicht starten
- In Portainer steht der iobroker Container auf "healthy", nicht auf "running"
Gestartet hat dies nachdem ich den Admin Adapter in der Weboberfläche versehentlich gestoppt hatte
Hier die Antwort auf "list instances"
root@iobroker:/opt/iobroker# iobroker list instances
system.adapter.admin.0 : admin : iobroker - disabled, port: 8081, bind: 0.0.0.0, run as: admin
system.adapter.backitup.0 : backitup : iobroker - disabled- system.adapter.discovery.0 : discovery : iobroker - enabled
system.adapter.hm-rega.0 : hm-rega : iobroker - disabled
system.adapter.hm-rpc.0 : hm-rpc : iobroker - disabled, port: 0
system.adapter.hm-rpc.1 : hm-rpc : iobroker - disabled, port: 0
system.adapter.influxdb.0 : influxdb : iobroker - disabled, port: 8086
system.adapter.vis.0 : vis : iobroker - disabled
system.adapter.web.0 : web : iobroker - disabled, port: 8082, bind: 0.0.0.0, run as: admin
Danke für jeden Hinweis!
@hmuser sagte in Admin startet nicht - buanet image:
Der Admin Adapter ist disabled, lässt sich aber in der Konsole nicht starten
und was kommt dann in der Konsole wenn du
iob start adminmachst !?
Was steht sonst im Log !?
In Portainer steht der iobroker Container auf "healthy", nicht auf "running"
healthy ist richtig !
Zeige mal was du so hast :
Full Ausgabe von
iob diagaber bitte in Code-Tags </>
-
@hmuser sagte in Admin startet nicht - buanet image:
Der Admin Adapter ist disabled, lässt sich aber in der Konsole nicht starten
und was kommt dann in der Konsole wenn du
iob start adminmachst !?
Was steht sonst im Log !?
In Portainer steht der iobroker Container auf "healthy", nicht auf "running"
healthy ist richtig !
Zeige mal was du so hast :
Full Ausgabe von
iob diagaber bitte in Code-Tags </>
@glasfaser
Schicke ich gerne heute Abend: bekomme das auf dem iPhone nicht hin.
Danke schon mal für den Support. -
@hmuser sagte in Admin startet nicht - buanet image:
Der Admin Adapter ist disabled, lässt sich aber in der Konsole nicht starten
und was kommt dann in der Konsole wenn du
iob start adminmachst !?
Was steht sonst im Log !?
In Portainer steht der iobroker Container auf "healthy", nicht auf "running"
healthy ist richtig !
Zeige mal was du so hast :
Full Ausgabe von
iob diagaber bitte in Code-Tags </>
@glasfaser
Hier das Ergebnis von Diag:======== Start marking the full check here ========= Skript v.2023-10-10 *** BASE SYSTEM *** Hardware Vendor : Intel Corporation Kernel : x86_64 Userland : amd64 Docker : v9.0.1 Virtualization : Docker Kernel : x86_64 Userland : amd64 Systemuptime and Load: 21:28:34 up 3 days, 6:55, 0 user, load average: 2.40, 2.10, 1.88 CPU threads: 4 *** Time and Time Zones *** Mon Jan 22 20:28:34 UTC 2024 Mon Jan 22 21:28:34 CET 2024 CET +0100 Etc/UTC *** User and Groups *** root /root root *** X-Server-Setup *** X-Server: false Desktop: Terminal: *** MEMORY *** total used free shared buff/cache available Mem: 1.0G 914M 122M 2.7M 250M 122M Swap: 2.8G 699M 2.1G Total: 3.8G 1.6G 2.2G 988 M total memory 871 M used memory 197 M active memory 257 M inactive memory 116 M free memory 13 M buffer memory 225 M swap cache 2641 M total swap 667 M used swap 1974 M free swap *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on none aufs 3.6T 1.7T 2.0T 47% / tmpfs tmpfs 64M 0 64M 0% /dev tmpfs tmpfs 495M 0 495M 0% /sys/fs/cgroup shm tmpfs 64M 0 64M 0% /dev/shm /dev/mapper/cachedev_0 ext4 3.6T 1.7T 2.0T 47% /opt/iobroker tmpfs tmpfs 495M 0 495M 0% /proc/acpi tmpfs tmpfs 495M 0 495M 0% /proc/scsi tmpfs tmpfs 495M 0 495M 0% /sys/firmware Messages concerning ext4 filesystem in dmesg: [Fri Jan 19 14:34:06 2024] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [Fri Jan 19 14:34:08 2024] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [Fri Jan 19 14:34:08 2024] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null) [Fri Jan 19 14:34:13 2024] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [Fri Jan 19 14:34:14 2024] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: barrier=1 [Fri Jan 19 14:34:34 2024] EXT4-fs (dm-0): barriers disabled [Fri Jan 19 14:34:35 2024] EXT4-fs (dm-0): mounted filesystem with writeback data mode. Opts: usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,synoacl,oldalloc [Fri Jan 19 14:34:49 2024] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null) Show mounted filesystems \(real ones only\): TARGET SOURCE FSTYPE OPTIONS / none aufs rw,relatime,si=e20874a76f97f35,dio,dirperm1 |-/opt/iobroker /dev/mapper/cachedev_0[/docker/iobroker_data] ext4 rw,nodev,relatime,journal_checksum,synoacl,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group |-/etc/resolv.conf /dev/mapper/cachedev_0[/@docker/containers/fc8a2d4a9b91b0684e008a4d386fa591d0ba1fc92d86287615aa9ec6f7ba5ff4/resolv.conf] ext4 rw,nodev,relatime,journal_checksum,synoacl,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group |-/etc/hostname /dev/mapper/cachedev_0[/@docker/containers/fc8a2d4a9b91b0684e008a4d386fa591d0ba1fc92d86287615aa9ec6f7ba5ff4/hostname] ext4 rw,nodev,relatime,journal_checksum,synoacl,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group `-/etc/hosts /dev/mapper/cachedev_0[/@docker/containers/fc8a2d4a9b91b0684e008a4d386fa591d0ba1fc92d86287615aa9ec6f7ba5ff4/hosts] ext4 rw,nodev,relatime,journal_checksum,synoacl,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group Files in neuralgic directories: /var: 34M /var/ 32M /var/lib 19M /var/lib/apt/lists 19M /var/lib/apt 13M /var/lib/dpkg /opt/iobroker/backups: 54M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 109M /opt/iobroker/iobroker-data/ 62M /opt/iobroker/iobroker-data/files 33M /opt/iobroker/iobroker-data/backup-objects 30M /opt/iobroker/iobroker-data/files/web.admin/static 30M /opt/iobroker/iobroker-data/files/web.admin The five largest files in iobroker-data are: 21M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.aaea95f8.js.map 8.3M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.aaea95f8.js 8.2M /opt/iobroker/iobroker-data/objects.jsonl 6.3M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_js-node_modules_iobr-99c23e.847b8ad9.chunk.js.map 5.9M /opt/iobroker/iobroker-data/states.jsonl USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/* in your adapter setups, please always prefer the links 'by-id': find: '/dev/serial/by-id/': No such file or directory *** NodeJS-Installation *** /usr/bin/nodejs v18.19.0 /usr/bin/node v18.19.0 /usr/bin/npm 10.2.3 /usr/bin/npx 10.2.3 /usr/bin/corepack 0.22.0 nodejs: Installed: 18.19.0-1nodesource1 Candidate: 18.19.0+dfsg-6~deb12u1 Version table: 18.19.0+dfsg-6~deb12u1 500 500 http://deb.debian.org/debian-security bookworm-security/main amd64 Packages *** 18.19.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 18.18.2-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.17.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.17.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.15.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.2-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.13.0+dfsg1-1 500 500 http://deb.debian.org/debian bookworm/main amd64 Packages 18.13.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.12.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.11.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.10.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.8.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.7.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.6.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.5.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.4.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.3.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.2.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.1.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.0.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Core adapters versions js-controller: 5.0.17 admin: 6.12.0 javascript: "javascript" not found Adapters from github: 0 Adapter State system.adapter.admin.0 : admin : iobroker - disabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.admin.1 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.backitup.0 : backitup : iobroker - disabled + system.adapter.discovery.0 : discovery : iobroker - enabled system.adapter.hm-rega.0 : hm-rega : iobroker - disabled system.adapter.hm-rpc.0 : hm-rpc : iobroker - disabled, port: 0 system.adapter.hm-rpc.1 : hm-rpc : iobroker - disabled, port: 0 system.adapter.influxdb.0 : influxdb : iobroker - disabled, port: 8086 system.adapter.vis.0 : vis : iobroker - disabled system.adapter.web.0 : web : iobroker - disabled, port: 8082, bind: 0.0.0.0, run as: admin + instance is alive Enabled adapters with bindings + system.adapter.admin.1 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin ioBroker-Repositories stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json Active repo(s): stable Installed ioBroker-Instances Used repository: stable Adapter "admin" : 6.12.0 , installed 6.12.0 Adapter "backitup" : 2.9.8 , installed 2.8.7 [Updatable] Adapter "discovery" : 4.2.0 , installed 4.2.0 Adapter "hm-rega" : 4.0.0 , installed 4.0.0 Adapter "hm-rpc" : 1.15.19 , installed 1.15.19 Adapter "influxdb" : 3.2.0 , installed 3.2.0 Controller "js-controller": 5.0.17 , installed 5.0.17 Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "socketio" : 6.6.0 , installed 6.6.0 Adapter "vis" : 1.5.4 , installed 1.4.16 [Updatable] Adapter "web" : 6.1.10 , installed 6.1.10 Adapter "ws" : 2.5.8 , installed 2.5.8 Objects and States Please stand by - This may take a while Objects: 299 States: 279 *** OS-Repositories and Updates *** Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://deb.debian.org/debian bookworm-updates InRelease Hit:3 http://deb.debian.org/debian-security bookworm-security InRelease Hit:4 https://deb.nodesource.com/node_18.x nodistro InRelease Reading package lists... Pending Updates: 0 *** Listening Ports *** Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1000 13473077 - tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1000 13475539 - tcp6 0 0 :::8081 :::* LISTEN 1000 13475621 - udp 0 0 0.0.0.0:8472 0.0.0.0:* 0 13470984 - *** Log File - Last 25 Lines *** 2024-01-22 16:07:27.139 - info: host.iobroker Delete state "system.host.iobroker.versions.nodeCurrent" 2024-01-22 16:07:27.142 - info: host.iobroker 10 instances found 2024-01-22 16:07:27.186 - info: host.iobroker starting 2 instances 2024-01-22 16:07:27.303 - info: host.iobroker Delete state "system.host.iobroker.versions.nodeNewest" 2024-01-22 16:07:27.332 - info: host.iobroker instance system.adapter.admin.1 started with pid 184 2024-01-22 16:07:27.355 - info: host.iobroker Delete state "system.host.iobroker.versions.nodeNewestNext" 2024-01-22 16:07:27.369 - info: host.iobroker Delete state "system.host.iobroker.versions.npmCurrent" 2024-01-22 16:07:27.384 - info: host.iobroker Delete state "system.host.iobroker.versions.npmNewest" 2024-01-22 16:07:27.399 - info: host.iobroker Delete state "system.host.iobroker.versions.npmNewestNext" 2024-01-22 16:07:27.413 - info: host.iobroker Some obsolete host states deleted. 2024-01-22 16:07:31.285 - info: host.iobroker instance system.adapter.discovery.0 started with pid 191 2024-01-22 16:07:33.257 - info: admin.1 (184) starting. Version 6.12.0 in /opt/iobroker/node_modules/iobroker.admin, node: v18.19.0, js-controller: 5.0.17 2024-01-22 16:07:33.351 - info: admin.1 (184) requesting all objects 2024-01-22 16:07:34.689 - info: admin.1 (184) received all objects 2024-01-22 16:07:35.573 - info: discovery.0 (191) starting. Version 4.2.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v18.19.0, js-controller: 5.0.17 2024-01-22 16:07:36.683 - info: admin.1 (184) socket.io server listening on port 8081 2024-01-22 16:07:36.689 - info: admin.1 (184) http server listening on port 8081 2024-01-22 16:07:36.690 - info: admin.1 (184) Use link "http://127.0.0.1:8081" to configure. 2024-01-22 21:24:48.076 - info: admin.1 (184) ==> Connected system.user.admin from ::ffff:172.17.0.1 2024-01-22 21:24:50.064 - error: host.iobroker cannot call visUtils: Not exists 2024-01-22 21:25:03.083 - error: host.iobroker cannot call visUtils: Not exists 2024-01-22 21:26:22.491 - info: admin.1 (184) ==> Connected system.user.admin from ::ffff:172.17.0.1 2024-01-22 21:26:23.290 - error: host.iobroker cannot call visUtils: Not exists 2024-01-22 21:26:24.364 - info: admin.1 (184) <== Disconnect system.user.admin from ::ffff:172.17.0.1 admin ============ Mark until here for C&P =============und hier die summary:
======================= SUMMARY ======================= v.2023-10-10 model name : Intel(R) Atom(TM) CPU D2701 @ 2.13GHz Kernel : x86_64 Userland : amd64 Docker : v9.0.1 Installation: Docker Kernel: x86_64 Userland: amd64 Timezone: Etc/UTC User-ID: 0 X-Server: false Pending OS-Updates: 0 Pending iob updates: 2 Nodejs-Installation: /usr/bin/nodejs v18.19.0 /usr/bin/node v18.19.0 /usr/bin/npm 10.2.3 /usr/bin/npx 10.2.3 /usr/bin/corepack 0.22.0 Recommended versions are nodejs 18.19.0 and npm 10.2.3 Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 1.0G 901M 134M 2.8M 248M 134M Swap: 2.8G 710M 2.1G Total: 3.8G 1.6G 2.2G Active iob-Instances: 3 Active repo(s): stable ioBroker Core: js-controller 5.0.17 admin 6.12.0 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: system.adapter.admin.0 : admin : iobroker - disabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.admin.1 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.web.0 : web : iobroker - disabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 299 States: 279 Size of iob-Database: 8.2M /opt/iobroker/iobroker-data/objects.jsonl 5.9M /opt/iobroker/iobroker-data/states.jsonl =================== END OF SUMMARY ====================Synology 713+
IOBroker im Dockerumfeld auf Synology
Raspimatic -
@glasfaser
Hier das Ergebnis von Diag:======== Start marking the full check here ========= Skript v.2023-10-10 *** BASE SYSTEM *** Hardware Vendor : Intel Corporation Kernel : x86_64 Userland : amd64 Docker : v9.0.1 Virtualization : Docker Kernel : x86_64 Userland : amd64 Systemuptime and Load: 21:28:34 up 3 days, 6:55, 0 user, load average: 2.40, 2.10, 1.88 CPU threads: 4 *** Time and Time Zones *** Mon Jan 22 20:28:34 UTC 2024 Mon Jan 22 21:28:34 CET 2024 CET +0100 Etc/UTC *** User and Groups *** root /root root *** X-Server-Setup *** X-Server: false Desktop: Terminal: *** MEMORY *** total used free shared buff/cache available Mem: 1.0G 914M 122M 2.7M 250M 122M Swap: 2.8G 699M 2.1G Total: 3.8G 1.6G 2.2G 988 M total memory 871 M used memory 197 M active memory 257 M inactive memory 116 M free memory 13 M buffer memory 225 M swap cache 2641 M total swap 667 M used swap 1974 M free swap *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on none aufs 3.6T 1.7T 2.0T 47% / tmpfs tmpfs 64M 0 64M 0% /dev tmpfs tmpfs 495M 0 495M 0% /sys/fs/cgroup shm tmpfs 64M 0 64M 0% /dev/shm /dev/mapper/cachedev_0 ext4 3.6T 1.7T 2.0T 47% /opt/iobroker tmpfs tmpfs 495M 0 495M 0% /proc/acpi tmpfs tmpfs 495M 0 495M 0% /proc/scsi tmpfs tmpfs 495M 0 495M 0% /sys/firmware Messages concerning ext4 filesystem in dmesg: [Fri Jan 19 14:34:06 2024] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [Fri Jan 19 14:34:08 2024] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [Fri Jan 19 14:34:08 2024] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null) [Fri Jan 19 14:34:13 2024] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [Fri Jan 19 14:34:14 2024] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: barrier=1 [Fri Jan 19 14:34:34 2024] EXT4-fs (dm-0): barriers disabled [Fri Jan 19 14:34:35 2024] EXT4-fs (dm-0): mounted filesystem with writeback data mode. Opts: usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,synoacl,oldalloc [Fri Jan 19 14:34:49 2024] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null) Show mounted filesystems \(real ones only\): TARGET SOURCE FSTYPE OPTIONS / none aufs rw,relatime,si=e20874a76f97f35,dio,dirperm1 |-/opt/iobroker /dev/mapper/cachedev_0[/docker/iobroker_data] ext4 rw,nodev,relatime,journal_checksum,synoacl,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group |-/etc/resolv.conf /dev/mapper/cachedev_0[/@docker/containers/fc8a2d4a9b91b0684e008a4d386fa591d0ba1fc92d86287615aa9ec6f7ba5ff4/resolv.conf] ext4 rw,nodev,relatime,journal_checksum,synoacl,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group |-/etc/hostname /dev/mapper/cachedev_0[/@docker/containers/fc8a2d4a9b91b0684e008a4d386fa591d0ba1fc92d86287615aa9ec6f7ba5ff4/hostname] ext4 rw,nodev,relatime,journal_checksum,synoacl,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group `-/etc/hosts /dev/mapper/cachedev_0[/@docker/containers/fc8a2d4a9b91b0684e008a4d386fa591d0ba1fc92d86287615aa9ec6f7ba5ff4/hosts] ext4 rw,nodev,relatime,journal_checksum,synoacl,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group Files in neuralgic directories: /var: 34M /var/ 32M /var/lib 19M /var/lib/apt/lists 19M /var/lib/apt 13M /var/lib/dpkg /opt/iobroker/backups: 54M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 109M /opt/iobroker/iobroker-data/ 62M /opt/iobroker/iobroker-data/files 33M /opt/iobroker/iobroker-data/backup-objects 30M /opt/iobroker/iobroker-data/files/web.admin/static 30M /opt/iobroker/iobroker-data/files/web.admin The five largest files in iobroker-data are: 21M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.aaea95f8.js.map 8.3M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.aaea95f8.js 8.2M /opt/iobroker/iobroker-data/objects.jsonl 6.3M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_js-node_modules_iobr-99c23e.847b8ad9.chunk.js.map 5.9M /opt/iobroker/iobroker-data/states.jsonl USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/* in your adapter setups, please always prefer the links 'by-id': find: '/dev/serial/by-id/': No such file or directory *** NodeJS-Installation *** /usr/bin/nodejs v18.19.0 /usr/bin/node v18.19.0 /usr/bin/npm 10.2.3 /usr/bin/npx 10.2.3 /usr/bin/corepack 0.22.0 nodejs: Installed: 18.19.0-1nodesource1 Candidate: 18.19.0+dfsg-6~deb12u1 Version table: 18.19.0+dfsg-6~deb12u1 500 500 http://deb.debian.org/debian-security bookworm-security/main amd64 Packages *** 18.19.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 18.18.2-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.17.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.17.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.15.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.2-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.13.0+dfsg1-1 500 500 http://deb.debian.org/debian bookworm/main amd64 Packages 18.13.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.12.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.11.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.10.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.8.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.7.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.6.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.5.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.4.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.3.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.2.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.1.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.0.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Core adapters versions js-controller: 5.0.17 admin: 6.12.0 javascript: "javascript" not found Adapters from github: 0 Adapter State system.adapter.admin.0 : admin : iobroker - disabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.admin.1 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.backitup.0 : backitup : iobroker - disabled + system.adapter.discovery.0 : discovery : iobroker - enabled system.adapter.hm-rega.0 : hm-rega : iobroker - disabled system.adapter.hm-rpc.0 : hm-rpc : iobroker - disabled, port: 0 system.adapter.hm-rpc.1 : hm-rpc : iobroker - disabled, port: 0 system.adapter.influxdb.0 : influxdb : iobroker - disabled, port: 8086 system.adapter.vis.0 : vis : iobroker - disabled system.adapter.web.0 : web : iobroker - disabled, port: 8082, bind: 0.0.0.0, run as: admin + instance is alive Enabled adapters with bindings + system.adapter.admin.1 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin ioBroker-Repositories stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json Active repo(s): stable Installed ioBroker-Instances Used repository: stable Adapter "admin" : 6.12.0 , installed 6.12.0 Adapter "backitup" : 2.9.8 , installed 2.8.7 [Updatable] Adapter "discovery" : 4.2.0 , installed 4.2.0 Adapter "hm-rega" : 4.0.0 , installed 4.0.0 Adapter "hm-rpc" : 1.15.19 , installed 1.15.19 Adapter "influxdb" : 3.2.0 , installed 3.2.0 Controller "js-controller": 5.0.17 , installed 5.0.17 Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "socketio" : 6.6.0 , installed 6.6.0 Adapter "vis" : 1.5.4 , installed 1.4.16 [Updatable] Adapter "web" : 6.1.10 , installed 6.1.10 Adapter "ws" : 2.5.8 , installed 2.5.8 Objects and States Please stand by - This may take a while Objects: 299 States: 279 *** OS-Repositories and Updates *** Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://deb.debian.org/debian bookworm-updates InRelease Hit:3 http://deb.debian.org/debian-security bookworm-security InRelease Hit:4 https://deb.nodesource.com/node_18.x nodistro InRelease Reading package lists... Pending Updates: 0 *** Listening Ports *** Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1000 13473077 - tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1000 13475539 - tcp6 0 0 :::8081 :::* LISTEN 1000 13475621 - udp 0 0 0.0.0.0:8472 0.0.0.0:* 0 13470984 - *** Log File - Last 25 Lines *** 2024-01-22 16:07:27.139 - info: host.iobroker Delete state "system.host.iobroker.versions.nodeCurrent" 2024-01-22 16:07:27.142 - info: host.iobroker 10 instances found 2024-01-22 16:07:27.186 - info: host.iobroker starting 2 instances 2024-01-22 16:07:27.303 - info: host.iobroker Delete state "system.host.iobroker.versions.nodeNewest" 2024-01-22 16:07:27.332 - info: host.iobroker instance system.adapter.admin.1 started with pid 184 2024-01-22 16:07:27.355 - info: host.iobroker Delete state "system.host.iobroker.versions.nodeNewestNext" 2024-01-22 16:07:27.369 - info: host.iobroker Delete state "system.host.iobroker.versions.npmCurrent" 2024-01-22 16:07:27.384 - info: host.iobroker Delete state "system.host.iobroker.versions.npmNewest" 2024-01-22 16:07:27.399 - info: host.iobroker Delete state "system.host.iobroker.versions.npmNewestNext" 2024-01-22 16:07:27.413 - info: host.iobroker Some obsolete host states deleted. 2024-01-22 16:07:31.285 - info: host.iobroker instance system.adapter.discovery.0 started with pid 191 2024-01-22 16:07:33.257 - info: admin.1 (184) starting. Version 6.12.0 in /opt/iobroker/node_modules/iobroker.admin, node: v18.19.0, js-controller: 5.0.17 2024-01-22 16:07:33.351 - info: admin.1 (184) requesting all objects 2024-01-22 16:07:34.689 - info: admin.1 (184) received all objects 2024-01-22 16:07:35.573 - info: discovery.0 (191) starting. Version 4.2.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v18.19.0, js-controller: 5.0.17 2024-01-22 16:07:36.683 - info: admin.1 (184) socket.io server listening on port 8081 2024-01-22 16:07:36.689 - info: admin.1 (184) http server listening on port 8081 2024-01-22 16:07:36.690 - info: admin.1 (184) Use link "http://127.0.0.1:8081" to configure. 2024-01-22 21:24:48.076 - info: admin.1 (184) ==> Connected system.user.admin from ::ffff:172.17.0.1 2024-01-22 21:24:50.064 - error: host.iobroker cannot call visUtils: Not exists 2024-01-22 21:25:03.083 - error: host.iobroker cannot call visUtils: Not exists 2024-01-22 21:26:22.491 - info: admin.1 (184) ==> Connected system.user.admin from ::ffff:172.17.0.1 2024-01-22 21:26:23.290 - error: host.iobroker cannot call visUtils: Not exists 2024-01-22 21:26:24.364 - info: admin.1 (184) <== Disconnect system.user.admin from ::ffff:172.17.0.1 admin ============ Mark until here for C&P =============und hier die summary:
======================= SUMMARY ======================= v.2023-10-10 model name : Intel(R) Atom(TM) CPU D2701 @ 2.13GHz Kernel : x86_64 Userland : amd64 Docker : v9.0.1 Installation: Docker Kernel: x86_64 Userland: amd64 Timezone: Etc/UTC User-ID: 0 X-Server: false Pending OS-Updates: 0 Pending iob updates: 2 Nodejs-Installation: /usr/bin/nodejs v18.19.0 /usr/bin/node v18.19.0 /usr/bin/npm 10.2.3 /usr/bin/npx 10.2.3 /usr/bin/corepack 0.22.0 Recommended versions are nodejs 18.19.0 and npm 10.2.3 Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 1.0G 901M 134M 2.8M 248M 134M Swap: 2.8G 710M 2.1G Total: 3.8G 1.6G 2.2G Active iob-Instances: 3 Active repo(s): stable ioBroker Core: js-controller 5.0.17 admin 6.12.0 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: system.adapter.admin.0 : admin : iobroker - disabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.admin.1 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.web.0 : web : iobroker - disabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 299 States: 279 Size of iob-Database: 8.2M /opt/iobroker/iobroker-data/objects.jsonl 5.9M /opt/iobroker/iobroker-data/states.jsonl =================== END OF SUMMARY ==================== -
@hmuser sagte in Admin startet nicht - buanet image:
Der Admin Adapter ist disabled, lässt sich aber in der Konsole nicht starten
und was kommt dann in der Konsole wenn du
iob start adminmachst !?
Was steht sonst im Log !?
In Portainer steht der iobroker Container auf "healthy", nicht auf "running"
healthy ist richtig !
Zeige mal was du so hast :
Full Ausgabe von
iob diagaber bitte in Code-Tags </>
Das Ergebnis von Job start admin:
root@iobroker:/opt/iobroker# iob start admin
The execution of this command is blocked as your ioBroker is running inside a Docker container!
For more details see ioBroker Docker image docs (https://docs.buanet.de/iobroker-docker-image/docs/) or use the maintenance script 'maintenance --help'.Synology 713+
IOBroker im Dockerumfeld auf Synology
Raspimatic -
Das Ergebnis von Job start admin:
root@iobroker:/opt/iobroker# iob start admin
The execution of this command is blocked as your ioBroker is running inside a Docker container!
For more details see ioBroker Docker image docs (https://docs.buanet.de/iobroker-docker-image/docs/) or use the maintenance script 'maintenance --help'. -
@hmuser sagte in Admin startet nicht - buanet image:
- system.adapter.admin.1 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin
Admin ist da ... und auch an !?
@glasfaser
Hatte zusätzlich admin.1 installiert. Ist aber auch nicht erreichbar über 8081 bzw. 8089 (so gemapt) -
@hmuser sagte in Admin startet nicht - buanet image:
- system.adapter.admin.1 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin
Admin ist da ... und auch an !?
admin.1 ist jetzt erreichbar über 8081, obwohl gemapt auf 8089, verstehe ich nicht. aber immerhin läuft er jetzt.
Also jetzt noch das neue image ziehen und dann müsste admin start auch wieder funktionieren, korrekt?
Danke für Deine Hilfe!Synology 713+
IOBroker im Dockerumfeld auf Synology
Raspimatic -
admin.1 ist jetzt erreichbar über 8081, obwohl gemapt auf 8089, verstehe ich nicht. aber immerhin läuft er jetzt.
Also jetzt noch das neue image ziehen und dann müsste admin start auch wieder funktionieren, korrekt?
Danke für Deine Hilfe! -
@glasfaser
Anfängerfrage: in welcher Konsole/ welchem Verzeichnis sind die Befehle auszuführen? -
@hmuser sagte in Admin startet nicht - buanet image:
in welcher Konsole/
in der Synology Ebene / ( über Putty auf die Synology , also nicht zum Container )
-
@glasfaser
Also über ssl auf der Syno einloggen? oder geht das im Docker Paket? -
@hmuser sagte in Admin startet nicht - buanet image:
oder geht das im Docker Paket?
Nein ... siehe oben
adminle@DS_backup:~$ docker ps Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/json": dial unix /var/run/docker.sock: connect: permission denied adminle@DS_backup:~$ docker exec iobroker env Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/iobroker/json": dial unix /var/run/docker.sock: connect: permission denied adminle@DS_backup:~$Synology 713+
IOBroker im Dockerumfeld auf Synology
Raspimatic -
adminle@DS_backup:~$ docker ps Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/json": dial unix /var/run/docker.sock: connect: permission denied adminle@DS_backup:~$ docker exec iobroker env Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/iobroker/json": dial unix /var/run/docker.sock: connect: permission denied adminle@DS_backup:~$ -
adminle@DS_backup:~$ sudo docker exec iobroker env Password: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin HOSTNAME=iobroker DEBIAN_FRONTEND=teletype LANG=de_DE.UTF-8 LANGUAGE=de_DE:de LC_ALL=de_DE.UTF-8 SETGID=1000 SETUID=1000 TZ=Europe/Berlin HOME=/root adminle@DS_backup:~$ sudo docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES fc8a2d4a9b91 buanet/iobroker:latest "/bin/bash -c /opt/s…" 5 days ago Up 6 hours (healthy) 0.0.0.0:2001->2001/tcp, 0.0.0.0:2010->2010/tcp, 0.0.0.0:3307->3307/tcp, 0.0.0.0:8081-8082->8081-8082/tcp iobroker 4697a92fbc3b portainer/portainer-ce "/portainer" 8 days ago Up 3 days 8000/tcp, 9443/tcp, 0.0.0.0:8889->9000/tcp portainer adminle@DS_backup:~$Synology 713+
IOBroker im Dockerumfeld auf Synology
Raspimatic -
adminle@DS_backup:~$ sudo docker exec iobroker env Password: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin HOSTNAME=iobroker DEBIAN_FRONTEND=teletype LANG=de_DE.UTF-8 LANGUAGE=de_DE:de LC_ALL=de_DE.UTF-8 SETGID=1000 SETUID=1000 TZ=Europe/Berlin HOME=/root adminle@DS_backup:~$ sudo docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES fc8a2d4a9b91 buanet/iobroker:latest "/bin/bash -c /opt/s…" 5 days ago Up 6 hours (healthy) 0.0.0.0:2001->2001/tcp, 0.0.0.0:2010->2010/tcp, 0.0.0.0:3307->3307/tcp, 0.0.0.0:8081-8082->8081-8082/tcp iobroker 4697a92fbc3b portainer/portainer-ce "/portainer" 8 days ago Up 3 days 8000/tcp, 9443/tcp, 0.0.0.0:8889->9000/tcp portainer adminle@DS_backup:~$ -
@hmuser sagte in Admin startet nicht - buanet image:
8081-8082
Kann man machen .... von bis , bin aber kein Freund davon, lieber einzeln
8081 : 8081 8082 : 8082
637
Online32.4k
Benutzer81.4k
Themen1.3m
Beiträge