Exporting data from a SAS® Visual Analytics report might fail with a "Command line call failed. signal: killed" error


Exporting data from an object in a SAS Visual Analytics report might fail with the following error: 

Command line call failed. signal: killed

This issue typically occurs when you export data to Microsoft Excel. When this issue occurs, a network trace from the browser developer tools should display a 500 response for a request to the report-renderers pod.

For example, the request looks similar to the following: POST /reportRenderer/spreadsheets?packageUri=/reportPackages/packages....

Workaround

To circumvent this issue, increase memory on the report-renderers pod to 2G by adding a patch transformer to your configuration:

  1. Create a file named patch-sas-report-renderers-memory.yaml in your deployment directory: deploy/site-config/sas-report-renderers/patch-sas-report-renderers-memory.yaml.

  2. Copy the contents below and paste them in the patch-sas-report-renderers-memory.yaml file.

    apiVersion: builtin
    kind: PatchTransformer
    metadata:
      name: patch-transformer-sas-report-renderers-mem
    patch: |-
      - op: replace
        path: /spec/template/spec/containers/0/resources/limits/memory
        value: 2Gi
    target:
      group: apps
      kind: Deployment
      name: sas-report-renderers
      version: v1 

  3. Add the following line to the transformers section of your kustomization.yaml file so that the transformer is picked up:

    - site-config/sas-report-renderers/patch-sas-report-renderers-memory.yaml

  4. Complete the deployment steps in the SAS® Viya® Platform Operations: Deploy the Software documentation to ensure that the patch transformer is applied.

  5. Check to make sure that the deployment picked up the memory limit change by using the following command:

    kubectl -n viya describe deployment sas-report-renderers