Re: Nginx Address is already in use

On July 30, 2017 9:45:02 PM EDT, Raymundo Ramirez Mata wrote: >I do not have httpd: > > > >sudo service httpd stop > >Failed to stop httpd.service: Unit httpd.service not loaded. > > > > > > On Sun, 30 Jul 2017 20:40:14 -0500 spectre inc

Re: Nginx Address is already in use

Try the following to find which process listens on port 80: sudo netstat -tulpn | grep ':80 ' Igal Sapir Lucee Core Developer Lucee.org On 7/30/2017 6:48 PM, spectre inc wrote: Is there contact email so I can give it my head tech Sent from my iPhone On Jul 30, 2017,

Re: Nginx Address is already in use

Is there contact email so I can give it my head tech Sent from my iPhone > On Jul 30, 2017, at 9:45 PM, Raymundo Ramirez Mata > wrote: > > I do not have httpd: > > sudo service httpd stop > Failed to stop httpd.service: Unit httpd.service not loaded. > > >

Re: Nginx Address is already in use

I do not have httpd: sudo service httpd stop Failed to stop httpd.service: Unit httpd.service not loaded. On Sun, 30 Jul 2017 20:40:14 -0500 spectre inc sales.skylinehost...@gmail.com wrote Service nginx stop Service httpd stop Then Service nginx start Service httpd

Re: Nginx Address is already in use

Service nginx stop Service httpd stop Then Service nginx start Service httpd start Sent from my iPhone > On Jul 30, 2017, at 9:32 PM, Raymundo Ramirez Mata > wrote: > > I did, but the problem persists > > > On Sun, 30 Jul 2017 20:28:39 -0500 spectre inc

Re: Nginx Address is already in use

I asking my tech to see if he can help On Sun, Jul 30, 2017 at 9:32 PM Raymundo Ramirez Mata < rramir...@hatandslash.com> wrote: > I did, but the problem persists > > > On Sun, 30 Jul 2017 20:28:39 -0500 *spectre inc > >*

Re: Nginx Address is already in use

I did, but the problem persists On Sun, 30 Jul 2017 20:28:39 -0500 spectre inc sales.skylinehost...@gmail.com wrote Fine the process and kill it then restart nginx On Sun, Jul 30, 2017 at 8:57 PM Raymundo Ramirez Mata rramir...@hatandslash.com wrote:

Re: Nginx Address is already in use

Fine the process and kill it then restart nginx On Sun, Jul 30, 2017 at 8:57 PM Raymundo Ramirez Mata < rramir...@hatandslash.com> wrote: > > Hi, > > My nginx has stopped working, I upgraded and updated today, also purged > mysql and installed mariadb, so I don't know what might broke it. when

Nginx Address is already in use

Hi, My nginx has stopped working, I upgraded and updated today, also purged mysql and installed mariadb, so I don't know what might broke it. when i run sudo nginx I get: nginx: [emerg] bind() to [::]:80 failed (98: Address already in use) nginx: [emerg] bind() to [::]:443 failed

Re: redirect related questions...

On Sun, Jul 30, 2017 at 12:56:55PM +0300, ST wrote: Hi there, > Is it a good idea to use DNS forwarding in order not to obtain/install > ssl keys for example.com as we don't plan to use it? This should make > redirection faster and requires no setup on nginx... Are there any down > sides of such

Re: serving certain file for all but one server{}

On Sun, Jul 30, 2017 at 02:48:05PM +0300, ST wrote: Hi there, > That is the problem - the special server{} (example.org) should serve > robot.txt as is. Those are all the other server{}s that need a redirect > from /robot.txt to /robot_closed.txt. Are there other ways to do that > except for

Re: Identifying "Writing" connections in status stub

During a busier part of the day, what is your minimum, median,99%, max requests per sec? > On Jul 30, 2017, at 9:31 AM, Vlad K. wrote: > > >> If you open the status page in a browser do the numbers report match >> what you see with netstat? > > Waiting does: > > #

Re: Buffering issues with nginx

Yes, I tested that and it appears to be the case. However, I don't see where nginx sets rcvbuf on the upstream socket as this one cannot be inherited. Somehow even with SND/RCV buffers set to low values and buffering disabled I get around 2.5BM stuck on nginx side. With my own simple proxy I get

Re: Buffering issues with nginx

On Saturday 29 July 2017 22:41:25 Dan34 wrote: > In nginx docs I see sndbuf option in listen directive. > Is there something that I don't understand about it, or developers of nginx > don't understand meaning of sndbuf... but I do not see a point to set sndbuf > on a listening socket. It just does

Re: Identifying "Writing" connections in status stub

On 2017-07-30 13:30, Peter Booth wrote: It appears that you have a lot of data that could help in this analysis. How frequently is the status page being queried? Does every status datapoint get recorded or is munin showing some rolled up rrd data? The nginx status page is queried every 5

Re: serving certain file for all but one server{}

That is the problem - the special server{} (example.org) should serve robot.txt as is. Those are all the other server{}s that need a redirect from /robot.txt to /robot_closed.txt. Are there other ways to do that except for explicit redirect inside of all those server{}s? On Sun, 2017-07-30 at

Re: serving certain file for all but one server{}

Hi! You can rewrite the uri in the special server {} by the “rewrite” directive. On 30 July 2017 at 19:09:27, ST (smn...@gmail.com) wrote: Hello, I have a lot of server{}s with different server_names all over my setup. I want to serve robots_closed.txt instead of robot.txt for all but one

Re: Identifying "Writing" connections in status stub

On 2017-07-30 11:26, Peter Booth wrote: I just reread the thread and realize that you answered q2, and that makes the graph even more surprising. You say that it son FreeBSD - does this mean that you don’t have /proc available to you? Is there a procstat or other way to see the equivalent of

Re: redirect related questions...

PPS: my fault: there is no ssl key info so obviously it should not work. At least for those server name listed inside first server{} (strange is that https://example.org - server{} three also stops working...) Is it a good idea to use DNS forwarding in order not to obtain/install ssl keys for

Re: redirect related questions...

PS: actually merely adding "listen 443 ssl;" to the first server causes the same error (curl: (35) Unknown SSL protocol error in connection to www.example.org:443) server { listen 443 ssl; server_name www.example.org example.com; # and some more domains return 301

Re: Identifying "Writing" connections in status stub

I just reread the thread and realize that you answered q2, and that makes the graph even more surprising. You say that it son FreeBSD - does this mean that you don’t have /proc available to you? Is there a procstat or other way to see the equivalent of /proc//fd - a list of all open file

Re: Identifying "Writing" connections in status stub

Vlad, You might not need to replicate it- you have it happening in production in front of you. Some questions: 1. When is the last time that your production nginx was restarted? 2. Do you have regular restarts? 3. Is there an obstacle to restarting at some point? 4. Is this a single instance or

Re: redirect related questions...

Hi Francis, thank you for the detailed answer... I tried to take care of the first problem by doing this: server { listen 80; listen 443 ssl; server_name www.example.org example.com; # and some more domains return 301 https://example.org$request_uri; } But the site stopped working all

Re: Identifying "Writing" connections in status stub

On 2017-07-30 01:47, Maxim Dounin wrote: It might not be trivial to debug such socket leaks though, and before doing anything else it is in general a good idea to: - make sure you are using latest nginx version, and - the problem is not in a 3rd party module (that is, you can reproduce it