Search results

I got hacked via IPMI once. That time, the hacker reset the server and then boot to an ISO or sort mounted on ILO's virtual disk, which allowed them to do modifications to the hard disk (adding a backdoor or sort). They will quickly boot back to the system on drive to make this look like a...

In my case, I restored an Elasticsearch CT previously running on PVE 6.4 to a newly installed PVE 7.1 node and got OOMed when starting unless there's the manual heap limit (thanks @keeka for the fix!). Running the same CT on a 6.4 node works. Guess it's related to the cgroups v2 changes in PVE 7.

I managed to temporary fix it after some detours (mostly due to my very slow IPMI). My issue turns out to be related to org.zfsonlinux:large_dnode = active. This was an old HP BL460C G6 with a p410i (not an ideal setting to run ZFS). I setup two HW RAID0 on the raid card (because p410i does not...

Are you using HP server with HP Smart Array? It seems other people had the same issue too all HP server, e.g. https://forum.proxmox.com/threads/grub-errors-hp-servers.62009/ https://forum.proxmox.com/threads/proxmox-5-2-on-hp-dl380-g9-with-p440ar-and-sas-drives-final-recommendation.44694/ I...

Can confirm this works. My cluster had this 401 issue on all nodes (not just one), I had tried ntp and pvecm updatecerts and reboot the whole cluster but all failed. I ended up fixing this using this method, and replace pve-ssl cert on all nodes. Thanks skywyw.

In short, no. Basically, you need to restart every single node to solve the problem, which, I believe, happens when one node has too large transfers for a long time that it disrupted the corosync communication on that node. At this point, only this node should go question-marked. However, a bug...

The problem seems to be getting worse, now I cannot even run an update for some lock in pve-ha-lrm even though I didn't have an HA setup.

Same issue here on a 16-node LXC cluster. Only begin with a recent update and reboot, so I also suspect this to be an issue with the kernel. But, I also notice the issue persists for an hour or two everytime, then everything backs to normal. So instead of rebooting every node, I just wait (of...

+1. Looking for the plan as stretch will be released later today.

Hi there, I wonder why the next release is using Linux Kernel 4.10 instead of the LTS 4.9? 4.10 only has a lifecycle of around 0.5 years so is likely to be already end-of-life when Proxmox 5.1 is released.