[gentoo-amd64] mysql log-bin dir

[gentoo-amd64] mysql log-bin dir

[Clemente Aguiar]

I noticed that since the last upgrade (to mysql-5.0.38) that the bin
logging is being done to a different directory and with a different name
structure.

1. All log-bin files used to be in the /var/lib/mysql and used to be the
name of the host machine followed by -bin.xxxx.

2. Now, in this version (mysql-5.0.38) the logs are going to
/var/run/mysqld and with mysqld-bin.xxxxx names.

The manual for version 5.0
(http://dev.mysql.com/doc/refman/5.0/en/binary-log.html) says that it
should be as it was before (as in 1. above)!

Anybody know why this is happening?

Clemente
--
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] mysql log-bin dir

[Daniel Iliev]

On Thu, 10 May 2007 11:45:23 +0100
"Clemente Aguiar" <clemente.aguiar@madeiratecnopolo.pt> wrote:

> 
> I noticed that since the last upgrade (to mysql-5.0.38) that the bin
> logging is being done to a different directory and with a different
> name structure.
> 
> 1. All log-bin files used to be in the /var/lib/mysql and used to be
> the name of the host machine followed by -bin.xxxx.
> 
> 2. Now, in this version (mysql-5.0.38) the logs are going to
> /var/run/mysqld and with mysqld-bin.xxxxx names.
> 
> The manual for version 5.0
> (http://dev.mysql.com/doc/refman/5.0/en/binary-log.html) says that it
> should be as it was before (as in 1. above)!
> 
> Anybody know why this is happening?
> 
> Clemente


Hah! Nice warning!
If it works like this for me I'll pass the. Since I have several
scripts depending on those paths and file names, this behavior would
introduce breakage in my case. So, thanks for the just-in-time note - I
had this update scheduled for tomorrow, after the "End Of Day"
procedure.


-- 
Best regards,
Daniel

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] mysql log-bin dir

[Ferris McCormick]

