Read the statement by Michael Teeuw here.
Problems with starting pm2 start mm.sh
-
@sdetweil said in Problems with starting pm2 start mm.sh:
@madoXX does it restart on boot?
pm2 remove 0
should have been
pm2 delete 0and yep, needed a stop after the pm2 save
no, the boot menu from the magic mirror appears (booting up), no error but it goes straight to the desktop.
something strang here
@sdetweil said in Problems with starting pm2 start mm.sh:
then
pm2 listnothing running
In fact the themm.sh is running caus i startet it above
@sdetweil said in Problems with starting pm2 start mm.sh:
pm2 start /home/pi/mm.sh
-
OK command back…
after a few reboots now everything is starting fine.
A big thanks to the community here!
Very helpfull people here! -
I’m actually having thus EXACT problem and it is very frusterating. Im having a little trouble reading all of the instructions to fix it. Did you get yours fixed? If so exactly what did you do to fix it?
-
@Gomalley pm2 runs a script,
installers/mm.shIt should read
cd /home/pi/MagicMirror ...etcChange it if not.
Then
pm2 restart 0 -
I tried it but I do not think that it worked. My code before I touched it read
cd ~/MagicMirrorNow i tried two things both gave same output
cd ~/home/pi/MagicMirrorand
cd /home/pi/MagicMirrorIt now says
[PM2] Spawning PM2 daemon with pm2_home=/home/pi/.pm2
[PM2] PM2 Successfully daemonized
Use --update-env to update environment variables
[PM2] Applying action restartProcessId on app [0](ids: [ ‘0’ ])
[PM2] [ERROR] Process 0 not foundIn my mm.sh the file currently reads this:
cd /home/pi/MagicMirror
DISPLAY=:0 npm start -
And I tried restarting the pi and the “Booting up” MagicMirror2 showed but it never actually loaded.
-
-
@madoXX
just did a fresh install of my magicmirror, because the sd card went corrupt.
during the install procedure it somehwere asked me if i want to autostart MagicMirror.
after that it started automatically after booting into the desktop first.
When trying to use pm2, it shows me the process is already running, but it’s name is MagicMirror , not mm.
MagicMirror version 2.8.0 -
@Detto65 yes, the install script uses a json file to configure the pm2 process
-
When i do
pm2 listThe "name, id, mode, status, cpu, and memory chart shows up. It is all in blue.
Below it, it says “use ‘pm2 show <id/name>~ to get more details about an app.’”When i type in
pm2 startThe same chart above displays along with a message saying
[PM2] [ERROR] File ecosystem.config.js is not foundWhat does this mean?
-
I am having the same problem: I did what was mentioned above and after the reboot it stll did not start automaticly. Running “pm2 list” after the reboot shows mm.sh is not runnning.
permitted by applicable law. Last login: Sun Jul 28 20:48:49 2019 pi@magicmirror:~ $ pm2 list [PM2] Spawning PM2 daemon with pm2_home=/home/pi/.pm2 [PM2] PM2 Successfully daemonized ┌──────────┬────┬─────────┬──────┬─────┬────────┬─────────┬────────┬─────┬─────┬──────┬──────────┐ │ App name │ id │ version │ mode │ pid │ status │ restart │ uptime │ cpu │ mem │ user │ watching │ └──────────┴────┴─────────┴──────┴─────┴────────┴─────────┴────────┴─────┴─────┴──────┴──────────┘ Use `pm2 show <id|name>` to get more details about an app pi@magicmirror:~ $ pm2 start installers/mm.sh [PM2][ERROR] script not found : /home/pi/installers/mm.sh script not found : /home/pi/installers/mm.sh ┌──────────┬────┬─────────┬──────┬─────┬────────┬─────────┬────────┬─────┬─────┬──────┬──────────┐ │ App name │ id │ version │ mode │ pid │ status │ restart │ uptime │ cpu │ mem │ user │ watching │ └──────────┴────┴─────────┴──────┴─────┴────────┴─────────┴────────┴─────┴─────┴──────┴──────────┘ Use `pm2 show <id|name>` to get more details about an app pi@magicmirror:~ $ pm2 start mm.sh [PM2] Starting /home/pi/mm.sh in fork_mode (1 instance) [PM2] Done. ┌──────────┬────┬─────────┬──────┬─────┬────────┬─────────┬────────┬─────┬──────────┬──────┬──────────┐ │ App name │ id │ version │ mode │ pid │ status │ restart │ uptime │ cpu │ mem │ user │ watching │ ├──────────┼────┼─────────┼──────┼─────┼────────┼─────────┼────────┼─────┼──────────┼──────┼──────────┤ │ mm │ 0 │ N/A │ fork │ 718 │ online │ 0 │ 0s │ 0% │ 2.6 MB │ pi │ disabled │ └──────────┴────┴─────────┴──────┴─────┴────────┴─────────┴────────┴─────┴──────────┴──────┴──────────┘ Use `pm2 show <id|name>` to get more details about an app pi@magicmirror:~ $ pm2 save [PM2] Saving current process list... [PM2] Successfully saved in /home/pi/.pm2/dump.pm2 pi@magicmirror:~ $ pm2 list ┌──────────┬────┬─────────┬──────┬─────┬────────┬─────────┬────────┬─────┬──────────┬──────┬──────────┐ │ App name │ id │ version │ mode │ pid │ status │ restart │ uptime │ cpu │ mem │ user │ watching │ ├──────────┼────┼─────────┼──────┼─────┼────────┼─────────┼────────┼─────┼──────────┼──────┼──────────┤ │ mm │ 0 │ N/A │ fork │ 718 │ online │ 0 │ 44s │ 0% │ 2.6 MB │ pi │ disabled │ └──────────┴────┴─────────┴──────┴─────┴────────┴─────────┴────────┴─────┴──────────┴──────┴──────────┘ Use `pm2 show <id|name>` to get more details about an app pi@magicmirror:~ $ pm2 save [PM2] Saving current process list... [PM2] Successfully saved in /home/pi/.pm2/dump.pm2 pi@magicmirror:~ $ sudo reboot Connection to 192.168.138.28 closed by remote host. Connection to 192.168.138.28 closed.pi@magicmirror:~ $ cat mm.sh cd /home/pi/MagicMirror DISPLAY=:0 npm start pi@magicmirror:~ $ ls -lha mm.sh -rwxr-xr-x 1 pi pi 45 Jul 28 20:14 mm.sh pi@magicmirror:~ $ -
@Raksasas should be executing those while in the MagicMirror folder
-
Looking over the “Auto Start” page I do not see where it states that the pm2 commands are to be run while inside the MagicMirror folder.
With you stating that it seems to be saying that the “mm.sh” script needs to be ran from inside the “MagicMirror” too. Again the “Auto Start” page shows that it was created inside the ‘home’ (~) folder. So one would think/presume it can be ran from inside the “home” folder also.
Either way I will give it a go.
-
-
@Raksasas it was the
pm2 start installers/mm.shThat needed to be done from the MagicMirror folder.
Cause I ‘ASSUMED’ if u were working on mm, you would always be in that folder.
installers folder is in mm, not in user home
-
Part 1:
@sdetweilJust tried the
pm2 start installers/mm.sh pm2 saveFrom within the “MagicMirror” folder and no change. MagicMirror starts and at reboot it does not automaticly start
See below for my fix
Part 2:
@mumblebaj
This seems possible. So i re-ransudo npm install -g pm2 pm2 startupAfter running “pm2 startup” this time I noticed the following:
To setup the Startup Script, copy/paste the following command: sudo env PATH=$PATH:/usr/bin /usr/lib/node_modules/pm2/bin/pm2 startup systemd -u pi --hp /home/piSo I ran that and followed with the “pm2 start mm.sh” and “pm2 save”. Well now it is auto starting on reboot.
-
@Raksasas great news!
-
@Raksasas Exellent. Great it is working now.
-
T TDMPro2K referenced this topic on
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login