Search squid archive

squid+apache+php-fpm How squid could mark DEAD a peer where Apache is alive and php-fpm dead?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,


Thank you all for the great work on Squid.


I got last week a bad "issue" where a squid Version 4.0.23 set to send requests to 4 VMs didn't detect a dead peer.


On each VM are running Apache as the frontal, and php-fpm as php scripts execution.


Squid is using sourcehash load balancing algorithm.


But, if the php-fpm is down or busy, Apache will return a 504 Gateway timeout to Squid and browser, and squid will continue to send requests to same Apache, even if the answer will always be HTTP code 504, because Apache is ALIVE.


Apache is there, respawning, but the user is not getting the right answer.


And all IPs that are connecting to this VM, will fail, so 25% of all users will suffer unavailability.


I have setup some watchdogs scripts that will now, from the VM intern itself, check if there is a 504 code returned by Apache, and in that case, will restart php-fpm.


But how to tell squid to mark dead a peer that returns 504 code ?


Thanks

Patrick


_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users

[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux