Failed Starting mysqld on centOS 6mysqld_safe version different than mysqld?mysqld dead but subsys...

How should I state my MS degree in my CV when it was in practice a joint-program?

How to mitigate "bandwagon attacking" from players?

Activating a Alphanet Faucet Wallet Remotely (without tezos-client)

Incompressible fluid definition

What is Crew Dragon approaching in this picture?

4 Spheres all touching each other??

Getting a matrix of complex values from associations giving the real and imaginary parts of each element?

Does this pattern of summing polygonal numbers to get a square repeat indefinitely?

How to acknowledge an embarrassing job interview, now that I work directly with the interviewer?

Dilemma of explaining to interviewer that he is the reason for declining second interview

If all harmonics are generated by plucking, how does a guitar string produce a pure frequency sound?

What happens if a wizard reaches level 20 but has no 3rd-level spells that they can use with the Signature Spells feature?

Does Windows 10's telemetry include sending *.doc files if Word crashed?

Quenching swords in dragon blood; why?

Word to be used for "standing with your toes pointing out"

ip vs ifconfig commands pros and cons

Wanted: 5.25 floppy to usb adapter

What is the meaning of "pick up" in this sentence?

Can a person refuse a presidential pardon?

Finding the number of integers that are a square and a cube at the same time

Linux File Manager: Restore previous open session (folders and tab)

Am I using the wrong word all along?

Can I become debt free or should I file for bankruptcy? How do I manage my debt and finances?

What is the purpose of easy combat scenarios that don't need resource expenditure?



Failed Starting mysqld on centOS 6


mysqld_safe version different than mysqld?mysqld dead but subsys locked/usr/sbin/mysqld was deleted and replaced by another mysqld with different inodemysqld can't start without any infoError starting MongoDB on CentOSMAMP Pro - MySQL not startingmysqld not starting upPostgreSQL service start failed on CentOS 7Determine cause of failed MariaDB start on CentOS 7Mysqld process not showing all options on command line in CentOs 7













0
















I'm a newbie in Linux. I try to install and run MySQL but when I start
it it's got failed and this is my logs :



180426 18:01:03 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
180426 18:01:03 InnoDB: Initializing buffer pool, size = 8.0M
180426 18:01:03 InnoDB: Completed initialization of buffer pool
180426 18:01:03 InnoDB: Started; log sequence number 0 44233
180426 18:01:03 [ERROR] /usr/libexec/mysqld: unknown option '--Disabling symbolic-links is recommended to prevent assor$
180426 18:01:03 [ERROR] Aborting

180426 18:01:03 InnoDB: Starting shutdown...
180426 18:01:09 InnoDB: Shutdown completed; log sequence number 0 44233
180426 18:01:09 [Note] /usr/libexec/mysqld: Shutdown complete


What can I do?




I fix above problem But now I got this errors in Log:



2018-04-27T15:51:27.825000Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-04-27T15:51:27.827374Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.22) starting as process 9669 ...
2018-04-27T15:51:27.984517Z 0 [Note] InnoDB: PUNCH HOLE support available
2018-04-27T15:51:27.984546Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-04-27T15:51:27.984555Z 0 [Note] InnoDB: Uses event mutexes
2018-04-27T15:51:27.984563Z 0 [Note] InnoDB: GCC builtin __sync_synchronize() is used for memory barrier
2018-04-27T15:51:27.984570Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-04-27T15:51:27.984578Z 0 [Note] InnoDB: Using Linux native AIO
2018-04-27T15:51:27.984900Z 0 [Note] InnoDB: Number of pools: 1
2018-04-27T15:51:27.985021Z 0 [Note] InnoDB: Using CPU crc32 instructions
2018-04-27T15:51:27.987684Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2018-04-27T15:51:27.997035Z 0 [Note] InnoDB: Completed initialization of buffer pool
2018-04-27T15:51:28.001190Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2018-04-27T15:51:28.011286Z 0 [ERROR] InnoDB: The Auto-extending innodb_system data file './ibdata1' is of a different size 640 pages (rounded down to MB) than specified in the .cnf file: initial 768 pages, max 0 (relevant if non-zero) pages!

