sst: Nothing error on sst deploy but always interrupted

Hello i am using aws-nextjs example to try sst ion and nothing error but always interrupted, am I wrong?

here’s log verbose

sstv3 deploy --stage staging --verbose
time=2024-05-30T11:15:27.311+07:00 level=INFO msg="checking for pulumi" path=/root/.config/sst/bin/pulumi
time=2024-05-30T11:15:27.490+07:00 level=INFO msg="checking for bun" path=/root/.config/sst/bin/bun
time=2024-05-30T11:15:27.493+07:00 level=INFO msg="initializing project" version=0.0.395
time=2024-05-30T11:15:27.493+07:00 level=INFO msg="esbuild building"
time=2024-05-30T11:15:27.495+07:00 level=INFO msg="esbuild built" outfile=/repo/ion/examples/aws-nextjs/.sst/eval/eval-1717042527493.mjs
time=2024-05-30T11:15:27.496+07:00 level=INFO msg="evaluating config"
time=2024-05-30T11:15:27.529+07:00 level=INFO msg="config evaluated"
time=2024-05-30T11:15:27.529+07:00 level=INFO msg="checking platform"
time=2024-05-30T11:15:27.529+07:00 level=INFO msg="checking provider" name=aws version=latest compare=latest
time=2024-05-30T11:15:27.530+07:00 level=INFO msg="credentials found"
time=2024-05-30T11:15:27.530+07:00 level=INFO msg="fetching bootstrap"
time=2024-05-30T11:15:27.749+07:00 level=INFO msg="found existing bootstrap" data="{\"version\":1,\"asset\":\"sst-asset-nwdrtwhuhncw\",\"state\":\"sst-state-nwdrtwhuhncw\"}"
time=2024-05-30T11:15:27.749+07:00 level=INFO msg="loaded config" app=aws-nextjs stage=staging
SST ❍ ion 0.0.395  ready!

➜  App:        aws-nextjs
   Stage:      staging

time=2024-05-30T11:15:27.749+07:00 level=INFO msg="running stack command" cmd=deploy
time=2024-05-30T11:15:27.750+07:00 level=INFO msg="INFO locking app=aws-nextjs stage=staging"
time=2024-05-30T11:15:27.750+07:00 level=INFO msg="INFO getting data key=lock app=aws-nextjs stage=staging"
time=2024-05-30T11:15:27.914+07:00 level=INFO msg="INFO putting data key=lock app=aws-nextjs stage=staging"
~  Deploying

time=2024-05-30T11:15:28.051+07:00 level=INFO msg="INFO pulling state app=aws-nextjs stage=staging out=/repo/ion/examples/aws-nextjs/.sst/.pulumi/stacks/aws-nextjs/staging.json"
time=2024-05-30T11:15:28.204+07:00 level=INFO msg="INFO getting passphrase app=aws-nextjs stage=staging"
time=2024-05-30T11:15:28.387+07:00 level=INFO msg="INFO getting data key=secret app=aws-nextjs stage=staging"
time=2024-05-30T11:15:28.519+07:00 level=INFO msg="esbuild building"
time=2024-05-30T11:15:28.577+07:00 level=INFO msg="esbuild built" outfile=/repo/ion/examples/aws-nextjs/.sst/platform/eval/eval-1717042528519.mjs
time=2024-05-30T11:15:28.577+07:00 level=INFO msg="tracked files"
time=2024-05-30T11:15:28.749+07:00 level=INFO msg="built workspace"
time=2024-05-30T11:15:28.922+07:00 level=INFO msg="built stack"
time=2024-05-30T11:15:29.111+07:00 level=INFO msg="built config"
time=2024-05-30T11:15:29.111+07:00 level=INFO msg="running stack command" cmd=deploy
time=2024-05-30T11:15:29.698+07:00 level=INFO msg="INFO putting summary app=aws-nextjs stage=staging"
time=2024-05-30T11:15:29.698+07:00 level=INFO msg="INFO putting data key=summary app=aws-nextjs stage=staging/jydpmo0jvrpcmuux41qpd1ef"
time=2024-05-30T11:15:29.846+07:00 level=INFO msg="done running stack command"
time=2024-05-30T11:15:29.846+07:00 level=INFO msg="stack command complete"

×  Interrupted

time=2024-05-30T11:15:30.186+07:00 level=INFO msg="INFO pushing state app=aws-nextjs stage=staging from=/repo/ion/examples/aws-nextjs/.sst/.pulumi/stacks/aws-nextjs/staging.json"
time=2024-05-30T11:15:30.329+07:00 level=INFO msg="INFO unlocking app=aws-nextjs stage=staging"

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 43 (18 by maintainers)

Most upvoted comments

if anyone runs into this run

sst version --verbose

it should print out a config path - delete that folder and try again

I encountered the same issue, and changing the stage resolved it for me.

@jayair I’ve seen this issue on 3.0.75 today as well. Don’t think the PR would’ve fixed it based on the comment from @thdxr

better warning in v3.11.8

I have also encountered this issue inside a github action

I’ve upgraded today and I’m getting this on every deploy.

sst 3.4.56
pulumi 3.143.0

If I delete the config folder listed from sst version --verbose as suggested by @thdxr it’ll work but if I then try and redeploy I get Interrupted again. So at the moment I’m having to delete the folder for each deploy.

Edit: Seems to have resolved itself 🤷 Edit2: Happening again now 😦 Edit3: Now happening consistently, even when removing the config folder.

Still hitting this, even the manual install for pulumi didn’t solve it for me.

The logs always end like this

time=2024-12-16T20:38:42.616+01:00 level=INFO msg="INFO unlocking app=app-name stage=levi"
time=2024-12-16T20:38:42.993+01:00 level=INFO msg="shutting down server"
time=2024-12-16T20:38:42.993+01:00 level=INFO msg="server done"

Oddly enough the unlock command completes if run alone.

@thdxr suggested that I manually install Pulumi in the /Users/user/Library/Application Support/sst/bin/, which solved the issue.

https://github.com/pulumi/pulumi/releases

Can we get the .sst/log for this when this happens?

I get the same result having done all of

sst refresh
sst unlock
sst remove

The same two errors are in the logs when running sst dev next dev:

time=2024-06-27T09:19:20.874+10:00 level=ERROR msg="stack run failed" error="failed to run update: exit status 255\ncode: 255\nstdout: Updating (brendankerrison):\n\nstderr: error: failed to load language plugin nodejs: could not read plugin [/Users/brendan.kerrison/Library/Application Support/sst/bin/pulumi-language-nodejs] stdout: EOF\n\n"
time=2024-06-27T09:19:22.082+10:00 level=ERROR msg="exited with error" err="read tcp 127.0.0.1:51521->127.0.0.1:13557: use of closed network connection"

Not sure how it could have gotten into a state where pulumi cannot load the nodejs plugin, not how to resolve it.

@liltechnomancer but it works for other stages for you?