# Auditbeat logs many warnings

**URL:** <https://discuss.elastic.co/t/auditbeat-logs-many-warnings/339689>\
**Category:** Beats\
**Tags:** auditbeat\
**Created:** [July 31, 2023, 12:10pm UTC](https://discuss.elastic.co/t/auditbeat-logs-many-warnings/339689 "2023-07-31T12:10:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![floriankoenig-work](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/floriankoenig-work/32/124115_2.png) [@floriankoenig-work](https://discuss.elastic.co/u/floriankoenig-work)\
**Post date:** [July 31, 2023, 12:10pm UTC](https://discuss.elastic.co/t/auditbeat-logs-many-warnings/339689/1 "2023-07-31T12:10:27Z")

</div>

I've noticed auditbeat spamming (sometimes ~10/sec) the log with following messages:

```auto
Jul 30 00:04:44 HOSTNAME auditbeat[2327385]: {"log.level":"warn","@timestamp":"2023-07-30T00:04:44.668+0200","log.logger":"process","log.origin":{"file.name":"process/process.go","file.line":289},"message":"failed to get namespaces for /usr/bin/uniq PID 2155706: stat /proc/2155706/ns/mnt: no such file or directory","service.name":"auditbeat","ecs.version":"1.6.0"}
Jul 30 00:04:44 HOSTNAME auditbeat[2327385]: {"log.level":"warn","@timestamp":"2023-07-30T00:04:44.668+0200","log.logger":"process","log.origin":{"file.name":"process/process.go","file.line":289},"message":"failed to get namespaces for /usr/bin/apt-get PID 2155701: stat /proc/2155701/ns/mnt: no such file or directory","service.name":"auditbeat","ecs.version":"1.6.0"}
Jul 30 00:05:01 HOSTNAME auditbeat[2327385]: {"log.level":"warn","@timestamp":"2023-07-30T00:05:01.668+0200","log.logger":"process","log.origin":{"file.name":"process/process.go","file.line":289},"message":"failed to get namespaces for /usr/bin/smbclient PID 2156317: stat /proc/2156317/ns/mnt: no such file or directory","service.name":"auditbeat","ecs.version":"1.6.0"}

```

My first thought was that this could be a race condition. Auditbeat tries to capture information about a process that no longer exists.

With many short-running processes, however, the log is inevitably cluttered.  
(Thinking of chained calls to grep, cut, awk etc calls in scripts, which are indeed shortlived)

I have now set logging.loglevel: error for auditbeat, but think that this can only be a workaround.

How do you deal with this? Is there a way to suppress these warnings?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [August 28, 2023, 2:11pm UTC](https://discuss.elastic.co/t/auditbeat-logs-many-warnings/339689/2 "2023-08-28T14:11:18Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.