infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <>
Subject [jira] [Commented] (INFRA-15103) Detecting issues with mboxer system
Date Wed, 28 Feb 2018 19:26:00 GMT


Sebb commented on INFRA-15103:

I've been able to trigger a failure.

Feb 28 18:35:28 mbox-vm postfix/local[12307]: 33BC72F9B: to=<>,
relay=local, delay=0.67, delays=0.35/0/0/0.32, dsn=5.3.0, status=bounced (Command died with
status 1: "python3 /usr/local/etc/mboxer/tools/". Command output: <>
This is for, archiving under /x1/archives/!
Return-Path: <> Message-Id:
<> Traceback (most
recent call last):   File "/usr/local/etc/mboxer/tools/", line 184, in <module>
    main()   File "/usr/local/etc/mboxer/tools/", line 164, in main     with open(path,
"ab") as f: PermissionError: [Errno 13] Permission denied: '/x1/archives/'

This message appeared in both syslog and mail.log.

However I could not find the error in blocky/Kibana; there don't appear to be any messages
from mbox-vm listed there.

> Detecting issues with mboxer system
> -----------------------------------
>                 Key: INFRA-15103
>                 URL:
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Mail Archives
>            Reporter: Sebb
>            Assignee: Chris Lambertus
>            Priority: Major
> See INFRA-15100
> The mboxer system failed to create a couple of mailboxes due to exceeding the maximum
file size.
> This was not noticed for 3 days, and it was only noticed by accident.
> There needs to be proper monitoring for mboxer errors, as it may not always be possible
to recover lost mails if a fault is left uncorrected for long.
> This particularly applies in the case of mail aliases as there are no ezmlm archives
to fall back on.

This message was sent by Atlassian JIRA

View raw message