any thoughts or comments about it?

Works good so far. Cpanel is using this version right now

null

Originally posted by null
Works good so far. Cpanel is using this version right now

null

yeah I upgraded it today and it've been running pretty smooth :)

Guess what? If you log on cpanel, go to phpmyadmin, you will see everyone's databases, but you don't have access on them.

This is pretty annoying :) Anyone knows how to fix it?

inteltechs

Guess what, if your client has shell access he will see those databases too :)

I think this can be fixed in phpmyadmin config file

Yes.. itd fixable be in the phpmyadmin file wouldnt it?

humm...what version of Cpanel you guy're using? My still Version 3.23.56 (6.2 E54)

VNPIXEL

Latest stable Cpanel version: Cpanel-6.2.0-STABLE_56-Linux-i686-glibc-2.1

Originally posted by inteltechs
Guess what? If you log on cpanel, go to phpmyadmin, you will see everyone's databases, but you don't have access on them.

This is pretty annoying :) Anyone knows how to fix it?

Hmn.. I think you can go to the phpMyAdmin config.inc.php and change the value of $cfg['Servers'][$i]['auth_type'] to 'http'

Correct me if I am wrong.

yes, you can do that, but user will have to type his login pass again

I'll passed. Wait for them to fix the issue before update it. Thanks for the info guys.

I updated 3 Cpanel 6x version servers tonight to mysql 4, everythings running smooth. Logged into cpanel and yea you can see everyones database's but you cant see the tables or data in it. Plan on fixing this or finding a fix to this tommorrow

Try running

/usr/bin/mysql_fix_privilege_tables

and then restart mysql. That seemed to fix the phpMyAdmin problem for me.

Richard

Thanks, Noldar

Hello,

Run :
/scripts/updatenow
then.
/scripts/fixmysql

Thats whats in WHM. :)

anyone else noticed 9-10 permanent mysql processes running since upgrading to mysql4 ?? what's up with that?

I just noticed that too, hmm wonder why that is. Doesn't seem to be affecting performance though.

mysql 4 works great i noticed a perfromence boost from it and customers are complementing on it. the extra proceeses are not doing anyharm...

Well I've noticed that it's using up a fair bit more memory (29%).

Gonna have to look into this further as I don't see any need for 10 mySQL processes to be running at the same time when they're just basically sleeping and not actually needed.

Originally posted by xAngelx
Well I've noticed that it's using up a fair bit more memory (29%).

Gonna have to look into this further as I don't see any need for 10 mySQL processes to be running at the same time when they're just basically sleeping and not actually needed.

I've noticed this problem too :)

Near as I can figure is it's now sorta cacheing the most popular processes and that's why it's faster. The trade off being higher memory usage.

Still investigating though so not 100%. Gonna wait for most of my clients to go to bed then kill off some of the extra processes and see if it affects anything.

Oh god...mySQL just went ballistic with over 200 zombie processes and had to reboot to clear them out. Something tells me I'm gonna be downgrading to the old mySQL soon :(

You guys might wanna keep an eye on your servers and cPanel (when it starts acting up check ps -aux to see the problem)

Originally posted by xAngelx
Oh god...mySQL just went ballistic with over 200 zombie processes and had to reboot to clear them out. Something tells me I'm gonna be downgrading to the old mySQL soon :(

You guys might wanna keep an eye on your servers and cPanel (when it starts acting up check ps -aux to see the problem)

you might have to tweak your my.cnf configuration :)

According to top, mysql starts with 11 processes; each of it eats 5.4 MB of memory. So it's almost 60 MB (59.4 actually)

That's a lot, but this version seems to be faster. I tested it on 60 MB database with a lot of tables and fields.

I conclusion, I'd say, that memory is nothing comparing to speed.

null

YUP YUP ,,, it sucks too much ram :)...

root@cpanel [/]# ps -aux | grep mysql | wc -l
61

