Two Instances in PM2

shazglass

Hi everyone.
Please help. I have two instances of mm starting on boot up. I don’t know what I did wrong. When pi starts the cpu is showing movement but doesn’t boot into mm. I have to type is pi pm2 stop mm. Then pm2 stop MagicMirror to stop the cpu usage. I go into cd MagicMirror and type npm start and my mirror starts. Control q and quits. But this isn’t the right way to do it. How and in what directory do I go into to delete pm2 as I have two instances. Thnx everyone. Appreciate all help.

Mykle1

@shazglass

About 9 posts up from here are the directions on how to delete one instance on autostarting MM

shazglass

@mykle1 hi again😉. Yep. I did do that and that’s when both run in the background but none go to mirror mode. Then u suggested going into cd MagicMirror and running npm start and then it goes into mirror mode. I use control q to quit but I still have two instances. I need to delete both and reinstall but without losing my mirror and that’s what I don’t know how to do. I want it back to boot up going straight to mirror mode and then just control q to quit then pm2 stop MagicMirror and pm2 start MagicMirror. Right now I have mm and MagicMirror. I’m just at a loss☹️

bhepler

@shazglass All right, we’ll get you through it.

pm2 runs on Pi startup and will start your mirror process for you. There should be only one listing. If you ran the installation script and said “yes” to using pm2, there should be only one process called MagicMirror in pm2.

To remove the mm process from pm2, enter the following:

cd ~
pm2 stop all
pm2 delete mm
pm2 save
rm mm.sh
pm2 flush
pm2 start MagicMirror

At this point, your Magic Mirror interface should appear after a minute or so. You can press ctrl-q to exit the Magic Mirror interface, but pm2 should bring it back up in short order.

shazglass

@bhepler hi there.
Thank you for the instructions. I did exactly as you said. It has taken away the “mm” instance. I am left with only the MagicMirror one now. However. It will not boot Into mirror mode on start up, although I can see the CPU is being used, so I type pm2 stop MagicMirror and it shows that it has stopped. Only way I can get the mirror to show is by typing cd MagicMirror
Then in that directory I type npm start. It does a small load thing and then my mirror shows. How can I get it to how it should be without having to go into the mirror directory?
Thank you for your patience. Most appreciated!

bhepler

@shazglass - Hmm. I don’t know. It should be working normally at this point. Let’s try switching to the previous process. We’ll delete the one that the installer created, then add the one to your script.

First, we remove the existing process:

cd ~
pm2 delete MagicMirror
pm2 save

Then we use your mm.sh script that you had earlier.

pm2 flush
pm2 start mm.sh
pm2 save

At this point, your mirror should come up in about 30 seconds. If it does not, enter pm2 log mm and copy the results here. Be sure to use the forum markup tools to help format your log messages.

shazglass

@bhepler hithere
I did as per your instructions - except I dont know how to use the forum markup tool…so just copied and pasted.
I now dont have any instances running? I can only access my mirror if i go ino cd MagicMirror and then type npm install.

pi@raspberrypi:~ $ pm2 stop all
[PM2] Applying action stopProcessId on app [all](ids: 0)
[PM2] MagicMirror ✓
┌─────────────┬──────┬─────────┬───┬─────┬────────┐
│ Name │ mode │ status │ ↺ │ cpu │ memory │
├─────────────┼──────┼─────────┼───┼─────┼────────┤
│ MagicMirror │ fork │ stopped │ 6 │ 0% │ 0 B │
└─────────────┴──────┴─────────┴───┴─────┴────────┘
Use pm2 show <id|name> to get more details about an app
pi@raspberrypi:~ $ pm2 delete MagicMirror
[PM2] Applying action deleteProcessId on app [MagicMirror](ids: 0)
[PM2] MagicMirror ✓
┌──────┬──────┬────────┬───┬─────┬────────┐
│ Name │ mode │ status │ ↺ │ cpu │ memory │
└──────┴──────┴────────┴───┴─────┴────────┘
Use pm2 show <id|name> to get more details about an app
pi@raspberrypi:~ $ pm2 save
[PM2] Saving current process list…
[PM2] Nothing to save !!!
[PM2] In this case we keep old dump file. To clear dump file you can delete it manually !
pi@raspberrypi:~ $ pm2 flush
[PM2] Flushing /home/pi/.pm2/pm2.log
[PM2] Logs flushed
pi@raspberrypi:~ $ pm2 start mm.sh
[PM2][ERROR] script not found : /home/pi/mm.sh
script not found : /home/pi/mm.sh
┌──────┬──────┬────────┬───┬─────┬────────┐
│ Name │ mode │ status │ ↺ │ cpu │ memory │
└──────┴──────┴────────┴───┴─────┴────────┘
Use pm2 show <id|name> to get more details about an app
pi@raspberrypi:~ $ pm2 save
[PM2] Saving current process list…
[PM2] Nothing to save !!!
[PM2] In this case we keep old dump file. To clear dump file you can delete it manually !
pi@raspberrypi:~ $ pm2 start mm
[PM2][ERROR] script not found : /home/pi/mm
script not found : /home/pi/mm
┌──────┬──────┬────────┬───┬─────┬────────┐
│ Name │ mode │ status │ ↺ │ cpu │ memory │
└──────┴──────┴────────┴───┴─────┴────────┘
Use pm2 show <id|name> to get more details about an app
pi@raspberrypi:~ $ pm2 log mm
[TAILING] Tailing last 15 lines for [mm] process (change the value with --lines option)
[PM2][ERROR] No file to stream for app [mm], exiting.
pi@raspberrypi:~ $ pm2 log MagicMirror
[TAILING] Tailing last 15 lines for [MagicMirror] process (change the value with --lines option)
[PM2][ERROR] No file to stream for app [MagicMirror], exiting.
pi@raspberrypi:~ $

shazglass

I did find this in the cd MagicMirror???

bhepler

@shazglass - Ah. Okay, easy enough.

You’re missing the mm.sh script. I’m not sure how you had this registered in pm2 earlier, but we can fix it. We’ll use nano to create a new mm.sh file:

cd ~
nano mm.sh

This will give you a blank screen with the nano options at the bottom. Enter the following lines:

cd ~/MagicMirror
DISPLAY=:0 npm start

When you’re done, hit ctl+o to save the file and then ctl+x to exit nano. Then just like you did earlier, make your script executable by entering chmod +x mm.sh

Before we go any further, we need to test your script. From the command line, enter ./mm.sh
Your mirror should start after 30 seconds or so. Try this and report back with any errors and behaviors. Also, please use the markup commands when posting code and logs (follow this link for a quick tutorial).