1.0.7 ./sentry_cpu_profiler-darwin-arm64-115.node not found #171

andylacko · 2023-06-30T17:42:19Z

Is there an existing issue for this?

I have checked for existing issues https://github.com/getsentry/profiling-node/issues
I have reviewed the documentation https://docs.sentry.io/
I am using the latest SDK release https://github.com/getsentry/profiling-node/releases

How do you use Sentry?

Sentry Saas (sentry.io)

SDK Version

1.0.7

Link to Sentry event

No response

What environment is your node script running in?

20.3.1
pnpm

How is your code deployed and bundled?

webpack

Steps to Reproduce

try to run project

Expected Result

work

Actual Result

Error: Cannot find module './sentry_cpu_profiler-darwin-arm64-115.node'
Require stack:

/Users/andy/Developer/intellcre/node_modules/.pnpm/@sentry [email protected]/node_modules/@sentry/profiling-node/lib/index.js
/Users/andy/Developer/intellcre/services/api/dist/services/api/src/main.js
at Function.Module._resolveFilename (node:internal/modules/cjs/loader:1072:15)
at Function.Module._load (node:internal/modules/cjs/loader:925:27)
at Module.require (node:internal/modules/cjs/loader:1139:19)
at require (node:internal/modules/helpers:121:18)
at /Users/andy/Developer/intellcre/node_modules/.pnpm/@sentry [email protected]/node_modules/@sentry/profiling-node/lib/index.js:16691:57
at importCppBindingsModule (/Users/andy/Developer/intellcre/node_modules/.pnpm/@sentry [email protected]/node_modules/@sentry/profiling-node/lib/index.js:16691:14)
at /Users/andy/Developer/intellcre/node_modules/.pnpm/@sentry [email protected]/node_modules/@sentry/profiling-node/lib/index.js:16717:32
^C/Users/andy/Developer/intellcre/services/api:
ERR_PNPM_RECURSIVE_RUN_FIRST_FAIL [email protected] start:dev: pnpm run assets:copy && nest start --watch
Command failed with signal "SIGTERM"
ELIFECYCLE Command failed.

The text was updated successfully, but these errors were encountered:

stephenhmarsh · 2023-07-04T20:38:13Z

Yeah I get almost the same error in my Next.js project running @sentry/profiling-node 1.0.7 (latest published)

Error: Cannot find module './sentry_cpu_profiler-darwin-arm64-108.node'
Require stack:
- /Users/stephen/dev/met-js/web/node_modules/@sentry/profiling-node/lib/index.js
- /Users/stephen/dev/met-js/web/.next/server/pages/_document.js
- /Users/stephen/dev/met-js/web/node_modules/next/dist/server/require.js
- /Users/stephen/dev/met-js/web/node_modules/next/dist/server/load-components.js
- /Users/stephen/dev/met-js/web/node_modules/next/dist/build/utils.js
- /Users/stephen/dev/met-js/web/node_modules/next/dist/server/dev/static-paths-worker.js
- /Users/stephen/dev/met-js/web/node_modules/next/dist/compiled/jest-worker/processChild.js
    at Module._resolveFilename (node:internal/modules/cjs/loader:1047:15)
    at /Users/stephen/dev/met-js/web/node_modules/next/dist/server/require-hook.js:189:36
    at Module._load (node:internal/modules/cjs/loader:893:27)
    at Module.require (node:internal/modules/cjs/loader:1113:19)
    at require (node:internal/modules/cjs/helpers:103:18)
    at /Users/stephen/dev/met-js/web/node_modules/@sentry/profiling-node/lib/index.js:16691:57
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async importCppBindingsModule (/Users/stephen/dev/met-js/web/node_modules/@sentry/profiling-node/lib/index.js:16691:14)
    at async /Users/stephen/dev/met-js/web/node_modules/@sentry/profiling-node/lib/index.js:16717:32

It looks like #173 would fix this. Running those commands separately and manually from the terminal resolved this.

JonasBa · 2023-07-06T12:56:38Z

We've released 1.0.8 and some folks internally at Sentry who had issues have said that they now seem to be resolved. Do you mind upgrading and letting me know if this still happens?

Klaitos · 2023-07-10T13:51:20Z

Error still persists Cannot find module './sentry_cpu_profiler-darwin-arm64-115.node with node v18.16.0 and @sentry/profiling-node 1.0.8

Klaitos · 2023-07-10T14:01:11Z

For those having the issue, I've found in the code the following workaround :
Set a env var before running your code :
SENTRY_PROFILER_BINARY_PATH=./sentry_cpu_profiler-darwin-arm64-108.node

