Mysql Acting Up...

2025-04-18

Hey,

I'm in the process of moving into a new server... and am having a problem that has so far been unsolved...

I'm on a dedicated server withL Cent OS, 3.0 ghz, 2 gigs of Ram, 2 80 gig SATA HDs... w/ Cpanel/WHM...

I run a poll software, phpQJr, that has never cause me any trouble, but is causing a lot now... Everytime someone submits a vote, the process takes 99.9% of the CPU for a few seconds... (3-5)... then settles down...

Since the polls area is popular, its bogging down the server during these times...

I'm a near newbie with Server Administration, but have a decent grip on the basics...

Doing my homework on this board and others, I've tried to get all the info together...

errors in one of hte processes that keeps hitting 99.9% CPU
In the trace process area of WHM:
sched_setscheduler(1867, SCHED_OTHER, { 6 }) = -1 EINVAL (Invalid argument)
write(46, "\1\0\0\1\2\35\0\0\2\fphpQJr_BLOCK\5ip_id\3\n\0\0"..., 86) = 86
sched_setscheduler(1867, SCHED_OTHER, { 8 }) = -1 EINVAL (Invalid argument)
time([1136288343]) = 1136288343
read(46, "G\0\0\0", 4) = 4
read(46, "\3SELECT * FROM phpQJr_QUESTION W"..., 71) = 71
time([1136288343]) = 1136288343
sched_setscheduler(1867, SCHED_OTHER, { 6 }) = -1 EINVAL (Invalid argument)
write(46, "\1\0\0\1\v\"\0\0\2\17phpQJr_QUESTION\7poll_i"..., 560) = 560
sched_setscheduler(1867, SCHED_OTHER, { 8 }) = -1 EINVAL (Invalid argument)

My first guess on the next piece is that it may have to do with the apache error _log that is growing quickly right now... (in a worst case sceneriao move at the moment...)

root@aphrodite [/var/log]# cat boot.log.1
Jan 2 15:58:52 178 filelimits: Increasing file system limits succeeded
Jan 2 18:53:37 178 filelimits: Increasing file system limits succeeded
Jan 3 03:02:20 178 filelimits: Increasing file system limits succeeded
Jan 3 03:04:01 178 filelimits: Increasing file system limits succeeded
Jan 3 03:17:41 178 filelimits: Increasing file system limits succeeded

Mentioned in the previous post, the thread stack error...

root@aphrodite [/var/log]# cat mysqld.log
060102 22:48:37 mysqld started
060102 22:48:37 Warning: Asked for 196608 thread stack, but got 126976
/usr/sbin/mysqld: ready for connections.
Version: '4.0.25-standard' socket: '/var/lib/mysql/mysql.sock' port: 3306 Official MySQL RPM

Really got no clue on this one, but the file size of 0 caught my attention...

root@aphrodite [/var/lib/mysql]# ls -l mysql.sock
srwxrwxrwx 1 mysql mysql 0 Jan 2 22:48 mysql.sock=

root@aphrodite [/var/log]# cat /etc/my.cnf

[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
skip-locking
skip-innodb
query_cache_limit=1M
query_cache_size=32M
query_cache_type=1
max_user_connections=25
max_connections=500
interactive_timeout=10
wait_timeout=10
connect_timeout=10
thread_cache_size=128
key_buffer=16M
join_buffer=1M
max_allowed_packet=16M
table_cache=1024
record_buffer=1M
sort_buffer_size=2M
read_buffer_size=2M
max_connect_errors=10
# Try number of CPU's*2 for thread_concurrency
thread_concurrency=8
myisam_sort_buffer_size=64M
#log-bin
server-id=1

[mysql.server]
user=mysql
basedir=/var/lib

[safe_mysqld]
err-log=/var/log/mysqld.log
pid-file=/var/lib/mysql/mysql.pid
open_files_limit=8192

[mysqldump]
quick
max_allowed_packet=16M

[mysql]
no-auto-rehash
#safe-updates

[isamchk]
key_buffer=64M
sort_buffer=64M
read_buffer=16M
write_buffer=16M

[myisamchk]
key_buffer=64M
sort_buffer=64M
read_buffer=16M
write_buffer=16M

[mysqlhotcopy]
interactive-timeout

Thanks in advance... and hope everyone's 2006 is off to a great start.