PHWinfo - Afficher un message - Copying InnoDB files to remote server -> remote server won't start

11/09/2007, 23h17

Michael Dykman wrote:
> if you see no errors, check your config... are you sure InnoDB is enabled ?

I can create a new database and add InnoDB tables to it without problems.

Ack, I lied. No error in the /var/lib/mysql, but there IS an error file
in /var/logs, and it contains:

"./ibdata1: error 13 in a file operation"
"mysqld does not have access rights to the directory"

But..... I'm sitting here looking and I can't see any difference between
the ibdata1 and the ibdata1_orig files, nor the folders that contain the
..frm files either.

There must be something but I sure can't see it...

Whil

> On 9/11/07, Whil Hentzen <amp07@softwaremuscle.com> wrote:
>> Hi gang,
>>
>> After reading through two years of 'how do I back up my database'
>> threads, I'm trying out the various backup mechanisms offered up.
>>
>> I've read through these steps:
>> http://dev.mysql.com/doc/refman/5.0/...db-backup.html
>>
>> Running a local box and a remote box, both with Fedora 6, MySQL 5.
>> Trying to copy a local /var/lib/mysql/mydata InnoDB.
>>
>> The problem: After I copy InnoDB files to a remote box, the MySQL server
>> on the remote box won't restart. Here are the steps I've followed:
>>
>> 1. Stop the local and remote servers
>> 2. Rename the remote ibdata and ib_logfile0 files
>> 3. Copy the local ibdata and ib_logfile0 files to the remote
>> /var/lib/mysql folder
>> 4. Copy the local /var/lib/mysql/mydata/* to the remote
>> /var/lib/mysql/mydata/* folder (contains one .frm and db.opt)
>> 5. Change the ownership of the remote files and folders to 'mysql'
>> 6. Restart the remote server (service mysqld start)
>> 7. Failure, with a 'timeout' error
>>
>> There is no error log created in the remote /var/lib/mysql folder.
>>
>> When I rid the copied files and folders, and then rename the originals
>> back to their initial names, the server starts up nice and neat again.
>>
>> I can copy a MyISAM database from the local box to the remote box and it
>> is accessible via the remote MySQL server just fine.
>>
>> Obviously, there is something wrong in the way I'm copying the InnoDB
>> files.
>>
>> What am I missing?
>>
>> Whil
>>
>> --
>> MySQL General Mailing List
>> For list archives: http://lists.mysql.com/mysql
>> To unsubscribe: http://lists.mysql.com/mysql?unsub=mdykman@gmail.com
>>
>>
>
>

11/09/2007, 23h17	#2
Whil Hentzen Messages: n/a Hébergeur:	Re: Copying InnoDB files to remote server -> remote server won'tstart Michael Dykman wrote: > if you see no errors, check your config... are you sure InnoDB is enabled ? I can create a new database and add InnoDB tables to it without problems. Ack, I lied. No error in the /var/lib/mysql, but there IS an error file in /var/logs, and it contains: "./ibdata1: error 13 in a file operation" "mysqld does not have access rights to the directory" But..... I'm sitting here looking and I can't see any difference between the ibdata1 and the ibdata1_orig files, nor the folders that contain the ..frm files either. There must be something but I sure can't see it... Whil > On 9/11/07, Whil Hentzen <amp07@softwaremuscle.com> wrote: >> Hi gang, >> >> After reading through two years of 'how do I back up my database' >> threads, I'm trying out the various backup mechanisms offered up. >> >> I've read through these steps: >> http://dev.mysql.com/doc/refman/5.0/...db-backup.html >> >> Running a local box and a remote box, both with Fedora 6, MySQL 5. >> Trying to copy a local /var/lib/mysql/mydata InnoDB. >> >> The problem: After I copy InnoDB files to a remote box, the MySQL server >> on the remote box won't restart. Here are the steps I've followed: >> >> 1. Stop the local and remote servers >> 2. Rename the remote ibdata and ib_logfile0 files >> 3. Copy the local ibdata and ib_logfile0 files to the remote >> /var/lib/mysql folder >> 4. Copy the local /var/lib/mysql/mydata/* to the remote >> /var/lib/mysql/mydata/* folder (contains one .frm and db.opt) >> 5. Change the ownership of the remote files and folders to 'mysql' >> 6. Restart the remote server (service mysqld start) >> 7. Failure, with a 'timeout' error >> >> There is no error log created in the remote /var/lib/mysql folder. >> >> When I rid the copied files and folders, and then rename the originals >> back to their initial names, the server starts up nice and neat again. >> >> I can copy a MyISAM database from the local box to the remote box and it >> is accessible via the remote MySQL server just fine. >> >> Obviously, there is something wrong in the way I'm copying the InnoDB >> files. >> >> What am I missing? >> >> Whil >> >> -- >> MySQL General Mailing List >> For list archives: http://lists.mysql.com/mysql >> To unsubscribe: http://lists.mysql.com/mysql?unsub=mdykman@gmail.com >> >> > >