Has anyone ever been able to communicate between a client app and a mysql
server over stunnel ?
(stunnel listening on client; connecting to stunnel listening on mysql
server; which is redirecting traffic to the mysql port on localhost on the
server
client software connecting to localhost on client
For those who think I'm off the wall, here's what's driving me up it:
Had MySQL doing replication through stunnel for many months, flawlessly,
using MySQL 3.23.27 on master and slave. Now going to MySQL 3.23.37 on
master and 3.23.38 on slave, it's broken.
MySQL has some in
> > > > 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 i
> > > > 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]
On Sun, Jun 10, 2001 at 08:18:52PM -0500, Whit Blauvelt wrote:
>
> > > 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.
Right. That was a client error. The server is
> > 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
On Sun, Jun 10, 2001 at 03:27:44PM -0700, Jeremy Zawodny wrote:
> Does the master.info file on the slave contain accurate info? MySQL
> doesn't compare the contents of the file against your my.cnf. It
> creates the master.info file once and then considers it
> authoritative. This is neither well
> the slave. I'm using the same databases and same "my.cnf" as before, and
> invoking stunnel on both systems in the same way as when it was working
> before.
>
> If I do a "show processlist" on the slave server I see:
> "waiting to reconnect after a faile
er entering the password.
I'm trying to fix replication. It was working fine, but I rebuilt the
master, using 3.23.37-log in place of 3.23.27-beta-log, which still runs on
the slave. I'm using the same databases and same "my.cnf" as before, and
invoking stunnel on both system
