Krinetzki, Stephan writes: > The logrotate is executed by a system Timer (Rocky 9 OS btw) and is > planned for: So every day at midnight.
OK, that's confirmed then. > >That is not normal. Your control process is crashing every 15-20 > >seconds. > I saw this but I don't have any idea how this happens. Well, neither do we. As I say it's not normal. To investigate, first, you can move either the logrotate job or the digest-sending job to a different time. That would make it clear which event (or both) is connected to the problem. Second, find those exception tracebacks. They may be in the logs somewhere. Reenable email reports on the send-digest cron job, that's now a high-probability source of problem information. There is no top-level logging to files in that job, although there may be some internal modules that do logging. Most likely it just dumps exception information to stdout or stderr, which is currently going to /dev/null. Third, you can try moving the $mailman_home/lists/$list/digest.mmdf files for the problem lists. Don't delete them, just get them out of the way. If mail starts flowing to the lists we can be pretty sure content in the digest files is at least part of the issue. > Currently there are ~42 Mails after 'mailman unshunt' and I think, > mailman loops over them (queue doesn't get shorter). That's what I expected. Pretty sure there's an issue with the content of some messages and/or the digest files. Your situation may be different, but in the past that's almost always been the cause of inconsistency across time or across lists. > But mails are delivered for a lot of lists. That would be the case if the problem lists in question have invalid content and the ones being delivered don't. > So I should update my logging config. Do you have a good example or > maybe even the dist? You quoted it: > >I haven't thought about it carefully, but I would have separate > >logs for bounces, subscriptions, smtp, and nntp because they are > >quite separate. Everything else would go into mailman.log, because > >that makes it easier to trace a single message through the whole > >process. > >Until you know that you don't need it, I would have most channels > >at the info level. The debug level is almost never useful unless > >you're a developer trying to fix something (vs a troubleshooter > >trying to diagnose the problem). The logs compress very well > >(often 70% reduction), so it's generally a good idea to include > >the extra information at info level. Remember, the real explosion > >is logging is that outgoing mail gets logged up to 43k times per > >incoming post. Of course you can do quite a bit better if you can > >sacrifice the personalized footers, but most sites don't anymore > >because there are strict rules about convenience of > >unsubscription. > > > Well...i will stop the restart after the log rotate today. > > You can do that if you want, but it's likely that you'll end up losing logs. By "losing logs", I mean whole files. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan _______________________________________________ Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-le...@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/LMDO7L7BPJH4HUIE3DS4TF3J5D72FLNU/ This message sent to arch...@mail-archive.com
