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.
If as owner user from project home I run:
Traceback (most recent call last):
line 84, in _execute
return self.cursor.execute(sql, params)
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
I did not find information how to fix this. It was worked without errors
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.