Re: mysqld_multi
Am 01.06.2017 um 00:01 schrieb Matthew Black: I DON'T RUN SYSTEMD, so that's not an option. At all. Why is that so hard to grasp? then just clone the sysvinit script as i have done years ago before syetemd on dozens of machines without ever touch mysqld_multi - why is that so hard to grasp? Where do I enter the command "create table database" when mysqld isn't running? It isn't possible to launch mysqld when there's no database directory or initialized database. *that* was missing from the very begin but still RTFM https://dev.mysql.com/doc/refman/5.7/en/mysql-install-db.html in my google search field is nothing more than "mysql init database" and guess what - when you have *somewhere* a running instance you can just shut it down, rsync the "mysql" folder from the datadir to the new instance and just fire it up - that's how i clone and init mysqld instances since 15 years, i explained that already You fail to grasp my problem and your answers are completely unhelpful you fail to describe your problem properly they don't behave anything different if you have a single server Really? With mysqld_multi, each mysqld daemon listens on a separate port. Each database instance gets its own environment that database administrators control WITHOUT INTERFERING with other database instances. In single-server environment, the server listens only on port 3306 and all databases run on that one port; it is not possible to shutdown individual databases, only ALL databases. tell me something new - but there is no difference how you connect to a databaseserver - just host/port or host/socket - so what -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
RE: mysqld_multi
I DON'T RUN SYSTEMD, so that's not an option. At all. Why is that so hard to grasp? Where do I enter the command "create table database" when mysqld isn't running? It isn't possible to launch mysqld when there's no database directory or initialized database. You fail to grasp my problem and your answers are completely unhelpful. I did not ask for "help" commands or links to the 5200-page reference manual, as those did not supply the options required to solve MY PROBLEM. This is a community forum where members are free to post questions. Several people pointed me toward the right direction but their answers were incomplete. It was ultimately Oracle support that answered my question, for which I am most appreciative. > they don't behave anything different if you have a single server Really? With mysqld_multi, each mysqld daemon listens on a separate port. Each database instance gets its own environment that database administrators control WITHOUT INTERFERING with other database instances. In single-server environment, the server listens only on port 3306 and all databases run on that one port; it is not possible to shutdown individual databases, only ALL databases. matthew -Original Message- From: Reindl Harald [mailto:h.rei...@thelounge.net] Sent: Wednesday, May 31, 2017 9:28 AM To: mysql@lists.mysql.com Subject: Re: mysqld_multi Am 31.05.2017 um 17:48 schrieb Matthew Black: > # mysql -uroot -p --socket=/MySQLdb/cba/mysql.sock > mysql> ALTER USER 'root'@'localhost' IDENTIFIED BY 'password'; > mysql> quit > > I was simply seeking those three commands, but the reference manual did not > provide a real-world example. they don't behave anything different if you have a single server, mysqld_multi or just a dozen mysqld instances started directly with systemd and "Can anyone provide a simple example of how to edit /etc/my.cnf file and command line steps necessary for creating a new database running on, for example, port 3311" still is nosense besides a basic command like "create table database" where your problem was obviosuly connect to the instance at all in my first response you got: [harry@srv-rhsoft:~]$ mysql --help | grep port well, find the socket option is similar [harry@rh:~]$ mysql --help | grep socket -S, --socket=name The socket file to use for connection. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: mysqld_multi
Am 31.05.2017 um 17:48 schrieb Matthew Black: # mysql -uroot -p --socket=/MySQLdb/cba/mysql.sock mysql> ALTER USER 'root'@'localhost' IDENTIFIED BY 'password'; mysql> quit I was simply seeking those three commands, but the reference manual did not provide a real-world example. they don't behave anything different if you have a single server, mysqld_multi or just a dozen mysqld instances started directly with systemd and "Can anyone provide a simple example of how to edit /etc/my.cnf file and command line steps necessary for creating a new database running on, for example, port 3311" still is nosense besides a basic command like "create table database" where your problem was obviosuly connect to the instance at all in my first response you got: [harry@srv-rhsoft:~]$ mysql --help | grep port well, find the socket option is similar [harry@rh:~]$ mysql --help | grep socket -S, --socket=name The socket file to use for connection. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
RE: mysqld_multi
Thank you all for the tips. I've read the manual multiple times and it is NOT clear what options are necessary in a multi environment. The missing element was provided by Oracle support: I need to use --defaults-file=my.cnf as in: # mysqld --defaults-file=cba.cnf --initialize --user=cba CBA.CNF contents: [mysqld]# No instance number, NOT documented! socket = /MySQLdb/cba/mysql.sock port = 3317 pid-file = /MySQLdb/cba/mysqld.pid datadir= /MySQLdb/cba lc-messages-dir = /usr/share/mysql/English log-error = /MySQLdb/cba/mysql.error user = cba # mysql -uroot -p --socket=/MySQLdb/cba/mysql.sock mysql> ALTER USER 'root'@'localhost' IDENTIFIED BY 'password'; mysql> quit I was simply seeking those three commands, but the reference manual did not provide a real-world example. matthew -Original Message- From: shawn l.green [mailto:shawn.l.gr...@oracle.com] Sent: Saturday, May 20, 2017 10:57 AM To: mysql@lists.mysql.com Subject: Re: mysqld_multi Hello Matthew, On 5/19/2017 12:19 PM, Matthew Black wrote: > I just installed MySQL Enterprise Edition 5.7 on RHEL 6.8 to replace an aging > 5.1 system running on RHEL 5. We run mysqld_multi with multiple instances, > each database on its own TCP Port 33xx. I'm having trouble creating a > database on the new server in a multi environment. > > > > Can anyone provide a simple example of how to edit /etc/my.cnf file and > command line steps necessary for creating a new database running on, for > example, port 3311? > > > > Thanks in advance. > > > > matthew > How to use mysql_multi is covered in the Manual. This includes a sample my.cnf file demonstrating how to define your separate instances. https://dev.mysql.com/doc/refman/5.7/en/mysqld-multi.html However, before you setup an instance to be managed by mysqld_multi, you will need to instantiate a set of datafiles for that 5.7 instance of the mysqld daemon to manage. You do that following the directions here (by hand) the first time. https://dev.mysql.com/doc/refman/5.7/en/data-directory-initialization.html This means you need to setup at least two folders (one for --datadir and one for --tmpdir) for each separate instance you want to create and assign ownership and privileges to those folders appropriate to the user your mysqld daemon will be executing as when it runs. There are other things you must also keep unique between instances when they share a common host machine. Those are described here: https://dev.mysql.com/doc/refman/5.7/en/multiple-servers.html An example of setting up the folders and assigning privileges to them is located in the instructions to installing a set of mysqld binaries using a .zip or .tar archive. Please note, you do not need a separate mysqld installation for each instance you want to create. Several daemons (each operating on their own port, socket, folders, data files,... ) can be started using just one set of binary files. https://dev.mysql.com/doc/refman/5.7/en/binary-installation.html So... the general process would look like this (presuming you have already installed mysqld and setup at least one instance) == 1) Decide where you want a second (or later) instance to store its files. Choose port numbers and unix socket names for this new instance that are unique from any other instances that will be running on this host. 2) Setup any new folders you need to create (including assigning privileges) 3) Document those names and any other settings you want this additional instance to use in a configuration file specific for this instance 4) Use that special configuration file to bootstrap (initialize) the data files used to manage that instance (the --initialize instructions were linked to earlier in this reply) 5) Once you have this instance setup the way you want. Shut it down. 6) Copy the elements that are unique to this instance into an appropriately-named section of your common configuration file (the one that mysqld_multi will read) 7) Test that you can start/stop this new instance using mysqld_multi As you can tell, it takes a bit of planning and effort to establish a non-default setup of hosting multiple MySQL instances on the same host machine. There is no simple one-line command to tell mysqld_multi to create a new instance as there are things it cannot do (like create folders in your file system). Regards, -- Shawn Green MySQL Senior Principal Technical Support Engineer Oracle USA, Inc. - Integrated Cloud Applications & Platform Services Office: Blountville, TN Become certified in MySQL! Visit https://www.mysql.com/certification/ for details. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: mysqld_multi
Hello Matthew, On 5/19/2017 12:19 PM, Matthew Black wrote: I just installed MySQL Enterprise Edition 5.7 on RHEL 6.8 to replace an aging 5.1 system running on RHEL 5. We run mysqld_multi with multiple instances, each database on its own TCP Port 33xx. I'm having trouble creating a database on the new server in a multi environment. Can anyone provide a simple example of how to edit /etc/my.cnf file and command line steps necessary for creating a new database running on, for example, port 3311? Thanks in advance. matthew How to use mysql_multi is covered in the Manual. This includes a sample my.cnf file demonstrating how to define your separate instances. https://dev.mysql.com/doc/refman/5.7/en/mysqld-multi.html However, before you setup an instance to be managed by mysqld_multi, you will need to instantiate a set of datafiles for that 5.7 instance of the mysqld daemon to manage. You do that following the directions here (by hand) the first time. https://dev.mysql.com/doc/refman/5.7/en/data-directory-initialization.html This means you need to setup at least two folders (one for --datadir and one for --tmpdir) for each separate instance you want to create and assign ownership and privileges to those folders appropriate to the user your mysqld daemon will be executing as when it runs. There are other things you must also keep unique between instances when they share a common host machine. Those are described here: https://dev.mysql.com/doc/refman/5.7/en/multiple-servers.html An example of setting up the folders and assigning privileges to them is located in the instructions to installing a set of mysqld binaries using a .zip or .tar archive. Please note, you do not need a separate mysqld installation for each instance you want to create. Several daemons (each operating on their own port, socket, folders, data files,... ) can be started using just one set of binary files. https://dev.mysql.com/doc/refman/5.7/en/binary-installation.html So... the general process would look like this (presuming you have already installed mysqld and setup at least one instance) == 1) Decide where you want a second (or later) instance to store its files. Choose port numbers and unix socket names for this new instance that are unique from any other instances that will be running on this host. 2) Setup any new folders you need to create (including assigning privileges) 3) Document those names and any other settings you want this additional instance to use in a configuration file specific for this instance 4) Use that special configuration file to bootstrap (initialize) the data files used to manage that instance (the --initialize instructions were linked to earlier in this reply) 5) Once you have this instance setup the way you want. Shut it down. 6) Copy the elements that are unique to this instance into an appropriately-named section of your common configuration file (the one that mysqld_multi will read) 7) Test that you can start/stop this new instance using mysqld_multi As you can tell, it takes a bit of planning and effort to establish a non-default setup of hosting multiple MySQL instances on the same host machine. There is no simple one-line command to tell mysqld_multi to create a new instance as there are things it cannot do (like create folders in your file system). Regards, -- Shawn Green MySQL Senior Principal Technical Support Engineer Oracle USA, Inc. - Integrated Cloud Applications & Platform Services Office: Blountville, TN Become certified in MySQL! Visit https://www.mysql.com/certification/ for details. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: mysqld_multi
can't you just stop reply-all so that responses are going back to the list Am 20.05.2017 um 12:01 schrieb Johan De Meersman: He means a database, not a schema. Instance would have been clearer as terminology goes, admittedly, but in a MySQL context the two are identical. database and instance are identical? > I just installed MySQL Enterprise Edition 5.7 on RHEL 6.8 to > replace an aging 5.1 system running on RHEL 5. We run > mysqld_multi with multiple instances, each database on its > own TCP Port 33xx. I'm having trouble creating a database > on the new server in a multi environment. i still have no idea what is the problem * connect to the instance with "mysql -h 127.0.0.1 -P 3307 -u root -p" * create database dbname -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: mysqld_multi
He means a database, not a schema. Instance would have been clearer as terminology goes, admittedly, but in a MySQL context the two are identical. -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: mysqld_multi
Am 19.05.2017 um 18:42 schrieb Matthew Black: Sorry, but that is not the least bit helpful. We are not ready for RHEL 7, which is VERY different than prior versions. I don't really need the victim blaming for using an earlier RHEL release that is still fully supported and in widespread use. your problem - we are using Fedora in production since 2008 and systemd was introduced that i even can't remember the sysvinit mess... As for /etc/my.cnf, that's where one defines the port, database location, log file, port number, and user, so they don't have to be placed on the command line. and how do you imagine hat to work for *multiple instances* Your response does not explain the command line steps necessary for creating a new database. becasue creating a database is absolutely basic stuff at all and if you mean the mysql database with users itself - well, i hvanet created one from scratch since 2003 because they are portable between windows/linux/osx and i just rsync the folder or a baisc install and that's it -Original Message- From: Reindl Harald [mailto:h.rei...@thelounge.net] Sent: Friday, May 19, 2017 9:27 AM To: mysql@lists.mysql.com Subject: Re: mysqld_multi Am 19.05.2017 um 18:19 schrieb Matthew Black: I just installed MySQL Enterprise Edition 5.7 on RHEL 6.8 to replace an aging 5.1 system running on RHEL 5. We run mysqld_multi with multiple instances, each database on its own TCP Port 33xx. I'm having trouble creating a database on the new server in a multi environment. Can anyone provide a simple example of how to edit /etc/my.cnf file and command line steps necessary for creating a new database running on, for example, port 3311? what has this to do with the my.cnf? just connect to the correct instance and that's it and probably get rid of RHEL6 because with systemd you don't need all the crap around to start multiple instances, just a few lines in the unit-file pointing to the correct config and mysqld_safe is also no needed [harry@srv-rhsoft:~]$ mysql --help | grep port -P, --port=#Port number to use for connection or 0 for default to, in --progress-reports Get progress reports for long running commands (like (Defaults to on; use --skip-progress-reports to disable.) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
RE: mysqld_multi
Sorry, but that is not the least bit helpful. We are not ready for RHEL 7, which is VERY different than prior versions. I don't really need the victim blaming for using an earlier RHEL release that is still fully supported and in widespread use. As for /etc/my.cnf, that's where one defines the port, database location, log file, port number, and user, so they don't have to be placed on the command line. Your response does not explain the command line steps necessary for creating a new database. matthew -Original Message- From: Reindl Harald [mailto:h.rei...@thelounge.net] Sent: Friday, May 19, 2017 9:27 AM To: mysql@lists.mysql.com Subject: Re: mysqld_multi Am 19.05.2017 um 18:19 schrieb Matthew Black: > I just installed MySQL Enterprise Edition 5.7 on RHEL 6.8 to replace an aging > 5.1 system running on RHEL 5. We run mysqld_multi with multiple instances, > each database on its own TCP Port 33xx. I'm having trouble creating a > database on the new server in a multi environment. > > Can anyone provide a simple example of how to edit /etc/my.cnf file and > command line steps necessary for creating a new database running on, for > example, port 3311? what has this to do with the my.cnf? just connect to the correct instance and that's it and probably get rid of RHEL6 because with systemd you don't need all the crap around to start multiple instances, just a few lines in the unit-file pointing to the correct config and mysqld_safe is also no needed [harry@srv-rhsoft:~]$ mysql --help | grep port -P, --port=#Port number to use for connection or 0 for default to, in --progress-reports Get progress reports for long running commands (like (Defaults to on; use --skip-progress-reports to disable.) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: mysqld_multi
Am 19.05.2017 um 18:19 schrieb Matthew Black: I just installed MySQL Enterprise Edition 5.7 on RHEL 6.8 to replace an aging 5.1 system running on RHEL 5. We run mysqld_multi with multiple instances, each database on its own TCP Port 33xx. I'm having trouble creating a database on the new server in a multi environment. Can anyone provide a simple example of how to edit /etc/my.cnf file and command line steps necessary for creating a new database running on, for example, port 3311? what has this to do with the my.cnf? just connect to the correct instance and that's it and probably get rid of RHEL6 because with systemd you don't need all the crap around to start multiple instances, just a few lines in the unit-file pointing to the correct config and mysqld_safe is also no needed [harry@srv-rhsoft:~]$ mysql --help | grep port -P, --port=#Port number to use for connection or 0 for default to, in --progress-reports Get progress reports for long running commands (like (Defaults to on; use --skip-progress-reports to disable.) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: mysqld_multi startup stop
Sounds like you need to configure a user that has SHUTDOWN privileges. From: http://dev.mysql.com/doc/refman/5.0/en/mysqld-multi.html Make sure that the MySQL account used for stopping the mysqld servers (with the mysqladmin program) has the same username and password for each server. Also, make sure that the account has the SHUTDOWN privilege. If the servers that you want to manage have different usernames or passwords for the administrative accounts, you might want to create an account on each server that has the same username and password. For example, you might set up a common multi_admin account by executing the following commands for each server: shell mysql -u root -S /tmp/mysql.sock -p Enter password: mysql GRANT SHUTDOWN ON *.* - TO 'multi_admin'@'localhost' IDENTIFIED BY 'multipass'; The username/password goes in your my.cnf under a [mysqld_multi] section. Atle - Flying Crocodile Inc, Unix Systems Administrator On Sat, 21 Oct 2006, Low Kian Seong wrote: Dear all, I am running the official mysql rpms on a sles 9 box, and I am running multiple versions of mysql servers on different ports. The problem I am facing is that when i run mysqld_multi start n it starts the servers up fine but when i do the reverse : mysqld_multi stop n, it doesn't stop the server and I have to manually search for the pids and execute a kill on the process to stop it. Anybody have any idea ? Thank you in advance. Low Kian Seong -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysqld_multi at startup on Mac OS X not working
I have successfully configured mysqld_multi to have mysql 4.1.11 and
5.0.3 beta running on the same machine:
I would like to see how you configured mysqld_multi to do that, if you could
send me the information off list I'd appreciate it.
# mysqld_multi start
# exit
% mysqld_multi report
Reporting MySQL servers
MySQL server from group: mysqld4 is running
MySQL server from group: mysqld5 is running
%
However, I can't get this to work at system startup time. Starting up
a single mysql server works fine, with the following
/Library/StartupItems/MySQL/MySQL script:
#!/bin/sh
. /etc/rc.common
if [ ${MYSQL:=-YES-} = -YES- ]; then
ConsoleMessage Starting MySQL database server
/usr/local/mysql/bin/mysqld_safe
fi
But if I change /usr/local/mysql/bin/mysqld_safe to
/usr/local/mysql/bin/mysqld_multi start , no servers start up. There
are also no error messages in the .err logs: the last item there is
the previous 'normal shutdown'.
Any ideas? I would think that there should be no difference between
executing mysqld_multi from a root shell and executing it at startup
time, but apparently it's not the same.
You need to be careful... There isn't a difference between running
mysqld_multi at the command line and running it inside a script - remember
what you are running at startup isn't mysqld_multi but rather this command:
/System/Library/StartupItems/MySQL/MySQL start
That script then calls mysqld_multi, or not, depending on some variables in
the script...
What happens when you run
/System/Library/StartupItems/MySQL/MySQL start
At the command prompt... I venture a guess that the results are still no
mysqls start.
Let me share my startup script with you...
#!/bin/sh
. /etc/rc.common
StartService ()
{
if [ ${MYSQL=-NO-} = -YES- ]; then
ConsoleMessage Starting MySQL
/usr/local/mysql/bin/mysqld_multi start
fi
}
StopService ()
{
/usr/bin/mysqladmin ping /dev/null 21
if [ $? -eq 0 ]; then
ConsoleMessage Stopping MySQL
/usr/local/mysql/bin/mysqladmin --socket=/tmp/mysql.sock shutdown
/usr/local/mysql/bin/mysqladmin --socket=/tmp/mysql2.sock shutdown
else
ConsoleMessage MySQL is not running
fi
}
RestartService ()
{
StopService
StartService
}
RunService $1
There are some minor differences in how mine (which is working) and yours
seem to be configured... Let's look at those... What version of OS X are you
working on? Mine is running on 10.3.8, has been running on the previous
versions of 10.3 also. The major difference I see is the test on if to start
or not... This will be important. You have:
if [ ${MYSQL:=-YES-} = -YES- ]; then
While I have:
if [ ${MYSQL=-NO-} = -YES- ]; then
I don't know why yours is different, I know that mine works, it is Apple's
script and test, I just changed the binary it executes.
The other factor here is /etc/hostconfig - it must have a line that looks
like this:
MYSQL=-YES-
If YES is actually NO or if the line is not present at all, the startup
script will not execute the script.
Actually /etc/hostconfig is what the Startup scripts use to tell it what to
start or not, if you want to bounce your server and not have mysql start
when it reboots you can edit /etc/hostconfig and set the YES to a NO for the
MYSQL=-YES- line, just be sure to change it back when you are done.
When all is said and done you don't need to restart the whole machine to see
if your script is working.. You can simply run:
/System/Library/StartupItems/MySQL/MySQL start
And you will find out if you are working.
I also have some changes in the shutdown part of the script, because I use
mysqld_multi to start it, the original use of mysqladmin to shutdown the
single instance isn't going to shutdown both instances... So I add a line
for each instance to call mysqladmin shutdown and point it to each socket
file that is configured in the my.cnf file for each instance.
Hope that helps.
Best Regards, Bruce
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: mysqld_multi different server versions
You can use mysqld_multi to run different versions of MySQL on the same Server. You can run 4.0.x, 4.1.x and 5.0.x and manage these with mysqld_multi. -Original Message- From: sean c peters To: [EMAIL PROTECTED] Sent: 8/9/04 4:43 PM Subject: mysqld_multi different server versions In my ongoing quest to get upgraded to 4.1.3 beta (yes the version I'm upgrading to keeps changing), i have been reading about mysqld_multi to manage multiple server instances on the same machine. But, from what i've read, it appears that this is for running multiple instances of the same server version on one box. Same binary anyway. I say this because all the examples show as varying are the socket, port, pid-file, datadir, language, and user. The [mysqld_multi] directive for my.cnf points mysqld at a particular mysqld_safe, which would imply that all the instances would use the same server. So am i correct in thinking that i wont be able to use mysqld_multi for running two different server versions? This shouldn't be a problem, I dont think i'll need it. Just wanted to check if im missing something. thanks sean peters [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: mysqld_multi different server versions
DVP Dathan Vance Pattishall http://www.friendster.com -Original Message- From: sean c peters [mailto:[EMAIL PROTECTED] Sent: Monday, August 09, 2004 1:43 PM To: [EMAIL PROTECTED] Subject: mysqld_multi different server versions So am i correct in thinking that i wont be able to use mysqld_multi for running two different server versions? This shouldn't be a problem, I dont think i'll need it. Just wanted to check if im missing something. This is not entirely correct. A basedir definition will allow you do execute the safe_mysqld in the directory installed. thanks sean peters [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysqld_multi
Date: Wed, 14 Apr 2004 13:26:10 -0400 To: [EMAIL PROTECTED] From: Pingouin Team [EMAIL PROTECTED] Subject: mysqld_multi Message-Id: [EMAIL PROTECTED] Hi, I need help. I have my old mysql server running in my web server and I can't stop it for make the test of the new version (3.28 to 4.0). I have installed with compilation of the source code and configure my socket, var and port. I have make a config file with the --example: [mysqld_multi] mysqld = /home/benoit/mysql/bin/safe_mysqld mysqladmin = /home/benoit/mysql/bin/mysqladmin user = multi_admin password = multipass [mysqld2] socket = /home/benoit/tmp/mysql.sock port = 3310 pid-file = /home/benoit/mysql/var/pingouin.pid datadir = /home/benoit/mysql/var language = /home/benoit/mysql/share/mysql/english And I start my MySQL with ./mysqld_multi --config-file=/home/benoit/mysql/etc/my.cnf start 2 but when I execute that command line MySQL start and stop. In the log, I can see just that: mysqld_multi log file version 2.2; run: Wed Apr 14 13:01:02 2004 Starting MySQL servers Starting mysqld daemon with databases from /home/benoit/mysql/var 040414 13:01:05 mysqld ended Why the server do not stay online? Thank you, Benoit Tremblay -- NerdzTeam [EMAIL PROTECTED] ### Servus, to know what stops your MySQL Daemon you must look in your Log-File of this one. I don't know where it is in your system but it helps to add a separate one in [mysqld2] err-log = /var/log/mysql2d/mysqld.log and then look for the real problem (probably permissions ;-) But maybe you should wait an moment, because I have with this mysqld_multi a problem who can give you some trouble, too! As soon as I start the second Daemon the Socket of the first (main) Daemon disappears!! You can connect over TCP, but by default it tries the Socket at localhost. I have MySQL 5.0 running and maybe you haven't got this problem, but think about it. I posted about my Problem to the List (mysqld_multi kills socket from previous Daemon from 2004-04-07), but up to now I haven't got an answer and still don't know whats going on with my Sockets! (Has someone an Idea ??) Best regards, Tobias -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysqld_multi
On Thu, 7 Nov 2002, Chris Raymer wrote: Yes, that is what I meant. Thank you for the clarification and response. Any ideas on maximizing *server* performance besides the usual db-specific optimizations like indexing? If not too much trouble, could you give me a brief explanation why I would not see a performance boost if running separate servers on the same box? My thoughts, if have one MySQL server running on one box with 10 databases, and 1 or 2 of those databases are getting the majority of the requests and tying up the processes, seems like the other 8 would suffer. Hi! You can think of server instances as you'd think of databases. If one server instance (say, that with one or two heavily-loaded databases) gets a lot of requests, the other server instances suffer. With separate server instances you'll suffer from additional overhead. If you require different server configuration for different databases, then you'll have to install two or more separate server instances. Hope this clears it. :-) Regards, Iikka ** * Iikka Meriläinen * * E-mail: [EMAIL PROTECTED] * * Vaala, Finland * ** - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: mysqld_multi
Yes, that is what I meant. Thank you for the clarification and response. Any ideas on maximizing *server* performance besides the usual db-specific optimizations like indexing? If not too much trouble, could you give me a brief explanation why I would not see a performance boost if running separate servers on the same box? My thoughts, if have one MySQL server running on one box with 10 databases, and 1 or 2 of those databases are getting the majority of the requests and tying up the processes, seems like the other 8 would suffer. - Original Message - From: Iikka Meriläinen [EMAIL PROTECTED] To: Paul DuBois [EMAIL PROTECTED] Cc: Raymer, Chris [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, November 07, 2002 12:42 AM Subject: Re: mysqld_multi On Wed, 6 Nov 2002, Paul DuBois wrote: At 13:22 -0600 11/6/02, Raymer, Chris wrote: Any opinions on running mysqld_multi? Our architecture, X-serve, 2GBs RAM,Dual Procs, 480 GB stogage as Master MySQL server replicated to a less impressive server. Seems logical to separate the heavy-hitter dbs to their own servers and take more advantage of the server's resources. What's this got to do with mysqld_multi, which is used for running multiple servers on the *same* machine? Hi! Maybe Mr. Raymer means that he would get more performance when running multiple _MySQL_ servers (i.e. instances) on a same _physical_ server (i.e. box). Getting more performance this way is unfortunately a false assumption, though. More stability, perhaps, but not performance. Iikka ** * Iikka Meriläinen * * E-mail: [EMAIL PROTECTED] * * Vaala, Finland * ** - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: mysqld_multi
At 13:22 -0600 11/6/02, Raymer, Chris wrote: Any opinions on running mysqld_multi? Our architecture, X-serve, 2GBs RAM,Dual Procs, 480 GB stogage as Master MySQL server replicated to a less impressive server. Seems logical to separate the heavy-hitter dbs to their own servers and take more advantage of the server's resources. What's this got to do with mysqld_multi, which is used for running multiple servers on the *same* machine? Chris - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: mysqld_multi
On Wed, 6 Nov 2002, Paul DuBois wrote: At 13:22 -0600 11/6/02, Raymer, Chris wrote: Any opinions on running mysqld_multi? Our architecture, X-serve, 2GBs RAM,Dual Procs, 480 GB stogage as Master MySQL server replicated to a less impressive server. Seems logical to separate the heavy-hitter dbs to their own servers and take more advantage of the server's resources. What's this got to do with mysqld_multi, which is used for running multiple servers on the *same* machine? Hi! Maybe Mr. Raymer means that he would get more performance when running multiple _MySQL_ servers (i.e. instances) on a same _physical_ server (i.e. box). Getting more performance this way is unfortunately a false assumption, though. More stability, perhaps, but not performance. Iikka ** * Iikka Meriläinen * * E-mail: [EMAIL PROTECTED] * * Vaala, Finland * ** - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
