CA Configuration Automation

 View Only

 Wrong CPU Count affects Telemetry @ Linux

PauloAlexandre Pedrosa's profile image
PauloAlexandre Pedrosa posted Nov 07, 2025 01:50 PM

Hi,

Some servers are reporting more CPU cores or less than they should.


For example, I have a server that is reporting 128 CPUs Cores when in reality only have 16 available.

This is happening because when executing this code in the ‘Hardware Details (Linux)’ blueprint

numprocs=`/usr/bin/getconf _NPROCESSORS_ONLN`; x=`id|/usr/bin/cut -c5-11`; if [ ‘$numprocs’ -gt ‘1’ ]; then if [ $x != ‘0(root)’ ];then exit $? ;else numprocs=`if [ -f /usr/sbin/dmidecode ] ; then /usr/sbin/dmidecode |/bin/grep ‘Populated’ |/usr/bin/wc -l;fi`; fi; fi ;/bin/echo $numprocs

The command  ‘/usr/sbin/dmidecode |/bin/grep “Populated” |/usr/bin/wc -l’ is picking up the lines ‘Status: Populated, Enabled’ but also, incorrectly, the lines ‘Status: Populated, Disabled By BIOS’.


Another case is an azure server where I have 2 cores but cca says zero.

This happens because Azure does not expose the actual physical hardware (sockets, DIMMs, etc.). Reports: Status: Unpopulated

From the attribute's point of view, it is not a problem because we can create another blueprint with several ways to retrieve this data.

The problem is that this impacts what we see in telemetry reporting.


Any idea about fixing this?

Many Thx,

Paulo