Sponsored Content
Full Discussion: mysqld
Operating Systems BSD mysqld Post 70799 by SoulCoder on Wednesday 4th of May 2005 10:06:54 AM
Old 05-04-2005
mysqld

Hello

I installed mysql41 this is the end of the installation
Quote:
You already have a group "mysql", so I will use it.
mysql:*:88:88::0:0:MySQL Daemon:/var/db/mysql:/sbin/nologin
You already have a user "mysql", so I will use it.
===> Compressing manual pages for mysql-server-4.1.11_1
===> Registering installation for mysql-server-4.1.11_1
===> SECURITY REPORT:
This port has installed the following files which may act as network
servers and may therefore pose a remote security risk to the system.
/usr/local/libexec/mysqld

If there are vulnerabilities in these programs there may be a security
risk to the system. FreeBSD makes no guarantee about the security of
ports included in the Ports Collection. Please type 'make deinstall'
to deinstall the port if this is a concern.

For more information, and contact details about the security
status of this software, see the following webpage:
http://www.mysql.com/
but when I try to launch the mysqld daemon it write this:
Quote:
$ /usr/local/libexec/mysqld
050504 15:31:13 [Warning] Can't create test file /var/db/mysql/Lodelservoo.lower-test
/usr/local/libexec/mysqld: Can't change dir to '/var/db/mysql/' (Errcode: 13)
050504 15:31:13 [ERROR] Aborting

050504 15:31:13 [Note] /usr/local/libexec/mysqld: Shutdown complete
note: LodelServoo is a CMS which need mysql


I verify that the dir mysql existed under /var/db, but it doesn't so naively I created it and launch again the mysqld but each time i have the same error message.

If someone know something about it he is welcoming

Thanks in advance
 

5 More Discussions You Might Find Interesting

1. Red Hat

comm: mysqld Not tainted ... Kernel Panic , System totally unresponsive

Hi, I am experiencing frequent system hangs, hard kernel panics, etc almost thrice a day. The system would be totally unresponsive and the only way is to reboot is hard power recycling (plug out the power cable and plug in back after 30 secs). I enabled kdump, but unfortunately the kdump files... (3 Replies)
Discussion started by: massoo
3 Replies

2. UNIX for Dummies Questions & Answers

mysqld overloading cpu of VPS

Hi bros I have a VPS 512mb (Burst 2GB) with Kloxo installed and hosting few sites on it with not much traffic I am facing high cpu load for the last few days and seems mysqld is overloading the cpu Any suggestion will be appreciated Regards Rizwan Top output is as under top -... (2 Replies)
Discussion started by: rizwan65
2 Replies

3. Red Hat

MySQL (mysqld) fails to start!

Hello, I have recently installed MySql and I encourage an error. I am using Fedora 15 and when I am trying to start mysqld service i am getting the following error message: Starting mysqld (via systemctl): Job failed. See system logs and 'systemctl status' for details. If I try to start it... (4 Replies)
Discussion started by: dot_pro
4 Replies

4. Programming

PHP exec to restart mysqld

I want to do something very very bad. I want to create a button that restarts mysqld. Why is irrelevant for my issue. Here is my php script ... <?php if(isset($_POST)){ exec("sudo /etc/init.d/mysqld restart"); } ?> <form method="POST"> <input type="submit" name="restart"... (3 Replies)
Discussion started by: noPermissions
3 Replies

5. Homework & Coursework Questions

Mysql missing mysqld.sock (Linux)

I am trying to start a server for a class I am in but... mysql won't start with this error ( ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) ) ---------- Post updated at 03:51 PM ---------- Previous update was at 03:50 PM ---------- ... (2 Replies)
Discussion started by: Slayer939
2 Replies
OCF_HEARTBEAT_MYSQL(7)						OCF resource agents					    OCF_HEARTBEAT_MYSQL(7)

NAME
ocf_heartbeat_mysql - Manages a MySQL database instance SYNOPSIS
mysql [start | stop | status | monitor | promote | demote | notify | validate-all | meta-data] DESCRIPTION
Resource script for MySQL. May manage a standalone MySQL database, a clone set with externally managed replication, or a complete master/slave replication setup. SUPPORTED PARAMETERS
binary Location of the MySQL server binary (optional, string, default /usr/bin/mysqld_safe) client_binary Location of the MySQL client binary (optional, string, default mysql) config Configuration file (optional, string, default /etc/my.cnf) datadir Directory containing databases (optional, string, default /var/lib/mysql) user User running MySQL daemon (optional, string, default mysql) group Group running MySQL daemon (for logfile and directory permissions) (optional, string, default mysql) log The logfile to be used for mysqld. (optional, string, default /var/log/mysqld.log) pid The pidfile to be used for mysqld. (optional, string, default /var/lib/mysql/mysqld.pid) socket The socket to be used for mysqld. (optional, string, default /var/lib/mysql/mysql.sock) test_table Table to be tested in monitor statement (in database.table notation) (optional, string, default mysql.user) test_user MySQL test user (optional, string, default root) test_passwd MySQL test user password (optional, string, no default) enable_creation If the MySQL database does not exist, it will be created (optional, integer, default 0) additional_parameters Additional parameters which are passed to the mysqld on startup. (e.g. --skip-external-locking or --skip-grant-tables) (optional, string, no default) replication_user MySQL replication user. This user is used for starting and stopping MySQL replication, for setting and resetting the master host, and for setting and unsetting read-only mode. Because of that, this user must have SUPER, REPLICATION SLAVE, REPLICATION CLIENT, and PROCESS privileges on all nodes within the cluster. (optional, string, no default) replication_passwd MySQL replication password. Used for replication client and slave. (optional, string, no default) replication_port The port on which the Master MySQL instance is listening. (optional, string, default 3306) max_slave_lag The maximum number of seconds a replication slave is allowed to lag behind its master. Do not set this to zero. What the cluster manager does in case a slave exceeds this maximum lag is determined by the evict_outdated_slaves parameter. (optional, integer, default 3600) evict_outdated_slaves If set to true, any slave which is more than max_slave_lag seconds behind the master has its MySQL instance shut down. If this parameter is set to false in a primitive or clone resource, it is simply ignored. If set to false in a master/slave resource, then exceeding the maximum slave lag will merely push down the master preference so the lagging slave is never promoted to the new master. (optional, boolean, default false) SUPPORTED ACTIONS
This resource agent supports the following actions (operations): start Starts the resource. Suggested minimum timeout: 120. stop Stops the resource. Suggested minimum timeout: 120. status Performs a status check. Suggested minimum timeout: 60. monitor Performs a detailed status check. Suggested minimum timeout: 30. Suggested interval: 10. promote Promotes the resource to the Master role. Suggested minimum timeout: 120. demote Demotes the resource to the Slave role. Suggested minimum timeout: 120. notify Suggested minimum timeout: 90. validate-all Performs a validation of the resource configuration. Suggested minimum timeout: 5. meta-data Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5. EXAMPLE
The following is an example configuration for a mysql resource using the crm(8) shell: primitive example_mysql ocf:heartbeat:mysql op monitor depth="0" timeout="30" interval="10" SEE ALSO
http://www.linux-ha.org/wiki/mysql_(resource_agent) AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors) resource-agents 1.0.3 07/05/2010 OCF_HEARTBEAT_MYSQL(7)
All times are GMT -4. The time now is 09:45 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy