Hey all. I’m running into an issue where

sst start

or

sst deploy

hangs at the

Deploying Stacks

stage, it looks like it is caused by the following message from debug logs:

LoggingEvent {
  startTime: 2022-02-11T20:00:19.337Z,
  categoryName: 'cdk',
  data: [
    '2022-02-11T20:00:19.336Z proxy-agent creating new ProxyAgent instance: undefined\n'
  ],
  level: Level { level: 5000, levelStr: 'TRACE', colour: 'blue' },
  context: {},
  pid: 64731
}

And error :

LoggingEvent {
  startTime: 2022-02-11T20:00:40.219Z,
  categoryName: 'core',
  data: [
    'deploy stack: run cdk deploy: stderr:',
    "2022-02-11T20:00:40.218Z proxy-agent cache hit with key: 'no proxy secure'\n"
  ],
  level: Level { level: 5000, levelStr: 'TRACE', colour: 'blue' },
  context: {},
  pid: 64731
}

I’m assuming this is purely related to aws cdk and not sst, but wanted to see if anyone has encountered an issue like this before.

Hey @Zack McKenna, can u run

sst build

and then send me the

.build/sst-debug.log

file?

will do, thanks!

@Zack McKenna just following up here to see if you had a chance to send Frank the debug log?

@Jay yes I was able to! It turned out there were issues with bootstrapping the CDK tool stack and role creation which was in the verbose logs but not the debug logs.

Glad to hear it!