375 mysql 16 0 43728 42M 2220 S 1.7 4.8 0:02 mysqld
4398 mysql 15 0 43728 42M 2220 S 0.8 4.8 0:18 mysqld
4261 mysql 16 0 43820 42M 2220 S 0.7 4.8 0:20 mysqld
375 mysql 15 0 43820 42M 2220 S 0.1 4.8 0:02 mysqld
4393 mysql 15 0 43820 42M 2220 S 0.1 4.8 0:18 mysqld
4590 mysql 16 0 43820 42M 2220 S 0.1 4.8 0:12 mysqld
4588 mysql 15 0 43724 42M 2220 S 0.5 4.8 0:12 mysqld
375 mysql 15 0 43724 42M 2220 S 0.1 4.8 0:02 mysqld
4394 mysql 15 0 43724 42M 2220 S 0.1 4.8 0:12 mysqld
4603 mysql 15 0 43724 42M 2220 S 0.1 4.8 0:21 mysqld
4592 mysql 15 0 43836 42M 2220 S 5.6 4.8 0:15 mysqld
385 mysql 17 0 43836 42M 2220 S 5.2 4.8 0:44 mysqld
4400 mysql 16 0 43836 42M 2220 S 0.9 4.8 0:17 mysqld
4396 mysql 15 0 43836 42M 2220 S 0.7 4.8 0:12 mysqld
4587 mysql 16 0 43836 42M 2220 S 0.7 4.8 0:13 mysqld
4399 mysql 15 0 43836 42M 2220 S 0.5 4.8 0:15 mysqld
4392 mysql 15 0 43836 42M 2220 S 0.1 4.8 0:20 mysqld
4598 mysql 16 0 43740 42M 2220 S 1.3 4.8 0:26 mysqld
4259 mysql 15 0 43740 42M 2220 S 0.5 4.8 0:17 mysqld
362 mysql 15 0 43740 42M 2220 S 0.1 4.8 0:01 mysqld
4596 mysql 15 0 43740 42M 2220 S 0.1 4.8 0:19 mysqld
379 mysql 16 0 43840 42M 2220 S 2.9 4.8 0:25 mysqld
4595 mysql 16 0 43840 42M 2220 S 1.3 4.8 0:13 mysqld
377 mysql 15 0 43840 42M 2220 S 0.5 4.8 0:52 mysqld
384 mysql 15 0 43840 42M 2220 S 0.3 4.8 0:40 mysqld
375 mysql 15 0 43840 42M 2220 S 0.1 4.8 0:02 mysqld
376 mysql 15 0 43840 42M 2220 S 0.1 4.8 0:36 mysqld
4259 mysql 15 0 43840 42M 2220 S 0.1 4.8 0:17 mysqld
4184 mysql 15 0 43744 42M 2220 S 0.1 4.8 0:14 mysqld
4597 mysql 15 0 43744 42M 2220 S 0.1 4.8 0:10 mysqld
4600 mysql 15 0 43840 42M 2220 S 1.1 4.8 0:16 mysqld
4397 mysql 15 0 43840 42M 2220 S 0.5 4.8 0:12 mysqld
4264 mysql 15 0 43860 42M 2220 S 6.8 4.8 0:23 mysqld
4398 mysql 15 0 43860 42M 2220 S 0.1 4.8 0:18 mysqld
4590 mysql 16 0 43876 42M 2220 S 0.9 4.8 0:12 mysqld
4204 mysql 16 0 43876 42M 2220 S 0.5 4.8 0:17 mysqld
4393 mysql 15 0 43876 42M 2220 S 0.5 4.8 0:18 mysqld
380 mysql 16 0 43876 42M 2220 S 0.3 4.8 0:47 mysqld
375 mysql 15 0 43876 42M 2220 S 0.1 4.8 0:02 mysqld
4126 mysql 16 0 43876 42M 2220 S 3.1 4.8 0:18 mysqld
4588 mysql 16 0 43876 42M 2220 S 2.1 4.8 0:12 mysqld
383 mysql 15 0 43876 42M 2220 S 1.1 4.8 0:24 mysqld
4260 mysql 15 0 43876 42M 2220 S 0.3 4.8 0:15 mysqld
373 mysql 15 0 43876 42M 2220 S 0.1 4.8 0:00 mysqld
375 mysql 15 0 43876 42M 2220 S 0.1 4.8 0:02 mysqld
4261 mysql 15 0 43876 42M 2220 S 0.1 4.8 0:20 mysqld
4205 mysql 15 0 43876 42M 2220 S 0.3 4.8 0:15 mysqld
375 mysql 15 0 43876 42M 2220 S 0.1 4.8 0:02 mysqld

