Custom Query (2297 matches)

We use nginx+uwsgi stack and see many errors like:

Aug 30 00:00:55 imfmce-va-81-2 uwsgi: Tue Aug 30 00:00:55 2016 - SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) on request /provisioning/user/f205970b-6a9f-42b5-830f-c2bec9967b32 (ip 10.216.153.254) !!!

I understand that error occurs when client close connection before reading response or by uwsgi_read_timeout, but I don't understand why in access log I cann't see any error, nginx just log 200 OK:

Aug 30 00:00:55 imfmce-va-81-2 provisioning: active     [ 55544 ]       10.216.153.254  Sync-Wopi-SyncLocksTask hostpilot       73af65e4-5984-4b2c-baf4-c88cf8385898    -       ECDHE-RSA-AES256-GCM-SHA384     GET     /provisioning/user/f205970b-6a9f-42b5-830f-c2bec9967b32 -       0,0,1,0 200     -       1       OK      -       321     515     844

We use next format log line:

log_format ss_log_format "active\t[ \$pid ]\t\$remote_addr\t\$http_user_agent\t\$upstream_http_x_user_identity\t\$http_x_client_id\t\$http_x_request_id\t\$ssl_cipher\t\$request_method\t\$uri\t\$args\t\$upstream_http_x_durations\t\$status\t\$http_x_error_code\t\$connection_requests\t\$request_completion\t\$content_length\t\$request_length\t\$body_bytes_sent\t\$bytes_sent";

I would like you to understand that, we don't need to fix this error, we just need have right access logs.

Hello. I logging two parameters - request_time and upstream_response_time, but every time it's equal. For more, request_time in log about 5-7 ms, but browser show about 400-500 ms full load content. Why request_time show wrong time? How detect full time from start respons till last byte, sent to client? Nginx working in Docker container.

I installed nginx on my CentOS 7.2 machine from the mainline repo. All services are managed by systemd. When restarting nginx and viewing it's status, there is the following log line: Failed to read PID from file /run/nginx.pid: Invalid argument However, it doesn't affect nginx. But there is a really simple way to get rid of this error. The nginx config sets the pidfile to /var/run/nginx.pid while the PIDFile argument in the nginx.service systemd file is set to /run/nginx.pid. Changing this to the same value as in the nginx.conf (/var/run/nginx.pid) will remove the error. I know, it is the same physical directory, but somehow systemd has a problem if it's not the exact same path.