mirror of
https://github.com/modoboa/modoboa.git
synced 2026-04-25 00:46:03 +03:00
[GH-ISSUE #3072] High Cpu Usage after new installation during this week #1753
Labels
No labels
bug
bug
dependencies
design
documentation
duplicate
enhancement
enhancement
enhancement
feedback-needed
help-needed
help-needed
installer
invalid
looking-for-sponsors
modoboa-contacts
new-ui
new-ui
pr
pull-request
pyconfr
python
question
security
stale
webmail
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/modoboa-modoboa#1753
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @samuraikid0 on GitHub (Sep 22, 2023).
Original GitHub issue: https://github.com/modoboa/modoboa/issues/3072
Impacted versions
Steps to reproduce
Complete a fresh installation and look at task manager you see amavis foreground process run 99% all the time.
Current behavior
Expected behavior
System don't run at 100%
Video/Screenshot link (optional)
@samuraikid0 commented on GitHub (Sep 22, 2023):
What I've notice during installation
gevents takes 6x more time to build##############################
After install the dkim keeps red with not found all other are green I'll give it more time to see if it changes
@tonioo commented on GitHub (Sep 28, 2023):
@samuraikid0 Have you tried to restart this process?
@samuraikid0 commented on GitHub (Sep 28, 2023):
Yes, I've even purge amavisd and dkim and run the upgrade again attempting to reset the process high cpu without luck.
I'll wait to see if someone else reports thee same issue
Thanks !
@stale[bot] commented on GitHub (Mar 17, 2024):
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.
@Relic180 commented on GitHub (Oct 7, 2024):
I'm experience this as well, with a fairly similar build to OP:
Immediately after the install completed, my CPU usage shows up consistently around 80%. Prior to install, it had been between 5-15%.
I installed it yesterday originally. Overnight my VPS host capped me and sent a bunch of notifications / warnings for running at full-tilt for over 12 hours straight. Everything got stuck and unresponsive, I had to get uncapped just so I could restore from a backup image.
Trying to install again, and looks like I'm seeing the exact same thing. Restarted a couple times to be sure. CPU always hovering between 75-85%. Most terminal commands take far longer to execute than normal, etc...
@tonioo commented on GitHub (Oct 8, 2024):
Can you check which process is consuming your CPU(s) ?
@cyberarm commented on GitHub (Oct 8, 2024):
Have you checked that you're not using port 9000?
IIRC, I had a high cpu issue due to using that port and the modoboa worker attempting to bind to it, failing, and getting stuck in a loop.
@Relic180 commented on GitHub (Oct 8, 2024):
Although what ultimately kicked-off the behavior was the Modoboa installation, the issue was actually with pm2.
Not entirely sure what happened, but after the install pm2 went and fetched an outdated ecosystem config that had some no-longer-valid paths in it. So as soon as the install finished, pm2 started throwing massive errors and devouring my CPU.
Once I found it and fixed the paths, everything went back to normal. Sorry about the false alarm.