Hi Brant, We do have insight in to this issue, but we must first confirm the source of this copy of Scalr Enterprise Edition. Can you please let us know the sales contact with Scalr who provided you this copy of Enterprise Edition? If you are in the process of an official evaluation of EE we need to communicate and support through the correct channels with your sales contact.
Many thanks, Wm. Marc O'Brien Scalr Technical Support On Thursday, June 2, 2016 at 12:54:15 PM UTC-6, Brant Fortest wrote: > > Hi, Marc, > Just checked again, we have no support for this edition. We're still > evaluating it. > 1st, I want to make sure that our version now - 5.11.18(6 Apr 2016) is > in the safe zone that wouldn't cause this stuck snapshot issue in china > region. > 2nd, I just tried to build an image again, the same problem occurred, and > I've attached those log files from the aws china instance. Please take a > look. > Thanks! > > > Best Wishes, > Brant > > On Friday, June 3, 2016 at 1:21:36 AM UTC+8, Marc O'Brien wrote: >> >> Hi Brant, >> >> Before we continue any investigation, we need to clarify who your sales >> contact was that provided access to Scalr Enterprise Edition. Please let >> us know who your contact was, or reach out to our Sales team at >> [email protected] so that we may re-engage and set you up for success >> moving forward. >> >> Many thanks, >> Wm. Marc O'Brien >> Scalr Technical Support >> >> >> >> On Thursday, June 2, 2016 at 11:17:00 AM UTC-6, Brant Fortest wrote: >>> >>> Hi, Marc, >>> What's your minimum version requirement for AWS China region? >>> You'd supported AWS China in Scalr since Sep., 2014, right? >>> https://scalr-wiki.atlassian.net/wiki/display/docs/2014/09 >>> How can we upgrade to the latest version compatible with AWS China >>> without affecting any existing data on Scalr server? >>> Any log files we can investigate on Scalr server side? Thanks! >>> >>> >>> Best Wishes, >>> Brant >>> >>> On Thursday, June 2, 2016 at 4:33:02 AM UTC+8, Marc O'Brien wrote: >>>> >>>> Hi Brant, >>>> >>>> Are you receiving any errors when you attempt to use that key? In >>>> order to set you up for success moving forward, can you clarify who your >>>> Sales contact is who provided you access to Enterprise Edition of Scalr? >>>> It appears you are using an outdated version of Enterprise Edition and we >>>> need to ensure that you are using the correct support communication >>>> channels. >>>> >>>> Many thanks, >>>> Wm. Marc O'Brien >>>> Scalr Technical Support >>>> >>>> On Wednesday, June 1, 2016 at 1:56:16 PM UTC-6, Brant Fortest wrote: >>>>> >>>>> >>>>> The private key I downloaded from Scalr / SSH Keys cannot login that >>>>> instance. >>>>> >>>>> Brant >>>>> >>>>> On Thursday, June 2, 2016 at 12:27:06 AM UTC+8, Marc O'Brien wrote: >>>>>> >>>>>> Hi Brant, >>>>>> >>>>>> Could you please provide your scalarizr logs: >>>>>> /var/log/scalarizr_*.log as well as the role_builder log in the same >>>>>> folder >>>>>> on the instance? This should give us a starting point for investigation. >>>>>> >>>>>> Many thanks, >>>>>> Wm. Marc O'Brien >>>>>> Scalr Technical Support >>>>>> >>>>>> >>>>>> >>>>>> On Sunday, May 29, 2016 at 11:37:32 PM UTC-6, Brant Fortest wrote: >>>>>>> >>>>>>> Hi, Team, >>>>>>> >>>>>>> Our Scalr Upgraded to latest Release 5.11.18 >>>>>>> >>>>>>> >>>>>>> - After we added an user in cn-noth-1 (China), account type “AWS >>>>>>> CHINA”, everything seemed to be working just fine. >>>>>>> >>>>>>> But we are having some issues building the first base images. it >>>>>>> seems to be stuck in phase of creating the base image snapshot. >>>>>>> >>>>>>> >>>>>>> - Everything under another REGULAR Account is looking good. >>>>>>> >>>>>>> Any suggestions about this issue? What am I missing here ? Thanks! >>>>>>> >>>>>>> >>>>>>> Looking forward to hearing from you ASAP. >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> Yours sincerely, >>>>>>> >>>>>>> Brant >>>>>>> >>>>>> -- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
