Thanks Nick. Look fwd to the fix. I guess once released Scalrizr will auto update right?
Srini Sent on my BlackBerry® from Vodafone -----Original Message----- From: Nick Toursky <[email protected]> Sender: [email protected] Date: Mon, 10 Sep 2012 18:35:54 To: <[email protected]> Reply-To: [email protected] Subject: Re: Uploading MySQL backup to S3 is failing Srini, We've been able to find a problem with the bucket naming scheme and it will be fixed in one of the coming Scalr releases. Regards, Nick On Sat, Sep 8, 2012 at 6:12 AM, Srinivasan Subramanian < [email protected]> wrote: > Hi Nick > > Any updates on this? > > Cheers > > Srini > > On 9/5/2012 3:00 PM, Nick Toursky wrote: > > Hi Srini, > > Could you provide a full stack trace of Scalarizr error? > > Thanks, > Nick > > On Tuesday, September 4, 2012 6:45:07 AM UTC+3, Srini wrote: >> >> Any updates on this? Backup is critical and it would help to know if I >> have configured something wrongly or this is a bug. >> >> Regards >> Srini >> >> On 9/2/2012 11:57 AM, Srini wrote: >> >> I see the following messages in the log for a newly created farm using >> the Ubuntu MySQL 64bit latest role. >> >> Uploading '/mnt/dbstorage/tmp/tmp4KJWZN/**mysql-backup-2012-09-01-13 >> :00:**08.tar.gz' to S3 under 's3://scalr-1-us-east-1/** >> backups/7/mysql/79-mysql64-**ubuntu1204' >> Cannot process several files. ['/mnt/dbstorage/tmp/** >> tmp4KJWZN/mysql-backup-2012-**09-01-13:00:08.tar.gz'] >> >> As can be seen there is no S3 bucket name being used. >> >> (My older farms using the Centos MySQL role I see the following >> message: Uploading '/mnt/dbstorage/tmp/mysql-**backup-2012-09-01-15 >> :50:07.**tar.gz' to S3 under 's3://farm-<id-here>-us-east-**1) >> >> Is this a bug or am I missing some configuration? >> >> Regards >> Srini >> -- >> You received this message because you are subscribed to the Google Groups >> "scalr-discuss" group. >> To view this discussion on the web visit https://groups.google.com/d/** >> msg/scalr-discuss/-/Qgz_3-**2wMqUJ<https://groups.google.com/d/msg/scalr-discuss/-/Qgz_3-2wMqUJ> >> . >> To post to this group, send email to [email protected]**. >> To unsubscribe from this group, send email to scalr-discus...@** >> googlegroups.com. >> For more options, visit this group at http://groups.google.com/** >> group/scalr-discuss?hl=en<http://groups.google.com/group/scalr-discuss?hl=en> >> . >> >> >> -- > You received this message because you are subscribed to the Google Groups > "scalr-discuss" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/scalr-discuss/-/72x1PBs_YjkJ. > 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. > > > -- > 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. > -- 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. -- 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.
