Hi,
Your config refers to the file "list.sock" but your error log complains of
"listS.sock". Looks like your configuration has changed since Nginx read it.
Stop Nginx service and ensure there's no other Nginx process running (e.g.
pgrep nginx). Then start a clean instance of the service.
On T
There seems to be a naming issue for the socket.
nginx is configured to use /run/lists.sock yet your ls shows lists.sock-1
Steve.
On 26/03/2015 13:15, Silvio Siefke wrote:
> Hello,
>
> i try to run mailman on nginx over fcgiwrap. The sock is present on
> system and has correct rights, but
> log
That surely helps. So as of now the only way to resolve the issue is going
back to u12 version of libssl?
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,256373,257705#msg-257705
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/
Hi, FASTCGI is 'built in' NGINX. Can someone from the NGINX organization
confirm that there is no plan to retire the FASTCGI support in NGINX? Thank
you!
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,257704,257704#msg-257704
___
nginx mailin
Hello Maxim,
Thanks for having taken the time of explaining it all!
It seems HTTP/1.0 interoperability is seriously flawed...
Anyhow, now I understand nginx' default behavior, which makes sense.
Our needs are very specific, since nginx is hidden behind an internal
cache, but the general case, re
On Thu, Mar 26, 2015 at 02:15:44PM +0100, Silvio Siefke wrote:
Hi there,
> i try to run mailman on nginx over fcgiwrap.
> 2015/03/26 14:13:17 [crit] 13209#0: *21 connect() to unix:/run/list.sock
> failed (2: No such file or directory) while connecting to upstream, client:
> 87.161.141.92, server
Hello,
I need to log transaction time, so I simply add $request_time to my
log_format directive. Anyway the value in the access.log in always 0.000
even if the server is under heavy load (siege show transaction time up to 30
sec). This is a just a basic server with no more than one page for testin
Yes in nginx config is nginx the user.
Thank You & Nice Day
2015-03-26 14:23 GMT+01:00 Miguel Clara :
>
>
> On March 26, 2015 1:15:44 PM WET, Silvio Siefke
> wrote:
> >Hello,
> >
> >i try to run mailman on nginx over fcgiwrap.
>
> If you can I would suggest uWsgi module instead of fcgiwrap.
>
>
On March 26, 2015 1:15:44 PM WET, Silvio Siefke wrote:
>Hello,
>
>i try to run mailman on nginx over fcgiwrap.
If you can I would suggest uWsgi module instead of fcgiwrap.
The sock is present on
>system
>and has correct rights, but
>log say me can not find.
>
>server {
>listen 80;
>listen [::
Hello,
i try to run mailman on nginx over fcgiwrap. The sock is present on system
and has correct rights, but
log say me can not find.
server {
listen 80;
listen [::]:80;
server_name lists;
root /usr/lib64/mailman/cgi-bin;
access_log /var/log/nginx/lists.access.log;
error_log /var/log/nginx/
Hello,
I am using Varnish as a cache and reverse-proxy to distribute requests
between different backend workers. The workers expect some parameters,
that can be passed either through GET or POST.
The way Varnish works is by caching and distributing requests based on
the URL. So all GET requests a
11 matches
Mail list logo