Search results for "Postorius" - Mailman-users

Re: including a template failed

by Mark Sapiro

On 9/19/20 2:47 PM, Wolfgang Bock via Mailman-users wrote: > Hi, > > I created a new mailinglist and got during the test-process the following > errormessage in my mailman.log after: > ... > Sep 19 22:55:08 2020 (1433) ACCEPT: > <000001d68ec7$2553e6e0$6ffbb4a0$(a)domain-01.de> > > Errors: > > Sep 19 22:55:09 2020 (1436) Cannot connect to SMTP server localhost on port > 25 > HTTPSConnectionPool(host='webmail.domain-02.de', port=443): Max retries > exceeded with url: > /mailman3/postorius/api/templates/list/mylist.lists.domain-03.de/list:member > :regular:footer (Caused by NewConnectionError('<urllib3.connec > tion.VerifiedHTTPSConnection object at 0x7fc8380f1748>: Failed to establish > a new connection: [Errno -2] Name or service not known')) > ... This is wierd. It looks like we are trying to establish a connection to host='webmail.domain-02.de', port=443 in order to GET /mailman3/postorius/api/templates/list/mylist.lists.domain-03.de/list:member:regular:footer, but the error says "Cannot connect to SMTP server localhost on port 25". I have no idea how port 25 is coming into it. Can you get https://webmail.domain-02.de/mailman3/postorius/api/templates/list/mylist.l… on the Mailman machine? What is your setting for POSTORIUS_TEMPLATE_BASE_URL? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

500 Internal Server Error on specific list pages

by Johnny Cison

I have a new Mailman 3 server set up and am having a strange issue with just one particular list. Accessing the list's Info page URL or it's Archiving Settings page URL returns a 500 Internal Server Error, but its other pages work correctly. Also, the Info and Archiving pages on the other lists are working correctly. When I access the info page for the problem list, I get these errors in the log: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/django/core/handlers/exception.py", line 41, in inner response = get_response(request) File "/usr/lib/python2.7/dist-packages/django/core/handlers/base.py", line 249, in _legacy_get_response response = self._get_response(request) File "/usr/lib/python2.7/dist-packages/django/core/handlers/base.py", line 187, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/lib/python2.7/dist-packages/django/core/handlers/base.py", line 185, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python2.7/dist-packages/django/views/generic/base.py", line 68, in view return self.dispatch(request, *args, **kwargs) File "/usr/lib/python2.7/dist-packages/postorius/views/generic.py", line 59, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/usr/lib/python2.7/dist-packages/django/views/generic/base.py", line 88, in dispatch return handler(request, *args, **kwargs) File "/usr/lib/python2.7/dist-packages/postorius/views/list.py", line 216, in get 'hyperkitty' in self.mailing_list.archivers and File "/usr/lib/python2.7/_abcoll.py", line 388, in __contains__ self[key] File "/usr/lib/python2.7/dist-packages/mailmanclient/restbase/base.py", line 151, in __getitem__ return self._get(key) File "/usr/lib/python2.7/dist-packages/mailmanclient/restbase/base.py", line 90, in _get return self.rest_data[key] File "/usr/lib/python2.7/dist-packages/mailmanclient/restbase/base.py", line 76, in rest_data response, content = self._connection.call(self._url) File "/usr/lib/python2.7/dist-packages/mailmanclient/restbase/connection.py", line 103, in call raise HTTPError(url, response.status, content, response, None) HTTPError: HTTP Error 500: A server error occurred. Please contact the administrator. When I access the Archiving page in Settings, I get these: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/django/core/handlers/exception.py", line 41, in inner response = get_response(request) File "/usr/lib/python2.7/dist-packages/django/core/handlers/base.py", line 249, in _legacy_get_response response = self._get_response(request) File "/usr/lib/python2.7/dist-packages/django/core/handlers/base.py", line 187, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/lib/python2.7/dist-packages/django/core/handlers/base.py", line 185, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python2.7/dist-packages/django/contrib/auth/decorators.py", line 23, in _wrapped_view return view_func(request, *args, **kwargs) File "/usr/lib/python2.7/dist-packages/postorius/auth/decorators.py", line 39, in wrapper return fn(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/postorius/views/list.py", line 719, in list_settings form = form_class(initial=initial_data, mlist=m_list) File "/usr/lib/python2.7/dist-packages/postorius/forms.py", line 303, in __init__ [(key, key) for key in sorted(self._mlist.archivers.keys())]) File "/usr/lib/python2.7/dist-packages/mailmanclient/restbase/base.py", line 172, in keys return list(self) File "/usr/lib/python2.7/dist-packages/mailmanclient/restbase/base.py", line 166, in __len__ return len(self.rest_data) File "/usr/lib/python2.7/dist-packages/mailmanclient/restbase/base.py", line 76, in rest_data response, content = self._connection.call(self._url) File "/usr/lib/python2.7/dist-packages/mailmanclient/restbase/connection.py", line 103, in call raise HTTPError(url, response.status, content, response, None) HTTPError: HTTP Error 500: A server error occurred. Please contact the administrator. Not a python developer, which makes debugging based on the above more difficult. I've seen some other errors posted to this list that highlight specific setting or config issues, but I'm not seeing that in these. Any ideas?

