Automating Tasks with Cron in Linux for DevOps

🚀 Day 6/100 – #100DaysOfDevOps | #KodeKloud ⏰ Automating Tasks with Cron Jobs (Linux) Today’s focus was on one of the most practical DevOps skills automation using cron jobs. Instead of doing repetitive tasks manually, we can schedule them to run automatically in the background. 📚 What I learned: ✅ Installing and enabling cron service (cronie) ✅ Managing cron daemon with systemctl ✅ Writing and editing cron jobs using crontab ✅ Understanding cron timing syntax (*/5 * * * *) ✅ Verifying scheduled jobs for specific users (like root) 💡 Why this matters: Automation is at the heart of DevOps. Cron jobs help ensure consistency, reduce human error, and save time — whether it’s backups, monitoring scripts, or maintenance tasks. 🛠️ Quick Example: Run a command every 5 minutes: */5 * * * * echo hello > /tmp/cron_text Tip: Always verify your cron jobs using crontab -l and check logs if something doesn’t work as expected. #DevOps #Linux #Automation #CloudComputing #SRE #LearningInPublic #TechJourney #100DaysOfCode #KodeKloud

Linux Cron Jobs (Automating Tasks Like a DevOps Engineer) In Linux, many tasks need to run automatically such as backups, scripts, log cleanup, updates. That’s where cron jobs come in. Cron allows you to schedule tasks to run at specific times or intervals. 🔹 What is Cron? Cron is a time-based job scheduler in Linux that runs commands automatically in the background. 🔹 Crontab Command To manage cron jobs: crontab -e This opens the cron configuration file for your user. 🔹 Cron Job Format * * * * * command | | | | | | | | | └── Day of week (0–7) | | | └──── Month (1–12) | | └────── Day of month (1–31) | └──────── Hour (0–23) └────────── Minute (0–59) 🔹 Examples Run a script every day at 2 AM: 0 2 * * * /home/user/backup.sh Run every 5 minutes: */5 * * * * /home/user/script.sh 🔹 List & Remove Cron Jobs crontab -l # List cron jobs crontab -r # Remove all cron jobs 🔹 Why Cron Matters in DevOps In real environments, cron is used for: ✔ Automated backups ✔ Log rotation ✔ Scheduled scripts ✔ System maintenance tasks Automation reduces manual work and improves reliability. #jobs #linux#unix#software#silicondawn #pavan

🚀 Day 9: Linux Internals for DevOps Engineers 👉 Shell Scripting (Automation Starts Here) Running commands manually is fine… But real engineers don’t repeat tasks. 👉 They automate them. Today I explored how simple commands can be turned into powerful automation using shell scripts. 📌 What I learned today: 🔹 Shell scripting helps automate repetitive tasks 🔹 `#!/bin/bash` tells the system how to execute scripts 🔹 Variables and conditions make scripts dynamic 🔹 Loops help in repeating tasks efficiently 💡 Real Scenario: You restart a service manually every day. What’s better? ❌ Manual work ✅ Write a script + schedule it with cron This is where DevOps actually starts becoming powerful. 🧠 Question for you: What’s one task you would automate first using shell scripting? 👇 Drop your answer! 🎯 Learning Goal: To reduce manual work and build automation mindset. 📅 Day 10 Tomorrow: Process Monitoring & System Performance (CPU, Memory, Load) Let’s keep going deeper 🚀 #DevOps #Linux #ShellScripting #Automation #SRE #CloudComputing #SoftwareEngineering #TechLearning #LearningInPublic #ITCareers #EngineeringMindset #CareerGrowth

🚀 Automating Log Collection with Jenkins | Day 73/100 – DevOps Journey Today’s task was about setting up centralized log collection using Jenkins automation — a real-world DevOps use case. 🔹 What I did: - Created Jenkins job copy-logs - Configured it to run every 5 minutes (cron job) - Automated copying of Apache logs (access & error) - Transferred logs from App Server → Storage Server - Verified logs were successfully collected 📂 Github: https://lnkd.in/gnBnU_cv #100DaysOfDevOps #DevOps #Jenkins #Automation #Logging #Linux #CloudNative #LearningInPublic #TechCareers #OpenToWork

