# pveversion
pve-manager/6.4-4/337d6701 (running kernel: 5.4.106-1-pve)
I keep getting errors when backing up to CIFS mounted storage.
This on dedicated host rented from Hetzner.
# cat /etc/pve/storage.cfg
dir: local
path /var/lib/vz
content vztmpl,iso
shared 0
zfspool...
I suppose people suggest solutions they are familiar with. You may get better answers from more experience admins but my solution:
Get server grade host, install Proxmox 6. If you can afford, get two machines so you can cluster two Proxmox hosts and gain some redundancy. If your current host...
Why do you keep doing those commands? They are for corosync upgrade, which you should not do since you are not running corosync.
I begin to suspect you have not followed the upgrade instructions properly.
Do you have backups of your system? Do you have backups of all virtual machines on this...
Have you rebooted your proxmox host?
If you have, and pveversion -v still shows old versions, the upgrade has failed. There should have been messages indicating errors if this is the case.
Try doing the upgrade again, carefully following instructions and not install corosync.
I just noticed: If...
Are you using Corosync? Do you have a multiserver Proxmox cluster where this is one host?
Maybe you do not have Corosync and should not install it at all? Just proceed with the upgrade and leave corosync alone.
On host
# pve-firewall status
Status: disabled/running
What does that mean? Is firewall disabled or running? It can not be both, or can it?
I have fail2ban running on host, it has banned lots of IP-numbers so iptables is active on host. I have not done any firewall setup in Proxmox, as far as I...
Your virtual machine must be shutdown to "power off" state, then the new configuration is effective. So shutdown -h or stop it, that should do the trick.
proxmox-ve: 6.3-1 (running kernel: 5.4.103-1-pve)
pve-manager: 5.4-15 (running version: 5.4-15/d0ec33c6)
pve-kernel-5.4: 6.3-7
pve-kernel-helper: 6.3-7
pve-kernel-5.4.103-1-pve: 5.4.103-1
pve-kernel-4.15: 5.4-19
...
The versions are messed up. Your proxmox-ve is later version than mine, the...
This used to work, but stopped working on Thursday morning when I rebooted host (and guests).
Now mails stay in mailq. I can send e-mails to GMail, though. So port 25 is open to Internet but maybe it is closed between host and guest?
I can ping guests.
Telnet to guest port 25 outputs "Trying...
@dcsapak What abaout Devuan 2.1?
Devuan ascii
If that also works, then the network setup on my host causes this on those kernels.
Also, I am testing this on new Proxmox host with no enterprise repo, I have not yet copied the licence key.
No.
Tested Debian Stretch with stock kernel, mtr shows packet loss 52%.
Installed kernel 4.19 from stretch-backports, after booting with that no packet loss with mtr 1000 run.
It looks to me some kernels on guest do not work on curret Proxmox.
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.