nt: Monday, February 04, 2013 4:35 AM
To: Larry Martell
Cc: wha...@bfs.de; mysql
Subject: Re: log sequence number InnoDB: is in the future!?
2013/2/3 Larry Martell
>
>
> We also ended up dropping the database and restoring from dumps.
> However all recent dumps ended up having a similar co
2013/2/3 Larry Martell
>
>
> We also ended up dropping the database and restoring from dumps.
> However all recent dumps ended up having a similar corruption and we
> were still getting the same errors. We had to go back to an October
> dump before it would come up cleanly. And our db is fairly la
Am 03.02.2013 15:30, schrieb Larry Martell:
> We also ended up dropping the database and restoring from dumps.
> However all recent dumps ended up having a similar corruption and we
> were still getting the same errors. We had to go back to an October
> dump before it would come up cleanly. And o
On Sun, Feb 3, 2013 at 7:23 AM, walter harms wrote:
>
>
> Am 02.02.2013 01:34, schrieb Larry Martell:
>> On Mon, Jan 28, 2013 at 5:01 AM, walter harms wrote:
>>> hi list,
>>>
>>> i am using mysql 5.1.53.
>>> after a crash i have the follwing error in my log:
>>>
>>> 130128 10:45:25 InnoDB: Error
Am 02.02.2013 01:34, schrieb Larry Martell:
> On Mon, Jan 28, 2013 at 5:01 AM, walter harms wrote:
>> hi list,
>>
>> i am using mysql 5.1.53.
>> after a crash i have the follwing error in my log:
>>
>> 130128 10:45:25 InnoDB: Error: page 61 log sequence number 0 2871649158
>> InnoDB: is in the
On Mon, Jan 28, 2013 at 5:01 AM, walter harms wrote:
> hi list,
>
> i am using mysql 5.1.53.
> after a crash i have the follwing error in my log:
>
> 130128 10:45:25 InnoDB: Error: page 61 log sequence number 0 2871649158
> InnoDB: is in the future! Current system log sequence number 0 2494349480
Am 28.01.2013 16:18, schrieb Andrew Moore:
> So this isn't production - well just rebuild it from a backup? It's a pain
> in the rear to get the lsn aligned again through data creation/removal but
> if it's a system critical instance without possible downtime you've got
> some work to do...
>
t
Am 28.01.2013 16:01, schrieb walter harms:
>
>
> Am 28.01.2013 14:40, schrieb Andrew Moore:
>> Dump and reload or use some scripting to create and drop some fake data to
>> increase the lsn towards the 'future' value.
>>
>> http://dba.stackexchange.com/questions/8011/any-better-way-out-of-mysql
Am 28.01.2013 14:40, schrieb Andrew Moore:
> Dump and reload or use some scripting to create and drop some fake data to
> increase the lsn towards the 'future' value.
>
> http://dba.stackexchange.com/questions/8011/any-better-way-out-of-mysql-innodb-log-in-the-future
>
For now i tend to soluti
So this isn't production - well just rebuild it from a backup? It's a pain
in the rear to get the lsn aligned again through data creation/removal but
if it's a system critical instance without possible downtime you've got
some work to do...
On Mon, Jan 28, 2013 at 2:21 PM, walter harms wrote:
>
Am 28.01.2013 15:01, schrieb Manuel Arostegui:
> 2013/1/28 walter harms
>
>> hi list,
>>
>> i am using mysql 5.1.53.
>> after a crash i have the follwing error in my log:
>>
>> 130128 10:45:25 InnoDB: Error: page 61 log sequence number 0 2871649158
>> InnoDB: is in the future! Current system l
2013/1/28 walter harms
> hi list,
>
> i am using mysql 5.1.53.
> after a crash i have the follwing error in my log:
>
> 130128 10:45:25 InnoDB: Error: page 61 log sequence number 0 2871649158
> InnoDB: is in the future! Current system log sequence number 0 2494349480.
> InnoDB: Your database may
Dump and reload or use some scripting to create and drop some fake data to
increase the lsn towards the 'future' value.
http://dba.stackexchange.com/questions/8011/any-better-way-out-of-mysql-innodb-log-in-the-future
On Mon, Jan 28, 2013 at 12:01 PM, walter harms wrote:
> hi list,
>
> i am usi
Have a look on it:
mysql> show variables like '%slow%';
+-+--+
| Variable_name | Value|
+-+--+
| log_slow_queries| OFF |
| slow_launch_time
Hello Stephen,
Did u try this ??
mysql> show global variables like '%log_output%';
+---+---+
| Variable_name | Value |
+---+---+
| log_output| FILE |
+---+---+
If only the log_output is FILE, then the slow queries will get logged in the
log.
m
At 03:58 PM 5/7/2010, you wrote:
At 12:04 PM 5/7/2010, Stephen Sunderlin wrote:
Can't get slow querys to log. Does this not work in myisam?
Sure it does. Have you tried:
slow_query_time = 1
Mike
Sorry, ignore that previous message. (Serves me right for trying to
remember it from the top
At 12:04 PM 5/7/2010, Stephen Sunderlin wrote:
Can't get slow querys to log. Does this not work in myisam?
Sure it does. Have you tried:
slow_query_time = 1
Mike
*snip*
[mysqld]
log-slow-queries = /var/log/mysql/mysql-slow.log
long_query_time = 1
*snip*
restarted mysqld - no log.
Creat
Ah! Thanks - I see. 5.1.39
Actually I did look i the manual, but failed to note the differences between <
5.1.29 and > 5.1.29
I was using the syntax for < 5.1.29.
Now I am using the correct syntax in /etc/my.cnf
$ grep general /etc/my.cnf
general_log=1
general_log_file=/var/log/mysql/mysql.l
Sorry can't remember what version you said you were using; if you have a
version prior to 5.1.29 to log all queries enter the following in the
[mysqld] section of your my.cnf
log = /path/to/logfile/filename.log
Remembering that the path you specify must be writeable by the server.
If you are on
Hello Mauricio,
Mauricio Tellez wrote:
Hi, I'm trying to debug a stored procedure. This SP has a few queries and
also call another SP. I'm starting mysql with the --log=my_queries.log but I
found that mysql only log the "call my_sp(param1, param2)" but don't log any
query inside my_sp neither lo
Isn't the choice in the the "type" col of Explain a "full index scan"
rather than a full table scan ?My understanding was that the "ALL" stands
for "full table scan ".
Thanks,
Mariella
On Tue, Jul 29, 2008 at 11:03 AM, Mary Bahrami <[EMAIL PROTECTED]>wrote:
> The optimizer made the correct ch
The optimizer made the correct choice when it did a full table scan
where there were few rows...I wouldn't want to override the optimizer in
this case.
Check that you updated statistics between these two queries
(information_schema.statistics.cardinality).
-Original Message-
From: MySQLFo
>-Original Message-
>From: Pedro [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, July 23, 2008 6:48 PM
>To: Dan Nelson
>Cc: mysql@lists.mysql.com
>Subject: Re: Log
>
>I need to pass the user of my application pro bank.
>I want to log the user's application a
In the last episode (Jul 23), Pedro said:
> I need to pass the user of my application pro bank. I want to log the
> user's application and value of new fields or fields updated. To then
> have audit of who did what.
>
> It is really necessary to create a trigger and a table of log for
> each table
I need to pass the user of my application pro bank.
I want to log the user's application and value of new fields or fields
updated. To then have audit of who did what.
It is really necessary to create a trigger and a table of log for each
table that want to monitor?
What do you suggest me?
Sorry, not specified what I wanted to get inside the trigger. I would
pick who is running the operation.
Pedro Belmino escreveu:
I do a system log of their log everything that is done(INSERTS, UPDADES
and DELETES). Okay, can be done with trigger. But I need to know who
performed the operation.
In the last episode (Jul 23), Pedro Belmino said:
> I do a system log of their log everything that is done(INSERTS, UPDADES
> and DELETES). Okay, can be done with trigger. But I need to know who
> performed the operation. How can I get get it inside the trigger?
Try the USER() or CURRENT_USER() fu
Nice reply.
On Fri, Apr 4, 2008 at 5:19 PM, Krishna Chandra Prajapati <
[EMAIL PROTECTED]> wrote:
> Master-->Slave1/Master>Slave2 (Chain 1
> to 1)
> Slave1 should have --log_slave_updates
>
>
> Master->Slave1/Slave2/Slave3.
>
thank u very much
On 4/4/08, Krishna Chandra Prajapati <[EMAIL PROTECTED]> wrote:
>
> Master-->Slave1/Master>Slave2 (Chain 1
> to 1)
> Slave1 should have --log_slave_updates
>
>
> Master->Slave1/Slave2/Slave3.
> (Parallel 1 to
Master-->Slave1/Master>Slave2 (Chain 1
to 1)
Slave1 should have --log_slave_updates
Master->Slave1/Slave2/Slave3.
(Parallel 1 to many)
--log_slave_updates is not required
If all the slaves are in a single chain model then --
so, we should not have --log-slave-update on slaves on setup with one master
and multiple slaves...right.
regards
anandkl
On 4/4/08, Krishna Chandra Prajapati <[EMAIL PROTECTED]> wrote:
>
> In case of master is down. Slave 1 has to be made as master and
> --log_slave_updates has to be removed. S
In case of master is down. Slave 1 has to be made as master and
--log_slave_updates has to be removed. Slave2 will act as slave. There will
be no "duplicate key"
On Thu, Apr 3, 2008 at 1:02 PM, Ananda Kumar <[EMAIL PROTECTED]> wrote:
> But, it also says, that if slave1 is made master and if log-s
But, it also says, that if slave1 is made master and if log-slave-update is
set on it, then
slave2 might receive data that it might have arleady got from the old
master, which might cause errors like "duplicate keys" etc.
On 4/3/08, Krishna Chandra Prajapati <[EMAIL PROTECTED]> wrote:
>
> Hi,
> T
Hi,
There is nothing that, you can not enable log_slave_updates on slave.
Basically, it is useful in a situation when you have 1 master and 2 or more
slave in chain series. In this model 1st slave server should work as master
as well as slave. So, log_slave_update and binlog can be enabled to log
On Wed, Mar 12, 2008 at 12:48 PM, Hiep Nguyen <[EMAIL PROTECTED]> wrote:
> hi all,
>
> i have a table (not my design) with a lot of fields and users have access
> to insert/update/delete record from this table. is there a way that mysql
> can log all transactions who change what on this table??
l'...
>
> thanks
>
>
>
> -Original Message-
> From: bruce [mailto:[EMAIL PROTECTED]
> Sent: Saturday, December 08, 2007 5:39 PM
> To: 'mysql list'
> Subject: RE: log-bin
>
>
>
> arrggg..
>
> hi martin.
>
> nope, i tried
y only have the "log-bin" in the my.cnf, allowing mysql to
write things to the "default" locations then everything starts as
expected...
thanks
-Original Message-
From: Martin Gainty [mailto:[EMAIL PROTECTED]
Sent: Saturday, December 08, 2007 1:49 PM
To: bruce
Subject: R
in" in the my.cnf, allowing mysql to
write things to the "default" locations then everything starts as
expected...
thanks
-Original Message-
From: Martin Gainty [mailto:[EMAIL PROTECTED]
Sent: Saturday, December 08, 2007 1:49 PM
To: bruce
Subject: Re: log-bin
Bruce-
when l
Hi,
On Dec 8, 2007 3:44 PM, bruce <[EMAIL PROTECTED]> wrote:
> hi...
>
> i'm trying to run mysql on a fedora core 5, system to allow the log bin
> files to be created.
>
> i have the following my.cnf file:
>
> ---
> [mysqld]
> datadir=/var/lib/mysql
> socket=/var/li
I don't think there is any way to lock down the general log to a
single database.. perhaps if you tell us what you are trying to
accomplish, we might be able to propose something..
As of today, 5.0.45 is the recommended install version.
http://dev.mysql.com/downloads/mysql/5.0.html
- micha
of course you'll need to restart the server after making the changes
to the options file..
On 7/30/07, Christian High <[EMAIL PROTECTED]> wrote:
> set these options in the option file under the [mysqld] section
>
> log-slow-queries=
> log=
>
> log= is the general query log
>
> i am not sur
set these options in the option file under the [mysqld] section
log-slow-queries=
log=
log= is the general query log
i am not sure what you mean by the mysql log. if you mean the error
log than that would be
log-error=
if you mean the binary log that would be
log-bin=
if you don't enter anyt
On 2/6/07, Yong Lee <[EMAIL PROTECTED]> wrote:
Hi all,
Just wondering how people are dealing with tables that are used for
logging, ie: insert only tables supporting occasional queries used for audit
or event logs.
These tables will keep growing and there is no need to keep them that
large
> Hi all,
>
>
>
> Just wondering how people are dealing with tables that are used for
> logging, ie: insert only tables supporting occasional queries used for
> audit or event logs.
>
> These tables will keep growing and there is no need to keep them that
> large so what is the best strategy in man
Kristen G. Thorson wrote:
But all I really get from this reading is 0 turns it off, 1 prints
some
warnings, and 2 prints level 1 warnings plus aborted connections
warnings. I have not been able to find any additional information
in my
search. Am I missing something, or is this all the docu
> -Original Message-
> From: Colin Charles [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, January 17, 2007 9:08 PM
> To: Kristen G. Thorson
> Cc: mysql@lists.mysql.com
> Subject: Re: Log Warnings Level
>
> Kristen G. Thorson wrote:
>
> Hi!
>
> > But
Kristen G. Thorson wrote:
Hi!
But all I really get from this reading is 0 turns it off, 1 prints some
warnings, and 2 prints level 1 warnings plus aborted connections
warnings. I have not been able to find any additional information in my
search. Am I missing something, or is this all the doc
bruce wrote:
chris...
hate to tell you.. .but you can have the log files set as i described..
the real issue was due to permission issues on the dir/file for the mysql
lol.. i'm not having much luck answering questions lately ;)
Thanks for letting us know about the fix.
--
MySQL General Mai
bruce wrote:
hi...
i changed the mysql my.cnf to provide log files. i restarted mysql, but i
don't see the log files...
any idea as to what i may have missed. i'm running FC4, mysql 4.1.
the my.cnf is:
[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
set-variable = max_connect
Just a shot in the dark...
how about : \T /home/karl/sql_log_$$
I believe, in bash, $$ will give you the pid of the process, so you
should
get a unique (somewhat) file name every time
>>>-Original Message-
>>>From: Karl Larsen [mailto:[EMAIL PROTECTED]
>>>Sent: Tuesday, July 11, 2006
On 12 Nov 2005, at 04:26, Harrison Fisk wrote:
The log-warnings option doesn't do what you want. It will cause
the mysqld server log more internal errors. Non-critical errors
such as network disconnects will be logged into the error log with
that setting.
The option you want it is the -
Hi,
On Nov 11, 2005, at 10:01 PM, Marcus Bointon wrote:
At the time I reported this bug back in February: http://
bugs.mysql.com/bug.php?id=8684 I was pleased to see it apparently
fixed so fast. I wasn't yet using MySQL 5, so I couldn't get the
fix. I am now upgrading to 5 using mysql 5.0.1
received from GLEB
http://dev.mysql.com/doc/mysql/en/communication-errors.html
I am going down that path right now
Thanks
Randy
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 21, 2005 8:19 AM
To: Randy Paries
Cc: mysql@lists.mysql.com
Subje
] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 21, 2005 8:19 AM
To: Randy Paries
Cc: mysql@lists.mysql.com
Subject: Re: Log file full of Got an error reading communication packets
"Randy Paries" <[EMAIL PROTECTED]> wrote on 09/21/2005 08:56:13 AM:
> Hello,
> My log file
"Randy Paries" <[EMAIL PROTECTED]> wrote on 09/21/2005 08:56:13 AM:
> Hello,
> My log file is getting filled with these.
> Can someone tell me what these mean?
>
> Thanks
> Randy
> //-snip-//
> 050122 20:28:00 Aborted connection 53561 to db: 'u
"packet too big" errors in replication are often a sign of corrupt
binary logs. If it's on a slave reading the relay log
often times flushing it will temporarily solve the problem. The easiest
way to flush the relay logs is to do a slave stop; change master to back
to the current file name and p
Hello.
In my opinion (it is based on looking through the source code, but I
can be wrong) - the max_allowed_packet should be at least more than
any event in the master's binary log. The tool for researching
binary logs is mysqlbinlog utility. See:
http://dev.mysql.com/doc/mysql/en/mysqlbi
enable the bin log in mysql. It doesn't log "transactions" i.e. what it
was, what it became, but the update will be logged
prathima rao wrote:
hi,
how to create a log file of the updates done on the data in visual basic or
in mysql for a particular record
for example
i have a purchase orde
On 18 Feb 2005, at 16:05, Gleb Paharenko wrote:
There is no direct way to load warnings into log files.
Just for the archives, I reported this as a bug and it's in the MySQL
bug db as having been verified, so I guess now we just hope/wait for a
fix in a later version:
http://bugs.mysql.com/bug.p
Hello.
There is no direct way to load warnings into log files. But you
may use a small value for max_error_count and launch mysql in a
batch mode saving results in the file.
Marcus Bointon <[EMAIL PROTECTED]> wrote:
> I'm migrating a MySQL 3.23 db to 4.1.10 (on Linux x86) and I'm gett
On 18 Feb 2005, at 14:24, Thomas Sundberg wrote:
I would approach this problem by isolating the where the problem
occurs.
I.e. Remove, comment out, half of you insert queries and see if the
problem
still exists. If it does, then remove yet another half of the
remaining part
leaving only 1/4 of t
> -Original Message-
> From: Marcus Bointon [mailto:[EMAIL PROTECTED]
> Sent: den 18 februari 2005 14:47
> To: mysql@lists.mysql.com
> Subject: log-warnings
>
> I'm migrating a MySQL 3.23 db to 4.1.10 (on Linux x86) and
> I'm getting some infrequent warnings when importing data
> dumps
No ideas internally to mysql, you can always fire up a sniffer
(sniffit, tcpdump, etc).. something like that would tell you.
On Mon, 31 Jan 2005 20:32:49 -0500, John May
<[EMAIL PROTECTED]> wrote:
> Anyone have any ideas on this one? :
>
> >I've scoured the MySQL manuals... does anyone know if
Anyone have any ideas on this one? :
I've scoured the MySQL manuals... does anyone know if there's any
way to log the amount of data that individual queries produce? Eg:
like bytes transferred in a web server log?
- John
--
---
J
Tim Cutts <[EMAIL PROTECTED]> wrote:
>
> On 15 Mar 2004, at 12:34, Victoria Reznichenko wrote:
>
>> [EMAIL PROTECTED] wrote:
>>> Hello colleagues:
>>> I would like to know if it's possible to start the log file production
>>> at run time, i.e. without
>>> stopping and restarting the database ...
On 15 Mar 2004, at 12:34, Victoria Reznichenko wrote:
[EMAIL PROTECTED] wrote:
Hello colleagues:
I would like to know if it's possible to start the log file production
at run time, i.e. without
stopping and restarting the database ...
No, you should restart MySQL server.
Which is really irritating
[EMAIL PROTECTED] wrote:
> Hello colleagues:
> I would like to know if it's possible to start the log file production
> at run time, i.e. without
> stopping and restarting the database ...
No, you should restart MySQL server.
> I would like to know also of it's possible to change at run time the
António Fernandes wrote:
Hello,
I'm am trying to make MySQL Server to log connections (attempts, successes,
failures) to a Syslog. I know that it's possible to log all queries but I
just want the connections. Has anyone already done this? Is there a patch
file that I can use?
Wanring - I've never
> I think I am confused. I have many bin index files, but I have not gotten
rid of them.
>
> I read somewhere that I should not remove them...or I should not remove
the entries in the index file.
>
> Since I am unsure of which one above is correct, I am posting to the list.
>
> Can someone let
[EMAIL PROTECTED] wrote:
>
> I think I am confused. I have many bin index files, but I have not gotten rid of
> them.
>
> I read somewhere that I should not remove them...or I should not remove the entries
> in the index file.
>
> Since I am unsure of which one above is correct, I am posting
>> I think I am confused. I have many bin index files, but I have not
>> gotten rid of them.
>>
>> I read somewhere that I should not remove them...or I should not
>> remove the entries in the index file.
>>
>> Since I am unsure of which one above is correct, I am posting to the
>> list.
>>
> -Message d'origine-
> De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Envoyé : Monday, December 29, 2003 8:12 PM
> À : [EMAIL PROTECTED]
> Objet : Log Files in MySQL
>
>
> I think I am confused. I have many bin index files, but I
> have not gotten rid of them.
>
> I read somewh
"Jon Miller" <[EMAIL PROTECTED]> wrote:
>
> I need a way to log every message that MySQL generates. I have the following in the
> /etc/my.cnf file:
> [mysqld]
> port=3309
> datadir=/var/lib/mysql
> socket=/var/lib/mysql/mysql.sock
> log-bin=/var/log/mysql.log
> bind-address=192.168.0.15
> log=/
Egor Egorov wrote:
It's a process id. You can see it in the output of SHOW PROCESSLIST.
So, each Id represents a thread, and each thread represents a
connection? So an entry like this in the query log:
031029 9:56:43 6 Quit
:: would represent a connection returned to the pool through an
ex
Hassan Schroeder <[EMAIL PROTECTED]> wrote:
> If this is documented anywhere, I sure can't find it, so --
>
> The query log fields are headed: Time, Id, Command, Argument.
>
> What is 'Id'?
It's a process id. You can see it in the output of SHOW PROCESSLIST.
--
For technical support contract
At 17:22 -0300 10/14/03, Daniel Franco wrote:
InnoDB uses some log files that are placed in the directory 'MySQL / data'.
What are those files ? Why and when InnoDB needs to save those logs ?
InnoDB uses them to record ongoing changes being made by transactions,
and for auto-recovery after a crash.
Sohail Hasan <[EMAIL PROTECTED]> wrote:
> I am using mysql version 4.0.12 on a solaris sparc box. My server has
> stopped creating the log-bin files although it is defined in my.cnf. The
> directory permissions of the data directory are fine. What is wrong with
> the setup?
Is extention of log
Sounds like you want to give the DEBUG version a try ;-)
Best regards
Nils Valentin
Tokyo/Japan
2003年 7月 25日 金曜日 01:25、Miguel Perez さんは書きました:
> Hi:
>
> I have a question: does anyone know if exists a log in mysql to store only
> incorrect queries or queries that causes a code error in mysql.
>
At 11:25 -0500 7/24/03, Miguel Perez wrote:
Hi:
I have a question: does anyone know if exists a log in mysql to
store only incorrect queries or queries that causes a code error in
mysql.
There is no such log.
--
Paul DuBois, Senior Technical Writer
Madison, Wisconsin, USA
MySQL AB, www.mysql.co
I use an extraction layer between mysql and the application/db calls to
handle this.. typically it's only enabled in development to work out any bugs..
Might want to look at something like that..
On Thu, 24 Jul 2003, Miguel Perez wrote:
> Hi:
>
> I have a question: does anyone know if exists a lo
antispam,
Monday, September 16, 2002, 11:25:31 PM, you wrote:
aafdn> my log file (hostname.log) was soo large and i just deleted it(back up) and
created a new file called hostname.log but mysql does not stores anything in the log
file.. (i did mysqladmin
aafdn> log-flush and server stop and s
- Original Message -
From: "Heikki Tuuri" <[EMAIL PROTECTED]>
To: "ritu singla" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, May 29, 2002 2:31 PM
Subject: Re: Log Files in InnoDB (MySQL)
> Ritu,
>
> the ib log files contain r
> Hello,
> i could not understand what is the content of log
> files in InnoDB in MySQL...is it the log of the
database,i
> mean, the data, or the transaction log??
>
> Thanx in advance..
> Ritu Singla
>
>
> Everything y
On Fri, Jan 25, 2002 at 03:30:11AM -0500, Ken wrote:
> I'm trying to enable binary logging on my MySQL server (3.23.28-gamma-log), per the
>recommendations in the manual about properly backing up the database.
>
> In my /etc/my.cnf I have:
> [mysqld]
> log-bin=updates
>
> I had also tried just:
At 11:16 AM -0400 9/4/01, Nick Willey wrote:
>Hi all,
>
>Is it possible to use a tape drive (/dev/ht0 in my case) as the destination
>for mysql logging? MySQL manual only mentions outputting to disk file.
>Example:
>
>% safe-mysqld --log-update= tar -czvf /dev/ht0/mysql-update.log
>
>I've tried t
On Thu, Aug 23, 2001 at 03:45:05PM +0800, Alan Tai wrote:
> >
> > >grant all
> > >on dbname.*
> > >to user identified by 'password';
>
> check the manual for more detail. seems like you are missing the
> 'host'.
That's okay. As the manual says, that's a shorthand way of specifying
user@"%". B
On Thu, Aug 23, 2001 at 09:40:36AM +0100, Dvoøáèek Michal wrote:
> Hi,
>
> try command: flush privileges;
> flush tables;
The flush is automatic with GRANT for him. The issue is with
'localhost' vs. all other hosts.
--
Jeremy D. Zawodny, <[EMAIL PROTECTED]>
Technical Yahoo - Yahoo
On Thu, Aug 23, 2001 at 12:24:53AM -0700, Dave Walcott wrote:
> Greetings list,
>
> I'm having a MySQL login problem that I cannot figure out, and
> (surprise surprise), I'm something of a newcomer to MySQL. I have
> read two decent MySQL books, searched the MySQL.com online manual,
> and search
On Thu, 23 Aug 2001, Dave Walcott wrote:
> Greetings list,
>
> I'm having a MySQL login problem that I cannot figure out, and (surprise
> surprise), I'm something of a newcomer to MySQL. I have read two decent
> MySQL books, searched the MySQL.com online manual, and searched the web for
> everyt
Hi,
try command: flush privileges;
flush tables;
Michal Dvoracek [EMAIL PROTECTED]
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.my
> 1. In which directory i can find the config file to config the log file
> 2. Where can i find the log file for mysql?
The log file will be in the data directory. In my case:
/usr/local/mysql/var
It has ending .err
You can place my.cnf in this dir also and some other places.
C
For Unix /etc/my.cnf
you then in the my.cnf say were you would like the logs!
Simon
-Original Message-
From: Krishna M [mailto:[EMAIL PROTECTED]]
Sent: 09 July 2001 16:27
To: [EMAIL PROTECTED]
Subject: Log files
Hello,
I have a Question,
1. In which directory i can fi
Kenneth Kopelson wrote:
>
> Look into the Linux "logrotate" daemon. It allows you to configure what
> happens with logs.
That would work if the problem I'm looking to solve was predictable -
i.e. I have a busy site and I run logrotate three times a day to make
sure the logs haven't gotten too
Look into the Linux "logrotate" daemon. It allows you to configure what
happens with logs.
At 06:44 AM 6/6/01 -0400, Peter Billson wrote:
>I'm running mySQL on Linux and was wondering is there a way to limit the
>maximum log file size?
>
> From time to time I have written a bad script that w
On 30-May-01 Mohammad Shoja wrote:
> Hello everybody.
> would you please tell me how can I log execution of a DDL?
Whats a DDL ?
> I have a test.sql which is a DDL file, I wanna log its output but
> when I
> try the following it create log file but its empty.
>
> mysql -u root databasename log
hi.
if you're not on a windows box, try something like:
mysql -uroot -p &1 | tee output.log
the mysql client also has a --tee option, as well as a tee(\T) command that
could be of use.
-ravi.
-Original Message-
From: Mohammad Shoja [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 30, 200
Mohammad Shoja wrote:
> Mybe this is not a mysql question but a unix command line question:
> would you please tell me how can I log execution of a DDL?
> I have a test.sql which is a DDL file, I wanna log its output but when I
> try the following it create log file but its empty.
>
> mysql -u
Actually I have 2.23.20-gamma and I get 'create dabase blabla' in my update log.
cheers,
thalis
On Mon, 19 Mar 2001 [EMAIL PROTECTED] wrote:
> Hi,
>
> Can you guys confirm that "create database" statements are not logged in
> the log-update log? The version I am using is 3.22.32.
>
>
> Rega
98 matches
Mail list logo
