Strange error in uwsgi-error.log
I am seeing the following error being logged every few minutes:
18:50:29 [Q] INFO Process-1:7 processing [update_from_mailman]
18:50:29 [Q] ERROR malformed return hook '
The above exception was the direct cause of the following exception:
Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/django_q/cluster.py", line 377, in worker res = f(*task['args'], **task['kwargs']) File "/usr/lib/python3.6/site-packages/hyperkitty/tasks.py", line 66, in unlock_and_call return func(*args, **kwargs) File "/usr/lib/python3.6/site-packages/hyperkitty/tasks.py", line 293, in update_from_mailman mlist.update_from_mailman() File "/usr/lib/python3.6/site-packages/hyperkitty/models/mailinglist.py", line 192, in update_from_mailman self.save() File "/usr/lib/python3.6/site-packages/django/db/models/base.py", line 718, in save force_update=force_update, update_fields=update_fields) File "/usr/lib/python3.6/site-packages/django/db/models/base.py", line 748, in save_base updated = self._save_table(raw, cls, force_insert, force_update, using, update_fields) File "/usr/lib/python3.6/site-packages/django/db/models/base.py", line 812, in _save_table forced_update) File "/usr/lib/python3.6/site-packages/django/db/models/base.py", line 861, in _do_update return filtered._update(values) > 0 File "/usr/lib/python3.6/site-packages/django/db/models/query.py", line 712, in _update return query.get_compiler(self.db).execute_sql(CURSOR) File "/usr/lib/python3.6/site-packages/django/db/models/sql/compiler.py", line 1383, in execute_sql cursor = super().execute_sql(result_type) File "/usr/lib/python3.6/site-packages/django/db/models/sql/compiler.py", line 1065, in execute_sql cursor.execute(sql, params) File "/usr/lib/python3.6/site-packages/django/db/backends/utils.py", line 68, in execute return self._execute_with_wrappers(sql, params, many=False, executor=self._execute) File "/usr/lib/python3.6/site-packages/django/db/backends/utils.py", line 77, in _execute_with_wrappers return executor(sql, params, many, context) File "/usr/lib/python3.6/site-packages/django/db/backends/utils.py", line 85, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3.6/site-packages/django/db/utils.py", line 89, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/usr/lib/python3.6/site-packages/django/db/backends/utils.py", line 85, in _execute return self.cursor.execute(sql, params) django.db.utils.IntegrityError: null value in column "description" violates not-null constraint DETAIL: Failing row contains (1, testlist@"listdomain", Testlist, null, [Testlist] , 2, 2018-12-21 22:22:08.440729+00, testlist."listdomain").
Any ideas?
Thanks, Brian
On 2/6/19 11:00 AM, brian@emwd.com wrote:
I am seeing the following error being logged every few minutes:
18:50:29 [Q] INFO Process-1:7 processing [update_from_mailman] 18:50:29 [Q] ERROR malformed return hook '
' for [update_from_mailman] 18:50:29 [Q] ERROR Failed [update_from_mailman] - null value in column "description" violates not-null constraint DETAIL: Failing row contains (1, testlist@"listdomain", Testlist, null, [Testlist] , 2, 2018-12-21 22:22:08.440729+00, testlist."listdomain"). ... Any ideas?
This looks like https://gitlab.com/mailman/hyperkitty/issues/211
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark Sapiro wrote:
This looks like https://gitlab.com/mailman/hyperkitty/issues/211
Thanks Mark. It doesn't seem to impact the functionality of the mailing list in any way and the other lists are fine and producing no errors.
Brian
Brian,
When I was seeing this, new lists weren't showing in HyperKitty.
I was migrating from 2.1, so they were all new lists and was preventing HyperKitty from functioning. I had to drop the constraint to get the lists in. None of them have a description now.
Was this working for you in the past? If so, did you do any updates recently?
Derek Lambert
On 2/6/19, 1:50 PM, "brian@emwd.com" brian@emwd.com wrote:
Mark Sapiro wrote:
> This looks like <https://urldefense.proofpoint.com/v2/url?u=https-3A__gitlab.com_mailman_hyperkitty_issues_211&d=DwICAg&c=PzM68gSF_5r1R7BCE75oeA&r=GgD_LHpJpzqCgYl9euxHhlqYAOmF-LRf0L_q26FThVM&m=_I-gVTHJvvzvsx0RGPcI-5ZEyb3fhwwG8wEQTwuApoc&s=wzo4thbXdHwkCtMD7U2sqUrfnnjKTfZDqvHMYEdm9KI&e=>
Thanks Mark. It doesn't seem to impact the functionality of the mailing list in any way and the other lists are fine and producing no errors.
Brian
_______________________________________________
Mailman-users mailing list -- mailman-users@mailman3.org
To unsubscribe send an email to mailman-users-leave@mailman3.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.mailman3.org_mailman3_lists_mailman-2Dusers.mailman3.org_&d=DwICAg&c=PzM68gSF_5r1R7BCE75oeA&r=GgD_LHpJpzqCgYl9euxHhlqYAOmF-LRf0L_q26FThVM&m=_I-gVTHJvvzvsx0RGPcI-5ZEyb3fhwwG8wEQTwuApoc&s=hoviEXyn08JmI4ozfv4q-6uW6jeJpt4FGh1ETK5yKsQ&e=Derek Lambert wrote:
Brian,
When I was seeing this, new lists weren't showing in HyperKitty.
I was migrating from 2.1, so they were all new lists and was preventing HyperKitty from functioning. I had to drop the constraint to get the lists in. None of them have a description now.
Was this working for you in the past? If so, did you do any updates recently?
Derek Lambert
Hi Derek,
Actually you are right. None of my new lists are showing in http://mailmam3domain/hyperkitty/. However if you go directly to each lists' archives then you can access their archives via HK. I also recently did an update when Postorius 1.2.3 came out. I am using the Docker images for my Mailman 3 install.
How do you drop the constraint? DId that fix the error message? So this seems to be a new bug that was introduced in the recent updates? It's weird because I know Hyperkitty was not touched.
Brian
Brian,
I'd presume it's from something recent since you only started seeing it after updating. Do you recall what the prior version was?
To drop the constraint on postgres I did:
alter table hyperkitty_mailinglist alter column description drop not null;That's pretty standard SQL so I'd imagine it'd work on other platforms.
After dropping it the error message is no longer logged, but none of the maillists have descriptions in HK.
To add the constraint back after the bug is fixed:
alter table hyperkitty_mailinglist alter column description set not null;Derek
On 2/6/19, 4:23 PM, "brian@emwd.com" brian@emwd.com wrote:
Derek Lambert wrote:
> Brian,
>
> When I was seeing this, new lists weren't showing in HyperKitty.
>
> I was migrating from 2.1, so they were all new lists and was preventing HyperKitty from
> functioning. I had to drop the constraint to get the lists in. None of them have a
> description now.
>
> Was this working for you in the past? If so, did you do any updates recently?
>
> Derek Lambert
Hi Derek,
Actually you are right. None of my new lists are showing in https://urldefense.proofpoint.com/v2/url?u=http-3A__mailmam3domain_hyperkitty_&d=DwICAg&c=PzM68gSF_5r1R7BCE75oeA&r=GgD_LHpJpzqCgYl9euxHhlqYAOmF-LRf0L_q26FThVM&m=0xjH0_ihupjmWehCCt47AFy1WHM_9FsEZL1Q2_15yY0&s=sIb_dsRLTAdL4wLKYDQdML4MZamv0ZkhM0iLwF_gFYc&e=. However if you go directly to each lists' archives then you can access their archives via HK. I also recently did an update when Postorius 1.2.3 came out. I am using the Docker images for my Mailman 3 install.
How do you drop the constraint? DId that fix the error message? So this seems to be a new bug that was introduced in the recent updates? It's weird because I know Hyperkitty was not touched.
Brian
_______________________________________________
Mailman-users mailing list -- mailman-users@mailman3.org
To unsubscribe send an email to mailman-users-leave@mailman3.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.mailman3.org_mailman3_lists_mailman-2Dusers.mailman3.org_&d=DwICAg&c=PzM68gSF_5r1R7BCE75oeA&r=GgD_LHpJpzqCgYl9euxHhlqYAOmF-LRf0L_q26FThVM&m=0xjH0_ihupjmWehCCt47AFy1WHM_9FsEZL1Q2_15yY0&s=FhQ67D3bjS0OOY_crCvVk4ka0sBnuDu0SVjzwmgSsq8&e=
participants (3)
-
brian＠emwd.com -
Derek Lambert -
Mark Sapiro