Some Linux systems require sudo to run dmidecode -t system

dmidecode -t system returns: Manufacturer, Product Name, Version, Serial Number, UUID, Wake-up Type

Also verify uname and all the uname options can be run on the Linux systems

Reply if dmidecode needs sudo with your Unix team or check the communication log.

If you see this in the communication log then you will likely need sudo:

Reply to this post if you need help with changing the scripts to use sudo for dmidecode.

Hi Rey,

Thanks for the reply.

The user which I have updated in the SSH protocol is a "sudo" user(equivalent to root user) only but then also uCMDb is not retrieving the mentioned fields.

Thanks in advance.

Hi Student2912,

Could you share with me the communicaiton log of 3 job and which CP that you are using?

Best regards,

Hoang.

Hi,

I am using HP UD 10.10 CP 13.0.1179 on Windows OS.

PFA the Communication logs for Host Connection by Shell and HRA by Shell.

I see the below error in the Communication log for Host Connection by Shell.

<CMD>[CDATA&colon; dmidecode -t system | grep -A 6 "System Information" ; echo ERROR_CODE:$?]</CMD>
		<RESULT>[CDATA&colon; /dev/mem: Permission denied

I am using the sudo user in the SSH protocol.

Thanks in advance.

I mentioned that error in my post above.

To fix this, I edited the TTY_Connection_Utils.py and HostConnectionByShell.py scripts.

Its advised you create your own version of these scripts and do not alter the OOTB scripts.

So I recreated the script with a different name.

In your version of TTY_Connection_Utils.py find this section

Edit dmiDecodeCommand to the following:

In HostConnectionbyShell.py

Edit the 2 lines that contain the TTY_Connection_Utils so that it references the edited version:

and

Edit the adapter used by Host Connection by Shell to use the edited versions of the scripts

Rerun Host Connection by Shell.

The communication log previously errored at dmidecode:

<CMD>[CDATA&colon; dmidecode -t system | grep -A 6 "System Information" ; echo ERROR_CODE:$?]</CMD>
<RESULT>[CDATA&colon; /dev/mem: Permission denied
ERROR_CODE:1]</RESULT>

The script changes will return results:

CMD>[CDATA&colon; sudo /usr/sbin/dmidecode -t system | grep -A 6 "System Information" ; echo ERROR_CODE:$?]</CMD>
<RESULT>[CDATA&colon; System Information
Manufacturer: *************************************
Product Name: *******************************
Version: *************************
Serial Number: *****************************
UUID: ***********************************
Wake-up Type: *****************

ERROR_CODE:0]</RESULT>

Hi Rey,

I tried the solution suggested by you. Created new versions of these scripts and updated the section as mentioned.

Replaced these scripts in the Adapter and Rerun the "Host Connection By Shell" job.

But received an error for the Linux CI's as below.

<< Progress message, Severity: Error>>
SSH: Command timed out.

Thanks in advance.

Hi Rey,

I tried the solution suggested by you. Created new versions of these scripts and updated the section as mentioned.

Replaced these scripts in the Adapter and Rerun the "Host Connection By Shell" job.

But received an error for the Linux CI's as below.

<< Progress message, Severity: Error>>
SSH: Command timed out.

Thanks in advance.

Try increasing the shell global command timeout in globalSettings.xml

(The full size image is attached)

You may have to increase the max execution timeout to accomodate the value you changed the shell Global command timeout to

Hi Rey,

I increased the execution time parameter to 90000 at the following 3 locations.

- SSH protocol

- globalsettings.xml

- Adapter settings

Rerun the discovery job and checked the communication log and found the same error "Command time out".

Thanks in advance.

Hi Rey,

I increased the execution time parameter to 90000 at the following 3 locations.

- SSH protocol

- globalsettings.xml

- Adapter settings

Rerun the discovery job and checked the communication log and found the same error "Command time out".

Thanks in advance.