CLI Troubleshooting

Below are ways to troubleshoot some of the errors you may receive with Nimble Studio File Transfer (NSFT):

Expired Credentials Error:

FATAL  [202X-XX-XX XX:XX:XX] Failed establishing a session to AWS:InvalidAccessKeyId: The AWS Access Key Id you provided does not exist in our records. status code: 403, request id: FFYEFCKZX6F1YN8H, host id: aFtPOImvXdJQ+Ukf8SYRobDx4xmZsikoJUyJszJf3Wv74w0Q5cP9TCDz/YLKwSi53hc0hBScd58=
or
FATAL  [202X-XX-XX XX:XX:XX] Failed establishing a session to AWS:ExpiredToken: The provided token has expired. status code: 400, request id: 130NC8C984YZJMJH, host id: j7aA3Zs/O/H3QMYeoDv5Y62o7Mu/9tvi5m7jUVqTnveLZX4qrl/bKJl1j3dLVnhVda/WaUbEgO8=

• • Receiving either of these errors relate to an issue with the credentials you have provided Nimble Studio File Transfer (NSFT)

  • To resolve you can either refresh the credentials for the AWS profile it is referencing or update the access key and secret key that can be found in the configuration.yaml file

Invalid Vendor Error:

FATAL  [202X-XX-XX XX:XX:XX] Invalid vendor . Valid vendors:

• • Receiving this error means that you are using a vendor name that has not been setup yet

  • Ensure that you have not misspelled the name of the vendor, check the “Valid vendors: ” part of the error to see if any are listed

  • If no vendors are listed under “Valid vendors: ” then you will need to go to the configuration.yaml configuration file and add in the vendor, below is proper formatting:

vendors:
  vendor:
    aws_access_key: ABC123
    aws_secret_key: 123!@#
    accelerated: true
    bucket: bucket_name
    prefix: prefix
    region: us-west-2
    daemon_mode:
      enabled: true
      base_path: /media/drive

• • If you are still not seeing your vendor, make sure your yaml is properly formatted and make sure you are editing the correct yaml file (these are tied to the user signed in) . On Windows, make sure not to run CMD.exe or Powershell as Administrator otherwise it will try to read from a configuration file that is not the local user one

TCP I/O Error:

FATAL  [202X-XX-XX XX:XX:XX] Unrecoverable error: retryable: retryable: RequestError: send request failed caused by: Head "https://s3-bucket.s3.amazonaws.com/Volumes/media/drive/file.mov": dial tcp 0.0.0.0.0: i/o timeout

• • There are two reasons this error may occur:

    • Your computer disconnected from the internet and it lost connection to the S3 bucket. In this case be sure to check for a network outage or any firewall restrictions

    • The drive where the media is stored is being stored is not able to handle the load Nimble Studio File Transfer (NSFT) is placing on it causing a loss in connection to the media. This can be common among network drives. Try lowering the max_active_transfers and threads values to 1 and try the upload again to see if it works this time around. You can then slowly raise the value upon successful upload until you reach a configuration that will not overpower your drive

Absolute Path Warning:

WARN  [202X-XX-XX XX:XX:XX] Absolute paths are not supported, ignoring /media/drive

• • Receiving this warning means that you are using an absolute path which is not supported

  • An absolute path will contain the drive letter (i.e. C:\) in Windows or the leading “/” in Linux and Mac

  • To resolve this remove the leading C:\ or / if you are at the root level of your storage, or place the path relative to your current working directory