Closed entr0p1 closed 4 years ago
Hm, which procs do the high cpu usage then? And when? I only see 0.x. :)
That’s the thing, it’s always practically in a state of idle (Load averages 0.x) and I can’t work out why.
I wish the solution were as simple as throwing more resources at it :)
Hm. Even when it becodes slow/laggy? That's strange indeed. Does it show a high "wa" (io wait) in top?
Yeah, the slowness is constant but any CPU spikes are usually short-lived and associated with some sort of task (like the ClamAV updates). Here's the heading from top
right now:
top - 23:34:06 up 3:43, 2 users, load average: 0.06, 0.16, 0.17
Tasks: 377 total, 1 running, 278 sleeping, 0 stopped, 0 zombie
%Cpu(s): 2.8 us, 2.5 sy, 0.0 ni, 94.1 id, 0.0 wa, 0.0 hi, 0.5 si, 0.0 st
KiB Mem : 7944772 total, 3135608 free, 3454208 used, 1354956 buff/cache
KiB Swap: 4192252 total, 3986428 free, 205824 used. 4550248 avail Mem
But the server is fine as long as these spikes are not there?
I could think of a sudden high io wait. :/ ClamAV is heavy on the CPU and disk when reloading signatures.
Can you further monitor it? Did you run update.sh recently?
Nope, the slowness is constant :/ so for an example I've just loaded a random section of the admin interface and it's showing the loading spinner (in screenshot). The second screenshot is of the top
command 1 minute later. The interface is still loading, but the VM doesn't seem to be doing a whole lot...
Does it log anything in the browser dev console?
Nothing of interest, just warning me that the XSS header is bad so its being ignored
I'm wondering if maybe we start turning containers off one-by-one would that help us find a culprit perhaps?
I have seriously no idea. I thought about it, too. Can you start with netfilter-mailcow?
Okay I tried stopping them all one-by-one and it didn't settle for some reason. Any ideas?
I doubt it is mailcow then. It didn't stop when you stopped all containers?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Prior to placing the issue, please check following: (fill out each checkbox with a
X
once done)Description of the bug: Hi guys, I'm having some interesting performance issues with the VM I run my Mailcow instance on. It may not necessarily be a bug with Mailcow, but it seems to have occurred after an update of either Mailcow or the system (I usually do them at the same time) and I'm wondering if maybe you've seen anything like this.
The web interface is really slow to click through, clients take a very long time to refresh mailboxes (using ActiveSync), and even the VM itself seems to be performing badly (e.g. if I run a "yum update" it will sit at the blinking cursor for a good couple of minutes before it even starts reaching out to servers). The CLI itself is fairly responsive, just any sort of commands that take any "thought".
The VM runs under Hyper-V 2019 and has the following specs: CPU cores: 2 (Intel Xeon X5650) RAM: 8GB Disk: /var is 50GB (15% used) and /opt is 20GB (1% used)
So the strange thing is, I can't pinpoint what the exact cause is. CPU looks fine and load averages are low;
0.00, 0.04, 0.02
.There is plenty of free memory:
Disk IO seems to be fine too:
Disks are laid out as:
If I stop the mailcow processes, everything is snappy and responsive again (commands run quickly, VM performs well). As soon as I start them again, everything is back to a crawl.
Here's where it gets really weird. There are about 20 VMs on this host, all of which are performing really well and don't display any of these symptoms. The host itself is specced with:
My issue is...
Reproduction of said bug: How exactly do you reproduce the bug?
I have tried or I do... (fill out each checkbox with a
X
if applicable)System information
Further information (where applicable):
docker version
)docker-compose version
)Further notes:
git diff origin/master
, any other changes to the code? If so, please post them.firewall-cmd --list-all
public (active) target: default icmp-block-inversion: no interfaces: eth0 sources: services: dhcpv6-client https imaps smtp smtp-submission smtps ssh ports: protocols: masquerade: no forward-ports: source-ports: icmp-blocks: rich rules:
docker exec -it $(docker ps -qf name=acme-mailcow) dig +short stackoverflow.com @172.22.1.254
151.101.1.69 151.101.65.69 151.101.129.69 151.101.193.69
docker exec -it $(docker ps -qf name=acme-mailcow) dig +short stackoverflow.com @1.1.1.1
151.101.129.69 151.101.193.69 151.101.1.69 151.101.65.69
Any input or guidance greatly appreciated, thanks!