Custom Query (2296 matches)

Hello,

Nginx stops writing into error.log for the day after encountering some particular special character[s], e.g.:

2023/10/11 14:36:16 [warn] 184750#184750: *754 using uninitialized "domlogging" variable while logging request, client: 91.245.37.125, server: [...].com, request: "

(The final character here is an invisible space, not sure if this form can deliver it, just in case attach a screenshot from Brackets editor which displays special characters as red circles – ​https://i.imgur.com/j6XzKbT.png).

The error.log file time keeps getting updated after an entry like that (apparently from attempts to write...), however there is no more logging.

Restarting Nginx on the same day does not help, only restarting on the next day when the there's a newer error.log file works (until that special character line happens again).

For comparison, some other special characters do not break the log, example:

2023/10/11 14:15:47 [warn] 184750#184750: *351 using uninitialized "domlogging" variable while logging request, client: 64.227.138.197, server: [...].com, request: "zùÂÃòai¦¸fz¥_"

(Screenshot – ​https://i.imgur.com/3eZs881.png)

Server configuration related to "domlogging" is:

map $remote_addr $log_ip {
    "128.69.152.187" 0;
    "63.143.42.248" 0;
    "100.43.81.130" 0;
    "63.143.42.251" 0;
    "95.26.221.246" 0;
    default 1;
}
map $http_user_agent $log_bua {
    ~CloudFlare 0;
    ~Googlebot 0;
    ~YandexBot 0;
    ~bingbot 0;
    ~Baiduspider 0;
    ~UptimeRobot 0;
    ~YandexTurbo 0;
    default 1;
}

.....

    set $domlogging 1;
    if ( $log_bua = 0 ) {
        set $domlogging 0;
    }
    if ( $log_ip = 0 ) {
        set $domlogging 0;
    }

access_log /var/log/nginx/[...].log [...] if=$domlogging;

I have an old application that uses TLS 1.0 that I was attempting to proxy to a web app via NGINX. Unfortunately, NGINX seems to be causing a "short read", according to the app, and wireshark shows the app sending a "close notify" warning. Doing a janky setup without NGINX does not cause these warnings to show. I have tried switching web frameworks, and even languages entirely (twisted python -> rust actix -> rust rocket) but the same warning persists. The warning also shows when running NGINX on a raspberry pi. The configuration is listed below.

server {
	listen       9000 ssl;
	server_name  (server name here);

	ssl_certificate      (cert here);
	ssl_certificate_key  (key here);
	ssl_session_timeout 1d;
	ssl_session_cache shared:MozSSL:10m;
	ssl_session_tickets off;

	ssl_protocols TLSv1 TLSv1.1 TLSv1.2 TLSv1.3;
	ssl_ciphers "ALL:@SECLEVEL=0";
	ssl_prefer_server_ciphers off;
	location / {
		proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
		proxy_pass_request_headers on;
		proxy_pass http://127.0.0.1:80/;
	}
}

Hi ,

I tried to build nginx with quiche as explained below and tried to run curl with http3 but noticing below cores ​https://github.com/cloudflare/quiche/tree/master/nginx

nginx -V root@ubuntu:/tmp/cores# /src/nginx-1.16.1/objs/nginx -V nginx version: nginx/1.16.1 (quiche-ab2b44fa) built by gcc 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04) built with OpenSSL 1.1.1 (compatible; BoringSSL) (running with BoringSSL) TLS SNI support enabled configure arguments: --prefix=/src/nginx-1.16.1 --build=quiche-ab2b44fa --with-http_ssl_module --with-http_v2_module --with-http_v3_module --with-openssl=../quiche/quiche/deps/boringssl --with-quiche=../quiche

curl command and version root@ubuntu:/tmp/cores# curl -V curl 8.3.0-DEV (x86_64-pc-linux-gnu) libcurl/8.3.0-DEV OpenSSL/1.1.1s zlib/1.2.11 brotli/1.0.9 msh3/0.6.0.0 Release-Date: [unreleased] Protocols: dict file ftp ftps gopher gophers http https imap imaps mqtt pop3 pop3s rtsp smb smbs smtp smtps telnet tftp Features: alt-svc AsynchDNS brotli HSTS HTTP3 HTTPS-proxy IPv6 Largefile libz NTLM NTLM_WB SSL threadsafe UnixSockets

root@ubuntu:/tmp/cores# curl -k -v --http3-only -# -o /tmp/index.html ​https://127.0.0.1:5443/index.html below is the nginx bt

(gdb) bt #0 0x000055d6712442c2 in ngx_quic_write_handler (wev=<optimized out>) at src/event/ngx_event_quic.c:411 #1 0x000055d67123456f in ngx_event_process_posted (cycle=cycle@entry=0x55d6737d0700, posted=0x55d6717a0280 <ngx_posted_events>)

at src/event/ngx_event_posted.c:34

#2 0x000055d67123405c in ngx_process_events_and_timers (cycle=cycle@entry=0x55d6737d0700) at src/event/ngx_event.c:267 #3 0x000055d67123bf51 in ngx_worker_process_cycle (cycle=0x55d6737d0700, data=<optimized out>) at src/os/unix/ngx_process_cycle.c:750 #4 0x000055d67123a431 in ngx_spawn_process (cycle=cycle@entry=0x55d6737d0700,

proc=proc@entry=0x55d67123be67 <ngx_worker_process_cycle>, data=data@entry=0x4, name=name@entry=0x55d6715d8236 "worker process", respawn=respawn@entry=-3) at src/os/unix/ngx_process.c:199

#5 0x000055d67123b537 in ngx_start_worker_processes (cycle=cycle@entry=0x55d6737d0700, n=8, type=type@entry=-3)

at src/os/unix/ngx_process_cycle.c:359

#6 0x000055d67123c62d in ngx_master_process_cycle (cycle=cycle@entry=0x55d6737d0700) at src/os/unix/ngx_process_cycle.c:131 #7 0x000055d671214e0f in main (argc=<optimized out>, argv=<optimized out>) at src/core/nginx.c:382 (gdb) quit

nginx error log file

2023/09/06 11:26:06 [alert] 240245#0: worker process 240272 exited on signal 11 (core dumped) 2023/09/06 11:26:08 [alert] 240245#0: worker process 240274 exited on signal 11 (core dumped) 2023/09/06 11:26:12 [alert] 240245#0: worker process 240276 exited on signal 11 (core dumped) 2023/09/06 11:26:26 [alert] 240245#0: worker process 240247 exited on signal 11 (core dumped) 2023/09/06 11:26:27 [alert] 240245#0: worker process 240303 exited on signal 11 (core dumped) 2023/09/06 11:26:29 [alert] 240245#0: worker process 240305 exited on signal 11 (core dumped) 2023/09/06 11:26:33 [alert] 240245#0: worker process 240307 exited on signal 11 (core dumped) 2023/09/06 11:31:05 [alert] 240245#0: worker process 240250 exited on signal 11 (core dumped) 2023/09/06 11:31:06 [alert] 240245#0: worker process 241691 exited on signal 11 (core dumped) 2023/09/06 11:31:08 [alert] 240245#0: worker process 241692 exited on signal 11 (core dumped) 2023/09/06 11:31:12 [alert] 240245#0: worker process 241693 exited on signal 11 (core dumped) 2023/09/06 11:38:52 [alert] 240245#0: worker process 241694 exited on signal 11 (core dumped) 2023/09/06 11:38:53 [alert] 240245#0: worker process 241734 exited on signal 11 (core dumped) 2023/09/06 11:38:55 [alert] 240245#0: worker process 241735 exited on signal 11 (core dumped) 2023/09/06 11:38:59 [alert] 240245#0: worker process 241736 exited on signal 11 (core dumped) root@ubuntu:/tmp/cores#

root@ubuntu:/tmp/cores# ls -lrth total 89M -rwxrwxrwx 1 root root 12M Sep 6 11:31 core.nginx.240250 -rwxrwxrwx 1 root root 12M Sep 6 11:31 core.nginx.241691 -rwxrwxrwx 1 root root 12M Sep 6 11:31 core.nginx.241692 -rwxrwxrwx 1 root root 12M Sep 6 11:31 core.nginx.241693 -rwxrwxrwx 1 root root 12M Sep 6 11:38 core.nginx.241694 -rwxrwxrwx 1 root root 12M Sep 6 11:38 core.nginx.241734 -rwxrwxrwx 1 root root 12M Sep 6 11:38 core.nginx.241735 -rwxrwxrwx 1 root root 12M Sep 6 11:38 core.nginx.241736 root@ubuntu:/tmp/cores#

am i missing anything here?