Marc 'risson' Schmitt
Marc 'risson' Schmitt
Thanks for the pointer, the dump is too big for github. I've uploaded it to https://bin.lama-corp.space/upload/eel-camel-jaguar (expires in 7 days). Happy to provide any additional information
I've put the sysdump on my nextcloud instead, it shouldn't expire now: https://cloud.lama-corp.space/s/TDXmkdF5CLqqLS7 I've also tried moving the IP in an interface that isn't down, and that directly has default...
The line that stands out, with the gateway IP not looking quite right: ``` time=2025-06-20T13:14:00Z level=debug source=/go/src/github.com/cilium/cilium/pkg/egressgateway/manager.go:666 msg="IPv4 egress gateway policy applied" module=agent.controlplane.egressgateway sourceIP=172.28.131.6 destinationCIDR=0.0.0.0/0 egressIP=148.251.148.232 gatewayIP=2001:67c:17fc:101::11 ``` But just...
Is there anything I can try on my end?
I cannot reproduce with the images from the PR you linked, aka the issue is fixed. The log line now reads: ``` time=2025-06-25T15:03:57.597680463Z level=debug source=/go/src/github.com/cilium/cilium/pkg/egressgateway/manager.go:667 msg="IPv4 egress gateway policy applied"...
Unfortunately we stopped using this library and instead re-wrote an implementation more suitable for our needs. Our main problem was that the postgres pool wasn't scoped to a specific loop,...
Hi, we are unable to reproduce this stacktrace. Do you have any other error that could cause this one maybe?
Yeah, if you could look in the worker logs, where the sync happens, and give us the full stacktrace.
Will look into that for 2024.8
Superseeds #13436 #9607 #6845