Channels
pulumi-ai
package-authoring
pulumi-cdk
oracle-cloud-infrastructure
learn-pulumi-events
linen
registry
built-with-pulumi
pulumi-cloud
contribex
testingtesting321
hacktoberfest
cloudengineering
yaml
pulumi-crosscode
content-share
finops
multi-language-hackathon
office-hours
workshops
blog-posts
localstack
welcome
gitlab
pulumi-kubernetes-operator
jobs
aws
pulumi-deployments
dotnet
golang
announcements
java
pulumiverse
python
install
getting-started
cloudengineering-support
testingtesting123
hackathon-03-19-2020
typescript
google-cloud
contribute
azure
kubernetes
docs
automation-api
status
general
Title
w
wet-noon-14291
10/26/2022, 10:02 PMAnyone that has experience
pulumi up➜ deploy git:(deps/minimist_1.2.7) ✗ pulumi up
View Live: https://.....
[1] 3433262 killed pulumi up
➜ deploy git:(deps/minimist_1.2.7) ✗this happens both on the local machine and on my build server.
To get it working again I had to remove the stack all together and then create it again, not ideal but worked this time. I tried to do a verbose debug during
pulumi upe
echoing-dinner-19531
10/27/2022, 7:29 AMNot seen this, if it repros you might want to run with debug logs on
--logtostderr -v10w
wet-noon-14291
10/27/2022, 10:23 AMI did v9, but nothing useful.
e
echoing-dinner-19531
10/27/2022, 10:26 AMMight be out of memory? Is this a large stack, or using a lot of nested parent resources?
w
wet-noon-14291
10/27/2022, 10:28 AMThe stack was pretty small, so I’m pretty sure that isn’t the case.
e
echoing-dinner-19531
10/27/2022, 10:39 AMMight be worth checking that, try running top while running up and keeping an eye on usage, the only time I've seen pulumi getting killed like this has been the oom killer
w
wet-noon-14291
10/27/2022, 2:19 PMAs mentioned, I was washer trying to fix it yesterday and I did by doing a rm on the stack and then try again which lead me to believe that there was something related to the pulumi service.
e
echoing-dinner-19531
10/27/2022, 2:49 PMoh interesting, I'll keep an eye out for anything like this coming up again. There was some service latency the other day but I wouldn't expect it to trigger process kills
w
wet-noon-14291
10/28/2022, 7:30 PMDon't think it was a service latency either since other updates worked fine, it was just this one that failed over and over again.