Well the table was so badly built, and the site has a lot of load on it, what happens is that using MyISAM table when ever and add, or update , or what ever happens all the table is locked, and on some load some of the updates take a while in this stupid table, in this while a lot of queries would be queued to be run on the table each one is holding a connection, so in less than a minute the whole connections would be taken, so when changing the table to InnoDB what happens is that the lock would be only on one row instead of all the table, which allows the other queries to be run in the same time.
That's it!
On 10/24/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Table? what do you mean! the two many connection situations was caused by
a Table?
guys, is this guy for real?
> Hay thanks for replying,
> but it turned out that the problem is something else, There is a table
> (which was so badly built) that was causing the problem, the table was
> fixed
> (converted to innodb instead of myisam and some indexes added, and some
> optimization), and everything is working good thanks for the help
>
> On 10/23/05, [EMAIL PROTECTED] <[EMAIL PROTECTED] > wrote:
>>
>> Ala',
>>
>> Are you sure that the problem is with "max_connections" or
>> "max_connection_errors". if the first then you have a capacity issue
>> that
>> you need to overcome (check you're apache configuration for your
>> connection time out and time to keep your connection pooled "use the
>> module if necessary)
>> if the second is what causing the problem, then you have to review your
>> PHP code to make sure that half open DB connections are eliminated (or
>> the
>> reason for your db connections are accumilating with errors).
>>
>> as for the iptables -m limit extension; I don't think it would be much
>> of
>> help, since it works on a connection syment not a logical connection,
>> but
>> you can make use of the syn-flood (if you think your getting one) by:
>>
>>
>> /sbin/iptables -A INPUT -i eth0 -p tcp --syn -j syn-flood
>> /sbin/iptables -A syn-flood -m limit --limit 10/s --limit-burst 15 -j
>> RETURN
>> /sbin/iptables -A syn-flood -j DROP
>>
>> base idea, you have to know for sure what is going on on your wire, and
>> then decide what to do (start by monitoring the site, and make sense out
>> of the times at which your glitches occure)
>>
>> hope this help.
>>
>>
>> Note: I don't see turing off PHP persistant connection going anywhere
>> but
>> aside from helping you, you might fight HTTP connections but you're
>> loose
>> DB connections as well (just a thought)
>>
>>
>> > Actually it is possible using iptables, use the -m limit module.
>> > I'll check it out for you when I get off work.
>> >
>> > On 10/23/05, Ala'a Ibrahim < [EMAIL PROTECTED]> wrote:
>> >>
>> >> hi all,
>> >> I have this problme on one of the servers, I have this site, that
>> runs
>> >> smoothly with no problems (php, and mysql), but at one point the site
>> >> suffers from too any connections to the database, on the other times
>> no
>> >> problems with this site.
>> >> I've mad the maximum connections at some to 1000 but the same problem
>> >> remains, I've checked the code, all of the connections are closed,
>> and
>> >> there
>> >> is no persistant connections used, all of them are mysql_connect,
>> I've
>> >> also
>> >> turned off the mysql.allow_persistent in the php.ini, but the same
>> >> problem
>> >> is there.
>> >> I'm suspecting an attack on the site is happining at some time
>> (perhaps
>> >> a
>> >> DoS), does anybody have any idea.
>> >> I'm thinking if there is a way in apache to set that if some ip is
>> >> making
>> >> an n calls in an x period of time, to block that ip for some period
>> of
>> >> time.
>> >> (is this possible, and how).
>> >>
>> >> --
>> >> Ala'a A. Ibrahim
>> >> http://360.yahoo.com/bai_83
>> >> http://alaa83.blogspot.com/
>> >>
>> >> _______________________________________________
>> >> General mailing list
>> >> [email protected]
>> >> http://mail.jolug.org/mailman/listinfo/general_jolug.org
>> >>
>> >>
>> >>
>> >
>> >
>> > --
>> > abulyomon
>> >
>> > www.KiLLTHeUPLiNK.com <http://www.killtheuplink.com/>
>> <http://www.KiLLTHeUPLiNK.com
>> < http://www.killtheuplink.com/>>
>> > _______________________________________________
>> > General mailing list
>> > [email protected]
>> > http://mail.jolug.org/mailman/listinfo/general_jolug.org
>> >
>>
>>
>> _______________________________________________
>> General mailing list
>> [email protected]
>> http://mail.jolug.org/mailman/listinfo/general_jolug.org
>>
>
>
>
> --
> Ala'a A. Ibrahim
> http://360.yahoo.com/bai_83
> http://alaa83.blogspot.com/
> _______________________________________________
> General mailing list
> [email protected]
> http://mail.jolug.org/mailman/listinfo/general_jolug.org
>
_______________________________________________
General mailing list
[email protected]
http://mail.jolug.org/mailman/listinfo/general_jolug.org
--
Ala'a A. Ibrahim
http://360.yahoo.com/bai_83
http://alaa83.blogspot.com/
_______________________________________________ General mailing list [email protected] http://mail.jolug.org/mailman/listinfo/general_jolug.org
