Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am running Mandrake 10.0. I wanted to install the latest version of Mysql so I grab both the client and server RPM's from mysql.com and installed them like the docs say "rpm -i server.rpm" and "rpm -i client".
Here is the problem. As soon as it installed the server the RPM tried to run mysql_install_db to initialize the grant tables and it errored out with
Quote:
"Warning: Asked for 196608 thread stack, but got 126976
040922 22:54:29 /usr/sbin/mysqld: Shutdown Complete
I have no idea what this means other than I can't start the server up. I get this everytime I try and run mysqld or mysqld_safe --user=mysql & or mysql_install_db Doing some internet searches it seems that it might have something to do with the kernal restricting the amount of threads the daemon is requesting. But I have no idea how to alter or fix that.
This is really a bummer as I wanted to get Atomic photo album up and running on my website...
Actually, no, this is the only error on screen that is reported. It simply shuts the server down after this is reported.
I am extremely new to Mysql so I don't know if there are any logs available to look at. I am sure there are, I just don't know how to turn them on or access them...
Why is mysql trying to use the /root directory? Did you provide /root as an option when it was being configured? This is almost certainly where your problem is - mysql shouldn't be running with root permissions, and so it won't have permission to use the /root folder. You should set up (well, the installation should have set up, but never mind that now) a directory under /var for mysql to use for it's data, and make sure the mysql daemon user has full access to it.
Hmm.. Well, all I did was run the "rpm -i xxx.client" and "rpm -i xxx.server" files. I did not add anything to the command lines when they were run. I did run them as root, however if that makes a differences.
Like I said, I followed the instructions exactly as outlined on www.mysql.com.
So what do I do. Do I need to uninstall the rpms and start over??
export TMPDIR=/tmp
Then try and launch mysql again. You may want to make sure that TMPDIR is set to /tmp for the user that launches mysql in future. Or manually set it in the mysql startup script.
I've reported this as a bug. They're probably going to claim it's a feature, but I thought I'd give it a shot anyway cos it wasted an hour of my time. http://bugs.mysql.com/bug.php?id=5822
Make sure you fix the link (in the MySql bug area) you posted that points back to this thread. It seems that the end of the link got cutoff and the numbers "4077" aren't included...
Hmmm, link works for me, but I'm using firefox. Wonder if it's an IE thing. Too lazy to check the HTML source of the board.
Remember that you're using a Gamma release of mysql and not a production release. If there are features you specifically need that the production release doesn't have, then stick with it. I am. Otherwise be aware that you may run into more issues like the above - and when you do be sure to search bugs.mysql.com for help.
Also, that log message of:
Warning: Asked for 196608 thread stack, but got 126976
Has been reported in the bugs database. It's nothing to worry about, but check the bugs if you want to know more.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.