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
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
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/
