Hi, Jay, Thanks for your help. Do you mean we should check the ssh errors with -vv while connecting to the auto-generated instances on AWS China by Scalr?
Best Wishes, Brant On Thursday, June 2, 2016 at 9:59:37 PM UTC+8, Jay Farschman wrote: > > Hey Brant, > > I'm with Marc... check the ssh errors using a manual connection with the > -vv switch. That will expose a lot of additional communication and > probably give you your answer. > > 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.
