headers
pub crawler | 1 Mar 2011 23:40
Picon

Marketplace Wordpress install issue

Trying to do a Wordpress install from the MarketPlace.  Getting an error:

"Neither the 'mysql' nor the 'mysqli' modules are supported by your
PHP interpreter

Try the following instructions to install the required software:

sudo apt-get install php5-mysql"

So I do the apt-get and this outputs:

# apt-get install php5-mysql
Reading package lists... Done
Building dependency tree
Reading state information... Done
php5-mysql is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Ideas?
Permalink | Reply | 9 comments |
headers
Dean Matzkov | 1 Mar 2011 23:51
Picon
Gravatar

Re: Marketplace Wordpress install issue

On Tue, Mar 1, 2011 at 3:40 PM, pub crawler <pubcrawler.com <at> gmail.com> wrote:
> Trying to do a Wordpress install from the MarketPlace.  Getting an error:
>
> "Neither the 'mysql' nor the 'mysqli' modules are supported by your
> PHP interpreter

Did you enable loading of the MySQL extension in /etc/php5/cgi/php.ini?

Try adding the following line under the "Dynamic Extensions" section,
and see if it helps:

extension=mysql.so
Permalink | Reply | 8 comments |
headers
pub crawler | 2 Mar 2011 00:08
Picon

Re: Marketplace Wordpress install issue

Thanks Dean,

That *appears* to work. Now to get WordPress debugged and operating :)

Is this a typical step needed on all installs or did something install
wrong earlier? (adding extension=mysql.so)

Thanks!

On Tue, Mar 1, 2011 at 5:51 PM, Dean Matzkov <bapabooiee <at> gmail.com> wrote:
> On Tue, Mar 1, 2011 at 3:40 PM, pub crawler <pubcrawler.com <at> gmail.com> wrote:
>> Trying to do a Wordpress install from the MarketPlace.  Getting an error:
>>
>> "Neither the 'mysql' nor the 'mysqli' modules are supported by your
>> PHP interpreter
>
> Did you enable loading of the MySQL extension in /etc/php5/cgi/php.ini?
>
> Try adding the following line under the "Dynamic Extensions" section,
> and see if it helps:
>
> extension=mysql.so
>
Permalink | Reply | 7 comments |
headers
Chad Smith | 2 Mar 2011 04:59
Favicon

Want to tell my Cherokee story

Hi everyone,

I own The Easy API we are one of the fastest growing API's on the net and we provide services to developers here is how I came about to Cherokee. I have no idea if this is the right place for it but figured it would help to know who I am and why I came to the product.

The Easy API picked up 2 really big clients, and we started to run into a big problem about a month ago when we were using Apache and PHP Apache module. What we found is that it would choke under heavy load because of the framework that I originally built the system in (CakePHP). I then took a month and completely re-wrote the API from the ground up using only best practices PHP OOP5 code. I will be honest I started with Nginx and PHP-FPM. I was fairly happy with the service and the responsiveness of Nginx. There was a draw-back though, since the API is obviously very dynamic it wasn't harnessing the power of Nginx with it's caching mechanisms. More importantly when calls would be made within rapid succession Nginx would throw 500's. This made my clients extremely mad, and one of my big clients left because of it.

The next system I looked into was Lighttpd (Lighty). It was such an awful experience from the time of install to the time of benchmarking. It was just horrible.

That's when I decided to try Cherokee again, I tried it about a year ago and wasn't fully into it as I am now. The product has really became a stable, efficient, feature rich product. I loaded PHP-FPM through CGI and utilized PHP-FPM's child processes killer to limit the amount of memory that was being consumed by PHP. Furthermore the first day that I put it into production was a "big day" where we did over 100,000 requests within 4 hours. I was so proud when I didn't see one 500 and my clients were extremely happy. We are now doing about 1 million requests a month and it's just growing. The websites are still on Apache until I get some time to move them over to Cherokee, which will be soon.

Well done developers behind this project, you have made this customer a believer in what good well thought out code can do.

Thank you,
Chad R. Smith
Creator of The Easy API
http://theeasyapi.com

_______________________________________________
Cherokee mailing list
Cherokee <at> lists.octality.com
http://lists.octality.com/listinfo/cherokee
Permalink | Reply | 2 comments |
headers
David Moreno | 2 Mar 2011 05:03
Gravatar

Re: Want to tell my Cherokee story

This is pretty awesome. Thanks for sharing :)
-- 
David Moreno
http://damog.net/

On Tuesday, March 1, 2011 at 10:59 PM, Chad Smith wrote:

Hi everyone,

I own The Easy API we are one of the fastest growing API's on the net and we provide services to developers here is how I came about to Cherokee. I have no idea if this is the right place for it but figured it would help to know who I am and why I came to the product.

