Search results

After tonight's update there are many live migrations were failed, what has never happened before. I did reboot all nodes after installing updates, but it didn't help. The installation log: Preparing to unpack .../0-libgstreamer-plugins-base1.0-0_1.14.4-2+deb10u1_amd64.deb ... Unpacking...

You can use the nomachine to acces the remote desktop and pass the port 4000 from the router to the vm. Nomachine will try to it by itself, if upnp is enabled at the router. In this case no need to use VPN, because NX is a secure protocol by itself.

No. All is separated. Question is, if LACP increase Ceph performance or not? Currently it is root@asr4:~# dd if=/dev/zero of=/mnt/pve/cephfs/aaaa bs=1M status=progress count=500000 524121276416 bytes (524 GB, 488 GiB) copied, 1230 s, 426 MB/s 500000+0 records in 500000+0 records out There are...

I have a spare 10G interfaces at all cluster nodes. Planning to add this interface to Ceph. What is the best way to do it? I see following choises: 1) Add an additional network to Ceph. It will mean stop a service, delete all monitors and create it again, right? 2) Just create LACP (802.3ad)...

I have removed the monitor via web GUI, later created it again, but it doesn't start. Can't remove it or create again. root@asr3:~# pveceph mon destroy asr3 no such monitor id 'asr3' root@asr3:~# pveceph mon create --monid asr3 monitor address '192.168.121.3' already in use root@asr3:~# pveceph...

it help, no these messages any more at the /var/log/syslog, but messages still arrive, if read the syslog via the PVE web. root@asr2:~# cat /etc/rsyslog.d/proxmox.conf :msg, contains, "replication runner" stop :msg, contains, "pvesr.service: Succeeded" stop

To get the same effect for the kernel 5.4 you can edit the file /usr/lib/systemd/network/99-default.link, as I did, because I've got interfaces called like renamed3, renamed4,... after installing Proxmox 6.3 from the scratch: root@asr2:~# uname -a Linux asr2 5.4.106-1-pve #1 SMP PVE 5.4.106-1...

Measure the network performance first, so as not to guess fortune-telling. Install iperf3 on nodes apt install iperf3 On the node which act as a testing server type iperf3 -s On the node which will act as a client type iperf3 -c 192.168.122.3 Where 192.168.122.3 is the server node address at the...

Can I just type systemctl restart ceph.target instead of restarting one after other?

Why not. To use it as a firewall you will need also an USB ethernet adapter, because there is only 1 ethernet port.

Put a Raspberry Pi as a quorum device in a place where 2 nodes are located.

mon_host - how to specify 2 addresses for each node?

Why so slow? I have much more on a single 10Gb link. 2021-04-19 02:12:54 use dedicated network address for sending migration traffic (192.168.122.1) 2021-04-19 02:12:54 starting migration of VM 110 to node 'asr1' (192.168.122.1) 2021-04-19 02:12:54 starting VM 110 on remote node 'asr1'...

Could You share your ceph.conf? I'm interesting also try 2x10G

120 MB/s is an exactly single link speed at 1Gb/s connection. Your bond doesn't work.

Have you tried to enable jumbo frames at the switch and at the node network interface? I did so for migration and ceph networks: auto enp130s0f1 iface enp130s0f1 inet static address 192.168.122.1/24 mtu 9000 #Migration network auto enp130s0f0 iface enp130s0f0 inet static...

After accidentially misconfiguring the network switch I have got infinitely messages in syslog Apr 18 14:17:01 asr1 ceph-mon[2262]: 2021-04-18T14:17:01.917+0300 7f1ac94f1700 -1 mon.asr1@0(leader) e3 get_health_metrics reporting 11 slow ops, oldest is osd_failure(failed timeout osd.6...

What is a reason of following error messages in the syslog every night? Proxmox 6.3, Ceph 15.2. Apr 14 03:00:49 asr2 sudo[181953]: ceph : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/smartctl -a --json=o /dev/sdb Apr 14 03:00:49 asr2 sudo[181953]: pam_unix(sudo:session): session...

After installing Proxmox 6.3 I also got these infamous rename3, rename4, etc. again. To fix it I had to edit the file /usr/lib/systemd/network/99-default.link [Link] #NamePolicy=keep kernel database onboard slot path NamePolicy=path MACAddressPolicy=persistent Aftter apt dist-upgrade it appeared...

Tried OVS and got a problem with a bond with an LACP link with L3+L4 hashing policy configuration. It didn't work. Linux bond was ok in this configuration: auto bond0 iface bond0 inet manual bond-slaves enp6s0f0 enp7s0f0 bond-miimon 100 bond-mode 802.3ad...