whaagmans · 2023-07-10T14:07:39Z

SENTRY_PROFILER_BINARY_PATH=./sentry_cpu_profiler-darwin-arm64-108.node

I don't have this token set. Where is yours located? It could be due to the token being set it overrides the default space it looks for the file.

Klaitos · 2023-07-10T14:12:44Z

The issue is here https://github.com/getsentry/profiling-node/blob/main/src/cpu_profiler.ts#L2, the versions variable returned by the import is 20.4, while my code is running on node 18.16.

whaagmans · 2023-07-10T14:31:40Z

The issue is here https://github.com/getsentry/profiling-node/blob/main/src/cpu_profiler.ts#L2, the versions variable returned by the import is 20.04, while my code is running on node 18.04. I guess this var is read at the build time, when you build and upload the package it is saved inside.

Maybe I am missing something but based on the Node docs the process.versions has been in there since 0.2 with the last update in 9.0. https://nodejs.org/docs/latest-v18.x/api/process.html#processversions So maybe the problem is in another part. But still weird that adding the ENV solves it.

You don't have a --ignore-scripts anywhere in you npm specified. You can check by with npm config get ignore-scripts

Klaitos · 2023-07-10T14:54:39Z

No I don't npm ignore scripts

Klaitos · 2023-07-10T15:06:36Z

Oh I found this is related to yarn, because when I start my server with npm (and nodemon) this works !

whaagmans · 2023-07-10T15:20:46Z

Interesting since I use yarn 😅. But then again I am also on the latest node version so maybe there lies the crux. But happy that it works at least.

Klaitos · 2023-07-10T16:47:51Z

For my case, it appears that the issue was a conflict on where and how was installed node and yarn on my laptop.

I had a yarn version installed with brew and a node version with brew also but not used, my default node binary was the one installed with nvm. (type which node)

When I used yarn dlx to use nodemon and ts-node to start my server which is using your library, the node 20.4 version (the brew one) was used by yarn for any reason.

To fix this, I executed brew remove yarn and corepack enable, yarn dlx is now using my default node binary.

Hope that helps someone, not sure if it the same reason than @andylacko.

JonasBa · 2023-07-17T19:17:28Z

Anyone on the latest version of the package still experiencing this problem?

nicksrandall · 2023-07-17T20:02:48Z

Anyone on the latest version of the package still experiencing this problem?

Yes, I'm still seeing this issue with PNPM.

whaagmans · 2023-07-17T20:23:13Z

Anyone on the latest version of the package still experiencing this problem?

Yes, I'm still seeing this issue with PNPM.

Probably you've already tried this but as a novelty, have you've already tried:

Remove the node_modules directory and the lock file (pnpm-lock.yaml).
pnpm store prune
Run pnpm install again.
Check whether the package in question is at the correct version by using pnpm list [package-name].

JonasBa · 2023-07-19T21:09:12Z

@nicksrandall can you please run a clean install as @whaagmans suggested? I just attempted to install the package via pnpm, build and run and I could not reproduce your error.

yash-coded · 2023-07-28T13:30:01Z

This is still unusable in M1 macs. Did anyone find a workaround for this?

JonasBa · 2023-07-28T13:36:21Z

@yash-coded are you using pnpm as well?

yash-coded · 2023-07-28T13:45:08Z

Hey @JonasBa, I'm using node v18.16.1 (npm v9.5.1)

JonasBa · 2023-07-28T13:50:25Z

@yash-coded are you by any chance ignoring install scripts? What does npm config get ignore-scripts output? Can you bump the package to version 1.1.2?

nicksrandall · 2023-07-28T13:52:13Z

@JonasBa I did a clean install and realized that I think the issue is with my bundler and maybe not pnpm? I'm using remix (which is using esbuild) and the server fails to start when I'm using this package because node can't find the .node file

yash-coded · 2023-07-28T13:52:46Z

ignore-scripts is set to false and we're already on 1.1.2

yash-coded · 2023-07-28T13:56:21Z

Getting this error when I run my server but i didn't get any errors during installation.

JonasBa · 2023-07-28T14:10:10Z

@yash-coded, you are running the script with node 16 - it looks for binary compatible with 93 identifier which corresponds to node 16 and not node 18 as you mentioned.

Can you make sure to run the script with node 18?

yash-coded · 2023-07-28T14:26:10Z

Sorry about that, i switched to node 16 just to try another version when I took the screenshot but I was getting the same error with node 18: node_modules/@sentry/profiling-node/lib/sentry_cpu_profiler-darwin-arm64-108.node, 0x0001)

