server overload server overload
 

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Main Menu

server overload

Started by jstill, November 12, 2008, 02:48:29 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

jstill

IX webhost is telling me that the overload on the server was caused by the information below.  I have no idea what to do or what this means.   I know I need to add captcha to my coppermine galleries to stop all the spam, but I do not know how to to that.  I hope someone can help me. I cannot get into my galleries.  Thanks

==>Most common queries shampoo_copperm:
->Query summary
Time: 98% (1827 sec) Amount: 96% (81 queries) Rows Examined/Sent: 12377361 / 1956292 Avg. Query Exec/Lock Time: 22 / 0 sec.
Used databases: [shampoo_coppermine]
Query example: use shampoo_coppermine; SELECT p.*, msg_id, author_id, msg_author, UNIX_TIMESTAMP(msg_date) as msg_date, msg_body, aid FROM cpg140_comments as c, cpg140_pictures as p WHERE approved = 'YES' AND c.pid = p.pid AND ( aid IN (1,2,4,5) ) ORDER by msg_id DESC;
|id rows Extra
|1 439 Using where; Using temporary; Using filesort
|1 157 Using where
|__________________
->Query summary
Time: 0% (16 sec) Amount: 2% (2 queries) Rows Examined/Sent: 488 / 244 Avg. Query Exec/Lock Time: 8 / 1 sec.
Used databases: [shampoo_coppermine]
Query example: use shampoo_coppermine; SELECT msg_id, msg_author, msg_body, UNIX_TIMESTAMP(msg_date) AS msg_date, author_id, author_md5_id, msg_raw_ip, msg_hdr_ip, pid FROM cpg140_comments WHERE pid='406' ORDER BY msg_id ASC;
|id rows Extra
|1 144 Using where; Using filesort
|__________________
->Query summary
Time: 1% (21 sec) Amount: 1% (1 queries) Rows Examined/Sent: 55625 / 1 Avg. Query Exec/Lock Time: 21 / 0 sec.
Used databases: [shampoo_coppermine]
Query example: use shampoo_coppermine; SELECT count(*), MAX(msg_id) FROM cpg140_comments as c, cpg140_pictures as p WHERE c.pid = p.pid AND author_id = '1';
|id rows Extra
|1 439 Using index
|1 157 Using where
|__________________

