Replies: 1 comment 1 reply
-
|
@mrproliu Would you able to find any clue from the logs? It is not clear to me. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Search before asking
Apache SkyWalking Component
Satellite (apache/skywalking-satellite)
What happened
Hi,
I made all the configurations as instructed in git hub, but when I access the UI, I have no data, searching in the logs I found many logs about connection refused as you can see in the file attached:
satellite2.log
Bellow I put the command that I used to install the components using Helm:
Can you help me to solve this problem?
What you expected to happen
I expect that satellite pod could send the information to the OAP servers.
How to reproduce
Creating the components with the instructions below:
export SKYWALKING_RELEASE_VERSION=4.5.0 # change the release version according to your need
export SKYWALKING_RELEASE_NAME=skywalking # change the release name according to your scenario
export SKYWALKING_RELEASE_NAMESPACE=skywalking # change the namespace to where you want to install SkyWalking
helm install "${SKYWALKING_RELEASE_NAME}"
oci://registry-1.docker.io/apache/skywalking-helm
--version "${SKYWALKING_RELEASE_VERSION}"
-n "${SKYWALKING_RELEASE_NAMESPACE}"
--set oap.image.tag=9.5.0
--set elasticsearch.replicas=1
--set elasticsearch.minimumMasterNodes=1
--set elasticsearch.volumeClaimTemplate.resources.requests.storage=10Gi
--set oap.storageType=elasticsearch
--set ui.image.tag=9.5.0
--set satellite.enabled=true
--set satellite.image.tag=v1.2.0
Anything else
No response
Are you willing to submit PR?
Code of Conduct
Beta Was this translation helpful? Give feedback.
All reactions