Next week I'll be going offline for 3 weeks (two of them being really off
the grid, I'm going to the European equivalent of the Burning Man
festival...), so I'd like to check with you what errors I've seen our
production Mailman3 instance do these last weeks.
I think that the main issue I haven't fixed yet is the fact that sometimes,
for an unknown reason (yet), the archiving process dies, and email isn't
archived anymore. The posts are still relayed to the subscribers, but the
email are not archived. This can be detected by two ways:
* there is no running process called "/usr/bin/python3.4
/usr/libexec/mailman3/runner --runner=archive:0:1 -C /etc/mailman.cfg" (see
the "runner" option on the command line)
* the "/var/spool/mailman3/archive/" directory starts filling up with
files. It's usually empty.
The best way to fix this is currently to restart the mailman process with
"systemctl restart mailman3". Then the unarchived emails in the backlog
will be processed, the speed is variable but it's around 1 or 2 per second.
The other problems that I've been pinged about recently are really
specific, it's either configuration problems or bugs that I've fixed now.
When it's about emails being rejected, it's usually a good idea to start
looking at the list's header filters (in Postorius).
If you have any questions, feel free to ask me. I'm leaving for the desert
on June 30th, I'll start being mildly reacheable on July 13th, and will be
back on Monday 18th.
Answers in-line. Correcting month in Subject line.
On Sat, Jul 2, 2016 at 10:31 PM, Kevin Fenzi <kevin(a)scrye.com> wrote:
> You are getting this email because you are in the 'fi-apprentice' group
> in the fedora account system (or are reading this on the
> infrastructure list).
> Feel free to reply just directly to me, or cc the infrastructure list
> for everyone to see and comment on.
> At the first of every month(or so), I am going to be sending out an
> email like this one. I would like feedback on how things are going for
> I'd like to ask for everyone to send me a quick reply with the
> following data or anything related you can think of that might help us
> make the apprentice program more useful.
> 0. Whats your fedora account system login?
> 1. Have you logged in and used your fi-apprentice membership to look at
> our machines/setup in the last month? Do you plan to?
> 2. Has it helped you decide any area you wish to focus on or contribute
> to more?
> 3. Have you looked at or been able to work on any of the fi-apprentice
> 'easyfix' tickets?
> 4. Do you still wish to be a member of the group? If not (for whatever
> reason) could you provide any hints to help others down the road?
> 5. Is there any help or communication or ideas you have that would help
> you do any of the above?
> 6. What do you find to be the hardest part of getting involved?
> Finding things to work on? Getting attention from others to help you?
> Finding tickets in your interest area?
> 7. Have you been able to make any weekly irc meetings? Do you find them
> helpful or interesting?
> 8. Have you logged into our Gobby instance and read/seen/added to our
> meeting agenda? https://fedoraproject.org/wiki/Gobby
> 9. When was the last time it rained where you are?
> Any other general feedback is also quite welcome, including
> improvements to this email, the wiki page, etc.
> Any folks I do not hear from in the next week will be removed from the
> group. (Note that it's easy to be readded when you have time or
> whatever and it's nothing at all personal, we just want to keep the
> group up to date with active folks).
> Thanks, and looking forward to your feedback!
> infrastructure mailing list
Just FYI, I have reinstalled our staging builders:
with Fedora 24.
Since we have koschei running there, we should be able to see in a bit
if things look stable or run into issues, so please do keep an eye out.