RE: connection problems
The problem was /etc/hosts, but not for localhost. My issue was that whomever setup /etc/hosts swapped the fields: Old busted: IP blah blah.1.2.3.net Working: IP blah.1.2.3.net blah Oh well...Thank for every one's time. Drew On Wed, 2004-07-28 at 17:33, Victor Pendleton wrote: > My apologies I was reading an ip address. Have you tried logging in from the > server itself? Since this is the initial install I think root needs to log > in from the localhost. > > -Original Message- > From: Andrew Hall > To: Victor Pendleton > Cc: '[EMAIL PROTECTED] ' > Sent: 7/28/04 4:35 PM > Subject: RE: connection problems > > Yes I have. The hostname of the box returned with 'hostname' is the > fqdn and is in the format of blah.1.2.3.net. > > Drew > > On Wed, 2004-07-28 at 17:16, Victor Pendleton wrote: > > Can you check the host name again? You have a five segment address. > > > > -Original Message- > > From: Andrew Hall > > To: [EMAIL PROTECTED] > > Sent: 7/28/04 3:55 PM > > Subject: connection problems > > > > Greetings, > > > > I have what I hope is an easy problem. I have installed mysql 4.0.20 > > and when I execute mysqladmin to set the root password using the -h > flag > > my hostname is truncated, and I get a connection refused message. > > > > The hostname on this box is a fqdn like blah.1.2.3.net. My command > line > > is "mysqladmin -u root -h blah.1.2.3.net password 'test'" > > > > mysqladmin -u root -h blah.1.2.3.net password "test" > > /path/to/mysql/bin/mysqladmin: connect to server at 'blah.1.2.3.net' > > failed > > error: 'Host 'blah' is not allowed to connect to this MySQL server' > > > > Can anyone shed any light on why the hostname is being truncated? Am > I > > missing something obvious here? > > > > Thank you in advance, > > > > Andrew > > > > > > -- > > 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: connection problems
This is a local connection. Thanks again! Drew On Wed, 2004-07-28 at 17:33, Victor Pendleton wrote: > My apologies I was reading an ip address. Have you tried logging in from the > server itself? Since this is the initial install I think root needs to log > in from the localhost. > > -Original Message- > From: Andrew Hall > To: Victor Pendleton > Cc: '[EMAIL PROTECTED] ' > Sent: 7/28/04 4:35 PM > Subject: RE: connection problems > > Yes I have. The hostname of the box returned with 'hostname' is the > fqdn and is in the format of blah.1.2.3.net. > > Drew > > On Wed, 2004-07-28 at 17:16, Victor Pendleton wrote: > > Can you check the host name again? You have a five segment address. > > > > -Original Message- > > From: Andrew Hall > > To: [EMAIL PROTECTED] > > Sent: 7/28/04 3:55 PM > > Subject: connection problems > > > > Greetings, > > > > I have what I hope is an easy problem. I have installed mysql 4.0.20 > > and when I execute mysqladmin to set the root password using the -h > flag > > my hostname is truncated, and I get a connection refused message. > > > > The hostname on this box is a fqdn like blah.1.2.3.net. My command > line > > is "mysqladmin -u root -h blah.1.2.3.net password 'test'" > > > > mysqladmin -u root -h blah.1.2.3.net password "test" > > /path/to/mysql/bin/mysqladmin: connect to server at 'blah.1.2.3.net' > > failed > > error: 'Host 'blah' is not allowed to connect to this MySQL server' > > > > Can anyone shed any light on why the hostname is being truncated? Am > I > > missing something obvious here? > > > > Thank you in advance, > > > > Andrew > > > > > > -- > > 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: connection problems
Yes I have. The hostname of the box returned with 'hostname' is the fqdn and is in the format of blah.1.2.3.net. Drew On Wed, 2004-07-28 at 17:16, Victor Pendleton wrote: > Can you check the host name again? You have a five segment address. > > -Original Message----- > From: Andrew Hall > To: [EMAIL PROTECTED] > Sent: 7/28/04 3:55 PM > Subject: connection problems > > Greetings, > > I have what I hope is an easy problem. I have installed mysql 4.0.20 > and when I execute mysqladmin to set the root password using the -h flag > my hostname is truncated, and I get a connection refused message. > > The hostname on this box is a fqdn like blah.1.2.3.net. My command line > is "mysqladmin -u root -h blah.1.2.3.net password 'test'" > > mysqladmin -u root -h blah.1.2.3.net password "test" > /path/to/mysql/bin/mysqladmin: connect to server at 'blah.1.2.3.net' > failed > error: 'Host 'blah' is not allowed to connect to this MySQL server' > > Can anyone shed any light on why the hostname is being truncated? Am I > missing something obvious here? > > Thank you in advance, > > Andrew > > > -- > 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]
connection problems
Greetings, I have what I hope is an easy problem. I have installed mysql 4.0.20 and when I execute mysqladmin to set the root password using the -h flag my hostname is truncated, and I get a connection refused message. The hostname on this box is a fqdn like blah.1.2.3.net. My command line is "mysqladmin -u root -h blah.1.2.3.net password 'test'" mysqladmin -u root -h blah.1.2.3.net password "test" /path/to/mysql/bin/mysqladmin: connect to server at 'blah.1.2.3.net' failed error: 'Host 'blah' is not allowed to connect to this MySQL server' Can anyone shed any light on why the hostname is being truncated? Am I missing something obvious here? Thank you in advance, Andrew -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: replication/InnoDB errors
Greetings, > > Didn't find any fields in table 'blah' > 031208 18:15:16 InnoDB error: > Cannot find table db/blah from the internal data dictionary > of InnoDB though the .frm file for the table exists. Maybe you > have deleted and recreated InnoDB data files but have forgotten > to delete the corresponding .frm files of InnoDB tables, or you > have moved .frm files to another database? > Look from section 15.1 of http://www.innodb.com/ibman.html > how you can resolve the problem. I found out what was causing this, for me at least. When I tar-ed the db's to copy to the new slave server, I did not include the file 'ibdata1' in the tarball. I scp-ed it over and bingo! Thanks, Andrew -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
replication/InnoDB errors
Greetings, I am having a difficult time understanding my replication error. I have two mysql installs both 3.23.54. I executed the following for my replication setup. On master: - stop mysql - add the following to my.cnf: [mysqld] log-bin server-id=1 - tar up data dir, copy to slave - start db - show master status; On slave: - stop mysql - add the following to my.cnf [mysqld] server-id=2 - untar data file - start db - connect, change master to. - slave start; At this point I get: 031208 18:10:24 Slave: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'xx-bin.001' at position 73 And it appears that its working, but if I attempt to use the db I get: Didn't find any fields in table 'blah' 031208 18:15:16 InnoDB error: Cannot find table db/blah from the internal data dictionary of InnoDB though the .frm file for the table exists. Maybe you have deleted and recreated InnoDB data files but have forgotten to delete the corresponding .frm files of InnoDB tables, or you have moved .frm files to another database? Look from section 15.1 of http://www.innodb.com/ibman.html how you can resolve the problem. And if I try to select I get the same error as above plus: ERROR 1016: Can't open file: 'blah.InnoDB'. (errno: 1) But my master does not have any files name *.InnoDB in it's data dir, so why does the master believe the table is of the InnoDB type? Could someone please shed some light on what I have done wrong here. Thank you in advance, Andrew Hall -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
[Fwd: RE: replication question]
Didn't have the list cc-ed. -Forwarded Message- > From: Andrew Hall <[EMAIL PROTECTED]> > To: Mike Johnson <[EMAIL PROTECTED]> > Subject: RE: replication question > Date: Fri, 05 Dec 2003 16:17:14 -0500 > > Ok, at this point it appears my replication is working, but I have two > questions: > > 1. I tested by creating a table on the master, populated it, then on the > slave did a 'show tables', and 'select * from test', and my test table > and data was there. Is this methodology acceptable for a basic test? > Any suggestions on testing methodology? > > 2. When I execute 'show master status' the Binlog_db_do fields is > empty. This seems erroneous to me. Shouldn't this field be populated > with the db name(s) to replicate? > > Thanks again, > > Drew > > > execute > > > 'START SLAVE' > > > on my slave I get > > > > > > ERROR 1064: You have an error in your SQL syntax near 'START SLAVE' at > > > line 1 > > > > > > This tells me that my version of mysql does not support the 'START' > > > command. Do I need to add something at compile time? Are the > > > instructions only for 4.x? Am I just missing something > > > really obvious? > > > > > > Don't quote me on it, but I think START SLAVE was introduced in 4.x. Try SLAVE > > START. I recently read that SLAVE START was being deprecated; I can only assume > > START SLAVE was a recent introduction. > > > > Regardless, I always used SLAVE START on 3.23.x. > > > > HTH > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: replication question
DUH!! I should have tried that... Thank you! Drew On Fri, 2003-12-05 at 15:49, Victor Pendleton wrote: > Try slave start > > -Original Message- > From: Andrew Hall [mailto:[EMAIL PROTECTED] > Sent: Friday, December 05, 2003 2:46 PM > To: [EMAIL PROTECTED] > Subject: replication question > > > Greetings, > > Firstly I have searched the archives and received exactly 0 results > returned for 'START SLAVE 1064' so... > > I have a mysql server I wish to replicate, its running 3.23.54. I have > two test FreeBSD 5.1 servers I installed and from ports version > 3.23.58. I completed the following steps to setup replication. > > I followed the steps in the documentation on mysql.com, made the > necessary my.conf modification, archived and imported my test db to the > slave, defined the master config w/ 'change master to' on the > slave. > > Everything worked well up to this point, but if I execute 'START SLAVE' > on my slave I get > > ERROR 1064: You have an error in your SQL syntax near 'START SLAVE' at > line 1 > > This tells me that my version of mysql does not support the 'START' > command. Do I need to add something at compile time? Are the > instructions only for 4.x? Am I just missing something really obvious? > > Thank you for your time in advance, > > Andrew > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
replication question
Greetings, Firstly I have searched the archives and received exactly 0 results returned for 'START SLAVE 1064' so... I have a mysql server I wish to replicate, its running 3.23.54. I have two test FreeBSD 5.1 servers I installed and from ports version 3.23.58. I completed the following steps to setup replication. I followed the steps in the documentation on mysql.com, made the necessary my.conf modification, archived and imported my test db to the slave, defined the master config w/ 'change master to' on the slave. Everything worked well up to this point, but if I execute 'START SLAVE' on my slave I get ERROR 1064: You have an error in your SQL syntax near 'START SLAVE' at line 1 This tells me that my version of mysql does not support the 'START' command. Do I need to add something at compile time? Are the instructions only for 4.x? Am I just missing something really obvious? Thank you for your time in advance, Andrew -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Off Topic: MySQL Icons
Try google images... It's where I go every time I need to find an image that I don't have on hand. Drew On Thu, 2003-12-04 at 18:01, Daniel Kasak wrote: > Hi all. > > I'm prettying up my Gnome desktop, and I'm after a MySQL icon for my > MySQLCC launcher. > Anyone know of some icons? > > -- > Daniel Kasak > IT Developer > NUS Consulting Group > Level 5, 77 Pacific Highway > North Sydney, NSW, Australia 2060 > T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989 > email: [EMAIL PROTECTED] > website: http://www.nusconsulting.com.au > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: mysql disaster recovery
John, Thank you for your reply. I have read the replication chapter and this seems to be easier, but I do have a few questions. 1. I am using InnoDB tables, at least there are innodb argument to mysqld in the start script, so should I use mysqldump instead of tar-ing the data dir to create the baseline for the slave? I believe thats what the docs are stating, but I wanted to be certain. 2. I want to have a failover scenario here, so what would the impact be on the mysql db if I go master->slave->master? 3. What happens if the master fails, dies, and goes offline. Must I change all my apps to connect to the IP of the slave for connections to work? I am unclear if replication will provide failover capabilities. 4. What is necessary to bring the master back up after a failure? Should I? or should I leave the slave (new master) up, and make the old master the new slave? 5. I am running 3.23.54 and I know I should upgrade, but its not going to happen today, so are there any show stopping bugs with this version? Thank you for your time, Andrew On Tue, 2003-12-02 at 17:10, John Griffin wrote: > Hi Andrew, > > I am not a Guru. I would suggest that you look at MySQL's excellent replication > facility rather than NFS mount a drive. Having your data on an NFS mounted drive > will significantly degrade the performance of your database. Replication will not. > > > John Griffin > > --Original Message-- > From: Andrew Hall [mailto:[EMAIL PROTECTED] > Sent: Tuesday, December 02, 2003 4:51 PM > To: [EMAIL PROTECTED] > Subject: mysql disaster recovery > > > Greetings Gurus, > > I have a mysql server that I need to create a disaster recovery system > for. What I am planning on doing is putting the data dir on a NFS > mounted directory so that I can start mysql on either of two servers in > case one dies. The inbound connections would be load balanced in a fail > over scenario, so the IP that clients will connect to will be on the > load balancer. > > I'm wondering if there is anything already developed that would test > mysql on the primary server, and if its not functioning, kill any > remaining mysql processes if necessary, and start it on the secondary. > This logic seems to be the biggest problem. > > Any suggestions, or other methodologies to implement this would be > welcome. > > Thank you for your time in advance, > > Andrew > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
mysql disaster recovery
Greetings Gurus, I have a mysql server that I need to create a disaster recovery system for. What I am planning on doing is putting the data dir on a NFS mounted directory so that I can start mysql on either of two servers in case one dies. The inbound connections would be load balanced in a fail over scenario, so the IP that clients will connect to will be on the load balancer. I'm wondering if there is anything already developed that would test mysql on the primary server, and if its not functioning, kill any remaining mysql processes if necessary, and start it on the secondary. This logic seems to be the biggest problem. Any suggestions, or other methodologies to implement this would be welcome. Thank you for your time in advance, Andrew -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
