Custom Query (2297 matches)

I set up nginx 1.1.13 to keep the connection to my backend server alive. I put this into production and nginx would only stay up for about 10 or 15 seconds. No errors were reported in the error log. I've attached my nginx.conf file.

Here's the info from the Event Viewer

Faulting application name: nginx.exe, version: 0.0.0.0, time stamp: 0x4f1442c0 Faulting module name: ntdll.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba58 Exception code: 0xc0000374 Fault offset: 0x000ce653 Faulting process id: 0x12c0 Faulting application start time: 0x01ccdac4bff11e83 Faulting application path: c:\nginx\nginx.exe Faulting module path: C:\Windows\SysWOW64\ntdll.dll Report Id: 0a51b1e5-46b8-11e1-9eec-001999546962

Nginx after a Load Balancer and proxying Apache php site behaves in a strange way when defining a default_server catch-all block. Scenario :: Only one site-enabled with several server blocks defined on it. Each server has plenty of server_name (as ServerAlias does have the underlying apache). Next block is defined at the very beggining of site-enabled/onlysite :

server {
  listen 80 default_server;
  server_name _;
  proxy_intercept_errors on;
  error_log /var/log/nginx/000default-error.log debug;
  access_log /var/log/nginx/000default-access.log;
  return 444;
}

Result: .- As soon as i enable the above block, Server seems to respond Ok, returning 444 to every request like nonexistantsubdomain.mydomain.com but the 000default-access.log starts to be filled with:

..-[A] Plenty of requests which souhld be ok responded with the 444 code ..- [B] Plenty of strange request like this ::: [01/Feb/2012:12:13:40 +0100] "-" 400 0 "-" "-"

.- In less than 3 minutes, suddenly the above access log stops receiving that bunch of 444 responded requests[A] and it only shows the [B] from time to time (some buffer overloaded?). From that moment on, any request gets error as reponse.

Steps:

1. Setup nginx for mp4 streaming using the default config from docs.
2. Open streamed mp4 file in flowplayer or jwplayer.
3. Position to the center of the clip.

NOTE: you should position to the uncached part of the clip to reproduce the bug. It's hard to do this locally due to very high load speed.

Happened: video playback fails to resume (at about 80% of the cases) only sound plays. Expected: normal playback after positioning.

tested on win 1.1.15 / win 1.0.12 / linux64 1.0.12 - behavior is the same.

Comments:

1. Tried with the same clip and apache2 with h264 streaming module - works fine.
2. I also found the way to reproduce the issue using local web-server and local mplayer.

Steps:

• install local nginx & mplayer
• setup mp4 streaming as described above
• run "mplayer ​http://127.0.0.1/clip.mp4?start=600"

result: everything is almost OK, BUT note that for about 0.5/1 sec video is distorted (until the key frame) - there is no such behavior on apache2+streaming, everything works fine with apache

• try to fast forward the clip using "right" button on the keyboard.

result: video playback stopped with a lot of errors in mplayer log - there is no such behavior on apache2+streaming, everything works fine with apache

-- Dan