node-red-node-beaglebone install broke node-red on 2016-03-27 image

The 2016-03-27 image got off to a very good start for me with node-red working out of the box and all the Bonescript issues I’d had with earlier images appear fixed – analogRead/Write, digitalRead/Write and attachInterrupt in the Cloud9 examples all appear to run correctly without throwing spurious error messages. I mentioned in another thread that only the START.htm link to didn’t work – Navigation Bar on the left was broken and all the Interactive buttons were grayed out.

But when I tried to install node-red-node-beaglebone with:

sudo -i
cd .node-red
npm install -g --unsafe-perm node-red-node-beaglebone

Things went horribly wrong:

./src/ In function ‘v8::Handlev8::Value WriteWord(const int&)’:
…/src/ warning: control reaches end of non-void function [-Wreturn-type]
^ recipe for target ‘Release/’ failed
make: *** [Release/] Error 1
make: Leaving directory ‘/usr/local/lib/node_modules/node-red-node-beaglebone/node_modules/i2c/build’
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack at ChildProcess.emit (events.js:110:17)
gyp ERR! stack at Process.ChildProcess._handle.onexit (child_process.js:1078:12)
gyp ERR! System Linux 4.1.18-ti-r55
gyp ERR! command “node” “/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js” “rebuild”
gyp ERR! cwd /usr/local/lib/node_modules/node-red-node-beaglebone/node_modules/i2c
gyp ERR! node -v v0.12.12
gyp ERR! node-gyp -v v3.3.1
gyp ERR! not ok
npm WARN install:i2c@0.1.8 i2c@0.1.8 install: node-gyp rebuild
npm WARN install:i2c@0.1.8 Exit status 1
└── node-red-node-beaglebone@0.1.5

And after I rebooted something is running on port 1880 but the web browser never connects.
Any ideas how to fix?

Some extra follow-up possibly related to the issue above.

Doing apt-get update, apt-get upgrade on 2015-11-12 the bb-node-red-installer upgrade failed

Setting up libjasper1:armhf (1.900.1-debian1-2.4+deb8u1) …
Setting up bb-node-red-installer (0.13.4-0rcnee1~bpo80+20160321+1) …
bb-node-red-installer:npm: [1.4.21]
bb-node-red-installer:node: [v0.10.42]
bb-node-red-installer:Installing: systemd-0.2.6 (for node-red)
systemd@0.2.6 /usr/local/lib/node_modules/systemd
bb-node-red-installer:Installing: node-red-0.13.4 (for node-red)

bcrypt@0.8.5 install /usr/local/lib/node_modules/node-red/node_modules/bcrypt
node-gyp rebuild

make: Entering directory ‘/usr/local/lib/node_modules/node-red/node_modules/bcrypt/build’
make: Warning: File ‘’ has modification time 2.4 s in the future
CXX(target) Release/
CXX(target) Release/
CXX(target) Release/
dpkg: error processing package bb-node-red-installer (–configure):
subprocess installed post-installation script returned error exit status 137
Setting up c9-core-installer (3.1.1670+git20160304-0rcnee2~bpo80+20160307+1) …
c9-core-installer:npm: [3.8.2]
c9-core-installer:node: [v0.10.42]

Setting up pastebinit (1.5-1~bpo80+20160303+1) …
Processing triggers for initramfs-tools (0.120+deb8u1-1rcnee1~bpo80+20160229+1) …
update-initramfs: Generating /boot/initrd.img-4.1.18-ti-r49
Processing triggers for libc-bin (2.19-18+deb8u3) …
Errors were encountered while processing:
E: Sub-process /usr/bin/dpkg returned an error code (1)

This system is kernel 4.1.18-ti-r49 and I’ve been doing apt-get update, apt-get upgrade pretty regularly (monthly?) so as to not fall to far out of date.
Have I managed to end up with the wrong kernel as things have evolved?

Is there a package to install that would track the current kernel series updates when doing an apt-get upgrade?

I managed to get node red working again with:

sudo npm uninstall -g --unsafe-perm node-red-node-beaglebone
sudo apt-get purge bb-node-red-installer
sudo apt-get install bb-node-red-installer