5 years

import21 / hyperkitty_import: sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none()

by Christian Schwarz

Hi all, after upgrading from Mailman 2.1 to Mailman 3 (Debian Buster), one (but not all) of the lists causes the following exception. The list was imported using import21 and archives were imported using manage.py hyperkitty_import. Jul 29 10:19:43 2019 (761) REST request handler error: Traceback (most recent call last): File "/usr/lib/python3.7/wsgiref/handlers.py", line 137, in run self.result = application(self.environ, self.start_response) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 50, in wrapper rtn = function(*args, **kws) File "/usr/lib/python3/dist-packages/mailman/rest/wsgiapp.py", line 216, in __call__ return super().__call__(environ, start_response) File "falcon/api.py", line 215, in falcon.api.API.__call__ File "falcon/api.py", line 189, in falcon.api.API.__call__ File "/usr/lib/python3/dist-packages/mailman/rest/lists.py", line 402, in on_get archiver_set = IListArchiverSet(self._mlist) File "/usr/lib/python3/dist-packages/zope/interface/interface.py", line 135, in __call__ adapter = self.__adapt__(obj) File "/usr/lib/python3/dist-packages/zope/interface/interface.py", line 151, in __adapt__ adapter = hook(self, obj) File "/usr/lib/python3/dist-packages/zope/component/_api.py", line 156, in adapter_hook return sitemanager.queryAdapter(object, interface, name, default) File "/usr/lib/python3/dist-packages/zope/interface/registry.py", line 348, in queryAdapter return self.adapters.queryAdapter(object, interface, name, default) File "/usr/lib/python3/dist-packages/zope/interface/adapter.py", line 353, in queryAdapter return self.adapter_hook(provided, object, name, default) File "/usr/lib/python3/dist-packages/zope/interface/adapter.py", line 363, in adapter_hook result = factory(object) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3/dist-packages/mailman/model/mailinglist.py", line 607, in __init__ ListArchiver.name == archiver_name).one_or_none() File "/usr/lib/python3/dist-packages/sqlalchemy/orm/query.py", line 3017, in one_or_none "Multiple rows were found for one_or_none()" sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none() I got that from the log file /var/log/mailman3/mailman.log. The Installation also sends emails to me, indicating some kind of exception in the except branch (see below). What can I do to debug this? Thanks, Christian --------------------------------------------- Internal Server Error: /postorius/lists/LISTNAMEREDACTED/ KeyError at /postorius/lists/LISTNAMEREDACTED/ 'file' Traceback: File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner 41. response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 187. response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 185. response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py" in view 68. return self.dispatch(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/postorius/views/generic.py" in dispatch 65. return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py" in dispatch 88. return handler(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/postorius/views/list.py" in get 252. 'hyperkitty' in self.mailing_list.archivers and # noqa: W504 File "/usr/lib/python3.7/_collections_abc.py" in __contains__ 666. self[key] File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py" in __getitem__ 151. return self._get(key) File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py" in _get 90. return self.rest_data[key] File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py" in rest_data 76. response, content = self._connection.call(self._url) File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py" in call 99. raise HTTPError(url, response.status, content, response, None) During handling of the above exception (HTTP Error 500: b'A server error occurred. Please contact the administrator.'), another exception occurred: File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner 41. response = get_response(request) File "/usr/lib/python3/dist-packages/postorius/middleware.py" in __call__ 39. return self.get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner 43. response = response_for_exception(request, exc) File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in response_for_exception 93. response = handle_uncaught_exception(request, get_resolver(get_urlconf()), sys.exc_info()) File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in handle_uncaught_exception 135. extra={'status_code': 500, 'request': request}, File "/usr/lib/python3.7/logging/__init__.py" in error 1412. self._log(ERROR, msg, args, **kwargs) File "/usr/lib/python3.7/logging/__init__.py" in _log 1519. self.handle(record) File "/usr/lib/python3.7/logging/__init__.py" in handle 1529. self.callHandlers(record) File "/usr/lib/python3.7/logging/__init__.py" in callHandlers 1591. hdlr.handle(record) File "/usr/lib/python3.7/logging/__init__.py" in handle 905. self.emit(record) File "/usr/lib/python3/dist-packages/django/utils/log.py" in emit 118. reporter = ExceptionReporter(request, is_email=True, *exc_info) File "/usr/lib/python3/dist-packages/django/views/debug.py" in __init__ 246. self.template_info = getattr(self.exc_value, 'template_debug', None) File "/usr/lib/python3.7/tempfile.py" in __getattr__ 614. file = self.__dict__['file'] Exception Type: KeyError at /postorius/lists/LISTNAMEREDACTED/ Exception Value: 'file'

6 years

Re: Change digest frequency and default threshold

by Mark Sapiro

On 9/21/18 6:21 AM, Henrik Rasmussen wrote: > When creating a new list in Mailman 3, the Digest Size Threshold is set to 30KB, which is not much in my opnion. > > 1) How do I set another default for Digest Size Threshold for new lists. It's hard coded in mailman/styles/base.py. It should be a config setting, but I think it's not. > 2) How do I change the default for existing lists Postorius -> Settings -> Digest > When Digest Size Threshold is not reached, mails seems to be sent according to digest_volume_frequency': which is set to 'monthly'. The web interface doesn't seem to have a setting for this. No. digest_volume_frequency only controls how often the digest volume number increments (and issue number resets). In order to send periodic digests, you need to run 'mailman digests --periodic' via cron. > How do I change this setting, both on a single list and the default for new lists? The only setting is the lists digest_send_periodic which again is hard coded (to True) in mailman/styles/base.py. For existing lists, it is exposed in REST, but not yet in Postorius. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 10 months

