My Server is unable to connect to Mailman REST API few times
Hi Team,
I am currently running Mailman 3 with version 3.3.1 and inbuilt postfix version 2.10.1-6 on RHEL 7.5 with PostgreSQL 11.7 version with default values in production environment from the past 4 months almost. As of now, we are having around 1327 lists created on this.
When I am trying to do some operations like creating thelists, deleting the lists or accessing the lists through the GUI, I am getting the below error. If I am trying to do the operations through API or through mailman shell, still I am not able to connect to the API.
Something went wrong
Mailman REST API not available. Please start Mailman core.
But my mailman core was working fine in the background. Atthe same time I was able to do other operations on a few other lists.
By the time I am getting the above error, the mailman.logrecorded the below messages.
*[2020-09-16 12:49:08 +0530] [2600] [CRITICAL] WORKER TIMEOUT (pid:20234)*
*[2020-09-16 12:49:08 +0530] [20234] [INFO] Worker exiting (pid: 20234)*
*[2020-09-16 12:49:09 +0530] [21042] [INFO] Booting worker with pid: 21042*
My mailman.cfg configuration is as below. The timeout valueis the default value. I did not set any customized value.
*(venv3) [root@lsmgr mailman]# grep -v ^# /var/lib/mailman/mailman/var/etc/mailman.cfg*
*[archiver.hyperkitty]*
*class: mailman_hyperkitty.Archiver*
*enable: yes*
*configuration: /var/lib/mailman/mailman-hyperkitty/mailman-hyperkitty.cfg*
*[mta]*
*incoming: mailman.mta.postfix.LMTP*
*outgoing: mailman.mta.deliver.deliver*
*lmtp_host: 0.0.0.0*
*lmtp_port: 8024*
*smtp_host: localhost*
*smtp_port: 25*
*[webservice]*
*workers: 10*
*[database]*
*class: mailman.database.postgresql.PostgreSQLDatabase*
*url: postgres://<postgresdbuser>:<postgresdbpassword>@127.0.0.1/mailman <http://127.0.0.1/mailman>*
Then as per the suggestion I got earlier I configured the[webservice] section in the above file as below.
*[webservice]*
*configuration: /var/lib/mailman/mailman/var/etc/gunicorn.cfg*
/var/lib/mailman/mailman/var/etc/gunicorn.cfg*[root@lsmgr logs]# cat
*[gunicorn]*
*workers = 10*
*timeout = 90 *
After the above configuration, I found many errors like below in mailman.log file:
*sqlalchemy.exc.NoSuchColumnError: "Could not locate column in row for column 'pended.id <http://pended.id>'"*
*sqlalchemy.exc.ResourceClosedError: This result object does not return rows. It has been closed automatically.*
*sqlalchemy.exc.DatabaseError: (psycopg2.DatabaseError) error with status PGRES_TUPLES_OK and no message from the libpq*
The above might be few of the errors. FYI, for the creation of each list, it is taking almost around 15 to 20 minutes. After multiple times of the above error messages, at some time, I am fortunately getting the list created or some other operation getting done.
I found the same scenario when the workers are from default 2to 10. I don't understand where exactly I need to focus to solve the issue.
Please let me know if I have to share any other details foryou to suggest to me.
-- Thanks & Regards, Shashi Kanth.K 9052671936
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
Shashikanth Komandoor writes:
I am currently running Mailman 3 with version 3.3.1 and inbuilt postfix version 2.10.1-6 on RHEL 7.5 with PostgreSQL 11.7 version with default values in production environment from the past 4 months almost. As of now, we are having around 1327 lists created on this.
Aren't you the crew that modified Mailman to interface with SMS or something like that? If so, don't worry, it doesn't invalidate your warranty, but it seems possible that it has something to do with this:
After the above configuration, I found many errors like below in mailman.log file:
*sqlalchemy.exc.NoSuchColumnError: "Could not locate column in row for column 'pended.id <http://pended.id>'"*
*sqlalchemy.exc.ResourceClosedError: This result object does not return rows. It has been closed automatically.*
*sqlalchemy.exc.DatabaseError: (psycopg2.DatabaseError) error with status PGRES_TUPLES_OK and no message from the libpq*
Whether you have that modified Mailman or not, the messages above suggest that there may have been a change in the schema of the database that one side (presumably SQLAlchemy) knows about but have not been propagated to the other (PostgreSQL). Have you perhaps done an upgrade but not run the database migration script?
About the REST API not available error:
Something went wrong
Mailman REST API not available. Please start Mailman core.
But my mailman core was working fine in the background. Atthe same time I was able to do other operations on a few other lists.
By the time I am getting the above error, the mailman.logrecorded the below messages.
*[2020-09-16 12:49:08 +0530] [2600] [CRITICAL] WORKER TIMEOUT (pid:20234)*
*[2020-09-16 12:49:08 +0530] [20234] [INFO] Worker exiting (pid: 20234)*
*[2020-09-16 12:49:09 +0530] [21042] [INFO] Booting worker with pid: 21042*
Something is taking too long, the worker is timing out. That's probably why you get the REST API not available message. Do the sqlalchemy errors correlate with the timeouts?
I suspect the exit and reboot of the worker is normal but I haven't looked at this part of the code.
My mailman.cfg configuration is as below. The timeoutvalue is the default value. I did not set any customized value.
Thanks for sending it; sometimes it speeds up debugging. But in this case you say that other lists are working, so site configuration doesn't seem to be the problem. Is this particular list special in some way? List configuration is different?
The above might be few of the errors. FYI, for the creation of each list, it is taking almost around 15 to 20 minutes. After multiple times of the above error messages, at some time, I am fortunately getting the list created or some other operation getting done.
This is quite strange. I don't see why this would suddenly start working after many minutes.
Does PostgreSQL have any logs with "interesting" (or scary) messages in them?
Maybe somebody else has some ideas, but this is as far as I can go.
Hi Shashikanth,
It appears I may have sent you on a wild goose chase. You have my apologies. There's a very similar report today, so this appears to be a Mailman 3 issue. For now, pleasee see Mark's post for the correct way to increase timeout: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
I am working with Mark to diagnose the underlying problem.
Steve
Stephen J. Turnbull writes:
Shashikanth Komandoor writes:
I am currently running Mailman 3 with version 3.3.1 and inbuilt postfix version 2.10.1-6 on RHEL 7.5 with PostgreSQL 11.7 version with default values in production environment from the past 4 months almost. As of now, we are having around 1327 lists created on this.
Aren't you the crew that modified Mailman to interface with SMS or something like that? If so, don't worry, it doesn't invalidate your warranty, but it seems possible that it has something to do with this:
After the above configuration, I found many errors like below in mailman.log file:
*sqlalchemy.exc.NoSuchColumnError: "Could not locate column in row for column 'pended.id <http://pended.id>'"*
*sqlalchemy.exc.ResourceClosedError: This result object does not return rows. It has been closed automatically.*
*sqlalchemy.exc.DatabaseError: (psycopg2.DatabaseError) error with status PGRES_TUPLES_OK and no message from the libpq*
Whether you have that modified Mailman or not, the messages above suggest that there may have been a change in the schema of the database that one side (presumably SQLAlchemy) knows about but have not been propagated to the other (PostgreSQL). Have you perhaps done an upgrade but not run the database migration script?
About the REST API not available error:
Something went wrong
Mailman REST API not available. Please start Mailman core.
But my mailman core was working fine in the background. Atthe same time I was able to do other operations on a few other lists.
By the time I am getting the above error, the mailman.logrecorded the below messages.
*[2020-09-16 12:49:08 +0530] [2600] [CRITICAL] WORKER TIMEOUT (pid:20234)*
*[2020-09-16 12:49:08 +0530] [20234] [INFO] Worker exiting (pid: 20234)*
*[2020-09-16 12:49:09 +0530] [21042] [INFO] Booting worker with pid: 21042*
Something is taking too long, the worker is timing out. That's probably why you get the REST API not available message. Do the sqlalchemy errors correlate with the timeouts?
I suspect the exit and reboot of the worker is normal but I haven't looked at this part of the code.
My mailman.cfg configuration is as below. The timeoutvalue is the default value. I did not set any customized value.
Thanks for sending it; sometimes it speeds up debugging. But in this case you say that other lists are working, so site configuration doesn't seem to be the problem. Is this particular list special in some way? List configuration is different?
The above might be few of the errors. FYI, for the creation of each list, it is taking almost around 15 to 20 minutes. After multiple times of the above error messages, at some time, I am fortunately getting the list created or some other operation getting done.
This is quite strange. I don't see why this would suddenly start working after many minutes.
Does PostgreSQL have any logs with "interesting" (or scary) messages in them?
Maybe somebody else has some ideas, but this is as far as I can go.
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/
Thank you a lot Stephen for your attempt to help me. In fact I got some info from your response.
Aren't you the crew that modified Mailman to interface with SMS or
something like that? If so, don't worry, it doesn't invalidate your warranty, but it seems possible that it has something to do with this:
Yes. We have taken the source code of mailman and customised the software to send SMS notifications along with the mail notifications when any mail is waiting for the pending approval. But not sure if it is creating a problem.
Whether you have that modified Mailman or not, the messages above
suggest that there may have been a change in the schema of the database that one side (presumably SQLAlchemy) knows about but have not been propagated to the other (PostgreSQL). Have you perhaps done an upgrade but not run the database migration script?
I have not done any upgrade of any component of the mailman.
Something is taking too long, the worker is timing out. That's
probably why you get the REST API not available message. Do the sqlalchemy errors correlate with the timeouts?
I am unable to state if both are correlating with each other.
Thanks for sending it; sometimes it speeds up debugging. But in this
case you say that other lists are working, so site configuration doesn't seem to be the problem. Is this particular list special in some way? List configuration is different?
No. All the lists on the server are similarly configured. May be with different settings of list or list members.
Does PostgreSQL have any logs with "interesting" (or scary) messages in them?
No, I don't find any messages in postgresql logs.
It appears I may have sent you on a wild goose chase. You have my
apologies.
I am very happy you spent your precious time working on my issue.
I am working with Mark to diagnose the underlying problem.
Thank you both for this.
But I am trying to delete a list on an urgent basis. Because of which I am getting the above said errors. I tried to delete through the interface, through curl command and through "mailman shell" but nothing led me to a positive result. Is there any work around to delete the list ?
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Thu, Sep 17, 2020 at 5:22 PM Stephen J. Turnbull < turnbull.stephen.fw@u.tsukuba.ac.jp> wrote:
Hi Shashikanth,
It appears I may have sent you on a wild goose chase. You have my apologies. There's a very similar report today, so this appears to be a Mailman 3 issue. For now, pleasee see Mark's post for the correct way to increase timeout:
https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
I am working with Mark to diagnose the underlying problem.
Steve
Shashikanth Komandoor writes:
I am currently running Mailman 3 with version 3.3.1 andin
built postfix version 2.10.1-6 on RHEL 7.5 with PostgreSQL 11.7 version with default values in production environment from the past 4 months almost. As of now, we are having around 1327 lists created on this.
Aren't you the crew that modified Mailman to interface with SMS or something like that? If so, don't worry, it doesn't invalidate your warranty, but it seems possible that it has something to do with this:
After the above configuration, I found many errors like below in mailman.log file:
*sqlalchemy.exc.NoSuchColumnError: "Could not locate column in row for column 'pended.id <http://pended.id>'"*
*sqlalchemy.exc.ResourceClosedError: This result object does not return rows. It has been closed automatically.*
*sqlalchemy.exc.DatabaseError: (psycopg2.DatabaseError) error with status PGRES_TUPLES_OK and no message from the libpq*
Whether you have that modified Mailman or not, the messages above suggest that there may have been a change in the schema of the database that one side (presumably SQLAlchemy) knows about but have not been propagated to the other (PostgreSQL). Have you perhaps done an upgrade but not run the database migration script?
About the REST API not available error:
Something went wrong
Mailman REST API not available. Please start Mailman core.
But my mailman core was working fine in thebackground. At the same time I was able to do other operations on a few other lists.
By the time I am getting the above error, themailman.log recorded the below messages.
*[2020-09-16 12:49:08 +0530] [2600] [CRITICAL] WORKER TIMEOUT (pid:20234)*
*[2020-09-16 12:49:08 +0530] [20234] [INFO] Worker exiting (pid: 20234)*
*[2020-09-16 12:49:09 +0530] [21042] [INFO] Booting worker with pid: 21042*
Something is taking too long, the worker is timing out. That's probably why you get the REST API not available message. Do the sqlalchemy errors correlate with the timeouts?
I suspect the exit and reboot of the worker is normal but I haven't looked at this part of the code.
My mailman.cfg configuration is as below. The timeoutvalue is the default value. I did not set any customized value.
Thanks for sending it; sometimes it speeds up debugging. But in this case you say that other lists are working, so site configuration doesn't seem to be the problem. Is this particular list special in some way? List configuration is different?
The above might be few of the errors. FYI, for the creation of each
it is taking almost around 15 to 20 minutes. After multiple times of
Stephen J. Turnbull writes: list, the
above error messages, at some time, I am fortunately getting the list created or some other operation getting done.
This is quite strange. I don't see why this would suddenly start working after many minutes.
Does PostgreSQL have any logs with "interesting" (or scary) messages in them?
Maybe somebody else has some ideas, but this is as far as I can go.
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 & Regards, Shashi Kanth.K 9052671936
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On 9/19/20 4:32 AM, Shashikanth Komandoor wrote:
But I am trying to delete a list on an urgent basis. Because of which I am getting the above said errors. I tried to delete through the interface, through curl command and through "mailman shell" but nothing led me to a positive result. Is there any work around to delete the list ?
What have you tried in Mailman shell? This should do it.
$ mailman shell -l list.example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list.example.com mailing list
getUtility(IListManager).delete(m) commit()
So should just
$ mailman remove list.example.com
What happens if you do those?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Thank you Mark a lot.
It worked awesome. You don't know how much you helped me.
Thank you once again.
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Sat, Sep 19, 2020 at 8:56 PM Mark Sapiro <mark@msapiro.net> wrote:
On 9/19/20 4:32 AM, Shashikanth Komandoor wrote:
But I am trying to delete a list on an urgent basis. Because of which I
am
getting the above said errors. I tried to delete through the interface, through curl command and through "mailman shell" but nothing led me to a positive result. Is there any work around to delete the list ?
What have you tried in Mailman shell? This should do it.
$ mailman shell -l list.example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list.example.com mailing list
getUtility(IListManager).delete(m) commit()
So should just
$ mailman remove list.example.com
What happens if you do those?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
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 & Regards, Shashi Kanth.K 9052671936
Dear Mark,
As I already said, your suggestion worked well on one list.
But when I tried to implement the same trick on another list, Ifound the below error messages in the mailman.log.
Sep 23 18:31:31 2020 (22951) Uncaught runner exception: [Errno*Sep 23 18:31:31 2020 (22951) Traceback (most recent call last):*
File "/usr/lib64/python3.6/mailbox.py", line 581, in __init__*
f = open(self._path, 'rb+')* *FileNotFoundError: [Errno 2] No such file or directory: '/var/lib/mailman/mailman/var/lists/press.dpr-pb.lsmgr.nic.in/digest.mmdf <http://press.dpr-pb.lsmgr.nic.in/digest.mmdf>'* *During handling of the above exception, another exception occurred:* *Traceback (most recent call last):*
File "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 173, in _one_iteration*
self._process_one_file(msg, msgdata)*
File "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 266, in _process_one_file*
keepqueued = self._dispose(mlist, msg, msgdata)*
File "/var/lib/mailman/mailman/src/mailman/runners/pipeline.py", line 37, in _dispose*
process(mlist, msg, msgdata, pipeline)*
File "/var/lib/mailman/mailman/src/mailman/core/pipelines.py", line 50, in process*
handler.process(mlist, msg, msgdata)*
File "/var/lib/mailman/mailman/src/mailman/handlers/to_digest.py", line 47, in process*
with Mailbox(mailbox_path, create=True) as mbox:*
File "/usr/lib64/python3.6/mailbox.py", line 893, in __init__*
_mboxMMDF.__init__(self, path, factory, create)*
File "/usr/lib64/python3.6/mailbox.py", line 585, in __init__*
f = open(self._path, 'wb+')**FileNotFoundError: [Errno 2] No such file or directory: '/var/lib/mailman/mailman/var/lists/press.dpr-pb.lsmgr.nic.in/digest.mmdf <http://press.dpr-pb.lsmgr.nic.in/digest.mmdf>'*
I ran in both the ways you suggested i.e. through "mailman shell" and "mailman remove". But no luck.
Could you please suggest me at this point ?<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Tue, Sep 22, 2020 at 10:29 PM Shashikanth Komandoor < shashikanth.komandoor@gmail.com> wrote:
Thank you Mark a lot.
It worked awesome. You don't know how much you helped me.
Thank you once again.
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#m_8502129290396208734_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Sat, Sep 19, 2020 at 8:56 PM Mark Sapiro <mark@msapiro.net> wrote:
On 9/19/20 4:32 AM, Shashikanth Komandoor wrote:
But I am trying to delete a list on an urgent basis. Because of which I
am
getting the above said errors. I tried to delete through the interface, through curl command and through "mailman shell" but nothing led me to a positive result. Is there any work around to delete the list ?
What have you tried in Mailman shell? This should do it.
$ mailman shell -l list.example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list.example.com mailing list
getUtility(IListManager).delete(m) commit()
So should just
$ mailman remove list.example.com
What happens if you do those?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
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 & Regards, Shashi Kanth.K 9052671936
-- Thanks & Regards, Shashi Kanth.K 9052671936
On 9/23/20 6:32 AM, Shashikanth Komandoor wrote:
Dear Mark,
As I already said, your suggestion worked well on one list. But when I tried to implement the same trick on another list, Ifound the below error messages in the mailman.log.
Sep 23 18:31:31 2020 (22951) Uncaught runner exception: [Errno*Sep 23 18:31:31 2020 (22951) Traceback (most recent call last):*
File "/usr/lib64/python3.6/mailbox.py", line 581, in __init__*
f = open(self._path, 'rb+')* *FileNotFoundError: [Errno 2] No such file or directory: '/var/lib/mailman/mailman/var/lists/press.dpr-pb.lsmgr.nic.in/digest.mmdf <http://press.dpr-pb.lsmgr.nic.in/digest.mmdf>'* *During handling of the above exception, another exception occurred:* *Traceback (most recent call last):*
File "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 173, in _one_iteration*
self._process_one_file(msg, msgdata)*
File "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 266, in _process_one_file*
keepqueued = self._dispose(mlist, msg, msgdata)*
File "/var/lib/mailman/mailman/src/mailman/runners/pipeline.py", line 37, in _dispose*
process(mlist, msg, msgdata, pipeline)*
File "/var/lib/mailman/mailman/src/mailman/core/pipelines.py", line 50, in process*
handler.process(mlist, msg, msgdata)*
File "/var/lib/mailman/mailman/src/mailman/handlers/to_digest.py", line 47, in process*
with Mailbox(mailbox_path, create=True) as mbox:*
File "/usr/lib64/python3.6/mailbox.py", line 893, in __init__*
_mboxMMDF.__init__(self, path, factory, create)*
File "/usr/lib64/python3.6/mailbox.py", line 585, in __init__*
f = open(self._path, 'wb+')**FileNotFoundError: [Errno 2] No such file or directory: '/var/lib/mailman/mailman/var/lists/press.dpr-pb.lsmgr.nic.in/digest.mmdf <http://press.dpr-pb.lsmgr.nic.in/digest.mmdf>'*
I ran in both the ways you suggested i.e. through "mailman shell" and "mailman remove". But no luck.
Could you please suggest me at this point ?
Mailman is trying to add a message to the digest of the press.dpr-pb.lsmgr.nic.in list, but the /var/lib/mailman/mailman/var/lists/press.dpr-pb.lsmgr.nic.in/ directory doesn't exist, presumably because the list has been removed.
The question is why is Mailman trying to write to this list's digest.mmdf? Did the above result from unshunting something from before the list was removed?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Thank you Mark for your response.
I am not sure. How can I check that if it is from unshunting ?
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Wed, Sep 23, 2020 at 10:33 PM Mark Sapiro <mark@msapiro.net> wrote:
Dear Mark,
As I already said, your suggestion worked well on one list. But when I tried to implement the same trick on another list, Ifound the below error messages in the mailman.log.
Sep 23 18:31:31 2020 (22951) Uncaught runner exception:<http://press.dpr-pb.lsmgr.nic.in/digest.mmdf>'*
*Sep 23 18:31:31 2020 (22951) Traceback (most recent call last):*
- File "/usr/lib64/python3.6/mailbox.py", line 581, in __init__*
- f = open(self._path, 'rb+')* *FileNotFoundError: [Errno 2] No such file or directory: '/var/lib/mailman/mailman/var/lists/
<http://press.dpr-pb.lsmgr.nic.in/digest.mmdf>'* *During handling of the above exception, another exception occurred:* *Traceback (most recent call last):*
- File "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 173, in _one_iteration*
- self._process_one_file(msg, msgdata)*
- File "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 266, in _process_one_file*
- keepqueued = self._dispose(mlist, msg, msgdata)*
- File "/var/lib/mailman/mailman/src/mailman/runners/pipeline.py", line 37, in _dispose*
- process(mlist, msg, msgdata, pipeline)*
- File "/var/lib/mailman/mailman/src/mailman/core/pipelines.py", line 50, in process*
- handler.process(mlist, msg, msgdata)*
- File "/var/lib/mailman/mailman/src/mailman/handlers/to_digest.py",
47, in process*
- with Mailbox(mailbox_path, create=True) as mbox:*
- File "/usr/lib64/python3.6/mailbox.py", line 893, in __init__*
- _mboxMMDF.__init__(self, path, factory, create)*
- File "/usr/lib64/python3.6/mailbox.py", line 585, in __init__*
- f = open(self._path, 'wb+')**FileNotFoundError: [Errno 2] No such file or directory: '/var/lib/mailman/mailman/var/lists/
On 9/23/20 6:32 AM, Shashikanth Komandoor wrote: press.dpr-pb.lsmgr.nic.in/digest.mmdf press.dpr-pb.lsmgr.nic.in/digest.mmdf line press.dpr-pb.lsmgr.nic.in/digest.mmdf
<http://press.dpr-pb.lsmgr.nic.in/digest.mmdf>'*
I ran in both the ways you suggested i.e. through "mailmanshell" and "mailman remove". But no luck.
Could you please suggest me at this point ?Mailman is trying to add a message to the digest of the press.dpr-pb.lsmgr.nic.in list, but the /var/lib/mailman/mailman/var/lists/press.dpr-pb.lsmgr.nic.in/ directory doesn't exist, presumably because the list has been removed.
The question is why is Mailman trying to write to this list's digest.mmdf? Did the above result from unshunting something from before the list was removed?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
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 & Regards, Shashi Kanth.K 9052671936
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On 9/24/20 4:34 AM, Shashikanth Komandoor wrote:
Thank you Mark for your response.
I am not sure. How can I check that if it is from unshunting ?
It is from unshunting if you or someone else manually ran mailman unshunt.
I was trying to understand how Mailman would be trying to add a message for the digest to a non-existent list. One way I think is if a message to be added was shunted from the digest queue and then unshunted after the list was deleted. This however seems unlikely.
Another possibility is mailman was stopped with an entry for the list in the digest queue and started again after deleting the list. This seems more likely.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
Mark Sapiro -
Shashikanth Komandoor -
Stephen J. Turnbull