Keine Geräterkennung in Proxmox LXC Container Installation
-
@dp20eic Hallo Danke für den Tipp.
hier der Dialog.
Skript v.2023-10-10 *** BASE SYSTEM *** Static hostname: Proxmox181 Icon name: computer-container Chassis: container Virtualization: lxc Operating System: Ubuntu 22.04.3 LTS Kernel: Linux 6.2.16-3-pve Architecture: x86-64 model name : Intel(R) N95 Docker : false Virtualization : lxc Kernel : x86_64 Userland : amd64 Systemuptime and Load: 16:38:56 up 1 day, 7:23, 2 users, load average: 0.07, 0.14, 0.15 CPU threads: 4 *** Time and Time Zones *** Local time: Sun 2023-11-05 16:38:56 CET Universal time: Sun 2023-11-05 15:38:56 UTC RTC time: n/a Time zone: Europe/Berlin (CET, +0100) System clock synchronized: yes NTP service: inactive RTC in local TZ: no *** User and Groups *** aro /home/aro aro sudo iobroker *** X-Server-Setup *** X-Server: false Desktop: Terminal: Boot Target: graphical.target *** MEMORY *** total used free shared buff/cache available Mem: 4.1G 882M 2.7G 0.0K 515M 3.2G Swap: 512M 0.0K 511M Total: 4.6G 882M 3.2G 4096 M total memory 883 M used memory 170 M active memory 1160 M inactive memory 2697 M free memory 0 M buffer memory 515 M swap cache 512 M total swap 0 M used swap 511 M free swap *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION * run-rpc_pipefs.mount loaded failed failed RPC Pipe File System LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. 1 loaded units listed. *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/pve-vm--181--disk--0 ext4 63G 2.4G 57G 4% / none tmpfs 492K 4.0K 488K 1% /dev tmpfs tmpfs 7.7G 0 7.7G 0% /dev/shm tmpfs tmpfs 3.1G 116K 3.1G 1% /run tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock Messages concerning ext4 filesystem in dmesg: dmesg: read kernel buffer failed: Operation not permitted Show mounted filesystems \(real ones only\): TARGET SOURCE FSTYPE OPTIONS / /dev/mapper/pve-vm--181--disk--0 ext4 rw,relatime,stripe=16 Files in neuralgic directories: /var: 516M /var/ 251M /var/lib 239M /var/cache 232M /var/cache/apt 156M /var/lib/apt/lists Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. Archived and active journals take up 8.0M in the file system. /opt/iobroker/backups: 14M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 166M /opt/iobroker/iobroker-data/ 123M /opt/iobroker/iobroker-data/files 52M /opt/iobroker/iobroker-data/files/javascript.admin 34M /opt/iobroker/iobroker-data/files/javascript.admin/static 33M /opt/iobroker/iobroker-data/files/javascript.admin/static/js The five largest files in iobroker-data are: find: Failed to change directory: /root: Permission denied find: Failed to restore initial working directory: /root: Permission denied 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 find: Failed to restore initial working directory: /root: Permission denied *** NodeJS-Installation *** /usr/bin/nodejs v18.18.2 /usr/bin/node v18.18.2 /usr/bin/npm 9.8.1 /usr/bin/npx 9.8.1 /usr/bin/corepack 0.19.0 nodejs: Installed: 18.18.2-1nodesource1 Candidate: 18.18.2-1nodesource1 Version table: *** 18.18.2-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 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-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 12.22.9~dfsg-1ubuntu3.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-security/universe amd64 Packages 12.22.9~dfsg-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages find: Failed to restore initial working directory: /root: Permission denied 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.12 admin: 6.12.0 javascript: 7.1.4 Adapters from github: 0 Adapter State + system.adapter.admin.0 : admin : Proxmox181 - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.backitup.0 : backitup : Proxmox181 - enabled + system.adapter.discovery.0 : discovery : Proxmox181 - enabled + system.adapter.history.0 : history : Proxmox181 - enabled + system.adapter.jarvis.0 : jarvis : Proxmox181 - enabled + system.adapter.javascript.0 : javascript : Proxmox181 - enabled + system.adapter.shelly.0 : shelly : Proxmox181 - enabled, port: 1882, bind: 0.0.0.0 system.adapter.vis.0 : vis : Proxmox181 - enabled + system.adapter.web.0 : web : Proxmox181 - enabled, port: 8082, bind: 0.0.0.0, run as: admin + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : Proxmox181 - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.shelly.0 : shelly : Proxmox181 - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.web.0 : web : Proxmox181 - enabled, port: 8082, 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.8.7 , installed 2.8.7 Adapter "discovery" : 3.1.0 , installed 3.1.0 Adapter "history" : 3.0.1 , installed 3.0.1 Adapter "jarvis" : 3.1.8 , installed 3.1.8 Adapter "javascript" : 7.1.4 , installed 7.1.4 Controller "js-controller": 5.0.12 , installed 5.0.12 Adapter "shelly" : 6.4.5 , installed 6.4.5 Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "socketio" : 6.5.5 , installed 6.5.5 Adapter "vis" : 1.4.16 , installed 1.4.16 Adapter "web" : 6.1.4 , installed 6.1.2 [Updatable] Adapter "ws" : 2.5.5 , installed 2.5.5 Objects and States Please stand by - This may take a while Objects: 292 States: 222 *** OS-Repositories and Updates *** Hit:1 https://deb.nodesource.com/node_18.x nodistro InRelease Hit:2 http://archive.ubuntu.com/ubuntu jammy InRelease Hit:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease Hit:4 http://archive.ubuntu.com/ubuntu jammy-security 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 0.0.0.0:111 0.0.0.0:* LISTEN 0 35138774 1/init tcp 0 0 0.0.0.0:8400 0.0.0.0:* LISTEN 1001 35141083 402/io.jarvis.0 tcp 0 0 0.0.0.0:1882 0.0.0.0:* LISTEN 1001 35325246 1098/io.shelly.0 tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 35139904 113/iobroker.js-con tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 35137968 113/iobroker.js-con tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 0 35138081 296/master tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 106 35140671 107/systemd-resolve tcp6 0 0 :::111 :::* LISTEN 0 35138776 1/init tcp6 0 0 :::22 :::* LISTEN 0 35137509 1/init tcp6 0 0 ::1:25 :::* LISTEN 0 35138082 296/master tcp6 0 0 :::8081 :::* LISTEN 1001 35140735 149/io.admin.0 tcp6 0 0 :::8082 :::* LISTEN 1001 35140974 387/io.web.0 udp 0 0 0.0.0.0:5678 0.0.0.0:* 1001 35147332 357/io.discovery.0 udp 0 0 127.0.0.53:53 0.0.0.0:* 106 35140670 107/systemd-resolve udp 0 0 192.168.1.181:68 0.0.0.0:* 105 35139848 84/systemd-networkd udp 0 0 0.0.0.0:111 0.0.0.0:* 0 35138775 1/init udp6 0 0 :::111 :::* 0 35138777 1/init *** Log File - Last 25 Lines *** 2023-11-05 14:09:32.083 - error: host.Proxmox181 cannot call visUtils: Not exists 2023-11-05 14:10:11.797 - info: discovery.0 (357) Discovering devices with a HF-LPB100 chipset... 2023-11-05 14:10:11.799 - info: discovery.0 (357) Discovering mDNS devices... 2023-11-05 14:10:11.800 - info: discovery.0 (357) Discovering ping devices... 2023-11-05 14:10:11.809 - info: discovery.0 (357) Done discovering serial devices. 0 packages received 2023-11-05 14:10:11.811 - info: discovery.0 (357) Discovering UPnP devices... 2023-11-05 14:10:11.812 - info: discovery.0 (357) Discovering wifi-mi-light devices... 2023-11-05 14:10:11.850 - warn: discovery.0 (357) tr-064.0 not installed 2023-11-05 14:10:11.850 - info: discovery.0 (357) Done discovering tr064 devices. 0 packages received 2023-11-05 14:10:13.812 - info: discovery.0 (357) Done discovering wifi-mi-light devices. 0 packages received 2023-11-05 14:10:16.809 - info: discovery.0 (357) Done discovering udp devices. 1 packages received 2023-11-05 14:10:21.801 - info: discovery.0 (357) Done discovering HF-LPB100 devices. 0 packages received 2023-11-05 14:10:25.761 - info: discovery.0 (357) Done discovering ping devices. 1 packages received 2023-11-05 14:10:26.801 - info: discovery.0 (357) Done discovering mdns devices. 3 packages received 2023-11-05 14:10:26.812 - info: discovery.0 (357) Done discovering upnp devices. 89 packages received 2023-11-05 14:10:28.353 - info: discovery.0 (357) Found 13 addresses 2023-11-05 14:10:38.515 - info: discovery.0 (357) Discovery finished. Found new or modified 68 instances 2023-11-05 14:10:38.542 - info: discovery.0 (357) Discovery finished 2023-11-05 15:10:52.360 - info: admin.0 (149) <== Disconnect system.user.admin from ::ffff:192.168.1.143 admin 2023-11-05 16:33:39.866 - info: admin.0 (149) failed connection to socket.io from ::ffff:192.168.1.143: Passport was not initialized 2023-11-05 16:34:12.804 - info: admin.0 (149) ==> Connected system.user.admin from ::ffff:192.168.1.143 2023-11-05 16:34:12.909 - error: host.Proxmox181 cannot call visUtils: Not exists 2023-11-05 16:35:57.108 - info: admin.0 (149) ==> Connected system.user.admin from ::ffff:192.168.1.143 2023-11-05 16:36:03.263 - info: admin.0 (149) <== Disconnect system.user.admin from ::ffff:192.168.1.143 javascript 2023-11-05 16:39:13.144 - error: host.Proxmox181 cannot call visUtils: Not exists============ Mark until here for C&P =============
iob diag has finished.
-
@aro65 bitte den Text in CODETAGS hier posten, danke.
-
@djmarc75 Hallo, danke dir mache ich morgen und melde dich. Sorry fange gerade erst an !
-
@aro65 Melde mich natürlich
-
@aro65 sagte in Keine Geräterkennung in Proxmox LXC Container Installation:
find: Failed to change directory: /root: Permission denied
Du stehst in Verzeichnissen herum, in denen du nichts verloren hast.
Und füg den
aroin die Gruppeadmein.sudo usermod -a -G adm aro exit -
@aro65 sagte in Keine Geräterkennung in Proxmox LXC Container Installation:
Sorry fange gerade erst an !
Na dann:
https://forum.iobroker.net/topic/51555/hinweise-für-gute-forenbeiträge -
@aro65 meine Meinung:
Iob in eine VM, den discovery Adapter braucht man nicht.
Warum Ubuntu? -
@aro65 sagte in Keine Geräterkennung in Proxmox LXC Container Installation:
@djmarc75 Hallo, danke dir mache ich morgen und melde dich. Sorry fange gerade erst an !
dann rein aus Neugierde:
Warum Container mit all seinen Stolperfallen und Warum Ubuntu? -
@homoran Tja, wie gesagt, ich fange erst an und kann hier nur bedingt mitreden.-. Habe mich mit Youtube Videos durchgehangelt und fand die Proxmox Installation mit den Containern interessant . Ubuntu wurde dort als Template empfohlen. Das hat ja auch eigentlich gut funktioniert
Ich werde dann nochmal die VM Installation in Proxmox versuchen.
Welches Linux ist den zu empfehlen ? Spricht etwas gegen Ubuntu ?
Danke und Gruß Andreas
-
@aro65 sagte in Keine Geräterkennung in Proxmox LXC Container Installation:
Welches Linux ist den zu empfehlen ? Spricht etwas gegen Ubuntu ?
Ich würde das Original (Debian) immer der Kopie vorziehen.
-
@thomas-braun Danke Dir, teste ich. Das Forum ist klasse muss ich sagen und das man als Anfänger nicht gleich rund gemacht wird.
Grüße und noch einen schönen Abend Euch Allen
-
@aro65 ja, da wird sehr gerne geholfen!
Die YT Videos sind meist uralt und großteils Mumpitz.
Da bekommt man immer alles frisch. -
@da_woody sagte in Keine Geräterkennung in Proxmox LXC Container Installation:
Da bekommt man immer alles frisch.
Moin,
da hat der liebe @da_Woody wohl den Link vergessen ⇒ https://www.iobroker.net/#de/documentation/install/proxmox.md
VG
Bernd
