FreeLists / mylvmbackup / [mylvmbackup] Re: innodb_recover bug, related to pid (0.6 release)

[Lenz Grimmer <lenz@xxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Guillaume,

thanks for your message!

Guillaume Boddaert wrote:

> I'd like to submit a but report concerning mylvmbackup. On CentOS 5.1, I 
> stubbled on this error :
> 
> If you activate the innodb_recover option, the mysql_safe thread that 
> intend to run the innodb restoration use the --pidfile option which is 
> not valid. Hence the server starts with default pid file, which is 
> already in use.
> 
>  > A mysqld process already exists
> 
> To correct this, you'd need to correct the mylvmbackup script at line 497
>  > if ( system("echo 'select 1;' | $mysqld_safe --pidfile=$pidfile 
> --datadir=$mountdir --skip-networking --skip-grant --bootstrap 
> --skip-ndbcluster --skip-slave-start") != 0 )
> for :
>  > if ( system("echo 'select 1;' | $mysqld_safe --pid-file=$pidfile 
> --datadir=$mountdir --skip-networking --skip-grant --bootstrap 
> --skip-ndbcluster --skip-slave-start") != 0 )
> 
> the correct pidfile flag for mysqld (on my CentOS box at least) is 
> --pid-file not --pidfile.
> 
> Thanks for this useful tool !

Whoops, good spotting. Thanks for the hint! I have applied a fix to SVN
for this, it will be part of the upcoming 0.7 release.

Bye,
        LenZ
- --
- ------------------------------------------------------------------
 Lenz Grimmer <lenz@xxxxxxxxxxx>                             -o)
 [ICQ: 160767607 | Jabber: LenZGr@xxxxxxxxxx]                /\\
 http://www.lenzg.org/                                       V_V
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFHzBzbSVDhKrJykfIRAqcnAJ9871k9gExttlEy2Ewd0AM7vpU32gCcCqJi
pQtaNnzhzdzSYbByBNH6Xbo=
=FkRN
-----END PGP SIGNATURE-----