# AWX rsyslog configurer - CrashLoopBackOff

**URL:** <https://forum.ansible.com/t/awx-rsyslog-configurer-crashloopbackoff/2629>\
**Category:** Get Help\
**Tags:** awx\
**Created:** [November 29, 2023, 9:44am UTC](https://forum.ansible.com/t/awx-rsyslog-configurer-crashloopbackoff/2629 "2023-11-29T09:44:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kronk74](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/kronk74/32/1085_2.png) [@Kronk74](https://forum.ansible.com/u/Kronk74)\
**Post date:** [November 29, 2023, 9:44am UTC](https://forum.ansible.com/t/awx-rsyslog-configurer-crashloopbackoff/2629/1 "2023-11-29T09:44:59Z")

</div>

Hi,

I’m configuring a new AWX instance with an external database. Here are the versions used :

- Enviroment : OKD 4.13
- AWX Operator : 2.8.0
- AWX : 23.3.1 (for testing upgrade process)
- PostgreSQL : 15

This is not yet a production environment.

I have a problem with rsyslog pod which restart very often and put my pods in CrashLoopBackup error.

Is anyone already had this issue ?

Best regards,

Here are the logs :

```auto
[wait-for-migrations] Waiting for database migrations...
[wait-for-migrations] Attempt 1
2023-11-29 09:32:09,627 INFO RPC interface 'supervisor' initialized
2023-11-29 09:32:09,627 INFO RPC interface 'supervisor' initialized
2023-11-29 09:32:09,627 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2023-11-29 09:32:09,627 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2023-11-29 09:32:09,627 INFO supervisord started with pid 8
2023-11-29 09:32:09,627 INFO supervisord started with pid 8
2023-11-29 09:32:10,630 INFO spawned: 'superwatcher' with pid 31
2023-11-29 09:32:10,630 INFO spawned: 'superwatcher' with pid 31
2023-11-29 09:32:10,632 INFO spawned: 'awx-rsyslog-configurer' with pid 32
2023-11-29 09:32:10,632 INFO spawned: 'awx-rsyslog-configurer' with pid 32
2023-11-29 09:32:10,633 INFO spawned: 'awx-rsyslogd' with pid 33
2023-11-29 09:32:10,633 INFO spawned: 'awx-rsyslogd' with pid 33
READY
2023-11-29 09:32:11,635 INFO success: superwatcher entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-29 09:32:11,635 INFO success: superwatcher entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-29 09:32:17,054 WARN exited: awx-rsyslog-configurer (terminated by SIGKILL; not expected)
2023-11-29 09:32:17,054 WARN exited: awx-rsyslog-configurer (terminated by SIGKILL; not expected)
2023-11-29 09:32:18,057 INFO spawned: 'awx-rsyslog-configurer' with pid 38
2023-11-29 09:32:18,057 INFO spawned: 'awx-rsyslog-configurer' with pid 38
2023-11-29 09:32:23,731 WARN exited: awx-rsyslog-configurer (terminated by SIGKILL; not expected)
2023-11-29 09:32:23,731 WARN exited: awx-rsyslog-configurer (terminated by SIGKILL; not expected)
2023-11-29 09:32:25,735 INFO spawned: 'awx-rsyslog-configurer' with pid 43
2023-11-29 09:32:25,735 INFO spawned: 'awx-rsyslog-configurer' with pid 43
2023-11-29 09:32:32,442 WARN exited: awx-rsyslog-configurer (terminated by SIGKILL; not expected)
2023-11-29 09:32:32,442 WARN exited: awx-rsyslog-configurer (terminated by SIGKILL; not expected)
2023-11-29 09:32:35,447 INFO spawned: 'awx-rsyslog-configurer' with pid 48
2023-11-29 09:32:35,447 INFO spawned: 'awx-rsyslog-configurer' with pid 48
2023-11-29 09:32:40,855 INFO success: awx-rsyslogd entered RUNNING state, process has stayed up for > than 30 seconds (startsecs)
2023-11-29 09:32:40,855 INFO success: awx-rsyslogd entered RUNNING state, process has stayed up for > than 30 seconds (startsecs)
2023-11-29 09:32:41,857 WARN exited: awx-rsyslog-configurer (terminated by SIGKILL; not expected)
2023-11-29 09:32:41,857 WARN exited: awx-rsyslog-configurer (terminated by SIGKILL; not expected)
2023-11-29 09:32:42,858 INFO gave up: awx-rsyslog-configurer entered FATAL state, too many start retries too quickly
2023-11-29 09:32:42,858 INFO gave up: awx-rsyslog-configurer entered FATAL state, too many start retries too quickly
Processing Event: ver:3.0 server:supervisor serial:0 pool:superwatcher poolserial:0 eventname:PROCESS_STATE_FATAL len:79
2023-11-29 09:32:43,860 WARN received SIGQUIT indicating exit request
2023-11-29 09:32:43,860 WARN received SIGQUIT indicating exit request
2023-11-29 09:32:43,860 INFO waiting for superwatcher, awx-rsyslogd to die
2023-11-29 09:32:43,860 INFO waiting for superwatcher, awx-rsyslogd to die
2023-11-29 09:32:43,861 INFO stopped: awx-rsyslogd (exit status 0)
2023-11-29 09:32:43,861 INFO stopped: awx-rsyslogd (exit status 0)
2023-11-29 09:32:43,861 WARN stopped: superwatcher (terminated by SIGTERM)
2023-11-29 09:32:43,861 WARN stopped: superwatcher (terminated by SIGTERM)

```

---

<div class="post-metadata">

**Author:** ![TheRealHaoLiu](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/therealhaoliu/32/100_2.png) [@TheRealHaoLiu](https://forum.ansible.com/u/TheRealHaoLiu)\
**Post date:** [November 29, 2023, 7:45pm UTC](https://forum.ansible.com/t/awx-rsyslog-configurer-crashloopbackoff/2629/2 "2023-11-29T19:45:24Z")

</div>

need to figure out what’s terminating the awx-rsslog-configurer with SIGKILL

do you have kernel log for the pod that runs the container?

maybe the awx-rsyslog-configurer is being OOMKIlled?