[GH-ISSUE #899] 100% cpu on logout #787

Closed
opened 2026-02-27 11:13:32 +03:00 by kerem · 8 comments
Owner

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 uwsgi

Any idea where it could come from ?

I am using the modoboa version: 1.5.3 and ldap authentication backend.

Romain

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 uwsgi` Any idea where it could come from ? I am using the modoboa version: 1.5.3 and ldap authentication backend. Romain
kerem closed this issue 2026-02-27 11:13:32 +03:00
Author
Owner

@romainreuillon commented on GitHub (Jul 18, 2016):

I forgot to tell that the 100% uwsgi process never ends...

<!-- gh-comment-id:233345268 --> @romainreuillon commented on GitHub (Jul 18, 2016): I forgot to tell that the 100% uwsgi process never ends...
Author
Owner

@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)

<!-- gh-comment-id:233351487 --> @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)
Author
Owner

@romainreuillon commented on GitHub (Jul 18, 2016):

I just tested it and it works fine with non-ldap users (admin and a test user).

<!-- gh-comment-id:233355949 --> @romainreuillon commented on GitHub (Jul 18, 2016): I just tested it and it works fine with non-ldap users (admin and a test user).
Author
Owner

@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.

<!-- gh-comment-id:242718549 --> @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.
Author
Owner

@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?

<!-- gh-comment-id:243073447 --> @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?
Author
Owner

@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.

<!-- gh-comment-id:243074888 --> @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.
Author
Owner

@hardikvala commented on GitHub (Aug 29, 2016):

Hi is this bounty still open.
I think I can help you on this

<!-- gh-comment-id:243146520 --> @hardikvala commented on GitHub (Aug 29, 2016): Hi is this bounty still open. I think I can help you on this
Author
Owner

@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.

<!-- gh-comment-id:243148477 --> @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.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/modoboa-modoboa#787
No description provided.