Unable to migrate embedded db to external mysql.

[Jeff Mitchell]

On 12/26/2009 02:23 AM, tris_r wrote:
> First I wanted to check that I was barking up the right tree with what I
> wanted to do.   Got a new HTPC for xmas and want it's instance of Amarok to
> read / write and interact with the amarok database on my office PC that I've
> had for some time.  i.e rate a song on the office pc and the rating appears
> on the other.  I figured that using the new external mysql db on both
> pointing the HTPC's amarok database to the mysql server on the office pc
> would allow me to do this.

Sharing a DB between two machines is not currently supported; it may
work, it may not, and if it doesn't work it's not a bug. It was
unsupported but working in 1.4; I haven't checked on it in 2 yet but if
there's sufficient demand I could be persuaded to do it at some point...

> Could not open required defaults file:
> /home/tris/.kde/share/apps/amarok/my.cnf                                                                                                   
> Fatal error in defaults handling. Program aborted                                                                                                                                 
> 091226 16:18:12 [Warning] Can't create test file
> /home/tris/.kde/share/apps/amarok/mysqle/vostok.lower-test                                                                       
> 091226 16:18:12 [Warning] Can't create test file
> /home/tris/.kde/share/apps/amarok/mysqle/vostok.lower-test                                                                       
> 091226 16:18:12 [Note] Plugin 'FEDERATED' is disabled                                                                                                                            
> 091226 16:18:12  InnoDB: Operating system error number 13 in a file
> operation.                                                                                                    
> InnoDB: The error means mysqld does not have the access rights to                                                                                                                 
> InnoDB: the directory.                                                                                                                                                            
> InnoDB: File name ./ibdata1                                                                                                                                                       
> InnoDB: File operation call: 'create'.                                                                                                                                            
> InnoDB: Cannot continue  operation.                                                                                                                                                

Have you checked permissions on the my.cnf file/mysqle directory? Both
the first error (not being able to open the my.cnf file) and the last
one ("mysqld does not have access rights to the directory") seem to
pretty clearly indicate that there's a permissions problem.

> There seems to be a couple of warnings / errors that come up and I've tried
> a few things like stopping the running mysql service, playing with
> permissions of the ./mysqle dir etc but I think that the main concern is
> that the my.cnf file in the base directory is empty and doesn't contain any
> configuration.

The my.cnf file in the base directory is supposed to be empty.

--Jeff

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://mail.kde.org/pipermail/amarok/attachments/20091226/f8b0eb39/attachment.sig>