The Easy API picked up 2 really big clients, and we started to run into a big problem about a month ago when we were using Apache and PHP Apache module. What we found is that it would choke under heavy load because of the framework that I originally built the system in (CakePHP). I then took a month and completely re-wrote the API from the ground up using only best practices PHP OOP5 code. I will be honest I started with Nginx and PHP-FPM. I was fairly happy with the service and the responsiveness of Nginx. There was a draw-back though, since the API is obviously very dynamic it wasn't harnessing the power of Nginx with it's caching mechanisms. More importantly when calls would be made within rapid succession Nginx would throw 500's. This made my clients extremely mad, and one of my big clients left because of it.

The next system I looked into was Lighttpd (Lighty). It was such an awful experience from the time of install to the time of benchmarking. It was just horrible.

That's when I decided to try Cherokee again, I tried it about a year ago and wasn't fully into it as I am now. The product has really became a stable, efficient, feature rich product. I loaded PHP-FPM through CGI and utilized PHP-FPM's child processes killer to limit the amount of memory that was being consumed by PHP. Furthermore the first day that I put it into production was a "big day" where we did over 100,000 requests within 4 hours. I was so proud when I didn't see one 500 and my clients were extremely happy. We are now doing about 1 million requests a month and it's just growing. The websites are still on Apache until I get some time to move them over to Cherokee, which will be soon.

Well done developers behind this project, you have made this customer a believer in what good well thought out code can do.

Thank you,
Chad R. Smith
Creator of The Easy API
http://theeasyapi.com

_______________________________________________
Cherokee mailing list
Cherokee <at> lists.octality.com
http://lists.octality.com/listinfo/cherokee
 

_______________________________________________
Cherokee mailing list
Cherokee <at> lists.octality.com
http://lists.octality.com/listinfo/cherokee
Permalink | Reply | 0 comments |
headers
Dean Matzkov | 2 Mar 2011 07:01
Picon
Gravatar

Re: Marketplace Wordpress install issue

On Tue, Mar 1, 2011 at 4:08 PM, pub crawler <pubcrawler.com <at> gmail.com> wrote:
> Is this a typical step needed on all installs or did something install
> wrong earlier? (adding extension=mysql.so)

As far as I'm aware, this is something you'll need to do manually. All
the php5-mysql package on Debian does is install its files - no extra
configuration is done at all.

To verify this, look at the files '/var/lib/dpkg/info/php5-mysql.*'.
You'll notice there are no '.postinst' or '.prerm' files, which means
no automagical configuration is done when it's installed or
uninstalled.
Permalink | Reply | 6 comments |
headers
Alvaro Lopez Ortega | 2 Mar 2011 07:14
Favicon
Gravatar

Re: Want to tell my Cherokee story

Hello Chad,

Thanks for sharing your story with us.. and of course for you kind comments about the product.

All the best!


On 02/03/2011, at 04:59, Chad Smith wrote:

Hi everyone,

I own The Easy API we are one of the fastest growing API's on the net and we provide services to developers here is how I came about to Cherokee. I have no idea if this is the right place for it but figured it would help to know who I am and why I came to the product.

The Easy API picked up 2 really big clients, and we started to run into a big problem about a month ago when we were using Apache and PHP Apache module. What we found is that it would choke under heavy load because of the framework that I originally built the system in (CakePHP). I then took a month and completely re-wrote the API from the ground up using only best practices PHP OOP5 code. I will be honest I started with Nginx and PHP-FPM. I was fairly happy with the service and the responsiveness of Nginx. There was a draw-back though, since the API is obviously very dynamic it wasn't harnessing the power of Nginx with it's caching mechanisms. More importantly when calls would be made within rapid succession Nginx would throw 500's. This made my clients extremely mad, and one of my big clients left because of it.

The next system I looked into was Lighttpd (Lighty). It was such an awful experience from the time of install to the time of benchmarking. It was just horrible.

That's when I decided to try Cherokee again, I tried it about a year ago and wasn't fully into it as I am now. The product has really became a stable, efficient, feature rich product. I loaded PHP-FPM through CGI and utilized PHP-FPM's child processes killer to limit the amount of memory that was being consumed by PHP. Furthermore the first day that I put it into production was a "big day" where we did over 100,000 requests within 4 hours. I was so proud when I didn't see one 500 and my clients were extremely happy. We are now doing about 1 million requests a month and it's just growing. The websites are still on Apache until I get some time to move them over to Cherokee, which will be soon.

Well done developers behind this project, you have made this customer a believer in what good well thought out code can do.

Thank you,
Chad R. Smith
Creator of The Easy API
http://theeasyapi.com

