-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Nginx error log : recv() failed (104: Connection reset by peer) #12160
Comments
This means that your fastcgi ended unexpectedly. Check php-fpm(or whatever other handler you are using) logs. It's possible that you have core dump. Then try to use this to generace backtrace: https://github.com/phalcon/cphalcon/wiki/Generating-a-backtrace |
[23-Aug-2016 16:57:10] WARNING: [pool www] child 1933 exited on signal 11 (SIGSEGV) after 221.151060 seconds from start |
This means segfault, read what i wrote above. Provide backtrace from gdb. |
With Phalcon 2.0.x and PHP 5.x this issue was also present, but only during high load. |
Guys, please post backtrace, we don't anything how to reproduce this issue, you just posted some code of controller, i have controller and action too and it works for me. I NEVER had such an issue on php 5.x and phalcon 2.0.x, php5-fpm uptime is like xxx hours. |
|
|
Disable xdebug and post backtrace again. Also post whole backtrace, from beginning to end, this is beginning from #24 jump/function execute. Also reading symbols etc is not needed, only backtrace of functions executed. |
Disable xdebug ,it's ok now. |
xdebug - a tool which can cause many issues, and not only with Phalcon! |
We find it maybe same error code in view script. |
@Jurigag Can you help provide any more insight as I think this issue seems to be persistent with Xdebug + PHP7-phalcon -- definitely an issue in my opinion (currently disabled in my testing) |
IMHO, xdebug shoudn't be used at all with Phalcon since it interferes with PHP internals. For instance, ionCube loader and Xdebug cannot work together officially for the same reason. |
@virgofx what yu mean ? Just don't use phalcon and xdebug, don't see any other soultion to be honest, and there can be way too much things causing this. |
@stamster - I guess I'm curious as to why? Phalcon worked fine with PHP56 and XDebug. Debugging is very useful in enterprise and large applications. Why don't we just get a few more stack traces and see if @andresgutierrez can look into it? |
Then post whole script to reproduce, best repository, whole stacktrace with both php and phalcon compiled as debug and then someone can look into this. |
Thank you for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please feel free to either reopen this issue or open a new one. We will be more than happy to look at it again! You can read more here: https://blog.phalconphp.com/post/github-closing-old-issues |
Details
The text was updated successfully, but these errors were encountered: