👀 Views: 21 💬 Answers: 1 📅 Created: 2025-06-06

cron bash ubuntu

I'm a bit lost with I'm wondering if anyone has experience with I'm sure I'm missing something obvious here, but I've been trying to set up a cron job on my Ubuntu 22.04 server to run a custom Bash script every day at 3 AM, but it seems to be failing silently..... My script is located at `/home/user/scripts/backup.sh`. I added the following line to my crontab using `crontab -e`: ``` 0 3 * * * /home/user/scripts/backup.sh ``` However, when I check the logs, there's no indication that the script ran. I've added logging to the script to confirm execution: ```bash #!/bin/bash echo "Backup started at $(date)" >> /home/user/scripts/backup.log # Your backup commands here echo "Backup finished at $(date)" >> /home/user/scripts/backup.log ``` I also verified that the script has executable permissions with: ``` chmod +x /home/user/scripts/backup.sh ``` To troubleshoot further, I tried running the script manually, and it works perfectly. Additionally, I added a line to redirect both stdout and stderr in the crontab entry: ``` 0 3 * * * /home/user/scripts/backup.sh >> /home/user/scripts/cron.log 2>&1 ``` The `cron.log` file is still empty after the scheduled time. I've checked the system logs in `/var/log/syslog`, but there's no entry that indicates an scenario with cron. Is there something I'm missing in the cron configuration or the script itself? Could the environment variables be different when executing from cron compared to the terminal? I’m also aware of common pitfalls, such as PATH issues, but I ensured to specify the full paths for any commands used in the script. Any insights would be greatly appreciated! For context: I'm using Bash on Ubuntu. How would you solve this? Any ideas what could be causing this? My team is using Bash for this web app.