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/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;
}
}
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"
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
On March 26, 2015 1:15:44 PM WET, Silvio S. [email protected]
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
access_log /var/log/nginx/lists.access.log;
fastcgi_param PATH_INFO $fastcgi_path_info;
}
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?
Whats the user nginx is set run use on nginx. conf?
Thank You & Nice Day
Silvio
nginx mailing list
[email protected]
nginx Info Page
–
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Yes in nginx config is nginx the user.
Thank You & Nice Day
2015-03-26 14:23 GMT+01:00 Miguel C. [email protected]:
On Thu, Mar 26, 2015 at 02:15:44PM +0100, Silvio S. 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: lists.local, request: “GET /listinfo HTTP/1.1”,
upstream: “fastcgi://unix:/run/lists.sock:”, host: “lists.local”
When you request /listinfo, what file on your filesystem do you want
your fastcgi server to process? (From the perspective of the fastcgi
server, in case any kind of chrooting is involved.)
What fastcgi_param does your fastcgi server (fcgiwrap) use to determine
the file to process? (It is usually SCRIPT_FILENAME; but some fastcgi
servers use something different.)
f
Francis D. [email protected]
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.
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 Thursday, March 26, 2015 02:15:44 PM Silvio S. wrote:
server_name lists;
fastcgi_split_path_info ^(/[^/])(.)$;
location /archives {
upstream: “fastcgi://unix:/run/lists.sock:”, host: “lists.local”
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
–
Best regards,
Styopa S…