Devesh Pathak c93716a142 rsyslog to start after interfaces-config (#13503) ... Fixes #12408 Why I did it We are running into #12408 very frequently. This results in no syslogs from any containers as rsyslog server could not start. some of the sonic-mgmt scripts look for log statements and error out if log is not present. Interfaces-config service configures the loopback interface along with other interfaces. rsyslog-config reads ip address of loopback interface and generates /etc/rsyslog.conf. When this race condition happens, lo interface ip is not yet programmed and rsyslog-config ends up writing UDP server as null in /etc/rsyslog.conf. How I did it rsyslog-config service is started after interfaces-config service. How to verify it Did multiple reboots and verified that $UDPServerAddress is valid.		2023-01-26 20:39:13 -08:00
..
rsyslog.d	Move frr logs from syslog to /var/log/frr/*.log (#5988)	2020-12-10 08:44:34 -08:00
rsyslog-config.service	rsyslog to start after interfaces-config (#13503)	2023-01-26 20:39:13 -08:00
rsyslog-config.sh	[multi-asic] fix syslog not getting generated. (#9160)	2021-11-03 18:29:09 -07:00
rsyslog-container.conf.j2	[containercfgd] Add containercfgd and syslog rate limit configuration support (#12489)	2022-12-08 08:58:35 -08:00
rsyslog.conf.j2	[infra] Support syslog rate limit configuration (#12490)	2022-12-20 10:53:58 +02:00