Custom Query (2297 matches)

Hi

In an unit-file nginx.server (from RPM packages for CentOS 7,8) I offer to change a option ExecReload from ExecReload=/bin/kill -s HUP $MAINPID to ExecReload=/usr/sbin/nginx -s reload. Because /bin/kill -s HUP $MAINPID does not have an exit code unlike ExecReload=/usr/sbin/nginx -s reload. As a result now, a command systemctl reload nginx.service ; echo $? does not show a correct exit code.

Thanks in advance Alex Yakimov

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.

Currently, proxy_pass via upstream sends $host resolved in server_name or user-defined. This is usually good enough solution, but sometimes it's not, as I have experienced and I found other users having trouble with this too.

Use case is this: You have multiple servers serving content. This could be VPS, dedicated servers, but also shared hostings. Problem is, that you can't configure shared hosting to server same content under two different hosts (original www.example.com and from proxy proxy-example.com). It routes to different folder. Now you want to use one proxy server to serve content from all those servers.

Solution is very easy: extends server directive in upstream module to allow specifying host.

upstream example {
    server 1.2.3.4:80 host=www.example.com;
    server 1.2.3.3:80 host=www.example2.com;
}

when server 1.2.3.4:80 is chosen, it send header Host www.example.com; when server 1.2.3.3:80, it sends www.example2.com; if host is not specified, it sends Host resolved from server_name or specified with proxy_pass_header.