JonasBa · 2023-07-28T14:33:36Z

@yash-coded I dont think your install script ran for some reason (or your node version was different at install time). Can you cd into node_modules/@sentry/profiling-node and manually run node scripts/check-build.mjs and tell me what it outputs? This should detect the runtime error and trigger a rebuild from source.

yash-coded · 2023-07-28T14:56:59Z

This was with node 16 but I got the same result with node v18

@sentry/profiling-node: Precompiled binary found, attempting to load /path/to/repo/node_modules/@sentry/profiling-node/lib/sentry_cpu_profiler-darwin-arm64-93.node
@sentry/profiling-node: Precompiled binary found but failed loading
@sentry/profiling-node: Compiling from source...

JonasBa · 2023-07-28T15:02:00Z

Hmm, I think compiling from source might fail here and we may be swallowing error. If a binary is successfully compiled from source on your local machine then it should work (or at least the error would have been different)

do you mind running npm run build:configure,npm run build:bindings and node scripts/copy-target.mjs in this order from the profiling dir and seeing if any of these fail?

yash-coded · 2023-07-28T15:59:11Z

npm run build:configure didn't fail but got following responses from other two commands

❯ npm run build:bindings

> @sentry/[email protected] build:bindings
> node-gyp build && node scripts/copy-target.mjs

gyp info it worked if it ends with ok
gyp info using [email protected]
gyp info using [email protected] | darwin | arm64
gyp info spawn make
gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
make ✖ ERR  Missing Makefile / Bakefile 
make ℹ info Run "make init" to generate a Makefile.
gyp info ok 
Source file does not exist: /path/to/repo/node_modules/@sentry/profiling-node/build/Release/sentry_cpu_profiler.node

❯ node scripts/copy-target.mjs
Source file does not exist: /path/to/repo/node_modules/@sentry/profiling-node/build/Release/sentry_cpu_profiler.node

JonasBa · 2023-07-28T16:09:40Z

Quick search for that error finds nodejs/node-report#102 (comment)

Do you have a make package installed that is being confused by make from the build toolchain?

mrmckeb · 2023-08-04T05:20:32Z

I'm hitting this issue too.

Error: Cannot find module '[project-path]/node_modules/.pnpm/@[email protected]/node_modules/@sentry/profiling-node/lib/sentry_cpu_profiler-darwin-arm64-110.node'

I see the following sentry_cpu_profiler-darwin-arm64-* modules installed.

JonasBa · 2023-08-04T12:16:01Z

@mrmckeb mind running the steps that I described manually in and tell me if you see errors? #171 (comment)

JonasBa · 2023-08-28T15:00:49Z

Closing due to inactivity. @mrmckeb please make sure you don't have a "make" package installed that is confusing the build toolchain. Feel free to reopen the issue if you still have a problem - I would just ask you to re-run the commands I described in #171 and paste the output so we can efficiently debug

miteshkotak · 2023-08-29T15:57:51Z

I faced the similar issue issue with M1 Macs , Node 20.5.1, npm : 8.5.5

running npm i @sentry/profiling-node ( latest package removed the error for me)

nicksrandall · 2023-08-29T16:21:15Z

This is also not working for me. Basic Remix app.

JonasBa · 2023-08-29T16:32:40Z

@nicksrandall mind opening a new issue with an example stacktrace? This issue has been polluted by a mix of a few different errors (and causes) and I would like to not add to it.

theobouwman · 2024-02-08T16:27:44Z

I am seeing the same error on Google Cloud Run:

Error: Cannot find module '/usr/src/app/node_modules/@sentry/profiling-node/lib/sentry_cpu_profiler-linux-x64-glibc-120.node'

I am using this template https://github.com/GoogleCloudPlatform/cloud-run-microservice-template-nodejs

jamespsterling · 2024-03-25T12:57:58Z

I am seeing the same error on Google Cloud Run:
Error: Cannot find module '/usr/src/app/node_modules/@sentry/profiling-node/lib/sentry_cpu_profiler-linux-x64-glibc-120.node'
I am using this template https://github.com/GoogleCloudPlatform/cloud-run-microservice-template-nodejs

I am seeing this on MacOS M2 Max as well.

JonasBa · 2024-03-25T14:37:17Z

@jamespsterling @theobouwman It seems like this is attempting to load the binaries for Node version 21. We do not officially support non LTS node versions and we do not provide precompiled binaries for these environments - v21 is not LTS. You will have to compile the binaries yourself and install the required tooling (which depends on the images you are using, but tipically involves python, git and a couple other build tools). The alternative is to downgrade to v20 or wait for when v22 reaches LTS and we provide precompiled binaries.