2018-04-27T15:51:28.011335Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2018-04-27T15:51:28.612062Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2018-04-27T15:51:28.612135Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2018-04-27T15:51:28.612175Z 0 [ERROR] Failed to initialize builtin plugins.
2018-04-27T15:51:28.612190Z 0 [ERROR] Aborting


NEW EDIT



[root@static ~]# sudo service mysqld start
Initializing MySQL database: [FAILED]


and /etc/my.cnf content :



# For advice on how to change settings please see
# http://dev.mysql.com/doc/refman/5.7/en/server-configuration-defaults.html

[mysqld]
#
# Remove leading # and set to the amount of RAM for the most important data
# cache in MySQL. Start at 70% of total RAM for dedicated server, else 10%.
# innodb_buffer_pool_size = 128M
#
# Remove leading # to turn on a very important data integrity option: logging
# changes to the binary log between backups.
# log_bin
#
# Remove leading # to set options mainly useful for reporting servers.
# The server defaults are faster for transactions and fast SELECTs.
# Adjust sizes as needed, experiment to find the optimal values.
# join_buffer_size = 128M
# sort_buffer_size = 2M
# read_rnd_buffer_size = 2M
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock

# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0

log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
explicit_defaults_for_timestamp=1
innodb_force_recovery=1









share|improve this question
















