Search results

Can report: 17:32 ch@vn01:~ % systemctl show system-check_mk.slice -p MemoryLimit MemoryLimit=infinity 17:32 ch@vn01:~ % systemctl show system-check_mk.slice -p MemoryCurrent MemoryCurrent=562638848 17:32 ch@vn03:~ % systemctl show system-check_mk.slice -p MemoryLimit MemoryLimit=infinity...

Also see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940021

The packages to install would be `bpfcc-tools` and `pve-headers`; then you'll have execsnoop-bpfcc. Can just run this for a few minutes (as `execsnoop-bpfcc -tx` preferably). It will show what programs get executed.

Can you run execsnoop for a few minutes and post what it reports? My other wild guess is stopping pve-firewall.service.

Ah. So then you had ipmitool installed but it could never do anything, right? Yeah so we are indeed chasing more than one leak there...

Can you try unloading all the ipmi_ kmods? (lsmod | grep ipmi_ -> rmmod ...) Result over here: But as just said to someone else, I suspect we're chasing more than one kernel memleak ...

Not seeing these in stretch/pve-no-subscription yet?

$Kollege hat sich das in den letzten Tagen auch angesehen und dann aufgegeben; hat aber auch festgestellt dass es vielleicht gar nicht so sinnvoll ist einen SCSI/RAID-Controller an einen Guest durchzugeben. Für Storage sollte man wohl besser direkt Volumes durchgeben, und wenns um andere SCSI...

Apparently, updating the openvswitch packages cause openvswitch to restart, thereby losing its configuration (and then the cluster watchdog kills the box). For now, I'd suggest to install a policy-rc.d file blacklisting openvswitch-switch until this is resolved. Or are there better solutions? -c

This is indeed a bug in the 4.4 kernel with bnx2x cards and bridge interfaces attached to them. We've avoided this by using OVS instead. See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616107

This is now https://bugzilla.proxmox.com/show_bug.cgi?id=1169

Well yes, but migration complains about the unknown storage type.

It is my understanding "cluster awareness" comes from PVE handling it correctly, not strictly from the LVM storage plugin. Why we want to use this: these LUNs happen to be (storage-level) snapshots of other LUNs; having LVM metadata on them can only confuse the PVE hosts. We have existing...

Hi, I've found some topics on this, but they did not really answer my question so far, so have to ask again: We are planning to have a three node PVE 4.3 cluster, with LXC CTs, where most of the CTs will have "normal" LVM storage on top of FC exported LUNs. Now some CTs should also get...