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
As part of the acl/test_acl.py::TestAclWithReboot on a T2 or T2-min topology we reboot the individual LCs sequentially.
This results in the first rebooted LC emitting these error logs continuously:
2024 Aug 26 20:00:35.241646 cmp214-5 ERR swss0#orchagent: :- removeLag: Failed to remove ref count 1 LAG cmp214-6|asic0|PortChannel101
2024 Aug 26 20:00:35.241646 cmp214-5 ERR swss0#orchagent: :- removeLag: Failed to remove ref count 1 LAG cmp214-6|asic1|PortChannel105
2024 Aug 26 20:00:35.241673 cmp214-5 NOTICE swss0#orchagent: :- removeRouterIntfs: Router interface cmp214-6|asic0|Ethernet-IB0 is still referenced with ref count 4
2024 Aug 26 20:00:35.241673 cmp214-5 NOTICE swss0#orchagent: :- removeRouterIntfs: Router interface cmp214-6|asic0|Ethernet16 is still referenced with ref count 4
2024 Aug 26 20:00:35.241686 cmp214-5 INFO swss0#rsyslogd: imuxsock[pid: 55, name: /usr/bin/orchagent]: 2698 messages lost due to rate-limiting (20000 allowed within 300 seconds)
2024 Aug 26 20:00:35.241701 cmp214-5 NOTICE swss0#orchagent: :- removeRouterIntfs: Router interface cmp214-6|asic0|PortChannel101 is still referenced with ref count 4
2024 Aug 26 20:00:35.241701 cmp214-5 NOTICE swss0#orchagent: :- removeRouterIntfs: Router interface cmp214-6|asic1|Ethernet-IB1 is still referenced with ref count 4
2024 Aug 26 20:00:35.241731 cmp214-5 NOTICE swss0#orchagent: :- removeRouterIntfs: Router interface cmp214-6|asic1|Ethernet160 is still referenced with ref count 4
2024 Aug 26 20:00:35.241731 cmp214-5 NOTICE swss0#orchagent: :- removeRouterIntfs: Router interface cmp214-6|asic1|PortChannel105 is still referenced with ref count 4
2024 Aug 26 20:00:35.303070 cmp214-5 ERR swss1#orchagent: :- removeLag: Failed to remove ref count 1 LAG cmp214-6|asic0|PortChannel101
2024 Aug 26 20:00:35.303070 cmp214-5 ERR swss1#orchagent: :- removeLag: Failed to remove ref count 1 LAG cmp214-6|asic1|PortChannel105
2024 Aug 26 20:00:35.303104 cmp214-5 NOTICE swss1#orchagent: :- removeRouterIntfs: Router interface cmp214-6|asic0|Ethernet-IB0 is still referenced with ref count 4
2024 Aug 26 20:00:35.303104 cmp214-5 INFO swss1#rsyslogd: imuxsock[pid: 55, name: /usr/bin/orchagent]: 3646 messages lost due to rate-limiting (20000 allowed within 300 seconds)
2024 Aug 26 20:00:35.303118 cmp214-5 NOTICE swss1#orchagent: :- removeRouterIntfs: Router interface cmp214-6|asic0|Ethernet16 is still referenced with ref count 4
2024 Aug 26 20:00:35.303141 cmp214-5 NOTICE swss1#orchagent: :- removeRouterIntfs: Router interface cmp214-6|asic0|PortChannel101 is still referenced with ref count 4
2024 Aug 26 20:00:35.303193 cmp214-5 NOTICE swss1#orchagent: :- removeRouterIntfs: Router interface cmp214-6|asic1|Ethernet-IB1 is still referenced with ref count 4
2024 Aug 26 20:00:35.303228 cmp214-5 NOTICE swss1#orchagent: :- removeRouterIntfs: Router interface cmp214-6|asic1|Ethernet160 is still referenced with ref count 4
2024 Aug 26 20:00:35.303265 cmp214-5 NOTICE swss1#orchagent: :- removeRouterIntfs: Router interface cmp214-6|asic1|PortChannel105 is still referenced with ref count 4
2024 Aug 26 20:00:35.806972 cmp214-5 ERR swss0#orchagent: :- removeLag: Failed to remove ref count 1 LAG cmp214-6|asic0|PortChannel101
2024 Aug 26 20:00:35.807066 cmp214-5 ERR swss0#orchagent: :- removeLag: Failed to remove ref count 1 LAG cmp214-6|asic1|PortChannel105
I can manually reproduce this with the following steps:
The side effect of these continuous logs is syslog rate-limiting gets engaged:
2024 Aug 26 19:57:21.303029 cmp214-5 INFO swss1#rsyslogd: imuxsock[pid: 55, name: /usr/bin/orchagent] from <cmp214-5:orchagent>: begin to drop messages due to rate-limiting
2024 Aug 26 19:58:10.807179 cmp214-5 INFO swss0#rsyslogd: imuxsock[pid: 55, name: /usr/bin/orchagent] from <cmp214-5:orchagent>: begin to drop messages due to rate-limiting
2024 Aug 26 20:00:35.241686 cmp214-5 INFO swss0#rsyslogd: imuxsock[pid: 55, name: /usr/bin/orchagent]: 2698 messages lost due to rate-limiting (20000 allowed within 300 seconds)
2024 Aug 26 20:00:35.303104 cmp214-5 INFO swss1#rsyslogd: imuxsock[pid: 55, name: /usr/bin/orchagent]: 3646 messages lost due to rate-limiting (20000 allowed within 300 seconds)
Causing the ACL tests to fail as they are waiting for important syslogs to show up which get rate-limited:
E Expected Messages that are missing:
E .*Successfully created ACL rule.*
The text was updated successfully, but these errors were encountered:
As part of the
acl/test_acl.py::TestAclWithReboot
on a T2 or T2-min topology we reboot the individual LCs sequentially.This results in the first rebooted LC emitting these error logs continuously:
I can manually reproduce this with the following steps:
The side effect of these continuous logs is syslog rate-limiting gets engaged:
Causing the ACL tests to fail as they are waiting for important syslogs to show up which get rate-limited:
The text was updated successfully, but these errors were encountered: