동호회사이트를 하나 구축하고 새롭게 2008년에 리뉴얼을 하면서
개발자가 그누보드가 좋다고 하여 그누보드를 이용한 동호회사이트를 만들게되었습니다.
제로보드에서 그누보드로 옮기게 된...

이후 빈번하게 속도문제가 발생하여 올해까지 3년째 문제가 발생하여
그동안 서버도 옮겨보고 DB서버도 따로 비용들여서 해보고 하였는데
도저히 해결이 되지 않습니다. 동호회특성상 여름이면 폭주하는 시기인데 요즘 더더욱 사이트가 느려서 문제가 이만저만이 아닙니다.

그동안 안해본 방법이 없을정도인데.. 그누보드 담당자로서 정답은 아니더라도 그나마 제시해줄수 잇는 해답이 있으신지요???

부탁드리겠습니다.

빈번히 발생하는 속도느림 - 결국 뜨는 에러 (아래)

select * from g4_config

1046 : No database selected

error file : /index.html


****************************************************************


select bo_skin from g4_board where bo_table = 'Menu01Top1'

1040 : Too many connections

error file : /bbs/board.php

****************************************************************

2010 3 21 11:54
FTP도 느림(업로드시 불안정,빠를때 빠르고 느릴때느리고)

****************************************************************

dossa.kr 접속시 느리다가 에러나는게아니고 바로 에러남.

select * from g4_config

2002 : Can't connect to local MySQL server through socket '/tmp/mysql.sock' (11)

error file : /index.html


******************************************************************

select bo_table, bo_subject from g4_board where bo_table in () order by bo_table
1064 : You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') order by bo_table' at line 2
error file : /2010_3_1.html

--------------------------------------------------------------------------------------------------------------

select * from g4_config
2002 : Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)
error file : /index.html

--------------------------------------------------------------------------------------------------------------

1.Server timed out and closed the connection. How to fix: check that wait_timeout variable in your mysqld’s my.cnf configuration file is large enough. On Debian: sudo nano /etc/mysql/my.cnf, set wait_timeout to at least 600 seconds (you can tweak/decrease this value when error 2006 is gone), then sudo /etc/init.d/mysql restart. I didn’t check, but the default value for wait_timeout might be around 28800 seconds (8 hours).
2.Server dropped an incorrect or too large packet. If mysqld gets a packet that is too large or incorrect, it assumes that something has gone wrong with the client and closes the connection. You can increase the maximal packet size limit by increasing the value of max_allowed_packet in my.cnf file. On Debian: sudo nano /etc/mysql/my.cnf, set max_allowed_packet to to something like 64M (you can tweak/decrease this value when error 2006 is gone), then sudo /etc/init.d/mysql restart.

--------------------------------------------------------------------------------------------------------------

select * from g4_config
1046 : No database selected
error file : /index.html

--------------------------------------------------------------------------------------------------------------

select * from g4_config
2002 : Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)
error file : /index.html

--------------------------------------------------------------------------------------------------------------

select wr_id,wr_subject,wr_comment,wr_content from g4_write_Menu18Top2 where wr_is_comment = 0 order by wr_is_comment desc , wr_hit desc, wr_id desc limit 1
1028 : Sort aborted
error file : /index.html

--------------------------------------------------------------------------------------------------------------

select * from g4_config
2002 : Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)
error file : /index.html

--------------------------------------------------------------------------------------------------------------

.Server timed out and closed the connection. How to fix: check that wait_timeout variable in your mysqld’s my.cnf configuration file is large enough. On Debian: sudo nano /etc/mysql/my.cnf, set wait_timeout to at least 600 seconds (you can tweak/decrease this value when error 2006 is gone), then sudo /etc/init.d/mysql restart. I didn’t check, but the default value for wait_timeout might be around 28800 seconds (8 hours).
2.Server dropped an incorrect or too large packet. If mysqld gets a packet that is too large or incorrect, it assumes that something has gone wrong with the client and closes the connection. You can increase the maximal packet size limit by increasing the value of max_allowed_packet in my.cnf file. On Debian: sudo nano /etc/mysql/my.cnf, set max_allowed_packet to to something like 64M (you can tweak/decrease this value when error 2006 is gone), then sudo /etc/init.d/mysql restart.

--------------------------------------------------------------------------------------------------------------

select * from g4_config
1046 : No database selected
error file : /index.html

--------------------------------------------------------------------------------------------------------------

select bo_skin from g4_board where bo_table = 'Menu01Top1'
1040 : Too many connections
error file : /bbs/board.php