![]() | |
![]() |
| | Thread Tools | Display Modes |
#11
| |||
| |||
|
|
Kees Nuyt wrote: On Fri, 29 Jul 2011 17:04:12 -0400, Jerry Stuckle jstucklex (AT) attglobal (DOT) net> wrote: bind-address (should NOT be set or should be set to the remote's ip address). Are you sure? I would expect it should be set (in this use case) to either 0.0.0.0 (=listen on all interfaces) or 192.168.10.101 (=listen on the interface the partner tries to connect to). Best regards, unsetting it has the same effect as setting it to 0.0.0.0 |
#12
| |||
| |||
|
|
On Fri, 29 Jul 2011 17:04:12 -0400, Jerry Stuckle jstucklex (AT) attglobal (DOT) net> wrote: bind-address (should NOT be set or should be set to the remote's ip address). Are you sure? I would expect it should be set (in this use case) to either 0.0.0.0 (=listen on all interfaces) or 192.168.10.101 (=listen on the interface the partner tries to connect to). Best regards, |
#13
| |||
| |||
|
|
bill <will... (AT) TechServSys (DOT) com> wrote: The error log contains [ERROR] Slave I/O: error connecting to master 'r... (AT) 192 (DOT) 168.10.101:3306 I do have a user on the master named repl (AT) localhost (DOT) The user must be created on the master, the user name must be repl@'slave-ip-address' and it needs the replication slave privilege. Besides that replication uses the normal MySQL protocol, so you can use any MySQL client to test the connection. I.e. mysql -h 192.168.10.101 -u repl -p (to be run on the slave, of course) XL |
#14
| |||
| |||
|
|
On Jul 28, 5:00 am, Axel Schwenke <axel.schwe... (AT) gmx (DOT) de> wrote: bill <will... (AT) TechServSys (DOT) com> wrote: The error log contains [ERROR] Slave I/O: error connecting to master 'r... (AT) 192 (DOT) 168.10.101:3306 I do have a user on the master named repl (AT) localhost (DOT) The user must be created on the master, the user name must be repl@'slave-ip-address' and it needs the replication slave privilege. Besides that replication uses the normal MySQL protocol, so you can use any MySQL client to test the connection. I.e. mysql -h 192.168.10.101 -u repl -p (to be run on the slave, of course) XL Resolved: in the default my.cnf supplied with Ubuntu is an entry "bind-address = 127.0.0.1" which prevents the mysql daemon from accepting connections other than locally. Commenting out this entry fixed the problem and replication is working well. This brings up 2 questions: 1) how does phpmyadmin connect from a remote computer (and it did) ? |
|
2) rather than leaving it wide open, what can I put for bind-address to allow both local access and replication from a remote IP address ? |
#15
| |||
| |||
|
|
On Jul 28, 5:00 am, Axel Schwenke<axel.schwe... (AT) gmx (DOT) de> wrote: bill<will... (AT) TechServSys (DOT) com> wrote: The error log contains [ERROR] Slave I/O: error connecting to master 'r... (AT) 192 (DOT) 168.10.101:3306 I do have a user on the master named repl (AT) localhost (DOT) The user must be created on the master, the user name must be repl@'slave-ip-address' and it needs the replication slave privilege. Besides that replication uses the normal MySQL protocol, so you can use any MySQL client to test the connection. I.e. mysql -h 192.168.10.101 -u repl -p (to be run on the slave, of course) XL Resolved: in the default my.cnf supplied with Ubuntu is an entry "bind-address = 127.0.0.1" which prevents the mysql daemon from accepting connections other than locally. Commenting out this entry fixed the problem and replication is working well. This brings up 2 questions: 1) how does phpmyadmin connect from a remote computer (and it did) ? 2) rather than leaving it wide open, what can I put for bind-address to allow both local access and replication from a remote IP address ? bill |
#16
| |||
| |||
|
|
Resolved: in the default my.cnf supplied with Ubuntu is an entry "bind-address = 127.0.0.1" which prevents the mysql daemon from accepting connections other than locally. Commenting out this entry fixed the problem and replication is working well. This brings up 2 questions: 1) how does phpmyadmin connect from a remote computer (and it did) ? |
|
2) rather than leaving it wide open, what can I put for bind-address to allow both local access and replication from a remote IP address ? |
#17
| |||
| |||
|
|
The Natural Philosopher wrote: e.g. in my my.cnf is: # Instead of skip-networking the default is now to listen only on # localhost which is more compatible and is not less secure. bind-address = 127.0.0.1 |
#18
| |||
| |||
|
|
The Natural Philosopher <tnp (AT) invalid (DOT) invalid> wrote: The Natural Philosopher wrote: e.g. in my my.cnf is: # Instead of skip-networking the default is now to listen only on # localhost which is more compatible and is not less secure. bind-address = 127.0.0.1 This is not the default. Some distributors might put such a line in the my.cnf. But this is a poor decision unless they ask for confirmation that this MySQL server is only to be used locally. |
| XL |
![]() |
| Thread Tools | |
| Display Modes | |
| |