Search results

thanks, update-ca-certificate solved my problem

attached

add print Dumper($conn); after constructor $VAR1 = bless( { 'username' => 'root@pam', 'manual_verification' => 1, 'port' => 8007, 'host' => '192.168.122.231', 'timeout' => 7, 'useragent' =>...

root@proxmox232:~# perl p.pl 500 Can't connect to 192.168.122.231:8007

upgrade path for this nodes different proxmox231 (setup debian10, setup pve 6.4, upgrade ifupdown -> ifupdown2, upgrade 6.4 -> 7.0, setup pbs) proxmox232 (setup debian10, pve6.4, upgrade 6.4 -> 7.0, upgrade ifupdown -> ifupdown2)

proxmox231 proxmox-ve: 7.0-2 (running kernel: 5.11.22-3-pve) pve-manager: 7.0-10 (running version: 7.0-10/d2f465d3) pve-kernel-5.11: 7.0-6 pve-kernel-helper: 7.0-6 pve-kernel-5.11.22-3-pve: 5.11.22-6 pve-kernel-5.11.22-2-pve: 5.11.22-4 ceph-fuse: 14.2.21-1 corosync: 3.1.2-pve2 criu: 3.15-1+pve-1...

no, i upgrade nodes simultaneously

status - inactive and in web interface same error 500

proxmox-backup-client works proxmox-backup-client login --repository root@pam@192.168.122.231:backup Password for "root@pam": *************** fingerprint: d4:bc:7a:af:35:52:b7:26:df:e3:43:f5:e4:60:69:fa:93:2c:34:de:15:ec:4d:d3:36:2d:eb:ca:3b:b5:cc:9e Are you sure you want to continue...

no no no (my mistake when copying, but in this case does not matter) if wrong fingerprint - other error message for example first node (proxmox231) pvesm scan pbs 192.168.122.231 root@pam --password xxxxxxxxxxxxxxxx --fingerprint...

try nomodeset kernel parameter

1. No, no one firewall rules (on both node) proxmox231 iptables -xvnL Chain INPUT (policy ACCEPT 22410989 packets, 13521272392 bytes) pkts bytes target prot opt in out source destination Chain FORWARD (policy ACCEPT 5353 packets, 1858795 bytes)...

yes .231 ping 192.168.122.232 PING 192.168.122.232 (192.168.122.232) 56(84) bytes of data. 64 bytes from 192.168.122.232: icmp_seq=1 ttl=64 time=0.155 ms 64 bytes from 192.168.122.232: icmp_seq=2 ttl=64 time=0.298 ms ^C --- 192.168.122.232 ping statistics --- 2 packets transmitted, 2 received...

pveversion -v proxmox-ve: 7.0-2 (running kernel: 5.11.22-2-pve) pve-manager: 7.0-10 (running version: 7.0-10/d2f465d3) pve-kernel-5.11: 7.0-5 pve-kernel-helper: 7.0-5 pve-kernel-5.11.22-2-pve: 5.11.22-4 ceph-fuse: 14.2.21-1 corosync: 3.1.2-pve2 criu: 3.15-1+pve-1 glusterfs-client: 9.2-1...

Hi I setup two node test cluster with qdevice on my work linux station install debian 10 and proxmox 6.4 over it. Run mirror on zfs, setup 2 vms (1 vm to 1 node), run replication from one to other) next big step - upgrade to proxmox 7 first node - first migrate to ifupdown2 (pve6.4 version)...

In current roadmap missing next point *improved SDN support what wrong with SDN?

bad solution - you lost deduplication benefits

https://pbs.proxmox.com/wiki/index.php/Roadmap

I think this problem related with https://forum.proxmox.com/threads/frequent-cpu-stalls-in-kvm-guests-during-high-io-on-host.30702/ https://forum.proxmox.com/threads/3000-msec-ping-and-packet-drops-with-virtio-under-load.36687/ high IO on host slowdown VMs terrible (i have this problem on small...

i`m wait next version, non critical problem 8-)