Problems mit config.js

Hakupapa

Thx for helping. I have done this in this way (but with pm2 start mm.sh) and I allready became the Raspian Desktop :(

ostfilinchen

do you do this via ssh or directly on the raspi?

ostfilinchen

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?

Hakupapa

Ich have tested directly and with ssh. Ich will try to install pm one more time.

Hakupapa

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 │
└──────────┴────┴──────┴──────┴────────┴─────────┴────────┴─────┴──────────┴──────────┘
Use pm2 show <id|name> to get more details about an app

Jopyth

@Hakupapa The autostart should happen automatically. Once you start the mirror with pm2 restart and it is running, and then do pm2 save, pm2 should save the current status (which is, your mirror application is running), and try to restore it after a reboot, or even after the program crashes.

If it really does not do this, maybe try updating as described here?

Hakupapa

speciall thx my dear. I have reached the problem in another way. I wrote this command into the rc.local:
su pi -c ‘/home/pi/mm.sh &’
And now I have the MM after reboot. I am so happy :)