Skip to content

batchiepatchie backend crashes when new job spins up #93

@erhaben-Raupe

Description

@erhaben-Raupe

We have batchie patchie running in a production setup. Whenever new job spins up backend throws nil pointer reference and crashes.

{"level":"info","msg":"Logging ECS cluster statuses.","time":"2023-01-19T11:25:36Z"}
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xa54007]

goroutine 11 [running]:
github.com/AdRoll/batchiepatchie/jobs.MonitorECSClusters({0x7f192019aff8, 0xc000012c60}, {0x160a640, 0x0, 0x1?})
	/home/ubuntu/batchiepatchie/jobs/monitor_ecs_clusters.go:126 +0x16e7
github.com/AdRoll/batchiepatchie/syncer.RunPeriodicScaler.func1()
	/home/ubuntu/batchiepatchie/syncer/batchsync.go:296 +0x13e
created by github.com/AdRoll/batchiepatchie/syncer.RunPeriodicScaler
	/home/ubuntu/batchiepatchie/syncer/batchsync.go:287 +0x6a

This happens when the job status is STARTING in AWS console. When the status change to RUNNING I can restart batchiepatchie again.

FYI, my setup is running on ubuntu 22.04 in an EC2 and the capacity provider for batch is Fargate

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions