Resolving Elasticube(s) not starting the build process issue

[CKennington]

Resolving Elasticube(s) not starting to build process issue

Summary

This article addresses the issue where Elasticubes are not properly starting the build process and fail to produce a build error (before the initialization process can begin). 

Step-by-Step Instructions to Resolve the Issue

1. Identify the Problematic Elasticube:

• Open the Sisense application and open the data model from the Data tab.

• Attempt to manually trigger a build for a specific Elasticube to confirm build process does not show starting.

• If the build does not start, note the specific Elasticube name.

1. Check for the existence of the build pod via the command line:

• Open the command line from SSH access to your Sisense server.

• Run this command to see a list of current cube build pods: kubectl -n sisense get pods | grep bld

• If a build pod exists, it will look like ec-cubename-bld.

• If this pod DOES exist:

• - verify this pod is up and in running status

• - verify build and management pods are up and running

• - recycle build and management pods together: kubectl -n sisense rollout restart deployment build management

• If ec-bld pod does NOT exist for your cube, there is likely a pod issue with the build or management service. 

• - if your deployment is a single node, verify only one pod of each build and management exists (and is in up-and-running status)

• - likely, you have an older (build or management) pod that is stuck in a terminating or similar status

• - run force delete command for older (build or management) pod which does not kill itself: kubectl -n sisense delete pod <name of build or management pod> --grace-period 0 --force

2. Monitor Logs:

• Review the logs for both the build and management pods to identify any errors that could provide more info on why the management service is unable to create ec-bld pod for your cube; kubectl -n sisense logs <name of management pod> | grep ERROR,  kubectl -n sisense logs <name of build pod> | grep ERROR

• Look for patterns or recurring issues that might indicate a deeper problem.

Supplementary Information

• Contact Support:
  • If the issue persists after following the above steps, contact Sisense Support for further assistance.
  • Provide detailed information about Elasticube and logs from the previous section

Check out this related content: 
Academy
Documentation