Trying to update node.js fails

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

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?

thad

@sdetweil

It’s buster and I believe the pi4 is a 2GB model.

sdetweil

@thad do

uname - a

so I can see if legacy buster or real…

free -m

will tell u how much memory

thad

@sdetweil

pi@raspberrypi:~/MagicMirror $ uname -a
Linux raspberrypi 4.19.97-v7l+ #1294 SMP Thu Jan 30 13:21:14 GMT 2020 armv7l GNU/Linux
pi@raspberrypi:~/MagicMirror $ free -m
total used free shared buff/cache available
Mem: 1939 342 888 254 708 1261

sdetweil

@thad thx… original buster (4.19.97), legacy is 5.??? something)

and yes, 2gig memory

did u do any display config settings info in the /boot/confg.txt

i have gpu trouble on my jetson nano, but never on any pi so far…

thad

@sdetweil

I don’t recall making any edits to that file. Most items in that file are commented out. Here’s a list of what’s not commented out:

hdmi_force_hotplug=1
hdmi_group=1
hdmi_mode=97
dtparam=audio=on
[pi4]
dtoverlay=vc4-fkms-v3d
max_framebuffers=2
[all]
hdmi_force_hotplug=1

sdetweil

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

dtoverlay=vc4-fkms-v3d
max_framebuffers=2

same for my pi4 (4 gig)