Search results

Well, i only meant here in public. Some info if someone is on the case or not should be enough. Email list does not help visitors here. Found this report: https://bugzilla.proxmox.com/show_bug.cgi?id=2326 @ahovda i did that (almost same, see thread above) but did not help my cluster. Please...

Proxmox team. You need to comunicate more with us users, are your engineers working on this problem ? What happens ? If i buy a subscription and Enterprise repo, will these bugs still affect me ?

Sounds like same problem everybody else has, check here: https://forum.proxmox.com/threads/pve-5-4-11-corosync-3-x-major-issues.56124/ No solution yet, just be agile then cluster fails.

>Currently we are running the cluster with HA services disabled. Absolutely, first thing i also had to disable. I also wish Proxmox could warn user to NOT upgrade yet, i feel sorry for all people that finds this thread after upgrade. But i guess thats life when running no-subscription. Does...

Today all servers went nuts, had to restart almost all vm and physical servers. Lots of: pmxcfs[1814]: [dcdb] crit: cpg_send_message failed: 9 This command fixed some servers: systemctl restart pve-cluster.service Several days problems now start at circa 08:00, what could that be that runs...

No crash of cluster yet since 22 hours after knet 1.11. So my systemd change of the most problem server (i guess its best to set it on all servers later, if needed): nano /lib/systemd/system/corosync.service Add code in [service] Restart=on-failure Save systemctl daemon-reload systemctl restart...

Last fail was this morning, all servers down. I have updated 2 hours ago, all good, nothing yet to report ;-)

Until you replace 1 disk autoscale works, you need to be prepared for disaster: https://forum.proxmox.com/threads/ceph-went-down-after-reinstall-1-osd.57013/

So the fix until 14.2.2 is installed, on every OSD in system, stop 1 at a time, then run: ceph-bluestore-tool repair --path /var/lib/ceph/osd/ceph-22 (change the number to correct OSD.) Watch disk usage go up with: ceph df Or reinstall all disks, zap and create via gui. ugh. Proxmox, you...

Could be that this is fixed in 14.2.2: https://ceph.io/releases/v14-2-2-nautilus-released/ Earlier Nautilus releases (14.2.1 and 14.2.0) have an issue where deploying a single new (Nautilus) BlueStore OSD on an upgraded cluster (i.e. one that was originally deployed pre-Nautilus) breaks the...

All disks was ceph-disk, then i upgraded like: https://pve.proxmox.com/wiki/Ceph_Luminous_to_Nautilus#Restart_the_OSD_daemon_on_all_nodes According to Ceph: https://docs.ceph.com/docs/master/ceph-volume/#migrating Should i (and everyone that upgrades from Luminous to Nautilus) reinstall ALL...

Cluster Ceph 4 nodes, 24 OSD (mixed ssd and hdd), ceph Nautilus 14.2.1 (via proxmox 6, 7 nodes). Autoscale PG is ON, 5 pools, 1 big pool with all the VM's 512 PG (all ssd). This size did not change when i turned on Autoscale on SSD pool, only the smaller for HDD and test. All OSD installed in...

SLC flash should be ok for Debian and Proxmox.

We have 3 R720 in Ceph, i used this SAS3 card https://www.supermicro.com/products/accessories/addon/AOC-S3008L-L8e.cfm And 2 cables for each server that transform SAS2 backplane to the SAS3 card. It was really cheap and works perfect, i did remove the H710. Proxmox boots on raid1 ZFS, and 4 SAS...

No, raid0 with 1 disk is like: 1 disk, no raid, no stipe. Old raidcontrollers dont have IT-mode, therefore you must use Raid0 to use one disk at a time for Ceph or ZFS.

Did you try to change Processor type in Proxmox ? What setting do you have now in your VM?

You must have same Hardware/Processor type on both nodes, try Default kvm64. Works for me.

I did repair this error by just manually syncing the /etc/pve/corosync.conf on my at the time offline server. After that it was in sync and working normal. You dont need to reinstall for this simple error.

Thanks Fabian. I did start older kernel 4.13.16-2, so no problem at the moment. How do i blacklist this specific kernel version ?(incase there is a reboot in the middle of night)

pve-kernel-4.15.15-1-pve does NOT work for Dell R740 and R420. Same as UDO and PFOO. >in other news, pve-kernel-4.15 is now the default kernel in pve-no-subscription! Why did you make a broken kernel the new default ?