Read the statement by Michael Teeuw here.
Trying to update node.js fails
-
@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: )
-
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.
-
@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.
-
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!
-
@bugsounet thx… added to upgrade, had for install
-
@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 .
-
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:
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 | /home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGTERM
PM2 | pid=1386 msg=process killed
PM2 | Exited peacefully
0|MagicMFor some reason this keeps cycling. At the moment I’ve started MM using the run-start.sh script and it appears to be stable.
-
@thad is there a cron job running? maybe killing pm2
-
I don’t have any cron jobs running. A crontab -l says there’s nothing for user pi.
-
@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 dosudo npm uninstall pm2
then run my fixuppm2.sh script again … it will redo all the setup