dancrumb · 2024-04-23T21:03:37Z

In case this helps others: I was seeing this issue on a fresh Ubuntu box.

I'd install node via nvm.

Once I installed node-gyp via apt, everything worked correctly for me. Installing that brought in a lot of dependencies, so I couldn't say for sure whether it was node-gyp or a dependency that solved the issue.

pppdns · 2024-04-24T17:30:26Z

@jamespsterling @theobouwman It seems like this is attempting to load the binaries for Node version 21. We do not officially support non LTS node versions and we do not provide precompiled binaries for these environments - v21 is not LTS. You will have to compile the binaries yourself and install the required tooling (which depends on the images you are using, but tipically involves python, git and a couple other build tools). The alternative is to downgrade to v20 or wait for when v22 reaches LTS and we provide precompiled binaries.

🎉🎉🎉 Switching to Node v20 from v21 fixed the issue for me! 🎉🎉🎉

package.json:

  "engines": {
    "node": "20"
  },

I'm using ubuntu-22 on DigitalOcean (default DO image) and npm.

pppdns · 2024-07-07T13:54:25Z

I got Node 22 to work (even though it's not yet LTS...) by updating these Sentry packages to their latest versions in package.json.

      "@sentry/cli": "^2.32.0",
      "@sentry/node": "^8.15.0",
      "@sentry/profiling-node": "^8.15.0",
...
  "engines": {
    "node": "22"
  },

I did this because Node 20 suddenly started throwing errors during build and deployment in the Sentry step.

We do not officially support non LTS node versions and we do not provide precompiled binaries for these environments

It looks like these Sentry binary versions are highly unreliable. It would be nice to have a more robust and reliable automatic build process at Sentry to build these binaries for all Node versions (not just LTS).

My LTS Node 20 suddenly started throwing errors during build, but the non-LTS Node 22 works, which is not supposed to work based on the above comment that I quoted

JonasBa · 2024-07-07T18:35:51Z

@pppdns It has been a while since that comment and we actually build binaries for v22 since a few months now, so the binaries working for v22 is expected.

I did this because Node 20 suddenly started throwing errors during build and deployment in the Sentry step.

Would you mind sharing what sort of errors you were seeing? Did you upgrade or change anything in your environment? Our code here hadnt changed, so I suspect there might be something external that caused this. Please send us the error so we can investigate

Regarding the binaries being unreliable, I would disagree that it's the actual binaries that are unreliable. That said, there is a lot of confusion and required knowledge around how nodejs and bundling works with native binaries which can unfortunately lead to errors in the setup. We'll try see if we can improve that.

pppdns · 2024-07-14T16:38:59Z

I'll see if I can get the error logs, if yes, I will post them.

Regarding the confusion around how these binaries are supposed to work, some extra documentation would be nice. I don't think it's available for the public currently

JefferyHus · 2024-08-15T08:17:09Z

Not sure why this started happening just today, the project was running fine and is in production but just trying to run it today in my local it gave me the same error:

npm error   code: 'MODULE_NOT_FOUND',
npm error   requireStack: [
npm error     '/Users/path/to/node_modules/@sentry/profiling-node/scripts/check-build.js'
npm error   ]
npm error }
npm error
npm error Node.js v20.15.1

codeyourwayup · 2024-09-08T05:08:00Z

The issue is here https://github.com/getsentry/profiling-node/blob/main/src/cpu_profiler.ts#L2, the versions variable returned by the import is 20.4, while my code is running on node 18.16.

There is an issue because the code checks your current Node.js version and retrieves the abi for version "21.0.0" (which is 120). Therefore, if I use Node.js version 18.18.0, it will use the correct profiling version. It worked!

JonasBa · 2024-09-09T15:42:19Z

The issue is here https://github.com/getsentry/profiling-node/blob/main/src/cpu_profiler.ts#L2, the versions variable returned by the import is 20.4, while my code is running on node 18.16.

There is an issue because the code checks your current Node.js version and retrieves the abi for version "21.0.0" (which is 120). Therefore, if I use Node.js version 18.18.0, it will use the correct profiling version. It worked!

Yes, that is because we only support even major versions of nodejs as they have long term support as opposed to becoming unsupported after ~6 months.

