'packetbeat service stop' times out when auth failure

[LeeDr]

Please post all questions and issues on https://discuss.elastic.co/c/beats
before opening a Github Issue. Your questions will reach a wider audience there,
and if we confirm that there is a bug, then you can open a new issue.

For confirmed bugs, please report:

• Version: https://download.elastic.co/beats/packetbeat/packetbeat-5.0.0-alpha3-SNAPSHOT-amd64.deb
• Operating System: Ubuntu 15.10
• Steps to Reproduce:

NOTE: I think this is a pretty low priority issue since it's only a problem when there's a mis-configuration. I think it's more important to have the correct logging levels by default and to log an authentication error at ERROR level.

1. Misconfigure packetbeat by leaving out or having bad auth params in the yml file so it can't connect to Elasticsearch
2. Start packetbeat service
3. do some network activity (I ping google.com)
4. Stop packetbeat service
5. The stop service command may take around 1 minute 30 seconds to return
6. and you may have messages in the journal like this;

root@U14K:~/integration-test# date; time service packetbeat start
Thu May 26 12:27:02 CDT 2016

real    0m0.411s
user    0m0.022s
sys     0m0.066s
root@U14K:~/integration-test# ping google.com
PING google.com (216.58.194.78) 56(84) bytes of data.
64 bytes from dfw25s13-in-f14.1e100.net (216.58.194.78): icmp_seq=1 ttl=49 time=19.2 ms
64 bytes from dfw25s13-in-f14.1e100.net (216.58.194.78): icmp_seq=2 ttl=49 time=20.1 ms
64 bytes from dfw25s13-in-f14.1e100.net (216.58.194.78): icmp_seq=3 ttl=49 time=24.3 ms
64 bytes from dfw25s13-in-f14.1e100.net (216.58.194.78): icmp_seq=4 ttl=49 time=32.1 ms
64 bytes from dfw25s13-in-f14.1e100.net (216.58.194.78): icmp_seq=5 ttl=49 time=21.0 ms
64 bytes from dfw25s13-in-f14.1e100.net (216.58.194.78): icmp_seq=6 ttl=49 time=23.5 ms
64 bytes from dfw25s13-in-f14.1e100.net (216.58.194.78): icmp_seq=7 ttl=49 time=22.9 ms
64 bytes from dfw25s13-in-f14.1e100.net (216.58.194.78): icmp_seq=8 ttl=49 time=16.2 ms
64 bytes from dfw25s13-in-f14.1e100.net (216.58.194.78): icmp_seq=9 ttl=49 time=19.7 ms
64 bytes from dfw25s13-in-f14.1e100.net (216.58.194.78): icmp_seq=10 ttl=49 time=80.4 ms
64 bytes from dfw25s13-in-f14.1e100.net (216.58.194.78): icmp_seq=11 ttl=49 time=18.5 ms
64 bytes from dfw25s13-in-f14.1e100.net (216.58.194.78): icmp_seq=12 ttl=49 time=16.8 ms
64 bytes from dfw25s13-in-f14.1e100.net (216.58.194.78): icmp_seq=13 ttl=49 time=16.6 ms
64 bytes from dfw25s13-in-f14.1e100.net (216.58.194.78): icmp_seq=14 ttl=49 time=24.7 ms
64 bytes from dfw25s13-in-f14.1e100.net (216.58.194.78): icmp_seq=15 ttl=49 time=22.7 ms
^C
--- google.com ping statistics ---
15 packets transmitted, 15 received, 0% packet loss, time 14073ms
rtt min/avg/max/mdev = 16.283/25.282/80.480/15.265 ms
root@U14K:~/integration-test# date; time service packetbeat stop
Thu May 26 12:27:43 CDT 2016

real    1m30.476s
user    0m0.007s
sys     0m0.045s

root@U14K:~/integration-test# journalctl -u packetbeat.service | tail -n 6
May 26 12:27:43 U14K systemd[1]: Stopping packetbeat...
May 26 12:29:13 U14K systemd[1]: packetbeat.service: State 'stop-sigterm' timed out. Killing.
May 26 12:29:13 U14K systemd[1]: packetbeat.service: Main process exited, code=killed, status=9/KILL
May 26 12:29:13 U14K systemd[1]: Stopped packetbeat.
May 26 12:29:13 U14K systemd[1]: packetbeat.service: Unit entered failed state.
May 26 12:29:13 U14K systemd[1]: packetbeat.service: Failed with result 'signal'.

[tsg]

I believe this is fixed in the 5.0-alphas.