Their was issue with my install. Too many open connection via TCP/IP.

I think switch to bind PHP-FPM to socket will increase perfomance. I'll working on this.

CommentFileSizeAuthor
#1 phpfpm_socket-2056321.patch10.26 KBShellingfox

Comments

Shellingfox’s picture

Status: Needs work » Needs review
StatusFileSize
new10.26 KB

Here is my change in my current server, it work perferct.

omega8cc’s picture

Project: Barracuda » Octopus
Component: Code » Nginx Configuration
Assigned: Shellingfox » Unassigned
Status: Needs review » Postponed

Thanks for the patch, but Aegir doesn't use unix socket for PHP-FPM by default *by design* - it is unreliable in the high-performance configuration and real world high traffic sites. Also, if you have got such weird error, it is probably your parent virtualization host fault (wrong restrictions) or some other bug. I would suggest to find and fix the source of your problem instead of looking for unreliable workaround.

We do plan to make this *configurable*, similarly to the auto-detection we have added in the Aegir HEAD: http://drupalcode.org/project/provision.git/commit/2d4a4c9 but it has low priority, because we recommend to avoid unix socket for PHP-FPM, especially in the stack designed for high performance and reliability.

~Greg

omega8cc’s picture

Project: Octopus » Barracuda
Component: Nginx Configuration » PHP-FPM Server

Since it will affect both Barracuda and Octopus side, I'm moving this back to the Barracuda queue for now.

~Greg

omega8cc’s picture

Version: » 6.x-2.x-dev
Issue summary: View changes
Status: Postponed » Fixed

This has been implemented by default for PHP 5.4 and 5.5 (in HEAD) and later also 5.3 will listen by default on instance specific socket. Now it still listens on the port for legacy reasons/compatibility.

Anonymous’s picture

Hello,

Does # 4 mean that you are now recommending to use socket based php-fmp for all php 5.4 and 5.5 fpm instances? In a high performance real-world setting? Thanks for clarification.

omega8cc’s picture

Yes, it is now recommended because it allows us to use separate sockets per Octopus instance without going with crazy custom ports for FPM per instance (every Octopus instance will have its own FPM pool for greater virtual chroot separation and will run as a USER.ftp and not www-data). We have also tweaked some kernel defaults to avoid typical issues affecting otherwise the socket mode.

That said, we have introduced it for PHP 5.4 and 5.5 only (none is default), before doing it also for 5.3 (default) in the next release, so there will be enough time to test how it works.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.