SOLVED MM on Ubuntu
pm2 stop 0 cd ~/MagicMirror npm start
@sdetweil Probably i was editing on the wrong files. Already re-edited on the correct ones. Thanks for your kind help
My MM2 is running well under Ubuntu 18.04. I’ve installed pm2 and that works as well to start/stop MM2. However, I’m not able to get pm2 to work when using crontab. My crontab script looks like this:
40 * * * * pm2 restart mm.sh
so I can restart MM2 at 40 minutes after each hour. I don’t really plan to restart MM2 that often, I just want to get this working. I don’t know my way around Linux well enough to figure out what’s wrong. Can anyone point me to solution or an approach to one? Thanks!
@dwburger what does crontab say when i tries to launch pm2?
Well…I learned something. I didn’t know about crontab logs and I found this command to try:
sudo grep CRON /var/log/syslog
When I did that I found this line on the end of the log:
Apr 24 10:40:01 dave-ubuntu CRON: (CRON) info (No MTA installed, discarding output)
I guess I need to install an MTA???
(CRON) info (No MTA installed, discarding output)
see the last answer here
but that doesn’t some why pm2 was not executed
note that you saved the pm2 config as user pi, and cron will run as root
Hmmm…installed the default MTA for Ubuntu 18 which fixed the error message in the logfile, but pm2 still didn’t restart the MM2. I’m afraid I don’t really understand your note about pi versus root cron running. I can “sudo crontab -e” if that’s a better idea. I will add, my Ubuntu is starting up with its GUI and then I’m opening a terminal window to start MM2 using “pm2 start mm.sh”.
@dwburger ok, but you don’t have to do ANY of this… if you used my install script, it set pm2 to autostart on boot
to fix if you DIDN’T use my install script, use my fixuppm2 script
read the readme.
if MM crashes, pm2 auto restarts
YOU don’t have to have any additional commands any where
I may have given you the wrong impression…I really don’t know my way around Linux/Ubuntu. However, I was able to run your fixuppm2 script and I now see what you mean about not having to do anything else. I’m getting the behavior I want. When I reboot my machine MM2 starts right up. I’m getting ready to make another MM2 on a mini PC running Ubuntu. This time, I’m going to use your install script!
OK…your script did a great job in getting a new MM installed onto another Ubuntu machine. There’s one odd behavior I’m noticing. When the MM2 first comes up after power-on or reboot, not all the modules get started. I have to press the key and the File -> Close. When the MM2 comes up again all is well. I’m wondering why that is??? Is it possible to place a delay in the config.js (or somewhere else) so each module has plenty of time to get started. Maybe there’s another solution to this behavior???
BTW…thanks for all your work on the installation scripts and the help you’ve provided!