Hello.
I plan to use mysql with only instance database so I can stop one database for maintenance without stopping every thing.
When one reads through the my.cnf config file, it is not clear if we must use at the same time a single database mysql plus any instances mysqld2 (for app1), mysqld3 (for app2), and so on.
Or may I get rid of the mysqld process and start only mysqld2, mysqld3, ....
I have try that but could not start any instance. Of course I have configured a systemd service file.
Or may I use mysqld1 as mysql database pointing to mysql as first mandatory database and then add more instance when necessary.
here code for mysqld@.service
my config file in /etc/my.cnf
I would like some advise.
Dear all.....
I am currently writing a Help-Desk / Knowledge Base application using PHP/PostGreSQL.
I authenticate the user using a quite elaborate mechanism of cookies. The problem is that using cookies (I also have a version using sessions with the same problem), I can only seem to get one... (4 Replies)
;)Hi Everyone,
I am using solaris 5.10.
I have a java process running in server mode in unix.
The problem is that it automatically forks i.e creates a child process.
I mean suddenly two instances of that process start running , in which the process-id of first instance is the parent... (0 Replies)
Hi Everyone,
I am using solaris 5.10.
I have a java process running in server mode in unix.
The problem is that it automatically forks i.e creates a child process.
I mean suddenly two instances of that process start running , in which the process-id of first instance is the parent... (5 Replies)
I am trying to debug the following script. It appears that when the check for script running occurs, it's finding the actual grep statement and causing the script believe the script is already running. This is deployed on two different servers where one works fine, the other doesn't. Any ideas?
... (2 Replies)
Hi All,
I have a problem mentioned below.
I have a script which performs line by line operations on several files.
I have a temp_file storing the list of names of the file to be validated. Right not in while loop i validate these files one by one.
Is there anyway that i can modify... (1 Reply)
Hi all,I have some questions of forking new process,the code is below.Any help will be appreciated.
1 #! /bin/bash
2
3 PIDS=$(pidof sh $0)
4 P_array=( $PIDS )
5 echo $PIDS
6 let "instances = ${#P_array}-1"
7
8 echo "$instances instance(s)" of this script running."
9... (4 Replies)
I need to install a tomcat6 with multiple instances like instance1,instance2 and instance3 in a server.
I came to know that for that we need to install tomcat6,apache2.0,mod_jk1.2 and jre with tools.jar installed.And we need to create multiple instances with same web.xml and difference... (0 Replies)
I've been bitten by using a lock or pid file to prevent multiple instances of a script. A user typed kill -9, and the pid file didn't go away. You can't trap -9. So when he tried to restart, it said "already running", and I got trouble report. Argh.
So here's what we came up with:
# Stop if... (1 Reply)
Hi,
Trying to setup mediawiki on a system but having problems configuring mysql:
CC=/usr/bin ./configure
checking build system type... powerpc-ibm-aix6.1.0.0
checking host system type... powerpc-ibm-aix6.1.0.0
checking target system type... powerpc-ibm-aix6.1.0.0
checking for a... (9 Replies)
Hello,
can someone please suggest me in configuring the mysql db on redhat cluster, I have few questions.
1. where do I have to configure heart beat links, and is there any file in the redhat cluster that we update it to use these ipaddress and these interface on the node.
2. I am configuring... (0 Replies)
Discussion started by: bobby320
0 Replies
LEARN ABOUT SUSE
ocf_heartbeat_mysql
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)