View Full Version : MySQL on FC3 - seems to work now! How?
26th January 2005, 03:00 PM
This worked for me! But don't ask me why or how.
First i used the graphic tool (KDE) to turn off SELinux:
Start/System Settings/Security Level:
Choose the SELinux tab => Click "Enabled" a few times till it gets shaded. Click OK.
Then I rebooted the box!!! This seems to be important!!!
And then, from the prompt, as root:
[root@sesr0001 /]# yum install mysql-server mysql
Setting up Install Process
Setting up Repo: livna-stable
repomd.xml 100% |=========================| 951 B 00:00
.... and so on....
Installed: mysql.i386 0:3.23.58-14 mysql-server.i386 0:3.23.58-14
... and then the final test:
[root@sesr0001 /]# service mysqld restart
Stopping MySQL: [FAILED]
Initializing MySQL database: [ OK ]
Starting MySQL: [ OK ]
And tht's it! - Now I'll start configuring the databases...
Then getting phpMyAdmin and phpNuke to work was a piece og cake....
26th January 2005, 03:06 PM
I'm glad to hear that it was the issue of selinux. The process you did is one way of disabling this service. Congrats on getting it working now. Enjoy the fun in playing with a CMS package now.
31st January 2005, 05:21 AM
Thank you Blixten .. that worked perfectly !! :)
25th February 2005, 09:33 PM
I remember having problems with mysqld too and I followed your advise and it helped! Thanks! But since I'm new. What are the next steps?
1st March 2005, 01:02 PM
Sorry for the delay... I was on vacation skiing :-)
The next steps depends on what you are aiming at... I wanted to test phpNuke... what is your specific objective? I am lazy myself but I have smart friends...
3rd March 2005, 12:44 AM
That command yum install mysql-server mysql is actually amazing. In my case it installed an instance of MySQL server in 5 minutes:
1. Resolved dependencies
2. Downloaded the latest installation.
3. Installed database from scratch.
4. Verified installation.
Once all of that was done (took about 2 minutes), I was able to find mysqld server in Services GUI, and start it with no problem. I verified with telnet locahost 3306 that listener is actually working.
Thanks for the great command and tips.
3rd March 2005, 12:46 AM
Forgot to tell you guys, that SELinux has nothing to do with MySQL. Don't even look into that direction.
17th May 2005, 07:01 PM
Don't you guy's think that SELinux is a rather important part of Fedora security and disabeling it might not be the best move? I've noticed this error after I did "yum update" a month or so ago. It didn't affect the functionality of the previosly installed MySQL 4.1 database. Doing a fresh install on another box that had all updates applied after the build I have experienced the problem where mysqld won't run.
Based on this my conclusion is that one of the recent selinux updates has introduced this problem.
17th May 2005, 07:26 PM
I got a simpler version:
1) Disabel SE Linux
2) Get ALL RPM's off MySQL web site for maximum productivity
3) Delete and then recreate the /var/lib/mysql directory (su, then rm -drf /var/lib/mysql;mkdir /var/lib/mysql) <-- That's the command on 1 line
4) Install the RPMS (rpm -Uhv MySQL*.rpm)
6) Enable SE Linux
17th May 2005, 07:35 PM
Blindly disabling SELinux is a bad idea. SELinux targetted policy is designed to work out of the box in a flexible manner for everyone. If you do have problems, ask in the fedora-selinux list
Red Hat Inc
20th May 2005, 08:31 PM
Look at this post http://forums.fedoraforum.org/showthread.php?p=252668#post252668 where i link to bugtraq where two fully patched redhat clones are cracked. SELINUX prevents attacks through /tmp and /var/tmp (assuming its not turned off!)
You would certainly be the looser for disabling SELINUX!
27th May 2005, 05:24 PM
These guys are right on the SE-Linux thing. Instead of disabling SE Linux, you should put it in Warn mode, install and run your software, then watch your logs for the warnings. Then you can change your SE Linux policies to get rid of the warnings, and then put SE back into active mode.
28th May 2005, 02:06 AM
good stuff guys!!!
vBulletin® v3.8.7, Copyright ©2000-2013, vBulletin Solutions, Inc.