2013/04/05 11:16 +0200, Johan De Meersman
Half and half - rename the file, then issue "flush logs" in mysql to close and
reopen the logs, which will cause a new log with the configured name to be
created.
That being said, I'm not much aware of Windows' idiosyncracies - I hope the
damn
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
Not Unix!
In any case, I take this to mean that this
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,
this will help you
http://adminlinux.blogspot.com/2009/09/mysql-log-file-rotation.html
On Fri, Aug 12, 2011 at 9:43 AM, Paul DuBois wrote:
>
> On Aug 11, 2011, at 2:30 PM, Keith Murphy wrote:
>
> > Hey everyone,
> >
> > I have run across something that has me stumped. I have some systems that
>
On Aug 11, 2011, at 2:30 PM, Keith Murphy wrote:
> Hey everyone,
>
> I have run across something that has me stumped. I have some systems that
> have very large error logs because we haven't moved from statement-based to
> mixed-based replication yet so they get a lot of warnings logged. I need
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
