Bas Smeelen wrote: [snip] > > My previous response was sent too early :( > > I still get errors in apache > [Tue Sep 04 08:14:42 2012] [error] [client 192.168.1.189] PHP Warning: > Unknown: Unable to allocate memory for pool. in Unknown on line 0, > referer: > http://sys.ose.nl/cacti/graph_view.php?action=tree&tree_id=1&leaf_id=21 > [Tue Sep 04 08:14:43 2012] [notice] child pid 56172 exit signal > [Segmentation > fault (11) > [Tue Sep 04 08:14:43 2012] [notice] child pid 56163 exit signal > [Segmentation > fault (11) > [Tue Sep 04 08:14:53 2012] [error] [client 192.168.1.189] PHP Warning: > Unknown: Unable to allocate memory for pool. in Unknown on line 0, > referer: > http://sys.ose.nl/cacti/graph_view.php?action=tree&tree_id=1&leaf_id=7 > [Tue Sep 04 08:15:59 2012] [notice] child pid 56169 exit signal > [Segmentation > fault (11) > > So now I will comment out all extensions and start investigating. > Well it turns out to be apc.so, this comes with core php I guess? > For completeness: The php manual states this is for alternative php cache. > http://php.net/manual/en/book.apc.php
I use xcache. However, whenever I rebuild PHP I also rebuild xcache. Sometimes when the change is very small you may get away with not doing it, but whenever updating between major versions it is a must. I had this happen one time too many and just got into the habit of whenever I rebuild/update PHP I rebuild xcache as well. I believe it pulls in includes form PHP during it's build process so if PHP changes too much xcache will segfault, or just outright refuse to load. [snip] _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
