# How to kill filebeat (docker) process? **URL:** \ **Category:** Beats\ **Tags:** docker, filebeat\ **Created:** [February 8, 2021, 8:42am UTC](https://discuss.elastic.co/t/how-to-kill-filebeat-docker-process/263561 "2021-02-08T08:42:37Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![skime](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/skime/32/83555_2.png) [@skime](https://discuss.elastic.co/u/skime)\ **Post date:** [February 8, 2021, 8:42am UTC](https://discuss.elastic.co/t/how-to-kill-filebeat-docker-process/263561/1 "2021-02-08T08:42:37Z")
Hello, how can I **kill filebeat** process that was started on docker? Linux situation by "top" command: ![image](https://us1.discourse-cdn.com/elastic/original/3X/7/6/7682929a48ef319fe4d51a96d1fd0df868a37459.png) I have restarted docker daemon, and it don't want to start - probably because of the filebeat, last log from docker service is: `Feb 05 11:30:30 server.address.com dockerd[86573]: time="2021-02-05T11:30:30.700507408Z" level=info msg="Loading containers: start.` Docker commands are unresponsive, restarting docker service is getting me the same situation, kill -9 filebeat-process-id/kill filebeat-process-id is not working. Do you have any ideas **besides restarting of the server**? Last log that I have from filebeat container is: `2021-02-02T12:35:14.380Z ERROR pipeline/output.go:121 Failed to publish events: 400 Bad Request: {"error":{"root_cause":[{"type":"remote_transport_exception","reason":"[elastic-ingest-1][ip-address:9300][indices:data/write/bulk]"}],"type":"illegal_argument_exception","reason":"no write index is defined for alias [alias-name]. The write index may be explicitly disabled using is_write_index=false or the alias points to multiple indices without one being designated as a write index"},"status":400}` ---
**Author:** ![ChrsMark](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chrsmark/32/55858_2.png) [@ChrsMark](https://discuss.elastic.co/u/ChrsMark)\ **Post date:** [February 8, 2021, 10:21am UTC](https://discuss.elastic.co/t/how-to-kill-filebeat-docker-process/263561/2 "2021-02-08T10:21:54Z")
Hi! How about "killing" the container and starting it again? ie `docker kill `. C. ---
**Author:** ![skime](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/skime/32/83555_2.png) [@skime](https://discuss.elastic.co/u/skime)\ **Post date:** [February 8, 2021, 10:56am UTC](https://discuss.elastic.co/t/how-to-kill-filebeat-docker-process/263561/3 "2021-02-08T10:56:23Z")
Unfortunately - `docker kill ` is not responding, even `docker ps` is not responding. Docker service status is: ``` > Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled) > Active: activating (start) since Fri 2021-02-05 11:30:29 UTC; 2 days ago > Docs: https://docs.docker.com > Main PID: 86573 (dockerd) > Tasks: 36 > Memory: 107.5M > CGroup: /system.slice/docker.service > └─86573 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock ``` ---
**Author:** ![ChrsMark](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chrsmark/32/55858_2.png) [@ChrsMark](https://discuss.elastic.co/u/ChrsMark)\ **Post date:** [February 8, 2021, 1:17pm UTC](https://discuss.elastic.co/t/how-to-kill-filebeat-docker-process/263561/4 "2021-02-08T13:17:17Z")
Can you even `docker run` sth? If your docker daemon is not responding you can try to restart it, otherwise your system is problematic in general and a restart may be the way to go regardless of Filebeat's involvement. ---
**Author:** ![skime](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/skime/32/83555_2.png) [@skime](https://discuss.elastic.co/u/skime)\ **Post date:** [February 9, 2021, 8:26am UTC](https://discuss.elastic.co/t/how-to-kill-filebeat-docker-process/263561/5 "2021-02-09T08:26:21Z")
Docker commands were also unresponsive. It seems like **restart did the job**. Do you know why filebeat could behave in such way? ---
**Author:** ![ChrsMark](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chrsmark/32/55858_2.png) [@ChrsMark](https://discuss.elastic.co/u/ChrsMark)\ **Post date:** [February 9, 2021, 1:36pm UTC](https://discuss.elastic.co/t/how-to-kill-filebeat-docker-process/263561/6 "2021-02-09T13:36:54Z")
I don't think that Filebeat as a container could make docker daemon crash/stall 🤔 directly. Maybe sth else went wrong on the system (could be related to filebeat's container) but cannot assume what. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 9, 2021, 3:37pm UTC](https://discuss.elastic.co/t/how-to-kill-filebeat-docker-process/263561/7 "2021-03-09T15:37:14Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.