Skip to content

Crash when trying to archive mails

Quack,

After a seemingly successful migration from Mailman 2, mails were properly delivered and archives generated (well, except for one single ML affected by mailman#416). Shortly after the archives stopped being updated (while mails still get delivered properly) and I found multiple messages like this in mailman.log:

May 11 13:27:41 2018 (27869) Invalid response from HyperKitty on https://lists.ovirt.org/archives/api/mailman/archive: Expecting value: line 5 column 1 (char 4)
Traceback (most recent call last):
  File "/usr/lib/python3.4/site-packages/mailman_hyperkitty/__init__.py", line 98, in _get_url
    result = result.json()
  File "/usr/lib/python3.4/site-packages/requests/models.py", line 850, in json
    return complexjson.loads(self.text, **kwargs)
  File "/usr/lib64/python3.4/json/__init__.py", line 318, in loads
    return _default_decoder.decode(s)
  File "/usr/lib64/python3.4/json/decoder.py", line 343, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/lib64/python3.4/json/decoder.py", line 361, in raw_decode
    raise ValueError(errmsg("Expecting value", s, err.value)) from None
ValueError: Expecting value: line 5 column 1 (char 4)

I could not find a message at the same date and time in hyperkitty.log.

Nothing changed in between in the configuration.

We're using the following packages:

hyperkitty-1.1.5-0.1.el7.centos.noarch
python-django-mailman3-1.1.1-0.3.el7.centos.noarch
mailman3-selinux-3.1.1-0.6.el7.centos.noarch
mailman3-hyperkitty-1.1.1-0.2.el7.centos.noarch
mailman3-3.1.1-0.6.el7.centos.noarch
python-mailman-client-3.1.1-0.5.el7.centos.noarch
hyperkitty-selinux-1.1.5-0.1.el7.centos.noarch

Regards \_o<