#support

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.

Powered by Struct AI
Jul 13, 2023 (5 months ago)
Anil
Photo of md5-0dab8f2f962f63d6c9665dc6d172db0c
Anil
09:21 AM
Srikanth/ Prashant/ Ankit, we upgraded signoz to 21.0 and node js version to 18.9. Everything is working fine only. now i am able to see one exception ENOENT, operation name: fs realpath, stack trace is "ENOENT: no such file or directory, realpath '/usr/src/app/node_modules/diff/node_modules'". The Node JS will always flatten the dependencies of dependencies. there will be no nested node_modules .
Srikanth
Photo of md5-ce04a9988e2fd758a659dc55be6f2543
Srikanth
09:26 AM
I don’t think this is related to SigNoz. Does it happen only when the instrumentation is enabled?
Anil
Photo of md5-0dab8f2f962f63d6c9665dc6d172db0c
Anil
09:36 AM
Srikanth, when we use older version of signoz 10.2 and node version 11 . we could not see this error
09:37
Anil
09:37 AM
after upgrading signoz and node version we are facing this issue
Srikanth
Photo of md5-ce04a9988e2fd758a659dc55be6f2543
Srikanth
09:37 AM
I am saying it is a node version issue which probably has nothing to do with SigNoz
Anil
Photo of md5-0dab8f2f962f63d6c9665dc6d172db0c
Anil
09:38 AM
oh ok
09:39
Anil
09:39 AM
thanks for your valuable time