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@asynchronous.in> rašė:
On Sun, Sep 1, 2019, at 3:22 AM,ugniusviln@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@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)
-- thanks, Abhilash Raj (maxking)