Am 10.09.2011 19:21, schrieb a.sm...@ukgrid.net:
> Hi Walter/all,
>
> ok nailed it, the issue is the default hosts.allow installed on FreeBSD,
> and specifically the last section that
> denies everything. By default it looks like this:
>
> # The rest of the daemons are protected.
> ALL : ALL
Hi Walter/all,
ok nailed it, the issue is the default hosts.allow installed on
FreeBSD, and specifically the last section that denies everything. By
default it looks like this:
# The rest of the daemons are protected.
ALL : ALL \
: severity auth.info \
: twist /bin/echo "Y
Am 10.09.2011 19:02, schrieb a.sm...@ukgrid.net:
> Quoting Reindl Harald :
>
>>
>> "You are not welcome to use mysqld from tau" is NOT from mysqld
>> remove your hosts.allow/hosts.deny crap and replace it with firewall-rules
>> if the problem goes away make a bugreport on BSD side becahuse this
Quoting Reindl Harald :
"You are not welcome to use mysqld from tau" is NOT from mysqld
remove your hosts.allow/hosts.deny crap and replace it with firewall-rules
if the problem goes away make a bugreport on BSD side becahuse this
is NOT a mysqld issue
I've already established that the is
Am 10.09.2011 18:52, schrieb a.sm...@ukgrid.net:
> Quoting walter harms :
>
>> restart it with the same parameter on the command line and see what happens
>> the server support a verbos option (never used) perhaps it will tell you
>> more.
>>
>
> I can start mysqld direct from the command line an
Quoting walter harms :
restart it with the same parameter on the command line and see what happens
the server support a verbos option (never used) perhaps it will tell
you more.
I can start mysqld direct from the command line and reproduce the
problem. I checked and it seems the verbose
Am 10.09.2011 17:32, schrieb a.sm...@ukgrid.net:
> Quoting walter harms :
>
>> I still do not see why it is restarting ... there must be something
>> watching is disappear.
>> Just to be sure, you do from a remote host: mysql -hHOST -ume -e "show
>> tables&quo
Quoting walter harms :
I still do not see why it is restarting ... there must be something
watching is disappear.
Just to be sure, you do from a remote host: mysql -hHOST -ume -e
"show tables" ?
long shot: Do you have LDAP, NIS or so enabled ?
Ok so made a script as you suggest
Quoting Reindl Harald :
Odd that, so I added a mysql specific line to the hosts.allow
who is using hosts.allow for protection instead a firewall in front
of the machine
or iptables (linux) / ipf (bsd)?
Its used for denyhosts as I mentioned.
As I said I can get it to restart just by doing
mysqld only ? (therefore the script)
Since my first idea was that something was calling the starter script
we will modify the dummy a bit.
#!/bin/sh
while true
do
echo "mysqld ..." | logger -t TEST
sleep 1m
done
This will make sure that you see a msg every minute. If you trigger
Am 10.09.2011 16:07, schrieb a.sm...@ukgrid.net:
> Then I thought, what if I have hosts.allow misconfigured and its wide open
> maybe a remote system is connecting and
> messing with it. But hosts.allow was correct (mysql not listed, so denied by
> the last all:all). I tested connecting
> from
Quoting walter harms :
What i found odd that your mysqld actualy restarts.
Do you have it in some runlevel ? if yes stop and see
what happens.
If this does not work simple move the mysqld out of he way
and replace it with a script like
#!/bin/sh
echo "mysqld ..." | logger -t TEST
see what ha
Am 10.09.2011 16:07, schrieb a.sm...@ukgrid.net:
> Ok, this is pretty odd but I have found the problem.
>
> Today I have repointed all applications to a different DB server, so I
> have been free to do any testing on the problem server.
>
> I started by dropping the databases one by one, droppe
Ok, this is pretty odd but I have found the problem.
Today I have repointed all applications to a different DB server, so I
have been free to do any testing on the problem server.
I started by dropping the databases one by one, dropped em all and the
issue persisted.
I stopped crond, even t
i bet if he stops crond the problem is going away
anyways i have enough of this thread after "the part for the shutdown"
because if peopole are way too stupid to provide full logs (normally
in the first post) even after requested multiple times they should
learn their lessons the hard way...
This was me restarting MySQL as was requested by Suresh...
Quoting "Singer X.J. Wang" :
This doesn't look like a MySQL issue. Verify that there's no rogue scripts
that shutdowns MySQL...
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/
can you check for any table crashes in the db by using mysqlcheck.
and enable the general log for the database.
On Fri, Sep 9, 2011 at 10:37 PM, wrote:
> No need for that really is there? I posted what was requested.
> The part for the shutdown:
>
> 110909 17:27:31 InnoDB: Starting shutdown...
No need for that really is there? I posted what was requested.
The part for the shutdown:
110909 17:27:31 InnoDB: Starting shutdown...
110909 17:27:32 InnoDB: Shutdown completed; log sequence number 1589339
110909 17:27:32 [Note] /usr/local/libexec/mysqld: Shutdown complete
110909 17:27:32 mys
jesus christ can you post a WHOLE log
this is only a normal start, there is no single line about stop
Am 09.09.2011 18:30, schrieb a.sm...@ukgrid.net:
> Yep, but its basically identical to the info in the logs when its restarting
> itself. I have upgraded to MySQL 5.5
> as of yesterda
Yep, but its basically identical to the info in the logs when its
restarting itself. I have upgraded to MySQL 5.5 as of yesterday, so
the error info differs due to the version now. Here is the log output:
110909 17:27:35 mysqld_safe Starting mysqld daemon with databases from
/var/db/mysql
can you remove it from service and start it normally using mysqld_safe with
log warnings enabled in the cnf file.
On Fri, Sep 9, 2011 at 4:16 PM, wrote:
> Hi,
>
> that really is the complete error log, that exact same info gets repeated
> over and over, there is zero in the syslog and I get thi
Hi,
that really is the complete error log, that exact same info gets
repeated over and over, there is zero in the syslog and I get this
behaviour when running with no my.cnf (I do obviously have one but I
tried without and it I still see the prob, so that probably makes
things easier fr
erday the MySQL Daemons keep restarting every 7 mins or so on
> one of my FreeBSD servers. The only work carried out recently related to
> MySQL on this server was to temporarily disable replication (its a slave) of
> one DB, and then re-enable it (via restore of data and updating the log file
&
Hi,
as of yesterday the MySQL Daemons keep restarting every 7 mins or
so on one of my FreeBSD servers. The only work carried out recently
related to MySQL on this server was to temporarily disable replication
(its a slave) of one DB, and then re-enable it (via restore of data
and
bject:
Re: Serialization failure: 1213 Deadlock found when trying to get lock;
try restarting transaction
Try to run
SHOW ENGINE INNODB STATUS;
Near the top there will be some information on the latest deadlock.
That might help you to understand what is deadlocking. Sometimes
changing the
li_lock l ON l.object_id = q.queue_id AND l.lock_type =
'parse'
WHERE l.object_id IS NULL
AND q.status = 'parse'
ORDER BY q.file_size ASC, q.created ASC, q.queue_id ASC
LIMIT 1
However, as I execute this query several times each minute from
different
applications, I fr
LECT $LOCK_ID, q.queue_id, 'parse', DATE_ADD(NOW(), INTERVAL 1 HOUR)
>>> FROM queue q
>>> LEFT JOIN cli_lock l ON l.object_id = q.queue_id AND l.lock_type =
>>> 'parse'
>>> WHERE l.object_id IS NULL
>>> AND q.status = 'parse&#x
d IS NULL
AND q.status = 'parse'
ORDER BY q.file_size ASC, q.created ASC, q.queue_id ASC
LIMIT 1
However, as I execute this query several times each minute from different
applications, I frequently get these messages:
DB ERROR: SQLSTATE[40001]: Serialization failure: 1213 Deadlock found
fferent
> applications, I frequently get these messages:
>
> DB ERROR: SQLSTATE[40001]: Serialization failure: 1213 Deadlock
found when
> trying to get lock; try restarting transaction
>
> Am I writing my query wrong or expecting behavior th
ile_size ASC, q.created ASC, q.queue_id ASC
> > LIMIT 1
> >
> > However, as I execute this query several times each minute from different
> > applications, I frequently get these messages:
> >
> > DB ERROR: SQLSTATE[40001]: Serialization failure: 1213 Deadlock found
.file_size ASC, q.created ASC, q.queue_id ASC
> LIMIT 1
>
> However, as I execute this query several times each minute from different
> applications, I frequently get these messages:
>
> DB ERROR: SQLSTATE[40001]: Serialization failure: 1213 Deadlock found when
> trying t
on failure: 1213 Deadlock found when
trying to get lock; try restarting transaction
Am I writing my query wrong or expecting behavior that MySQL doesn't
support?
-- Dante
Hi,
On Wed, Jan 14, 2009 at 3:00 PM, John Daisley
wrote:
> Hi,
>
> Probably a simple question for someone who knows :)
>
> Is there a way to force MySQLD to restart after it has finished processing
> all current transactions?
>
> I seem to remember from the bit of Oracle work I did in the past w
Read the mysqld man pages about what it does with kill -X signals.
One of them may mean "graceful stop"
Or not.
If there is one, you'd still have to figure out how to tie that into a re-boot
or whatever for updates.
Sounds like a perfectly reasonable feature request if you find nothin
Hi,
Probably a simple question for someone who knows :)
Is there a way to force MySQLD to restart after it has finished processing
all current transactions?
I seem to remember from the bit of Oracle work I did in the past we could
do a Transactional Restart in Oracle 10g which caused the server
I'm getting
2008-09-11 10:42:25 [MgmSrvr] ALERT-- Node 1: Node 3 Disconnected
2008-09-11 10:42:25 [MgmSrvr] ALERT-- Node 3: Forced node shutdown
completed. Occured during startphase 4. Caused by error 2306: 'Pointer too
large(Internal error, programming error or missing error message, p
Thanks Mike!
Le 2008-05-22 à 17:13, Mike a écrit :
If your taking a dump of the master open two windows. Don't close
either
In the first lock all tables with FLUSH ALL TABLES WITH READ LOCK; &
master status;
Then in the second window procedure with mysqldump.
The exact syntax was FLUSH
This is a classic error.
You just reconfigurate the parameter master_log_file and master_log_pos
.Good luck.
On Fri, May 23, 2008 at 5:13 AM, Mike <[EMAIL PROTECTED]> wrote:
> On Thu, May 22, 2008 at 10:41 AM, François Beausoleil <
> [EMAIL PROTECTED]>
> wrote:
>
> > Hi all!
> > I must be stupid
On Thu, May 22, 2008 at 10:41 AM, François Beausoleil <[EMAIL PROTECTED]>
wrote:
> Hi all!
> I must be stupid or something. I can't find what my problem is.
>
> I searched this list, and did find a couple of hits, but nothing that
> seemed fully relevant. This one in particular was interesting:
Hi all!
I must be stupid or something. I can't find what my problem is.
I searched this list, and did find a couple of hits, but nothing that
seemed fully relevant. This one in particular was interesting: http://lists.mysql.com/mysql/212863
I have a single master (server-id=1) and a single
I'm rebuilding a server that is a slave to our primary. At this
point in the game, I can no longer access anything on the slave server
(its main drive is being rebuild). However, I do have a full rsync of
the /var/lib/mysql folder that was on it (this rsync was done AFTER
MySql was prope
Ravi,
Got it, thanks!!
Ben
Ravi Prasad wrote:
Make sure each of the replication slaves uses different server_id.
--Ravi
Ben Clewett wrote:
MySql,
I am running 5.0.41 on a master and four replication slaves, all 64
bit Linux.
In the error.log on all four replication servers I keep seei
Make sure each of the replication slaves uses different server_id.
--Ravi
Ben Clewett wrote:
MySql,
I am running 5.0.41 on a master and four replication slaves, all 64
bit Linux.
In the error.log on all four replication servers I keep seeing:
070626 8:34:23 [Note] Slave: received end pac
MySql,
I am running 5.0.41 on a master and four replication slaves, all 64 bit
Linux.
In the error.log on all four replication servers I keep seeing:
070626 8:34:23 [Note] Slave: received end packet from server, apparent
master shutdown:
070626 8:34:23 [Note] Slave I/O thread: Failed readi
> - Original Message -
> From: "Jay Paulson" <[EMAIL PROTECTED]>
> To:
> Sent: Friday, September 08, 2006 9:51 PM
> Subject: Restarting MySQL on Solaris 8?
>
>>A couple questions since I'm not a Solaris person I really don't know how
&g
ve DB Team" <[EMAIL PROTECTED]>
To: "Jay Paulson" <[EMAIL PROTECTED]>;
Sent: Monday, September 11, 2006 9:35 AM
Subject: Re: Restarting MySQL on Solaris 8?
> Hi,
>
> Try
>
> /usr/local/bin/mysqld_safe
> to start MySQL
>
> /usr/local/bi
Hi,
Try
/usr/local/bin/mysqld_safe
to start MySQL
/usr/local/bin/mysqld_safe &
to start MySQL as a background process.
Thanks.
ViSolve DB Team.
- Original Message -
From: "Jay Paulson" <[EMAIL PROTECTED]>
To:
Sent: Friday, September 08, 2006 9:51 PM
Subject:
A couple questions since I'm not a Solaris person I really don't know how to
do the following and was hoping that someone could help me out (Google isn't
much help on this).
How does one start the MySQL daemon on Solaris 8? (it's running MySQL
3.23.49)
How does one tell Solaris 8 to start the MyS
Yes, that was the problem, the my.cnf file was missing, replace it, restarted
and all is well :)
thx's
Mike
- Original Message -
From: "Heikki Tuuri" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, March 22, 2006 2:10 AM
Subject: Re: Problem restarting server
Mike,
- Original Message -
From: ""Mike Blezien"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Wednesday, March 22, 2006 3:42 AM
Subject: Problem restarting server
Hello,
we had to reboot our server and now we can't get MySQL starte
Hello,
we had to reboot our server and now we can't get MySQL started, in the error log
it states:
==
060321 19:34:13 mysqld started
060321 19:34:13 [Warning] Asked for 196608 thread stack, but got 126976
InnoDB: Error: log file ./ib_logfile0 is of
, and I don't
> really understand how it can happen.
> I've strip down an example, that does basically :
>
> BEGIN;
> SELECT id FROM ttt WHERE id=3D7 FOR UPDATE;
> INSERT INTO ttt(id) VALUES (7);
> DELETE FROM ttt WHERE id=3D7;
> COMMIT;
>
> I run 10
NTO ttt(id) VALUES (7);
DELETE FROM ttt WHERE id=7;
COMMIT;
I run 10 instances of the program in parallel and I get the error :
Deadlock found when trying to get lock; try restarting transaction.
The isolation level is the default one.
My understanding of the SELECT ... FOR UPDATE is that I should no
Hello.
It looks like the path is wrong. Find out the correct value
from /etc/init.d/mysql file and put it in the configuration file.
>Hi,
>I check my.cnf configure file. I find Pid-file path is
>/var/run/mysqld/mysqld.pid, but I couldn't find mysqld directory in
>/var/run and couldn't
Hello.
Probably mysqld_safe uses wrong values for directories. Possible
solution is to store the correct paths in configuration file, and
if it is situated not in standard location, launch mysqld_safe with
--defaults-file=path_to_config_file. Or use command line options for
mysqld_safe. Chec
Dear there,
After install mysql 4.1.12 by using rpm, I have some problems to restart server
after shutting down it. When I use "mysqld_safe" try to restart, it give me
error as follws:
Starting mysqld daemon with databases from /var/lib/mysql
STOPPING server from pid file /var/run/mysqld/mysqld
[EMAIL PROTECTED] wrote:
So this would imply that you cannot simply stop/start a slave server -
instead, I would need to write a wrapper script that stops the slave
using "STOP SLAVE", and at next startup, read the master.info file to
find out where it left off, and then issue a "CHANGE MASTER TO..
ave. Which MySQL version or release on what O/S?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, December 20, 2004 9:26 AM
To: [EMAIL PROTECTED]
Subject: RE: Problems with replication restarting
So this would imply that you cannot simply stop/start a sl
42
To: Round, Mark - CALM Technical <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: Re: Problems with replication restarting
[EMAIL PROTECTED] wrote:
>However, when I restart the slave (through init scripts, or when
>rebooting the server etc.), instead of continuing on from where i
[EMAIL PROTECTED] wrote:
However, when I restart the slave (through init scripts, or when
rebooting the server etc.), instead of continuing on from where it left
off, it appears to start again from the beginning. This is confirmed by
watching the value of Relay_Log_Pos from SHOW SLAVE STATUS\G.
Hi all,
I originally posted this to the replication list, but as I haven't yet
received a response, I thought I'd try my luck here...
I'm having some troubles with replication, in particular restarting a
slave. I'm using MySQL 4.0.22 for the slave, and 4.0.21 as the maste
Yeah, that's exactly what I figured out.. We do record the SHOW SLAVE
STATUS settings before each backup.
I find we need individual tables restored far more frequently than
whole databases. It's much easier using mysqldump and perl to dump
each table in text to its own file. This is especially tru
On Friday 08 October 2004 19.01, Gary Richardson wrote:
> Hey guys,
>
> I'm running a master/slave setup with v4.0.20. There are a hand full
> of databases being replicated. For backups, we stop replication on the
> slave and pull a text dump using mysqldump. I also record a 'SHOW
> SLAVE STATUS' f
Hey guys,
I think I have this figured out. I'm just doing some testing. If I
manually recreate the master.info file, it sort of works, but I get
the following error from the IO thread:
Error reading relay log event: slave SQL thread aborted because of I/O error
So, instead of manually creating t
anner
Systems Administrator
Rowe/AMi
"Gary Richardson" <[EMAIL PROTECTED]>
10/08/2004 02:04 PM
Please respond to Gary Richardson
To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
cc: [EMAIL PROTECTED]
Subject:Re: Restarting Rep
edure.
>
>
> Regards,
>
> Scott Tanner
> Systems Administrator
> Rowe/AMi
>
>
>
>
> "Gary Richardson" <[EMAIL PROTECTED]>
>
> 10/08/2004 01:01 PM
> Please respond to Gary Richardson
>
> To:
some knowledge on the correct procedure.
Regards,
Scott Tanner
Systems Administrator
Rowe/AMi
"Gary Richardson" <[EMAIL PROTECTED]>
10/08/2004 01:01 PM
Please respond to Gary Richardson
To: [EMAIL PROTECTED]
cc:
Subject:Restarting Replicat
Hey guys,
I'm running a master/slave setup with v4.0.20. There are a hand full
of databases being replicated. For backups, we stop replication on the
slave and pull a text dump using mysqldump. I also record a 'SHOW
SLAVE STATUS' from the time of the backup.
My replica server crashed last night.
is there a way to turn on log_slave_updates on a server without having to restart it?
-L
Luke Crouch
918-461-5326
[EMAIL PROTECTED]
cause when it happened
originally.
-Original Message-
From: Dathan Vance Pattishall [mailto:[EMAIL PROTECTED]
Sent: Monday, September 13, 2004 2:49 PM
To: Tucker, Gabriel; 'Mysql General (E-mail)'
Subject: RE: Innodb Message "Lock wait timeout exceeded; Try restarting
tran
t; To: Mysql General (E-mail)
> Subject: Innodb Message "Lock wait timeout exceeded; Try restarting
> transaction"
>
> Hello All
>
> V4.0.16 on Sun Sparc 5.8
> Innodb_lock_wait_timeout = 50.
>
> A application using jboss got this error a few days ago. The
Hello All
V4.0.16 on Sun Sparc 5.8
Innodb_lock_wait_timeout = 50.
A application using jboss got this error a few days ago. The SQL being used, AFAIK,
was a simple delete from table where date = {date}.
I am trying to determine why this happened. Searching back in the MySQL lists
archives, I
Hi,
I'm running MySQL 4.0.17-nt, and for some reason the my.cnf file in my
C:\ directory got renamed around the time we rebooted the server last.
Now the global variable innodb_buffer_pool_size is set to a small value,
and my queries are taking a long time to execute. I don't want to
restart the
How would the table survive a reset/reboot ?
If you need it to be persistant, use a regular table and lots of system
ram for cache.
m0llbuz_ wrote:
Hi!
I wonder if I can somehow preserve the table rows in a memory table when I restart the
MySQL server?
I've read the documentation about memory ta
Hi!
I wonder if I can somehow preserve the table rows in a memory table when I restart the
MySQL server?
I've read the documentation about memory tables, and it states that I can populate the
table at startup, but it doesn't say if I can store the table rows at shutdown in a
file. Maybe I can d
I did similar insert minutes ago with no problems. Now I try to do the same
insert just with differnet parameters and got such error message.
insert into users(first_name, last_name) values('john', 'smith');
ERROR 1205: Lock wait timeout exceeded; Try restarting transaction
"Steven Hentschel" <[EMAIL PROTECTED]> wrote:
> Can anyone tell me why the following behaviour occurs. There is no change to
> the contents of tables_priv after adding the table grant to some_user before
> and after the database restart. The database has been upgraded from 3.23 to
> 4.1.1 and the
>
Can anyone tell me why the following behaviour occurs. There is no change to
the contents of tables_priv after adding the table grant to some_user before
and after the database restart. The database has been upgraded from 3.23 to
4.1.1 and the
mysql_fix_privilege_tables script has been run.
# mysq
I am using tables INNODB.
After one query, the MySQL does not liberate the LOCK, and when I try to
execute same query it appears the message.
#1205 - Lock wait timeout exceeded; Try restarting transaction
whait urgently one helps. thanks, Bruno
--
MySQL General Mailing List
For list
Hello all,
Please forgive what seems like a basic question, but I'm noticing that
my mysql server (4.0.16) is restarting every couple of days. I recently
upgraded from 3.23.53, and it was doing something similar. Problem is
that I'm not sure how to go about diagnosing this proble
> truncate table_name
> does both in one statement. And even optimizes the table (frees up
> unused disk space). However take care that you cannot rollback this DDL.
Wow. Learn something new every day! :p
Thanks for the tip, Rudy!
Chris
--
MySQL General Mailing List
For list archives: http://
: Krasimir_Slaveykov; Miroslav I.; [EMAIL PROTECTED]
Subject: Re: auto number primary key - restarting
> Easiest way to do what you want is to make this:
> 1.SHOW CREATE TABLE TableName
> and copy SQL
> 2. DROP TABLE TableName
> 3. CREATE TABLE - with SQL copied in 1.
Actually, the easiest
> Easiest way to do what you want is to make this:
> 1.SHOW CREATE TABLE TableName
> and copy SQL
> 2. DROP TABLE TableName
> 3. CREATE TABLE - with SQL copied in 1.
Actually, the easiest way to do this (assuming *all*
records have been deleted) is:
UPDATE table_name SET auto_increment_field = 0;
Hello Miroslav,
Tuesday, July 15, 2003, 3:10:10 PM, you wrote:
Easiest way to do what you want is to make this:
1.SHOW CREATE TABLE TableName
and copy SQL
2. DROP TABLE TableName
3. CREATE TABLE - with SQL copied in 1.
MI> Hi,
MI> is there an SQL command for making a primary key (auto numbe
Please check the history on this list. There are numerous answers to
this problem.
Cheers
/rudy
-Original Message-
From: Miroslav I. [mailto:[EMAIL PROTECTED]
Sent: dinsdag 15 juli 2003 14:10
To: [EMAIL PROTECTED]
Subject: auto number primary key - restarting
Hi,
is there an SQL
"Miroslav I." <[EMAIL PROTECTED]> wrote:
>
> is there an SQL command for making a primary key (auto number key) to start
> numbering from beginning after deleting all the records from the table.
For MyISAM tables you can use ALTER TABLE:
http://www.mysql.com/doc/en/ALTER_TABLE.html
--
delete all records by this command:
TRUNCATE TABLE `mytable`;
- Original Message -
From: "Miroslav I." <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 15, 2003 8:10 AM
Subject: auto number primary key - restarting
Hi,
is there an SQL command fo
Hi,
is there an SQL command for making a primary key (auto number key) to start numbering
from beginning after deleting all the records from the table.
thanks
: Ian Collins [mailto:[EMAIL PROTECTED]
Sent: Friday 11 July 2003 00:59
To: [EMAIL PROTECTED]
Subject: Turn off log-bin without restarting database
I want to turn off replication logging (we have stopped using
replication) without shutting down the server.
(The only downtime allowed is about 2am,
CHANGE MASTER TO MASTER_LOG_HOST='', MASTER_LOG_POS='',
MASTER_LOG_PORT='';
SLAVE STOP;
SHOW SLAVE STATUS;
-->-Original Message-
-->From: Ian Collins [mailto:[EMAIL PROTECTED]
-->Sent: Thursday, July 10, 2003 4:59 PM
-->To: [EMAIL PROTECTED]
-->
I want to turn off replication logging (we have stopped using
replication) without shutting down the server.
(The only downtime allowed is about 2am, and I needmy sleep).
I couldn't see how to do this in the docs. Is it possible?
The variables in my /etc/my.cnf are,
log-bin
server-id=1000
binlo
I recently updated from MySQL 3.23-55 to 4.0.12 now my mysql log keeps
showing lots of restarts. I've searched around but have not found anything.
I upgraded the 3.x rpm's using rpm -Uvh MySQL* and did the following rpm's.
I also followed the upgtrade doc on the MySQL page and ran the
mysql_fix_p
On Sun, Aug 04, 2002 at 11:45:27AM +0200, Hussein Morsy wrote:
> Is it possible to reload changes of my.cnf without restarting the
> Server ?
> The reason is, that i want to toggle the log-file output of mysqld.
Some changes are going into MySQL 4.0.3 to allow many server settings to
b
Is it possible to reload changes of my.cnf without restarting the
Server ?
The reason is, that i want to toggle the log-file output of mysqld.
Thanks
-
Before posting, please check:
http://www.mysql.com/manual.php (the
Alex,
Tuesday, May 21, 2002, 3:43:16 PM, you wrote:
AP> I was wondering if anyone knew the "proper" way to restart MySQL on OS X?
AP> I did mysqladmin -p shutdown then safe_mysqld...is this the same as
AP> if the machine started up?
mysqladmin shutdown - takes down your MySQL server. Using saf
At 9:20 AM -0400 5/21/02, Reid Sutherland (mysql) wrote:
>Alex Pilson wrote:
>>I was wondering if anyone knew the "proper" way to restart MySQL on OS X?
>>
>>I did mysqladmin -p shutdown then safe_mysqld...is this the same as
>>if the machine started up?
>
>Not exactly the same. But for intents
Alex Pilson wrote:
> I was wondering if anyone knew the "proper" way to restart MySQL on OS X?
>
> I did mysqladmin -p shutdown then safe_mysqld...is this the same as if
> the machine started up?
Not exactly the same. But for intents and purposes it does what you want.
If you want to truly ma
There is a link for mysql-startupitem.pkg.tar.gz on
http://www.entropy.ch/software/macosx/mysql/
This will install the startup stuff needed to do what you want.
On 5/21/2002 5:43 AM, "Alex Pilson" <[EMAIL PROTECTED]> wrote:
> I was wondering if anyone knew the "proper" way to restart MySQL on O
alex, chuck a copy of phpMyAdmin onto the machine.
edit the phpMyAdmin configuration file to your username and password and
load it up on the loopback address.
you should find a button saying 'reload mysql' on the page.
phpMyAdmin rules!!!
cheers,
jake
on 21/5/02 1:43 pm, Alex Pilson at [E
I was wondering if anyone knew the "proper" way to restart MySQL on OS X?
I did mysqladmin -p shutdown then safe_mysqld...is this the same as
if the machine started up?
--
<--->
Alex Pilson
FlagShip Interactive, Inc.
[EM
1 - 100 of 132 matches
Mail list logo
