Instana

 View Only

 Error installing "Self Hosted Standard Edition"

  • Self-Hosted
Pablo Casal's profile image
Pablo Casal posted Tue March 25, 2025 10:29 AM
I'm trying to install Instana in "Self Hosted Standard Edition" mode (over k3s), and the installation process aborts with the error:
 
"Error: Unable to continue with install: could not get information about the resource Secret "elasticsearch-admin" in namespace "instana-elasticsearch": Get "https://127.0.0.1:6443/api/v1/namespaces/instana-elasticsearch/secrets/elasticsearch-admin": dial tcp 127.0.0.1:6443: connect: connection refused - error from a previous attempt: unexpected EOF"
Sometimes it's with the ElasticSearch component, but it can be any other component.
 
From what I can see, the k3s service always restarts when this error occurs.
 
Has this happened to anyone else? How can it be fixed?
Thanks
Bart Bogaerts's profile image
Bart Bogaerts

Hi Pablo,

Did you check the firewall rules:
https://www.ibm.com/docs/en/instana-observability/current?topic=cluster-preparing#firewall-rules ?

Pablo Casal's profile image
Pablo Casal

Hi Bart, thanks for reply.

I was checked that and the firewall is disable. 
It's strange becasuse I tryed to install online and air-gapped and the error is the same, the k3s service restart in a ramdom time and the installation cancelled.

Could you install well in standard mode?

Bart Bogaerts's profile image
Bart Bogaerts

Hi Pablo,

If you are running RHEL 9.3, then you could be impacted by:
https://www.ibm.com/docs/en/instana-observability/current?topic=edition-troubleshooting-debugging#standard-edition-installation-on-rhel-93-fails

You would need to update iptables...

Hope this helps.

Pablo Casal's profile image
Pablo Casal

I  try to run Instana in Ubuntu 24.04 that is supported. 

https://www.ibm.com/docs/en/instana-observability/current?topic=cluster-system-requirements

Bart Bogaerts's profile image
Bart Bogaerts

There are plenty of ways to troubleshoot this (kubectl logs, kubectl get events, kubectl get pods, kubectl describe pod), but i would advise that you raise a support case to have this diagnosed by support:
https://www.ibm.com/mysupport/s/?language=en_US

Pablo Casal's profile image
Pablo Casal

After many installation attempts, the maximum I've managed to install is 17 pods. All are running, but the installer doesn't progress beyond that point.
The k3s service restarts and the installation doesn't completes.
When the k3s service restarts, the pods restart, but the installation doesn't complete.
I already have a case open, but it's running slowly, like every case I open.
I thought, maybe it's a simple issue and someone on the forum could help me resolve it.
Thanks Bart, I'll continue with support. When I resolve it, I'll let you know what it was.

Mertcan Akdeniz's profile image
Mertcan Akdeniz

Network interfaces might cause problems in some on-prem environments, especially if the servers are provisioned by VMware. Please review the checksum settings of the following interfaces:

ethtool --show-offload ens192 | grep tx-checksum
ethtool --show-offload cni0 | grep tx-checksum
ethtool --show-offload flannel.1 | grep tx-checksum

If they are enabled, please disable them and go with stanctl up again. 

sudo ethtool -K ens192 tx-checksumming off
sudo ethtool -K flannel.1 tx-checksumming off
sudo ethtool -K cni0 tx-checksumming off

Note: The cni0 and flannel.1 interfaces are created each time during the k3s setup process, so make sure checksum offloading is disabled properly during or immediately after setup.

** The commands provided are based on Rhel. If you encounter errors on Ubuntu, please find the appropriate Ubuntu equivalents, as offloading feature names or syntax might differ.

Mertcan Akdeniz's profile image
Mertcan Akdeniz

https://github.com/k3s-io/k3s/issues/5013

https://knowledge.broadcom.com/external/article/331419/using-nondefault-ports-for-vxlan-traffic.html

https://github.com/projectcalico/calico/issues/3145

Pablo Casal's profile image
Pablo Casal

Thanks Mertcan for the answer. I tried it, and the parameters were off.
Even so, it still doesn't work.
I tried installing it on RHEL 9 and it worked without problems. It's probably an Instana issue with Ubuntu 24, even though the documentation says it works.
In the meantime, I'll continue with the IBM support case.

Thanks