On Thu, Jul 28, 2016 at 3:52 PM, Francis Daly wrote:
> On Thu, Jul 28, 2016 at 03:01:17PM -0400, Larry Martell wrote:
>
> Hi there,
>
>> netstat shows that nginx is listening on port 80:
>>
>> tcp0 0 0.0.0.0:80 0.0.0.0:*
>> LISTEN 9256/nginx: master
>>
>> But I canno
Thanks Reinis.
The system is ARM-based server development platform. The chip is
essentially a Pass 1 prototype (with known limitations) - not a production
part
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,268609,268623#msg-268623
___
ngi
Thanks Maxim.
Setting either 'accept_mutex pff;' or reuseport on the listen directive
doesn't seem to change the general trend much
(apologies for formatting below but can't seem to find a way to paste data
elegantly in this forum)
In data below the Columns are as follows
"Wrk_threads" "Conne
But I cannot connect from my browser (I get connection timeout):
Is there a firewall on the server (if yes - is the port 80 open?).
rr
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On Thu, Jul 28, 2016 at 03:01:17PM -0400, Larry Martell wrote:
Hi there,
> netstat shows that nginx is listening on port 80:
>
> tcp0 0 0.0.0.0:80 0.0.0.0:*
> LISTEN 9256/nginx: master
>
> But I cannot connect from my browser (I get connection timeout):
> The err
On Thursday, July 28, 2016, Pratyush Kumar wrote:
> Can you please share the address which you are using in browser.
>
> According to the config which you shared, you will get a response only if
> you use localhost as URL in browser
>
I am connecting from the outside to the public IP of the mach
Can you please share the address which you are using in browser.
According to the config which you shared, you will get a response only if you use localhost as URL in browser
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo
Trying to set up nginx and uwsgi for django. Following the directions here:
https://www.digitalocean.com/community/tutorials/how-to-serve-django-applications-with-uwsgi-and-nginx-on-centos-7
netstat shows that nginx is listening on port 80:
tcp0 0 0.0.0.0:80 0.0.0.0:*
L
Very thorough and detailed explanation, even if it was "simplified". Both
you and Reinis have been a tremendous help.
On Thu, Jul 28, 2016 at 11:07 AM, Robert Paprocki <
rpapro...@fearnothingproductions.net> wrote:
> Hello,
>
> On Thu, Jul 28, 2016 at 7:32 AM, Brian Pugh wrote:
>
>> Yesterday on
Hello,
On Thu, Jul 28, 2016 at 7:32 AM, Brian Pugh wrote:
> Yesterday once I got the traffic going to the backend servers from nginx I
> noticed that I was pinned to "backend3", which is last in the order. And
> since I am the one setting this up I am the only user. So I changed up my
> order ju
The results with defaults including ‘access_log /var/log/nginx/access.log;’
show the Requests/sec ramping up to ~24.5K and staying there.
The results with defaults and access_log changed to ‘access_log off;’ show
the Requests/sec initially ramping up to ~28.5K but then decreasing down to
~20K
Hello!
On Thu, Jul 28, 2016 at 10:32:13AM -0400, stevewin wrote:
> I am beginning to look at NGINX performance on a development system with
> traffic driven by Wrk. Initially I am just looking at static HTTP serving.
>
> I am using NGINX v1.10.1 running on the host system with Ubuntu 16.04. Wr
Yesterday once I got the traffic going to the backend servers from nginx I
noticed that I was pinned to "backend3", which is last in the order. And
since I am the one setting this up I am the only user. So I changed up my
order just to see the effects of calculating a new hash. Instead of:
upstrea
I am beginning to look at NGINX performance on a development system with
traffic driven by Wrk. Initially I am just looking at static HTTP serving.
I am using NGINX v1.10.1 running on the host system with Ubuntu 16.04. Wrk
v4.0.4 is running from a separate client platform over a private 40GB
con
Thanks Maxim, its works. :)
On 07/28/2016 03:29 PM, Maxim Konovalov wrote:
> Hi Dewangga,
>
> On 7/28/16 10:31 AM, Dewangga Bachrul Alam wrote:
>> Hello!
>>
>> I've tried to build nginx 1.11.3 with --with-stream module parameter,
>> but, attached below:
>>
> [...]
>
> That was already fixed.
>
Hi Dewangga,
On 7/28/16 10:31 AM, Dewangga Bachrul Alam wrote:
> Hello!
>
> I've tried to build nginx 1.11.3 with --with-stream module parameter,
> but, attached below:
>
[...]
That was already fixed.
As a workaround you can add "--with-stream_ssl_module" to your
configure args.
--
Maxim Kon
Hi Andrea,
The 404 Forbidden error is because of the permission of that particular
file / directory . NGINX process should be able to read that file in
/home/a/all/index.html.
Cheers!
Zeal
On Tue, Jul 26, 2016 at 4:47 PM, ndrini wrote:
> I have this server block in a EC2 nginx webserver.
>
>
Hello!
I've tried to build nginx 1.11.3 with --with-stream module parameter,
but, attached below:
.. snip ..
./configure \
--prefix=%{_sysconfdir}/nginx \
--sbin-path=%{_sbindir}/nginx \
--conf-path=%{_sysconfdir}/nginx/nginx.conf \
--error-log-path=%{_localstated
18 matches
Mail list logo