# Filebeat and GLIBC Errors on Ubuntu 22.04

**URL:** <https://discuss.elastic.co/t/filebeat-and-glibc-errors-on-ubuntu-22-04/306653>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [June 8, 2022, 8:35am UTC](https://discuss.elastic.co/t/filebeat-and-glibc-errors-on-ubuntu-22-04/306653 "2022-06-08T08:35:00Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![cmacknz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cmacknz/32/103773_2.png) [@cmacknz](https://discuss.elastic.co/u/cmacknz)\
**Post date:** [June 8, 2022, 3:57pm UTC](https://discuss.elastic.co/t/filebeat-and-glibc-errors-on-ubuntu-22-04/306653/2 "2022-06-08T15:57:07Z")

</div>

glibc \>= 2.35 added a new rseq syscall that is not in our default list of allowed syscalls. That is likely the problem you are running into.

We added rseq to our list of allowed syscalls in [common/seccomp: add rseq syscall by belimawr · Pull Request #30620 · elastic/beats · GitHub](https://github.com/elastic/beats/pull/30620). The first release with that fix would be 7.17.2: [Beats version 7.17.2 | Beats Platform Reference [7.17] | Elastic](https://www.elastic.co/guide/en/beats/libbeat/7.17/release-notes-7.17.2.html)

If you can't upgrade to 7.17.2 it is possible to customize the list of allowed syscalls through the configuration file in 7.10.x: [Use Linux Secure Computing Mode (seccomp) | Filebeat Reference [7.10] | Elastic](https://www.elastic.co/guide/en/beats/filebeat/7.10/linux-seccomp.html)

---

_[View the full topic](https://discuss.elastic.co/t/filebeat-and-glibc-errors-on-ubuntu-22-04/306653)._