NEWS
[Neuer Adapter] Proxmox VM
-
Hallo
Hat noch jemand das Problem mit
has no existing object, this might lead to an error in future versions?Issue hab ich gerade erstellt.
@negalein welche adapter version..ahh ich seh 2.2.0
da wurde das object nicht angelegt
proxmox.0.storage_proxmox_local-lvmlösche den mal .. und starte den adapter neu
zigbee hab ich, zwave auch, nuc's genauso und HA auch
-
@negalein welche adapter version..ahh ich seh 2.2.0
da wurde das object nicht angelegt
proxmox.0.storage_proxmox_local-lvmlösche den mal .. und starte den adapter neu
wenn du grad an dem Thema bist, ich hab mal alle Objects von Proxmox geloescht und den Adapter dann neu gestartet, hier kommt das bei den vmid , Adapter Version 2.2.0 :
2023-10-27 09:16:32.292 - info: host.themachine instance system.adapter.proxmox.0 started with pid 78860 2023-10-27 09:16:33.146 - info: proxmox.0 (78860) starting. Version 2.2.0 in /opt/iobroker/node_modules/iobroker.proxmox, node: v20.9.0, js-controller: 5.0.14 2023-10-27 09:16:33.156 - warn: proxmox.0 (78860) Using Proxmox API: https://192.168.0.210:8006/api2/json 2023-10-27 09:16:33.605 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.docker.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.672 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.bookworm-ilovegym.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.742 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.themachine.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.789 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.redis.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.826 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.octoprint.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.902 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.grafana.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.960 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.wireguard.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.023 - info: proxmox.0 (78860) State value to set for "proxmox.0.qemu.pfSense.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.054 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.Network-Test.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.141 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.node-red.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.219 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.uptimekuma.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.275 - info: proxmox.0 (78860) State value to set for "proxmox.0.qemu.iobroker.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.335 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.redisdb.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:32.256 - info: host.themachine "system.adapter.proxmox.0" enabled 2023-10-27 09:16:32.292 - info: host.themachine instance system.adapter.proxmox.0 started with pid 78860 2023-10-27 09:16:33.146 - info: proxmox.0 (78860) starting. Version 2.2.0 in /opt/iobroker/node_modules/iobroker.proxmox, node: v20.9.0, js-controller: 5.0.14 2023-10-27 09:16:33.156 - warn: proxmox.0 (78860) Using Proxmox API: https://192.168.0.210:8006/api2/json 2023-10-27 09:16:33.605 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.docker.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.672 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.bookworm-ilovegym.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.742 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.themachine.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.789 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.redis.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.826 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.octoprint.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.902 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.grafana.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.960 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.wireguard.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.023 - info: proxmox.0 (78860) State value to set for "proxmox.0.qemu.pfSense.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.054 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.Network-Test.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.141 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.node-red.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.219 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.uptimekuma.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.275 - info: proxmox.0 (78860) State value to set for "proxmox.0.qemu.iobroker.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.335 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.redisdb.vmid" has to be type "string" but received type "number" -
wenn du grad an dem Thema bist, ich hab mal alle Objects von Proxmox geloescht und den Adapter dann neu gestartet, hier kommt das bei den vmid , Adapter Version 2.2.0 :
2023-10-27 09:16:32.292 - info: host.themachine instance system.adapter.proxmox.0 started with pid 78860 2023-10-27 09:16:33.146 - info: proxmox.0 (78860) starting. Version 2.2.0 in /opt/iobroker/node_modules/iobroker.proxmox, node: v20.9.0, js-controller: 5.0.14 2023-10-27 09:16:33.156 - warn: proxmox.0 (78860) Using Proxmox API: https://192.168.0.210:8006/api2/json 2023-10-27 09:16:33.605 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.docker.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.672 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.bookworm-ilovegym.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.742 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.themachine.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.789 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.redis.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.826 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.octoprint.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.902 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.grafana.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.960 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.wireguard.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.023 - info: proxmox.0 (78860) State value to set for "proxmox.0.qemu.pfSense.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.054 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.Network-Test.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.141 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.node-red.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.219 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.uptimekuma.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.275 - info: proxmox.0 (78860) State value to set for "proxmox.0.qemu.iobroker.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.335 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.redisdb.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:32.256 - info: host.themachine "system.adapter.proxmox.0" enabled 2023-10-27 09:16:32.292 - info: host.themachine instance system.adapter.proxmox.0 started with pid 78860 2023-10-27 09:16:33.146 - info: proxmox.0 (78860) starting. Version 2.2.0 in /opt/iobroker/node_modules/iobroker.proxmox, node: v20.9.0, js-controller: 5.0.14 2023-10-27 09:16:33.156 - warn: proxmox.0 (78860) Using Proxmox API: https://192.168.0.210:8006/api2/json 2023-10-27 09:16:33.605 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.docker.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.672 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.bookworm-ilovegym.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.742 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.themachine.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.789 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.redis.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.826 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.octoprint.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.902 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.grafana.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.960 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.wireguard.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.023 - info: proxmox.0 (78860) State value to set for "proxmox.0.qemu.pfSense.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.054 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.Network-Test.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.141 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.node-red.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.219 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.uptimekuma.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.275 - info: proxmox.0 (78860) State value to set for "proxmox.0.qemu.iobroker.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.335 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.redisdb.vmid" has to be type "string" but received type "number" -
Proxmox V8.0.4
-
Adapter v2.2.0
Proxmox v8.0.4Löschen der Objekte und restart.
Ich habe den String proxmox.0.lxc_pihole.vmid nicht in den letzten 2 Tagen im Log gefunden, scheint also nur bei/mit/vor/nach dem Erstellen der States zu passieren. :)
2023-10-27 09:59:39.426 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_pihole.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:39.738 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_zigbee2mqtt.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:39.998 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_mqtt.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:40.287 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_influxdb.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:40.466 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_bind.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:40.774 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_mariadb.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:41.163 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_grafana.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:41.600 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_samba.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:41.718 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_scrypted.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:42.019 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_plex.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:42.223 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_wireguard.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:42.431 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_openssl.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:42.627 - info: proxmox.0 (1159091) State value to set for "proxmox.0.qemu_iobroker.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:42.794 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_iobroker-test.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:42.932 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_tautulli.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:43.177 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_wikijs.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:43.307 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_mediamtx.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:43.619 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_redis.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:43.760 - info: proxmox.0 (1159091) State value to set for "proxmox.0.qemu_iobroker-devel.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:43.917 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_bookworm-template-sudo-tim.vmid" has to be type "string" but received type "number" -
@arteck sagte in [Neuer Adapter] Proxmox VM:
isch guck später nach
... wenn du schon dabei bist... hier kam gerade waehrend des Backups des LXC, indem iobroker laeuft, diese Errors:
-
@arteck sagte in [Neuer Adapter] Proxmox VM:
isch guck später nach
... wenn du schon dabei bist... hier kam gerade waehrend des Backups des LXC, indem iobroker laeuft, diese Errors:
@ilovegym sagte in [Neuer Adapter] Proxmox VM:
/nodes/hpg380/storage/VMBackup/content
da ist der storage nicht da.. und da du nur 1 node hast oder nur angegeben hast, kann der nicht switchen
früher war die meldung unterdrückt
-
@ilovegym sagte in [Neuer Adapter] Proxmox VM:
/nodes/hpg380/storage/VMBackup/content
da ist der storage nicht da.. und da du nur 1 node hast oder nur angegeben hast, kann der nicht switchen
früher war die meldung unterdrückt
ja, weil er gerade am backup schreiben ist.. hmmpff d.h. die Meldung kommt jetzt immer, wenn ich ein Backup mache in Proxmox.. ? mit dem LXC.. ?
Kann man da das Timeout hoeher setzen.. fuer den Fehler? er kommt genau einmal, wie im Logfile, dann ist wieder ruhe.. -
@negalein welche adapter version..ahh ich seh 2.2.0
da wurde das object nicht angelegt
proxmox.0.storage_proxmox_local-lvmlösche den mal .. und starte den adapter neu
@arteck sagte in [Neuer Adapter] Proxmox VM:
lösche den mal .. und starte den adapter neu
Danke, funktioniert wieder.
-
ja, weil er gerade am backup schreiben ist.. hmmpff d.h. die Meldung kommt jetzt immer, wenn ich ein Backup mache in Proxmox.. ? mit dem LXC.. ?
Kann man da das Timeout hoeher setzen.. fuer den Fehler? er kommt genau einmal, wie im Logfile, dann ist wieder ruhe.. -
habe auch von git installiert.
Bitte noch überprüfen:
maxmem wird bei den Objekten nicht aktualisiert.sowohl dies:
als auch dies:
Wenn ich helfen konnte, dann Daumen hoch (Pfeil nach oben)!
Danke.
gute Forenbeiträge: https://forum.iobroker.net/topic/51555/hinweise-f%C3%BCr-gute-forenbeitr%C3%A4ge
ScreenToGif :https://www.screentogif.com/downloads.html -
habe auch von git installiert.
Bitte noch überprüfen:
maxmem wird bei den Objekten nicht aktualisiert.sowohl dies:
als auch dies:
-
@arteck
Na klar ist die Maschine an.Und ja, der DP wird bei start der Instanz aktualisiert.
Aber dann nicht mehr.Die anderen DP von mem werden dagegen regelmäßig (so alle 30 Sek.) aktualisiert.
Wenn ich helfen konnte, dann Daumen hoch (Pfeil nach oben)!
Danke.
gute Forenbeiträge: https://forum.iobroker.net/topic/51555/hinweise-f%C3%BCr-gute-forenbeitr%C3%A4ge
ScreenToGif :https://www.screentogif.com/downloads.html -
@arteck
Na klar ist die Maschine an.Und ja, der DP wird bei start der Instanz aktualisiert.
Aber dann nicht mehr.Die anderen DP von mem werden dagegen regelmäßig (so alle 30 Sek.) aktualisiert.
-
@arteck
Na klar ist die Maschine an.Und ja, der DP wird bei start der Instanz aktualisiert.
Aber dann nicht mehr.Die anderen DP von mem werden dagegen regelmäßig (so alle 30 Sek.) aktualisiert.
@bahnuhr sagte in [Neuer Adapter] Proxmox VM:
Und ja, der DP wird bei start der Instanz aktualisiert.
Aber dann nicht mehr.Moin,
max Mem. ist ja eher ein statischer Wert, der sich nicht laufend ändert, wohin gegen Mem. sich zur Laufzeit schon veränder, Du muss mal mit der Einstellung von MaxMem, spielen und dann schauen, ob die Änderung angezeigt wird.
VG
Bernd -
Neulich ist ja ein DP mit einer JSON der die Backups beinhaltet in den Adapter gekommen.
Ich habe da mal eine kleine Tabelle für meine Visu für gemacht.
Ist die Unterste Tabelle im ersten Post
https://forum.iobroker.net/topic/59661/zusammenstellung-meiner-tabellen?_=1701274643122
Edit:
@Meistertr
Wie oft wird die Datei mit den Infos über die Backups aktualisiert?
Durch die Tabelle habe ich jetzt gemerkt, dass es Teilweise Stunden braucht, bis ich aktuelle Daten bekomme. -
Seit dem ich die oben genannte Tabelle im Einsatz habe ist mir aufgefallen, dass mir der Adapter andauert abschmiert.
Mal nach ein paar Minuten, mL nach ein paar Stunden.Das war der Log vor dem letzten Crash.
Jemand eine Idee?-12-12 23:15:20.511 - [34mdebug[39m: proxmox.0 (395719) found states: [["proxmox.0.storage.pve_tank","active","default_num",1],["proxmox.0.storage.pve_tank","avail","size",633887],["proxmox.0.storage.pve_tank","content","text","rootdir,images"],["proxmox.0.storage.pve_tank","total","size",1841664],["proxmox.0.storage.pve_tank","used_lev","level",65.58],["proxmox.0.storage.pve_tank","used","size",1207777],["proxmox.0.storage.pve_tank","shared","default_num",0],["proxmox.0.storage.pve_tank","type","text","zfspool"],["proxmox.0.storage.pve_tank","enabled","default_num",1]] 2023-12-12 23:15:33.369 - [32minfo[39m: host.iobroker stopInstance system.adapter.proxmox.0 (force=false, process=true) 2023-12-12 23:15:33.373 - [32minfo[39m: proxmox.0 (395719) Got terminate signal TERMINATE_YOURSELF 2023-12-12 23:15:33.373 - [34mdebug[39m: proxmox.0 (395719) clearing request timeout 2023-12-12 23:15:33.374 - [32minfo[39m: proxmox.0 (395719) terminating 2023-12-12 23:15:33.374 - [32minfo[39m: proxmox.0 (395719) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-12-12 23:15:33.417 - [32minfo[39m: host.iobroker stopInstance system.adapter.proxmox.0 send kill signal 2023-12-12 23:15:33.874 - [32minfo[39m: proxmox.0 (395719) terminating 2023-12-12 23:15:33.963 - [32minfo[39m: host.iobroker instance system.adapter.proxmox.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-12-12 23:15:36.519 - [32minfo[39m: host.iobroker instance system.adapter.proxmox.0 started with pid 395797 2023-12-12 23:15:37.898 - [32minfo[39m: proxmox.0 (395797) starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.proxmox, node: v18.19.0, js-controller: 5.0.12 2023-12-12 23:15:37.909 - [33mwarn[39m: proxmox.0 (395797) Using Proxmox API: https://192.168.99.58:8006/api2/jsonAb hier kommt im Log nichts mehr mit Proxmox.
Adapter v. 2.2.2
Proxmox 8.3.1
Admin: 6.12.0
js-controller: 5.0.12
node: 18.19
O/S: bookworm -
Seit dem ich die oben genannte Tabelle im Einsatz habe ist mir aufgefallen, dass mir der Adapter andauert abschmiert.
Mal nach ein paar Minuten, mL nach ein paar Stunden.Das war der Log vor dem letzten Crash.
Jemand eine Idee?-12-12 23:15:20.511 - [34mdebug[39m: proxmox.0 (395719) found states: [["proxmox.0.storage.pve_tank","active","default_num",1],["proxmox.0.storage.pve_tank","avail","size",633887],["proxmox.0.storage.pve_tank","content","text","rootdir,images"],["proxmox.0.storage.pve_tank","total","size",1841664],["proxmox.0.storage.pve_tank","used_lev","level",65.58],["proxmox.0.storage.pve_tank","used","size",1207777],["proxmox.0.storage.pve_tank","shared","default_num",0],["proxmox.0.storage.pve_tank","type","text","zfspool"],["proxmox.0.storage.pve_tank","enabled","default_num",1]] 2023-12-12 23:15:33.369 - [32minfo[39m: host.iobroker stopInstance system.adapter.proxmox.0 (force=false, process=true) 2023-12-12 23:15:33.373 - [32minfo[39m: proxmox.0 (395719) Got terminate signal TERMINATE_YOURSELF 2023-12-12 23:15:33.373 - [34mdebug[39m: proxmox.0 (395719) clearing request timeout 2023-12-12 23:15:33.374 - [32minfo[39m: proxmox.0 (395719) terminating 2023-12-12 23:15:33.374 - [32minfo[39m: proxmox.0 (395719) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-12-12 23:15:33.417 - [32minfo[39m: host.iobroker stopInstance system.adapter.proxmox.0 send kill signal 2023-12-12 23:15:33.874 - [32minfo[39m: proxmox.0 (395719) terminating 2023-12-12 23:15:33.963 - [32minfo[39m: host.iobroker instance system.adapter.proxmox.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-12-12 23:15:36.519 - [32minfo[39m: host.iobroker instance system.adapter.proxmox.0 started with pid 395797 2023-12-12 23:15:37.898 - [32minfo[39m: proxmox.0 (395797) starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.proxmox, node: v18.19.0, js-controller: 5.0.12 2023-12-12 23:15:37.909 - [33mwarn[39m: proxmox.0 (395797) Using Proxmox API: https://192.168.99.58:8006/api2/jsonAb hier kommt im Log nichts mehr mit Proxmox.
Adapter v. 2.2.2
Proxmox 8.3.1
Admin: 6.12.0
js-controller: 5.0.12
node: 18.19
O/S: bookworm@david-g poste mal den gesammten LOG..
zigbee hab ich, zwave auch, nuc's genauso und HA auch
Support us
362
Online32.4k
Benutzer81.5k
Themen1.3m
Beiträge