wrote:
How do you do this?
--- Whit Blauvelt [EMAIL PROTECTED] wrote:
Even if you have the zlib library, you may have to
add the flag for it
manually - it's not properly found by the configure
routine as of 3.23.37,
at least on Debian Linux 2.2
On Tue, Jun 12, 2001 at 08:23:02PM -0400, William M. Quarles wrote:
Make sure you have also read chapter 4.16, most importantly 4.16.5. it has
some important information in it, too.
Those chapters have nothing directly regarding replication. If you're to the
point of worrying about
Even if you have the zlib library, you may have to add the flag for it
manually - it's not properly found by the configure routine as of 3.23.37,
at least on Debian Linux 2.2.
On Wed, Jun 13, 2001 at 03:11:42PM +0300, Sinisa Milivojevic wrote:
[EMAIL PROTECTED] writes:
Description:
Unable
If PHP is compiled with its own MySQL support (as compared to using the
MySQL shared libraries - which are not in every MySQL distribution) it
expects mysql.sock to be in /tmp - whereas recent versions of MySQL put it
in /var/lib/mysql/. PHP will find it if you add mysql.default_socket =
Have you tried rebooting? I'm seeing the same problem with 3.23.38 (after
stopping the server with mysqladmin and then trying to restart with
safe_mysqld) but rebooting resets whatever it is that 3.23.38 is not
properly clearing on the shutdown.
Don't have this problem on another system running
On Wed, Jun 13, 2001 at 12:42:00AM -, [EMAIL PROTECTED] wrote:
database,sql,query,table
Anyone have an interpretation of this:
010612 20:37:32 Slave: Failed reading log event, reconnecting to retry, log 'FIRST'
position 4
010612 20:37:32 Slave: reconnected to master
On Wed, Jun 13, 2001 at 12:49:22AM -, [EMAIL PROTECTED] wrote:
database,sql,query,table
- which is really too constricted!
On Tue, Jun 12, 2001 at 04:10:44PM -0400, Jim Ziegler wrote:
010410 16:37:24 Slave: Failed reading log event, reconnecting to retry, log 'FIRST'
position 4
Doing that, I'm now seeing: ERROR 2013: Lost connection to MySQL
server during query after entering the password.
The problem above shouldn't be master.info related.
Sheesh, yeah, it's:
stunnel[7765]: Connection from xxx.xx.xxx.xx:1635 REFUSED by libwrap
which is the problem for
Doing that, I'm now seeing: ERROR 2013: Lost connection to MySQL
server during query after entering the password.
Right. That was a client error. The server is the only thing which
cares about the master.info file.
Okay, this is solved - stunnel works better when compiled without
Well, getting stunnel clean now presents additional info in the *.err file
on the slave:
010611 13:35:41 Error reading packet from server: Access denied for user:
'ftp@localhost' (Using password: YES) (0)
This being repeated every minute implies it's from the replication
connection, which is
Is that a Red Hat gcc? There was a famous version they put out with 7.0
that's broken for a lot of things - but I don't recall the gcc version
number.
I've compiled MySQL just fine with gcc version 2.95.2 on Debian (aside from
MySQL needing some help finding zlib). If you go to gnu.org and
Okay, password was not recognized because I had the tunnel working with the
f.q. server name rather than localhost (whereas the mysql client on the
slave will _only_ work with the tunnel if it is by the fq server name, since
localhost just goes to the local machine regardless of socket).
But
Trying to upgrade from 3.23.27 to 3.23.38 via rpm. The problem is then
Apache/PHP cannot connect to the database (using the mysql routines internal
to PHP), so I'm left having to --force --nodeps a downgrade to keep the
system up. Now, PHP can be compiled to use the current MySQL libraries, but
Okay, to get mysql --port= to work with a forwarded port it's also
necessary to specify the host name as the external name rather than the
assumed localhost.
Doing that, I'm now seeing: ERROR 2013: Lost connection to MySQL server during query
after entering the password.
I'm trying to fix
Doing that, I'm now seeing: ERROR 2013: Lost connection to MySQL
server during query after entering the password.
The problem above shouldn't be master.info related.
Does the master.info file on the slave contain accurate info?
Removing master.info and restarting the slave server
15 matches
Mail list logo
