Admin startet nicht - buanet image[gelöst]
-
@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:~$ -
sudo docker ps sudo docker exec iobroker env -
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 -
@glasfaser
Das kann ich noch ändern wenn ich das neue image ziehe.
Habe das hier noch im Log:Cannot get NPM version: timeoutMuss ich da noch etwas verändern?
-
-
@glasfaser
Hm, wollte jetzt mit der Vorgehensweise des obigen Threads weitermachen, aber jetzt funktioniert iobroker stop etc. wieder nicht. hatte vermeintlich das neueste Image gezogen mit "recreate". muss ich eine spezielle Version fordern? -
@glasfaser
Inzwischen ist 9.1.0 installiert, aber iob start/ stop funktioniert trotzdem nicht.
Gibt es vielleicht noch eine andere Ursache? -
@hmuser sagte in Admin startet nicht - buanet image:
aber iob start/ stop funktioniert trotzdem nicht.
Was meinst du damit .
Es ging hier um die Instanz
iob start admin.0 -
@hmuser sagte in Admin startet nicht - buanet image:
aber jetzt funktioniert iobroker stop etc. wieder nicht.
das gab es noch nie im Container , dazu gibt es
pkill -u iobroker -
@glasfaser
Ok, super, start admin funktioniert jetzt, vielen Dank. Das mit pkill war mir nicht klar. -
@hmuser sagte in Admin startet nicht - buanet image:
Ok, super, start admin funktioniert jetzt,
???
und warum vorhin nicht !? -
@hmuser sagte in Admin startet nicht - buanet image:
Inzwischen ist 9.1.0 installiert,
kannst du bitte die Full Ausgabe von
iob diagdavon mal zeigen !
-
@glasfaser
Hatte es nur iob stop probiert - der Hinweis des Programms ist dann der gleiche. Das iob stop gar nicht zulässig ist war mir nicht klar. -
Skript v.2023-10-10 *** BASE SYSTEM *** Hardware Vendor : Intel Corporation Kernel : x86_64 Userland : amd64 Docker : v9.1.0 Virtualization : Docker Kernel : x86_64 Userland : amd64 Systemuptime and Load: 21:34:54 up 4 days, 7:01, 0 user, load average: 2.68, 2.29, 2.18 CPU threads: 4 *** Time and Time Zones *** Tue Jan 23 20:34:54 UTC 2024 Tue Jan 23 21:34:54 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 915M 120M 3.0M 230M 120M Swap: 2.8G 727M 2.0G Total: 3.8G 1.6G 2.2G 988 M total memory 873 M used memory 195 M active memory 239 M inactive memory 115 M free memory 8 M buffer memory 211 M swap cache 2641 M total swap 693 M used swap 1948 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=e20874a68cf9f35,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/b7b29cf44ccd7e3917f6654705dce653b19400dcfc8a57fc13178d0aa6077bba/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/b7b29cf44ccd7e3917f6654705dce653b19400dcfc8a57fc13178d0aa6077bba/hostname] ext4 rw,nodev,relatime,journal_checksum,synoacl,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group `-/etc/hosts /dev/mapper/cachedev_0[/@docker/containers/b7b29cf44ccd7e3917f6654705dce653b19400dcfc8a57fc13178d0aa6077bba/hosts] ext4 rw,nodev,relatime,journal_checksum,synoacl,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group Files in neuralgic directories: /var: 38M /var/ 35M /var/lib 19M /var/lib/apt/lists 19M /var/lib/apt 17M /var/lib/dpkg /opt/iobroker/backups: 54M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 114M /opt/iobroker/iobroker-data/ 62M /opt/iobroker/iobroker-data/files 34M /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 13M /opt/iobroker/iobroker-data/objects.jsonl 8.3M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.aaea95f8.js 6.7M /opt/iobroker/iobroker-data/states.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 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-1nodesource1 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 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 18.18.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.17.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.0-1nodesource1 1001 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 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.0.0-1nodesource1 1001 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 - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.admin.1 : 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 + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : 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.9.8 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.5.4 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: 271 *** 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 17400825 - tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1000 17407578 - tcp6 0 0 :::8081 :::* LISTEN 1000 19043686 - udp 0 0 0.0.0.0:8472 0.0.0.0:* 0 17394061 - *** Log File - Last 25 Lines *** 2024-01-23 21:22:27.635 - info: admin.1 (227) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2024-01-23 21:22:27.532 - info: host.iobroker stopInstance system.adapter.admin.1 (force=false, process=true) 2024-01-23 21:22:27.666 - info: host.iobroker stopInstance system.adapter.admin.1 send kill signal 2024-01-23 21:22:28.138 - info: admin.1 (227) terminating 2024-01-23 21:22:28.201 - error: admin.1 (227) Cannot find view "system" for search "instance" : Connection is closed. 2024-01-23 21:22:28.692 - info: host.iobroker stopInstance system.adapter.admin.1 killing pid 227 2024-01-23 21:22:29.192 - info: host.iobroker instance system.adapter.admin.1 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2024-01-23 21:24:09.233 - info: host.iobroker "system.adapter.admin.0" enabled 2024-01-23 21:24:09.473 - info: host.iobroker instance system.adapter.admin.0 started with pid 24575 2024-01-23 21:24:16.245 - info: admin.0 (24575) starting. Version 6.12.0 in /opt/iobroker/node_modules/iobroker.admin, node: v18.19.0, js-controller: 5.0.17 2024-01-23 21:24:16.315 - info: admin.0 (24575) requesting all objects 2024-01-23 21:24:18.107 - info: admin.0 (24575) received all objects 2024-01-23 21:24:19.773 - info: admin.0 (24575) Request actual repository... 2024-01-23 21:24:19.983 - error: host.iobroker cannot call visUtils: Not exists 2024-01-23 21:24:20.046 - info: admin.0 (24575) socket.io server listening on port 8081 2024-01-23 21:24:20.151 - info: admin.0 (24575) http server listening on port 8081 2024-01-23 21:24:20.152 - info: admin.0 (24575) Use link "http://127.0.0.1:8081" to configure. 2024-01-23 21:24:21.041 - info: host.iobroker Updating repository "stable" under "http://download.iobroker.net/sources-dist.json" 2024-01-23 21:24:29.941 - info: admin.0 (24575) Repository received successfully. 2024-01-23 21:24:31.334 - info: admin.0 (24575) failed connection to socket.io from ::ffff:172.17.0.1: Passport was not initialized 2024-01-23 21:24:42.251 - info: admin.0 (24575) ==> Connected system.user.admin from ::ffff:172.17.0.1 2024-01-23 21:24:51.278 - error: host.iobroker cannot call visUtils: Not exists 2024-01-23 21:25:27.271 - error: host.iobroker cannot call visUtils: Not exists 2024-01-23 21:33:39.133 - info: admin.0 (24575) <== Disconnect system.user.admin from ::ffff:172.17.0.1 admin 2024-01-23 21:35:17.076 - info: admin.0 (24575) failed connection to socket.io from ::ffff:172.17.0.1: Passport was not initialized============ Mark until here for C&P =============
-
@glasfaser
Jetzt läuft soweit alles - das einzige was mir noch unklar ist: Im docker ist nur der portainer als Container sichtbar, iobroker nicht: das kenne ich von einer anderen Installation nicht so. -
Hattest du nicht schonmal diese Problem !?
Würde mal Portainer als app deinstallieren , neustes Image laden und dann neu installieren
-
Nein, das hatte ich noch nicht.
Portainer habe ich über die Konsole installiert, ist das auch eine app auf der Synology? -
Einfach den Container löschen ... über die Syn Docker Konsole
