Issue with ENOENT Exception After Upgrade
TLDR Anil faced ENOENT exception after upgrading SigNoz and Node.js. Srikanth clarified it's likely a Node.js version issue unrelated to SigNoz.
Jul 13, 2023 (5 months ago)
Anil
09:21 AMSrikanth
09:26 AMAnil
09:36 AMAnil
09:37 AMSrikanth
09:37 AMAnil
09:38 AMAnil
09:39 AMSigNoz Community
Indexed 1023 threads (61% resolved)
Similar Threads
Issues with SigNoz on DigitalOcean k8s After Upgrade
Thomas experienced issues with SigNoz on DigitalOcean k8s after upgrading to v0.19. Prashant identified a PR to address the issue and provided a solution.
Error Installing SigNoz on NodeJS App on Graviton Server
abhinav faced errors installing SigNoz on a NodeJS app. vishal-signoz suggested following a workaround on an opentelemetry issue, which resolved the problem.
Issues with Signoz 10.2: Grouping, Missing Traces, and Capturing Requests
Anil reported issues with Signoz 10.2, including grouping, missing traces, and capturing requests. Srikanth suggested upgrading to a newer version. The issue was resolved after upgrading the node version to 18 and additional clarifications were provided.