Hi Carlos Gonzalez Betancort,
I've reopened this an assigned it to you as this appears to be an issue with cbbs; more specifically cbbs does not appear to be passing the existing environment down to cbm (this may be desired, however, we should be at least passing select variables e.g. PATH).
I've reproduced this issue using a test server from QE and we can clearly see this issue now that we're no longer ignoring the error message.
uname not in $PATH
2021-03-15T13:30:13.611-07:00 ERRO: failed to get system version: failed to run 'uname -r': exec: "uname": executable file not found in $PATH -- logging.(*ToolsCommonLogger).Log() at tools_common.go:30
Please note that uname does exist on this machine, and running without using cbbs results in the version being detected correctly.
Looking at the second example for exec.Command is appears that we should be passing down os.Environ() to cbbackupmgr. I understand that this might not be possible/viable due to cbauth environment variables, however, we should at least be passing the PATH environment variable.
Please could you look at getting a patch up for this.