I've just upgrade mailman 3 installation following Mr. Sapiro advice: did a
pip install --upgrade django-mailman3 hyperkitty mailman mailmanclient mailman-hyperkitty postorius
I did a "python3 manage.py migrate" after, too.
And all seemed to run well.
All the lists showed in postorius via web, but when I try to accesss into one of them the browser shows an error.
In the log you can see:
*-*-*-*-*-*-*
Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 119, in __getattr__ return self._get(name) File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 86, in _get raise KeyError(key) KeyError: 'get_requests_count'
... (And after all the traceback lines)
AttributeError: 'MailingList' object has no attribute 'get_requests_count'
*-*-*-*-*-*-*-*
The lists seem to be distributing messeages well.. but I cannot acces via web administration (django/postorius)
Can anyone point me in the right direction to solve this, please?
I restarted de server and the error changed. Now the log shows "KeyError: 'subscription_mode'":
ERROR 2021-02-06 11:47:49,015 26798 django.request Internal Server Error: /mailman3/mailman3/lists/name_and_domain.of.the.list Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 119, in __getattr__ return self._get(name) File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 86, in _get raise KeyError(key) KeyError: 'subscription_mode'
During handling of the above exception, another exception occurred:
Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/postorius/views/generic.py", line 74, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", line 97, in dispatch return handler(request, *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/postorius/views/list.py", line 295, in get member.subscription_mode == File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 124, in __getattr__ self.__class__.__name__, name)) AttributeError: 'Member' object has no attribute 'subscription_mode'
some info about the installed versions via pip list: pip list | grep django django-allauth 0.44.0 django-appconf 1.0.4 django-compressor 2.4 django-extensions 3.1.0 django-gravatar2 1.4.4 django-haystack 3.0 django-mailman3 1.3.5 django-picklefield 3.0.1 django-q 1.3.4 djangorestframework 3.12.2
pip list | grep mailman django-mailman3 1.3.5 mailman 3.3.3 mailman-hyperkitty 1.1.0 mailmanclient 3.3.2
pip list | grep postorius postorius 1.3.4
On 6/2/21 11:12, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
I've just upgrade mailman 3 installation following Mr. Sapiro advice: did a
pip install --upgrade django-mailman3 hyperkitty mailman mailmanclient mailman-hyperkitty postorius
I did a "python3 manage.py migrate" after, too.
And all seemed to run well.
All the lists showed in postorius via web, but when I try to accesss into one of them the browser shows an error.
In the log you can see:
*-*-*-*-*-*-*
Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 119, in __getattr__ return self._get(name) File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 86, in _get raise KeyError(key) KeyError: 'get_requests_count'
... (And after all the traceback lines)
AttributeError: 'MailingList' object has no attribute 'get_requests_count'
*-*-*-*-*-*-*-*
The lists seem to be distributing messeages well.. but I cannot acces via web administration (django/postorius)
Can anyone point me in the right direction to solve this, please?
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
On Sat, Feb 6, 2021, at 3:04 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
I restarted de server and the error changed. Now the log shows "KeyError: 'subscription_mode'":
Did you also restart Mailman Core after the upgrade?
ERROR 2021-02-06 11:47:49,015 26798 django.request Internal Server Error: /mailman3/mailman3/lists/name_and_domain.of.the.list Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 119, in __getattr__ return self._get(name) File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 86, in _get raise KeyError(key) KeyError: 'subscription_mode'
During handling of the above exception, another exception occurred:
Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/postorius/views/generic.py", line 74, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", line 97, in dispatch return handler(request, *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/postorius/views/list.py", line 295, in get member.subscription_mode == File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 124, in __getattr__ self.__class__.__name__, name)) AttributeError: 'Member' object has no attribute 'subscription_mode'
some info about the installed versions via pip list: pip list | grep django django-allauth 0.44.0 django-appconf 1.0.4 django-compressor 2.4 django-extensions 3.1.0 django-gravatar2 1.4.4 django-haystack 3.0 django-mailman3 1.3.5 django-picklefield 3.0.1 django-q 1.3.4 djangorestframework 3.12.2
pip list | grep mailman django-mailman3 1.3.5 mailman 3.3.3 mailman-hyperkitty 1.1.0 mailmanclient 3.3.2
pip list | grep postorius postorius 1.3.4
On 6/2/21 11:12, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
I've just upgrade mailman 3 installation following Mr. Sapiro advice: did a
pip install --upgrade django-mailman3 hyperkitty mailman mailmanclient mailman-hyperkitty postorius
I did a "python3 manage.py migrate" after, too.
And all seemed to run well.
All the lists showed in postorius via web, but when I try to accesss into one of them the browser shows an error.
In the log you can see:
*-*-*-*-*-*-*
Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 119, in __getattr__ return self._get(name) File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 86, in _get raise KeyError(key) KeyError: 'get_requests_count'
... (And after all the traceback lines)
AttributeError: 'MailingList' object has no attribute 'get_requests_count'
*-*-*-*-*-*-*-*
The lists seem to be distributing messeages well.. but I cannot acces via web administration (django/postorius)
Can anyone point me in the right direction to solve this, please?
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- thanks, Abhilash Raj (maxking)
On 6/2/21 18:08, Abhilash Raj wrote:
On Sat, Feb 6, 2021, at 3:04 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
I restarted de server and the error changed. Now the log shows "KeyError: 'subscription_mode'": Did you also restart Mailman Core after the upgrade?
Yes, indeed:
I stopped mailman core and all the processes related. Did the upgrades. Started all again. Find the errors in the web user interface. Stopped all again. Looked for errors in the log. Restarted the complete server.
Found the second error that this second mail is about to. It happens when, in the main page that shows all the lists you click to see one of them. It seems to me that it has been database structure changes in django that the upgrade is not aware... but it's a very long shot from my side.
I'm using sqlite as django database and mysql for mailman.
ERROR 2021-02-06 11:47:49,015 26798 django.request Internal Server Error: /mailman3/mailman3/lists/name_and_domain.of.the.list Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 119, in __getattr__ return self._get(name) File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 86, in _get raise KeyError(key) KeyError: 'subscription_mode'
During handling of the above exception, another exception occurred:
Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/postorius/views/generic.py", line 74, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", line 97, in dispatch return handler(request, *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/postorius/views/list.py", line 295, in get member.subscription_mode == File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 124, in __getattr__ self.__class__.__name__, name)) AttributeError: 'Member' object has no attribute 'subscription_mode'
some info about the installed versions via pip list: pip list | grep django django-allauth 0.44.0 django-appconf 1.0.4 django-compressor 2.4 django-extensions 3.1.0 django-gravatar2 1.4.4 django-haystack 3.0 django-mailman3 1.3.5 django-picklefield 3.0.1 django-q 1.3.4 djangorestframework 3.12.2
pip list | grep mailman django-mailman3 1.3.5 mailman 3.3.3 mailman-hyperkitty 1.1.0 mailmanclient 3.3.2
pip list | grep postorius postorius 1.3.4
On 6/2/21 11:12, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
I've just upgrade mailman 3 installation following Mr. Sapiro advice: did a
pip install --upgrade django-mailman3 hyperkitty mailman mailmanclient mailman-hyperkitty postorius
I did a "python3 manage.py migrate" after, too.
And all seemed to run well.
All the lists showed in postorius via web, but when I try to accesss into one of them the browser shows an error.
In the log you can see:
*-*-*-*-*-*-*
Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 119, in __getattr__ return self._get(name) File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 86, in _get raise KeyError(key) KeyError: 'get_requests_count'
... (And after all the traceback lines)
AttributeError: 'MailingList' object has no attribute 'get_requests_count'
*-*-*-*-*-*-*-*
The lists seem to be distributing messeages well.. but I cannot acces via web administration (django/postorius)
Can anyone point me in the right direction to solve this, please?
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
On Sat, Feb 6, 2021 at 19:44, Guillermo Hernandez (Oldno7) via Mailman-users <mailman-users@mailman3.org> wrote:
On 6/2/21 18:08, Abhilash Raj wrote:
On Sat, Feb 6, 2021, at 3:04 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
I restarted de server and the error changed. Now the log shows "KeyError: 'subscription_mode'": Did you also restart Mailman Core after the upgrade?
Yes, indeed:
I stopped mailman core and all the processes related. Did the upgrades. Started all again. Find the errors in the web user interface. Stopped all again. Looked for errors in the log. Restarted the complete server.
Found the second error that this second mail is about to. It happens when, in the main page that shows all the lists you click to see one of them. It seems to me that it has been database structure changes in django that the upgrade is not aware... but it's a very long shot from my side.
subscription_mode was added in Mailman Core 3.3.2 and it is actually
a derived atrribute and not stored in Database. Mailman's API should be
returning this attribute for each Member, but for some reason it seems
to me like it isn't doing that even though do have Mailman 3.3.3 running
like you said.
If you have Curl installed, can you send me the output of:
$ curl -u <user>:<pass> http://localhost:8001/3.1/members?count=5&page=1
It should ideally return an output that looks something like shown here1. You can put the username/password of Core's API server in the above command.
Abhilash
I'm using sqlite as django database and mysql for mailman.
ERROR 2021-02-06 11:47:49,015 26798 django.request Internal Server Error: /mailman3/mailman3/lists/name_and_domain.of.the.list Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 119, in __getattr__ return self._get(name) File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 86, in _get raise KeyError(key) KeyError: 'subscription_mode'
During handling of the above exception, another exception occurred:
Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/postorius/views/generic.py", line 74, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", line 97, in dispatch return handler(request, *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/postorius/views/list.py", line 295, in get member.subscription_mode == File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 124, in __getattr__ self.__class__.__name__, name)) AttributeError: 'Member' object has no attribute 'subscription_mode'
some info about the installed versions via pip list: pip list | grep django django-allauth 0.44.0 django-appconf 1.0.4 django-compressor 2.4 django-extensions 3.1.0 django-gravatar2 1.4.4 django-haystack 3.0 django-mailman3 1.3.5 django-picklefield 3.0.1 django-q 1.3.4 djangorestframework 3.12.2
pip list | grep mailman django-mailman3 1.3.5 mailman 3.3.3 mailman-hyperkitty 1.1.0 mailmanclient 3.3.2
pip list | grep postorius postorius 1.3.4
On 6/2/21 11:12, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
I've just upgrade mailman 3 installation following Mr. Sapiro advice: did a
pip install --upgrade django-mailman3 hyperkitty mailman mailmanclient mailman-hyperkitty postorius
I did a "python3 manage.py migrate" after, too.
And all seemed to run well.
All the lists showed in postorius via web, but when I try to accesss into one of them the browser shows an error.
In the log you can see:
*-*-*-*-*-*-*
Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 119, in __getattr__ return self._get(name) File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 86, in _get raise KeyError(key) KeyError: 'get_requests_count'
... (And after all the traceback lines)
AttributeError: 'MailingList' object has no attribute 'get_requests_count'
*-*-*-*-*-*-*-*
The lists seem to be distributing messeages well.. but I cannot acces via web administration (django/postorius)
Can anyone point me in the right direction to solve this, please?
Mailman-users mailing list -- mailman-users@mailman3.org <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave@mailman3.org <mailto:mailman-users-leave@mailman3.org> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>
Mailman-users mailing list -- mailman-users@mailman3.org <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave@mailman3.org <mailto:mailman-users-leave@mailman3.org> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>
Mailman-users mailing list -- mailman-users@mailman3.org <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave@mailman3.org <mailto:mailman-users-leave@mailman3.org> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>
On 6/2/21 21:19, Abhilash Raj wrote:
On 6/2/21 18:08, Abhilash Raj wrote:
On Sat, Feb 6, 2021, at 3:04 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: I restarted de server and the error changed. Now the log shows "KeyError: 'subscription_mode'": Did you also restart Mailman Core after the upgrade?Yes, indeed: I stopped mailman core and all the processes related. Did the upgrades. Started all again. Find the errors in the web user interface. Stopped all again. Looked for errors in the log. Restarted the complete server. Found the second error that this second mail is about to. It happens when, in the main page that shows all the lists you click to see one of them. It seems to me that it has been database structure changes in django that the upgrade is not aware... but it's a very long shot from my side.
subscription_modewas added in Mailman Core 3.3.2 and it is actually a derived atrribute and not stored in Database. Mailman's API should be returning this attribute for each Member, but for some reason it seems to me like it isn't doing that even though do have Mailman 3.3.3 runningOn Sat, Feb 6, 2021 at 19:44, Guillermo Hernandez (Oldno7) via Mailman-users <mailman-users@mailman3.org> wrote: like you said. If you have Curl installed, can you send me the output of: $ curl -u <user>:<pass> http://localhost:8001/3.1/members?count=5&page=1
This is the output you asked for (it's the same you can see when you try to interact with one list):
/usr/local/mailman3 # curl -u XXXXXX:XXXXXX http://localhost:8001/3.1/members?count=5&page=1 /usr/local/mailman3 # <html> <head> <title>Internal Server Error</title> </head> <body> <h1><p>Internal Server Error</p></h1>
</body> </html>
No log entry has been produced...
TIA.
It should ideally return an output that looks something like shown here[1]. You can put the username/password of Core's API server in the above command. [1]: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/m...
Abhilash
I'm using sqlite as django database and mysql for mailman.
ERROR 2021-02-06 11:47:49,015 26798 django.request Internal Server Error: /mailman3/mailman3/lists/name_and_domain.of.the.list Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 119, in __getattr__ return self._get(name) File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 86, in _get raise KeyError(key) KeyError: 'subscription_mode' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/postorius/views/generic.py", line 74, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", line 97, in dispatch return handler(request, *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/postorius/views/list.py", line 295, in get member.subscription_mode == File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 124, in __getattr__ self.__class__.__name__, name)) AttributeError: 'Member' object has no attribute 'subscription_mode' *********************** some info about the installed versions via pip list: pip list | grep django django-allauth 0.44.0 django-appconf 1.0.4 django-compressor 2.4 django-extensions 3.1.0 django-gravatar2 1.4.4 django-haystack 3.0 django-mailman3 1.3.5 django-picklefield 3.0.1 django-q 1.3.4 djangorestframework 3.12.2 pip list | grep mailman django-mailman3 1.3.5 mailman 3.3.3 mailman-hyperkitty 1.1.0 mailmanclient 3.3.2 pip list | grep postorius postorius 1.3.4 On 6/2/21 11:12, Guillermo Hernandez (Oldno7) via Mailman-users wrote: I've just upgrade mailman 3 installation following Mr. Sapiro advice: did a pip install --upgrade django-mailman3 hyperkitty mailman mailmanclient mailman-hyperkitty postorius I did a "python3 manage.py migrate" after, too. And all seemed to run well. All the lists showed in postorius via web, but when I try to accesss into one of them the browser shows an error. In the log you can see: *-*-*-*-*-*-* Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 119, in __getattr__ return self._get(name) File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 86, in _get raise KeyError(key) KeyError: 'get_requests_count' .. (And after all the traceback lines) AttributeError: 'MailingList' object has no attribute 'get_requests_count' *-*-*-*-*-*-*-* The lists seem to be distributing messeages well.. but I cannot acces via web administration (django/postorius) Can anyone point me in the right direction to solve this, please? _______________________________________________ Mailman-users mailing list -- mailman-users@mailman3.org <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave@mailman3.org <mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/> _______________________________________________ Mailman-users mailing list -- mailman-users@mailman3.org <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave@mailman3.org <mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/>_______________________________________________ Mailman-users mailing list -- mailman-users@mailman3.org <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave@mailman3.org <mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/>
On Sun, Feb 7, 2021, at 1:07 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
On 6/2/21 21:19, Abhilash Raj wrote:
On 6/2/21 18:08, Abhilash Raj wrote:
On Sat, Feb 6, 2021, at 3:04 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: I restarted de server and the error changed. Now the log shows "KeyError: 'subscription_mode'": Did you also restart Mailman Core after the upgrade?Yes, indeed: I stopped mailman core and all the processes related. Did the upgrades. Started all again. Find the errors in the web user interface. Stopped all again. Looked for errors in the log. Restarted the complete server. Found the second error that this second mail is about to. It happens when, in the main page that shows all the lists you click to see one of them. It seems to me that it has been database structure changes in django that the upgrade is not aware... but it's a very long shot from my side.
subscription_modewas added in Mailman Core 3.3.2 and it is actually a derived atrribute and not stored in Database. Mailman's API should be returning this attribute for each Member, but for some reason it seems to me like it isn't doing that even though do have Mailman 3.3.3 runningOn Sat, Feb 6, 2021 at 19:44, Guillermo Hernandez (Oldno7) via Mailman-users <mailman-users@mailman3.org> wrote: like you said. If you have Curl installed, can you send me the output of: $ curl -u <user>:<pass> http://localhost:8001/3.1/members?count=5&page=1
This is the output you asked for (it's the same you can see when you try to interact with one list):
/usr/local/mailman3 # curl -u XXXXXX:XXXXXX http://localhost:8001/3.1/members?count=5&page=1 /usr/local/mailman3 # <html> <head> <title>Internal Server Error</title> </head> <body> <h1><p>Internal Server Error</p></h1>
</body> </html>
No log entry has been produced...
This is weird, if you have working Core, then there should be *some* json returned
from the above command. Do you have the Gunicorn running? What is the
output of ps -ef | grep mailman?
Are you able to run mailman members command to list the members of a list?
Also, how did you actually install Mailman?
Abhilash.
TIA.
It should ideally return an output that looks something like shown here[1]. You can put the username/password of Core's API server in the above command. [1]: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/m...
Abhilash
I'm using sqlite as django database and mysql for mailman.
ERROR 2021-02-06 11:47:49,015 26798 django.request Internal Server Error: /mailman3/mailman3/lists/name_and_domain.of.the.list Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 119, in __getattr__ return self._get(name) File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 86, in _get raise KeyError(key) KeyError: 'subscription_mode' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/postorius/views/generic.py", line 74, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", line 97, in dispatch return handler(request, *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/postorius/views/list.py", line 295, in get member.subscription_mode == File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 124, in __getattr__ self.__class__.__name__, name)) AttributeError: 'Member' object has no attribute 'subscription_mode' *********************** some info about the installed versions via pip list: pip list | grep django django-allauth 0.44.0 django-appconf 1.0.4 django-compressor 2.4 django-extensions 3.1.0 django-gravatar2 1.4.4 django-haystack 3.0 django-mailman3 1.3.5 django-picklefield 3.0.1 django-q 1.3.4 djangorestframework 3.12.2 pip list | grep mailman django-mailman3 1.3.5 mailman 3.3.3 mailman-hyperkitty 1.1.0 mailmanclient 3.3.2 pip list | grep postorius postorius 1.3.4 On 6/2/21 11:12, Guillermo Hernandez (Oldno7) via Mailman-users wrote: I've just upgrade mailman 3 installation following Mr. Sapiro advice: did a pip install --upgrade django-mailman3 hyperkitty mailman mailmanclient mailman-hyperkitty postorius I did a "python3 manage.py migrate" after, too. And all seemed to run well. All the lists showed in postorius via web, but when I try to accesss into one of them the browser shows an error. In the log you can see: *-*-*-*-*-*-* Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 119, in __getattr__ return self._get(name) File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 86, in _get raise KeyError(key) KeyError: 'get_requests_count' .. (And after all the traceback lines) AttributeError: 'MailingList' object has no attribute 'get_requests_count' *-*-*-*-*-*-*-* The lists seem to be distributing messeages well.. but I cannot acces via web administration (django/postorius) Can anyone point me in the right direction to solve this, please? _______________________________________________ Mailman-users mailing list -- mailman-users@mailman3.org <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave@mailman3.org <mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/> _______________________________________________ Mailman-users mailing list -- mailman-users@mailman3.org <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave@mailman3.org <mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/>_______________________________________________ Mailman-users mailing list -- mailman-users@mailman3.org <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave@mailman3.org <mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/>
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- thanks, Abhilash Raj (maxking)
On 7/2/21 19:04, Abhilash Raj wrote:
On Sun, Feb 7, 2021, at 1:07 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
On 6/2/21 21:19, Abhilash Raj wrote:
On 6/2/21 18:08, Abhilash Raj wrote:
On Sat, Feb 6, 2021, at 3:04 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: I restarted de server and the error changed. Now the log shows "KeyError: 'subscription_mode'": Did you also restart Mailman Core after the upgrade?Yes, indeed: I stopped mailman core and all the processes related. Did the upgrades. Started all again. Find the errors in the web user interface. Stopped all again. Looked for errors in the log. Restarted the complete server. Found the second error that this second mail is about to. It happens when, in the main page that shows all the lists you click to see one of them. It seems to me that it has been database structure changes in django that the upgrade is not aware... but it's a very long shot from my side.
subscription_modewas added in Mailman Core 3.3.2 and it is actually a derived atrribute and not stored in Database. Mailman's API should be returning this attribute for each Member, but for some reason it seems to me like it isn't doing that even though do have Mailman 3.3.3 runningOn Sat, Feb 6, 2021 at 19:44, Guillermo Hernandez (Oldno7) via Mailman-users <mailman-users@mailman3.org> wrote: like you said. If you have Curl installed, can you send me the output of: $ curl -u <user>:<pass> http://localhost:8001/3.1/members?count=5&page=1
This is the output you asked for (it's the same you can see when you try to interact with one list):
/usr/local/mailman3 # curl -u XXXXXX:XXXXXX http://localhost:8001/3.1/members?count=5&page=1 /usr/local/mailman3 # <html> <head> <title>Internal Server Error</title> </head> <body> <h1><p>Internal Server Error</p></h1>
</body> </html>
No log entry has been produced... This is weird, if you have working Core, then there should be *some* json returned from the above command. Do you have the Gunicorn running?
I have the uwsgi approach running...
What is the output of
ps -ef | grep mailman?
none
but if I do an ps ax | grep mailman it shows
/usr/local/mailman3 # ps ax | grep mailman 26803 - IsJ 0:00.87 /usr/local/bin/python3.7 /usr/local/bin/master --force -C /usr/local/mailman3/var/et 26834 - SJ 0:07.57 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26835 - IJ 0:05.84 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26836 - SJ 0:07.16 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26837 - SJ 0:08.74 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26838 - SJ 0:03.16 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26839 - SJ 0:07.07 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26840 - SJ 0:08.12 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26841 - SJ 0:09.07 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26842 - SJ 0:07.45 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26843 - IJ 0:00.95 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26844 - SJ 0:07.27 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26845 - SJ 0:07.69 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26859 - IJ 0:01.01 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26860 - IJ 0:05.75 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 50153 - IsJ 0:00.16 /usr/local/bin/uwsgi --ini /usr/local/mailman3/uwsgi.ini 50481 2 S+J 0:00.00 grep mailman 26808 1 SJ 0:02.09 /usr/local/bin/uwsgi --ini /usr/local/mailman3/uwsgi.ini 26832 1 IJ 0:00.00 /usr/local/bin/uwsgi --ini /usr/local/mailman3/uwsgi.ini
Are you able to run
mailman memberscommand to list the members of a list?
Yes. All the commands are working as expected.
Also, how did you actually install Mailman?
Using pip. Here is a detailled post of how I did put all together:
https://forums.FreeBSD.org/threads/mailman-3.61050/post-488128
Thanks for your support
Abhilash.
TIA.
It should ideally return an output that looks something like shown here[1]. You can put the username/password of Core's API server in the above command. [1]: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/m...
Abhilash
I'm using sqlite as django database and mysql for mailman.
ERROR 2021-02-06 11:47:49,015 26798 django.request Internal Server Error: /mailman3/mailman3/lists/name_and_domain.of.the.list Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 119, in __getattr__ return self._get(name) File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 86, in _get raise KeyError(key) KeyError: 'subscription_mode' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/postorius/views/generic.py", line 74, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", line 97, in dispatch return handler(request, *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/postorius/views/list.py", line 295, in get member.subscription_mode == File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 124, in __getattr__ self.__class__.__name__, name)) AttributeError: 'Member' object has no attribute 'subscription_mode' *********************** some info about the installed versions via pip list: pip list | grep django django-allauth 0.44.0 django-appconf 1.0.4 django-compressor 2.4 django-extensions 3.1.0 django-gravatar2 1.4.4 django-haystack 3.0 django-mailman3 1.3.5 django-picklefield 3.0.1 django-q 1.3.4 djangorestframework 3.12.2 pip list | grep mailman django-mailman3 1.3.5 mailman 3.3.3 mailman-hyperkitty 1.1.0 mailmanclient 3.3.2 pip list | grep postorius postorius 1.3.4 On 6/2/21 11:12, Guillermo Hernandez (Oldno7) via Mailman-users wrote: I've just upgrade mailman 3 installation following Mr. Sapiro advice: did a pip install --upgrade django-mailman3 hyperkitty mailman mailmanclient mailman-hyperkitty postorius I did a "python3 manage.py migrate" after, too. And all seemed to run well. All the lists showed in postorius via web, but when I try to accesss into one of them the browser shows an error. In the log you can see: *-*-*-*-*-*-* Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 119, in __getattr__ return self._get(name) File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 86, in _get raise KeyError(key) KeyError: 'get_requests_count' .. (And after all the traceback lines) AttributeError: 'MailingList' object has no attribute 'get_requests_count' *-*-*-*-*-*-*-* The lists seem to be distributing messeages well.. but I cannot acces via web administration (django/postorius) Can anyone point me in the right direction to solve this, please? _______________________________________________ Mailman-users mailing list -- mailman-users@mailman3.org <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave@mailman3.org <mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/> _______________________________________________ Mailman-users mailing list -- mailman-users@mailman3.org <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave@mailman3.org <mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/>_______________________________________________ Mailman-users mailing list -- mailman-users@mailman3.org <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave@mailman3.org <mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/>
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
On 7/2/21 19:33, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
On 7/2/21 19:04, Abhilash Raj wrote:
Well... I did reinstall all mailman relationed apps with a
pip install --upgrade --force-reinstall --no-deps --no-cache-dir django-mailman3 mailman mailman-hyperkitty mailmanclient
Restarted thee apache24 server...
Aaaaaand closed de admin session and reopened it... (just for a "what if" sensation).
I can not tell what have been the solution here, but now I can access the administrative pages and attend de pending subscriptions and discard retained messages.
Thanks Abhilash and Mark for your support.
On Sun, Feb 7, 2021, at 1:07 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
On 6/2/21 21:19, Abhilash Raj wrote:
On 6/2/21 18:08, Abhilash Raj wrote:
On Sat, Feb 6, 2021, at 3:04 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
I restarted de server and the error changed. Now the log shows "KeyError: 'subscription_mode'":
Did you also restart Mailman Core after the upgrade?
Yes, indeed: I stopped mailman core and all the processes related. Did the upgrades. Started all again. Find the errors in the web user interface. Stopped all again. Looked for errors in the log. Restarted the complete server. Found the second error that this second mail is about to. It happens when, in the main page that shows all the lists you click to see one of them. It seems to me that it has been database structure changes in django that the upgrade is not aware... but it's a very long shot from my side.
subscription_modewas added in Mailman Core 3.3.2 and it is actually a derived atrribute and not stored in Database. Mailman's API should be returning this attribute for each Member, but for some reason it seems to me like it isn't doing that even though do have Mailman 3.3.3 runningOn Sat, Feb 6, 2021 at 19:44, Guillermo Hernandez (Oldno7) via Mailman-users <mailman-users@mailman3.org> wrote: like you said. If you have Curl installed, can you send me the output of: $ curl -u <user>:<pass> http://localhost:8001/3.1/members?count=5&page=1
This is the output you asked for (it's the same you can see when you try to interact with one list):
/usr/local/mailman3 # curl -u XXXXXX:XXXXXX http://localhost:8001/3.1/members?count=5&page=1 /usr/local/mailman3 # <html> <head> <title>Internal Server Error</title> </head> <body> <h1><p>Internal Server Error</p></h1>
</body> </html>
No log entry has been produced... This is weird, if you have working Core, then there should be *some* json returned from the above command. Do you have the Gunicorn running?
I have the uwsgi approach running...
What is the output of
ps -ef | grep mailman?none
but if I do an ps ax | grep mailman it shows
/usr/local/mailman3 # ps ax | grep mailman 26803 - IsJ 0:00.87 /usr/local/bin/python3.7 /usr/local/bin/master --force -C /usr/local/mailman3/var/et 26834 - SJ 0:07.57 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26835 - IJ 0:05.84 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26836 - SJ 0:07.16 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26837 - SJ 0:08.74 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26838 - SJ 0:03.16 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26839 - SJ 0:07.07 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26840 - SJ 0:08.12 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26841 - SJ 0:09.07 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26842 - SJ 0:07.45 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26843 - IJ 0:00.95 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26844 - SJ 0:07.27 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26845 - SJ 0:07.69 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26859 - IJ 0:01.01 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26860 - IJ 0:05.75 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 50153 - IsJ 0:00.16 /usr/local/bin/uwsgi --ini /usr/local/mailman3/uwsgi.ini 50481 2 S+J 0:00.00 grep mailman 26808 1 SJ 0:02.09 /usr/local/bin/uwsgi --ini /usr/local/mailman3/uwsgi.ini 26832 1 IJ 0:00.00 /usr/local/bin/uwsgi --ini /usr/local/mailman3/uwsgi.ini
Are you able to run
mailman memberscommand to list the members of a list?Yes. All the commands are working as expected.
Also, how did you actually install Mailman?
Using pip. Here is a detailled post of how I did put all together:
https://forums.FreeBSD.org/threads/mailman-3.61050/post-488128
Thanks for your support
Abhilash.
TIA.
It should ideally return an output that looks something like shown here[1]. You can put the username/password of Core's API server in the above command. [1]: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/m...
Abhilash
I'm using sqlite as django database and mysql for mailman.
ERROR 2021-02-06 11:47:49,015 26798 django.request Internal Server Error: /mailman3/mailman3/lists/name_and_domain.of.the.list Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py",
line 119, in __getattr__ return self._get(name) File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py",
line 86, in _get raise KeyError(key) KeyError: 'subscription_mode' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py",
line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py",
line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py",
line 71, in view return self.dispatch(request, *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/postorius/views/generic.py", line 74, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py",
line 97, in dispatch return handler(request, *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/postorius/views/list.py", line 295, in get member.subscription_mode == File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py",
line 124, in __getattr__ self.__class__.__name__, name)) AttributeError: 'Member' object has no attribute 'subscription_mode' *********************** some info about the installed versions via pip list: pip list | grep django django-allauth 0.44.0 django-appconf 1.0.4 django-compressor 2.4 django-extensions 3.1.0 django-gravatar2 1.4.4 django-haystack 3.0 django-mailman3 1.3.5 django-picklefield 3.0.1 django-q 1.3.4 djangorestframework 3.12.2 pip list | grep mailman django-mailman3 1.3.5 mailman 3.3.3 mailman-hyperkitty 1.1.0 mailmanclient 3.3.2 pip list | grep postorius postorius 1.3.4 On 6/2/21 11:12, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
I've just upgrade mailman 3 installation following Mr. Sapiro advice: did a pip install --upgrade django-mailman3 hyperkitty mailman mailmanclient mailman-hyperkitty postorius I did a "python3 manage.py migrate" after, too. And all seemed to run well. All the lists showed in postorius via web, but when I try to accesss into one of them the browser shows an error. In the log you can see: *-*-*-*-*-*-* Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py",
line 119, in __getattr__ return self._get(name) File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py",
line 86, in _get raise KeyError(key) KeyError: 'get_requests_count' .. (And after all the traceback lines) AttributeError: 'MailingList' object has no attribute 'get_requests_count' *-*-*-*-*-*-*-* The lists seem to be distributing messeages well.. but I cannot acces via web administration (django/postorius) Can anyone point me in the right direction to solve this, please? _______________________________________________ Mailman-users mailing list -- mailman-users@mailman3.org <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave@mailman3.org <mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/>
_______________________________________________ Mailman-users mailing list -- mailman-users@mailman3.org <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave@mailman3.org <mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/>
_______________________________________________ Mailman-users mailing list -- mailman-users@mailman3.org <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave@mailman3.org <mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/>
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
On 8/2/21 11:26, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
On 7/2/21 19:33, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
On 7/2/21 19:04, Abhilash Raj wrote:
Well... I did reinstall all mailman relationed apps with a
pip install --upgrade --force-reinstall --no-deps --no-cache-dir django-mailman3 mailman mailman-hyperkitty mailmanclient
Restarted thee apache24 server...
Aaaaaand closed de admin session and reopened it... (just for a "what if" sensation).
I can not tell what have been the solution here, but now I can access the administrative pages and attend de pending subscriptions and discard retained messages.
Thanks Abhilash and Mark for your support.
Some things did not work well enough after that (the subscriptions pending approval, between others), and then I did an
pip install --upgrade --force-reinstall --no-deps --no-cache-dir django-mailman3 mailman mailman-hyperkitty mailmanclient postorius django
(adding postorius and django to my previous reinstall)
And a
su -m mailman3 -c "python3 manage.py collectstatic"
in the mailman dir (mailman3 is the user who exectues all mailman related things)
and again a
su -m mailman3 -c "python3 manage.py migrate"
And it seems there were things pendig to update...
Restarted the server and now it seems all is OK.
Thanks all and sorry for the noise.
On 2/6/21 10:44 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
I'm using sqlite as django database and mysql for mailman.
I'm not certain about this, but having separate databases for Django and Mailman core may be an issue.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 7/2/21 18:35, Mark Sapiro wrote:
On 2/6/21 10:44 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
I'm using sqlite as django database and mysql for mailman.
I'm not certain about this, but having separate databases for Django and Mailman core may be an issue.
Thanks for your reply.
I'm aware by this list that some people had problems using mysql in upgrades from previous releases. That was my first thought... But it seems that the problem is not database related. As far as I can see is about some missing properties in the "REST" process from 3.3.2 to 3.3.3 or maybe some template is not well upgraded even I did a "migrate" command.
I installed mailman 3 in 24th of last december, with 3.3.2 version and all worked as expected. It's my first upgrade.
participants (3)
-
Abhilash Raj -
Guillermo Hernandez (Oldno7) -
Mark Sapiro