mysql vbulletin problems - LOTS !!
edited to add in my server specs (realising not everyone knows it )
Red Hat Linux 6.1/Apache
AMD K6/2 500
384MB ram
10GB EIDE hdd
php 4.02 and mysql 3.22.23 + zend optimiser 0.99
(i think that's right)
30 domains on server (only the vbulletin forum, a perl based links directory, a perl based imagefolio powered gallery site, perl based post cards and before phpads/mysql based)
i'm posting this here in hopes that someone has come across these errors or know of a solution to my problems
i have a dedicated red hat linux 6.1 server with apache on a 384MB , 10GB EIDE server.
here we go, bringing my problems over here
Full story
error 134s
http://vbulletin.com/forum/showthread.php?threadid=3348
mysql appears to have shutdown but hasn't
http://vbulletin.com/forum/showthread.php?threadid=3438
ran out of memory server crash
http://vbulletin.com/forum/showthread.php?threadid=3530
8 crashes/etc in 5 days !
http://vbulletin.com/forum/showthread.php?threadid=3576
I moved my settings down and seemed fine for 24 hrs to
Quote:
# The MySQL server
[mysqld]
port = 3306
socket = /var/lib/mysql/mysql.sock
skip-locking
set-variable = max_connections=100
set-variable = join_buffer=4M
set-variable = key_buffer=16M
set-variable = record_buffer=4M
set-variable = sort_buffer=4M
set-variable = max_allowed_packet=1M
set-variable = thread_stack=128K
set-variable = table_cache=200[mysqldump]
quick
set-variable = max_allowed_packet=16M[mysql]
no-auto-rehash[isamchk]
set-variable = key_buffer=16M
moved apache max connections down from 150 to 100
memory usage (55 - 75%) seemed fine for 4 -24 hrs on mid loads 18 members + 14 guests but i go away for a few hours and the forum doesn't respond and it looks like mysql shutdown but it wasn't a shutdown, so i needed to reboot the server. my hostname.err file didn't reveal anything different
just today added the following indexes with the help of J.Eng
Quote:
### start of indexes ###
alter table forum add index idxhome (active,displayorder,categoryid);alter table forumpermission add index (forumid);
alter table post add index (username);
alter table post add index (userid);alter table session add index (userid);
alter table thread add index idxforumdisplay (forumid,visible);
alter table thread add index (lastpost);#Also, in your custom_avatar table, you've got a duplicate index
#(userid), so let's drop one of them:alter table custom_avatar drop index userid_2;
###end of indexes###
but still the mysql shutdown appearance happened one more time.
i have been reading
http://www.mysql.com/documentation/mysql/bychapter/manual_Problems.html#Problems
http://www.mysql.com/documentation/mysql/bychapter/manual_Problems.html#Crashing
but haven't a clue ?
[Edited by eva2000 on 10-03-2000 at 11:24 AM]
JamesUS posted this at 16:42 — 4th October 2000.
They have: 11 posts
Joined: Jul 2000
Sounds like it might be time to start running your mySL database off a seperate server.
Your webserver doesn't have to be high-specced as it will only be serving up pages. I recommend another server for the actual HTML/PHP pages (can be something pretty slow with minimal RAM)...that would probably help with the problems you are experiencing.
Want to join the discussion? Create an account or log in if you already have one. Joining is fast, free and painless! We’ll even whisk you back here when you’ve finished.