I've had some very weird issues that I've posted about here in the
past, but no one was able to help. I posted a bug report on mysql.com
and have received some advice on how to suppress the problems I was
having. The problem seems to be exploited when running a slave server
on OSX 10.3.x; alt
On Dec 05, 2003, at 17:00, Lost Idols wrote:
A newbie here, with a simple question (I guess).
I just installed MySQL on my OS X 10.2
But failed pretty quick. Please help me... I wanna get started.
This it what it looks like after following the description in the
ReadMe file.
Last login: Fri Dec
he same file even), so I'm sure that the problem is not
starting from the master. The only difference between the two slave
servers is the OS. The slave that is 'broken' is on Mac OS X 10.3
Server and the one that works is Mac OS X 10.1 Server.
On Dec 01, 2003, at 03:42,
On Dec 01, 2003, at 14:35, Elton wrote:
So, maybe it was a bug that was fixed in 4.0.16; how do I upgrade to
v4.0.16? I'm sort of a novice with MySQL and am using what was
pre-installed with Apple's Panther_server -- have never installed it
myself.
Elton,
I've had some weird issues with the d
On Dec 01, 2003, at 18:00, Jared Klett wrote:
b.) Is there a proven way to backup MySQL databases that have to be up
and running 24/7/365?
Well, I don't know so much about a 'proven' way - but I use replication
on another server and it works pretty good for me. When i want to make
a static bac
One of my server is a slave to another. The slave server's host.err
file is getting filled with blocks like this:
Status information:
Current dir: /usr/local/mysql/var/
Running threads: 0 Stack size: 65536
Current locks:
lock: 82268c:
key_cache status:
blocks used:15
not flushed:
First off, I'd like to say hello. I just signed up for the list today.
I'm having some weird things happen on my slave server. I'll give more
details in a second, but to sum it up, its creating thousands of
'host-relay-bin' files and the 'host.err' file is getting filled with
what looks like
