The \! command is specific to the mysql client and executes locally,
making it useless for this purpose.
If you don't have access to 5.0.41+ and the database you are querying is a
replicated slave, you can use the 'server_id' variable to tie the server
to an actual hostname (SHOW VARIABLES LIKE
What I know is that:
Heartbeat with MySQL uses two IP's. That of the server, and that of the
resource MySql. The former is fixed, the latter moves with MySQL when
it's moved to another server.
The one I need is the hostname of the physical server, not the resource.
I've installed 5.0.41
There's a 'report-host' option that can be set in the conf file to
mask the host name. Sounds like this may be set.
If you want to get the server's actual host name from within mysql,
how about running a system command:
mysql \! hostname;
or
mysql \! cat /etc/hostnames;
Dear MySQL,
I'm running 5.0.26 through Heartbeat. Which seems to work well, even as
a replication slave and Heartbeat continously stopping and starting the
server.
The Heartbeat moves MySQL around from server to server when a failure
occures. I am trying to find a way for MySQL to report
Hi,
Ben Clewett wrote:
Dear MySQL,
I'm running 5.0.26 through Heartbeat. Which seems to work well, even as
a replication slave and Heartbeat continously stopping and starting the
server.
The Heartbeat moves MySQL around from server to server when a failure
occures. I am trying to find a
Ben Clewett wrote:
Dear MySQL,
I'm running 5.0.26 through Heartbeat. Which seems to work well, even as
a replication slave and Heartbeat continously stopping and starting the
server.
The Heartbeat moves MySQL around from server to server when a failure
occures. I am trying to find a way
Baron,
Thanks for the fast reply.
I like the idea of piping in the servername to a small table on startup.
Since this will only change on startup, sounds like an excellent idea.
Or I may upgrade to above 5.0.41...
Regards,
Ben
Baron Schwartz wrote:
Hi,
Ben Clewett wrote:
Dear MySQL,
Gerald L. Clark wrote:
Ben Clewett wrote:
Dear MySQL,
I'm running 5.0.26 through Heartbeat. Which seems to work well, even
as a replication slave and Heartbeat continously stopping and starting
the server.
The Heartbeat moves MySQL around from server to server when a failure
occures. I
Baron Schwartz wrote:
Gerald L. Clark wrote:
Ben Clewett wrote:
Dear MySQL,
I'm running 5.0.26 through Heartbeat. Which seems to work well, even
as a replication slave and Heartbeat continously stopping and
starting the server.
The Heartbeat moves MySQL around from server to server
Gerald L. Clark wrote:
Baron Schwartz wrote:
Gerald L. Clark wrote:
Ben Clewett wrote:
Dear MySQL,
I'm running 5.0.26 through Heartbeat. Which seems to work well,
even as a replication slave and Heartbeat continously stopping and
starting the server.
The Heartbeat moves MySQL around
10 matches
Mail list logo
