Problems with starting pm2 start mm.sh

madoXX

@CyruS1337 said in Problems with starting pm2 start mm.sh:

Did you also follow this point:

Starting PM2 on boat
To make sure PM2 can do it’s job when (re) booting your operating system, it needs to be started on boot. Luckily, PM2 has a handy helper for this.

pm2 startup
PM2 wants to show you a command you need to execute.

Thanks for your reply. For the moment i want to know why it doesn’t even start, when i try to start it manually.

Moreover, here the content of the file mm.sh (saved in /home/pi)

cd ~/MagicMirror
DISPLAY=:0 npm start

sdetweil

@madoXX said in Problems with starting pm2 start mm.sh:

cd ~/MagicMirror

change that 1st line to be

cd /home/pi/MagicMirror

pm2 is running under root at the time of startup

madoXX

@sdetweil said in Problems with starting pm2 start mm.sh:

@madoXX said in Problems with starting pm2 start mm.sh:

cd ~/MagicMirror

change that 1st line to be
cd /home/pi/MagicMirror
pm2 is running under root at the time of startup

changed it, saved and made a reboot. nothing changed.

when i write pm2 start i receive the following message:

[PM2][ERROR] File ecosystem.config.js not found
┌──────────┬────┬─────────┬──────┬─────┬────────┬─────────┬────────┬─────┬──────────┬──────┬──────────┐
│ App name │ id │ version │ mode │ pid │ status │ restart │ uptime │ cpu │ mem │ user │ watching │
├──────────┼────┼─────────┼──────┼─────┼────────┼─────────┼────────┼─────┼──────────┼──────┼──────────┤
│ mm │ 0 │ N/A │ fork │ 838 │ online │ 0 │ 3m │ 0% │ 2.4 MB │ pi │ disabled │
└──────────┴────┴─────────┴──────┴─────┴────────┴─────────┴────────┴─────┴──────────┴──────┴──────────┘
Use pm2 show <id|name> to get more details about an app

sdetweil

@madoXX said in Problems with starting pm2 start mm.sh:

File ecosystem.config.js not found

ok, seems pm2 is not setup right

1st make sure script works
is it executable?
chmod +x mm.sh

/home/pi/mm.sh &
(and stop it)
then 

pm2 remove 0
pm2 startup
   this will return a command u need to execute (cut/paste)
pm2 start /home/pi/mm.sh
pm2 save

then

pm2 list

nothing running

pm2 start mm

should start ok

reboot

madoXX

@sdetweil said in Problems with starting pm2 start mm.sh:

1st make sure script works
is it executable?
chmod +x mm.sh

ok, done

@sdetweil said in Problems with starting pm2 start mm.sh:

/home/pi/mm.sh &
(and stop it)
then

don’t get this…
should i enter
pm2 stop /home/pi/mm.sh &

@sdetweil said in Problems with starting pm2 start mm.sh:

pm2 remove 0

when i enter this, this appears:
[PM2] Command not found

usage: pm2 [options]

pm2 -h, --help all available commands and options
pm2 examples display pm2 usage examples
pm2 -h help on a specific command

Access pm2 files in ~/.pm2
[1]+ Fertig pm2 stop /home/pi/mm.sh

@sdetweil said in Problems with starting pm2 start mm.sh:

pm2 startup
ok, had to enter this one:
sudo env PATH=$PATH:/usr/bin /usr/lib/node_modules/pm2/bin/pm2 startup systemd -u pi --hp /home/pi

After the enter this one appeared:
[PM2] Init System found: systemd
Platform systemd
Template
[Unit]
Description=PM2 process manager
Documentation=https://pm2.keymetrics.io/
After=network.target

[Service]
Type=forking
User=pi
LimitNOFILE=infinity
LimitNPROC=infinity
LimitCORE=infinity
Environment=PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games:/usr/bin:/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
Environment=PM2_HOME=/home/pi/.pm2
PIDFile=/home/pi/.pm2/pm2.pid
Restart=on-failure

ExecStart=/usr/lib/node_modules/pm2/bin/pm2 resurrect
ExecReload=/usr/lib/node_modules/pm2/bin/pm2 reload all
ExecStop=/usr/lib/node_modules/pm2/bin/pm2 kill

