Cron jobs not running!!!
zahinabrer5
FREEOP

7 months ago

Hello,
So I tried setting up Cron on my new laptop (EndeavourOS with kernel 6.14.5) and none of my Cron jobs are running :/

here's my crontab (output of running crontab -e):

SHELL=/bin/bash
MAILTO=loaf@example.com
PATH=/bin:/sbin/:/usr/bin:/usr/sbin:/usr/local/bin/:/usr/local/sbin:$HOME/bin

# Warning Alarms for Salah -- Plays a rooster alarm SFX when there's ~20 minutes left until Jama'at at local masjid.
# For now, it must be manually updated, unfortunately :(
# Fajr
55 03 * * * ffplay -v 0 -nodisp -autoexit /home/loaf/SFX/rooster.mp3 2>&1 >> $HOME/.adhan
# Dhuhr
55 12 * * * ffplay -v 0 -nodisp -autoexit /home/loaf/SFX/rooster.mp3 2>&1 >> $HOME/.adhan
# Asr
10 17 * * * ffplay -v 0 -nodisp -autoexit /home/loaf/SFX/rooster.mp3 2>&1 >> $HOME/.adhan
# Maghrib
20 10 * * * ffplay -v 0 -nodisp -autoexit /home/loaf/SFX/rooster.mp3 2>&1 >> $HOME/.adhan
# Isha
22 10 * * * ffplay -v 0 -nodisp -autoexit /home/loaf/SFX/rooster.mp3 2>&1 >> $HOME/.adhan

@weekly rsync-backup 2>&1 >> $HOME/.rsync-backup

0 22 * * 5 notify-send -t 10000 -i /home/loaf/ricing/icons/update.png "Update Time" "Oi... update yo system naow..."

*/10 * * * * /usr/local/bin/mailsync

And yes, I've already made sure to run sudo systemctl enable cronie.service and sudo systemctl start cronie.service beforehand…

perhaps I need to restart my system, but I doubt that is the case here… (I tried it and it still wouldn't run my debug job that echoes "Bruh" every minute)

Solved

0 Replies

zahinabrer5
FREEOP

7 months ago

N/A


zahinabrer5
FREEOP

7 months ago

here's the output of systemctl status cronie.service:

 cronie.service - Command Scheduler
     Loaded: loaded (/usr/lib/systemd/system/cronie.service; enabled; preset: disabled)
     Active: active (running) since Fri 2025-05-16 22:08:39 EDT; 5min ago
 Invocation: 4a8bcadbeed34b74a0c515756634fa0e
   Main PID: 2679419 (crond)
      Tasks: 1 (limit: 37999)
     Memory: 940K (peak: 3.7M)
        CPU: 115ms
     CGroup: /system.slice/cronie.service
             └─2679419 /usr/sbin/crond -n

May 16 22:13:00 host crond[2687342]: pam_unix(crond:session): session opened for user>
May 16 22:13:00 host CROND[2687344]: (loaf) CMD (/usr/local/bin/mailsync)
May 16 22:13:00 host CROND[2687342]: (loaf) CMDOUT (/bin/bash: line 1: /usr/local/bi>
May 16 22:13:00 host CROND[2687342]: (loaf) CMDEND (/usr/local/bin/mailsync)
May 16 22:13:00 host CROND[2687342]: pam_unix(crond:session): session closed for user>
May 16 22:14:00 host crond[2689316]: pam_unix(crond:session): session opened for user>
May 16 22:14:00 host CROND[2689318]: (loaf) CMD (/usr/local/bin/mailsync)
May 16 22:14:00 host CROND[2689316]: (loaf) CMDOUT (/bin/bash: line 1: /usr/local/bi>
May 16 22:14:00 host CROND[2689316]: (loaf) CMDEND (/usr/local/bin/mailsync)
May 16 22:14:00 host CROND[2689316]: pam_unix(crond:session): session closed for user>

Thanks in advance for the help :)


zahinabrer5
FREEOP

7 months ago

I've tried running most of the commands with root (by appending sudo at the beginning) and they didn't work… so it might be because cron is trying to run the commands as root…


zahinabrer5
FREEOP

7 months ago

tried this, still not working: https://serverfault.com/a/352837


medim
MODERATOR

7 months ago

er.. uhm…


medim
MODERATOR

7 months ago

I don't think this is railway related


medim
MODERATOR

7 months ago

This is a community-driven help forum for issues on the railway platform



zahinabrer5
FREEOP

7 months ago

Oh I thought I could use this place for any linux related issues since some1 pointed me here when i said my cron was borked


zahinabrer5
FREEOP

7 months ago

maybe they thought i was talking abt a cron job in railway deployment


zahinabrer5
FREEOP

7 months ago

anyways, my very first solution with crontab -e was actually working… I was appending the output at the end of the file for debugging and i just noticed that it's been appending it correctly this whole time LOL
stll dont know whether my ffplay alarms will start at the right time tho… gotta wait for those (fixed it by adding an env var at the top of the crontab)


medim
MODERATOR

7 months ago

!s


Status changed to Solved medim 7 months ago


Loading...