Read the statement by Michael Teeuw here.
Problems mit config.js
-
U must start the MM with pm2 start mm and after this u can exec the command pm2 save
-
thx for the fast answer. :)
I have done this way (just forgot to write down). I got this information after saving:
pi@raspberrypi:~ $ pm2 save
[PM2] Saving current process list…
[PM2] Successfully saved in /home/pi/.pm2/dump.pm2
but after reeboting I just see the desktop -
do u run the commands with sudo? if not, can you test it?
-
I tested all commands with sudo at the beginning. The same problem. Is it maybe because of the command for reebot (sudo shutdown -h 0)?
-
i don’t think so.
please do this: pm2 start mm -> pm2 save -> pm2 Status -> pm2 save -> sudo reboot
-
Thx for helping. I have done this in this way (but with pm2 start mm.sh) and I allready became the Raspian Desktop :(
-
do you do this via ssh or directly on the raspi?
-
i have testet is myself via ssh.
pm2 stop mm -> pm2 delete mm -> pm2 save
then
sudo reboot
After the reboot there is no mm in the processlist. Now i do pm2 start mm.sh and pm2 status. At the End sudo reboot. When the raspi is up, the mirror starts without any Problems via pm2.
Is it possible, that anything goes wrong during the Installation of pm2?
-
Ich have tested directly and with ssh. Ich will try to install pm one more time.
-
I allready tried your way step by step. Everything worked but not the autostart of the mm. I just can start it manually with pm2 start mm.sh
Don´t know how to get a autostart for the mm.
Here is the information from the pm2 status:
┌──────────┬────┬──────┬──────┬────────┬─────────┬────────┬─────┬──────────┬──────────┐
│ App name │ id │ mode │ pid │ status │ restart │ uptime │ cpu │ mem │ watching │
├──────────┼────┼──────┼──────┼────────┼─────────┼────────┼─────┼──────────┼──────────┤
│ mm │ 0 │ fork │ 1123 │ online │ 0 │ 6s │ 0% │ 2.3 MB │ disabled │
└──────────┴────┴──────┴──────┴────────┴─────────┴────────┴─────┴──────────┴──────────┘
Usepm2 show <id|name>to get more details about an app
