Node-Red does not start BeagleBone Black (Linux 4.4.30 - Debian 8.7 : jessie)

[NikoSt]

Hi all,
I have followed the instructions to install Node-Red on my BBB (Linux 4.4.30-ti-r64 #1, Debian Linux 8.7 (jessie),
as described in node-red site :

https://nodered.org/docs/hardware/beagleboneblack

but when I try to run it : sudo node-red-pi (this is the suggested command)
I get the following messages:

Welcome to Node-RED
===================

22 May 15:11:28 - [info] Node-RED version: v0.16.2
22 May 15:11:28 - [info] Node.js  version: v6.10.1
22 May 15:11:28 - [info] Linux 4.4.30-ti-r64 arm LE
22 May 15:11:32 - [info] Loading palette nodes
22 May 15:11:48 - [warn] ------------------------------------------------------
22 May 15:11:48 - [warn] [rpi-gpio] Info : Ignoring Raspberry Pi specific node
22 May 15:11:48 - [warn] [upm-grove-button] Error: Module version mismatch. Expected 48, got 14.
22 May 15:11:48 - [warn] [upm-grove-buzzer] Error: Module version mismatch. Expected 48, got 14.
22 May 15:11:48 - [warn] [upm-grove-led] Error: Module version mismatch. Expected 48, got 14.
22 May 15:11:48 - [warn] [upm-grove-light] Error: Module version mismatch. Expected 48, got 14.
22 May 15:11:48 - [warn] [upm-grove-relay] Error: Module version mismatch. Expected 48, got 14.
22 May 15:11:48 - [warn] [upm-grove-rgb-lcd] Error: Module version mismatch. Expected 48, got 14.
22 May 15:11:48 - [warn] [upm-grove-rotary] Error: Module version mismatch. Expected 48, got 14.
22 May 15:11:48 - [warn] [upm-grove-sound] Error: Module version mismatch. Expected 48, got 14.
22 May 15:11:48 - [warn] [upm-grove-temperature] Error: Module version mismatch. Expected 48, got 14.
22 May 15:11:48 - [warn] [upm-grove-adxl345] Error: Module version mismatch. Expected 48, got 14.
22 May 15:11:48 - [warn] [upm-grove-servo] Error: Module version mismatch. Expected 48, got 14.
22 May 15:11:48 - [warn] ------------------------------------------------------
22 May 15:11:48 - [info] Settings file  : /root/.node-red/settings.js
22 May 15:11:48 - [info] User directory : /root/.node-red
22 May 15:11:48 - [info] Flows file     : /root/.node-red/flows_beaglebone.json
22 May 15:11:48 - [info] Creating new flow file
22 May 15:11:48 - [info] Starting flows
22 May 15:11:48 - [info] Started flows
22 May 15:11:48 - [warn] Communication server error: Error: listen EADDRINUSE 0.0.0.0:1880
22 May 15:11:48 - [error] Unable to listen on http://127.0.0.1:1880/
22 May 15:11:48 - [error] Error: port in use

I have checked with :
$netstat -npl

and I get
............
............
tcp6   0  0:::1880 :::* LISTEN 1/init
............
............

any ideas/help are welcomed.

Regards
Nikolas

[Mark Setrem]

Well you appear to have multiple issues. The bottom 3 lines suggest you could be running multiple versions of node-red concurrently.

Did you start by running it without sudo and then try starting a version with sudo in order to use the GPIO ports?
Alternatively have you followed the instruction to auto-start and are now trying to also start it using the command line?

Either way you can only run one copy of node-red at a time (pointing at the same port number (1880)) so you need to either stop the other copy of node-red or work out what is using that port and stop that.

[NikoSt]

Dear Mark, thanks for your post.
It is running now (I am putting everything for anyone may interested)
 
Referring to your questions:
I haven't intentionally started the node-red twice. Actually, after the installation process I tried to start node-red with no success.
I may tried without sudo at first, and then using sudo. But in anyway, I had no success launching node-red at all.

Having read your post I checked with
ps -ef
and I didn't see anything looking similar to node-red or nodjs.

Then I reboot it (sudo reboot) and having connected back through USB (putty at 192.168.7.2)
I tested the ports again
netstat -a
and the port 1880 was not reported at all.
So, I tried again : sudo no-red-pi
and now I have (see bellow), the cursor is not appearing (it looks waiting for something or it is stuck)

Welcome to Node-RED
===================

22 May 17:29:09 - [info] Node-RED version: v0.16.2
22 May 17:29:09 - [info] Node.js  version: v6.10.1
22 May 17:29:09 - [info] Linux 4.4.30-ti-r64 arm LE
22 May 17:29:14 - [info] Loading palette nodes
22 May 17:29:32 - [warn] ------------------------------------------------------
22 May 17:29:32 - [warn] [rpi-gpio] Info : Ignoring Raspberry Pi specific node
22 May 17:29:32 - [warn] [upm-grove-button] Error: Module version mismatch. Expected 48, got 14.
22 May 17:29:32 - [warn] [upm-grove-buzzer] Error: Module version mismatch. Expected 48, got 14.
22 May 17:29:32 - [warn] [upm-grove-led] Error: Module version mismatch. Expected 48, got 14.
22 May 17:29:32 - [warn] [upm-grove-light] Error: Module version mismatch. Expected 48, got 14.
22 May 17:29:32 - [warn] [upm-grove-relay] Error: Module version mismatch. Expected 48, got 14.
22 May 17:29:32 - [warn] [upm-grove-rgb-lcd] Error: Module version mismatch. Expected 48, got 14.
22 May 17:29:32 - [warn] [upm-grove-rotary] Error: Module version mismatch. Expected 48, got 14.
22 May 17:29:32 - [warn] [upm-grove-sound] Error: Module version mismatch. Expected 48, got 14.
22 May 17:29:32 - [warn] [upm-grove-temperature] Error: Module version mismatch. Expected 48, got 14.
22 May 17:29:32 - [warn] [upm-grove-adxl345] Error: Module version mismatch. Expected 48, got 14.
22 May 17:29:32 - [warn] [upm-grove-servo] Error: Module version mismatch. Expected 48, got 14.
22 May 17:29:32 - [warn] ------------------------------------------------------
22 May 17:29:32 - [info] Settings file  : /root/.node-red/settings.js
22 May 17:29:32 - [info] User directory : /root/.node-red
22 May 17:29:32 - [info] Flows file     : /root/.node-red/flows_beaglebone.json
22 May 17:29:32 - [info] Creating new flow file
22 May 17:29:32 - [info] Starting flows
22 May 17:29:32 - [info] Started flows
22 May 17:29:32 - [info] Server now running at http://127.0.0.1:1880/

BUT the node-red is running !!!

To finally get into its editor I typed
http://192.168.7.2:1880
(which is the IP of the USB port)
When I was trying to connect to the eth0 ip (192.168.1.6 : 1880) I had no success.

Now, I have it running and connected to it
why I get all these warnings ? I am loosing these modules?

[Mark Setrem]

Well one problem solved....

 I dont have a beaglebone but on having a quick read, have you added the upm modules yourself?  They appear to come from http://flows.nodered.org/node/node-red-node-upm which in the readme states "Only tested on the Intel Edison" which might explain it.

Hopefully someone else with a beaglebone will see this thread and be able to confirm if they work on your device or not.

[Dave C-J]

I think some beaglebone images now actually come with Node-RED and the upm stuff installed... (all very nice !) - but we don't know who did it... 

By all accounts they have done a decent job, but it not the same as our install so they can and do clash if you try to mix them up, which is a pain.

Those warnings are typically due to the modules having native code that is compiled against a different version of node.js, so they would all need rebuilding - but again, as we didn't do the base install I'm not sure how or where they are installed in the first place so can't really advise how exactly to upgrade them.

[NikoSt]

I haven't downloaded myself, so it has to be the case described by Dave
(came with BBB image)
The image I have installed is one from the BBB  .org site.

As I don't actually need them, how can I delete them ?
Do they harm my installation? (causing trouble with other nodes-flows)?

[ResoTek Inc]

Niko,

I think your solution is to disable the node-red socket:

$ sudo systemctl disable node-red.socket

An alternative solution would be to uninstall node-red version 0.15.2 before installing version 0.16.x

Both solutions are proposed in the thread Node-Red upgrade to 16.0 on BeagleBone breaks