@pat59 it’s 2 dashes

—lines

You could have seen this in the help from pm2

@pat59

Ok,

Because you are using pm2 makes getting log a little more interesting

Do

pm2 stop all
pm2 flush
pm2 start MagicMirror

Wait til MagicMirror comes up and modules show loading
Then do

pm2 logs —lines=100. 

The n look thru the listing and see if there are any errors reported

Also can you post the configuration from config.js for those two modules
Note the calendar module url needs to be mangled, xxx part so it doesn’t expose the full url

@plainbroke pi0w

Did you use my install script?

Electron is not available for armv6l

You need to install another browser, Firefox, midori, push
Then launch browser over server mode

My script does all the setup
You have to set an env variable for which ever browser

If you are installed but still need updated, there is a separate script for that

@pat59 is it working? after the pm2 restart?

@pat59 im 74… so its never too late

try this

pm2 stop mm
pm2 restart MagicMirror

@pat59 said in update package list:

I used restart RPII used restart RPI

I don’t know what that means in reality under the covers

so, you need to delete one of the apps… unless you intentionally have two instances.

they show online, and no restarts, which is weird

@pat59 you have two instances… pick one… delete the other

pm2 --help

will give you the command options

what is the remote control function to stop it?

@pat59

Did you stop it manually ctrl-q
Yesterday after we finished testing?

pm2 status

Is anything listed as running?
If not then do this

ps -ef| grep MagicMirror 

You should only get one line of output

@pat59 and now

npm start 

@pat59 so, you already have an instance running, probably under pm2

when I said stop MM I meant in whatever way running…

pm2’s JOB is to start and KEEP MM running… no matter what
you ctrl-Q
pm2 says, oops, app crashed, restart…

so, you have to use the pm2 commands to tell it what to do

pm2 status

will show the managed apps, one line per
you can control the app, by using the name or number of the app in a row

pm2 stop 0
pm2 stop MagicMirror 

could both be for the same app

once stopped, THEN you can go to the MM folder and do the npm start to see the possible errors easier…

once you fix the errors, you can stop the temp MM with ctrl-q (as you started it manually)
and then tell pm2 to manage it again

pm2 start 0/MagicMirror