Trying to update node.js fails

thad

I recently updated MM and I’m having problems getting MM to start. It appears my issues are due to an old version of node.js (v10.15.2) and attempts to upgrade it fail. I can get MM to start using run-start.sh, but it doesn’t work with pm2. Here’s what I think should be a clue:

Check current Node installation …
Node currently installed. Checking version number.
Minimum Node version: v16.9.1
Installed Node version: v10.15.2
Node should be upgraded.
Installing Node.js …
E: Repository ‘http://archive.raspberrypi.org/debian buster InRelease’ changed its ‘Suite’ value from ‘testing’ to ‘oldstable’
E: Repository ‘http://raspbian.raspberrypi.org/raspbian buster InRelease’ changed its ‘Suite’ value from ‘stable’ to ‘oldstable’
Reading package lists… Done
Building dependency tree
Reading state information… Done
nodejs is already the newest version (10.15.2~dfsg-2+rpi1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
node version is
Node.js installation Done! version=v10.15.2
Check current NPM installation …
NPM currently installed. Checking version number.
npm does not support Node.js v10.15.2
You should probably upgrade to a newer version of node as we
can’t make any promises that npm will work with this version.
You can find the latest version at https://nodejs.org/
/usr/local/lib/node_modules/npm/lib/npm.js:32

I need some help deciphering why it’s failing and what I can do to upgrade node.js successfully.

Let me know if you have any suggestions, or if you think I’m looking in the wrong direction.

Thanks.
Thad

sdetweil

@thad do you have nvm installed
do

which nvm

(if nvm is NOT installed u will get a blank response)
nvm sets its own path which overrides the base path

sdetweil

@thad as for pm2, then show the pm2 logs

pm2 logs --lines=100

(ctrl-c to end)
maybe need to clear them first to get shorter version

pm2 flush
then pm2 start
them pm2 logs --lines=100 as above

bugsounet

@thad said in Trying to update node.js fails:

E: Repository ‘http://archive.raspberrypi.org/debian buster InRelease’ changed its ‘Suite’ value from ‘testing’ to ‘oldstable’
E: Repository ‘http://raspbian.raspberrypi.org/raspbian buster InRelease’ changed its ‘Suite’ value from ‘stable’ to ‘oldstable’

@sdetweil : to correct this:

sudo apt-get --allow-releaseinfo-change update

(I’m really so kind, this cannot last !!! :dizzy_face: )

thad

I don’t have nvm installed. The command ‘which nvm’ command returned nothing.

If I clear the pm2 logs and immediately look at them, I’m seeing something odd. It appears I have 2 processed controlled by pm2. Here’s the output:

pi@raspberrypi:~/MagicMirror $ pm2 logs --lines=100
[TAILING] Tailing last 100 lines for [all] processes (change the value with --lines option)
/home/pi/.pm2/pm2.log last 100 lines:
/home/pi/.pm2/logs/MagicMirror-out.log last 100 lines:
/home/pi/.pm2/logs/MagicMirror-error.log last 100 lines:
/home/pi/.pm2/logs/mm-out.log last 100 lines:
/home/pi/.pm2/logs/mm-error.log last 100 lines:

I think the MagicMirror references are to my initial installation from a year or two ago. The references to ‘mm’ are what I attempted to do this morning.

thad

@bugsounet said in Trying to update node.js fails:

sudo apt-get --allow-releaseinfo-change update

That made a big difference! The script that updates node.js now runs properly! Thanks.

I’ll keep playing and see if I can get this thing running again.

thad

@bugsounet @bugsounet

Thanks for your help. This has me running again. I need to work on the weather module some more. I have the current weather working, but the forecast is hung on ‘loading’. Thanks again for the super quick responses!

sdetweil

@bugsounet thx… added to upgrade, had for install

sdetweil

@thad pm2 status shows the processes registered to manage

pm2 info x (x is name or number) will show what it run

pm2 delete x will remove an entry

pm2 --help will show all the things u can do .

thad

@sdetweil

Thanks. I was able to remove the entry I created this morning, to there’s only one. I’m still having issues with pm2. If I start MM using pm2 after a couple of minutes it restarts. The pm2 log shows:

For some reason this keeps cycling. At the moment I’ve started MM using the run-start.sh script and it appears to be stable.

sdetweil

@thad is there a cron job running? maybe killing pm2

thad

@sdetweil

I don’t have any cron jobs running. A crontab -l says there’s nothing for user pi.

sdetweil

@thad ok, lets see if we can start over on pm2

do

pm2 unstartup

it will give u a command to issue to remove the pm2 hooks
then do

sudo npm uninstall pm2

then run my fixuppm2.sh script again … it will redo all the setup

thad

@sdetweil

Looks promising! MagicMirror has been running with the same pid for 5 minutes now!

thad

@sdetweil

That worked for around 20 minutes and now it’s restarting randomly again. Let me get the pm2 logs…

Here they are:

0|MagicMirror | Newsfeed-Fetcher: Broadcasting 54 items.
0|MagicMirror | [12.01.2022 11:40.16.970] [INFO]
0|MagicMirror | Calendar-Fetcher: Broadcasting 9 events.
PM2 | pm2 has been killed by signal, dumping process list before exit…
PM2 | Deleting process 0
PM2 | Stopping app:MagicMirror id:0
PM2 | App [MagicMirror:0] exited with code [0] via signal [SIGTERM]
0|MagicMirror | [12.01.2022 11:41.34.434] [LOG] Shutting down server…
0|MagicMirror | [12.01.2022 11:41.34.457] [LOG] Stopping module helper: updatenotification
0|MagicMirror | [12.01.2022 11:41.34.459] [LOG] Stopping module helper: MMM-AVStock
0|MagicMirror | [12.01.2022 11:41.34.460] [LOG] Stopping module helper: calendar
0|MagicMirror | [12.01.2022 11:41.34.461] [LOG] Stopping module helper: newsfeed
0|MagicMirror | [1561:0112/114134.512661:ERROR:command_buffer_proxy_impl.cc(328)] GPU state invalid after WaitForGetOffsetInRange.
0|MagicMirror | [1561:0112/114134.561597:ERROR:zygote_communication_linux.cc(276)] Failed to send GetTerminationStatus message to zygote
0|MagicMirror | [1561:0112/114134.568770:ERROR:zygote_communication_linux.cc(276)] Failed to send GetTerminationStatus message to zygote
PM2 | pid=1533 msg=process killed
PM2 | Exited peacefully
0|MagicMirror | > magicmirror@2.18.0 start
0|MagicMirror | > DISPLAY=“${DISPLAY:=:0}” ./node_modules/.bin/electron js/electron.js
0|MagicMirror | [12.01.2022 11:41.39.771] [LOG]
0|MagicMirror | Starting MagicMirror: v2.18.0

sdetweil

@thad fun times

edit package.json and add

--disable-gpu

between the node_modules/electron and the js/electron.js

on the start statement

on my phone so hard to build good statement result… like this…

"start":"DISPLAY=${DISPLAY:=:0}./node_modules/.bin/electron --disable-gpu js/electron.js"

thad

@sdetweil

Looking good. Right at an hour with no restarts.

sdetweil

@thad what pi is this? and what os?

lsb_release -a

will show the os release info

thad

@sdetweil

It’s a pi4 running Raspbian release 10.

sdetweil

@thad release 10, is that buster or bullseye?

pi4, 2,4,8 gig?