If you want to become a DevOps engineer in 2026… Start with Linux. Here’s the exact roadmap: 1️⃣ Basics ✔ File system (ls, cd, pwd) ✔ Navigation ✔ File operations 2️⃣ Permissions ✔ chmod ✔ chown ✔ User & group management 3️⃣ Process Management ✔ ps, top ✔ kill ✔ Background jobs 4️⃣ Networking ✔ ping ✔ curl ✔ netstat / ss 5️⃣ Package Management ✔ apt / yum ✔ Install & manage software 6️⃣ Logs & Debugging ✔ tail -f ✔ journalctl ✔ dmesg 7️⃣ Scripting ✔ Bash basics ✔ Automate tasks Simple rule: 👉 Don’t skip steps 👉 Practice daily Most people jump to Docker/Kubernetes… And struggle. Because they skipped Linux. If you build strong Linux fundamentals, DevOps becomes easy. Save this roadmap. Follow me if you want real DevOps skills (not tutorial knowledge). #Linux #DevOps #CloudComputing #CareerGrowth #Roadmap

Devops Hands-on practice with KodeKloud Completed real world task ✨ Task: create a cron job for root user that runs every 5 minutes every day. ➡️ Install Cronie package "sudo yum install -y cronie" ➡️ start crond service "sudo systemctl start crond" ➡️ Check crond service status "systemctl status crond" ➡️ For adding crontab, open root user's crontab "sudo crontab -e" , add "*/5 * * * * /path of the script" and save the file ➡️ Verify the cron job added "sudo crontab -l" 💡 Cronie package contains "crond" daemon and "crontab" utility 👉 crond is the background daemon that runs continuously and checks the task list every minute to see if anything is scheduled to run and executes it. 👉 crontab (cron table) utility is a time-based job scheduler which serves two primary roles:  ⌛Command: The crontab command allows users to create, edit, view, and delete their task schedules. ⌛ File: "crontab file" is a simple text file that stores the list of commands (cron jobs) and the specific times they should run.  #Devops #Linux #DevopsEngineer #Learning #Kodekloud

🐧 Linux Troubleshooting Guide — The Skill That Turns Beginners into DevOps Engineers In DevOps, things will break. Servers will go down. Applications will fail. Logs will explode. And in those moments, one skill matters most: 👉 Linux troubleshooting A solid Linux troubleshooting guide doesn’t just give commands — it teaches you how to think under pressure. Here’s what every DevOps beginner should focus on 👇 🔹 Start with the Basics (Always) Before panicking, check: - Disk space ("df -h") - Memory usage ("free -m") - CPU load ("top", "htop") Most issues start here. 🔹 Logs Are Your Best Friend 📄 - "/var/log/syslog" - "/var/log/messages" - "journalctl" 👉 If you’re not reading logs, you’re guessing — not troubleshooting. 🔹 Process & Service Debugging - Check running processes ("ps", "top") - Restart services ("systemctl restart") - Verify service status ("systemctl status") 🔹 Networking Issues 🌐 - Is the port open? ("ss -tuln") - Can you reach the host? ("ping", "curl") - DNS working? ("nslookup", "dig") 🔹 Permission Problems 🔐 “Permission denied” is one of the most common errors. Understand: - "chmod" - "chown" - user/group access 🔹 Golden Troubleshooting Mindset 🧠 ✔ Don’t jump to conclusions ✔ Check step-by-step ✔ Identify root cause ✔ Fix — and verify --- 💡 DevOps Reality: Anyone can deploy a system. But engineers who can troubleshoot it… are the ones who grow fast. If you master Linux troubleshooting, you’ll never feel stuck — only challenged. 📌 Comment “your Linux Debug scenarios” with the community 🚀 #LinuxTroubleshooting #DevOpsBeginners #LinuxForDevOps #DevOpsEngineer #SystemAdministration #CloudComputing #TroubleshootingSkills #CloudEngineer #SRE #DevOpsJourney #LearningInPublic #TechCareers #Automation #LinuxAdmin #Infrastructure #ITOperations