_______________________________________________
Cherokee mailing list
Cherokee <at> lists.octality.com
http://lists.octality.com/listinfo/cherokee


_______________________________________________
Cherokee mailing list
Cherokee <at> lists.octality.com
http://lists.octality.com/listinfo/cherokee
Permalink | Reply | 0 comments |
headers
Taher Shihadeh | 2 Mar 2011 11:36

Re: Marketplace Wordpress install issue

Hi Paul, Dean.

As far as I'm aware of, it was working automatically.
Could you please specify exactly what Debian version you are using?
A bare Debian 5 netinstall plus php5-cgi and php5-mysql does the trick 
for me (same for Ubuntu, Mint, etc).

# php-cgi -m |grep mysql

mysql

mysqli

pdo_mysql

Regards

On 02/03/11 07:01, Dean Matzkov wrote:
> On Tue, Mar 1, 2011 at 4:08 PM, pub crawler<pubcrawler.com <at> gmail.com>  wrote:
>> Is this a typical step needed on all installs or did something install
>> wrong earlier? (adding extension=mysql.so)
> As far as I'm aware, this is something you'll need to do manually. All
> the php5-mysql package on Debian does is install its files - no extra
> configuration is done at all.
>
> To verify this, look at the files '/var/lib/dpkg/info/php5-mysql.*'.
> You'll notice there are no '.postinst' or '.prerm' files, which means
> no automagical configuration is done when it's installed or
> uninstalled.

--

-- 
taher <at> unixwars.com
http://unixwars.com/
Permalink | Reply | 5 comments |
headers
Ringo Hartmann | 2 Mar 2011 12:28
Picon

Re: Marketplace Wordpress install issue

> As far as I'm aware of, it was working automatically.

Yes, the Debian PHP packages usually load their extensions out of the
box.

Please see my earlier mail (that somehow didn't show up on the list) for
details:

> As far as I'm aware, this is something you'll need to do manually. All
> the php5-mysql package on Debian does is install its files - no extra
> configuration is done at all.

I'm not sure about Ubuntu but the Debian php5-mysql package usually
drops files into /etc/php5/conf.d which should take care of loading
the extensions.

/etc/php5/conf.d/mysql.ini:
extension=mysql.so

/etc/php5/conf.d/mysqli.ini:
extension=mysqli.so

/etc/php5/conf.d/pdo_mysql.ini:
extension=pdo_mysql.so

I've never had to do any of those manually on any Debian server.

There should also be a symlink on /etc/php5/cgi/conf.d to
/etc/php5/conf.d
that makes sure the conf.d contents are observed by your PHP CGI
processes.

However, restarting or reloading your PHP CGI processes to catch up
on conf.d contents might be required.
Permalink | Reply | 3 comments |
headers
Chad Smith | 2 Mar 2011 14:43
Favicon

Re: Marketplace Wordpress install issue

I'm running an ubuntu machine and found that PHP-FPM is a lot more robust and well suited for high traffic sites.

Check out the following install helper: http://www.howtoforge.com/installing-php-5.3-nginx-and-php-fpm-on-ubuntu-debian

This tells you how to setup Nginx with it but just ignore those parts, pay attention to the PHP install portion. Then startup the cherokee-admin and it will automagically find the php-cgi.

Hope this helps,
Chad


On Wed, Mar 2, 2011 at 6:28 AM, Ringo Hartmann <r.hartmann <at> wabnitz.it> wrote:
> As far as I'm aware of, it was working automatically.

Yes, the Debian PHP packages usually load their extensions out of the
box.

Please see my earlier mail (that somehow didn't show up on the list) for
details:


> As far as I'm aware, this is something you'll need to do manually. All
> the php5-mysql package on Debian does is install its files - no extra
> configuration is done at all.

I'm not sure about Ubuntu but the Debian php5-mysql package usually
drops files into /etc/php5/conf.d which should take care of loading
the extensions.

/etc/php5/conf.d/mysql.ini:
extension=mysql.so

/etc/php5/conf.d/mysqli.ini:
extension=mysqli.so

/etc/php5/conf.d/pdo_mysql.ini:
extension=pdo_mysql.so


I've never had to do any of those manually on any Debian server.

There should also be a symlink on /etc/php5/cgi/conf.d to
/etc/php5/conf.d
that makes sure the conf.d contents are observed by your PHP CGI
processes.

However, restarting or reloading your PHP CGI processes to catch up
on conf.d contents might be required.
_______________________________________________
Cherokee mailing list
Cherokee <at> lists.octality.com
http://lists.octality.com/listinfo/cherokee

_______________________________________________
Cherokee mailing list
Cherokee <at> lists.octality.com
http://lists.octality.com/listinfo/cherokee
Permalink | Reply | 2 comments |

Gmane