Details
Description
Problem
The first message in the backup logs is a bit confusing:
2020-08-11T13:32:54.558+00:00 (Cmd) cbbackupmgr version Unknown Hostname: ip-10-0-120-216.us-west-2.compute.internal OS: linux Version: unavailable Arch: amd64 vCPU: 4 Memory: unavailable
|
Lots of "unknown" and "unavailable" in there.
Steps to reproduce
1. Create a repo using cbbackupmgr.
Attachments
Issue Links
- relates to
-
MB-44772 Backup Service test one_off_merge fails with permission denied
-
- Closed
-
Activity
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.
James Lee I'll try and get a paatch Up fist, i am going to check that ns_server gives us the path, if not I will have to pass it along.
Build couchbase-server-7.0.0-4704 contains cbbs commit 220ae80 with commit message:
MB-40878 Pass the PATH env var to CBM
Can reproduce the issue by simply deleting the uname binary, looks like cbbackupmgr logs why it failed to get the system version.
2021-03-18T10:19:57.241+00:00 ERRO: failed to get system version: failed to run 'uname -r': -- logging.(*ToolsCommonLogger).Log() at tools_common.go:30
|
2021-03-18T10:19:57.241+00:00 (Cmd) cbbackupmgr version 7.0.0-4678 Hostname: node1-cheshire-cat-testing-centos7.vagrants OS: linux Version: unavailable Arch: amd64 vCPU: 1 Memory: 2912301056 (2.71GiB)
|
Closing.
I'm going to mark this as resolved for the time being, I've updated the way that we determine the system memory/version so that it now correctly handles errors, and no longer conditionally runs commands at runtime i.e. the right commands are determined at compile time.
If we see unknown/unavailable in the logs, we'll not see an accompanying error indicating why we failed to determine the system version/memory.