I've just discovered that no response after showmount -e <server> command on client could be due to DoS Defend setting enabled on TP-Link switch and the reason is SYN sPort Less 1024 rule.
Hope this help to somebody.
I've tested on laptop with Windows and console accepts symbols.
I suspect this is combination of my current setup on working place, just strange that it works on PVE 3.x and doesn't on 5.2.
Thanks for you answer. It works: when I have to pass "@" symbol in password I go to monitor and type "sendkey shift-2".
However what is the sense of strong passwords if you can't directly use them where they expected to be used?
Is it existing bug somewhere?
The latest PVE version 5.2 is installed.
I've moved several KVMs from older 3.4 server and realized that can't login to any: "Login incorrect".
Password has "@" symbol so I tried to type it in Login prompt instead of Password prompt and got "2".
Non of symbols are worked.
I have default Eng-Us...
I have 2 servers: Proxmox and NFS/Samba. They are directly connected by cable.
My PVE server has been upgraded from old PVE 2.x version to the newest one 5.2.
Upgrade has been performed from scratch by installing to new hdd from usb-drive with pve.iso.
Old kvm and openvz images were...
Hi, I have pve-manager: 2.1-1 (pve-manager/2.1/f9b0f63a) with KVM and OpenVZ based VMs.
root@proxmox:~# uptime
10:46:12 up 670 days, 13:05, 1 user, load average: 0.39, 0.23, 0.17
I'd like to upgrade this server to the newest PVE 5.
Is it possible to restore backups that were created on PVE...
One of my cluster's node has been reported by zabbix as having Lack of free swap space:
Free swap space in % (pve1:system.swap.size[,pfree]): 9.98 %
What could cause this and how to resolve?
It seems that others nodes don't have such problem.
Yes, it's clear, but I expect this line should appears after image creation, after these lines:
125: Jul 31 02:46:02 INFO: transferred 107374 MB in 942 seconds (113 MB/s)
125: Jul 31 02:46:02 INFO: archive file size: 13.93GB
i.e. after 942 seconds, instead it appears immediately after stop...
Ssh to first host and ssh from it to others. You'll be asked to trust remote hosts. Accept.
Then try to open web at first host and open console at others nodes.
Hope this helps.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.