Read the statement by Michael Teeuw here.
Cronjob
-
Good evening
I’d like to see my MagicMirror restart at a certain time each day. What should I enter in the crontrab? I have already tried x variants, but unfortunately it never worked.
27 17 * * * Command pm2 restart mmThe sudo reboot command works fine.
27 17 * * 5 sudo poweroff -
@CyruS1337 said in Cronjob:
Good evening
I’d like to see my MagicMirror restart at a certain time each day. What should I enter in the crontrab? I have already tried x variants, but unfortunately it never worked.
27 17 * * * Command pm2 restart mmThe sudo reboot command works fine.
27 17 * * 5 sudo poweroffDid you forget to write the full command? Try pm2 restart mm.sh
By the way: I prefere the online crontab generator (https://crontab-generator.org/). It’s very easy.
Regards Mike -
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 # -
This is my crontab:
# 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 0 6 * * * pm2 reload mmAre you running
crontab -ewith sudo? Because you have to run it as the user that runs MM (= most likely without sudo).Edit: @Zwirbel: For me it works using a cronjob. See what I wrote above and if you have questions regarding crontab, just ask again.
-
Juhuiiiii, finally it worked. Many Thanks
I have always used the command
sudo crontab -eand with this it did not work.It works fine with the
crontab -ecommand and then0 6 * * * pm2 reload mmOnce again, thank you very much for your help!!!
-
Glad it worked! :smiling_face_with_open_mouth:
-
@CyruS1337 said in Cronjob:
I have always used the command sudo crontab -e and with this it did not work.
Just to clarify.
Normally you are user pi:
$ who am ISo
crontab -ewill work for the pi user.
Usingsudo crontab -ewill change the crontab for the root user.Now how can you tell what is what ?
For the user pi:
$ sudo crontab -l -u pi
which is the same as
$ crontab -l
For the user root:
$ sudo crontab -l -u rootFurthermore, when you have activated the root crontab, then the command will run as root, in the root (/) directory.
In this casepm2 reloadcommand will search for themm.shscript under/and will not find it.
Whereas when activated the pi crontab, themm.shscript will be searched in the/home/pidirectory, where it should be, and it will work.Use
pm2 show mmto show the details on mm under pm2.
Then you will understand it better.Cron messages normally are directed to
/var/log/cron.log, but on my system it is not directed:$ grep cron /etc/rsyslog.conf #cron.* /var/log/cron.logTo see the cron messages, when not in cron.log:
$ tail -F /var/log/syslog | grep CRON[ On my system I see CRON messages for root, although I do not have root crontab entries. There is a crond running that runs alongside
$ systemctl status cron.]Have fun :-)
-
@evroom Many thanks for the detailed information.
As you can see, I always executed the command as sudo
sudo crontab -eSo I always executed the commands in the root directory. Which thus never led to success.
Thanks again for the help and the detailed listing.
Greeting
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login