MySQL Forums
Forum List  »  NDB clusters

SQL node 1 not starting - secure-file-priv set to NULL and Fatal error... find out how to run mysqld as root!
Posted by: Brian Paquin
Date: June 13, 2018 10:51AM

I'm using MySQL Cluster 7.6.6 with the Auto Installer on RHEL 7. The cluster consists of 1 management node and 2 data nodes. When I start the cluster, the management node starts, followed by the 2 data nodes. But then I get the following error when starting SQL node 1:

Command `nohup /usr/local/mysql/bin/mysqld --defaults-file=/home/administrator/cluster2/53/my.cnf' exited with 1:
nohup: appending output to ‘nohup.out’
2018-06-13T16:19:38.456883Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-06-13T16:19:38.456971Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2018-06-13T16:19:38.456997Z 0 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.7.22-ndb-7.6.6-cluster-gpl) starting as process 16711 ...
2018-06-13T16:19:38.459812Z 0 [ERROR] Fatal error: Please read "Security" section of the manual to find out how to run mysqld as root!

2018-06-13T16:19:38.459841Z 0 [ERROR] Aborting

2018-06-13T16:19:38.459860Z 0 [Note] Binlog end
2018-06-13T16:19:38.459906Z 0 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete

I stopped the cluster, killed any remaining mysqld processes, and got the same error when starting the cluster. Do I need to go back and define parameters?

I feel like I am SO close to getting the cluster started!

Thank you,


Options: ReplyQuote

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.