How to fix Response Status 0 Worker Process Exited on Signal 11 in Nginx

Current Location：Home > Learning > NETWORK >

WEB FRONT-END PROGRAM NETWORK ALGORITHM OPERATING SYSTEM DATABASE

How to fix Response Status 0 Worker Process Exited on Signal 11 in Nginx

Author：JIYIK Last Updated：2025/03/17 Views：

Actually, let's clarify something first: HTTP does not have status code 0 (zero). The problem is that the nginx worker process died while handling the request, so the connection was broken, resulting in an error without any response data.

question

We have encountered this problem in various situations:

Github Webhooks : The webhook request was not completed successfully, and the response code is always 0
Piwik : We were unable to open the Piwik web control panel in Safari, nor were we able to add connection details on Android. Requests in both cases resulted in an error response with status 0.

Since we can't find any application errors in Strider and Piwik logs, the problem should be in the next layer: nginx.

We checked the nginx error log file and finally found a clue.

This is the default nginx error log file location on Ubuntu:/var/log/nginx/error.log

Error log file data:

2022/05/10 09:37:34 [alert] 7955#0: worker process 9835 exited on signal 11 (core dumped)  
2022/05/10 09:37:36 [alert] 7955#0: worker process 9853 exited on signal 11 (core dumped)  
2022/05/10 09:37:36 [alert] 7955#0: worker process 9855 exited on signal 11 (core dumped)  
2022/05/106 09:42:34 [alert] 7955#0: worker process 9857 exited on signal 11 (core dumped)

If anyone is interested, we use nginx version 1.8.0 .

Workaround

To fix this problem, you need to modify the nginx configuration and add the following line in the http block.

The default location of the nginx configuration file on Ubuntu is /etc/nginx/nginx.conf

http {  
    …
    ssl_session_cache    shared:SSL:10m;
    …
}

Nginx uses multiple worker processes to handle the requests it receives. ssl_session_cache shared:SSL:10mMake nginx share session information between all worker processes. From now on, each worker process has session information available and will not stop executing requests due to lack of request data.

Don't forget to restart the nginx service.

$ sudo service nginx restart

That's it. Our requests will flow through nginx to the application and vice versa without a problem!

Previous：Nginx is running but not serving sites

Next：How to fix the Unknown ＂connection_upgrade＂ Variable error in Nginx

For reprinting, please send an email to 1244347461@qq.com for approval. After obtaining the author's consent, kindly include the source as a link.

Article URL：

JIYIK CN >