# Xcache admin kills fpm childs on debian 64bit nginx php5-fpm mysql

**URL:** <https://www.ruby-forum.com/t/xcache-admin-kills-fpm-childs-on-debian-64bit-nginx-php5-fpm-mysql/219937>\
**Category:** NGINX\
**Created:** [May 22, 2012, 2:19pm UTC](https://www.ruby-forum.com/t/xcache-admin-kills-fpm-childs-on-debian-64bit-nginx-php5-fpm-mysql/219937 "2012-05-22T14:19:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gurdipe\_D](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/b77776/32.png) [@Gurdipe\_D](https://www.ruby-forum.com/u/Gurdipe_D)\
**Post date:** [May 22, 2012, 2:19pm UTC](https://www.ruby-forum.com/t/xcache-admin-kills-fpm-childs-on-debian-64bit-nginx-php5-fpm-mysql/219937/1 "2012-05-22T14:19:53Z")

</div>

Hello people,

I have a minimal debian 64bit server with nginx php5-fpm mysql and  
xcache installed on it. Seems everything is ok, but as soon as I decided  
to use xcache-admin skripts accessing them are ok, it asks the login and  
password and accepts the one I put in xcache.ini, but then it kills the  
fpm child that must serve the request and quiting with following log  
entries

in php-fpm.log  
WARNING: [pool www] child 3385 exited on signal 11 (SIGSEGV) after  
833.669396 seconds from start

in nginx log  
[error] 3040#0: \*48 recv() failed (104: Connection reset by peer) while  
reading response header from upstream, client: , server: localhost,  
request: “GET /xcache-admin/ HTTP/1.1”, upstream:  
“fastcgi://127.0.0.1:9000”, host:

Do anybody able to use xcache-admin with nginx?

Regards  
Voter

Posted at Nginx Forum:

> **[xcache admin kills fpm childs on debian 64bit nginx php5-fpm mysql](https://forum.nginx.org/read.php?2,226707,226707#msg-226707)**
>
> Hello people, I have a minimal debian 64bit server with nginx php5-fpm mysql and xcache installed on it. Seems everything is ok, but as soon as I decided to use xcache-admin skripts accessing them are ok, it asks the login and password and accepts...

---

<div class="post-metadata">

**Author:** ![voter](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/v/b487fb/32.png) [@voter](https://www.ruby-forum.com/u/voter)\
**Post date:** [May 22, 2012, 5:27pm UTC](https://www.ruby-forum.com/t/xcache-admin-kills-fpm-childs-on-debian-64bit-nginx-php5-fpm-mysql/219937/2 "2012-05-22T17:27:33Z")

</div>

> WARNING: [pool www] child 3385 exited on signal 11 (SIGSEGV) after 833.669396  
> seconds from start

Since php segfaults there is nothing nginx can really do.

Can only suggest to enable core dumps to pinpoint the problem and/or  
send those to the Xcache developer or try another opcode cacher  
like APC (in my own experience after comparing nearly all - APC while  
not being always the fastest (for example eAccelerator can  
outperform) under load usually has had less problems in the past).

There are also quite a plenty of segfault tickets and one which looks  
similar to your: [http://xcache.lighttpd.net/ticket/272](http://xcache.lighttpd.net/ticket/272)  
So maybe try to set xcache.admin.enable\_auth = Off and see if it helps.

rr