pm2 no longer launching MM

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

JMac

made the name change and started the install.
How long should the install take? After installing the helper tools it’s got about half way across the screen on updating packages and hasn’t moved for about 10 minutes, prior to that it was pretty quick. I tried to use the arrow keys on my keyboard to move up the terminal window a little and have ^[[A[ and ^[[C[ in the list, is this an issue?

sdetweil

@JMac depends on how much updating is required… there is a little => arrow moving at the bottom

JMac

yea that’s the little widget that wasn’t moving all that much for a good while, low and behold not 2 minutes after posting it starting carrying on. I tried to come and delete the pending post but you got in there pretty quick with the reply.

once this has run do I need to run your update code or will this be the most current version of MM?

sdetweil

@JMac this is the most current version… we update versions every 3 months…

if you try update and its the same as current, it just exists, after writing a log message to that effect

upgrade is a two step process… I don’t want to mess anything up…

so, running script with no parms, tests, and sees if there are any issues you need to know about… code that you changed that might be overwritten, …

and if you are happy (or resolved all the issues) , then adding the parm

apply

and running again will DO the upgrade

JMac

So I run the restore and some things have loaded up fine, so the default calendar and new headlines. everything else hasn’t.
I had an extended calendar module, and a PIR sensor to shut the screen off after 5 minutes.

The were some npm err and npm warn issues.

The PIR sensor was the most useful feature I had but I genuinely don’t think I could replicate how I got it working in the first place. It was a case of loads of misses then an eventual hit (plenty of luck).

DO I need to restart the pi for some of these changes to come into effect, or do I need to start messing with modules again, or do I need to do a further update to some modules? Is this the parm you mentioned?

sdetweil

@JMac no restart needed…

pir sensor has a rebuild problem , I’ve fixed it in a fork,

do this

cd ~/MagicMirror
npm install electron-rebuild
cd modules/MMM-PIRSensor (or whatever name it is exactly) 
../../node_modules/.bin/electron-rebuild

sdetweil

@JMac said in pm2 no longer launching MM:

I had an extended calendar module

what is the name of that module?

JMac

I had 2 versions of the PIR sensor module as one didn’t work, I don’t know if I ended up using the lite version or the other one.

some of the modules are saying they have old lockfiles (this is for the ISS module) or in the case of dad jokes it has an ERR! code eresolve.

Any ideas why the calendar extension hasn’t popped back up? It was calendar ext2 I was using I think.

sdetweil

@JMac said in pm2 no longer launching MM:

It was calendar ext2 I was using I think.

no idea… but one might look at the logs

sdetweil

@JMac ignore the lockfiles message…

modules shouldn’t ship lock files… (in my opinion)

JMac

Sam, scratch my last message, I was just about to turn everything off as it’s getting pretty late here.
used ctrl c to stop the MM so I could shutdown the pi and attack it another day.
pm2 restarted the MM and hey presto the mirror seems by and large back to normal.

I’m away with work for the next 3 days but will have a proper butchers (look) when I’m back home.

Thank you so much for both your patience and help.
I had genuine fears I’d have to start the entire build (modules bit) again and I was lucky I got it up and running like I did in the first place.

thank you!

JMac

Thought I’d drop in here rather than start a new thread, with this current setup pm2 stop mm in terminal no longer stops the mirror from relaunching after using shift+Q.

Any ideas how I stop the MM to allow me to shut the pi down safely for a brief time?

sdetweil

@JMac pm2’s JOB is to keep the apps it manages running. so if YOU stop it, or it crashes doesn’t matter , same job, restart the app.

to stop a managed app. you need to use the pm2 command

so, minimize the app, ctrl-m for mm
open a terminal window on the desktop, ctrl-alt-t, and type

pm2 status

and get the name or number of the app you are interested in and then do

pm2 stop x

where x is the name or number

most Linux commands have help built in by convention

pm2 --help

TDMPro2K

i followed this to get my starting again
https://forum.magicmirror.builders/topic/10840/problems-with-starting-pm2-start-mm-sh/7