documentation
there
is on this?
What kind of additional information are you looking about the --W (or
--log-warnings=N) option?
Thank you for the response.
I was looking for information on how high the level can go - 2? 5? 200?
- and what types of warnings are logged for a given level?
AFAIK
> -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
documentation there
is on this?
What kind of additional information are you looking about the --W (or
--log-warnings=N) option?
I'd pay attention to aborted connections, as MySQL Network's monitoring
service actually does do so
kind regards
--
Colin Charles, Community Enginee
The manual indicates that you can specify a specific level to control
what types of warnings are logged:
http://dev.mysql.com/doc/refman/5.0/en/server-options.html
(See section on log-warnings.)
But all I really get from this reading is 0 turns it off, 1 prints some
warnings, and 2 prints level
nt: Friday, March 10, 2006 8:14 PM
> To: Dan Nelson
> Cc: mysql@lists.mysql.com
> Subject: Re: How to Log Warnings and Errors from queries
>
>
> Hi Dan,
>
> Noted with thanks.
>
> As such, is there a workaround to log problematic sql queries ran against
> the mysqld se
: ryan lwf [mailto:[EMAIL PROTECTED]
Sent: Friday, March 10, 2006 8:14 PM
To: Dan Nelson
Cc: mysql@lists.mysql.com
Subject: Re: How to Log Warnings and Errors from queries
Hi Dan,
Noted with thanks.
As such, is there a workaround to log problematic sql queries ran against
the mysqld server ? Do
sql"));
Regards!
Edwin.
-Mensaje original-
De: Subscriptions [mailto:[EMAIL PROTECTED]
Enviado el: Viernes, 10 de Marzo de 2006 10:27 a.m.
Para: mysql@lists.mysql.com
Asunto: Re: How to Log Warnings and Errors from queries
In PHP, you can see the error message as follows:
$resu
(mysql_error()) );
where you create that function log_error to write to a file.
Jenifer
- Original Message -
From: "Kishore Jalleda" <[EMAIL PROTECTED]>
To: "ryan lwf" <[EMAIL PROTECTED]>
Cc: "Dan Nelson" <[EMAIL PROTECTED]>;
Sent: Fr
te:
> >
> > In the last episode (Mar 08), ryan lwf said:
> > > I understand that the option log-errors and log-warnings only logs
> > > server related internal errors. How do I enable logging errors from
> > > queries executed, so that I can fix the problemat
said:
> > I understand that the option log-errors and log-warnings only logs
> > server related internal errors. How do I enable logging errors from
> > queries executed, so that I can fix the problematic query statement
> > accordingly?
> >
> > The statement "
In the last episode (Mar 08), ryan lwf said:
> I understand that the option log-errors and log-warnings only logs
> server related internal errors. How do I enable logging errors from
> queries executed, so that I can fix the problematic query statement
> accordingly?
>
> T
Hi all,
I understand that the option log-errors and log-warnings only logs server
related internal errors. How do I enable logging errors from queries
executed, so that I can fix the problematic query statement accordingly?
The statement "SHOW WARNINGS" and "SHOW ERRORS"
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 i
sing mysql 5.0.15, and I find I still
face much the same problem. Despite much rummaging in the docs, the
log-warnings options still seem completely undocumented (it gets a
few mentions as a startup option, but nowhere does it say where the
messages disappear to), and despite having it '
me problem. Despite much rummaging in the docs, the log-
warnings options still seem completely undocumented (it gets a few
mentions as a startup option, but nowhere does it say where the
messages disappear to), and despite having it 'enabled' (it's
difficult to know what
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
27;s just not practical to scan the output, plus
> it makes it go very slowly.
>
> I've got log-warnings in my my.cnf file, and mysqld is definitely
> picking it up (adding it made log-warnings appear as set to 2, though I
> can't find any reference in the docs for what th
hen I import. I can't believe that there's no
way of having these reported - does no-one value their data? Why
doesn't log-warnings do anything? Should I report it as a bug? I really
don't want to spend days trawling through/slicing up 3Gb of dump files
when a trivial sett
> -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 infre
t not practical to scan the output, plus
it makes it go very slowly.
I've got log-warnings in my my.cnf file, and mysqld is definitely
picking it up (adding it made log-warnings appear as set to 2, though I
can't find any reference in the docs for what the values mean), but
mysql is
n the latest release
(4.1.9 now)? Try only --log-warnings, without specifying the exact value.
[snip]
We are with mysql 4.0.17-log and we want to use --log-warnings to see aborted
connections
in our errorlog.
We put log_warnings = 2 in our my.cnf and restarted mysql but we did not see
ab
We are with mysql 4.0.17-log and we want to use --log-warnings to see aborted
connections in our errorlog.
We put log_warnings = 2 in our my.cnf and restarted mysql but we did not see
aborted connections in our errorlog.
We tried --log-warnings = 2 on the command line when we started mysql
22 matches
Mail list logo