Major Node.js versions enter Current release status for six months, which gives library authors time to add support for them. After six months, odd-numbered releases (9, 11, etc.) become unsupported, and even-numbered releases (10, 12, etc.) move to Active LTS status and are ready for general use. LTS release status is "long-term support", which typically guarantees that critical bugs will be fixed for a total of 30 months. Production applications should only use Active LTS or Maintenance LTS releases.

Source: https://nodejs.org/en/about/previous-releases

jl75 mentioned this issue Jul 2, 2023

Error: Cannot find module '/.next/server/app/(account)/binaries/sentry_cpu_profiler-v93-darwin-arm64.node' #141

Closed

11 tasks

timonmasberg mentioned this issue Jul 3, 2023

fix(deps): update dependency @sentry/profiling-node to v1.0.8 kordis-leitstelle/kordis#251

Merged

1 task

whaagmans mentioned this issue Jul 4, 2023

fix: Issue fixed for building binary with recompileFromSource #173

Merged

JonasBa closed this as completed Aug 28, 2023

rajdip-b mentioned this issue May 7, 2024

feat(api): Skip workspace creation if the user is an admin user keyshade-xyz/keyshade#194

Closed

10 tasks

1.0.7 ./sentry_cpu_profiler-darwin-arm64-115.node not found #171

1.0.7 ./sentry_cpu_profiler-darwin-arm64-115.node not found #171

Comments

andylacko commented Jun 30, 2023

Is there an existing issue for this?

How do you use Sentry?

SDK Version

Link to Sentry event

What environment is your node script running in?

How is your code deployed and bundled?

Steps to Reproduce

Expected Result

Actual Result

stephenhmarsh commented Jul 4, 2023

JonasBa commented Jul 6, 2023

Klaitos commented Jul 10, 2023 • edited Loading

Klaitos commented Jul 10, 2023

whaagmans commented Jul 10, 2023

Klaitos commented Jul 10, 2023 • edited Loading

whaagmans commented Jul 10, 2023 • edited Loading

Klaitos commented Jul 10, 2023

Klaitos commented Jul 10, 2023 • edited Loading

whaagmans commented Jul 10, 2023 • edited Loading

Klaitos commented Jul 10, 2023

JonasBa commented Jul 17, 2023

nicksrandall commented Jul 17, 2023

whaagmans commented Jul 17, 2023

JonasBa commented Jul 19, 2023

yash-coded commented Jul 28, 2023

JonasBa commented Jul 28, 2023

yash-coded commented Jul 28, 2023

JonasBa commented Jul 28, 2023

nicksrandall commented Jul 28, 2023

yash-coded commented Jul 28, 2023

yash-coded commented Jul 28, 2023

JonasBa commented Jul 28, 2023

yash-coded commented Jul 28, 2023

JonasBa commented Jul 28, 2023 • edited Loading

yash-coded commented Jul 28, 2023 • edited Loading

JonasBa commented Jul 28, 2023

yash-coded commented Jul 28, 2023

JonasBa commented Jul 28, 2023

mrmckeb commented Aug 4, 2023

JonasBa commented Aug 4, 2023

JonasBa commented Aug 28, 2023 • edited Loading

miteshkotak commented Aug 29, 2023 • edited Loading

nicksrandall commented Aug 29, 2023

JonasBa commented Aug 29, 2023

theobouwman commented Feb 8, 2024

jamespsterling commented Mar 25, 2024

JonasBa commented Mar 25, 2024 • edited Loading

dancrumb commented Apr 23, 2024

pppdns commented Apr 24, 2024 • edited Loading

pppdns commented Jul 7, 2024 • edited Loading

JonasBa commented Jul 7, 2024 • edited Loading

pppdns commented Jul 14, 2024

JefferyHus commented Aug 15, 2024

codeyourwayup commented Sep 8, 2024

JonasBa commented Sep 9, 2024

Klaitos commented Jul 10, 2023 •

edited

Loading

Klaitos commented Jul 10, 2023 •

edited

Loading

whaagmans commented Jul 10, 2023 •

edited

Loading

Klaitos commented Jul 10, 2023 •

edited

Loading

whaagmans commented Jul 10, 2023 •

edited

Loading

JonasBa commented Jul 28, 2023 •

edited

Loading

yash-coded commented Jul 28, 2023 •

edited

Loading

JonasBa commented Aug 28, 2023 •

edited

Loading

miteshkotak commented Aug 29, 2023 •

edited

Loading

JonasBa commented Mar 25, 2024 •

edited

Loading

pppdns commented Apr 24, 2024 •

edited

Loading

pppdns commented Jul 7, 2024 •

edited

Loading

JonasBa commented Jul 7, 2024 •

edited

Loading