Instana

 View Only

 Implementation issue

  • Administration
sudharsanam v's profile image
sudharsanam v posted Fri December 20, 2024 06:36 AM

HI team

I'm setting a instana lab self hosted standard edition.

with skiping the preflight check of data storage. I'm getting a error like below and makes the cluster stopped.

Bart Bogaerts's profile image
Bart Bogaerts

Why did you decide to skip the preflight check? If the server has resource issues then it can throw the 'context deadline exceeded' error...

sudharsanam v's profile image
sudharsanam v

We already have 150 GB level of disk space for every partition since we planning to give small load to monitor thats why skiping the preflight check.

Its just a testing environment

Bart Bogaerts's profile image
Bart Bogaerts

It would point more to a shortage of cpu or memory. Please make sure that you meet the requirements (https://www.ibm.com/docs/en/instana-observability/current?topic=cluster-system-requirements), also on the supported OS.

If this is RHEL 9.3, check here: https://www.ibm.com/docs/en/instana-observability/current?topic=edition-troubleshooting-debugging#standard-edition-installation-on-rhel-93-fails

More info might be in $HOME/.stanctl/logs/console.log, Also 'kubectl get events -A' might give some clues.

sudharsanam v's profile image
sudharsanam v

I see after lot of retry on the same part its getting started at last getting another kind of errors

 will share the error and log

sudharsanam v's profile image
sudharsanam v

Im using RHEL 8.10

The LOG where it is stopping

ts=2024-12-26T07:58:27Z level=INFO msg="using values files" app=cert-manager files=[/root/.stanctl/values/cert-manager/instana-values.yaml]
ts=2024-12-26T07:58:28Z level=INFO msg="upgrading Helm chart" name=cert-manager release=cert-manager version=v1.16.2

sudharsanam v's profile image
sudharsanam v

and 

sudharsanam v's profile image
sudharsanam v

After running the command  ------ >       kubect get events -A

Bart Bogaerts's profile image
Bart Bogaerts

There appear to be multiple issues here. I suggest you raise a support case so IBM support (https://www.ibm.com/mysupport/s/createrecord/NewCase) can take a deeper look into this.