Instana

Instana

The community for performance and observability professionals to learn, to share ideas, and to connect with others.

 View Only

  • 1.  Error installing "Self Hosted Standard Edition"

    Posted 11 days ago

    Hi.. I'm trying to install Instana Self-Hosted Standard Edtition last version on RHEL 9.4 (VM on Azure), but I got the next error:

    Get "https://127.0.0.1:6443/apis/apps/v1/namespaces/instana-elasticsearch/statefulsets/elasticsearch-es-default": dial tcp 127.0.0.1:6443: connect: connection refused - error from a previous attempt: unexpected EOF

    Any recomendation?

    Regards


    #Self-Hosted

    ------------------------------
    Carlos Americo Ojeda Medina
    ------------------------------


  • 2.  RE: Error installing "Self Hosted Standard Edition"

    Posted 10 days ago

    Hi @Carlos Americo Ojeda Medina, 

    Could you pls have check, whether you have enough storage.

    Could be multiple reason, one could be the disk I/O limit on your mount space.

    https://www.ibm.com/docs/en/instana-observability/1.0.300?topic=cluster-preparing

    https://www.ibm.com/docs/en/instana-observability/1.0.300?topic=cluster-system-requirements ...Hope this helps...Thanks!



    ------------------------------
    Neha Ghongade
    ------------------------------

    Original Message


  • 3.  RE: Error installing "Self Hosted Standard Edition"

    Posted 10 days ago

    Hello, 

    I suggest to check the network rules first. Especially, these two might be hit the problem. 

    all Inbound TCP/UDP 10.42.0.0/16 and 10.43.0.0/16 Subnets of the self-hosted Instana components
    all Inbound TCP/UDP Loopback Open the ports to allow a VM to send and receive its own data packets.

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

    Secondly, I encountered a similar connection issue between the pods while installing Std. Edt. Multinode on RHEL9 servers as well. The main problem was checksum settings on the server. When I disabled it, pods could communicate with each other. But in my case, the servers were provisioned by VMware. So I don't think this issue might happen on Cloud. But no harm in trying it.

    https://github.com/k3s-io/k3s/issues/5013
    ethtool -K flannel.1 checksum-ip-generic off
    ethtool -K cni checksum-ip-generic off
    ethtool -K ens192 checksum-ip-generic off



    ------------------------------
    Mertcan Akdeniz
    Observability Engineer
    Kloia
    Ankara
    ------------------------------

    Original Message


Related Content