Okta Module Crashing Constantly

Hello,

I'm using Elastic 7.7 and wanted to try out the newly-released Okta module. I can get it running for about a minute at a time, during which I can see that it's sending logs to Elasticsearch as expected, but it always crashes with a httpjson error:

2020-05-19T14:49:36.130Z	INFO	[httpjson]	runtime/panic.go:679	httpjson input worker has stopped.	{"url": "https://[instance].okta.com/api/v1/logs"}
panic: non-positive interval for NewTicker

goroutine 427 [running]:
time.NewTicker(0xfffffffff8349d12, 0xed655e900)
	/usr/local/go/src/time/tick.go:23 +0x147
github.com/elastic/beats/v7/x-pack/filebeat/input/httpjson.(*HttpjsonInput).applyRateLimit(0xc000366690, 0x3e13a20, 0xc0003c4bc0, 0xc0011ff200, 0xc00053fa10, 0x0, 0x0)
	/go/src/github.com/elastic/beats/x-pack/filebeat/input/httpjson/input.go:243 +0x1a2
github.com/elastic/beats/v7/x-pack/filebeat/input/httpjson.(*HttpjsonInput).processHTTPRequest(0xc000366690, 0x3e13a20, 0xc0003c4bc0, 0xc000dd7e60, 0xc000e23e08, 0xdf8475800, 0x3da8ae0)
	/go/src/github.com/elastic/beats/x-pack/filebeat/input/httpjson/input.go:304 +0x337
github.com/elastic/beats/v7/x-pack/filebeat/input/httpjson.(*HttpjsonInput).run(0xc000366690, 0x0, 0x0)
	/go/src/github.com/elastic/beats/x-pack/filebeat/input/httpjson/input.go:425 +0x38f
github.com/elastic/beats/v7/x-pack/filebeat/input/httpjson.(*HttpjsonInput).Run.func1.1(0xc000366690)
	/go/src/github.com/elastic/beats/x-pack/filebeat/input/httpjson/input.go:122 +0x1d6
created by github.com/elastic/beats/v7/x-pack/filebeat/input/httpjson.(*HttpjsonInput).Run.func1
	/go/src/github.com/elastic/beats/x-pack/filebeat/input/httpjson/input.go:117 +0x63

I can see that someone else has reported a similar issue on github (https://github.com/elastic/beats/issues/18530) so I'm assuming it will be fixed at some point, but has anyone found a way around this in the meantime?

Hi Sean,
The correlating PR https://github.com/elastic/beats/pull/18534 for this is tagged for next upcoming version 7.7.1. Until this version is released, there is no workaround afaik.

1 Like

Hi Andre, thanks for letting me know! I'll wait until 7.7.1 is released.

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