Skip to content
This repository has been archived by the owner on Jun 16, 2022. It is now read-only.

rio-autoscaler panic #12

Open
sdhoward opened this issue Oct 26, 2020 · 0 comments
Open

rio-autoscaler panic #12

sdhoward opened this issue Oct 26, 2020 · 0 comments

Comments

@sdhoward
Copy link

found the following in my logs, maybe you will find it useful

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x11f039b]
goroutine 173369 [running]:
github.com/rancher/rio-autoscaler/pkg/controllers/servicescale.(*SimpleScale).Scale(0xc000bc2000, 0x0, 0x0)
/go/src/github.com/rancher/rio-autoscaler/pkg/controllers/servicescale/scaler.go:149 +0x1ab
github.com/rancher/rio-autoscaler/pkg/controllers/servicescale.(*SimpleScale).Start.func2(0xc000bc2000)
/go/src/github.com/rancher/rio-autoscaler/pkg/controllers/servicescale/scaler.go:208 +0xf7
created by github.com/rancher/rio-autoscaler/pkg/controllers/servicescale.(*SimpleScale).Start
/go/src/github.com/rancher/rio-autoscaler/pkg/controllers/servicescale/scaler.go:203 +0x8d

When we see this message, we are doing rio up and then rio scale. We haven't noticed any impact from this; the autoscaler restarts and seems to do the right thing.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant