You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
go to the the database container: docker exec -it database bash
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
…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>
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:
Describe the results you received:
Describe the results you expected:
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):
The text was updated successfully, but these errors were encountered: