Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed Machine provisions can lead to nil pointer panic. #18

Open
davissp14 opened this issue May 8, 2024 · 0 comments
Open

Failed Machine provisions can lead to nil pointer panic. #18

davissp14 opened this issue May 8, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@davissp14
Copy link
Contributor

// 2024-05-08T00:32:15Z app[4d896d4b592258] ord [info]api     | INFO[382714] Preparing job...                              app-name=shaun-pg-flex job-id=15516 schedule=uptime-check
// 2024-05-08T00:32:15Z app[4d896d4b592258] ord [info]monitor | panic: runtime error: invalid memory address or nil pointer dereference
// 2024-05-08T00:32:15Z app[4d896d4b592258] ord [info]monitor | [signal SIGSEGV: segmentation violation code=0x1 addr=0xe8 pc=0x7734bc]
// 2024-05-08T00:32:15Z app[4d896d4b592258] ord [info]monitor |
// 2024-05-08T00:32:15Z app[4d896d4b592258] ord [info]monitor | goroutine 9 [running]:
// 2024-05-08T00:32:15Z app[4d896d4b592258] ord [info]monitor | github.com/fly-apps/cron-manager/internal/cron.findEvent(...)
// 2024-05-08T00:32:15Z app[4d896d4b592258] ord [info]monitor | 	/app/internal/cron/monitor.go:172
// 2024-05-08T00:32:15Z app[4d896d4b592258] ord [info]monitor | github.com/fly-apps/cron-manager/internal/cron.evaluateJob({0xaadf90, 0xde9e40}, 0xc0000ac300?, 0xc000032158, {0x1ede, 0x4, {0xc000014c78, 0x7}, {{0x0, 0x0}, ...}, ...})
// 2024-05-08T00:32:15Z app[4d896d4b592258] ord [info]monitor | 	/app/internal/cron/monitor.go:91 +0x9fc
// 2024-05-08T00:32:15Z app[4d896d4b592258] ord [info]monitor | github.com/fly-apps/cron-manager/internal/cron.MonitorActiveJobs.func1({0x1ede, 0x4, {0xc000014c78, 0x7}, {{0x0, 0x0}, 0x0}, {{0x0, 0x0}, 0x0}, ...})
// 2024-05-08T00:32:15Z app[4d896d4b592258] ord [info]monitor | 	/app/internal/cron/monitor.go:40 +0xbb
// 2024-05-08T00:32:15Z app[4d896d4b592258] ord [info]monitor | panic: runtime error: invalid memory address or nil pointer dereference
// 2024-05-08T00:32:15Z app[4d896d4b592258] ord [info]monitor | [signal SIGSEGV: segmentation violation code=0x1 addr=0xe8 pc=0x7734bc]
// 2024-05-08T00:32:15Z app[4d896d4b592258] ord [info]monitor |
// 2024-05-08T00:32:15Z app[4d896d4b592258] ord [info]monitor | goroutine 8 [running]:
// 2024-05-08T00:32:15Z app[4d896d4b592258] ord [info]monitor | github.com/fly-apps/cron-manager/internal/cron.findEvent(...)
// 2024-05-08T00:32:15Z app[4d896d4b592258] ord [info]monitor | 	/app/internal/cron/monitor.go:172
// 2024-05-08T00:32:15Z app[4d896d4b592258] ord [info]monitor | github.com/fly-apps/cron-manager/internal/cron.evaluateJob({0xaadf90, 0xde9e40}, 0xc0000ac300?, 0xc000032158, {0x1edd, 0x4, {0xc000014ba8, 0x7}, {{0x0, 0x0}, ...}, ...})
// 2024-05-08T00:32:15Z app[4d896d4b592258] ord [info]monitor | 	/app/internal/cron/monitor.go:91 +0x9fc
// 2024-05-08T00:32:15Z app[4d896d4b592258] ord [info]monitor | github.com/fly-apps/cron-manager/internal/cron.MonitorActiveJobs.func1({0x1edd, 0x4, {0xc000014ba8, 0x7}, {{0x0, 0x0}, 0x0}, {{0x0, 0x0}, 0x0}, ...})
// 2024-05-08T00:32:15Z app[4d896d4b592258] ord [info]monitor | 	/app/internal/cron/monitor.go:40 +0xbb
// 2024-05-08T00:32:15Z app[4d896d4b592258] ord [info]monitor | created by github.com/fly-apps/cron-manager/internal/cron.MonitorActiveJobs in goroutine 1
// 2024-05-08T00:32:15Z app[4d896d4b592258] ord [info]monitor | 	/app/internal/cron/monitor.go:38 +0x230
// 2024-05-08T00:32:15Z app[4d896d4b592258] ord [info]monitor | exit status 2
// 2024-05-08T00:32:15Z app[4d896d4b592258] ord [info]monitor | restarting in 5s [attempt 14]
@davissp14 davissp14 added the bug Something isn't working label May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant