Thread: Disable pconnect system wide

To disable the annoying pconnects system wide , without having to do any code changes, just edit your php.ini file, and restart apache.

Set this section in php.ini to:

Code:

[MySQL]
; Allow or prevent persistent links.
mysql.allow_persistent = Off

It will not break any scripts - they just automatically fall back to plain connects.

Smoge

Sorry for asking but could you describe it a little bit more for a newbie like me. Is there any connection by any means with log out problem ..

Zonebase

Hi,

No - a "logout problem" would be a "cookie problem".

Pconnect is persistant connections - between the application and mySQL.

On some servers, the way aeDating is coded, causes persistant connections to use up all available connections to the mySQL server - and make the system unavailable (more or less, crash).

Turning off pconnect fixes this, and is perhaps recommended if your webserver (apache) and database server (mysql) are on the same server. If your database is on a different server - you may wish to not disable pconnect.

Smoge

Originally Posted by TruckerJeff

what are the goods and bads on disabling this on a dedicated server just for your aedating site?

Well - I see really no bad if your web server and mysql server are on the same server.... most importantly - it stops the "too many connections" problem that seems to be a ongoing problem with aeDating (i think db.inc.php could use a re-write).

So like, what will happen if i leave it on?, What will happen if i disable it?

Your aedating will use pconnect (and other applications), and possibly, if your my.cnf file is not configured correclty (max connections) or if you have lots of online users - you will crash.

Turn it off - well - all good. (see above).

I have yet to get any errors but usually the most i have for now on the site is 30 to 50 concurrent logins at once. So i want to know if this will fix some future errors when connections get higher? Though this may fix errors does it slow things down?

Sounds like your my.cnf is set with a high number of connections (good) - is it slower or faster? I think the difference is small, when apache and mysql on same server. Big fear is running out of connections - and you can see whats up with that by running some mysql stats on your server - and see how many connections are sleeping and orphaned.

also SSH how do i edit the php.ini?

SSH in... do a

locate -u
locate php.ini

then edit php.ini with nano or vi or something... make a backup first..

For changes to apply, you need to restart apache.

Rob

phpinfo will tell you this information - which php.ini file is in use.

Create phpinfo.php and then run it from your web browser:

Code:

<?php
phpinfo();
?>

Smoge

SSH is easier than FTP... if you use www.bitvise.com and their "tunneler" application...

With this, you could sFTP it down, edit - upload.

Then restart apache.

Rob

I use cuteftp pro.........................
much easier.
also once you know the path by using the php info file of your php.ini you right click on it and click edit and edit it like a word document.

or download the file on your computer and edit and just replace it .

ftp is not secure (unless you take steps to encrypt your passwords).... while using SSH is. Same reason why most servers disable telnet - unsecure passwords.

Depends on how much you worry about this.... not a big deal in most cases I guess.

Smoge

Thought I would just mention cuteftp pro has a list of ways you can connect. Including ssh.
I use SSH2 Which is even more secure than ssh. You can also use it to connect via https etc and select the encryption you want to use and make it as secure as you want. Certainly can be made more secure than putty.

If you can not disable system wide in php.ini or by using a local php.ini file, you can try this:

Edit your db.inc.php file, and look for:

Code:

mysql_pconnect

and change to

Code:

mysql_connect

Be sure to test afterwards.

Rob