Our supporttrio support ticket installation went down last night. Their code is protected via Zend Guard, which requires Zend Optimizer to be installed.
Our site is served and managed by Rackspace. Last night I realized that I should actually use their services rather than keep installing things myself. So I asked them to install APC.
All seemed a-okay. Unfortunately, supporttrio wasn’t on our Pingdom web monitoring account, so we didn’t know about its death until the next morning. No harm done except a few delayed tickets, but this was an unexpected surprise. Disabling APC caused the site to come back up.
Moral of the story: APC + Zend = Death. Google knows more about why; I can only infer it may be a namespace conflict, or perhaps even a misguided attempt at competition (Zend has their own cache product). I don’t really need to use APC, so I didn’t investigate, but I figured I’d save someone else the headache of discovery.
Hope this was helpful.
Posted on October 10th, 2007 by plusbryan
Filed under: Development
Aahhh, I wasn’t sure what the whole story was behind that crash.
Hey Bryan,
Thanks for the post… This is exactly what I experienced. Installed Zend Optimizer first and then APC on a debian 64bit box. PHP crashed immediately and then apache logs started flooding with errors like this
[notice] child pid 26126 exit signal Segmentation fault (11)
[notice] child pid 26155 exit signal Segmentation fault (11)
After spending a lot of time troubleshooting and google’ing I was able to find out the cause. Apparently, Zend does not want APC take over their business
https://www.zend.com/forums/index.php?t=msg&goto=6565&S=1c90a51e4f1bf8e8d712f622aacb0abe#msg_6565