🐧 Linux Troubleshooting Guide — The Skill That Turns Beginners into DevOps Engineers In DevOps, things will break. Servers will go down. Applications will fail. Logs will explode. And in those moments, one skill matters most: 👉 Linux troubleshooting A solid Linux troubleshooting guide doesn’t just give commands — it teaches you how to think under pressure. Here’s what every DevOps beginner should focus on 👇 🔹 Start with the Basics (Always) Before panicking, check: - Disk space ("df -h") - Memory usage ("free -m") - CPU load ("top", "htop") Most issues start here. 🔹 Logs Are Your Best Friend 📄 - "/var/log/syslog" - "/var/log/messages" - "journalctl" 👉 If you’re not reading logs, you’re guessing — not troubleshooting. 🔹 Process & Service Debugging - Check running processes ("ps", "top") - Restart services ("systemctl restart") - Verify service status ("systemctl status") 🔹 Networking Issues 🌐 - Is the port open? ("ss -tuln") - Can you reach the host? ("ping", "curl") - DNS working? ("nslookup", "dig") 🔹 Permission Problems 🔐 “Permission denied” is one of the most common errors. Understand: - "chmod" - "chown" - user/group access 🔹 Golden Troubleshooting Mindset 🧠 ✔ Don’t jump to conclusions ✔ Check step-by-step ✔ Identify root cause ✔ Fix — and verify --- 💡 DevOps Reality: Anyone can deploy a system. But engineers who can troubleshoot it… are the ones who grow fast. If you master Linux troubleshooting, you’ll never feel stuck — only challenged. 📌 Comment “your Linux Debug scenarios” with the community 🚀 #LinuxTroubleshooting #DevOpsBeginners #LinuxForDevOps #DevOpsEngineer #SystemAdministration #CloudComputing #TroubleshootingSkills #CloudEngineer #SRE #DevOpsJourney #LearningInPublic #TechCareers #Automation #LinuxAdmin #Infrastructure #ITOperations

🐧 Linux Troubleshooting Guide — The Skill That Turns Beginners into DevOps Engineers In DevOps, things will break. Servers will go down. Applications will fail. Logs will explode. And in those moments, one skill matters most: 👉 Linux troubleshooting A solid Linux troubleshooting guide doesn’t just give commands — it teaches you how to think under pressure. Here’s what every DevOps beginner should focus on 👇 🔹 Start with the Basics (Always) Before panicking, check: - Disk space ("df -h") - Memory usage ("free -m") - CPU load ("top", "htop") Most issues start here. 🔹 Logs Are Your Best Friend 📄 - "/var/log/syslog" - "/var/log/messages" - "journalctl" 👉 If you’re not reading logs, you’re guessing — not troubleshooting. 🔹 Process & Service Debugging - Check running processes ("ps", "top") - Restart services ("systemctl restart") - Verify service status ("systemctl status") 🔹 Networking Issues 🌐 - Is the port open? ("ss -tuln") - Can you reach the host? ("ping", "curl") - DNS working? ("nslookup", "dig") 🔹 Permission Problems 🔐 “Permission denied” is one of the most common errors. Understand: - "chmod" - "chown" - user/group access 🔹 Golden Troubleshooting Mindset 🧠 ✔ Don’t jump to conclusions ✔ Check step-by-step ✔ Identify root cause ✔ Fix — and verify --- 💡 DevOps Reality: Anyone can deploy a system. But engineers who can troubleshoot it… are the ones who grow fast. If you master Linux troubleshooting, you’ll never feel stuck — only challenged. 📌 Comment “your Linux Debug scenarios” with the community 🚀 #LinuxTroubleshooting #DevOpsBeginners #LinuxForDevOps #DevOpsEngineer #SystemAdministration #CloudComputing #TroubleshootingSkills #CloudEngineer #SRE #DevOpsJourney #LearningInPublic #TechCareers #Automation #LinuxAdmin #Infrastructure #ITOperations

DevOps Zero to Job-Ready – Day 7/180 | Putting It All Together Today felt different. For the past six days, I’ve been learning individual concepts. But today, everything started to connect. Here’s what the journey looked like so far: * Day 1 — Navigating a Linux system * Day 2 — File permissions and access control * Day 3 — Managing running processes * Day 4 — Extracting information using text processing * Day 5 — Writing basic Bash scripts * Day 6 — Connecting to remote servers using SSH What I understood today: These are not separate topics. They all come together in real DevOps work. Example: You connect to a remote server (SSH), check logs (text processing), identify a failing process, fix permissions if needed, and automate the solution using a script. That is a deployment. Six steps. Now the next step is clear: Write a script that does all six. Sharing today’s notes for reference. Also organized structured DevOps notes and scenarios on [www.engidock.com](https://www.engidock.com). #DevOps #Linux #Automation #LearningInPublic