On Mon, Nov 10, 2014 at 02:01:13AM -0500, FireFalcon wrote:
Hi there,
> When I run the following command:
>
> fastcgi-mono-server4 --appconfigdir /etc/webapps /socket=tcp:127.0.0.1:9002
>
> nothing happens, Terminal doesn't show any response. What can I do???
What response do you expect to see
On Fri, Nov 07, 2014 at 09:17:18PM -0500, cachito wrote:
Hi there,
> Yesterday after I replaced the domain in the various configuration files,
> nginx started sending every request to the PHP processor. The location / is
> pretty standard:
> location / {
> try_files cache_path$uri $uri $uri/ /ind
I suppose it has to do with the fact that error_page masks errors coming
from the backend, impersonating them with nginx.
If nginx shows a 404 when the backend actually generated it, and you digged
improperly into the logs, you might be fooled by that and get lost when
trying to trace the error.
I
Thank you for your reply Maxim, that's exactly what's happening. It's
closing the socket for all the other requests I try, but not that one. I
guess the problem is farther down the line somewhere.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,254687,254743#msg-254743
___
Hello!
On Mon, Nov 10, 2014 at 10:16:16AM -0500, zhijianpeng wrote:
> Yes,we found that it was caused by a 3rd party module named
> "nginx_upstream_check_module".
>
> I want to know the use of connections in cache manager process. And if
> there are no free connections of cache manager process
Yes,we found that it was caused by a 3rd party module named
"nginx_upstream_check_module".
I want to know the use of connections in cache manager process. And if
there are no free connections of cache manager process,any thing bad would
happend?
Posted at Nginx Forum:
http://forum.nginx.org/re
Hello!
On Fri, Nov 07, 2014 at 05:52:31PM -0500, jpherbst wrote:
> Hello,
>
> I have nginx 1.6.1 setup in front of uwsgi 2.0.7 using uwsgi_pass, which has
> been working very well for me except for one request. When I make the
> failing request uwsgi processes the request and returns the respon
Hello!
On Fri, Nov 07, 2014 at 02:05:38PM -0500, zappa wrote:
> Btw, why is it you don't recomment using the error_page method?
It's an error-prone approach.
--
Maxim Dounin
http://nginx.org/
___
nginx mailing list
nginx@nginx.org
http://mailman.ngi
It makes no difference as this combo;
root '/path/';
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
open_basedir = '/path/'
doc_root = '/path/'
Next to jailing, this boxes everything in.
With location /.../ '.php' you fine-tune where scripts live which may be
run.
I'd le