bumped to the homepage by Community 10 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • Look at the first entry in the log - [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more!

    – Vérace
    Apr 27 '18 at 21:31











  • @Vérace I do it but this still not working!

    – M.D
    Apr 27 '18 at 21:49











  • What's your first warning now then?

    – Vérace
    Apr 27 '18 at 22:01











  • @Vérace| [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option

    – M.D
    Apr 28 '18 at 10:11











  • @Vérace I add new Edition

    – M.D
    Apr 28 '18 at 10:15
















0
















I'm a newbie in Linux. I try to install and run MySQL but when I start
it it's got failed and this is my logs :



180426 18:01:03 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
180426 18:01:03 InnoDB: Initializing buffer pool, size = 8.0M
180426 18:01:03 InnoDB: Completed initialization of buffer pool
180426 18:01:03 InnoDB: Started; log sequence number 0 44233
180426 18:01:03 [ERROR] /usr/libexec/mysqld: unknown option '--Disabling symbolic-links is recommended to prevent assor$
180426 18:01:03 [ERROR] Aborting

180426 18:01:03 InnoDB: Starting shutdown...
180426 18:01:09 InnoDB: Shutdown completed; log sequence number 0 44233
180426 18:01:09 [Note] /usr/libexec/mysqld: Shutdown complete


What can I do?




I fix above problem But now I got this errors in Log:



2018-04-27T15:51:27.825000Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-04-27T15:51:27.827374Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.22) starting as process 9669 ...
2018-04-27T15:51:27.984517Z 0 [Note] InnoDB: PUNCH HOLE support available
2018-04-27T15:51:27.984546Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-04-27T15:51:27.984555Z 0 [Note] InnoDB: Uses event mutexes
2018-04-27T15:51:27.984563Z 0 [Note] InnoDB: GCC builtin __sync_synchronize() is used for memory barrier
2018-04-27T15:51:27.984570Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-04-27T15:51:27.984578Z 0 [Note] InnoDB: Using Linux native AIO
2018-04-27T15:51:27.984900Z 0 [Note] InnoDB: Number of pools: 1
2018-04-27T15:51:27.985021Z 0 [Note] InnoDB: Using CPU crc32 instructions
2018-04-27T15:51:27.987684Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2018-04-27T15:51:27.997035Z 0 [Note] InnoDB: Completed initialization of buffer pool
2018-04-27T15:51:28.001190Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2018-04-27T15:51:28.011286Z 0 [ERROR] InnoDB: The Auto-extending innodb_system data file './ibdata1' is of a different size 640 pages (rounded down to MB) than specified in the .cnf file: initial 768 pages, max 0 (relevant if non-zero) pages!

2018-04-27T15:51:28.011335Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2018-04-27T15:51:28.612062Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2018-04-27T15:51:28.612135Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2018-04-27T15:51:28.612175Z 0 [ERROR] Failed to initialize builtin plugins.
2018-04-27T15:51:28.612190Z 0 [ERROR] Aborting


NEW EDIT



[root@static ~]# sudo service mysqld start
Initializing MySQL database: [FAILED]


and /etc/my.cnf content :



# For advice on how to change settings please see
# http://dev.mysql.com/doc/refman/5.7/en/server-configuration-defaults.html

[mysqld]
#
# Remove leading # and set to the amount of RAM for the most important data
# cache in MySQL. Start at 70% of total RAM for dedicated server, else 10%.
# innodb_buffer_pool_size = 128M
#
# Remove leading # to turn on a very important data integrity option: logging
# changes to the binary log between backups.
# log_bin
#
# Remove leading # to set options mainly useful for reporting servers.
# The server defaults are faster for transactions and fast SELECTs.
# Adjust sizes as needed, experiment to find the optimal values.
# join_buffer_size = 128M
# sort_buffer_size = 2M
# read_rnd_buffer_size = 2M
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock

# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0

log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
explicit_defaults_for_timestamp=1
innodb_force_recovery=1









share|improve this question
















bumped to the homepage by Community 10 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • Look at the first entry in the log - [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more!

    – Vérace
    Apr 27 '18 at 21:31











  • @Vérace I do it but this still not working!

    – M.D
    Apr 27 '18 at 21:49











  • What's your first warning now then?

    – Vérace
    Apr 27 '18 at 22:01











  • @Vérace| [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option

    – M.D
    Apr 28 '18 at 10:11











  • @Vérace I add new Edition

    – M.D
    Apr 28 '18 at 10:15














0












0








0









I'm a newbie in Linux. I try to install and run MySQL but when I start
it it's got failed and this is my logs :



180426 18:01:03 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
180426 18:01:03 InnoDB: Initializing buffer pool, size = 8.0M
180426 18:01:03 InnoDB: Completed initialization of buffer pool
180426 18:01:03 InnoDB: Started; log sequence number 0 44233
180426 18:01:03 [ERROR] /usr/libexec/mysqld: unknown option '--Disabling symbolic-links is recommended to prevent assor$
180426 18:01:03 [ERROR] Aborting

180426 18:01:03 InnoDB: Starting shutdown...
180426 18:01:09 InnoDB: Shutdown completed; log sequence number 0 44233
180426 18:01:09 [Note] /usr/libexec/mysqld: Shutdown complete


What can I do?




I fix above problem But now I got this errors in Log:



2018-04-27T15:51:27.825000Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-04-27T15:51:27.827374Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.22) starting as process 9669 ...
2018-04-27T15:51:27.984517Z 0 [Note] InnoDB: PUNCH HOLE support available
2018-04-27T15:51:27.984546Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-04-27T15:51:27.984555Z 0 [Note] InnoDB: Uses event mutexes
2018-04-27T15:51:27.984563Z 0 [Note] InnoDB: GCC builtin __sync_synchronize() is used for memory barrier
2018-04-27T15:51:27.984570Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-04-27T15:51:27.984578Z 0 [Note] InnoDB: Using Linux native AIO
2018-04-27T15:51:27.984900Z 0 [Note] InnoDB: Number of pools: 1
2018-04-27T15:51:27.985021Z 0 [Note] InnoDB: Using CPU crc32 instructions
2018-04-27T15:51:27.987684Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2018-04-27T15:51:27.997035Z 0 [Note] InnoDB: Completed initialization of buffer pool
2018-04-27T15:51:28.001190Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2018-04-27T15:51:28.011286Z 0 [ERROR] InnoDB: The Auto-extending innodb_system data file './ibdata1' is of a different size 640 pages (rounded down to MB) than specified in the .cnf file: initial 768 pages, max 0 (relevant if non-zero) pages!

2018-04-27T15:51:28.011335Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2018-04-27T15:51:28.612062Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2018-04-27T15:51:28.612135Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2018-04-27T15:51:28.612175Z 0 [ERROR] Failed to initialize builtin plugins.
2018-04-27T15:51:28.612190Z 0 [ERROR] Aborting


NEW EDIT



[root@static ~]# sudo service mysqld start
Initializing MySQL database: [FAILED]


and /etc/my.cnf content :



# For advice on how to change settings please see
# http://dev.mysql.com/doc/refman/5.7/en/server-configuration-defaults.html

[mysqld]
#
# Remove leading # and set to the amount of RAM for the most important data
# cache in MySQL. Start at 70% of total RAM for dedicated server, else 10%.
# innodb_buffer_pool_size = 128M
#
# Remove leading # to turn on a very important data integrity option: logging
# changes to the binary log between backups.
# log_bin
#
# Remove leading # to set options mainly useful for reporting servers.
# The server defaults are faster for transactions and fast SELECTs.
# Adjust sizes as needed, experiment to find the optimal values.
# join_buffer_size = 128M
# sort_buffer_size = 2M
# read_rnd_buffer_size = 2M
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock

# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0

log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
explicit_defaults_for_timestamp=1
innodb_force_recovery=1









share|improve this question

















I'm a newbie in Linux. I try to install and run MySQL but when I start
it it's got failed and this is my logs :



180426 18:01:03 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
180426 18:01:03 InnoDB: Initializing buffer pool, size = 8.0M
180426 18:01:03 InnoDB: Completed initialization of buffer pool
180426 18:01:03 InnoDB: Started; log sequence number 0 44233
180426 18:01:03 [ERROR] /usr/libexec/mysqld: unknown option '--Disabling symbolic-links is recommended to prevent assor$
180426 18:01:03 [ERROR] Aborting

180426 18:01:03 InnoDB: Starting shutdown...
180426 18:01:09 InnoDB: Shutdown completed; log sequence number 0 44233
180426 18:01:09 [Note] /usr/libexec/mysqld: Shutdown complete


What can I do?




I fix above problem But now I got this errors in Log:



2018-04-27T15:51:27.825000Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-04-27T15:51:27.827374Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.22) starting as process 9669 ...
2018-04-27T15:51:27.984517Z 0 [Note] InnoDB: PUNCH HOLE support available
2018-04-27T15:51:27.984546Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-04-27T15:51:27.984555Z 0 [Note] InnoDB: Uses event mutexes
2018-04-27T15:51:27.984563Z 0 [Note] InnoDB: GCC builtin __sync_synchronize() is used for memory barrier
2018-04-27T15:51:27.984570Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-04-27T15:51:27.984578Z 0 [Note] InnoDB: Using Linux native AIO
2018-04-27T15:51:27.984900Z 0 [Note] InnoDB: Number of pools: 1
2018-04-27T15:51:27.985021Z 0 [Note] InnoDB: Using CPU crc32 instructions
2018-04-27T15:51:27.987684Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2018-04-27T15:51:27.997035Z 0 [Note] InnoDB: Completed initialization of buffer pool
2018-04-27T15:51:28.001190Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2018-04-27T15:51:28.011286Z 0 [ERROR] InnoDB: The Auto-extending innodb_system data file './ibdata1' is of a different size 640 pages (rounded down to MB) than specified in the .cnf file: initial 768 pages, max 0 (relevant if non-zero) pages!

2018-04-27T15:51:28.011335Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2018-04-27T15:51:28.612062Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2018-04-27T15:51:28.612135Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2018-04-27T15:51:28.612175Z 0 [ERROR] Failed to initialize builtin plugins.
2018-04-27T15:51:28.612190Z 0 [ERROR] Aborting


NEW EDIT



[root@static ~]# sudo service mysqld start
Initializing MySQL database: [FAILED]


and /etc/my.cnf content :



# For advice on how to change settings please see
# http://dev.mysql.com/doc/refman/5.7/en/server-configuration-defaults.html

[mysqld]
#
# Remove leading # and set to the amount of RAM for the most important data
# cache in MySQL. Start at 70% of total RAM for dedicated server, else 10%.
# innodb_buffer_pool_size = 128M
#
# Remove leading # to turn on a very important data integrity option: logging
# changes to the binary log between backups.
# log_bin
#
# Remove leading # to set options mainly useful for reporting servers.
# The server defaults are faster for transactions and fast SELECTs.
# Adjust sizes as needed, experiment to find the optimal values.
# join_buffer_size = 128M
# sort_buffer_size = 2M
# read_rnd_buffer_size = 2M
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock

# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0

log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
explicit_defaults_for_timestamp=1
innodb_force_recovery=1






centos mysqld






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Apr 28 '18 at 10:15







M.D

















asked Apr 27 '18 at 15:15









M.DM.D

11




11





bumped to the homepage by Community 10 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 10 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • Look at the first entry in the log - [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more!

    – Vérace
    Apr 27 '18 at 21:31











  • @Vérace I do it but this still not working!

    – M.D
    Apr 27 '18 at 21:49











  • What's your first warning now then?

    – Vérace
    Apr 27 '18 at 22:01











  • @Vérace| [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option

    – M.D
    Apr 28 '18 at 10:11











  • @Vérace I add new Edition

    – M.D
    Apr 28 '18 at 10:15



















  • Look at the first entry in the log - [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more!

    – Vérace
    Apr 27 '18 at 21:31











  • @Vérace I do it but this still not working!

    – M.D
    Apr 27 '18 at 21:49











  • What's your first warning now then?

    – Vérace
    Apr 27 '18 at 22:01











  • @Vérace| [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option

    – M.D
    Apr 28 '18 at 10:11











  • @Vérace I add new Edition

    – M.D
    Apr 28 '18 at 10:15

















Look at the first entry in the log - [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more!

– Vérace
Apr 27 '18 at 21:31





Look at the first entry in the log - [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more!

– Vérace
Apr 27 '18 at 21:31













@Vérace I do it but this still not working!

– M.D
Apr 27 '18 at 21:49





@Vérace I do it but this still not working!

– M.D
Apr 27 '18 at 21:49













What's your first warning now then?

– Vérace
Apr 27 '18 at 22:01





What's your first warning now then?

– Vérace
Apr 27 '18 at 22:01













@Vérace| [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option

– M.D
Apr 28 '18 at 10:11





@Vérace| [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option

– M.D
Apr 28 '18 at 10:11













@Vérace I add new Edition

– M.D
Apr 28 '18 at 10:15





@Vérace I add new Edition

– M.D
Apr 28 '18 at 10:15










2 Answers
2






active

oldest

votes


















0














Looks like maybe a comment in one of the option files (such as /etc/my.cnf and any .cnf file included from that file) has become un-commented. Search through these files for "Disabling symbolic-links is recommended" and make sure there is a comment character (i.e. '#') in front of it, then save the file and try starting mysqld again.






share|improve this answer
























  • i fixed this I have another problem

    – M.D
    Apr 27 '18 at 18:17





















0














I change /etc/ directory permission to 650 and MySQL run successfully.
it's doesn't run cuz the MySQL can't read and write in my.cnf file.






share|improve this answer
























  • MySQL doesn't write to its option files. You changed the whole /etc/ directory? 650 is "rw-r-x---" ... I'd suggest instead chmod 664 /etc/my.cnf and chown root:root /etc/my.cnf which are standard MySQL ownership and permissions.

    – dbdemon
    Apr 28 '18 at 11:33











  • I used chmod 650 /etc/

    – M.D
    Apr 28 '18 at 15:02













Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f205180%2ffailed-starting-mysqld-on-centos-6%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














Looks like maybe a comment in one of the option files (such as /etc/my.cnf and any .cnf file included from that file) has become un-commented. Search through these files for "Disabling symbolic-links is recommended" and make sure there is a comment character (i.e. '#') in front of it, then save the file and try starting mysqld again.






share|improve this answer
























  • i fixed this I have another problem

    – M.D
    Apr 27 '18 at 18:17


















0














Looks like maybe a comment in one of the option files (such as /etc/my.cnf and any .cnf file included from that file) has become un-commented. Search through these files for "Disabling symbolic-links is recommended" and make sure there is a comment character (i.e. '#') in front of it, then save the file and try starting mysqld again.






share|improve this answer
























  • i fixed this I have another problem

    – M.D
    Apr 27 '18 at 18:17
















0












0








0







Looks like maybe a comment in one of the option files (such as /etc/my.cnf and any .cnf file included from that file) has become un-commented. Search through these files for "Disabling symbolic-links is recommended" and make sure there is a comment character (i.e. '#') in front of it, then save the file and try starting mysqld again.






share|improve this answer













Looks like maybe a comment in one of the option files (such as /etc/my.cnf and any .cnf file included from that file) has become un-commented. Search through these files for "Disabling symbolic-links is recommended" and make sure there is a comment character (i.e. '#') in front of it, then save the file and try starting mysqld again.







share|improve this answer












share|improve this answer



share|improve this answer










answered Apr 27 '18 at 16:00









dbdemondbdemon

3,0872625




3,0872625













  • i fixed this I have another problem

    – M.D
    Apr 27 '18 at 18:17





















  • i fixed this I have another problem

    – M.D
    Apr 27 '18 at 18:17



















i fixed this I have another problem

– M.D
Apr 27 '18 at 18:17







i fixed this I have another problem

– M.D
Apr 27 '18 at 18:17















0














I change /etc/ directory permission to 650 and MySQL run successfully.
it's doesn't run cuz the MySQL can't read and write in my.cnf file.






share|improve this answer
























  • MySQL doesn't write to its option files. You changed the whole /etc/ directory? 650 is "rw-r-x---" ... I'd suggest instead chmod 664 /etc/my.cnf and chown root:root /etc/my.cnf which are standard MySQL ownership and permissions.

    – dbdemon
    Apr 28 '18 at 11:33











  • I used chmod 650 /etc/

    – M.D
    Apr 28 '18 at 15:02


















0














I change /etc/ directory permission to 650 and MySQL run successfully.
it's doesn't run cuz the MySQL can't read and write in my.cnf file.






share|improve this answer
























  • MySQL doesn't write to its option files. You changed the whole /etc/ directory? 650 is "rw-r-x---" ... I'd suggest instead chmod 664 /etc/my.cnf and chown root:root /etc/my.cnf which are standard MySQL ownership and permissions.

    – dbdemon
    Apr 28 '18 at 11:33











  • I used chmod 650 /etc/

    – M.D
    Apr 28 '18 at 15:02
















0












0








0







I change /etc/ directory permission to 650 and MySQL run successfully.
it's doesn't run cuz the MySQL can't read and write in my.cnf file.






share|improve this answer













I change /etc/ directory permission to 650 and MySQL run successfully.
it's doesn't run cuz the MySQL can't read and write in my.cnf file.







share|improve this answer












share|improve this answer



share|improve this answer










answered Apr 28 '18 at 10:21









M.DM.D

11




11













  • MySQL doesn't write to its option files. You changed the whole /etc/ directory? 650 is "rw-r-x---" ... I'd suggest instead chmod 664 /etc/my.cnf and chown root:root /etc/my.cnf which are standard MySQL ownership and permissions.

    – dbdemon
    Apr 28 '18 at 11:33











  • I used chmod 650 /etc/

    – M.D
    Apr 28 '18 at 15:02





















  • MySQL doesn't write to its option files. You changed the whole /etc/ directory? 650 is "rw-r-x---" ... I'd suggest instead chmod 664 /etc/my.cnf and chown root:root /etc/my.cnf which are standard MySQL ownership and permissions.

    – dbdemon
    Apr 28 '18 at 11:33











  • I used chmod 650 /etc/

    – M.D
    Apr 28 '18 at 15:02



















MySQL doesn't write to its option files. You changed the whole /etc/ directory? 650 is "rw-r-x---" ... I'd suggest instead chmod 664 /etc/my.cnf and chown root:root /etc/my.cnf which are standard MySQL ownership and permissions.

– dbdemon
Apr 28 '18 at 11:33





MySQL doesn't write to its option files. You changed the whole /etc/ directory? 650 is "rw-r-x---" ... I'd suggest instead chmod 664 /etc/my.cnf and chown root:root /etc/my.cnf which are standard MySQL ownership and permissions.

– dbdemon
Apr 28 '18 at 11:33













I used chmod 650 /etc/

– M.D
Apr 28 '18 at 15:02







I used chmod 650 /etc/

– M.D
Apr 28 '18 at 15:02




















draft saved

draft discarded




















































Thanks for contributing an answer to Database Administrators Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f205180%2ffailed-starting-mysqld-on-centos-6%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Armoriale delle famiglie italiane (Car) Indice Armi | Bibliografia | Menu di navigazioneBlasone...

Why does this relation fail symmetry and transitivity properties?Properties of Relations. Reflexive,...

why typing a variable (or expression) prints the value to stdout?Calling a function of a module by using its...