Issues after upgrade to v0.50

Ubuntu 18.04.5 LTS

when I login to the web admin page I get 'Error: Something went wrong, sorry."

also getting this emailed to me as the Status Checks Change Notice

multiprocessing.pool.RemoteTraceback:
“”"
Traceback (most recent call last):
File “/usr/lib/python3.6/multiprocessing/pool.py”, line 119, in worker
result = (True, func(*args, **kwds))
File “/usr/lib/python3.6/multiprocessing/pool.py”, line 47, in starmapstar
return list(itertools.starmap(args[0], args[1]))
File “management/status_checks.py”, line 367, in run_domain_checks_on_domain
check_mail_domain(domain, env, output)
File “management/status_checks.py”, line 625, in check_mail_domain
mxhost = mx.split(’; ‘)[0].split(’ ')[1]
IndexError: list index out of range
“”"

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File “management/status_checks.py”, line 1031, in
run_and_output_changes(env, pool)
File “management/status_checks.py”, line 876, in run_and_output_changes
run_checks(True, env, cur, pool)
File “management/status_checks.py”, line 66, in run_checks
run_domain_checks(rounded_values, env, output, pool)
File “management/status_checks.py”, line 335, in run_domain_checks
ret = pool.starmap(run_domain_checks_on_domain, args, chunksize=1)
File “/usr/lib/python3.6/multiprocessing/pool.py”, line 274, in starmap
return self._map_async(func, iterable, starmapstar, chunksize).get()
File “/usr/lib/python3.6/multiprocessing/pool.py”, line 644, in get
raise self._value
IndexError: list index out of range

@christian7

Do you have any entries on the “Custom DNS” page … specifically any MX record entries?

I do have two MX entries actually

Why? And to clarify, these are for the same domain?

I found an email alias for a domain that had expired and that caused the problem. Once I deleted the email alias the status checks logging into the web admin worked again. Now I’ll see if the daily emailed status check is also fixed. In a perfect world, this should not happen!

Correct, in a perfect world you’d not be hosting email for an expired domain.

But I am curious as to what actually caused this to happen, as I have invalid domains on one of my test installs, and have not run into this problem

I’m glad that removing the invalid alias was the solution for you. :slight_smile: