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
Instance built on Ubuntu won't work on Debian or Red Hat systems #248
Comments
I should point out, the obvious answer is to use Ubuntu on all machines (I've tried it, and it works). However, this isn't politically possible |
Run ldd on the .node file and see if there's some differences with linked On Tuesday, January 22, 2013, Simon Emms wrote:
|
Interesting. I'm getting an error. The version built on Ubuntu (when ldd canvas.node is done on the Debian machine) responds.
The working version (built on Debian) reads...
Ideas? |
Your versions of glibc on the two machines are incompatible. |
Thanks, that appears to be the case. Looks like we'll have to set up a build server then... |
I'm having a really frustrating issue getting this integrated with our infrastructure. The company setup is:
All machines are 64 bit.
When we build and release to the Debian/RedHat machines, we always get the following error:
At first, we assumed that there was some architecture issue as per #184, but have subsequently proven this not to be the case and that all machines are indeed running 64 bit builds of NodeJS. What we have noticed is that this is only an issue when deploying to a Debian/RedHat machine - we have some Ubuntu machines in the office and, when we deploy to that, it works first time.
Next, we looked at #216 and updated our PATH and LD_LIBRARY_PATH. However, this has again not worked.
What is particularly confusing is that, if we build everything on the Debian/RedHat box and deploy to anything else (including Ubuntu), it all works. We're therefore assuming that there is something that is some difference between the Debian/RedHat setup compared to the Ubuntu one but cannot identify what this is.
Can someone help shed some light onto that issue?
Thanks
Setup
The text was updated successfully, but these errors were encountered: