of Windows' idiosyncracies - I hope the
damn thing allows you to rename a file that's being held open by a program. If
not, well... see above.
<<<<<<<<
No, as Reindl answered, but in 5.5.8 there is this:
If you flush the logs using
FLUSH
LOGS or
mysqladmin
flush
Am 04.04.2013 23:08, schrieb h...@tbbs.net:
> Is there somewhere within MySQL means of aging the error log, that it not
> indefinitly grow big, or is that done through the OS and filesystem on which
> "mysqld" runs?
man logrotate
signature.asc
Description: OpenPGP digital signature
Am 05.04.2013 11:16, schrieb Johan De Meersman:
> - Original Message -
>> From: h...@tbbs.net
>> Subject: Re: error-log aging
>>
>> man logrotate
>> <<<<<<<<
>> Not Unix!
>
> So get unix :-)
>
>> In any cas
- Original Message -
> From: h...@tbbs.net
> Subject: Re: error-log aging
>
> man logrotate
> <<<<<<<<
> Not Unix!
So get unix :-)
> In any case, I take this to mean that this is not done within MySQL,
> right?
Half and half - rename the
>>>> 2013/04/04 23:18 +0200, Reindl Harald >>>>
> Is there somewhere within MySQL means of aging the error log, that it not
> indefinitly grow big, or is that done through the OS and filesystem on which
> "mysqld" runs?
man logrotate
<<<&l
Is there somewhere within MySQL means of aging the error log, that it not
indefinitly grow big, or is that done through the OS and filesystem on which
"mysqld" runs?
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql
Hey everyone,
the problem was that I have the error log in /var/log/mysqld/mysql.error and
SELinux was not configured to allow it to rotate. I have compiled a custom
module to allow it so the problem is resolved. It was not an issue with
MySQL Server itself.
thanks again.
Keith
On Fri, Aug 12
;
> > log in with mysql client and 'flush logs' OR mysqladmin --flush-log
> >
> > It should rename the old log file to mysqld.log-old and start a new
> > mysqld.log file.
> >
> > On one system it works perfectly
> >
> > On the other...nothi
from the MySQL website).
>
> Here is what I do:
>
>
> log in with mysql client and 'flush logs' OR mysqladmin --flush-log
>
> It should rename the old log file to mysqld.log-old and start a new
> mysqld.log file.
>
> On one system it works perfectly
OR mysqladmin --flush-log
It should rename the old log file to mysqld.log-old and start a new
mysqld.log file.
On one system it works perfectly
On the other...nothing.
I tried moving the error log (mv /var/log/mysqld/mysqld.log
/var/log/mysqld.log.old) and then issuing the flush logs command...i
Background: Solaris 10, MySQL 5.0.45.
I have changed something recently that is causing the error log file to be
created with mode 660. I would like for it it be mode 664. I admit that I
recently changed the my.cnf file and added a log-error line which did not
have the fully qualified path and
Good Morning Ben
this is an acknowledged bug
http://bugs.mysql.com/bug.php?id=20090
which was fixed in 5.1.22-beta +
can you upgrade?
Martin--
- Original Message -
From: "Ben Clewett" <[EMAIL PROTECTED]>
To:
Sent: Friday, December 21, 2007 4:52 AM
Subject: Odd item in
MySql 5.0.41
SUSE 10.2
Linux dbms-04-r1 2.6.18.2-34-default #1 SMP Mon Nov 27 11:46:27 UTC 2006
x86_64 x86_64 x86_64 GNU/Linux
Dear MySql,
I have an odd item in my error log, I wonder if you can tell me what
this means? Also whether should do anything about it?
(This table once corrupted
H LOGS (or mysqld catches a
SIGHUP), it rotates the error log to -old, like this:
Here's the config file line:
log-error = /var/log/mysql/mysqld.err
And here's the directory:
$ ls -l /var/log/mysql/
-rw-rw 1 mysql mysql 0 Jul 11 08:40 mysql.err
-rw-rw 1 mysql mysql
rrect password.
*
If these kinds of things happen, it might indicate that someone is
trying to break into your server!
I see that this event is written to the general log. Is there a way to
log such an event to the error log?
Amit
--
MySQL General Mailing List
For
Why can't output to error log file when INNODB happened ERROR1205?
All server error message is output to error log file, isn't it?
--
create table test (id int ,name text)engine=innodb;
insert into test values ( 1, 'test');
--
Pattern 1
--
CLIE
Why can't output to error log file when INNODB happened ERROR1205?
All server error message is output to error log file, isn't it?
--
create table test (id int ,name text)engine=innodb;
insert into test values ( 1, 'test');
--
Pattern 1
--
CLIE
> >
> > I haven't admin'd MySQL in a couple of years, and I have forgotten
and lot
> > (and probably never knew even more.)
> >
> > I recently installed the current 4.1x MySQL release in Windows XP. I am
> > trying to track down problems, and can't
obably never knew even more.)
>
> I recently installed the current 4.1x MySQL release in Windows XP. I am
> trying to track down problems, and can't seem to get an error log. I
> expected to see a file, mysql.err in the data directory.
>
> Not only isn't it ther
[EMAIL PROTECTED] wrote:
Hi,
I haven't admin'd MySQL in a couple of years, and I have forgotten and lot
(and probably never knew even more.)
I recently installed the current 4.1x MySQL release in Windows XP. I am
trying to track down problems, and can't seem to get an error log
Hi,
I haven't admin'd MySQL in a couple of years, and I have forgotten and lot
(and probably never knew even more.)
I recently installed the current 4.1x MySQL release in Windows XP. I am
trying to track down problems, and can't seem to get an error log. I
expected to see a fil
Hi,
do you continue to have it even if you EXIT your Mysql Administrator ?
Mathias
Selon [EMAIL PROTECTED]:
> Does anyone know why this message keeps repeating:
> 050425 11:31:40 229 Query SHOW STATUS
> 229 Query SHOW INNODB STATUS
> 050425 11:31:41 229 Qu
Does anyone know why this message keeps repeating:
050425 11:31:40 229 Query SHOW STATUS
229 Query SHOW INNODB STATUS
050425 11:31:41 229 Query SHOW STATUS
229 Query SHOW INNODB STATUS
050425 11:31:42 229 Query SHOW S
Is there any way to find log of queries that returned errors. Syntax
errors or column not found, for example?
The General Log simply logs the query without giving any information as
to whether the query was successful or not
Thank you in advance.
Best regards,
TS
> From: Paul DuBois [mailto:[EMAIL PROTECTED]
> I don't understand that second sentence, but you can submit
> feature requests at http://bugs.mysql.com/
For example, I would like the error log to look something like...
MySQL: ready for connections.
Version: '4.0.18-
> From: Paul DuBois [mailto:[EMAIL PROTECTED]
> I suppose you could consider it such, but on the other hand, it's not
the
> sort of error that prevents the server from running or processing
other
> queries. In any case, logging it to the error log isn't going to help
>
At 12:40 -0600 3/24/04, Daniel Gaddis wrote:
> From: Victor Pendleton [mailto:[EMAIL PROTECTED]
This error should be logged. Do you have a file called .err
in your
directory?
Yes I have a file called .err and that error is not in it.
From: Paul DuBois [mailto:[EMAIL PROTECTED]
The error
> From: Victor Pendleton [mailto:[EMAIL PROTECTED]
> This error should be logged. Do you have a file called .err
in your
directory?
Yes I have a file called .err and that error is not in it.
> From: Paul DuBois [mailto:[EMAIL PROTECTED]
> The error log is for messages pertaining
SET heading =
> 'Delete', body = '',
> keywords = '' ,
> dateVerified = NULL WHERE entryID
> = 168"" "
>
> The contents makes me think there should also be something in t
dateVerified = NULLWHERE entryID
= 168"" "
The contents makes me think there should also be something in the mysql
error log similar to...
Incorrect key file for table: 'referenceEntries'. Try to repair it
But there is no entry in th
WHERE entryID
= 168"" "
The contents makes me think there should also be something in the mysql
error log similar to...
Incorrect key file for table: 'referenceEntries'. Try to repair it
But there is no entry in the mysql error log. Any thoughts why not?
On a new installation of mysql on a Mac OS X machine 10.3.x I am getting the
following in the .err log:
040127 17:23:29 mysqld started
/Library/MySQL/libexec/mysqld: ERROR: unknown variable
'innodb_buffer_pool_size = 70M'
040127 17:23:32 mysqld ended
040127 18:43:58 mysqld started
/Li
Hello,
I have about half a dozen servers running mysql. I'd like to be able to
consolidate all of the error logs in one place so that I can just
tail -f one log file to watch for any problems. It seems like this would
be very easy to do if I could send the error log to syslog, and hav
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
uuri
Innobase Oy
http://www.innodb.com
Foreign keys, transactions, and row level locking for MySQL
InnoDB Hot Backup - a hot backup tool for MySQL
Order MySQL technical support from https://order.mysql.com/
Subject: InnoDB warning in error log
From: Marek Lewczyk
Date: Wed, 27 Au
I'm testing my application using MySQL 4.1.0. Before I was using 4.0.14
version. Today I've looked into error file of the 4.1.0 where there was
hundreds of new lines with information like this:
InnoDB: Warning: an inconsistent page in the doublewrite buffer
InnoDB: space id 3686351459 page number
Pushpinder Singh Garcha <[EMAIL PROTECTED]> wrote:
> I need to find out why the mysqld is not starting up ? Can someone
> please throw some light to the location of this file on a Mac?
By default in the MySQL data dir.
--
For technical support contracts, goto https://order.mysql.com/?ref=ensi
# [EMAIL PROTECTED] / 2003-06-18 12:24:06 -0400:
> [psg:/usr/local/mysql] psgarcha% sudo ./bin/mysqld_safe &
> [5] 703
> [psg:/usr/local/mysql] psgarcha% Starting mysqld daemon with databases
> from /usr/local/mysql/data
> 030618 11:50:09 mysqld ended
>
>
> [5]Done
Hello everyone,
I am unable to start the mysqld, i keep getting "mysqld ended" error.
-
[psg:/usr/local/mysql] psgarcha% sudo ./bin/mysqld_safe &
[5] 703
[psg:/usr/local/mysql] psgarcha% Start
I need to find out why the mysqld is not starting up ? Can someone
please throw some light to the location of this file on a Mac?
Thanks in adavnce.
--Pushpinder
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTE
Hello.
How can I recover query errors done on a mysql server?
Is there a log file?
It's very important to me to know about this.
Thanx so much!!!
Lorenzo
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
I've set up replication and the slave is updating any changes made to the
master, but these errors keep showing up in the error log. Any ideas??
020716 12:57:26 Slave: Failed reading log event, reconnecting to retry, log
'walt-bin.002' position 265
020716 12:57:26 Slave:
On Fri, 19 Apr 2002 16:03:44 -0500 (CDT)
Russell E Glaue <[EMAIL PROTECTED]> wrote:
>
> I think it would be a good idea to be able to specify the error log on
> the command line when starting mysqld. Right now mysql users can only
> specify the following logs on the command
I think it would be a good idea to be able to specify the error log on
the command line when starting mysqld. Right now mysql users can only
specify the following logs on the command line:
log (access/activity log)
log bin
log bin index
log update
log isam
please, if somebody knows about this problem, help me
regards
alemo
- Original Message -
> Hello,
>
> I've updated my mySQL from version 3.21 to 3.23, and (after this change)
all
> of my perl programs which use mysql, prints to STDERR, a debug (?) message
> like this:
> SV = RV(0x84ec388
Hello,
I've updated my mySQL from version 3.21 to 3.23, and (after this change) all
of my perl programs which use mysql, prints to STDERR, a debug (?) message
like this:
SV = RV(0x84ec388) at 0xb2f0
REFCNT = 1
FLAGS = (ROK,READONLY)
RV = 0x8552d3c
Then, I updated the mySQL version to 4
Rafal Jank wrote:
> Hi!
> Is there a possibility to rotate mysql error log without stoping the server?
I was waiting for someone else to respond. But some possibilities are 1: use
the apache program 'rotatelog'. Not sure how you would do this.
In Linux you can rename the file
Hi!
Is there a possibility to rotate mysql error log without stoping the server?
TIA
--
_/_/ _/_/_/ - Rafał Jank [EMAIL PROTECTED] -
_/ _/ _/ _/ _/ Wirtualna Polska SA http://www.wp.pl
_/_/_/_/ _/_/_/ul. Uphagena 2, 80-237 Gdansk, tel/fax. (58
Probably doesn't really matter much, but I figured I'd report it at least.
010703 20:18:44 Aborted connection 112650 to db: 'unconnected' user: 'xxx' host:
`xx' (Got error %d from table handler)
010703 20:18:46 Aborted connection 112651 to db: 'unconnected' user: 'xxx' host:
`
that patched to authenticate
through MySQL server against passwd and this also working fine . The bad
things that bothering me is that I show this error in my MySQL error log
everytime :
010401 3:47:24 Aborted connection 6132751 to db: 'morva' user: 'radius
' (Got an error r
Hi !
I've just upgraded to the new mysql server 3.23.32 and in the error log I now see
'Aborted connection ... (Got an error reading communication packets)'.
I have found information about this problem such as using the binary release instead
of the source release.
I have no
51 matches
Mail list logo
