Bonjour,
Merci pour la précision pour le noeud.
J’ai bien créé un utilisateur « Jeedom » qui a tous les droits sur promox, il est admin pve
Voici le log proxmox, il est indiqué : [2021-11-28 18:23:02][WARNING] : Impossible d’assigner le parent par défaut à l’équipement ZWaveJS2MQTT, un équipement portant le même nom existe déjà ou l’objet n’existe plus.
==> Effectivement cet equipement existe déjà sur jmqtt et sur mon nuc…je viens de changer le nom de l’equipement dans Jmqtt et j’ai synchronisé le plugin proxmox, je ne sais pas si c’etait le problème ?
[2021-11-28 18:23:02][INFO] : Creating new resource with id='qemu/101' and name='JeedomBuster'
[2021-11-28 18:23:02][INFO] : Creating new resource with id='qemu/102' and name='TRUENAS'
[2021-11-28 18:23:02][INFO] : Creating new resource with id='qemu/103' and name='ZWaveJS2MQTT'
[2021-11-28 18:23:02][WARNING] : Impossible d'assigner le parent par défaut à l'équipement ZWaveJS2MQTT, un équipement portant le même nom existe déjà ou l'objet n'existe plus.
[2021-11-28 18:23:02][INFO] : Creating new resource with id='storage/NucJEEDOM/local-lvm' and name='local-lvm'
[2021-11-28 18:23:02][INFO] : Creating new resource with id='storage/NucJEEDOM/Disktation' and name='Disktation'
[2021-11-28 18:23:02][INFO] : Creating new resource with id='storage/NucJEEDOM/local' and name='local'
`
Ci-dessous un extrait du syslog promox, j’ai lancé d’abord la commande arréter tout, et, qqe minutes après "arréter noeud :
Nov 28 18:28:01 NucJEEDOM pvedaemon[1000]: <root@pam> successful auth for user 'Jeedom@pve'
Nov 28 18:28:17 NucJEEDOM pvedaemon[1001]: <root@pam> successful auth for user 'Jeedom@pve'
Nov 28 18:28:17 NucJEEDOM pvedaemon[1001]: <Jeedom@pve> starting task UPID:NucJEEDOM:000011A2:0013FA6C:61A3BC31:stopall::Jeedom@pve:
Nov 28 18:28:17 NucJEEDOM pvedaemon[4515]: shutdown VM 102: UPID:NucJEEDOM:000011A3:0013FA6D:61A3BC31:qmshutdown:102:Jeedom@pve:
Nov 28 18:28:17 NucJEEDOM pvedaemon[4514]: <Jeedom@pve> starting task UPID:NucJEEDOM:000011A3:0013FA6D:61A3BC31:qmshutdown:102:Jeedom@pve:
Nov 28 18:28:17 NucJEEDOM pvedaemon[4516]: shutdown VM 101: UPID:NucJEEDOM:000011A4:0013FA6E:61A3BC31:qmshutdown:101:Jeedom@pve:
Nov 28 18:28:17 NucJEEDOM pvedaemon[4514]: <Jeedom@pve> starting task UPID:NucJEEDOM:000011A4:0013FA6E:61A3BC31:qmshutdown:101:Jeedom@pve:
Nov 28 18:28:34 NucJEEDOM QEMU[1840]: kvm: terminating on signal 15 from pid 665 (/usr/sbin/qmeventd)
Nov 28 18:28:34 NucJEEDOM kernel: GPT:Primary header thinks Alt. header is not at the end of the disk.
Nov 28 18:28:34 NucJEEDOM kernel: GPT:5860533166 != 5860533167
Nov 28 18:28:34 NucJEEDOM kernel: GPT:Alternate GPT header not at the end of the disk.
Nov 28 18:28:34 NucJEEDOM kernel: GPT:5860533166 != 5860533167
Nov 28 18:28:34 NucJEEDOM kernel: GPT: Use GNU Parted to correct GPT errors.
Nov 28 18:28:34 NucJEEDOM kernel: sda: sda1 sda2
Nov 28 18:28:34 NucJEEDOM kernel: sdb: sdb1 sdb2
Nov 28 18:28:34 NucJEEDOM kernel: sdc: sdc1 sdc2
Nov 28 18:28:34 NucJEEDOM kernel: fwbr102i0: port 2(tap102i0) entered disabled state
Nov 28 18:28:34 NucJEEDOM kernel: sdd: sdd1 sdd2
Nov 28 18:28:34 NucJEEDOM kernel: fwbr102i0: port 1(fwln102i0) entered disabled state
Nov 28 18:28:34 NucJEEDOM kernel: vmbr0: port 3(fwpr102p0) entered disabled state
Nov 28 18:28:34 NucJEEDOM kernel: device fwln102i0 left promiscuous mode
Nov 28 18:28:34 NucJEEDOM kernel: fwbr102i0: port 1(fwln102i0) entered disabled state
Nov 28 18:28:34 NucJEEDOM kernel: device fwpr102p0 left promiscuous mode
Nov 28 18:28:34 NucJEEDOM kernel: vmbr0: port 3(fwpr102p0) entered disabled state
Nov 28 18:28:35 NucJEEDOM systemd[1]: 102.scope: Succeeded.
Nov 28 18:28:35 NucJEEDOM qmeventd[657]: Starting cleanup for 102
Nov 28 18:28:35 NucJEEDOM qmeventd[657]: Finished cleanup for 102
Nov 28 18:28:36 NucJEEDOM pvedaemon[4514]: end task UPID:NucJEEDOM:000011A3:0013FA6D:61A3BC31:qmshutdown:102:Jeedom@pve:
Nov 28 18:29:00 NucJEEDOM systemd[1]: Starting Proxmox VE replication runner...
Nov 28 18:29:00 NucJEEDOM systemd[1]: pvesr.service: Succeeded.
Nov 28 18:29:00 NucJEEDOM systemd[1]: Started Proxmox VE replication runner.
Nov 28 18:29:31 NucJEEDOM pvedaemon[1000]: <root@pam> successful auth for user 'root@pam'
Nov 28 18:29:49 NucJEEDOM QEMU[1030]: kvm: terminating on signal 15 from pid 665 (/usr/sbin/qmeventd)
Nov 28 18:29:49 NucJEEDOM kernel: fwbr101i0: port 2(tap101i0) entered disabled state
Nov 28 18:29:49 NucJEEDOM kernel: fwbr101i0: port 1(fwln101i0) entered disabled state
Nov 28 18:29:49 NucJEEDOM kernel: vmbr0: port 2(fwpr101p0) entered disabled state
Nov 28 18:29:49 NucJEEDOM kernel: device fwln101i0 left promiscuous mode
Nov 28 18:29:49 NucJEEDOM kernel: fwbr101i0: port 1(fwln101i0) entered disabled state
Nov 28 18:29:49 NucJEEDOM kernel: device fwpr101p0 left promiscuous mode
Nov 28 18:29:49 NucJEEDOM kernel: vmbr0: port 2(fwpr101p0) entered disabled state
Nov 28 18:29:50 NucJEEDOM kernel: usb 1-1: reset low-speed USB device number 2 using xhci_hcd
Nov 28 18:29:50 NucJEEDOM qmeventd[657]: Starting cleanup for 101
Nov 28 18:29:50 NucJEEDOM qmeventd[657]: trying to acquire lock...
Nov 28 18:29:50 NucJEEDOM kernel: hid-generic 0003:051D:0002.0002: hiddev0,hidraw0: USB HID v1.10 Device [APC Back-UPS ES 700G FW:871.O2 .I USB FW:O2 ] on usb-0000:00:14.0-1/input0
Nov 28 18:29:50 NucJEEDOM kernel: usb 1-4: reset full-speed USB device number 4 using xhci_hcd
Nov 28 18:29:50 NucJEEDOM kernel: ftdi_sio 1-4:1.0: FTDI USB Serial Device converter detected
Nov 28 18:29:50 NucJEEDOM kernel: usb 1-4: Detected FT232RL
Nov 28 18:29:50 NucJEEDOM kernel: usb 1-4: FTDI USB Serial Device converter now attached to ttyUSB0
Nov 28 18:29:51 NucJEEDOM kernel: usb 1-3: reset full-speed USB device number 3 using xhci_hcd
Nov 28 18:29:51 NucJEEDOM kernel: cdc_acm 1-3:1.0: ttyACM0: USB ACM device
Nov 28 18:29:51 NucJEEDOM systemd[1]: 101.scope: Succeeded.
Nov 28 18:29:52 NucJEEDOM qmeventd[657]: OK
Nov 28 18:29:52 NucJEEDOM qmeventd[657]: Finished cleanup for 101
Nov 28 18:29:53 NucJEEDOM pvedaemon[4514]: end task UPID:NucJEEDOM:000011A4:0013FA6E:61A3BC31:qmshutdown:101:Jeedom@pve:
Nov 28 18:29:54 NucJEEDOM pvedaemon[4514]: all VMs and CTs stopped
Nov 28 18:29:54 NucJEEDOM pvedaemon[1001]: <Jeedom@pve> end task UPID:NucJEEDOM:000011A2:0013FA6C:61A3BC31:stopall::Jeedom@pve: OK
Nov 28 18:30:00 NucJEEDOM systemd[1]: Starting Proxmox VE replication runner...
Nov 28 18:30:00 NucJEEDOM systemd[1]: pvesr.service: Succeeded.
Nov 28 18:30:00 NucJEEDOM systemd[1]: Started Proxmox VE replication runner.
Nov 28 18:30:10 NucJEEDOM pvedaemon[999]: <root@pam> successful auth for user 'root@pam'
Nov 28 18:31:00 NucJEEDOM systemd[1]: Starting Proxmox VE replication runner...
Nov 28 18:31:00 NucJEEDOM systemd[1]: pvesr.service: Succeeded.
Nov 28 18:31:00 NucJEEDOM systemd[1]: Started Proxmox VE replication runner.
Nov 28 18:31:36 NucJEEDOM pvedaemon[5127]: start VM 101: UPID:NucJEEDOM:00001407:0014483D:61A3BCF8:qmstart:101:root@pam:
Nov 28 18:31:36 NucJEEDOM pvedaemon[999]: <root@pam> starting task UPID:NucJEEDOM:00001407:0014483D:61A3BCF8:qmstart:101:root@pam:
Nov 28 18:31:36 NucJEEDOM systemd[1]: Started 101.scope.
Nov 28 18:31:36 NucJEEDOM systemd-udevd[5138]: Using default interface naming scheme 'v240'.
Nov 28 18:31:36 NucJEEDOM systemd-udevd[5138]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Nov 28 18:31:36 NucJEEDOM systemd-udevd[5138]: Could not generate persistent MAC address for tap101i0: No such file or directory
Nov 28 18:31:36 NucJEEDOM kernel: device tap101i0 entered promiscuous mode
Nov 28 18:31:36 NucJEEDOM systemd-udevd[5138]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Nov 28 18:31:36 NucJEEDOM systemd-udevd[5138]: Could not generate persistent MAC address for fwbr101i0: No such file or directory
Nov 28 18:31:36 NucJEEDOM systemd-udevd[5135]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Nov 28 18:31:36 NucJEEDOM systemd-udevd[5141]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Nov 28 18:31:36 NucJEEDOM systemd-udevd[5135]: Using default interface naming scheme 'v240'.
Nov 28 18:31:36 NucJEEDOM systemd-udevd[5141]: Using default interface naming scheme 'v240'.
Nov 28 18:31:36 NucJEEDOM systemd-udevd[5135]: Could not generate persistent MAC address for fwpr101p0: No such file or directory
Nov 28 18:31:36 NucJEEDOM systemd-udevd[5141]: Could not generate persistent MAC address for fwln101i0: No such file or directory
Nov 28 18:31:36 NucJEEDOM kernel: fwbr101i0: port 1(fwln101i0) entered blocking state
Nov 28 18:31:36 NucJEEDOM kernel: fwbr101i0: port 1(fwln101i0) entered disabled state
Nov 28 18:31:36 NucJEEDOM kernel: device fwln101i0 entered promiscuous mode
Nov 28 18:31:36 NucJEEDOM kernel: fwbr101i0: port 1(fwln101i0) entered blocking state
Nov 28 18:31:36 NucJEEDOM kernel: fwbr101i0: port 1(fwln101i0) entered forwarding state
Nov 28 18:31:36 NucJEEDOM kernel: vmbr0: port 2(fwpr101p0) entered blocking state
Nov 28 18:31:36 NucJEEDOM kernel: vmbr0: port 2(fwpr101p0) entered disabled state
Nov 28 18:31:36 NucJEEDOM kernel: device fwpr101p0 entered promiscuous mode
Nov 28 18:31:36 NucJEEDOM kernel: vmbr0: port 2(fwpr101p0) entered blocking state
Nov 28 18:31:36 NucJEEDOM kernel: vmbr0: port 2(fwpr101p0) entered forwarding state
Nov 28 18:31:36 NucJEEDOM kernel: fwbr101i0: port 2(tap101i0) entered blocking state
Nov 28 18:31:36 NucJEEDOM kernel: fwbr101i0: port 2(tap101i0) entered disabled state
Nov 28 18:31:36 NucJEEDOM kernel: fwbr101i0: port 2(tap101i0) entered blocking state
Nov 28 18:31:36 NucJEEDOM kernel: fwbr101i0: port 2(tap101i0) entered forwarding state
Nov 28 18:31:36 NucJEEDOM kernel: ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
Nov 28 18:31:36 NucJEEDOM kernel: ftdi_sio 1-4:1.0: device disconnected
Nov 28 18:31:36 NucJEEDOM pvedaemon[999]: <root@pam> end task UPID:NucJEEDOM:00001407:0014483D:61A3BCF8:qmstart:101:root@pam: OK
Nov 28 18:31:42 NucJEEDOM pvedaemon[5227]: start VM 102: UPID:NucJEEDOM:0000146B:00144AAE:61A3BCFE:qmstart:102:root@pam:
Nov 28 18:31:42 NucJEEDOM pvedaemon[1001]: <root@pam> starting task UPID:NucJEEDOM:0000146B:00144AAE:61A3BCFE:qmstart:102:root@pam:
Nov 28 18:31:42 NucJEEDOM systemd[1]: Started 102.scope.
Nov 28 18:31:42 NucJEEDOM systemd-udevd[5239]: Using default interface naming scheme 'v240'.
Nov 28 18:31:42 NucJEEDOM systemd-udevd[5239]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Nov 28 18:31:42 NucJEEDOM systemd-udevd[5239]: Could not generate persistent MAC address for tap102i0: No such file or directory
Nov 28 18:31:42 NucJEEDOM kernel: device tap102i0 entered promiscuous mode
Nov 28 18:31:43 NucJEEDOM systemd-udevd[5239]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Nov 28 18:31:43 NucJEEDOM systemd-udevd[5239]: Could not generate persistent MAC address for fwbr102i0: No such file or directory
Nov 28 18:31:43 NucJEEDOM systemd-udevd[5238]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Nov 28 18:31:43 NucJEEDOM systemd-udevd[5234]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Nov 28 18:31:43 NucJEEDOM systemd-udevd[5234]: Using default interface naming scheme 'v240'.
Nov 28 18:31:43 NucJEEDOM systemd-udevd[5238]: Using default interface naming scheme 'v240'.
Nov 28 18:31:43 NucJEEDOM systemd-udevd[5234]: Could not generate persistent MAC address for fwln102i0: No such file or directory
Nov 28 18:31:43 NucJEEDOM systemd-udevd[5238]: Could not generate persistent MAC address for fwpr102p0: No such file or directory
Nov 28 18:31:43 NucJEEDOM kernel: fwbr102i0: port 1(fwln102i0) entered blocking state
Nov 28 18:31:43 NucJEEDOM kernel: fwbr102i0: port 1(fwln102i0) entered disabled state
Nov 28 18:31:43 NucJEEDOM kernel: device fwln102i0 entered promiscuous mode
Nov 28 18:31:43 NucJEEDOM kernel: fwbr102i0: port 1(fwln102i0) entered blocking state
Nov 28 18:31:43 NucJEEDOM kernel: fwbr102i0: port 1(fwln102i0) entered forwarding state
Nov 28 18:31:43 NucJEEDOM kernel: vmbr0: port 3(fwpr102p0) entered blocking state
Nov 28 18:31:43 NucJEEDOM kernel: vmbr0: port 3(fwpr102p0) entered disabled state
Nov 28 18:31:43 NucJEEDOM kernel: device fwpr102p0 entered promiscuous mode
Nov 28 18:31:43 NucJEEDOM kernel: vmbr0: port 3(fwpr102p0) entered blocking state
Nov 28 18:31:43 NucJEEDOM kernel: vmbr0: port 3(fwpr102p0) entered forwarding state
Nov 28 18:31:43 NucJEEDOM kernel: fwbr102i0: port 2(tap102i0) entered blocking state
Nov 28 18:31:43 NucJEEDOM kernel: fwbr102i0: port 2(tap102i0) entered disabled state
Nov 28 18:31:43 NucJEEDOM kernel: fwbr102i0: port 2(tap102i0) entered blocking state
Nov 28 18:31:43 NucJEEDOM kernel: fwbr102i0: port 2(tap102i0) entered forwarding state
Nov 28 18:31:43 NucJEEDOM pvedaemon[1001]: <root@pam> end task UPID:NucJEEDOM:0000146B:00144AAE:61A3BCFE:qmstart:102:root@pam: OK
Nov 28 18:31:46 NucJEEDOM kernel: usb 1-1: reset low-speed USB device number 2 using xhci_hcd
Nov 28 18:31:47 NucJEEDOM kernel: usb 1-3: reset full-speed USB device number 3 using xhci_hcd
Nov 28 18:31:48 NucJEEDOM kernel: usb 1-4: reset full-speed USB device number 4 using xhci_hcd
Nov 28 18:32:00 NucJEEDOM systemd[1]: Starting Proxmox VE replication runner...
Nov 28 18:32:00 NucJEEDOM systemd[1]: pvesr.service: Succeeded.
Nov 28 18:32:00 NucJEEDOM systemd[1]: Started Proxmox VE replication runner.
Nov 28 18:32:07 NucJEEDOM kernel: mce: CPU4: Core temperature above threshold, cpu clock throttled (total events = 407)
Nov 28 18:32:07 NucJEEDOM kernel: mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 407)
Nov 28 18:32:07 NucJEEDOM kernel: mce: CPU4: Package temperature above threshold, cpu clock throttled (total events = 529)
Nov 28 18:32:07 NucJEEDOM kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 529)
Nov 28 18:32:07 NucJEEDOM kernel: mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 529)
Nov 28 18:32:07 NucJEEDOM kernel: mce: CPU7: Package temperature above threshold, cpu clock throttled (total events = 529)
Nov 28 18:32:07 NucJEEDOM kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 529)
Nov 28 18:32:07 NucJEEDOM kernel: mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 529)
Nov 28 18:32:07 NucJEEDOM kernel: mce: CPU6: Package temperature above threshold, cpu clock throttled (total events = 529)
Nov 28 18:32:07 NucJEEDOM kernel: mce: CPU5: Package temperature above threshold, cpu clock throttled (total events = 529)
Nov 28 18:32:07 NucJEEDOM kernel: mce: CPU4: Core temperature/speed normal
Nov 28 18:32:07 NucJEEDOM kernel: mce: CPU0: Core temperature/speed normal
Nov 28 18:32:07 NucJEEDOM kernel: mce: CPU6: Package temperature/speed normal
Nov 28 18:32:07 NucJEEDOM kernel: mce: CPU2: Package temperature/speed normal
Nov 28 18:32:07 NucJEEDOM kernel: mce: CPU4: Package temperature/speed normal
Nov 28 18:32:07 NucJEEDOM kernel: mce: CPU0: Package temperature/speed normal
Nov 28 18:32:07 NucJEEDOM kernel: mce: CPU7: Package temperature/speed normal
Nov 28 18:32:07 NucJEEDOM kernel: mce: CPU3: Package temperature/speed normal
Nov 28 18:32:07 NucJEEDOM kernel: mce: CPU5: Package temperature/speed normal
Nov 28 18:32:07 NucJEEDOM kernel: mce: CPU1: Package temperature/speed normal
Nov 28 18:33:00 NucJEEDOM systemd[1]: Starting Proxmox VE replication runner...
Nov 28 18:33:00 NucJEEDOM systemd[1]: pvesr.service: Succeeded.
Nov 28 18:33:00 NucJEEDOM systemd[1]: Started Proxmox VE replication runner.
Nov 28 18:33:03 NucJEEDOM pvedaemon[1000]: <root@pam> successful auth for user 'Jeedom@pve'
Nov 28 18:34:00 NucJEEDOM systemd[1]: Starting Proxmox VE replication runner...
Nov 28 18:34:00 NucJEEDOM systemd[1]: pvesr.service: Succeeded.
Nov 28 18:34:00 NucJEEDOM systemd[1]: Started Proxmox VE replication runner.
Nov 28 18:34:02 NucJEEDOM pvedaemon[1000]: <root@pam> successful auth for user 'Jeedom@pve'
Nov 28 18:34:09 NucJEEDOM pvedaemon[999]: <root@pam> successful auth for user 'Jeedom@pve'
Nov 28 18:34:19 NucJEEDOM pvedaemon[1001]: <root@pam> successful auth for user 'root@pam'
Nov 28 18:34:59 NucJEEDOM pvedaemon[1000]: <root@pam> successful auth for user 'Jeedom@pve'
Nov 28 18:35:00 NucJEEDOM systemd[1]: Starting Proxmox VE replication runner...
Nov 28 18:35:00 NucJEEDOM systemd[1]: pvesr.service: Succeeded.
Nov 28 18:35:00 NucJEEDOM systemd[1]: Started Proxmox VE replication runner.
Nov 28 18:35:01 NucJEEDOM pvedaemon[999]: <root@pam> successful auth for user 'Jeedom@pve'
Nov 28 18:36:00 NucJEEDOM systemd[1]: Starting Proxmox VE replication runner...
Nov 28 18:36:00 NucJEEDOM systemd[1]: pvesr.service: Succeeded.
Nov 28 18:36:00 NucJEEDOM systemd[1]: Started Proxmox VE replication runner.
Nov 28 18:36:01 NucJEEDOM pvedaemon[999]: <root@pam> successful auth for user 'Jeedom@pve'
Nov 28 18:37:00 NucJEEDOM systemd[1]: Starting Proxmox VE replication runner...
Nov 28 18:37:00 NucJEEDOM systemd[1]: pvesr.service: Succeeded.
Nov 28 18:37:00 NucJEEDOM systemd[1]: Started Proxmox VE replication runner.
Nov 28 18:37:02 NucJEEDOM pvedaemon[1000]: <root@pam> successful auth for user 'Jeedom@pve'
Nov 28 18:38:00 NucJEEDOM systemd[1]: Starting Proxmox VE replication runner...
Nov 28 18:38:00 NucJEEDOM systemd[1]: pvesr.service: Succeeded.
Nov 28 18:38:00 NucJEEDOM systemd[1]: Started Proxmox VE replication runner.
Nov 28 18:38:01 NucJEEDOM pvedaemon[999]: <root@pam> successful auth for user 'Jeedom@pve'
Nov 28 18:39:00 NucJEEDOM systemd[1]: Starting Proxmox VE replication runner...
Nov 28 18:39:00 NucJEEDOM systemd[1]: pvesr.service: Succeeded.
Nov 28 18:39:00 NucJEEDOM systemd[1]: Started Proxmox VE replication runner.
Nov 28 18:39:01 NucJEEDOM pvedaemon[1001]: <root@pam> successful auth for user 'Jeedom@pve'
Nov 28 18:39:43 NucJEEDOM pvedaemon[999]: <root@pam> successful auth for user 'Jeedom@pve'
Nov 28 18:40:00 NucJEEDOM systemd[1]: Starting Proxmox VE replication runner...
Nov 28 18:40:00 NucJEEDOM systemd[1]: pvesr.service: Succeeded.
Nov 28 18:40:00 NucJEEDOM systemd[1]: Started Proxmox VE replication runner.
Nov 28 18:40:02 NucJEEDOM pvedaemon[1001]: <root@pam> successful auth for user 'Jeedom@pve'
Nov 28 18:40:02 NucJEEDOM kernel: mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 176)
Nov 28 18:40:02 NucJEEDOM kernel: mce: CPU6: Core temperature above threshold, cpu clock throttled (total events = 176)
Nov 28 18:40:02 NucJEEDOM kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 651)
Nov 28 18:40:02 NucJEEDOM kernel: mce: CPU4: Package temperature above threshold, cpu clock throttled (total events = 651)
Nov 28 18:40:02 NucJEEDOM kernel: mce: CPU6: Package temperature above threshold, cpu clock throttled (total events = 651)
Nov 28 18:40:02 NucJEEDOM kernel: mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 651)
Nov 28 18:40:02 NucJEEDOM kernel: mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 651)
Nov 28 18:40:02 NucJEEDOM kernel: mce: CPU7: Package temperature above threshold, cpu clock throttled (total events = 651)
Nov 28 18:40:02 NucJEEDOM kernel: mce: CPU5: Package temperature above threshold, cpu clock throttled (total events = 651)
Nov 28 18:40:02 NucJEEDOM kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 651)
Nov 28 18:40:02 NucJEEDOM kernel: mce: CPU6: Core temperature/speed normal
Nov 28 18:40:02 NucJEEDOM kernel: mce: CPU2: Core temperature/speed normal
Nov 28 18:40:02 NucJEEDOM kernel: mce: CPU0: Package temperature/speed normal
Nov 28 18:40:02 NucJEEDOM kernel: mce: CPU4: Package temperature/speed normal
Nov 28 18:40:02 NucJEEDOM kernel: mce: CPU2: Package temperature/speed normal
Nov 28 18:40:02 NucJEEDOM kernel: mce: CPU6: Package temperature/speed normal
Nov 28 18:40:02 NucJEEDOM kernel: mce: CPU5: Package temperature/speed normal
Nov 28 18:40:02 NucJEEDOM kernel: mce: CPU3: Package temperature/speed normal
Nov 28 18:40:02 NucJEEDOM kernel: mce: CPU1: Package temperature/speed normal
Nov 28 18:40:02 NucJEEDOM kernel: mce: CPU7: Package temperature/speed normal
Nov 28 18:41:00 NucJEEDOM systemd[1]: Starting Proxmox VE replication runner...
Nov 28 18:41:00 NucJEEDOM systemd[1]: pvesr.service: Succeeded.
Nov 28 18:41:00 NucJEEDOM systemd[1]: Started Proxmox VE replication runner.
Nov 28 18:41:01 NucJEEDOM pvedaemon[1000]: <root@pam> successful auth for user 'Jeedom@pve'
Nov 28 18:42:00 NucJEEDOM systemd[1]: Starting Proxmox VE replication runner...
Nov 28 18:42:00 NucJEEDOM systemd[1]: pvesr.service: Succeeded.
Nov 28 18:42:00 NucJEEDOM systemd[1]: Started Proxmox VE replication runner.
Nov 28 18:42:01 NucJEEDOM pvedaemon[1001]: <root@pam> successful auth for user 'Jeedom@pve'
Nov 28 18:43:00 NucJEEDOM systemd[1]: Starting Proxmox VE replication runner...
Nov 28 18:43:00 NucJEEDOM systemd[1]: pvesr.service: Succeeded.
Nov 28 18:43:00 NucJEEDOM systemd[1]: Started Proxmox VE replication runner.
Nov 28 18:43:01 NucJEEDOM pvedaemon[999]: <root@pam> successful auth for user 'Jeedom@pve'
Nov 28 18:44:00 NucJEEDOM systemd[1]: Starting Proxmox VE replication runner...
Nov 28 18:44:00 NucJEEDOM systemd[1]: pvesr.service: Succeeded.
Nov 28 18:44:00 NucJEEDOM systemd[1]: Started Proxmox VE replication runner.
Nov 28 18:44:02 NucJEEDOM pvedaemon[999]: <root@pam> successful auth for user 'Jeedom@pve'
Nov 28 18:45:00 NucJEEDOM systemd[1]: Starting Proxmox VE replication runner...
Nov 28 18:45:00 NucJEEDOM systemd[1]: pvesr.service: Succeeded.
Nov 28 18:45:00 NucJEEDOM systemd[1]: Started Proxmox VE replication runner.
Nov 28 18:45:02 NucJEEDOM pvedaemon[1000]: <root@pam> successful auth for user 'Jeedom@pve'
Nov 28 18:46:00 NucJEEDOM systemd[1]: Starting Proxmox VE replication runner...
Nov 28 18:46:00 NucJEEDOM systemd[1]: pvesr.service: Succeeded.
Nov 28 18:46:00 NucJEEDOM systemd[1]: Started Proxmox VE replication runner.
Nov 28 18:46:01 NucJEEDOM pvedaemon[999]: <root@pam> successful auth for user 'Jeedom@pve'
Nov 28 18:47:00 NucJEEDOM systemd[1]: Starting Proxmox VE replication runner...
Nov 28 18:47:00 NucJEEDOM systemd[1]: pvesr.service: Succeeded.
Nov 28 18:47:00 NucJEEDOM systemd[1]: Started Proxmox VE replication runner.
Nov 28 18:47:02 NucJEEDOM pvedaemon[1001]: <root@pam> successful auth for user 'Jeedom@pve'
Nov 28 18:48:00 NucJEEDOM systemd[1]: Starting Proxmox VE replication runner...
Nov 28 18:48:00 NucJEEDOM systemd[1]: pvesr.service: Succeeded.
Nov 28 18:48:00 NucJEEDOM systemd[1]: Started Proxmox VE replication runner.
Nov 28 18:48:02 NucJEEDOM pvedaemon[999]: <root@pam> successful auth for user 'Jeedom@pve'
Nov 28 18:49:00 NucJEEDOM systemd[1]: Starting Proxmox VE replication runner...
Nov 28 18:49:00 NucJEEDOM systemd[1]: pvesr.service: Succeeded.
Nov 28 18:49:00 NucJEEDOM systemd[1]: Started Proxmox VE replication runner.
Nov 28 18:49:01 NucJEEDOM pvedaemon[1000]: <root@pam> successful auth for user 'Jeedom@pve'
Nov 28 18:50:00 NucJEEDOM systemd[1]: Starting Proxmox VE replication runner...
Nov 28 18:50:00 NucJEEDOM systemd[1]: pvesr.service: Succeeded.
Nov 28 18:50:00 NucJEEDOM systemd[1]: Started Proxmox VE replication runner.
Nov 28 18:50:02 NucJEEDOM pvedaemon[1001]: <root@pam> successful auth for user 'Jeedom@pve'
Nov 28 18:51:00 NucJEEDOM systemd[1]: Starting Proxmox VE replication runner...
Nov 28 18:51:00 NucJEEDOM systemd[1]: pvesr.service: Succeeded.
Nov 28 18:51:00 NucJEEDOM systemd[1]: Started Proxmox VE replication runner.
Nov 28 18:51:02 NucJEEDOM pvedaemon[1001]: <root@pam> successful auth for user 'Jeedom@pve'
Nov 28 18:52:00 NucJEEDOM systemd[1]: Starting Proxmox VE replication runner...
Nov 28 18:52:00 NucJEEDOM systemd[1]: pvesr.service: Succeeded.
Nov 28 18:52:00 NucJEEDOM systemd[1]: Started Proxmox VE replication runner.
Nov 28 18:52:01 NucJEEDOM pvedaemon[999]: <root@pam> successful auth for user 'Jeedom@pve'
Nov 28 18:53:00 NucJEEDOM systemd[1]: Starting Proxmox VE replication runner...
Nov 28 18:53:00 NucJEEDOM systemd[1]: pvesr.service: Succeeded.
Nov 28 18:53:00 NucJEEDOM systemd[1]: Started Proxmox VE replication runner.
Nov 28 18:53:01 NucJEEDOM pvedaemon[1001]: <root@pam> successful auth for user 'Jeedom@pve'
Nov 28 18:54:00 NucJEEDOM systemd[1]: Starting Proxmox VE replication runner...
Nov 28 18:54:00 NucJEEDOM systemd[1]: pvesr.service: Succeeded.
Nov 28 18:54:00 NucJEEDOM systemd[1]: Started Proxmox VE replication runner.
Nov 28 18:54:01 NucJEEDOM pvedaemon[1001]: <root@pam> successful auth for user 'Jeedom@pve'
Nov 28 18:55:00 NucJEEDOM systemd[1]: Starting Proxmox VE replication runner...
Nov 28 18:55:00 NucJEEDOM systemd[1]: pvesr.service: Succeeded.
Nov 28 18:55:00 NucJEEDOM systemd[1]: Started Proxmox VE replication runner.
Nov 28 18:55:02 NucJEEDOM pvedaemon[1001]: <root@pam> successful auth for user 'Jeedom@pve'
Nov 28 18:56:00 NucJEEDOM systemd[1]: Starting Proxmox VE replication runner...
Nov 28 18:56:00 NucJEEDOM systemd[1]: pvesr.service: Succeeded.
Nov 28 18:56:00 NucJEEDOM systemd[1]: Started Proxmox VE replication runner.
Nov 28 18:56:01 NucJEEDOM pvedaemon[1001]: <root@pam> successful auth for user 'Jeedom@pve'
Nov 28 18:57:00 NucJEEDOM systemd[1]: Starting Proxmox VE replication runner...
Nov 28 18:57:00 NucJEEDOM systemd[1]: pvesr.service: Succeeded.
Nov 28 18:57:00 NucJEEDOM systemd[1]: Started Proxmox VE replication runner.
Nov 28 18:57:01 NucJEEDOM pvedaemon[999]: <root@pam> successful auth for user 'Jeedom@pve'
Nov 28 18:58:00 NucJEEDOM systemd[1]: Starting Proxmox VE replication runner...
Nov 28 18:58:00 NucJEEDOM systemd[1]: pvesr.service: Succeeded.
Nov 28 18:58:00 NucJEEDOM systemd[1]: Started Proxmox VE replication runner.
Nov 28 18:58:01 NucJEEDOM pvedaemon[1001]: <root@pam> successful auth for user 'Jeedom@pve'
Nov 28 18:58:13 NucJEEDOM pvedaemon[1000]: <root@pam> successful auth for user 'root@pam'
Nov 28 18:58:37 NucJEEDOM kernel: mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 471)
Nov 28 18:58:37 NucJEEDOM kernel: mce: CPU4: Core temperature above threshold, cpu clock throttled (total events = 471)
Nov 28 18:58:37 NucJEEDOM kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 659)
Nov 28 18:58:37 NucJEEDOM kernel: mce: CPU4: Package temperature above threshold, cpu clock throttled (total events = 659)
Nov 28 18:58:37 NucJEEDOM kernel: mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 659)
Nov 28 18:58:37 NucJEEDOM kernel: mce: CPU6: Package temperature above threshold, cpu clock throttled (total events = 659)
Nov 28 18:58:37 NucJEEDOM kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 659)
Nov 28 18:58:37 NucJEEDOM kernel: mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 659)
Nov 28 18:58:37 NucJEEDOM kernel: mce: CPU5: Package temperature above threshold, cpu clock throttled (total events = 659)
Nov 28 18:58:37 NucJEEDOM kernel: mce: CPU7: Package temperature above threshold, cpu clock throttled (total events = 659)
Nov 28 18:58:37 NucJEEDOM kernel: mce: CPU0: Core temperature/speed normal
Nov 28 18:58:37 NucJEEDOM kernel: mce: CPU4: Core temperature/speed normal
Nov 28 18:58:37 NucJEEDOM kernel: mce: CPU0: Package temperature/speed normal
Nov 28 18:58:37 NucJEEDOM kernel: mce: CPU4: Package temperature/speed normal
Nov 28 18:58:37 NucJEEDOM kernel: mce: CPU6: Package temperature/speed normal
Nov 28 18:58:37 NucJEEDOM kernel: mce: CPU1: Package temperature/speed normal
Nov 28 18:58:37 NucJEEDOM kernel: mce: CPU2: Package temperature/speed normal
Nov 28 18:58:37 NucJEEDOM kernel: mce: CPU5: Package temperature/speed normal
Nov 28 18:58:37 NucJEEDOM kernel: mce: CPU3: Package temperature/speed normal
Nov 28 18:58:37 NucJEEDOM kernel: mce: CPU7: Package temperature/speed normal
Nov 28 18:59:00 NucJEEDOM systemd[1]: Starting Proxmox VE replication runner...
Nov 28 18:59:00 NucJEEDOM systemd[1]: pvesr.service: Succeeded.
Nov 28 18:59:00 NucJEEDOM systemd[1]: Started Proxmox VE replication runner.
Nov 28 18:59:02 NucJEEDOM pvedaemon[999]: <root@pam> successful auth for user 'Jeedom@pve'
Voici le log proxmox Log proxmox.txt (107,6 Ko) en pièce jointe
Enfin, j’ai lancer la commande en cliquant sur le bouton « tester » :