runtime error: invalid memory address or nil pointer dereference

1

flyctl secrets set and fly deploy are failing with the error above.

$ fly secrets set MUCH_CLANDESTINE="such_hidden"

Oops, something went wrong! Could you try that again?

runtime error: invalid memory address or nil pointer dereference
goroutine 1 [running]:
runtime/debug.Stack()
	/home/runner/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.22.6.linux-amd64/src/runtime/debug/stack.go:24 +0x5e
github.com/superfly/flyctl/internal/sentry.printError({0x2432d20, 0x40a6f30})
	/home/runner/work/flyctl/flyctl/internal/sentry/sentry.go:190 +0x16f
github.com/superfly/flyctl/internal/sentry.Recover({0x2432d20, 0x40a6f30})
	/home/runner/work/flyctl/flyctl/internal/sentry/sentry.go:180 +0xb4
main.run.func1()
	/home/runner/work/flyctl/flyctl/main.go:40 +0x2f
panic({0x2432d20?, 0x40a6f30?})
	/home/runner/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.22.6.linux-amd64/src/runtime/panic.go:770 +0x132
github.com/superfly/flyctl/internal/command/deploy.(*machineDeployment).setMachineReleaseData(0xc000023c80, 0x0)
	/home/runner/work/flyctl/flyctl/internal/command/deploy/machines_launchinput.go:197 +0x26b
github.com/superfly/flyctl/internal/command/deploy.(*machineDeployment).launchInputForRestart(0x457bc9?, 0xc000396dc0)
	/home/runner/work/flyctl/flyctl/internal/command/deploy/machines_launchinput.go:17 +0x65
github.com/superfly/flyctl/internal/command/deploy.(*machineDeployment).restartMachinesApp.func1({0x2d1c878, 0xc000a963c0}, 0x0?)
	/home/runner/work/flyctl/flyctl/internal/command/deploy/machines_deploymachinesapp.go:226 +0x3b
github.com/samber/lo.Map[...]({0xc0003c67c0?, 0x2, 0x27f5e03}, 0xc000955278?)
	/home/runner/go/pkg/mod/github.com/samber/lo@v1.47.0/slice.go:30 +0x6f
github.com/superfly/flyctl/internal/command/deploy.(*machineDeployment).restartMachinesApp(0xc000023c80, {0x2d01d10, 0xc000accea0})
	/home/runner/work/flyctl/flyctl/internal/command/deploy/machines_deploymachinesapp.go:225 +0x12f
github.com/superfly/flyctl/internal/command/deploy.(*machineDeployment).DeployMachinesApp(0xc000023c80, {0x2d01d10, 0xc000513da0})
	/home/runner/work/flyctl/flyctl/internal/command/deploy/machines_deploymachinesapp.go:85 +0x48b
github.com/superfly/flyctl/internal/command/secrets.DeploySecrets({0x2d01d10, 0xc00038a090}, 0xc0007f23f8, 0x0, 0x0)
	/home/runner/work/flyctl/flyctl/internal/command/secrets/secrets.go:98 +0x2d5
github.com/superfly/flyctl/internal/command/secrets.SetSecretsAndDeploy({0x2d01d10, 0xc00038a090}, 0xc0007f23f8, 0xc0009caed0, 0x0, 0x0)
	/home/runner/work/flyctl/flyctl/internal/command/secrets/set.go:75 +0xb4
github.com/superfly/flyctl/internal/command/secrets.runSet({0x2d01d10, 0xc00038a090})
	/home/runner/work/flyctl/flyctl/internal/command/secrets/set.go:66 +0x445
github.com/superfly/flyctl/internal/command/secrets.newSet.New.newRunE.func2(0xc000662f08, {0xc0002f2850?, 0x4?, 0x27a50f6?})
	/home/runner/work/flyctl/flyctl/internal/command/command.go:140 +0x1d9
github.com/spf13/cobra.(*Command).execute(0xc000662f08, {0xc0002f2820, 0x1, 0x1})
	/home/runner/go/pkg/mod/github.com/spf13/cobra@v1.8.1/command.go:985 +0xaca
github.com/spf13/cobra.(*Command).ExecuteC(0xc000026608)
	/home/runner/go/pkg/mod/github.com/spf13/cobra@v1.8.1/command.go:1117 +0x3ff
github.com/spf13/cobra.(*Command).ExecuteContextC(...)
	/home/runner/go/pkg/mod/github.com/spf13/cobra@v1.8.1/command.go:1050
github.com/superfly/flyctl/internal/cli.Run({0x2d01e98?, 0xc0005f1880?}, 0xc0000cf180, {0xc000050090, 0x3, 0x3})
	/home/runner/work/flyctl/flyctl/internal/cli/cli.go:94 +0x69a
main.run()
	/home/runner/work/flyctl/flyctl/main.go:47 +0x156
main.main()
	/home/runner/work/flyctl/flyctl/main.go:26 +0x18

It’s been happening since yesterday (around 10H UTC).

1 Like
2

Good day,

The problem still persists. I have been unable to deploy this week because of it.

3

Hi @timkofu, thanks for the report, we’re still investigating this deploy error.

Does the app you’re trying to deploy have any unavailable machines (on degraded/offline hosts) in them? If so, removing them with fly machine destroy --force might unblock your deploy while we look into a further fix for this issue.

4

@wjordan This worked. Thanks.

5

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.