->Query summary
Time: 99% (2810 sec) Amount: 97% (91 queries) Rows Examined/Sent: 13256279 / 2222728 Avg. Query Exec/Lock Time: 30 / 0 sec.
Used databases: [shampoo_coppermine]
Query example: use shampoo_coppermine; SELECT p.*, msg_id, author_id, msg_author, UNIX_TIMESTAMP(msg_date) as msg_date, msg_body, aid FROM cpg140_comments as c, cpg140_pictures as p WHERE approved = 'YES' AND c.pid = p.pid AND ( aid IN (1,2,5) ) ORDER by msg_id DESC;
|id rows Extra
|1 439 Using where; Using temporary; Using filesort
|1 157 Using where
|__________________
->Query summary
Time: 0% (7 sec) Amount: 1% (1 queries) Rows Examined/Sent: 278 / 139 Avg. Query Exec/Lock Time: 7 / 0 sec.
Used databases: [shampoo_coppermine]
Query example: use shampoo_coppermine; SELECT msg_id, msg_author, msg_body, UNIX_TIMESTAMP(msg_date) AS msg_date, author_id, author_md5_id, msg_raw_ip, msg_hdr_ip, pid FROM cpg140_comments WHERE pid='149' ORDER BY msg_id ASC;
|id rows Extra
|1 107 Using where; Using filesort
|__________________
->Query summary
Time: 0% (9 sec) Amount: 1% (1 queries) Rows Examined/Sent: 165558 / 1 Avg. Query Exec/Lock Time: 9 / 1 sec.
Used databases: [shampoo_coppermine]
Query example: use shampoo_coppermine; SELECT count(*) FROM cpg140_comments as c LEFT JOIN cpg140_pictures as p ON c.pid=p.pid LEFT JOIN cpg140_albums as a ON a.aid=p.aid WHERE 1;
|id rows Extra
|1 55186 Using index
|1 1
|1 1 Using index
|__________________
->Query summary
Time: 96% (3103 sec) Amount: 90% (101 queries) Rows Examined/Sent: 15155372 / 2600503 Avg. Query Exec/Lock Time: 30 / 0 sec.
Used databases: [shampoo_coppermine]
Query example: use shampoo_coppermine; SELECT p.*, msg_id, author_id, msg_author, UNIX_TIMESTAMP(msg_date) as msg_date, msg_body, aid FROM cpg140_comments as c, cpg140_pictures as p WHERE approved = 'YES' AND c.pid = p.pid AND ( aid IN (2) ) ORDER by msg_id DESC;
|id rows Extra
|1 330 Using where; Using temporary; Using filesort
|1 157 Using where
|__________________
->Query summary
Time: 0% (16 sec) Amount: 1% (2 queries) Rows Examined/Sent: 331116 / 2 Avg. Query Exec/Lock Time: 8 / 0 sec.
Used databases: [shampoo_coppermine]
Query example: use shampoo_coppermine; SELECT count(*) FROM cpg140_comments as c LEFT JOIN cpg140_pictures as p ON c.pid=p.pid LEFT JOIN cpg140_albums as a ON a.aid=p.aid WHERE 1;
|id rows Extra
|1 55186 Using index
|1 1
|1 1 Using index
|__________________
->Query summary
Time: 0% (20 sec) Amount: 0% (1 queries) Rows Examined/Sent: 0 / 1 Avg. Query Exec/Lock Time: 20 / 9 sec.
Used databases: [shampoo_coppermine]
Query example: use shampoo_coppermine; SELECT user_name as user_name FROM `shampoo_coppermine`.cpg140_users WHERE user_id = '1';
|id rows Extra
|1 1
|__________________
->Query summary
Time: 0% (7 sec) Amount: 0% (1 queries) Rows Examined/Sent: 0 / 1 Avg. Query Exec/Lock Time: 7 / 0 sec.
Used databases: [shampoo_coppermine]
Query example: use shampoo_coppermine; SELECT title, comments, votes, category, aid FROM cpg140_albums WHERE aid='1' LIMIT 1;
|id rows Extra
|1 1
|__________________
->Query summary
Time: 0% (8 sec) Amount: 0% (1 queries) Rows Examined/Sent: 276 / 138 Avg. Query Exec/Lock Time: 8 / 0 sec.
Used databases: [shampoo_coppermine]
Query example: use shampoo_coppermine; SELECT msg_id, msg_author, msg_body, UNIX_TIMESTAMP(msg_date) AS msg_date, author_id, author_md5_id, msg_raw_ip, msg_hdr_ip, pid FROM cpg140_comments WHERE pid='63' ORDER BY msg_id ASC;
|id rows Extra
|1 132 Using where; Using filesort
|__________________
->Query summary
Time: 0% (12 sec) Amount: 0% (1 queries) Rows Examined/Sent: 0 / 1 Avg. Query Exec/Lock Time: 12 / 5 sec.
Used databases: [shampoo_coppermine]
Query example: use shampoo_coppermine; SELECT cid, name, parent FROM cpg140_categories WHERE cid = '1';
|id rows Extra
|1 1
|__________________
->Query summary
Time: 0% (16 sec) Amount: 0% (1 queries) Rows Examined/Sent: 4 / 0 Avg. Query Exec/Lock Time: 16 / 6 sec.
Used databases: [shampoo_coppermine]
Query example: use shampoo_coppermine; SELECT aid FROM cpg140_albums WHERE visibility != '0' AND visibility !='10000' AND visibility NOT IN (3);
|id rows Extra
|1 4 Using where
|__________________
->Query summary
Time: 0% (17 sec) Amount: 0% (1 queries) Rows Examined/Sent: 17 / 1 Avg. Query Exec/Lock Time: 17 / 6 sec.
Used databases: [shampoo_coppermine]
Query example: use shampoo_coppermine; SELECT * from cpg140_pictures WHERE ((aid='1' ) ) AND approved='YES' AND aid IN (1,2,4,5) ORDER BY filename ASC LIMIT 3 ,1;
|id rows Extra
|1 12 Using where; Using filesort
|__________________


This is what caused the overload on the server.

Fabricio Ferrero

QuoteI know I need to add captcha to my coppermine galleries to stop all the spam
So, search for 'Captcha'. That's the button 'search' meant to be.    
Captcha (Visual Confirmation) for comments/registration/reporting/login/ecard
Read Docs and Search the Forum before posting. - Soporte en español
--*--
Fabricio Ferrero's Website

Catching up! :)

tuxsoul

Hi, may be do like read about cpg-dnsbl (gpl project), to block spam, more info here:
http://forum.coppermine-gallery.net/index.php/topic,50081.new.html

Greeting's  ;).
¿do you like my comment?, gift me one bitcoin: 1266FWznbEW1uLNPsLU9ATBxGuM1U19thB
bitcoin pay forward project: 15pjRCNT2CpzVo7HQ6b6r4q18Vv4Da7y9K