Hi, I've got a farm I've been playing around with - mainly for testing purposes. When I shut it down last week , it will not restart correctly.
Its the mysql server thats causing me some problems. Its failiing when looking for a non-existant snapshot / bundle on s3: Jun 1 08:14:17 ec2-72-44-46-33 logger: SCALR(mysql-init.sh): ERROR: S3 error: 404 (Not Found). Retrying. Jun 1 08:14:18 ec2-72-44-46-33 logger: SCALR(mysql-init.sh): Failed to fetch 's3://XXXXX/farm-mysql/mysql-snapshot.tar' to '/mnt/ tmp.BaASfk2016/mysql-snapshot.tar' for 4 tries. Jun 1 08:14:18 ec2-72-44-46-33 logger: SCALR(mysql-init.sh): Could not fetch MySQL data snapshot using index s3://XXXXXXXXX/farm-mysql/ mysql-snapshot.tar. Jun 1 08:14:19 ec2-72-44-46-33 logger: SCALR(instance-up.sh): /usr/ local/aws/bin/mysql-init.sh failed. Exiting. Looking at s3 via a firefox extension, I cannot see mysql-snapshot.tar but can see lots of :mysql-snapshot.tar.XXX e.g. mysql- snapshot.tar.aao I was only testing and the database is not needed. How can I get scalr to regenerate the missing mysql-snapshot file ? AND/OR reset mysql back to its initial status when I first made the farm? (I've tried logging into instance and running mysql-data-bundle.sh in aws/scripts - it fails) Thanks in advance. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
