Read the statement by Michael Teeuw here.
Problems with starting pm2 start 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 ...etc
Change 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 ~/MagicMirror
Now i tried two things both gave same output
cd ~/home/pi/MagicMirror
and
cd /home/pi/MagicMirror
It 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 list
The "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 start
The 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:~ $