pm2 no longer launching MM

[JMac]

@sdetweil yes ran all three lines you posted.

[JMac]

@sdetweil Sorry to double reply, I ran the last 2 again and they worked ok, right up until the very end of the npm install when I got an ERR_SOCKET_TIMEOUT.
I’m assuming this is a wifi strength issue as the position of this mirror means it struggles at times.

[sdetweil]

@JMac yeh, everything is very network dependent…

I ended up installing a mesh wifi system to be able to put an access point near where my hall mirror is

[JMac]

@sdetweil Managed to run it a second time and everything seems happy, however, the pm2 start mm.sh still isn’t launching the MM itself.
Is there any other way to launch the mirror, or a way to check why it’s suddenly lost function (it was always happy launching and stopping the MM) ?

[sdetweil]

@JMac so, I would do this

pm2 stop all

cd ~/MagicMirror
npm start

does it run correctly?

you MAY have to update pm2, its just an app too…
depending on how old it was

see the pm2 --help
for the command to do its update

[JMac]

@sdetweil when I run npm start from the MM folder I get:

magicmirror@2.23.0 start
DISPLAY=“${DISPLAY:=:0}” ./node_modules/.bin/electron js/electron.js

sh: 1: ./node_modules/.bin/electron: not found

[sdetweil]

@JMac ok, do this

what device is this on? pi3?

cd ~/MagicMirror
rm -rf node_modules/electron
npm install electron@22.3.4
npm start

please advise

[JMac]

@sdetweil this is on a 3b+.
when running npm install I’m now back to an error for ENOTEMPTY for node_modules/ansi-escapes.
it says directory not empty.
I think it wants it renamed no_modules/.ansi-escapes-TiTd7xs1

[sdetweil]

@JMac ok, try this

rm -rf node_modules/electron
rm package-lock.json 
npm install electron@22.3.4
npm start

[JMac]

@sdetweil after running the npm install now getting a different ENOTEMPTY for nodes_modules/basic-auth.
Same issue of directory not empty

[sdetweil]

@JMac weird, this makes no sense

[JMac]

@sdetweil I’m away with work until Friday but obviously want to try and get to the bottom of this.
I’ll likely end up moving the mirror to somewhere way closer to the WiFi router.
Will this stay open until the end of the week?

Out of curiosity when launching via pm2 should it (in the little box that pops up in terminal) mention fork?

[sdetweil]

@JMac this will stay open til u close it…

yes, that is the linux term for starting an independent process

[sdetweil]

@JMac I would rename the existing mm folder
and then run install again, use my script
https://github.com/sdetweil/MagicMirror_scripts

to help move the modules and config, I’d use my backup/restore scripts
https://github.com/sdetweil/MagicMirror-backup-restore

backup before rename, restore after reinstall

[JMac]

may sound like a daft question but how do I rename the magicmirror folder? I’ve run your back up (hopefully).

[sdetweil]

@JMac in Linux the rename command is mv

cd ~
mv MagicMirror newname

[JMac]

sorry to sound extremely daft, but what should I be renaming it? Is there a preferred name or one which makes most sense?

[sdetweil]

@JMac any name that works for you, you are just making room for the installer which is hard coded to use MagicMirror, and will abort if that folder is already created

[JMac]

once a new name is picked can it later be changed back to magicmirror just to keep everything standard?

Also, when you say,
mv magicmirror newname, I’m guessing the newname bit is actually what I want to call it, or do I put the new name after?
I’ve got a terrible feeling I’ll have to start the whole thing again which I definitely won’t look forward to.

[sdetweil]

@JMac new name is whatever u want to call it

it looks like there is a mess, and you are reinstalling.

my backup and restore scripts can capture your config and modules and let you out then back onto a new MagicMirror

but, by saving the folder anything not handled can be recovered