Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
After upgrading to 10.2(3t), the size of var/sysmgr will start growing: rtp-exa-tri02# show system internal flash | i /var/sysmgr /var/sysmgr 7782400 1343996 6438404 18 none <<<<<<<<<<<< /var/sysmgr/ftp 3145728 152 3145576 1 none /var/sysmgr/srv_logs 1536000 306608 1229392 20 none /var/sysmgr/ftp/debug_logs 10240 0 10240 0 none /var/sysmgr/startup-cfg 614400 60 614340 1 none In bash we can see that /var/sysmgr/tmp_logs is the largest directory: rtp-exa-tri02# conf t Enter configuration commands, one per line. End with CNTL/Z. rtp-exa-tri02(config)# feature bash rtp-exa-tri02# run bash bash-4.4$ du -shc /var/sysmgr/* 0 /var/sysmgr/dev_core 152K /var/sysmgr/ftp 0 /var/sysmgr/logs 96K /var/sysmgr/mtrack_info.uuid268.vdc1 88K /var/sysmgr/mtrack_info.uuid273.vdc1 112K /var/sysmgr/mtrack_info.uuid545.vdc1 0 /var/sysmgr/non-sysmgr 0 /var/sysmgr/remote 0 /var/sysmgr/rev-gsync 300M /var/sysmgr/srv_logs 60K /var/sysmgr/startup-cfg 0 /var/sysmgr/sysmgr-subproc 0 /var/sysmgr/tmp 1.3G /var/sysmgr/tmp_logs <<<<<<<<<<<< 0 /var/sysmgr/vsh 0 /var/sysmgr/work 0 /var/sysmgr/xml 1.6G total Within /var/sysmgr/tmp_logs we see that file "libcpa_sb_log.pfmclnt.3903" is very large. bash-4.4$ cd /var/sysmgr/tmp_logs bash-4.4$ ls -lh total 1.3G -rw-rw-rw- 1 root root 0 Oct 18 20:30 diag_port_lb.25113 -rw-rw-rw- 1 root root 0 Oct 18 20:34 hal.log -rw-rw-rw- 1 root root 110M Oct 21 09:28 libcpa_sb_log.dc3_sensor.27410 -rw-rw-rw- 1 root root 23K Oct 21 08:05 libcpa_sb_log.pfm.21928 -rw-rw-rw- 1 root root 1.2G Oct 21 09:29 libcpa_sb_log.pfmclnt.3903 <<<<<<<<<<<< -rw-rw-rw- 1 root root 0 Oct 18 20:34 liblinx_log.unkown.27407 -rw-rw-rw- 1 root root 4.8K Oct 19 21:38 lldp_niv_28761 -rw-rw-rw- 1 root root 9.9K Oct 21 09:00 ssd_script.log -rw-rw-rw- 1 root root 0 Oct 18 20:30 stripcl_20221018_203043_25138_init.log -rw-rw-rw- 1 root root 31K Oct 19 21:38 tun_enc_lc.out_27497
Running 10.2(3t) on 3550-T.
A Software Maintenance Upgrades (SMU) is now available for this issue. * nxos64-msll.CSCwd28430-1.0.0-10.2.3t.lib32_64_n9000.rpm The SMU requires a reload. It is recommended to use the provided SMU as a long term solution. The workaround shown here can be used temporarily. Workaround: Delete the "libcpa_sb_log.pfmclnt.*" file. This will stop the process from logging debug messages until the process is started or the switch is reloaded. bash-4.4$ cd /var/sysmgr/tmp_logs bash-4.4$ pwd /var/sysmgr/tmp_logs bash-4.4$ rm libcpa_sb_log.pfmclnt.3903 bash-4.4$ ls -lh total 110M -rw-rw-rw- 1 root root 0 Oct 18 20:30 diag_port_lb.25113 -rw-rw-rw- 1 root root 0 Oct 18 20:34 hal.log -rw-rw-rw- 1 root root 110M Oct 21 09:29 libcpa_sb_log.dc3_sensor.27410 -rw-rw-rw- 1 root root 23K Oct 21 08:05 libcpa_sb_log.pfm.21928 -rw-rw-rw- 1 root root 0 Oct 18 20:34 liblinx_log.unkown.27407 -rw-rw-rw- 1 root root 4.8K Oct 19 21:38 lldp_niv_28761 -rw-rw-rw- 1 root root 9.9K Oct 21 09:00 ssd_script.log -rw-rw-rw- 1 root root 0 Oct 18 20:30 stripcl_20221018_203043_25138_init.log -rw-rw-rw- 1 root root 31K Oct 19 21:38 tun_enc_lc.out_27497
The numerical sequence at the end of the filename corresponds to the process ID and may vary. Reloading the switch or starting the pfmclnt process with start the logging again. You can use the following method to determine the current PID of pfmclnt. bash-4.4$ ps aux | grep pfmclnt admin 3108 0.0 0.0 5384 1768 pts/2 S+ 09:46 0:00 grep pfmclnt root 3903 3.0 0.4 427288 68848 ? Ds Oct18 110:11 /lc/isan/bin/pfmclnt <<<<<<<<<<<<