Inteltechs....tweak my.cnf how? I already have a max connections set up of 500 and the actual connections has never gone over 50 at one time, usually it's less than 10.

xAngelx, yours eats 30 MB :eek: Show us your mysql processes

inteltechs, I see your mysql is a little busy ;)

Sorry meant 30% and atm there aren't actually any mySQL processes being used. Just the pid's running in ps -aux.

You like me :love::stickout:?

Aww we all like you, but we're still trying to figure out that dang fork fork thing. Sheesh, it'd be easier to figure out how they get the caramilk into a caramilk bar :P

OK pretty much all of my clients will be going to bed in an hour or two. Then it's time to go Rambo on the SQL and kill -9 em (I'll try a straight kill first :P). Then I'll see what hell breaks loose and decide if I really want that many SQL servers just sitting around sucking up my ram. It's not hurting anything atm but it still makes me nervous.

No idea why SQL went haywire earlier, although that might have been an attempted hack since I kicked off a clients subdomain customer for some less than honourable actions this morning. Then again it could've just been junk left over from the upgrade (although I did restart mySQL, apache etc.

I'll report later on how things go.

Wasn't happy with the upgrade. So many things affected. Feel like strangling someone.

Originally posted by sprintserve
Wasn't happy with the upgrade. So many things affected. Feel like strangling someone.

I am not happy too but it is running okay on my servers eventually :)

Well like I said guys, keep an eye on your servers. Mine appeared to be running perfectly till a client emailed my support dept to ask why he couldn't access his cpanel and that when I found mySQL going nuts.

Originally posted by xAngelx
Well like I said guys, keep an eye on your servers. Mine appeared to be running perfectly till a client emailed my support dept to ask why he couldn't access his cpanel and that when I found mySQL going nuts.

I've been watching 3 of them here... so far .. just one of them went nut last night :( but I've got it under control.

Well only 1 of mine has the new update, and it was ok for around 10 hours before it went schizo on me and I had to reboot.

Thank god I have 24/7 staff lol, otherwise I'd be staying up all night to babysit it :P

I only upgraded one server where we've been having mysql issues for 2 weeks now...I figured I didn't have anything to lose.

Now it's running perfectly, better than it has in a long time. :)

But I certainly didn't like the resource usage ... it uses 30% of the memory doing nothing. Luckily all our servers are due for an upgrade tommorrow to 2GB :)

Originally posted by null
According to top, mysql starts with 11 processes; each of it eats 5.4 MB of memory. So it's almost 60 MB (59.4 actually)

That's a lot, but this version seems to be faster. I tested it on 60 MB database with a lot of tables and fields.

I conclusion, I'd say, that memory is nothing comparing to speed.

null

No, your mysql is not using that much memory. Those processes are threads, I believe almost all of the memory shown on top are shared among threaded process. So in your case I think mysql doesn't use more than 10 MB of actual memory. I think this will be different under RedHat 9 where a threaded application will show as one process. CMIIW

Well mine definately are using just over 31% of the ram now, used to only be 2%.

mySQL peeps claim it's "normal" and have no idea why SQL went nuts with all the zombie processes.

Gonna keep watching it.