[-- Attachment #1: Type: text/plain, Size: 1408 bytes --]

On Thu, 2007-05-10 at 15:10 +0300, Daniel Iliev wrote:
> On Thu, 10 May 2007 11:45:23 +0100
> "Clemente Aguiar" <clemente.aguiar@madeiratecnopolo.pt> wrote:
> 
> > 
> > I noticed that since the last upgrade (to mysql-5.0.38) that the bin
> > logging is being done to a different directory and with a different
> > name structure.
> > 
> > 1. All log-bin files used to be in the /var/lib/mysql and used to be
> > the name of the host machine followed by -bin.xxxx.
> > 
> > 2. Now, in this version (mysql-5.0.38) the logs are going to
> > /var/run/mysqld and with mysqld-bin.xxxxx names.
> > 
> > The manual for version 5.0
> > (http://dev.mysql.com/doc/refman/5.0/en/binary-log.html) says that it
> > should be as it was before (as in 1. above)!
> > 
> > Anybody know why this is happening?
> > 
> > Clemente
> 
> 
> Hah! Nice warning!
> If it works like this for me I'll pass the. Since I have several
> scripts depending on those paths and file names, this behavior would
> introduce breakage in my case. So, thanks for the just-in-time note - I
> had this update scheduled for tomorrow, after the "End Of Day"
> procedure.
> 
> 
> -- 
> Best regards,
> Daniel
You mean like this. :) (From sparc.)

mysql mysql 1607 2007-05-08 11:02 /var/run/mysqld/mysqld-bin.000001

-- 
Ferris McCormick (P44646, MI) <fmccor@gentoo.org>
Developer, Gentoo Linux (Devrel, Sparc)


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: [gentoo-amd64] mysql log-bin dir

[Ferris McCormick]

[-- Attachment #1: Type: text/plain, Size: 1409 bytes --]

On Thu, 2007-05-10 at 15:10 +0300, Daniel Iliev wrote:
> On Thu, 10 May 2007 11:45:23 +0100
> "Clemente Aguiar" <clemente.aguiar@madeiratecnopolo.pt> wrote:
> 
> > 
> > I noticed that since the last upgrade (to mysql-5.0.38) that the bin
> > logging is being done to a different directory and with a different
> > name structure.
> > 
> > 1. All log-bin files used to be in the /var/lib/mysql and used to be
> > the name of the host machine followed by -bin.xxxx.
> > 
> > 2. Now, in this version (mysql-5.0.38) the logs are going to
> > /var/run/mysqld and with mysqld-bin.xxxxx names.
> > 
> > The manual for version 5.0
> > (http://dev.mysql.com/doc/refman/5.0/en/binary-log.html) says that it
> > should be as it was before (as in 1. above)!
> > 
> > Anybody know why this is happening?
> > 
> > Clemente
> 
> 
> Hah! Nice warning!
> If it works like this for me I'll pass the. Since I have several
> scripts depending on those paths and file names, this behavior would
> introduce breakage in my case. So, thanks for the just-in-time note - I
> had this update scheduled for tomorrow, after the "End Of Day"
> procedure.
> 
> 
> -- 
> Best regards,
> Daniel
> 

You mean like this. :)  (On sparc.)
mysql mysql 1607 2007-05-08 11:02 /var/run/mysqld/mysqld-bin.000001
-- 
Ferris McCormick (P44646, MI) <fmccor@gentoo.org>
Developer, Gentoo Linux (Devrel, Sparc)


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: [gentoo-amd64] mysql log-bin dir

[Daniel Iliev]

On Thu, 10 May 2007 12:30:27 +0000
Ferris McCormick <fmccor@gentoo.org> wrote:

> On Thu, 2007-05-10 at 15:10 +0300, Daniel Iliev wrote:
> > On Thu, 10 May 2007 11:45:23 +0100
> > "Clemente Aguiar" <clemente.aguiar@madeiratecnopolo.pt> wrote:
> > 
> > > 
> > > I noticed that since the last upgrade (to mysql-5.0.38) that the
> > > bin logging is being done to a different directory and with a
> > > different name structure.
> > > 
> > > 1. All log-bin files used to be in the /var/lib/mysql and used to
> > > be the name of the host machine followed by -bin.xxxx.
> > > 
> > > 2. Now, in this version (mysql-5.0.38) the logs are going to
> > > /var/run/mysqld and with mysqld-bin.xxxxx names.
> > > 
> > > The manual for version 5.0
> > > (http://dev.mysql.com/doc/refman/5.0/en/binary-log.html) says
> > > that it should be as it was before (as in 1. above)!
> > > 
> > > Anybody know why this is happening?
> > > 
> > > Clemente
> > 
> > 
> > Hah! Nice warning!
> > If it works like this for me I'll pass the. Since I have several
> > scripts depending on those paths and file names, this behavior would
> > introduce breakage in my case. So, thanks for the just-in-time note
> > - I had this update scheduled for tomorrow, after the "End Of Day"
> > procedure.
> > 
> > 
> > -- 
> > Best regards,
> > Daniel
> You mean like this. :) (From sparc.)
> 
> mysql mysql 1607 2007-05-08 11:02 /var/run/mysqld/mysqld-bin.000001
> 


Oh! I thought this version has a hard-coded path and name. If I have
the option "--log-bin[=base_name]" everything should be fine.

Thanks for the examples!

-- 
Best regards,
Daniel

-- 
gentoo-amd64@gentoo.org mailing list

RE: [gentoo-amd64] mysql log-bin dir

[Clemente Aguiar]

> -----Mensagem original-----
> De: Ferris McCormick [mailto:fmccor@gentoo.org] 
> Enviada: quinta-feira, 10 de Maio de 2007 13:34
> Para: gentoo-amd64@lists.gentoo.org
> Assunto: Re: [gentoo-amd64] mysql log-bin dir
> 
> 
> On Thu, 2007-05-10 at 15:10 +0300, Daniel Iliev wrote:
> > On Thu, 10 May 2007 11:45:23 +0100
> > "Clemente Aguiar" <clemente.aguiar@madeiratecnopolo.pt> wrote:
> > 
> > > 
> > > I noticed that since the last upgrade (to mysql-5.0.38) 
> that the bin 
> > > logging is being done to a different directory and with a 
> different 
> > > name structure.
> > > 
> > > 1. All log-bin files used to be in the /var/lib/mysql and 
> used to be 
> > > the name of the host machine followed by -bin.xxxx.
> > > 
> > > 2. Now, in this version (mysql-5.0.38) the logs are going to 
> > > /var/run/mysqld and with mysqld-bin.xxxxx names.
> > > 
> > > The manual for version 5.0
> > > (http://dev.mysql.com/doc/refman/5.0/en/binary-log.html) 
> says that 
> > > it should be as it was before (as in 1. above)!
> > > 
> > > Anybody know why this is happening?
> > > 
> > > Clemente
> > 
> > 
> > Hah! Nice warning!
> > If it works like this for me I'll pass the. Since I have several 
> > scripts depending on those paths and file names, this 
> behavior would 
> > introduce breakage in my case. So, thanks for the 
> just-in-time note - 
> > I had this update scheduled for tomorrow, after the "End Of Day" 
> > procedure.
> > 
> > 
> > --
> > Best regards,
> > Daniel
> > 
> 
> You mean like this. :)  (On sparc.)
> mysql mysql 1607 2007-05-08 11:02 /var/run/mysqld/mysqld-bin.000001
> -- 

Yes like that.



There is another behaviour which worries me, mysqld doesn't stop when I
issue the following command:
/etc/init.d/mysql stop
 * Stopping mysql ... OK
 * Stopping mysqld (0) ...[!!]

The same thing happens when I reboot ... it takes forever, and when it
comes up there is a warning saying that the mysqld.sock is present.

Humm ... Worrying.

Clemente
--
gentoo-amd64@gentoo.org mailing list

RE: [gentoo-amd64] mysql log-bin dir

[Ferris McCormick]

[-- Attachment #1: Type: text/plain, Size: 957 bytes --]

On Thu, 2007-05-10 at 17:08 +0100, Clemente Aguiar wrote:
> 

> > You mean like this. :)  (On sparc.)
> > mysql mysql 1607 2007-05-08 11:02 /var/run/mysqld/mysqld-bin.000001
> > -- 
> 
> Yes like that.
> 
> 
> 
> There is another behaviour which worries me, mysqld doesn't stop when I
> issue the following command:
> /etc/init.d/mysql stop
>  * Stopping mysql ... OK
>  * Stopping mysqld (0) ...[!!]
> 
> The same thing happens when I reboot ... it takes forever, and when it
> comes up there is a warning saying that the mysqld.sock is present.
> 
> Humm ... Worrying.
> 
> Clemente

There are open bugs on this:
https://bugs.gentoo.org/show_bug.cgi?id=174790
https://bugs.gentoo.org/show_bug.cgi?id=177128

And yes, it is worrying.  For me, if I ever get mysql to stop,
it takes a reboot to get it started again.

Regards,
-- 
Ferris McCormick (P44646, MI) <fmccor@gentoo.org>
Developer, Gentoo Linux (Devrel, Sparc)


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

RE: [gentoo-amd64] mysql log-bin dir

[Clemente Aguiar]

> -----Mensagem original-----
> De: Ferris McCormick [mailto:fmccor@gentoo.org] 
> Enviada: quinta-feira, 10 de Maio de 2007 18:21
> Para: gentoo-amd64@lists.gentoo.org
> Assunto: RE: [gentoo-amd64] mysql log-bin dir
> 
> 
> On Thu, 2007-05-10 at 17:08 +0100, Clemente Aguiar wrote:
> > 
> 
> > > You mean like this. :)  (On sparc.)
> > > mysql mysql 1607 2007-05-08 11:02 
> /var/run/mysqld/mysqld-bin.000001
> > > --
> > 
> > Yes like that.
> > 
> > 
> > 
> > There is another behaviour which worries me, mysqld doesn't 
> stop when 
> > I issue the following command: /etc/init.d/mysql stop
> >  * Stopping mysql ... OK
> >  * Stopping mysqld (0) ...[!!]
> > 
> > The same thing happens when I reboot ... it takes forever, 
> and when it 
> > comes up there is a warning saying that the mysqld.sock is present.
> > 
> > Humm ... Worrying.
> > 
> > Clemente
> 
> There are open bugs on this: 
> https://bugs.gentoo.org/show_bug.cgi?id=174790
> https://bugs.gentoo.org/show_bug.cgi?id=177128
> 
> And yes, it is worrying.  For me, if I ever get mysql to 
> stop, it takes a reboot to get it started again.
> 
> Regards,
> -- 
> Ferris McCormick (P44646, MI) <fmccor@gentoo.org>
> Developer, Gentoo Linux (Devrel, Sparc)
> 

I identified my shutdown problem with bug
https://bugs.gentoo.org/show_bug.cgi?id=174790 so I left a note there
:-)

Clemente
--
gentoo-amd64@gentoo.org mailing list