Comments (12)
Hi, I don't have system that runs on Cisco platform. There is no acms container running in Nvidia platform. And syncd container for different vendor might have different docker build file. Could you please check:
- Does containercfgd run in syncd/acms container?
- Does containercfgd installed in those container?
from sonic-mgmt.
Hi @Junchao-Mellanox , I took one in 2700 platform.
I saw we have acms container. But there is no containercfgd running in acms.
admin@str-msn2700-01:~$ docker ps | grep acms
3b832b238f3b docker-acms:latest "/usr/local/bin/supe…" 25 hours ago Up About an hour acms
admin@str-msn2700-01:~$ docker exec -it acms bash
root@str-msn2700-01:/# ps -aux
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1 0.0 0.3 30512 26116 pts/0 Ss+ 05:31 0:02 /usr/bin/python3 /usr/local/bin/supervisord
root 7 0.0 0.3 124864 27296 pts/0 Sl 05:31 0:01 python3 /usr/bin/supervisor-proc-exit-listener --container-name acms
root 8 0.0 0.2 37296 21840 pts/0 S 05:31 0:00 python3 /usr/bin/start.py
root 9 0.0 0.3 40556 24384 pts/0 S 05:31 0:00 python3 /usr/bin/CA_cert_downloader.py
root 10 0.0 0.1 13852 9872 pts/0 S 05:31 0:00 python3 /usr/bin/cert_converter.py
root 14 0.0 0.0 222184 4032 pts/0 Sl 05:31 0:00 /usr/sbin/rsyslogd -n
root 609 0.0 0.0 4160 3288 pts/1 Ss 07:01 0:00 bash
root 616 0.0 0.0 6756 2848 pts/1 R+ 07:01 0:00 ps -aux
root@str-msn2700-01:/#
admin@str-msn2700-01:~$ docker exec -it acms bash
root@str-msn2700-01:/# ls /usr/local/bin/containercfgd
/usr/local/bin/containercfgd
from sonic-mgmt.
Comparing to eventd, I can see containercfgd runnning in it
admin@str-msn2700-01:~$ docker exec -it eventd bash
root@str-msn2700-01:/# ps -aux
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1 0.1 0.3 30520 26272 pts/0 Ss+ 06:52 0:00 /usr/bin/python3 /usr/local/bin/supervisord
root 9 0.0 0.3 124840 27548 pts/0 Sl 06:52 0:00 python3 /usr/bin/supervisor-proc-exit-listener --container-name eventd
root 12 0.0 0.0 222184 6132 pts/0 Sl 06:52 0:00 /usr/sbin/rsyslogd -n -iNONE
root 17 0.0 0.2 40924 24048 pts/0 S 06:52 0:00 python3 /usr/local/bin/containercfgd
root 19 0.1 0.2 559180 16148 pts/0 Sl 06:52 0:01 /usr/bin/eventd
root 100 0.3 0.0 4160 3344 pts/1 Ss 07:04 0:00 bash
root 106 0.0 0.0 6756 2948 pts/1 R+ 07:04 0:00 ps -aux
root@str-msn2700-01:/#
from sonic-mgmt.
Thanks. But I don't see acms container on my side. Could you please point me to the docker folder in sonic-buildimage? I don't see it in https://github.com/sonic-net/sonic-buildimage/tree/master/dockers Maybe it is a private container on your side?
from sonic-mgmt.
Hi Junchao, I found that acms container was for internal use only. That's why you cannot see it.
And syncd container for different vendor might have different docker build file. Could you please check:
Do you mean syncd was built differently in each vendor with the same source code? If so, maybe we should bypass syncd syslog rate-limit test.
from sonic-mgmt.
Thanks for the confirmation. For syncd, do you see issue on Nvidia/Mellanox platform? We don't find it in our local regression. To my understanding, each vendor should maintain the FEATURE table for their platforms. In case a FEATURE does not support syslog rate limit, they should set FEATURE.support_syslog_rate_limit to false. For example, cisco does not support syslog rate limit for syncd, they should have following in FEATURE table:
{
"FEATULRE": {
"syncd": {
"support_syslog_rate_limit": "false"
}
}
}
The test case will ignore such service.
from sonic-mgmt.
I don't see issue on Nvdia/Mellanox platform. Thanks. I will close this issue and add check for other platform.
from sonic-mgmt.
admin@str3-msn4700-01:~$ show ver
SONiC Software Version: SONiC.20230531.14
SONiC OS Version: 11
Distribution: Debian 11.8
Kernel: 5.10.0-23-2-amd64
Build commit: 25f341a9dc
Build date: Sat Jan 6 18:28:53 UTC 2024
Built by: cloudtest@107a37f6c000000
Platform: x86_64-mlnx_msn4700-r0
HwSKU: Mellanox-SN4700-O8C48
ASIC: mellanox
ASIC Count: 1
Serial Number: MT2102X08020
Model Number: MSN4700-WS2FO
Hardware Revision: A1
Uptime: 10:59:19 up 2:24, 2 users, load average: 3.31, 3.03, 2.82
Date: Tue 09 Jan 2024 10:59:19
...
admin@str3-msn4700-01:~$ show syslog rate-limit-c
SERVICE INTERVAL BURST
------------ ---------- -------
acms 300 20000
bgp 300 20000
database 300 20000
dhcp_relay 300 20000
eventd 300 20000
gnmi 300 20000
lldp 300 20000
macsec 300 20000
mux 300 20000
pmon 300 20000
radv 300 20000
restapi 300 20000
snmp 300 20000
swss 300 20000
syncd 300 20000
teamd 300 20000
telemetry 300 20000
vnet-monitor 300 20000
admin@str3-msn4700-01:~$ docker exec -i eventd bash -c 'pidof rsyslogd'
129
admin@str3-msn4700-01:~$ sudo config syslog rate-limit-container eventd -b 100 -i 10
admin@str3-msn4700-01:~$ docker exec -i eventd bash -c 'pidof rsyslogd'
129
admin@str3-msn4700-01:~$ docker exec -i restapi bash -c 'pidof rsyslogd'
243
admin@str3-msn4700-01:~$ sudo config syslog rate-limit-container restapi -b 100 -i 10
admin@str3-msn4700-01:~$ docker exec -i restapi bash -c 'pidof rsyslogd'
243
admin@str3-msn4700-01:~$
admin@str3-msn4700-01:~$ docker exec -i syncd bash -c 'pidof rsyslogd'
467
admin@str3-msn4700-01:~$ sudo config syslog rate-limit-container syncd -b 100 -i 10
admin@str3-msn4700-01:~$ docker exec -i syncd bash -c 'pidof rsyslogd'
467
admin@str3-msn4700-01:~$ show syslog rate-limit-c
SERVICE INTERVAL BURST
------------ ---------- -------
acms 300 20000
bgp 300 20000
database 300 20000
dhcp_relay 300 20000
eventd 10 100
gnmi 300 20000
lldp 300 20000
macsec 300 20000
mux 300 20000
pmon 300 20000
radv 300 20000
restapi 10 100
snmp 300 20000
swss 300 20000
syncd 10 100
teamd 300 20000
telemetry 300 20000
vnet-monitor 300 20000
Hi @Junchao-Mellanox , found one issue in mellanox and also other platform.
Config rate limiter on any container won't restart. It didn't report any error. After load minigraph, issue persists.
Do you have any idea?
from sonic-mgmt.
What is the output of config syslog rate-limit-feature --help
? If subcommand rate-limit-feature
exists, please make sure your sonic-mgmt contains this PR #10986
from sonic-mgmt.
I saw the issue being widely happen in 20230531.14 which doesn't have your sonic-mgmt PR included.
I will keep this issue open and check if the issue no longer exist in our internal test after that PR being merged to 202305.
from sonic-mgmt.
Thanks.
There was a recent change related to syslog rate limit. The feature is disabled by default in that change. So, we need explicitly enable it in sonic-mgmt before doing the test.
from sonic-mgmt.
Close it after nightly testcase pass.
from sonic-mgmt.
Related Issues (20)
- test_iface_namingmode::TestConfigInterface::test_config_interface_speed HOT 1
- bgp/test_traffic_shift_sup.py harcoded for admin user, does not work for non admin sonic_admin_user HOT 3
- Traceback in 202311 branch running snappi_tests/lacp/ HOT 2
- test_pfc_mmu_change fail because of un imported argument
- testQosSaiHeadroomPoolSize and estQosSaiHeadroomPoolWatermark failed for Force10-S6100 t1-64-lag topology
- [Yang] DPU topology is using wrong dut type HOT 4
- [Vlan][Dual-Tor] The vlan ping test is failing on dualtor topology
- [test gap][dualtor-as] dualtor linked with ycable should recover from inconsistency when cable firmware is corrupted
- Add test for PFCWD storm on both Priority 3 and 4 on macsec ports HOT 2
- [IPv6 only] support IPv6 only test case for KVM testbed. HOT 2
- observed dhclient syslog errors while running sonic-mgmt tests
- What are all the modifications needed to use different NOS in Fanout switch for T0/T1 execution [other than SONiC or EOS] HOT 1
- [Autoneg] The auto negotiation test runs only on 100G ports
- snappi_tests/multidut/pfc/test_multidut_pfc_pause_lossless_with_snappi.py fails due to the difference in number of packets expected
- snappi_tests: multidut support causes failures in single-dut runs HOT 3
- T2 disk/test_disk_exhaustion.py multi-asic support HOT 3
- Snappi API does not identify port configuration for IXIA 4x100Gbps breakout links
- get_RIB_IN_capacity is called with one less argument.
- [telemetry/test_events.py] FAILS because of a timing issue
- Some test cases failure observed on sonic-buildimage master branch HOT 9
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from sonic-mgmt.