Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: Could not find wrtc binary on any of the paths when running pnpm start #1965

Open
junlongYE1110 opened this issue Jan 7, 2025 · 7 comments

Comments

@junlongYE1110
Copy link

I encountered an error when running pnpm start in my project. The error message indicates that the required wrtc binary could not be found. Below is the full error log:

/mnt/c/Users/cxz63/solana/eliza/eliza-starter/node_modules/.pnpm/@roamhq[email protected]/node_modules/@roamhq/wrtc/lib/binding.js:27
throw new Error(Could not find wrtc binary on any of the paths: ${paths_to_try});
^

Error: Could not find wrtc binary on any of the paths: ../build-linux-x64/wrtc.node,../build-linux-x64/Debug/wrtc.node,../build-linux-x64/Release/wrtc.node,@roamhq/wrtc-linux-x64,./node_modules/@roamhq/wrtc-linux-x64,./node_modules/@roamhq/wrtc-linux-x64/wrtc.node
at Object. (/mnt/c/Users/cxz63/solana/eliza/eliza-starter/node_modules/.pnpm/@roamhq[email protected]/node_modules/@roamhq/wrtc/lib/binding.js:27:9)
at Module._compile (node:internal/modules/cjs/loader:1568:14)
at Object..js (node:internal/modules/cjs/loader:1711:10)
at Module.load (node:internal/modules/cjs/loader:1328:32)
at Function._load (node:internal/modules/cjs/loader:1138:12)
at TracingChannel.traceSync (node:diagnostics_channel:315:14)
at wrapModuleLoad (node:internal/modules/cjs/loader:218:24)
at Module.require (node:internal/modules/cjs/loader:1350:12)
at require (node:internal/modules/helpers:138:16)
at Object. (/mnt/c/Users/cxz63/solana/eliza/eliza-starter/node_modules/.pnpm/@roamhq[email protected]/node_modules/@roamhq/wrtc/lib/index.js:23:5)

Here are the details of my development environment:
Operating System: Windows 10 using WSL 2 (Ubuntu 20.04.6 LTS)
Node.js Version: v23.0.0
pnpm Version: 9.15.2
Python Version: 3.8.10

Is this issue related to the @roamhq/wrtc module compatibility with WSL or Node.js v23?
Are there any additional steps or configurations required to make this module work in WSL?

Copy link
Contributor

github-actions bot commented Jan 7, 2025

Hello @junlongYE1110! Welcome to the ai16z community. Thank you for opening your first issue; we appreciate your contribution. You are now a ai16z contributor!

@www222fff
Copy link

same issue met, any solution?

@brkagithub
Copy link

hey, have the same issue on our server, we managed to run it locally on Mac but running into this on Linux
don't think its WSL specific, any Linux machine is affected

@BogBogdan
Copy link

Hey, I have the same issue.

@nicky-ru
Copy link
Contributor

nicky-ru commented Jan 8, 2025

it's something in the Twitter client, if removed twitter client import from the agent everything works fine (but it def not a solution lol)

@nicky-ru
Copy link
Contributor

nicky-ru commented Jan 8, 2025

agent-twitter-client v0.0.18 causes the issue with it's dependency on @roamhq/wrtc

@nicky-ru
Copy link
Contributor

nicky-ru commented Jan 8, 2025

Looks like the issue was with GLIBC version:

/node_modules/@roamhq/wrtc-linux-x64/wrtc.node: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.34' not found (required by /node_modules/@roamhq/wrtc-linux-x64/wrtc.node)
/node_modules/@roamhq/wrtc-linux-x64/wrtc.node: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.32' not found (required by /node_modules/@roamhq/wrtc-linux-x64/wrtc.node)
        linux-vdso.so.1 (0x00007fffdf7fb000)
        libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x0000716c7441e000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x0000716c75c3f000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x0000716c7422c000)
        /lib64/ld-linux-x86-64.so.2 (0x0000716c75d9a000)
        libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x0000716c74211000)

switched to Ubuntu 22.04 with GLIBC 2.35 and everything works now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants