-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
v3.0.0: loki backend SIGSEGV if index_gateway.mode: ring #12270
Comments
Closing since there have been some releases since, if it still happens I'll reopen |
Happend for me today while deploying a simple scalable loki 3.0.0 only on backend pod |
The same problem only the difference i have 3 pods 2 are ok 1 - CrashLoopBack k8 logs -n observability loki-backend-1 -c loki goroutine 1 [running]: |
@alexandergoncharovaspecta Can you provide your config? |
I am able to reproduce the bug on the $ ./cmd/loki/loki -target=backend -index-gateway.mode=ring
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x288 pc=0x22efff0]
goroutine 1 [running]:
github.com/grafana/loki/v3/pkg/loki.(*Loki).updateConfigForShipperStore(0xc0008b8960?)
/home/christian/sandbox/grafana/loki/pkg/loki/modules.go:755 +0xb0
github.com/grafana/loki/v3/pkg/loki.(*Loki).initBloomStore(0xc0007c9500)
/home/christian/sandbox/grafana/loki/pkg/loki/modules.go:715 +0x68
github.com/grafana/dskit/modules.(*Manager).initModule(0xc00063c780, {0x7fffab192a32, 0x7}, 0x1?, 0xc000eb8d20?)
/home/christian/sandbox/grafana/loki/vendor/github.com/grafana/dskit/modules/modules.go:136 +0x1f7
github.com/grafana/dskit/modules.(*Manager).InitModuleServices(0x0?, {0xc000a0dc20, 0x1, 0xc000eb8bd0?})
/home/christian/sandbox/grafana/loki/vendor/github.com/grafana/dskit/modules/modules.go:108 +0xd8
github.com/grafana/loki/v3/pkg/loki.(*Loki).Run(0xc0007c9500, {0x0?, {0x4?, 0x3?, 0x493d3e0?}})
/home/christian/sandbox/grafana/loki/pkg/loki/loki.go:453 +0x9d
main.main()
/home/christian/sandbox/grafana/loki/cmd/loki/main.go:122 +0x113b
|
The bloom store initialisation updates the shipper configuration which in turn requires the index gateway ring to be initialized in case `-index-gateway.mode` is set to `ring`. Therefore the `BloomStore` module needs to depend on the `IndexGatewayRing` module. Fixes #12270 Signed-off-by: Christian Haudum <christian.haudum@gmail.com>
YesSource: loki/templates/config.yamlapiVersion: v1
|
The bloom store initialisation updates the shipper configuration which in turn requires the index gateway ring to be initialised in case `-index-gateway.mode` is set to `ring`. Therefore the `BloomStore` module needs to depend on the `IndexGatewayRing` module. Fixes #12270 Signed-off-by: Christian Haudum <christian.haudum@gmail.com>
I am experiencing the same kubectl logs loki-backend-1 -c loki
|
What is the fix for this issue? |
I see index_gateway.mode from ring to simple. was the fix
|
fixed this making change to helm https://github.com/grafana/loki/blob/main/production/helm/loki/values.yaml#L337-L345
|
pod is coming up but loki is not working as expected
when used I am getting same error:
|
i had to use the service IP in vector endpoint along with previous fix
now its working as expected |
I ran into this crash too upgrading from v2.9.x to v3.0.0. Changing the mode from ring to simple fixed this crash (but still working through other problems). |
I'm hitting the same problem |
Describe the bug
Running version
grafana/loki:main-0bf894b
,loki-backend
(replicas: 1
) crashes:Workaround: edit the configmap, change
index_gateway.mode
fromring
tosimple
.Note that I use tsdb, having a boltdb config or not in
storage_config
does not change anything.Environment:
The text was updated successfully, but these errors were encountered: