General » Maintenance / Connection problems
Maintenance / Connection problems
Published 31/01/2010 @ 10:11:44, By antp
To try to solve the problem about "too many connections" which happens often these days, I'll today move the database to another server (still at the same hosting provider), for that I will have to lock the site to prevent any changes until end of the process, that may take only few minutes to at most one hour, I hope.
Latest Edition: 05/02/2010 @ 15:20:47
Latest Edition: 05/02/2010 @ 15:20:47
Maintenance of 31 January
Published 31/01/2010 @ 10:29:33, By dragonboy3000
This won't affect unprocessed contributions that are waiting for approval, will it?
Maintenance of 31 January
Published 31/01/2010 @ 11:20:07, By antp
No, that's why I lock the site for any change:
- lock
- save the database
- restore the database on the new server
- unlock
if there were changes done between save & restore, they would be lost. But all what was there before I locked it, is saved.
- lock
- save the database
- restore the database on the new server
- unlock
if there were changes done between save & restore, they would be lost. But all what was there before I locked it, is saved.
Maintenance of 31 January
Published 31/01/2010 @ 11:35:45, By antp
Done.
Those who were connected while the change was done will possibly have to logoff/logon again (in case you do not see contributor/admin links).
Those who were connected while the change was done will possibly have to logoff/logon again (in case you do not see contributor/admin links).
Maintenance of 31 January
Published 31/01/2010 @ 11:40:10, By t0nkatracker
still getting the error message so I logged off and now it wont even let me log in. Getting this one now:
Too many connections in /homez.83/imcdb/www/config_connection.php on line 14
Too many connections in /homez.83/imcdb/www/config_connection.php on line 14
Maintenance of 31 January
Published 31/01/2010 @ 11:40:57, By antp
I just saw that too... and I wonder why that happens since that server is not supposed to have a limit on the number of connections
Maintenance of 31 January
Published 31/01/2010 @ 11:44:10, By antp
I'll upgrade to 256 MB or memory on the server instead of 128 currently, I hope that it will be enough.
Price is not much a problem, Google ads pays for that but if even when paying more it does not work better I do not know what to do except having a server dedicated to imcdb... which I can't administrate myself as I do not have enough knowledge and time.
Price is not much a problem, Google ads pays for that but if even when paying more it does not work better I do not know what to do except having a server dedicated to imcdb... which I can't administrate myself as I do not have enough knowledge and time.
Maintenance of 31 January
Published 31/01/2010 @ 12:03:30, By antp
Done, I do not know if it will work or not. If we still get these errors I should contact the technical support, as it is not normal. But I am afraid that they will say as usual "try to optimize your code", which they say even when it is a problem on their server...
Maintenance of 31 January
Published 31/01/2010 @ 12:07:44, By antp
Argh... it is down again. I do not know what to do in the meantime.
Maintenance of 31 January
Published 31/01/2010 @ 12:51:12, By Jale
Maintenance of 31 January
Published 31/01/2010 @ 12:54:24, By Jale
Maintenance of 31 January
Published 31/01/2010 @ 13:18:07, By dragonboy3000
Yeah, im also getting the same thing as tonka (and probably various other members too) and unable to login.
Also get "Warning: Cannot modify header information - headers already sent by (output started at /homez.83/imcdb/www/config_connection.php:14) in /homez.83/imcdb/www/user.php on line 72" and the same one again but 73 at the end.
Latest Edition: 31/01/2010 @ 13:37:41
Also get "Warning: Cannot modify header information - headers already sent by (output started at /homez.83/imcdb/www/config_connection.php:14) in /homez.83/imcdb/www/user.php on line 72" and the same one again but 73 at the end.
Latest Edition: 31/01/2010 @ 13:37:41
Maintenance of 31 January
Published 31/01/2010 @ 13:19:40, By weasel1984
I have to say that the "too many connections error" I see since longer time, however it was never so irritating, like last time (site completly blocked at some hours) - since we have the new contributions system. If the site still won't work and other solutions won't help maybe it will be better to back to the old methods(?) unfortunately...
Latest Edition: 31/01/2010 @ 14:08:06
Latest Edition: 31/01/2010 @ 14:08:06
Maintenance of 31 January
Published 31/01/2010 @ 14:43:12, By antp
The server has a much higher limit than before, it does not even use all his memory. The code of the site is the same as it was in December before we started to have problems. I do not see why the server is filled with open connections. I should try to contact tech support I guess.
It is not due to new contributions system. I switched to another database server about at the same time I added the new contributions system, hence why it looks like the two are related
I can't switch to the old system for tong time as soon the database would be too big for it anyway.
So I have to find how to solve this.
Latest Edition: 31/01/2010 @ 14:43:39
It is not due to new contributions system. I switched to another database server about at the same time I added the new contributions system, hence why it looks like the two are related
I can't switch to the old system for tong time as soon the database would be too big for it anyway.
So I have to find how to solve this.
Latest Edition: 31/01/2010 @ 14:43:39
Maintenance of 31 January
Published 31/01/2010 @ 14:51:04, By antp
The limit is set at 100 connections (on the old server it was 5 or 10...), at some time I was seeing the list of 100 query results staying in the queue for clients which asked these. Now the queue is empty despite the fact that there must be as many people on the site as few hours ago.
So I really think it is not a problem in imcdb but just on the server itself.
I made a small change to use persistent connections (mysql_pconnect instead of mysql_connect) just to see if it helps. But as currently it seems to work I can't know if that change will help in case it fails again
Latest Edition: 31/01/2010 @ 14:51:51
So I really think it is not a problem in imcdb but just on the server itself.
I made a small change to use persistent connections (mysql_pconnect instead of mysql_connect) just to see if it helps. But as currently it seems to work I can't know if that change will help in case it fails again
Latest Edition: 31/01/2010 @ 14:51:51
Maintenance of 31 January
Published 31/01/2010 @ 15:15:18, By antp
Now it seems to work, I do not know if the problem is solved on the server or if it is the change I made... if you notice that problem again do not hesitate to report it
Maintenance of 31 January
Published 31/01/2010 @ 15:30:40, By antp
Hmm still not solved, it fails again
I'll contact them on Monday morning.
I'll contact them on Monday morning.
Maintenance of 31 January
Published 31/01/2010 @ 18:40:25, By Neptune
Don’t get frustrated, you’ll find a solution, I have faith in you.
(Probably not much comfort coming from a person over a thousand miles across the ocean )
We should break into celebration once the pesky problem is solved.
(Probably not much comfort coming from a person over a thousand miles across the ocean )
We should break into celebration once the pesky problem is solved.
Maintenance of 31 January
Published 31/01/2010 @ 18:57:03, By electra225
I really hope You'll solve the problem soon. this site is so nice...!!!
Maintenance of 31 January
Published 31/01/2010 @ 20:55:47, By 93_Montero
It seems to be working now for me!