Hit this issue once. On bootup after the container initialization, there should be syslogs from lldp container which will show the process spawned. However in one specific bootup after fresh installation, there were no syslogs. Config reload or reboot didn't help to recover.
Attached is the syslog file during reboot.
Steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Logs after lldp container start
May 16 21:19:24.872953 r-liger-02 NOTICE admin: Starting lldp service...
May 16 21:19:25.036370 r-liger-02 INFO lldp.sh[10303]: Starting existing lldp container with HWSKU ACS-MSN4600
May 16 21:19:26.372888 r-liger-02 DEBUG container: read_data: config:True feature:lldp fields:[('set_owner', 'local'), ('no_fallback_to_local', False), ('state', 'disabled')] val:['local', False, 'enabled']
May 16 21:19:26.374290 r-liger-02 DEBUG container: read_data: config:False feature:lldp fields:[('current_owner', 'none'), ('remote_state', 'none'), ('container_id', '')] val:['none', 'none', '']
May 16 21:19:26.374400 r-liger-02 DEBUG container: container_wait: lldp: set_owner:local ct_owner:none state:none id:lldp pend=0
May 16 21:19:26.374603 r-liger-02 DEBUG container: container_wait: END -- transitioning to docker wait
..
May 16 21:19:31.440319 r-liger-02 INFO hostcfgd: Updating feature 'lldp' systemd config file related to auto-restart ...
May 16 21:19:31.440537 r-liger-02 INFO hostcfgd: Feautre 'lldp' systemd config file related to auto-restart is update
May 16 21:19:31.440620 r-liger-02 INFO hostcfgd: Reloading systemd configuration files ...
May 16 21:19:31.455164 r-liger-02 INFO systemd[1]: Reloading.
Describe the results you expected:
May 19 07:20:58.819160 r-liger-02 INFO container: docker cmd: start for lldp
May 19 07:20:58.902668 r-liger-02 NOTICE root: Starting lldp service...
May 19 07:20:59.030264 r-liger-02 NOTICE admin: Started lldp service...
May 19 07:20:59.322646 r-liger-02 NOTICE root: Started lldp service
May 19 07:20:59.716696 r-liger-02 DEBUG container: read_data: config:True feature:lldp fields:[('set_owner', 'local'), ('no_fallback_to_local', False), ('state', 'disabled')] val:['local', False, 'enabled']
May 19 07:20:59.717401 r-liger-02 DEBUG container: read_data: config:False feature:lldp fields:[('current_owner', 'none'), ('remote_state', 'none'), ('container_id', '')] val:['none', 'none', '']
May 19 07:20:59.718488 r-liger-02 DEBUG container: container_wait: lldp: set_owner:local ct_owner:none state:none id:lldp pend=0
May 19 07:21:02.546022 r-liger-02 INFO lldp#rsyslogd: [origin software="rsyslogd" swVersion="8.2302.0" x-pid="13" x-info="https://www.rsyslog.com"] start
May 19 07:21:02.547742 r-liger-02 INFO lldp#supervisord 2023-05-19 04:20:59,914 INFO Included extra file "/etc/supervisor/conf.d/containercfgd.conf" during parsing
May 19 07:21:02.547742 r-liger-02 INFO lldp#supervisord 2023-05-19 04:20:59,914 INFO Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing
May 19 07:21:02.547742 r-liger-02 INFO lldp#supervisord 2023-05-19 04:20:59,914 INFO Set uid to user 0 succeeded
Description
Hit this issue once. On bootup after the container initialization, there should be syslogs from lldp container which will show the process spawned. However in one specific bootup after fresh installation, there were no syslogs. Config reload or reboot didn't help to recover.
Attached is the syslog file during reboot.
Steps to reproduce the issue:
1. 2. 3.
Describe the results you received:
Logs after lldp container start
Describe the results you expected:
Output of
show version
:Output of
show techsupport
:Additional information you deem important (e.g. issue happens only occasionally):
syslog.203.gz