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 say me can not find.
>
> <config>
> 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/lists.error.log;
>
> location = / {
> rewrite ^ /listinfo permanent;
> }
>
> location / {
> fastcgi_split_path_info ^(/[^/]*)(.*)$;
> fastcgi_pass unix:/run/lists.sock;
> include /etc/nginx/configuration/fastcgi.conf;
> fastcgi_param PATH_INFO $fastcgi_path_info;
> fastcgi_param PATH_TRANSLATED $document_root$fastcgi_path_info;
> }
>
> location /icons {
> alias /usr/lib64/mailman/icons;
> }
>
> location /archives {
> alias /var/lib64/mailman/archives/public;
> autoindex on;
> }
> }
> </config>
>
> <log>
> 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: lists.local,
> request: "GET /listinfo HTTP/1.1", upstream:
> "fastcgi://unix:/run/lists.sock:", host: "lists.local"
>
> <socket>
> ks3374456 nginx # ls -l /run | grep lists
> srwxr-xr-x 1 nginx nginx 0 26. Mär 13:01 lists.sock-1
>
>
> Has someone idea what goes wrong?
>
> Thank You & Nice Day
> Silvio
>
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx