mirror of
https://github.com/modoboa/modoboa.git
synced 2026-04-25 17:06:01 +03:00
[GH-ISSUE #899] 100% cpu on logout #787
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#787
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 @romainreuillon on GitHub (Jul 18, 2016).
Original GitHub issue: https://github.com/modoboa/modoboa/issues/899
Dear Devs,
I got a 100% CPU usage of uwgi on modoboa logout (as soon as I click on the logout link uwsgi gets to 100%):
4729 modoboa 20 0 301960 89708 14144 R 99,7 2,2 0:08.70 uwsgiAny idea where it could come from ?
I am using the modoboa version: 1.5.3 and ldap authentication backend.
Romain
@romainreuillon commented on GitHub (Jul 18, 2016):
I forgot to tell that the 100% uwsgi process never ends...
@tonioo commented on GitHub (Jul 18, 2016):
Looks like there is an infinite loop somewhere... Have you tried using a local account ? (ie non LDAP)
@romainreuillon commented on GitHub (Jul 18, 2016):
I just tested it and it works fine with non-ldap users (admin and a test user).
@ogg1980 commented on GitHub (Aug 26, 2016):
I have the same problem. Not using LDAP.
SimpleUsers results in 100% cpu usage by a uwsgi process and they never get logged out.
Also DomainAdmins.
SuperAdmins can log in / out just fine without any cpu spikes.
Modoboa version 1.5.3.
@tonioo commented on GitHub (Aug 29, 2016):
The issue reported by @ogg1980 was due to a wrong filesystem configuration. (emails were not stored into the location used by dovecot)
@romainreuillon Could you try to logout with such a user and check mail logs to see if there is anything interesting inside?
@romainreuillon commented on GitHub (Aug 29, 2016):
Great ! Next time I plan to work on this is at the end of September. I'll give it a try then.
@hardikvala commented on GitHub (Aug 29, 2016):
Hi is this bounty still open.
I think I can help you on this
@tonioo commented on GitHub (Aug 29, 2016):
@hardikvala Thank you but the bounty is closed.
@romainreuillon I close the issue for now (required by bountysource). Do not hesitate to reopen it when you'll do your tests.