<@U0401NB5RM1> can you share what you see on runni...
# supportp
Pranay
08/28/2022, 12:36 PM
@주현태 can you share what you see on running this. https://signoz.io/docs/install/troubleshooting/
u
주현태
08/28/2022, 12:41 PM@Pranay
This is the result of running with endpoint set to 172.17.0.1 and localhost.
Docker containers are running.
p
Pranay
08/28/2022, 6:37 PM
got it. So your SigNoz otel collector is not accessible from your application.
I think you need to check the address you have given - this grid may be helpful - https://signoz.io/docs/install/troubleshooting/#signoz-otel-collector-address-grid
p
Prashant Shahi
08/28/2022, 9:52 PMHey @주현태 👋
We don't officially support Windows yet. There is an open issue on the same.
Do check out this comment on the opened issue, if it helps. https://github.com/SigNoz/signoz/issues/645#issuecomment-1027629006
Prashant Shahi
08/28/2022, 10:03 PMThis is the result of running with endpoint set to 172.17.0.1 and localhost.The OtelCollector address grid does not include instruction for windows. Below command should do the equivalent to check if OtelCollector is accessible and accepting traces:
Copy code
docker run -it --network clickhouse-setup_default signoz/troubleshoot checkEndpoint --endpoint=otel-collector:4317u
주현태
08/29/2022, 6:22 AM@Pranay @Prashant Shahi
Thanks for your help.
I solved the issue as shown in the attached image.
It was a permission problem of the clickhouse's store data.
So, I used the docker internal volume.
Refer to the URL below.
https://medium.com/@tina168wong/problem-of-mysql-volumes-in-docker-in-ubuntu-wsl2-5aed9ce10013
Thank you.🙏
p
Pranay
08/29/2022, 6:24 AM
Awesome, thanks a lot for sharing back @주현태
2 Views