[Install]
WantedBy=multi-user.target

Target path
/etc/systemd/system/pm2-pi.service
Command list
[ ‘systemctl enable pm2-pi’ ]
[PM2] Writing init configuration in /etc/systemd/system/pm2-pi.service
[PM2] Making script booting at startup…

Executing: systemctl enable pm2-pi…

[PM2] [v] Command successfully executed.
±--------------------------------------+
[PM2] Freeze a process list on reboot via:
$ pm2 save

[PM2] Remove init script via:
$ pm2 unstartup systemd

@sdetweil said in Problems with starting pm2 start mm.sh:

pm2 start /home/pi/mm.sh

here this is the result:
[PM2] Applying action restartProcessId on app [mm](ids: 0)
[PM2] mm ✓
[PM2] Process successfully started
┌──────────┬────┬─────────┬──────┬───────┬────────┬─────────┬────────┬─────┬──────────┬──────┬──────────┐
│ App name │ id │ version │ mode │ pid │ status │ restart │ uptime │ cpu │ mem │ user │ watching │
├──────────┼────┼─────────┼──────┼───────┼────────┼─────────┼────────┼─────┼──────────┼──────┼──────────┤
│ mm │ 0 │ N/A │ fork │ 15797 │ online │ 0 │ 0s │ 0% │ 2.4 MB │ pi │ disabled │
└──────────┴────┴─────────┴──────┴───────┴────────┴─────────┴────────┴─────┴──────────┴──────┴──────────┘
Use pm2 show <id|name> to get more details about an app

@sdetweil said in Problems with starting pm2 start mm.sh:

pm2 save

Result
[PM2] Saving current process list…
[PM2] Successfully saved in /home/pi/.pm2/dump.pm2

@sdetweil said in Problems with starting pm2 start mm.sh:

pm2 list

nothing running

Yes there is the mm running:
┌──────────┬────┬─────────┬──────┬───────┬────────┬─────────┬────────┬─────┬──────────┬──────┬──────────┐
│ App name │ id │ version │ mode │ pid │ status │ restart │ uptime │ cpu │ mem │ user │ watching │
├──────────┼────┼─────────┼──────┼───────┼────────┼─────────┼────────┼─────┼──────────┼──────┼──────────┤
│ mm │ 0 │ N/A │ fork │ 15797 │ online │ 0 │ 103s │ 0% │ 2.4 MB │ pi │ disabled │
└──────────┴────┴─────────┴──────┴───────┴────────┴─────────┴────────┴─────┴──────────┴──────┴──────────┘
Use pm2 show <id|name> to get more details about an app

@sdetweil said in Problems with starting pm2 start mm.sh:

pm2 start mm

should start ok

perhaps no…
[PM2] Applying action restartProcessId on app [mm](ids: 0)
[PM2] mm ✓
[PM2] Process successfully started
┌──────────┬────┬─────────┬──────┬───────┬────────┬─────────┬────────┬─────┬──────────┬──────┬──────────┐
│ App name │ id │ version │ mode │ pid │ status │ restart │ uptime │ cpu │ mem │ user │ watching │
├──────────┼────┼─────────┼──────┼───────┼────────┼─────────┼────────┼─────┼──────────┼──────┼──────────┤
│ mm │ 0 │ N/A │ fork │ 16995 │ online │ 1 │ 0s │ 0% │ 2.5 MB │ pi │ disabled │
└──────────┴────┴─────────┴──────┴───────┴────────┴─────────┴────────┴─────┴──────────┴──────┴──────────┘
Use pm2 show <id|name> to get more details about an app

Thanks anyway for your help!

sdetweil

@madoXX does it restart on boot?

pm2 remove 0
should have been
pm2 delete 0

and yep, needed a stop after the pm2 save

madoXX

@sdetweil said in Problems with starting pm2 start mm.sh:

@madoXX does it restart on boot?

pm2 remove 0
should have been
pm2 delete 0

and 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 list

nothing 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

madoXX

OK command back…

after a few reboots now everything is starting fine.
A big thanks to the community here!
Very helpfull people here!

Gomalley

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?

sdetweil

@Gomalley pm2 runs a script,
installers/mm.sh

It should read

cd /home/pi/MagicMirror
...etc

Change it if not.

Then

pm2 restart 0