MySqld disabled in systemctl but MySqlClient works

I am in the process of installing lampserver on Fedora 20 apache and php were  straightforward.

MySql is proving more problematic I used yum install mysql-server

Everything went fine and I ended up with Complete!

I then entered service mysqld start

I received a message to copy support-files/mysql.server to the right place for your system

When I tried to find these files I couldn't find them anywhere and I didn't know where to copy them to.

Typing systemctl there is no mention of mysqld at all, but systemctl list-unit-files lists as disabled (in red)

ps -ef grep mysqld gives this output

mysql     5740     1  0 18:48 ?        00:00:00 /bin/sh /usr/bin/mysqld_safe --basedir=/usr
mysql     5922  5740  0 18:48 ?        00:00:08 /usr/libexec/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib64/mysql/plugin --log-error=/var/log/mariadb/mariadb.log --pid-file=/var/run/mariadb/ --socket=/var/lib/mysql/mysql.sock
root      6243  2218  0 20:30 pts/0    00:00:00 grep --color=auto mysqld

All of the references to mysqld are in red

However I can sign into MySql and when I show databases I get
| Database           |
| information_schema |
| mysql              |
| performance_schema |
| test               |
and I can select from tables as well

I would like to start the mysqld service have it running correctly and continue with my development tasks.

If anybody can help I would very much appreciate your effort

Thanks in anticipation of yoour support

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

mysqld_safe is the proper, correct wrapper service. It looks like you're running it correctly.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
johnecollinsAuthor Commented:
Hi Great can I call you that? ;-)

Thank you very much for responding I am new to Linux and I find it hard to comprehend that it can run whilst the monitor says it is disabled.

I have contemplated uninstalling MySql and starting again but I wouldn;t know how to do that.

If you  have any other thoughts I would be pleased to hear you have to say


johnecollinsAuthor Commented:
In the original post there is mention of a log file this is the contents of the log file:-

140103 12:45:48 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140103 12:45:48 InnoDB: The InnoDB memory heap is disabled
140103 12:45:48 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140103 12:45:48 InnoDB: Compressed tables use zlib 1.2.8
140103 12:45:48 InnoDB: Using Linux native AIO
140103 12:45:48 InnoDB: Initializing buffer pool, size = 128.0M
140103 12:45:48 InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
140103 12:45:48  InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
140103 12:45:48  InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
140103 12:45:49  InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: 127 rollback segment(s) active.
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
140103 12:45:50  InnoDB: Waiting for the background threads to start
140103 12:45:51 Percona XtraDB ( 5.5.34-MariaDB-31.1 started; log sequence number 0
140103 12:45:51 [Note] Plugin 'FEEDBACK' is disabled.
140103 12:45:51 [Note] Server socket created on IP: ''.
140103 12:45:51 [Note] Event Scheduler: Loaded 0 events
140103 12:45:51 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.34-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
140103 18:48:36 [Note] /usr/libexec/mysqld: Normal shutdown

140103 18:48:36 [Note] Event Scheduler: Purging the queue. 0 events
140103 18:48:36  InnoDB: Starting shutdown...
140103 18:48:37  InnoDB: Shutdown completed; log sequence number 1597945
140103 18:48:37 [Note] /usr/libexec/mysqld: Shutdown complete

140103 18:48:37 mysqld_safe mysqld from pid file /var/run/mariadb/ ended
140103 18:48:38 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
johnecollinsAuthor Commented:
I have got to the bottom of this after some considerable time, despite running yum install mysql-server,  I have ended up with a maria db.
I am concerned that I followed instructions to get something I know quite well, from use in Windows and got something different.
This is more than a little disconcerting, as I have spent time, trying to figure out what was going on when I do have something that appears to work.

Thanks Jon for your contribution I am grateful that you read it and your comments have helped me to decide what I need to do to achieve progress in my project

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.