-
Notifications
You must be signed in to change notification settings - Fork 292
segfault at 0 ip 00007fdb9bdfa746 sp 00007fff7c0475f8 error 4 in libc-2.23.so #136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@KfirManSnunit could you please provide a backtrace from one of coredumps? TIA. |
@KfirManSnunit can you also share your version of libModSecurity? One issue that was known to be causing segfault was addressed here owasp-modsecurity/ModSecurity@fa5f378. Make sure your libModSecurity version have this commit applied. This one is already part of the latest release (3.0.3). Also, you mention that you're running ModSecurity-nginx: 1.0.0., In case you have not cloned from master but used the 1.0.0 release version. There's important fixes there that you should consider in case you don't have them on your build. |
Thanks victorhora, I have re-compile both, libmodsecurity and ModSecurity-nginx connector from: And so far 24h without nginx processes that are killed by segfault. |
It has been almost two days without nginx processes killed by segfault Or any other error. I'll update in a few days if the segfault error is finally resolved. |
It has been several days without reload/restart nginx And no segfault Or any other error. |
That's great news @KfirManSnunit. The community really appreciate you coming back here to let us know of your positive outcome and closing the issue. Thanks! :) |
Hi All, After further testing it was found that it was ModSecurity. syslog: nginx log: I use COMODO WAF v3 rules, Could there be a problem with the COMODO rules that could cause a problem? Regards, |
Still no success... My env info: This is the stak trace from valgrind: "valgrind --leak-check=full -v nginx"
Any help will be appreciated! |
Hello,
I've been trying for a while to figure out what cause the problem for unkilled worker, without success.
It started to happen since I installed ModSecurity-nginx according to this guide:
https://www.nginx.com/blog/compiling-and-installing-modsecurity-for-open-source-nginx/
I've seen these cases:
#19
#29
And it did not work for me.
It happens randomly and without any action on our part like "restart\reload\nginx -t"... And usually not during rush hours.
The nginx error.log show:
2018/11/17 21:31:04 [alert] 23669#23669: worker process 17191 exited on signal 11 (core dumped)
2018/11/17 21:33:09 [alert] 23669#23669: worker process 17852 exited on signal 11 (core dumped)
The syslog show:
Nov 17 21:26:56 kernel: [340028.785042] nginx[17191]: segfault at 0 ip 00007fdb9bdfa746 sp 00007fff7c0475f8 error 4 in libc-2.23.so[7fdb9bd6f000+1c0000]
Nov 17 21:33:09 kernel: [340401.577572] nginx[17852]: segfault at 0 ip 00007fdb9bdfa746 sp 00007fff7c047678 error 4 in libc-2.23.so[7fdb9bd6f000+1c0000]
ps aux | grep nginx
root 15837 0.0 0.0 12944 1032 pts/0 S+ 09:12 0:00 grep --color=auto nginx
nginx 17186 0.8 3.1 1194640 1034896 ? S Nov14 50:05 nginx: worker process
nginx 17187 1.2 3.1 1194640 1039008 ? R Nov14 71:05 nginx: worker process
nginx 17188 1.8 3.1 1194640 1039072 ? S Nov14 102:29 nginx: worker process
nginx 17189 2.5 3.1 1194640 1039072 ? S Nov14 143:18 nginx: worker process
nginx 17190 4.0 3.1 1194640 1039072 ? R Nov14 228:49 nginx: worker process
nginx 17192 10.2 3.1 1194640 1039072 ? R Nov14 575:35 nginx: worker process
nginx 17193 12.0 3.1 1194640 1039072 ? R Nov14 677:13 nginx: worker process
nginx 18228 5.0 3.1 1194640 1039008 ? R Nov17 35:40 nginx: worker process
root 23669 0.0 3.0 1170036 1013272 ? Ss Nov14 0:17 nginx: master process /usr/sbin/nginx -c /etc/nginx/nginx.conf
nginx 23672 0.3 2.0 821436 667072 ? S Nov14 22:44 nginx: worker process is shutting down
nginx 23673 0.4 2.0 843064 688668 ? S Nov14 27:37 nginx: worker process is shutting down
Nginx Status:
Active connections: 463
server accepts handled requests
2009265 2009265 19419989
Reading: 2 Writing: 1300 Waiting: 321
My environment:
Ubuntu: 16.04.5
Nginx: 1.15.5
ModSecurity-nginx: 1.0.0
I have an open case at nginx support forum:
https://trac.nginx.org/nginx/ticket/1650
Can you confirm that this bug related to ModSecurity-nginx connector?
I can see that in https://github.com/SpiderLabs/ModSecurity-nginx/blob/master/CHANGES you plan to release new version, Does it include a fix to this problem?
If I re-compile the connector it will include the fixes mentioned in CHANGES?
Regards,
Kfir Man
The text was updated successfully, but these errors were encountered: