fedora-infrastructure

#10808 Mailman admin errors
Closed: Fixed by kevin. Opened by bcotton.

Closed: Fixed
Reopen Issue

Describe what you would like us to do:

Mailman admin interface is erroring quite a bit in the last day or so. I've gotten a mix of HTTP 500, HTTP 503, and "Mailman API not available. Restart mailman core".

Last night, a retry or two would get me through, but I've had no success this morning.

When do you need this to be done by? (YYYY/MM/DD)

2022/07/07

I restarted mailman about 20 minutes ago. mailman3 was pretty wedged at that time. Is the problem still occurring? [If it is, I don't have a solution beyond reboot and hope]

It seems to be working now, thanks!

Metadata Update from @phsmoura:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Alas, it's being troublesome again.

Metadata Update from @bcotton:
- Issue status updated to: Open (was: Closed)

How are things looking today?

I've hit 500 and 503 a few times while removing the silly-long list of council-private subscription requests (currently at about 3,762 pending requests). But it has worked more than it has failed.

Metadata Update from @zlopez:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: Needs investigation

Things are back to normal... is this working any better for you now?

I'm still getting an occasional 500, but I think that's more due to the number of pending subscription requests that I'm trying to clear. The "normal" operations (moderating posts, etc) are working reliably.

I don't guess we are gonna do too much better here for now, so closing...

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
Metadata
None

Needs investigation

None
None
Normal
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.