Re: grpc keepalive does not effect, nginx will close connection by the minute

2019-01-24 Thread Roar
It works! Thanks a ton! @Sergey Kandaurov Posted at Nginx Forum: https://forum.nginx.org/read.php?2,282769,282826#msg-282826 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: User directive error

2019-01-24 Thread Zhang Chao
Hello! > Why does this error occur (Ubuntu 18.04/nginx 1.14.0)? > > nginx.conf:21 > user www-data; > > error.log > 2019/01/24 19:07:07 [warn] 3526#3526: the "user" directive makes sense only if the master process runs with super- > user

Re: PCRE2 support?

2019-01-24 Thread Maxim Dounin
Hello! On Thu, Jan 24, 2019 at 10:47:48AM -0800, PGNet Dev wrote: > > Well, this depends on your point of view. If a project which > > actually developed the library fails to introduce support to the > > new version of the library - for an external observer this > > suggests that there is

Proxy with SSL offload and Nginx redirections

2019-01-24 Thread Artur
Hello, In my setup I have a proxy with TLS offload with Nginx as a backend server (without TLS). If client asks an url such as https://host/dir, the proxy relays the request to Nginx as follows : http://host/dir Nothing strange here, this is an usual behaviour. Then Nginx sees that there is

[nginx] Win32: detection of connect() errors in select().

2019-01-24 Thread Maxim Dounin
details: https://hg.nginx.org/nginx/rev/9234e8d61aa0 branches: changeset: 7446:9234e8d61aa0 user: Maxim Dounin date: Thu Jan 24 22:00:44 2019 +0300 description: Win32: detection of connect() errors in select(). On Windows, connect() errors are only reported via exceptfds descriptor

[nginx] Win32: properly enabled select on Windows.

2019-01-24 Thread Maxim Dounin
details: https://hg.nginx.org/nginx/rev/f3ff79ae31d9 branches: changeset: 7443:f3ff79ae31d9 user: Maxim Dounin date: Thu Jan 24 21:51:00 2019 +0300 description: Win32: properly enabled select on Windows. Previously, select was compiled in by default, but the NGX_HAVE_SELECT macro

[nginx] Win32: enabled both select and poll on Windows by default.

2019-01-24 Thread Maxim Dounin
details: https://hg.nginx.org/nginx/rev/c9235164bbf1 branches: changeset: 7445:c9235164bbf1 user: Maxim Dounin date: Thu Jan 24 22:00:13 2019 +0300 description: Win32: enabled both select and poll on Windows by default. Since we now have both select and poll on Windows, it is

[nginx] Win32: added WSAPoll() support.

2019-01-24 Thread Maxim Dounin
details: https://hg.nginx.org/nginx/rev/4089b3d2cb59 branches: changeset: 7444:4089b3d2cb59 user: Maxim Dounin date: Thu Jan 24 21:51:21 2019 +0300 description: Win32: added WSAPoll() support. WSAPoll() is only available with Windows Vista and newer (and only available during

[nginx] Events: fixed copying of old events in poll init.

2019-01-24 Thread Maxim Dounin
details: https://hg.nginx.org/nginx/rev/e0e636ab10be branches: changeset: 7442:e0e636ab10be user: Maxim Dounin date: Thu Jan 24 21:50:37 2019 +0300 description: Events: fixed copying of old events in poll init. Previously, the code incorrectly assumed "ngx_event_t *" elements

Re: PCRE2 support?

2019-01-24 Thread PGNet Dev
Well, this depends on your point of view. If a project which actually developed the library fails to introduce support to the new version of the library - for an external observer this suggests that there is something wrong with the new version. FUD 'suggestions' simply aren't needed. The

Re: PCRE2 support?

2019-01-24 Thread Maxim Dounin
Hello! On Thu, Jan 24, 2019 at 10:23:01AM -0500, Thomas Ward wrote: > It's been several more months, but now I need to ask what distributions > you are 'supporting' here, Maxim and nginx team. > > PCRE2 is in Debian, Ubuntu, CentOS, Fedora, and others.  That covers a > large portion of the

User directive error

2019-01-24 Thread Palvelin Postmaster via nginx
Why does this error occur (Ubuntu 18.04/nginx 1.14.0)? nginx.conf:21 user www-data; error.log 2019/01/24 19:07:07 [warn] 3526#3526: the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /etc/nginx/nginx.conf:21 # ps -axu |grep

Re: fcgiwrap не могу запустить

2019-01-24 Thread Иван
Ну вообще я же не телепатически эту инфу получил. Всё достаточно понятно написано в https://nginx.org/ru/docs/http/ngx_http_core_module.html#root : "Путь к файлу формируется путём простого добавления URI к значению директивы |root|." 24.01.2019 18:31, Victor Sudakov пишет: > Victor Sudakov

Re: grpc keepalive does not effect, nginx will close connection by the minute

2019-01-24 Thread Sergey Kandaurov
> On 24 Jan 2019, at 06:05, Roar wrote: > > I recompile nginx with debug module follow your instruction and check all > keepalive_timeout parameter. > I tested my application at 2019/01/24 10:49:53 and it responsed correctly, > and the connection between nginx and grpc server was closed as

Re: fcgiwrap не могу запустить

2019-01-24 Thread Victor Sudakov
Victor Sudakov wrote: > > > 2019/01/23 15:29:36 [error] 93721#100134: *5 FastCGI sent in stderr: > > > "Cannot get script name, are DOCUMENT_ROOT and SCRIPT_NAME (or > > > SCRIPT_FILENAME) set and is the script executable?" while reading > > > response header from upstream, client: 10.10.10.3,

Re: PCRE2 support?

2019-01-24 Thread Thomas Ward
It's been several more months, but now I need to ask what distributions you are 'supporting' here, Maxim and nginx team. PCRE2 is in Debian, Ubuntu, CentOS, Fedora, and others.  That covers a large portion of the major distributions at play. This has once again popped on my radar in Ubuntu as we

Re: aio/unix: Use signal.sival which is standard

2019-01-24 Thread Maxim Dounin
Hello! On Thu, Jan 24, 2019 at 10:07:57AM +0800, Sepherosa Ziehau wrote: > On Tue, Jan 22, 2019 at 10:54 PM Maxim Dounin wrote: > > This needs to be extended with some background information - > > notably why it used to be sigval_ptr, and why to switch to > > sival_ptr. > > I am not sure why

How to implement below config on nginx Reverse Proxy mode

2019-01-24 Thread blason
Hi Team, My nginx is configured in Reverse Proxy mode and catering to internet. However I have been tasked to add one e server with below config and I am facing difficulty while putting that in production. My scenario is I have internal server which accessed then gets diverted on to other port

Re: Use sub-url to identify the different server

2019-01-24 Thread Francis Daly
On Sun, Jan 20, 2019 at 10:13:05PM -0500, nevereturn01 wrote: Hi there, > Now, we are running a small business. So we don't have any load-balance or > fail-over deployment. So far, we have only 1 Nginx + 1 serverA + 1 serverB. So - you have internal serverA, which has its own content at