Re: Mailman REST API not available. Please start Mailman Core.
Thank you Mark for your response.
I understood that gunicorn is a front end that is used like web server like nginx.
But I don't think I am using it instead I am using the httpd to redirect requests to postorius.
And I am starting the mailman-suite with the command "python manage.py runserver 0.0.0.0:8000 --insecure &". Hope this does not use gunicorn (which of course I don't know what it is until now).
Please correct me if any point I am mentioning is wrong.
So, in this case, do you think configuring gunicorn as below would work:
*calling gunicorn.cfg in mailman.cfg as below *
*[webservice]* *configuration: /var/lib/mailman/mailman/src/mailman/config/gunicorn.cfg*
*and content of gunicorn.cfg 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.*
*workers = 4graceful_timeout = 90*
Also what is the difference between timeout and graceful_timeout ?
Please help me if I can increase the management better. Any guide is also helpful for me.
<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, Jul 23, 2020 at 4:10 AM Mark Sapiro <mark@msapiro.net> wrote:
On 7/22/20 9:21 AM, Shashikanth Komandoor wrote:
Hi Mark,
Never mind please I am sending to you only instead of group as I am
sending you the production content along with the mail.
See my other reply.
I have configured the workers count as 4 and timeout as 900 in
mailman.cfg under [webservice]. This is FYI.
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.
-- 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
Shashikanth Komandoor writes:
I understood that gunicorn is a front end that is used like web server like nginx.
But I don't think I am using it instead I am using the httpd to redirect requests to postorius.
You can't run recent Mailman 3 core without gunicorn, because gunicorn is the front-end for the REST API. This is completely separate from the front-ends for Postorius and HyperKitty. For the rest, I don't know offhand, and need to go to bed. Sorry I can't help with the details.
Steve
On 7/23/20 12:38 AM, Shashikanth Komandoor wrote:
Thank you Mark for your response.
I understood that gunicorn is a front end that is used like web server like nginx.
But I don't think I am using it instead I am using the httpd to redirect requests to postorius.
Steve has addressed this.
So, in this case, do you think configuring gunicorn as below would work:
You do need to configure gunicorn timeout to solve your issue.
*calling gunicorn.cfg in mailman.cfg as below *
*[webservice]* *configuration: /var/lib/mailman/mailman/src/mailman/config/gunicorn.cfg*
Do NOT do this. Make your own gunicorn.cfg outside of /var/lib/mailman/mailman/src/mailman/ and point to that. Otherwise any upgrade will reverse your changes.
*and content of gunicorn.cfg 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.
workers = 4 graceful_timeout = 90
Also what is the difference between timeout and graceful_timeout ?
graceful_timeout is not what you want. It addresses something different. As it says in the comment, all the gunicorn settings are described at <http://docs.gunicorn.org/en/stable/settings.html#settings>. timeout and graceful_timeout are near the bottom of that page at <https://docs.gunicorn.org/en/stable/settings.html#timeout> and <https://docs.gunicorn.org/en/stable/settings.html#graceful-timeout>.
-- 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