Installing NodeRed on emonSD-30Oct18

Paul · 2018-11-30T10:42:10.230Z

It certainly looks like that is your problem - it can’t locate the source files for nodeJS.

Could your system source list files have become corrupted, so that it cannot locate the nodeJS package?
You could try deleting them, and re-installing them.

sudo rm /var/lib/apt/lists/* -vf

and then add them back;

sudo apt-get update

borpin · 2018-11-30T10:55:27.935Z

I found this answer from here by searching on

The package nodejs needs to be reinstalled, but I can’t find an archive for it

might work.

If not I’d install ‘npm’ (if not installed) and then ‘n’ and then nodejs. n is an excellent package manager. I have had to switch down a NodeJS version to get some BLE packages to work. I can give you more info if necessary.

borpin · 2018-11-30T11:00:02.765Z

Might seem an odd question, but what Pi are you using?

Paul · 2018-11-30T11:00:33.944Z

borpin:

I found this answer from here

I don’t think it’s a corrupted package Brian. Because the node-RED script is confirming that it has successfully removed it from the system, before trying to find the source URL to re install it.

JohnSchols · 2018-11-30T11:03:08.844Z

borpin:

Might seem an odd question, but what Pi are you using?

as follows from admin page

Server Information


Emoncms	Version	low-write 9.9.5
	Modules	Administration : App v1.2.0 : Backup v1.1.5 : EmonHub Config v1.0.0 : Dashboard v1.3.1 : Device v1.2.0 : EventProcesses : Feed : Graph v1.2.1 : Input : Postprocess v1.0.0 : CoreProcess : Schedule : Network Setup v1.0.0 : sync : Time : User : Visualisation : WiFi v1.3.0
	Git URL	GitHub - emoncms/emoncms: Web-app for processing, logging and visualising energy, temperature and other environmental data
	Git Branch	* stable
	Buffer	loading…
	Writer	Daemon is running with sleep 60s
Server	OS	Linux 4.14.71-v7+
	Host	emonpi emonpi (192.168.1.121)
	Date	2018-11-30 11:01:49 UTC
	Uptime	11:01:49 up 1:11, 0 users, load average: 1.60, 1.71, 1.76
HTTP	Server	Apache/2.4.25 (Raspbian) HTTP/1.1 CGI/1.1 80
MySQL	Version	5.5.5-10.1.23-MariaDB-9+deb9u1
	Host	127.0.0.1 (127.0.0.1)
	Date	2018-11-30 11:01:49 (UTC 00:00‌)
	Stats	Uptime: 4265 Threads: 3 Questions: 16944 Slow queries: 0 Opens: 23 Flush tables: 1 Open tables: 17 Queries per second avg: 3.972
Redis	Version	3.2.6
	Host	localhost:6379 (127.0.0.1)
	Size	221 keys (869.52K)
	Uptime	0 days
MQTT Server	Version	Mosquitto 1.4.10
	Host	localhost:1883 (127.0.0.1)
Pi	Model	Raspberry Pi 3 Model B Rev 1.2 - 1 GB (Sony UK)
	SoC	Broadcom BCM2835
	Serial num.	2A7E72D2
	Temperature	CPU: 52.62°C - GPU: 53.2’C
	Release	emonSD-30Oct18
	File-system	Current: read-write - Set root file-system temporarily to read-write, (default read-only)
Memory	RAM	Used: 17.48% Total: 976.74 MB Used: 170.69 MB Free: 806.05 MB
	Swap	Used: 0.00% Total: 100 MB Used: 0 B Free: 100 MB
Disk	Mount	Stats
	/	Used: 39.33% Total: 3.81 GB Used: 1.5 GB Free: 2.13 GB
	/boot	Used: 51.69% Total: 42.52 MB Used: 21.98 MB Free: 20.54 MB
	/home/pi/data	Used: 4.09% Total: 10.32 GB Used: 431.92 MB Free: 9.37 GB
PHP	Version	7.0.30-0+deb9u1 (Zend Version 3.0.0)
	Modules	apache2handler : calendar v7.0.30-0+deb9u1 : Core v7.0.30-0+deb9u1 : ctype v7.0.30-0+deb9u1 : curl v7.0.30-0+deb9u1 : date v7.0.30-0+deb9u1 : dom v20031129 : exif v7.0.30-0+deb9u1 : fileinfo v1.0.5 : filter v7.0.30-0+deb9u1 : ftp v7.0.30-0+deb9u1 : gd v7.0.30-0+deb9u1 : gettext v7.0.30-0+deb9u1 : hash v1.0 : iconv v7.0.30-0+deb9u1 : igbinary v2.0.1 : json v1.4.0 : libxml v7.0.30-0+deb9u1 : mbstring v7.0.30-0+deb9u1 : mcrypt v7.0.30-0+deb9u1 : mosquitto v0.4.0 : mysqli v7.0.30-0+deb9u1 : mysqlnd vmysqlnd 5.0.12-dev - 20150407 - $Id: b5c5906d452ec590732a93b051f3827e02749b83 $ : openssl v7.0.30-0+deb9u1 : pcre v7.0.30-0+deb9u1 : PDO v7.0.30-0+deb9u1 : pdo_mysql v7.0.30-0+deb9u1 : Phar v2.0.2 : posix v7.0.30-0+deb9u1 : readline v7.0.30-0+deb9u1 : redis v4.1.1 : Reflection v7.0.30-0+deb9u1 : session v7.0.30-0+deb9u1 : shmop v7.0.30-0+deb9u1 : SimpleXML v7.0.30-0+deb9u1 : sockets v7.0.30-0+deb9u1 : SPL v7.0.30-0+deb9u1 : standard v7.0.30-0+deb9u1 : sysvmsg v7.0.30-0+deb9u1 : sysvsem v7.0.30-0+deb9u1 : sysvshm v7.0.30-0+deb9u1 : tokenizer v7.0.30-0+deb9u1 : wddx v7.0.30-0+deb9u1 : xml v7.0.30-0+deb9u1 : xmlreader v7.0.30-0+deb9u1 : xmlwriter v7.0.30-0+deb9u1 : xsl v7.0.30-0+deb9u1 : Zend OPcache v7.0.30-0+deb9u1 : zlib v7.0.30-0+deb9u1

Client Information


HTTP	Browser	Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Safari/537.36
Screen	Resolution	1920 x 1080
Window	Size	1903 x 948

borpin · 2018-11-30T11:18:52.461Z

Paul:

Because the node-RED script is confirming that it has successfully removed it from the system, before trying to find the source URL to re install it.

I think that is a default answer from the script rather than an actual confirmation as it keep repeating that answer despite not reinstalling.

@JohnSchols try


[edit] sorry should be
```
sudo dpkg --purge --force-all nodejs
```

and retry script.

JohnSchols · 2018-11-30T11:19:24.800Z

borpin:

I can give you more info if necessary.

I haven’t added anything to the recently received emonSD-30Oct18. Is it possible that the emonSD has a problem?

JohnSchols · 2018-11-30T11:23:05.253Z

borpin:

sudo dpkg --purge --force-all nodejs

is this the expected output

emonSD-30Oct18
pi@emonpi:~ $ sudo dpkg --purge --force-all nodejs
dpkg: warning: overriding problem because --force enabled:
dpkg: warning: package is in a very bad inconsistent state; you should
reinstall it before attempting a removal
(Reading database ... 45289 files and directories currently installed.)
Removing nodejs (10.14.0-1nodesource1) …
pi@emonpi:~ $

Paul · 2018-11-30T11:23:23.336Z

JohnSchols:

Is it possible that the emonSD has a problem?

Have you tried my suggestion above about replacing possibly corrupt list files?

borpin · 2018-11-30T11:24:35.339Z

OK so try

sudo dpkg --remove --force-remove-reinstreq nodejs

Paul · 2018-11-30T11:26:09.896Z

It’s misleading having 2 people advising John at once, so I’ll leave it with you for now Brian.

borpin · 2018-11-30T11:26:37.442Z

Paul:

It’s misleading having 2 people advising John at once, so I’ll leave it with you for now Brian.

Ok, I think the package itself is corrupt.

borpin · 2018-11-30T11:28:39.414Z

JohnSchols:

is this the expected output

I edited your reply. It is 3 ticks on a line on its own, then the code (no more ticks) then 3 more at the end of the block on a line on their own.

JohnSchols · 2018-11-30T11:29:22.247Z

glyn.hudson:

bash <(curl -sL https://raw.githubusercontent.com/node-red/raspbian-deb-package/master/resources/update-nodejs-and-nodered)

brian/Paul
Have restarted script and so far it has passed the place it was stopping at before. Will update if it finishes okay.

JohnSchols · 2018-11-30T11:41:20.390Z

All done.

Script finished. Thank you all for your help.

Paul · 2018-11-30T11:42:14.788Z

So, what made the difference?
What did you do before running the script?

JohnSchols · 2018-11-30T11:44:14.864Z

borpin:

sudo dpkg --purge --force-all nodejs

I ran sudo dpkg --purge --force-all nodejs

before restarting the command

glyn.hudson · 2018-12-01T00:13:43.564Z

Great to hear you got it sorted. Thanks for helping out guys

I’ve just testing again this evening with a fresh emonSD image and again it works first time. Something must have got messed up with @JohnSchols packages somehow.

borpin:

Perhaps add to documentation somewhere?

I just followed the NodeRed RasPi install guide. It’s best for NodeRED to mentain their own install guide since steps may change over time: Redirecting…

borpin · 2018-12-01T09:25:47.978Z

glyn.hudson:

Perhaps add to documentation somewhere?

I just followed the NodeRed RasPi install guide. It’s best for NodeRED to mentain their own install guide since steps may change over time: Redirecting…

Agreed, but what I meant was that, as it will be quite common for users to want Node-Red especially those upgrading from the old SD image, it would be worth, in the How to Upgrade to New SD Image (that is a thing right…) that users are pointed to the ‘How to install Node-Red on Raspbian’ pages (having been instructed to enable SSH first of course).

I’ll get my hat…

glyn.hudson · 2018-12-01T12:06:08.304Z

Yes, there is already a note on the NodeRED user guide integrations page:

Guide | OpenEnergyMonitor

Node-RED

Node-RED integration