# Topbeat: FATAL: kernel too old **URL:** \ **Category:** Beats\ **Created:** [November 27, 2015, 2:46pm UTC](https://discuss.elastic.co/t/topbeat-fatal-kernel-too-old/35769 "2015-11-27T14:46:53Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![Eric\_S](https://avatars.discourse-cdn.com/v4/letter/e/aca169/32.png) [@Eric\_S](https://discuss.elastic.co/u/Eric_S)\ **Post date:** [November 21, 2016, 5:41pm UTC](https://discuss.elastic.co/t/topbeat-fatal-kernel-too-old/35769/7 "2016-11-21T17:41:26Z")
> [@Is Filebeat, Log courier and logstash supported for CentOS RHEL 5?](https://discuss.elastic.co/t/is-filebeat-log-courier-and-logstash-supported-for-centos-rhel-5/66740/6): > > ha, it's working i think. there is no any console output on "filebeat -c /etc/filebeat/filebeat.yml -e - v -d "\*"" but i can see msg coming in on my kibana frontend now. i have filebeat running on RHEL5 box, then logstash, ES and Kibana on ubuntu 16 box waiting for filebeat. seems like it's working. by following andrew's suggestion above to run filebeat manually without using go-daemon. i'm able to run filebeat on my RHEL5 successfully. now i just need to figure out how to run filebeat in background as a service. not sure whether i should compile go-daemon or should i use some other utilities... --- _[View the full topic](https://discuss.elastic.co/t/topbeat-fatal-kernel-too-old/35769)._