Repository navigation
[regression] NodeOS don't boot with Node.js v0.11.15 #3204
Description
Activity
Could you share a small reproducable testcase that shows that this is a bug in Node.js/v8?
You can be able to download NodeOS and generate yourself with
npm install, by generating only the barebones is enought. You can check it withnpm startand it will start NodeOS directly to a Node.js REPL.Later, change the version to something bigger than v0.11.14, delete the
depsandobjfolders to force regeneration with the new version, and exec againnpm install: the new one will enter an infinite loop consuming the 100% of the CPU and not showing the REPL.nodeos-barebones is the most minimal use case... Besides that, I only can think about upload somewhere a compiled version with v0.11.14 and another with v0.11.15 (or v4.1.1 if you want, but this is still in experimental status and still not merged in master due to the requeriment of GCC 4.8) so you can be able to check both.
I'm not sure if this is a nodejs problem. What API in nodejs do you interface with? v8 is a very moving target which is why you should use NaN whenever possible.
Edit: I recall prior discussions about incompatibilities between musl and node (v8). Guessing that might be related. Even if you get it to compile I wouldn't assume it'll work as intended. It needs a lot of low level work [probably on both v8 and musl sides] and I'm not sure who would be interested in doing that at the moment.
Nodeos-barebones is only vanilla Node.js running directly on top of a Linux
kernel as PID 1, the only special thing is the usage of musl as C lib.
Besides that, code is untouched and are standard compilations.
El 06/10/2015 12:36, "Johan Bergström" notifications@github.com escribió:I'm not sure if this is a nodejs problem. What API in nodejs do you
interface with? v8 is a very moving target which is why you should use NaN
whenever possible.—
Reply to this email directly or view it on GitHub
#3204 (comment).@piranna I'm with @ChALkeR here; your case is specific enough to fall outside the scope of what is relevant to this project versus nodeos. If you can create a minimalistic test case which is debuggable it might be more relevant, but seeing how you're using musl I think thats too much to chew at the moment. Can you reproduce the same issue with glibc?
We already checked, read the issue pointed on the first comment: the problem came on Node.js v0.11.15 with the change of version of v8, and a lot of people got problems and regressions then, just check old issues tracker. Seems the problem is due to a spin lock on v8:
nodejs/node-v0.x-archive#9113
nodejs/node-v0.x-archive#25137
nodejs/node-v0.x-archive#25295@piranna v8 will continue to be updated, and we make sure we ship a nodejs binary that works on our supported platforms. Your peculiar setup I would argue is out of that scope. Can you try building against glibc and report back?
@piranna all linked issues has fixed closed to them. The last one seems to be related to using
node.js --profstuff. Do you use that in nodeos?No, I can't, we are using musl on NodeOS because glibc is too much complicated to compile from scratch. Node.js supports musl and there's a lot of people using it already, and NodeOS uses a vanilla Linux kernel. You could get a similar environment just by copying the files from your Linux system by hand and put them together, since there are no modified code. Honestly, I don't know why you say it's a peculiar setup...
The last one seems to be related to using node.js --prof stuff
No, I'm not using it, I'm using regular Node.js without flags, but the problem seems to be related, since the results are similar.
@piranna there's no official support of nodejs-baked binaries on top of musl as of yet. We're exploring this as part of making smaller docker images, but its still a work in progress. As per above, compile time doesn't mean runtime.
I don't have much to add from here. If anyone else wants to chip in and learn the innings of nodeos that would probably be a next step since we won't get a reduced case.
The Node.js binary used on NodeOS with musl works correctly on Ubuntu when pointing to the musl libraries, and as I told you, NodeOS uses a vanilla Linux kernel and Node.js v0.11.14 works but newer not. The only different thing between NodeOS and an Ubuntu environment that could explain this issue is the usage of /dev/console as stdio. Besides that, it's a plain regular Linux system.
And regarding NodeOS internals, honestly there's not too much to learn here...
9 remaining items
@seishun, you are right, I was waiting to have some time to try to bisect V8, but until that I can be able to decribe my problem in a more generic way.
My problem is that trying to use Node.js on Linux as PID 1 (
/init), up to Node.js v0.11.14 it gave me a REPL and also I was able to use Node.js apps as PID1, but starting at Node.js v0.11.15 and more exactly after the upgrade of the V8 version, I don't get anymore a Node.js REPL when using it as PID 1 nor use a Node.js app instead, and instead CPU gets at 100% without doing anything.I would need to test if this use case is reproducible with a standard Ubuntu kernel and Node.js (It's just a matter of launching the Linux kernel setting
/usr/bin/nodeas init), but basically that's the description of my problem.Checked on Ubuntu Willy with Node.js 0.12.17 on a real (not virtualized) Dual-Core machine: I get a blinking Node.js REPL prompt, but don't respond to the keyboard.
Can you try with the latest Node.js?
Can you try with the latest Node.js?
Same Dual Core machine, new test with Linux 4.2.0-1 from Ubuntu Willy and Node.js 4.2.1 from NodeSource.
On a first test it crashed because the root filesystem was mounted as readonly (the default of Linux when set as kernel command line parameter) about not being able to create the
.node_completionfile, so it exitted and being the PID1, Linux throw a kernel panic. Setting the root filesystem as read-write it didn't crashed, but the REPL promt was not shown and the console didn't responded, and after some seconds the computer fan started to do some noise so seems the CPU got stuck at 100% too.It's said: the problem is still there on Node.js 4.2.1 :-(
I've checkout the code just before the conflictive Node.js commit and checked that it worked, later I've changed the
deps/v8folder with agit cloneof v8 and none of the commits between 3.26.33 (the same that was included with Node.js) or 3.28.73 worked, sometimes giving me an error about v8.h not being found and anothers about TRANSITION not being defined. Any clue about what could I have done bad or how could I be able to investigate what was the v8 commit that inserted this error? Besided changing the v8 folder with the v8 git repo, I'm out of ideas... :-(I've done more checks and definitely there are some patches that need to be applied on v8, but don't know where to get them. In fact, If you checkout version 3.28.73 there are some differences with the same version of v8 used on Node.js... The list of commits show that there are several patches applied and backported. In any case, I'm not able to compile it and I'm not sure if this patches would help or if I have the problem in other place, because I've only changed the code of v8 for the one on the git repo and in fact it's being compiled... Honestly, I don't know to whom to ask for advice... :-(
Just checked with Linux 4.2 and Node.js 5.1, still not working :-/
@piranna there's not much we as an upstream project can do until you give us the information people have asked you for (see for instance Ben's comments). I'm suggesting we close this and reopen when that is available.
I have tried to bisect v8 changes, but there's a lot of patches on top of it applied by Node.js team over the upstream version that make it almost impossible to do. Is there any repo with the Node.js patched v8? Maybe maintained by @isaacs? Seems commits on Node.js with updates on the v8 version are mostly pushed by him... This way I would be able to bisect them to try to find the one that is causing troubles... On the other hand, seems there were changes on Node.js outside v8 to support that particular version upgrade, so I'm not sure if by bisecting v8 alone would be enough... :-/
@piranna bisecting it will most likely be enough. If I was in your position I wouldn't assume that anyone else would do it for me (ref isaacs), so I suggest that you use
git bisectto identify which commit caused it, then spend an hour looking at why. It should be pretty quick since you always cut the commit log in half. I'm closing this now; feel free to update us once you have a reproducible result.I'm not requesting that this get fixed by anybody nor asking for anybody to do nothing, what Iǜe said is that I already did a git bisect on Node.js and found that the problem surfaced when v8 was updated to 3.28.73, and that last week I did another
git bisectin this case in v8 itself but I was not able to compile Node.js with it because it had several patched from Node.js team, so what I'm asking about is to know about if there's a repo with the patched v8 so I could do thegit bisectover it, no more.If you want some steps to reproduce my problem, they are easy, just boot a Linux system with the
init=/usr/bin/nodeboot argument. Up to Node.js 0.12.14 this will boot Linux and give you a Node.js REPL, starting from Node.js 0.12.15 (and more exactly since v8 was updated to version 3.28.73) instead of getting a REPL the CPU gets hogged up to 100% indefinitely, and the same happens if instead of/usr/bin/nodeyou use a Node.js script.And regarding the v8
git bisect: the Node.js v8 3.28.79 is NOT the same as the upstream v8 3.28.79, that's why I ask for a v8 repo with the Node.js patches applied (if that thing exists...).@piranna: here's the commit history with floating patches for 0.11.15. Assumed you already checked it. https://github.com/nodejs/node/commits/v0.11.15/deps/v8
@piranna: here's the commit history with floating patches for 0.11.15. Assumed you already checked it. https://github.com/nodejs/node/commits/v0.11.15/deps/v8
Yes, I did so, in fact I was using the history up to the failling commit, that's when the already patched v8 3.28.73 was introduced. What I'm asking for if for a repo with the different patched v8 to see what change inserted the problem, as I was requested since that v8 upgrade commit has changes in 1700 files... :-/
In short: this Node.js commit updated v8 and inserted the problem, now I want to now what v8 commit did it, and bisect upstream v8 doesn't work because Node.js don't compile with it because it needs it's own patched one.
Continue discussion from nodejs/node-v0.x-archive#9097.
Since version v0.11.15 of Node.js that changed the version of v8, NodeOS can't boot entering an infinite loop instead of showing a REPL and consuming 100% of CPU. Recent tests showed that this still happen with Node.js v4.1.1