Re: mailing list aliases

by Mark Sapiro

On 01/19/2018 03:09 PM, Dmitry Makovey wrote: > Not sure whether to mark this "SOLVED" yet - but when I manually updated > postgres DB with the aliases I wanted - everything started to work as > expected. > > so it does sound like a bug in mailman-core 3.3.0 . Shall I file it or > was it already fixed in 3.3.1 (anouncement page didn't list that fix) As far as I know, this is not a bug in core. It is <https://gitlab.com/mailman/postorius/issues/58> however, this may in fact be a bug in the REST API in which case I don't think it's fixed in API 3.3.1 >> 2. Related to #1 - we've migrated our mailing lists from foo(a)my.com to >> foo(a)lists.my.com however we've preserved old addresses. But in new setup >> mail sent in gets stopped for moderation with: "X-Mailman-Rule-Hits: >> implicit-dest" . What's the best course of action here to get mailing >> list respond to multiple email addresses? acceptable_aliases is the way to address this, but as you note, it can't be properly set via Postorius and possibly via REST. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 6 months

Re: Member Issue Discovered

by Brian Carpenter

On 10/29/20 11:26 AM, Mark Sapiro wrote: > On 10/29/20 5:17 AM, Brian Carpenter wrote: >> On 10/29/20 4:27 AM, Alex Schuilenburg via Mailman-users wrote: >>> On 29/10/2020 01:57, Brian Carpenter wrote: >>>> With Mailman 3, every list owner has the ability to remove a reply in >>>> a thread, a complete thread, and even the entire archives. That is a >>>> welcome difference from MM2 in my opinion. >>> A very welcome difference, only I don't see this option in the web >>> interface of my debian 3.2.1 installation. Is this a shell only >>> option, 3.3 feature or configuration option I have missed? >> It is not a shell option. It can be done via Hyperkitty but I am not >> sure when that feature showed up. > > Actually, with current HyperKitty, only site admins can remove messages > or threads or the archive. The ability for list owners to do it is > <https://gitlab.com/mailman/hyperkitty/-/issues/261>. Thanks Mark. To clarify more, we have this ability for List owners with our own custom admin interface (Affinity). I thought Postorius had that. When I checked out Postorius, I was indeed logged in as server owner. Sorry for the incorrect info. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 9 months

Mails are not archived at all -- how to check if Hyperkitty is running or not?

by Stephen J. Turnbull

Franklin Weng writes: > However in the Archive section I couldn't see anything and all the > lists were "inactive" and hence were hidden by default. If you can see that much, HyperKitty is running. > There is no systemd service for Hyperkitty. systemd runs Apache, which loads mod_wsgi, which runs Python, which imports the HyperKitty package, which responds to web requests by building pages dynamically using Django from information from Django's database, which may be backed by MySQL, PostgreSQL, or sqlite3. Sounds complicated, but it performs well once you get it properly configured. Have you sent mail to the lists? Has it been delivered to subscribers? > I confirmed that api_key set in the /etc/mailman3/mailman-hyperkitty.cfg > and /etc/mailman3/mailman-web.py is the same. I also confirmed that the > apache2 wsgi module has been loaded. > > In the mailman.cfg database is set to mysql and in the mailman-web.py > database is set to sqlite3. Does it matter? I don't think they need to be the same. The HyperKitty and Postorius databases are a Django database backed by an RDBMS (typically sqlite3, PostgreSQL, or MySQL). The databases used by the Mailman core and the Django webservices HyperKitty and Postorius are conceptually separate, although they can be backed by the same RDBMS server. However, sqlite3 is likely to result in poor performance compared to PostgreSQL or MySQL. You have to configure HyperKitty's database. In my sqlite3 test installation it looks like this: # Top of settings.py. BASE_DIR is the directory containing settings.py. BASE_DIR = os.path.dirname(os.path.dirname(os.path.abspath(__file__))) # 30-50 lines later: DATABASES = { 'default': { 'ENGINE': 'django.db.backends.sqlite3', # This database file is in the same directory as settings.py. 'NAME': os.path.join(BASE_DIR, 'hyperkitty.db'), # Not used with sqlite3: 'USER': '', 'PASSWORD': '', 'HOST': '', 'PORT': '', } } Does the database file named by 'NAME' exist? I would recommend getting your sqlite3 configuration running, then you know that HyperKitty is partly working if the hyperkitty.db file is getting updated as you test Mailman by sending messages, and you can check if it's fully working by using HyperKitty's web pages. Then convert to MySQL for performance. Steve

5 years, 9 months

Re: Finding a user to delete them

by Stephen J. Turnbull

Brian Carpenter writes: > I do think List Admins would want an interface to help "manage" a > user account on behalf of a user then what is currently available > in Postorius. Oh, no question about that whatsoever. I'm quite surprised that this facility isn't present yet. (I rarely make mistakes in mass subscribe and the defaults work fine for my subscribers -- or they make their own changes -- so I can't recall ever encountering this need.) I wonder if in Mailman 3 where user profiles exist and are clearly *not* subject to control by *list* admins in the same way that subscriptions are, and in this day of GDPR etc if maybe we need to restrict admin access to various user properties. This sounds like a rather difficult design problem. > I don't see this functionality built into Mailman 3 nowhere near > the extent that Mailman 2 has. Web interfaces are supposed :-( to be easy enough for Great-Grandma to use, so I imagine the designers didn't think much admin intervention would be needed. > My approach with Affinity is definite leaning very heavy on the > needs of list admins atm. Perhaps that's a good division of responsibility between Postorius and Affinity dev processes. Something to think about. Steve

5 years, 5 months

Re: Upgrading mailman 3 venv installation

by Mark Sapiro

On 9/29/21 10:52 AM, Morris Jones wrote: > > In my virtual environment, I ran `pip list -o` and got a significant > list. I noticed that all of the mailman packages seemed to be "Type > sdist" and the framework packages "Type wheel". (Dunno what "Type" means > in this context.) Type is the package type. sdist is a source distribution. wheel is a form of binary distribution. Older forms are egg and bdist. > So I tried `pip list -o | grep sdist` and got a smaller list: > > (venv) mailman@mail:~$ pip list -o | grep sdist > atpublic 2.1.1 2.3 sdist > django-allauth 0.43.0 0.45.0 sdist > django-mailman3 1.3.4 1.3.7 sdist > flufl.i18n 3.1.3 3.2 sdist > flufl.lock 5.0.3 6.0 sdist > HyperKitty 1.3.3 1.3.4 sdist > lazr.config 2.2.2 2.2.3 sdist > mailman 3.3.2 3.3.5 sdist > mailmanclient 3.3.1 3.3.3 sdist > mysqlclient 2.0.1 2.0.3 sdist > postorius 1.3.3 1.3.6 sdist > > Is this a reasonable list of the packages that I should update? Several of those are dependencies. The packages you should upgrade are mailman, postorius, hyperkitty, django-mailman3 and mailmanclient. Dependencies will be upgraded as required. If a dependency is not upgraded, the older version should work. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

Re: sqlite3 Database "read only" error on mailman_sync job

by Ugnius S

Thank You, Abhilash, to helping. I have checked the processes, but also I have read, that sqlite3 can run in multi writing mode. May mailman processes are next: 6644 ? S 0:12 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini 6645 ? S 0:00 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 6653 ? Sl 636:28 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 6656 ? Sl 0:27 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini 6643 ? S 0:00 /usr/bin/python3 /usr/bin/master -C /opt/home/mailman.cfg 659 ? S 0:46 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=in:0:1 6660 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=nntp:0:1 6661 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=digest:0:1 6662 ? S 0:48 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=pipeline:0:1 6663 ? S 0:44 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=archive:0:1 6664 ? S 0:41 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=command:0:1 6665 ? S 0:01 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=retry:0:1 6666 ? S 0:45 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=virgin:0:1 6667 ? Sl 0:16 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=lmtp:0:1 6668 ? Sl 1:30 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=rest:0:1 6669 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=bounces:0:1 6670 ? S 0:49 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=out:0:1 Looks like there are no double. Nothing more is running. 2019-09-05, kt, 03:16 Abhilash Raj <maxking(a)asynchronous.in> rašė: > On Wed, Sep 4, 2019, at 2:05 PM, Ugnius S wrote: > > > I have installed using documentation. My linux distribution version has no > full package available. I have installed step by step: > $ sudo pip3 install mailman > $ sudo pip3 install postorius > > $ sudo pip3 install hyperkitty > > $ sudo pip3 install mailman-hyperkitty > > And of course all mandatory components... Everything without errors, I > can drop db files and I can download mailman-suite again and start from > empty page again. But it will not guarantee that DB will not become READ > ONLY again. Here should be logic. No developing support here? > > > Could you be running two separate processes such that the database is > locked by one and so other finds it as READ Only? When you find a read only > database, can you check if it is open in some other process? > > > > > 2019-09-03, an, 19:36 Abhilash Raj <maxking(a)asynchronous.in> rašė: > > > > On Sun, Sep 1, 2019, at 3:22 AM,ugniusviln(a)gmail.com wrote: > > Hi. All the project installation is under the same user / path and > > it works. Archiving working as well, (just one remark: no matter what > > to set in postorius, hyperkitty shows list as public) > > I have found work around - it is possible to change list as private in > > "admin" page. > > I started to get issues with runjobs after I have created couple of > > new lists with "no archive" option. > > How did you install all these components. It seems there the installation > is broken in weird ways. > > > > > If as owner user from project home I run: > > > > django-admin mailman_sync > > > > Traceback (most recent call last): > > File > > > "/home/user/.local/lib/python3.5/site-packages/django/db/backends/utils.py", > > line 84, in _execute > > return self.cursor.execute(sql, params) > > File > > > "/home/user/.local/lib/python3.5/site-packages/django/db/backends/sqlite3/base.py", > > line 383, in execute > > return Database.Cursor.execute(self, query, params) > > sqlite3.OperationalError: attempt to write a readonly database > > > > "django-admin runjob sync_mailman " - makes read only errors as well. > > "django-admin runjob new_lists_from_mailman" > > django.db.utils.OperationalError: attempt to write a readonly database > > END TRACEBACK > > > > I did not find information how to fix this. It was worked without errors > > before. > > I noticed, that if I stop mailman, "django-admin mailman_sync" starts > > to work. > > If I start "mailman start", then "django-admin mailman_sync" failing > > again. > > I did not check other jobs, but I think what is related to database, > > will get errors. > > Seems mailman locking the database. It is not a file permissions issue. > > Mailman db location is: /project_directory/var/data/mailman.db > > > > if to rename /project_directory/var/data/mailman.db to something, > > mailman creates database file size 0, django-admin runjobs start > > working, but of course postorius stops working. I did it for testing. > > I have returned this database file back, postorius started to work > > again, but django-admin runjobs does not work, error: "database read > > only". > > Please help me how to fix this issue. > > _______________________________________________ > > Mailman-users mailing list -- mailman-users(a)mailman3.org > > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > > -- > thanks, > Abhilash Raj (maxking) > > > -- > thanks, > Abhilash Raj (maxking) > > >

5 years, 11 months

Mailman-users search results for query "Postorius"