Read the statement by Michael Teeuw here.
Cronjob
-
Thanks for the link, but it still does not work :(
# Edit this file to introduce tasks to be run by cron. # # Each task to run has to be defined through a single line # indicating with different fields when the task will be run # and what command to run for the task # # To define the time you can provide concrete values for # minute (m), hour (h), day of month (dom), month (mon), # and day of week (dow) or use '*' in these fields (for 'any').# # Notice that tasks will be started based on the cron's system # daemon's notion of time and timezones. # # Output of the crontab jobs (including errors) is sent through # email to the user the crontab file belongs to (unless redirected). # # For example, you can run a backup of all your user accounts # at 5 a.m every week with: # 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/ # # For more information see the manual pages of crontab(5) and cron(8) # # m h dom mon dow command # #MONTAG BIS SONNTAG UM 19:55 MAGICMIRROR RESTART 55 19 * * * pm2 restart mm.sh >/dev/null 2>&1 # #SAMSTAG REBOOT UM 12:00 MAGICMIRROR REBOOT 24 17 * * * sudo reboot # -
@CyruS1337 said in Cronjob:
Thanks for the link, but it still does not work :(
# Edit this file to introduce tasks to be run by cron. # # Each task to run has to be defined through a single line # indicating with different fields when the task will be run # and what command to run for the task # # To define the time you can provide concrete values for # minute (m), hour (h), day of month (dom), month (mon), # and day of week (dow) or use '*' in these fields (for 'any').# # Notice that tasks will be started based on the cron's system # daemon's notion of time and timezones. # # Output of the crontab jobs (including errors) is sent through # email to the user the crontab file belongs to (unless redirected). # # For example, you can run a backup of all your user accounts # at 5 a.m every week with: # 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/ # # For more information see the manual pages of crontab(5) and cron(8) # # m h dom mon dow command # #MONTAG BIS SONNTAG UM 19:55 MAGICMIRROR RESTART 55 19 * * * pm2 restart mm.sh >/dev/null 2>&1 # #SAMSTAG REBOOT UM 12:00 MAGICMIRROR REBOOT 24 17 * * * sudo reboot #Sounds strange. Maybe you first have to stop the pm2 process before restart, with pm2 stop mm.sh. Don’t forget to complete the line für den reboot am Samstag - sudo reboot >/dev/null 2>&1
regards Michael -
Why do you want to restart MM? Maybe
pm2 reload mmis the better option. -
@MadScientist said in Cronjob:
Why do you want to restart MM? Maybe pm2 reload mmis the better option.
Why … that’s actually a good question. The problem is that if I bring the screens for about 5-6 hours and then turn back on that no picture appears on the monitors. Therefore, I would like a regular restart of my MagicMirros.
-
Are you using the GoogleMapsTraffic module? In that case the
pm2 reload mmwill do. Or a simple Ctrl+R on the mirror. The cronjob should then look something like55 19 * * * pm2 reload mm(mine is0 6 * * * pm2 reload mmand it works flawlessly). -
@MadScientist said in Cronjob:
Are you using the GoogleMapsTraffic module? In that case the pm2 reload mm will do. Or a simple Ctrl+R on the mirror. The cronjob should then look something like 55 19 * * * pm2 reload mm (mine is 0 6 * * * pm2 reload mm and it works flawlessly).
Exactly, I use the modules GoogleMapsTraffi on these two monitors and these two monitors will not wake up after a while, if I turned off the monitors for several hours.
Then tonight I will try
pm2 reload mm. Unfortunately, the commandpm2 restart mmdid not work. Then I’m curious. -
Depennding on the other modules you’re using it might be good to reload MM more than once a day. In my case once is enough. Without reloading the screen turns black after more than one day. Depending on your setup it could be better to reload it twice or 4 times a day. In the end the reload is very quick and you won’t notice anything.
-
Perfect, did not know that I can reload the MagicMirror. Have always made a restart in the past. I’ll give feedback this evening on whether the cronjob works with the
pm2 reload mmcommand -
@MadScientist : Is there a way to automatically reload MM once or twice a day? I have similar problems with the Netatmo module, which doesn’t pick up new data in the morning (as my WLAN is turned off during the night). A reload fixes this, but I would rather have this automatically (e.g. at 06:00 in the morning for example).
Maybe a simple script would help, but I don’t know where to put it.
-
@MadScientist said in Cronjob:
55 19 * * * pm2 reload mm
The command works in the console
pm2 reload mmIf I add it in the cron job, it will not do any reload.
Here is the excerpt from the crontab
# Edit this file to introduce tasks to be run by cron. # # Each task to run has to be defined through a single line # indicating with different fields when the task will be run # and what command to run for the task # # To define the time you can provide concrete values for # minute (m), hour (h), day of month (dom), month (mon), # and day of week (dow) or use '*' in these fields (for 'any').# # Notice that tasks will be started based on the cron's system # daemon's notion of time and timezones. # # Output of the crontab jobs (including errors) is sent through # email to the user the crontab file belongs to (unless redirected). # # For example, you can run a backup of all your user accounts # at 5 a.m every week with: # 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/ # # For more information see the manual pages of crontab(5) and cron(8) # # m h dom mon dow command # #MONTAG BIS SONNTAG UM 17:02 MAGICMIRROR RELOAD 02 17 * * * pm2 reload mm #
