Re: [ERROR] Error handling request List archivers
Thank you Mark for guiding me to the benefit of putting the list and so I have added the list.
Along with the [archiver.hyperkitty], [mta] and [database], few lines of my mailman.cfg look like below:
*[webservice]workers = 4timeout = 900*
The above block of webservice is added yesterday for testing or trail as I am getting the above issue.
And there is no line that is calling *gunicorn* in my mailman.cfg.
Apart from that I tried to locate and see the content of the gunicorn.cfg file as below :
*(venv3) [root@lsmgr mailman]# cat /var/lib/mailman/mailman/src/mailman/config/gunicorn.cfg[gunicorn]# All the options that can be put here are available at# http://docs.gunicorn.org/en/stable/settings.html#settings <http://docs.gunicorn.org/en/stable/settings.html#settings># No of seconds to wait before killing the worker processes.graceful_timeout = 30*
Please confirm the time I have to change is *graceful_timeout *in *gunicorn.cfg* and if I have changed how do I restart the *gunicorn*. I have never used or never known about this *gunicorn* but still running the service in production.
Please help me and also suggest if I could provide you any more data from giving resolution.
<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_5710631741815235215_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Thu, Jul 23, 2020 at 3:47 AM Mark Sapiro <mark@msapiro.net> wrote:
On 7/22/20 9:13 AM, Shashikanth Komandoor wrote:
Never mind please I am sending to you only instead of group as I am sending you the production content along with the mail.
I don't see anything there that can't be posted to the mailman-users@mailman3.org list. If your concern is revealing the support-tnvc.lsmgr.nic.in list id, just replace it with <list-id> or list.example.com or similar.
Messages sent to me personally rather than the list suffer many problems. They are my absolute last priority, and I am only one person, the collective knowledge of the list is greater. Also, at times I am off line for several days or longer.
Finally, there is no opportunity for other members of the community to benefit from an off-list exchange.
When I am trying to browse one of my lists, I am getting "[ERROR]Error handling request /3.1/lists/support-tnvc.lsmgr.nic.in/archivers <http://support-tnvc.lsmgr.nic.in/archivers>" in the mailman.log and the full error message is in attachment.
Try increasing your gunicorn worker timeout from the default 30 seconds. I.e., add
timeout = 90
to your gunicorn.cfg and restart gunicorn.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
-- 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 7/23/20 12:39 AM, Shashikanth Komandoor wrote:
Thank you Mark for guiding me to the benefit of putting the list and so I have added the list.
Along with the [archiver.hyperkitty], [mta] and [database], few lines of my mailman.cfg look like below:
[webservice] workers = 4 timeout = 900
The above block of webservice is added yesterday for testing or trail as I am getting the above issue.
And there is no line that is calling *gunicorn* in my mailman.cfg.
As I tried to explain to you in an off-list reply:
You can't configure Mailman's REST gunicorn workers directly in the [webservice] section of mailman.cfg. The only thing you can configure there is:
configuration: /path/to/gunicorn.cfg
That file, which is separate from your web server gunicorn.cfg, is where you put things like
[gunicorn] timeout = 900
It also will not work to put a gunicorn section in mailman.cfg. It must be in a separate file pointed to by webservice.configuration.
Increasing the number of workers won't help this issue.
Apart from that I tried to locate and see the content of the gunicorn.cfg file as below :
*(venv3) [root@lsmgr mailman]# cat /var/lib/mailman/mailman/src/mailman/config/gunicorn.cfg [gunicorn] # All the options that can be put here are available at # http://docs.gunicorn.org/en/stable/settings.html#settings
# No of seconds to wait before killing the worker processes. graceful_timeout = 30
Please confirm the time I have to change is *graceful_timeout *in *gunicorn.cfg* and if I have changed how do I restart the *gunicorn*. I have never used or never known about this *gunicorn* but still running the service in production.
First, the file you reference above is the default gunicorn configuration for the REST server. You don't want to edit this file because your changes will be overridden in an upgrade.
You want to create your own gunicorn.cfg file and point to it by adding
configuration: /path/to/your/gunicorn.cfg
to the webservice section in your mailman.cfg. Your gonicorn.cfg does not need to contain the
graceful_timeout = 30
setting as that is a gonicorn default, and that is not what you need to increase. What you need is
[gunicorn] timeout = 900
(actually 900 seconds is probably way overkill. 90 seconds would probably be enough.)
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Mark Sapiro -
Shashikanth Komandoor