Search results

Interesting to know! Thanks! Are you able to advise on the correct method for installing certificates? The instructions in the wiki don't seem to work "as is", and I had to resort to the above just to get something that works. We're now seeing other things broken though. As I say, an area in...

We've also had this issue lately, after our SSL stopped working on Proxmox for no apprent reason. Has something changed with updates in the last 30 days or so that affects the way SSL on PM works? Perhaps someone who is more knowledgeable on this issue could review the wiki documentation to...

Thanks for the update and advice there Igor! Glad to see the CL team on here! Jon

Progress :) Got things working by changing the order in which the certificates are listed in the PEM files. Despite the instructions on the Wiki, I added the intermediate certificate only to the server cert file. Seems to all be working now :) Thanks for all the help folks!

Ok - got full confirmation it's the certificates now. The new node does the same. This is very odd as the certs on the old cluster were not changed at any point! Seems we have an issue with our chain or CA - we're using Comodo PositiveSSL. I'll update if we find out where I'm going wrong.

Interestingly on a new cluster we're seeing the same: Running as unit 100.scope. kvm: -vnc unix:/var/run/qemu-server/100.vnc,x509,password: Failed to start VNC server: Our own certificate /etc/pve/local/pve-ssl.pem failed validation against /etc/pve/pve-root-ca.pem: The certificate hasn't got a...

Thanks for the reply! Running systemctl stop 100.scope has no effect sadly, as the system states that the scope is not yet loaded. I'd come across that thread you mention in my initial research of the issue, and whilst the symptoms seem related that sadly has no effect either. The cluster...

This has also been discussed here: https://forum.proxmox.com/threads/kernelcare-and-proxmox-4-x.25723/ Perhaps the moderators could merge the two threads?

There may not be updates yet, but this should not really generate an error that the kernel version is not recognised? Surely if there are no updates, but the kernel has been released KernelCare should have a place-holder added so as to avoid these errors. This is somewhat sad to see really...

Just a quick update; Changing the VM CPU type removes all the unsupported feature errors, but the rest remains. Very odd since these VMs have been running for months without issue. Jon

Hi all, After a little help here. Suddenly and seemingly without cause, we can't start any VMs on either of our cluster nodes. We get the message: root@[REDACTED]:~# qm start 100 ipcc_send_rec failed: File too large Running as unit 100.scope. warning: host doesn't support requested feature...

Hi all, Just wondering if anyone has issues with KernelCare and Proxmox 4.x. We've just set this up today, as we've had great success with it on our VMs. Sadly we're now seeing the below: From: Cron Daemon <[REDACTED]> Sent: 22 January 2016 00:27 To: [REDACTED] Subject: Cron <[REDACTED]>...

I can confirm this issue is solved in the production repo now - we've setup a new node this morning with 4.1 and all is as expected.

Is there an ETA on when these fixed packages will reach the production repo? Thanks, Jon

Still no issues for us, even after returning to stock kernel and build. We're calling case closed on this. Thanks for all the help - hope this thread is of use to others at some point! Jon

@gslongo - How's things your end? We've had no issues in 6 days now, which is great :). Jon

We've currently disabled cache on all VMs. No crashes so far, but it is early days. Performance does seem better however. Thanks, Jon

@gslongo - Just a hunch, but have you tried changing the disk type to "no cache"? It could be total coincidence, however the only crashes we've had this week are on machines with the cache enabled. It should be fine to disable this cache option, as the RAID controller will still perform its'...

Right you are! Yesterday was a long one :p Jon

Hi all, Thanks for the suggestions. We were thinking of the 4.0 beta idea - as this has a 4.6 kernel in which will contain a number of fixes, but we may try with the 3.10 first as containers/OpenVZ is not important to us. In the meantime we've transferred a single VM that was previously...