Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
I've got a server running on Amazon EC2, and I wanted to move the databases off onto a separate Elastic Block Storage volume, which means it persists after a server shutdown (the server's local disks only persist if you've bundled the machine image and stored it in S3).
So no problem: I copied the existing databases across to the new locations (they're just directories), renamed the old ones to something else, created symbolic links to the new locations, and done
Unfortunately, using my remote admin tool, several of my databases then vanished
After googling around for ages, I finally realised that when I'd changed ownership of the new locations and their contents to the mysql user account, I'd done
Code:
chown -r mysql:mysql dbname
instead of
Code:
chown -R mysql:mysql dbname
meaning that rather than recursively changing ownership of the directory and all its contents, I'd instead removed read access to it
All working again now
That is superb! I must pass that off as my own at clientco sometime.
Well imitation is the sincerest form of flattery.....
"I can put any old tat in my sig, put quotes around it and attribute to someone of whom I've heard, to make it sound true."
- Voltaire/Benjamin Franklin/Anne Frank...
Comment