Nil pointer dereference exception in libbeat/processors/add_kubernetes_metadata/kubernetes.go:161

(Okke Formsma) #1

I am seeing an issue in Filebeat 6.2.2. I'm running libbeat in a container on Kubernetes. Every other hour, the process will crash with the following stack trace:

panic: runtime error: invalid memory address or nil pointer dereference
	March 11th 2018, 11:51:44.107	167,691	[signal SIGSEGV: segmentation violation code=0x1 addr=0x158 pc=0x13dd8ba]

goroutine 76 [running]:*ContainerIndexer).GetIndexes(0xc42040a1f0, 0x0, 0xc4203ec900, 0xc4204bd620, 0xc4204bd560)
/go/src/ +0x3a*Indexers).GetIndexes(0xc4203ec900, 0x0, 0x0, 0x0, 0x0)
/go/src/ +0x230*kubernetesAnnotator).removePod(0xc42018e620, 0x0)
/go/src/ +0x3d*kubernetesAnnotator).(
/go/src/ +0x34, 0xc420956060)
/go/src/ +0x78*kubernetesAnnotator).worker(0xc42018e620)
/go/src/ +0x26f
created by
/go/src/ +0x9f7

The offending line of code is the following:

Any clue to why this might happen?

(Carlos PĂ©rez Aradros) #2

Hi @okke-formsma,

Thank you for reporting this! Actually this was a known issue that was recently fixed:

Next version (6.2.3) will be released soon, and it will pack a fix for this!

Best regards

(Okke Formsma) #3

Hi @exekias,

Thanks for the reply! I hadn't seen that github issue.



(system) #4

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.