Packetbeat.service stop-sigterm timed out. Killing

Hi,

I'm using packetbeat v6.2.2 and at times I see packetbeat service not getting stopped when the stop command is run.

Nov 15 15:18:49 systemd[1]: Stopping packetbeat...
Nov 15 15:20:19 systemd[1]: packetbeat.service stop-sigterm timed out. Killing.
Nov 15 15:20:19 systemd[1]: packetbeat.service: main process exited, code=killed, status=9/KILL
Nov 15 15:20:19 systemd[1]: Stopped packetbeat.
Nov 15 15:20:19 systemd[1]: Unit packetbeat.service entered failed state.
Nov 15 15:20:19 systemd[1]: packetbeat.service failed.

The service gets killed after 90 secs.

Does anyone know why this is happening and how I can avoid this?

Not sure if these failed to connect errors has any effect on the stopping of the service.

packetbeat.logs
|2018-11-15T15:17:57.058-0700|ERROR|pipeline/output.go:74|Failed to connect: dial tcp 10.x.x.x:5044: getsockopt: connection refused|
|2018-11-15T15:18:20.273-0700|ERROR|pipeline/output.go:74|Failed to connect: dial tcp 10.x.x.x:5044: getsockopt: connection refused|
|2018-11-15T15:18:57.059-0700|ERROR|pipeline/output.go:74|Failed to connect: dial tcp 10.x.x.x:5044: getsockopt: connection refused|
|2018-11-15T15:19:20.274-0700|ERROR|pipeline/output.go:74|Failed to connect: dial tcp 10.x.x.x:5044: getsockopt: connection refused|
|2018-11-15T15:19:57.060-0700|ERROR|pipeline/output.go:74|Failed to connect: dial tcp 10.x.x.x:5044: getsockopt: connection refused|