Databases
StackOverflow2013
Postsdbo
POConfiguration Issues with PECL and PHP-FPM
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POConfiguration Issues with PECL and PHP-FPM
    text
    copied!<p>I'm using Ubuntu Natty. I recently installed NGINX 1.0.6 and PHP 5.3.8 (with --enable-fpm) from source. Everything went ok and I tested it with an info.php page with <code>phpinfo()</code>.</p> <p>I then installed APC and Memcache using PECL i.e. <code>pecl install apc</code>, etc. That seemed to go ok as well.</p> <p>However, when I edit my php.ini file and add the extension_dir and extension modules for both APC and Memcache, I get the following when I restart PHP.</p> <pre><code>Starting php-fpm PHP Warning: Module 'apc' already loaded in Unknown on line 0 &lt;br /&gt; &lt;b&gt;Warning&lt;/b&gt;: Module 'apc' already loaded in &lt;b&gt;Unknown&lt;/b&gt; on line &lt;b&gt;0&lt;/b&gt;&lt;br /&gt; PHP Warning: Module 'memcache' already loaded in Unknown on line 0 &lt;br /&gt; &lt;b&gt;Warning&lt;/b&gt;: Module 'memcache' already loaded in &lt;b&gt;Unknown&lt;/b&gt; on line &lt;b&gt;0&lt;/b&gt;&lt;br /&gt; done </code></pre> <p>When I open the info.php file to check what loaded, everything seems ok i.e. I see APC and Memcache references in the information.</p> <p>But when I uncomment the extensions i.e. <code>;extension=apc.so</code> and <code>;extension=memcache.so</code>, there are no errors, but the APC and Memcache listings in PHPinfo no longer appear.</p> <p>I'm not sure how these extensions are being loaded twice and from where. I'd appreciate some guidance.</p> <p>Thanks in advance.</p> <p><strong>EDIT</strong></p> <p>I'm using PHP-FPM and using <code>lsof -i -P</code> it appears that I have multiple pools of PHP-FPM running. Could this be part of the problem why I am seeing this error?! Is there a way to fix this?!</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload