Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[rsyslogd][multiasic] rsyslogd process exited with FATAL status in mutliasic platform database container #8389

Closed
mlok-nokia opened this issue Aug 9, 2021 · 1 comment

Comments

@mlok-nokia
Copy link
Contributor

Description

In multiasic platform, rsyslogd process exited with FATAL status in the global instance database container. In the database container, /etc/rsyslog.conf is empty file.

Steps to reproduce the issue:

  1. go to the the database container: docker exec -it database bash
  2. execute command : supervisorctl status

Describe the results you received:

admin@sonic:~$ docker exec -it database bash
root@sonic:/# supervisorctl status
flushdb                          EXITED    Aug 08 05:33 PM
redis                            RUNNING   pid 38, uptime 21:32:12
rsyslogd                         FATAL     Exited too quickly (process log may have details)
supervisor-proc-exit-listener    RUNNING   pid 36, uptime 21:32:12
root@sonic:/# ls -al /etc/rsyslog.conf 
-rw-r--r-- 1 root root 0 Aug  8 17:28 /etc/rsyslog.conf
root@sonic:/# 

Describe the results you expected:

admin@sonic:~$ docker exec -it database bash
root@sonic:/# supervisorctl status
flushdb                          EXITED    Aug 08 03:20 AM
redis                            RUNNING   pid 38, uptime 1 day, 11:49:24
rsyslogd                         RUNNING   pid 37, uptime 1 day, 11:49:24
supervisor-proc-exit-listener    RUNNING   pid 36, uptime 1 day, 11:49:24
root@sonic:/# ls /etc/rsyslog.conf 
/etc/rsyslog.conf
root@sonic:/# ls -al /etc/rsyslog.conf 
-rw-r--r-- 1 root root 1924 Aug  7 21:39 /etc/rsyslog.conf 

Output of show version:

SONiC buildimage from commit '3b30127',

However, looking at the latest code, the issue still exists.

Output of show techsupport:

Additional information you deem important (e.g. issue happens only occasionally):

arlakshm pushed a commit that referenced this issue Dec 1, 2021
…iner in multi-asic box (#8390)

Why I did it
Fix for issue #8389

How I did it
The /etc/rsyslog.conf is empty file which cause the FATAL of the process rsyslogd in the global instance database container. The function updateSyslogConf() should only generate the rsyslog.conf for containers in the namespace. it should not do it for the containers in the global instance. Instead, default rsyslog.conf should be used. Especially for database container, updateSyslogConf() is called before the database container is created. The result cause the sonic-cfggen failed to generate the rsyslog.conf.Why I did it
Fix for issue #8389

How I did it
The /etc/rsyslog.conf is empty file which cause the FATAL of the process rsyslogd in the global instance database container. The function updateSyslogConf() should only generate the rsyslog.conf for containers in the namespace. it should not do it for the containers in the global instance. Instead, default rsyslog.conf should be used. Especially for database container, updateSyslogConf() is called before the database container is created. The result cause the sonic-cfggen failed to generate the rsyslog.conf.

Signed-off-by: mlok <marty.lok@nokia.com>
@mlok-nokia
Copy link
Contributor Author

Issue is fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant