nginx -t success but nginx -s reload failed

[夏 凯]

when nginx.conf have no "\n" in it, nginx -t will succeed with the error "[emerg] no "events" section in configuration", and when you reload nginx ,the daemon process crash.
where is the command:
15:24:11#tp#conf> echo abc |sudo tee nginx.conf >/dev/null
15:24:29#tp#conf> sudo ../sbin/nginx -t
nginx: [emerg] unexpected end of file, expecting ";" or "}" in /usr/local/nginx/conf/nginx.conf:2
nginx: configuration file /usr/local/nginx/conf/nginx.conf test failed
15:24:37#tp#conf> sudo ../sbin/nginx -s reload
nginx: [emerg] unexpected end of file, expecting ";" or "}" in /usr/local/nginx/conf/nginx.conf:2
15:24:40#tp#conf> ps -fe|grep nginx
root 30029 1 0 15:24 ? 00:00:00 nginx: master process ../sbin/nginx
nobody 30030 30029 0 15:24 ? 00:00:00 nginx: worker process
walkerxk 30045 29527 0 15:24 pts/4 00:00:00 grep --color nginx
15:24:43#tp#conf> echo -n abc |sudo tee nginx.conf >/dev/null
15:24:51#tp#conf> sudo ../sbin/nginx -t
nginx: the configuration file /usr/local/nginx/conf/nginx.conf syntax is ok
nginx: [emerg] no "events" section in configuration
15:24:54#tp#conf> ps -fe|grep nginx
root 30029 1 0 15:24 ? 00:00:00 nginx: master process ../sbin/nginx
nobody 30030 30029 0 15:24 ? 00:00:00 nginx: worker process
walkerxk 30055 29527 0 15:24 pts/4 00:00:00 grep --color nginx
15:24:58#tp#conf> sudo ../sbin/nginx -s reload
15:25:02#tp#conf> ps -fe|grep nginx
nobody 30030 1 0 15:24 ? 00:00:00 nginx: worker process
walkerxk 30068 29527 0 15:25 pts/4 00:00:00 grep --color nginx
15:25:03#tp#conf>

[Maxim Dounin]

In [4600/nginx]:

Fixed master exit if there is no events section (ticket #150).

Instead of checking if there is events{} section present in configuration
in init_module handler we now do the same in init_conf handler. This
allows master process to detect incorrect configuration early and
reject it.

[Maxim Dounin]

Fix committed, thanks.