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
The logging infrastructure works buy running one host rsyslogd and rsyslogd running per each container.
rsyslogd inside containers have configuration to forward messages via UDP 127.0.0.1 to host rsyslogd that will write them.
This causes that at boot, when services start and a container service does not define a dependency on interfaces-config.service - some logging messages will be lost due to interfaces-config service reconfigures lo interface.
Steps to reproduce the issue:
Create an app ext that logs messages every second
Don't define "after" interfaces-config
Install on the switch
Do reboot/fast-reboot/config reload
Describe the results you received:
Mar 28 16:36:48.573640 r-tigon-04 NOTICE test#root: Tue Mar 28 13:36:48 UTC 2023 msg from test
Mar 28 16:36:49.577431 r-tigon-04 NOTICE test#root: Tue Mar 28 13:36:49 UTC 2023 msg from test
Mar 28 16:36:50.581154 r-tigon-04 NOTICE test#root: Tue Mar 28 13:36:50 UTC 2023 msg from test
Mar 28 16:36:50.805143 r-tigon-04 INFO systemd[1]: interfaces-config.service: Succeeded.
Mar 28 16:36:53.000521 r-tigon-04 INFO networking[778152]: warning: lo: post-up cmd 'ip addr del 127.0.0.1/8 dev lo' failed: returned 2 (RTNETLINK answers: Cannot assign requested address
Mar 28 16:36:53.485899 r-tigon-04 INFO systemd[1]: Finished Network initialization.
Mar 28 16:36:53.489068 r-tigon-04 INFO systemd[1]: Finished Update interfaces configuration.
Mar 28 16:36:53.591488 r-tigon-04 NOTICE test#root: Tue Mar 28 13:36:53 UTC 2023 msg from test
Mar 28 16:36:54.594922 r-tigon-04 NOTICE test#root: Tue Mar 28 13:36:54 UTC 2023 msg from test
Mar 28 16:36:55.598508 r-tigon-04 NOTICE test#root: Tue Mar 28 13:36:55 UTC 2023 msg from test
3 seconds with no logs
Describe the results you expected:
No log messages lost.
Setting dependency on interfaces-config is unwanted and considered as a W/A due to reasons:
Unwanted delay at boot
Container might run without network attached or not in the same host network and can't forward logs to 127.0.0.1
The logging infrastructure shall work regardless of interfaces-config.service
Description
The logging infrastructure works buy running one host rsyslogd and rsyslogd running per each container.
rsyslogd inside containers have configuration to forward messages via UDP 127.0.0.1 to host rsyslogd that will write them.
This causes that at boot, when services start and a container service does not define a dependency on interfaces-config.service - some logging messages will be lost due to interfaces-config service reconfigures lo interface.
Steps to reproduce the issue:
Describe the results you received:
3 seconds with no logs
Describe the results you expected:
No log messages lost.
Setting dependency on interfaces-config is unwanted and considered as a W/A due to reasons:
The logging infrastructure shall work regardless of interfaces-config.service
Output of
show version
: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: