matthew/sonic-buildimage
Archived
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

rsyslog to start after interfaces-config (#13503)

Browse Source 
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.
This commit is contained in:
Devesh Pathak 2023-01-26 20:39:13 -08:00 committed by GitHub
parent dabb31c5f6
commit c93716a142
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
files/image_config/rsyslog/rsyslog-config.service
View File

@ -4,6 +4,7 @@ Requires=updategraph.service
After=updategraph.service After=updategraph.service
BindsTo=sonic.target BindsTo=sonic.target
After=sonic.target After=sonic.target
After=interfaces-config.service
[Service] [Service]
Type=oneshot Type=oneshot