Fix a VPS cron failure in layers: verify the crontab belongs to the intended user, validate the five-field schedule and command, remove assumptions about an interactive shell, test the exact command as the cron user, confirm the cron service is running, inspect captured output and service logs, then check system-directory rules and missed-run behavior. If systemd timers are also present, identify replacements or duplicates before adding another schedule.
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
Start by identifying which scheduler and user should run the job
A cron entry is not global. Debian’s crontab manual states: “Each user has their own crontab, and commands in any given crontab will be executed as the user who owns it.” That ownership determines the account, permissions, home directory, environment, and available credentials for the command.
As an Amazon Associate I earn from qualifying purchases.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Inspect the application account’s crontab
Log in as the account that is supposed to own the job and run:
crontab -lIf the job is deliberately root-owned, inspect root’s separate crontab:
#1 Best Overall
- BLUE LIGHT BLOCKING GLASSES: Our blue light glasses for women boast UV400 protection, blocking harmful blue rays from computer screens. With these bluelight glasses women, you can enjoy gaming, reading, or watching TV with no worries of eye strain.
- EYE RELIEF: Our blue light glasses are engineered to reduce blurry vision or strain caused by prolonged screen time. These womens blue light glasses aid in better sleep by preventing blue light from disrupting your natural sleep cycle, helping you fall asleep faster and enjoy a more restful night's sleep, making them the perfect christmas present.
- COMFORTABLE: Crafted from durable material, our trendy blue light glasses for woman or blue light glasses men ensure long-lasting comfort. The high-transmittance lenses accessories, gamer gifts for men, help keep your eyes relaxed. Perfect stocking stuffers, gifts for gamers men, christmas gifts for men, halloween costumes.
- LIGHTWEIGHT: These clear blue light glasses feature a lightweight frame, meaning they’ll stay comfy for long-term wear. Perfect as blue blockers glasses for women or mens blue light glasses, these non-prescription fake glasses for men can be worn throughout the day. The blue light blocking glasses women feature polycarbonate HD lenses, which are anti-reflective and restore true color.
- WORRY-FREE PURCHASE: If you experience any issues, our support team is ready to assist you quickly. These are the perfect costume glasses for cosplay dressing up.
sudo crontab -lDo not assume that editing root’s crontab installs a job for an application account. Conversely, an entry installed for an application account will not gain root’s permissions merely because the VPS administrator created it. Write down the intended owner before changing anything.
Distinguish user crontabs from system files
Files such as /etc/cron.d and the /etc/cron.* directories follow system-wide conventions rather than the per-user format. A system entry normally includes an explicit user field, so copying a line from a user crontab into /etc/cron.d without adding that field can prevent it from running or make it run under the wrong account.
Validate the schedule before debugging the command
A cron line has five schedule fields followed by the command: minute, hour, day of month, month, and day of week. Check every field and the timezone in which the VPS interprets it. A line intended for local midnight may run at a different wall-clock time if the server’s timezone is not the one you assumed.
Check each field and the command boundary
- Confirm that all five schedule fields are present and in the intended order.
- Check ranges, lists, steps, and wildcards for accidental edits.
- Look for an inline comment or shell quoting mistake that changes where the command starts.
- Make sure the command is on the same line as its schedule and that a wrapped line was not pasted into the crontab.
- Verify that the schedule is actually frequent enough for your test. A daily job can appear broken if you wait only a few minutes.
Use a temporary, unambiguous test schedule
When the production schedule is complex, temporarily replace it with a short interval that is safe for the command, such as:
*/5 * * * * /absolute/path/to/test-commandUse this only while diagnosing and restore the intended schedule afterward. A test command should write a timestamp to a diagnostic file or log so that you can distinguish “cron never launched it” from “the command launched and failed.”
Make the command independent of your SSH shell
“It works in SSH” proves only that it works inside your interactive login environment. Cron starts a non-interactive process with a smaller, different environment. Relative paths, shell startup files, aliases, functions, virtual-environment activation, and variables exported during login may not exist.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Use absolute executable and file paths
Call the interpreter or utility by its full path, for example:
Rank #2
- WINDEX GAMING WIPES: effortlessly clean all your gaming gear and gaming electronics in one easy step with our new Windex Gaming Wipes
- AMMONIA FREE: our ammonia-free formula is safe to use on all of your favorite gaming equipment like consoles, headsets, controllers, screens, keyboards, and more
- PRE-MOISTENED WIPES: each wipe instantly removes dust, dirt, and stubborn smudges and fingerprints leaving a streak-free shine
- ANTI-STATIC: great for cleaning and wiping down your gaming gear and electronics leaving behind no visible residue
- COMPACT RESEALABLE PACKAGE: store your pack of Windex Gaming Wipes anywhere in your home for whenever a quick and easy wipedown is needed
/usr/bin/php /srv/app/bin/maintenance.php
/usr/bin/curl https://example.invalid/healthThe examples illustrate the form to use; substitute paths that exist on your VPS. Do not rely on an interactive shell finding php or curl through a login-only PATH.
Declare the environment the job needs
Set a deliberate PATH and any required variables in the crontab or, preferably, in a wrapper script that you can test independently. Set an explicit working directory rather than assuming the process starts in your project directory. One pattern is:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
APP_ENV=production
*/5 * * * * cd /srv/app && /usr/bin/php /srv/app/bin/maintenance.phpKeep secrets out of a world-readable crontab. If the command needs credentials, arrange permissions for the owning account and load them through a protected configuration mechanism that the account can read.
Account for shell differences
Cron may invoke a different shell from the one you use interactively. Avoid aliases and shell functions. If the command depends on shell syntax, put that syntax in a tested wrapper with an explicit interpreter and call the wrapper by its absolute path. This also gives you one place to set the working directory, environment, and logging.
Reproduce the failure as the cron user
Run the exact command manually as the account shown by the crontab. For an application account named APPUSER:
sudo -u APPUSER -- /absolute/path/to/commandUse the same absolute paths, arguments, working directory, and environment that the cron entry uses. A successful run as your own login account does not rule out permission, home-directory, or credential failures for APPUSER.
Interpret what the manual test tells you
- If the command fails under
APPUSER, fix the command, its dependencies, or file permissions before investigating the scheduler. - If it succeeds under
APPUSERbut not from cron, compare the cron environment, working directory, schedule, and output redirection with the manual invocation. - If it produces no visible output, add temporary logging before deciding that it did not run.
Check that every input file, output directory, socket, executable, and configuration file is accessible to the owning account. A root-only path can make a job appear silent when the scheduler itself is healthy.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #3
- Ergonomic & Adjustable Design: Fight "text neck" and improve your posture. Designed for comfort, it offers an adjustable height (7.1in-8.5in) (1.4in adjustable range) and angle (5°-85°) Please note: cell phone stand is only 9 inches tall—the length of a standard pencil
- Without blocking subtitles Perfect for office desk Tiktok Face Time Zoom video—this is the ultimate kitchen desk essential for phones! Perfect viewing experience while reducing neck back strain, A must-have for gamers streamers desk, and anyone who values both style and support!
- Sleek & Stable Design fits Otterbox Case: Say goodbye to bent cables, tangles, and tip-overs! LISEN’s stylish adjustable desk phone holder features a built-in charging hole and smart cable management, keeping your phone secure and your workspace clutter-free cool gadgets for men
- ANTI-SLIP DESIGN free hands: The under 10.00 items easy gadgets back and the bottom of this kitchen essentials for women are fully covered by anti-skid silicone, which LISEN stand up desk decor can provide maximum protection device from any scratches and slides
- Your Perfect Viewing Companion:If your product arrives damaged or breaks within 365 days, reach out to LISEN for a quick and hassle-free solution. Struggling with assembly, like tightening the screw? We’ve got your back! Your experience matters to us. (Product including: phone Holder stand*1, screw*1, hexagon screwdriver*1, specification*1)
Confirm that cron is running and enabled at boot
The crontab is only a set of instructions; a service must read and execute those instructions. Service names differ by distribution.
Debian and Ubuntu-style systems
systemctl status cronIf the service is stopped or not enabled, enable the appropriate service at boot and start it according to your operating system’s service-management policy. After changing service state, rerun a short diagnostic schedule and inspect its output.
Red Hat-style systems
systemctl status crondRed Hat’s administration guidance uses crond for this check. A common mistake is checking cron on a system whose service is named crond, or enabling one name while the installed service uses the other.
Check after a reboot
If jobs stopped after a VPS reboot, first verify the service is enabled and active rather than assuming the crontab was deleted. Then confirm that the intended user’s crontab still contains the entry. Service state and crontab ownership are independent checks.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Capture stdout and stderr before guessing
During diagnosis, append both output streams to a dedicated log:
*/5 * * * * /absolute/path/to/command >> /var/log/myjob.log 2>&1Choose a log path that the cron user can write, or create the file and directory with permissions that allow that account to append safely. A root-owned log directory can cause the redirection itself to fail before the command starts.
Inspect service and system logs
On systems using the systemd journal, inspect the relevant unit:
Rank #4
- Easy Installation: Our gaming lights have been designed to enhance your entertainment experience. Simply position the led light bar next to your TV or game console to create a game room environment with ease. They come with USB power and a 60 inch cord for direct mounting and mobility
- Audio Syncing & Extensive Mode: The built-in high-sensitivity music sensor allows you to sync the TV led lights to your favorite music. Lights react and move to the beat of music, film and game audio, creating an incredible immersive sound and light experience – and all without the need for an additional hub. You can choose from 64+ patterns, including strobe, illusion, jump, energy, gradient, running, chasing, fluttering mode etc. Each mode can be applied to different scenes
- 64+ Chasing IC+RGB & W Effect: The independent control design of IC+RGB and white all-in-one multifunctional rgbw led bar lights monitor backlight allows you to easily switch the led lights for desk between IC+RGB and white to enjoy a variety of lighting effects, you can choose white lighting mode with high brightness for better illumination when working, etc. Choose IC+RGB lighting mode when you need to create an entertaining atmosphere for the light show, 16 million colours of Color changing rgb light bar let you dance to the beat and create a dynamic party atmosphere
- Dynamic and Dimmable Lights: 1%-full brightness free brightness adjustment gives you the flexibility to adjust dimmable led light bar for room decorations or a variety of occasions
- USB Powered: USB light bars for room can be powered by powernank, usb charger, TV, Monitor, laptop PC mainframe, making behind TV led lighting bar easy to install in any location.TV led lights are powered by the TV usb interface / PC mainframe, can be turned on/off synchronously with TV / PC
journalctl -u cron
journalctl -u crondUse the command matching the service name on your VPS. Also inspect the relevant syslog facility when your distribution records cron activity there. Look for evidence of the scheduler parsing the line, launching the process, rejecting a file, or reporting an exit failure.
Separate scheduler errors from application errors
- No scheduler entry and no application log usually points to the wrong crontab, an inactive service, an invalid system file, or a schedule that has not reached its due time.
- A scheduler entry followed by a nonzero application result points to the command, environment, permissions, or dependencies.
- Output showing a missing executable, directory, variable, or permission identifies a shell-environment or account problem rather than a timing problem.
Remove or rotate temporary verbose logging after the cause is fixed so a frequent job does not fill the VPS disk.
Check /etc/cron.d and /etc/cron.* rules
System cron directories add validation rules that do not apply in exactly the same way to a user crontab.
Validate the line format and user field
An entry in /etc/cron.d needs the schedule, an explicit user, and the command. Confirm that the user field names the intended account and that the command is not accidentally shifted into that field. Inspect the file for stray characters, malformed lines, and an absent final newline if your distribution’s parser requires a conventional text file.
Inspect ownership, modes, and executable status
Check the file’s ownership and permissions, and verify the executable bit where the directory’s mechanism requires it. The account running the command must also be able to read the script and write its destination files. Correcting a script’s mode does not fix an unreadable parent directory, so check the complete path.
Use accepted filenames
Debian’s systemd-cron documentation notes that generated cron filenames must use ASCII letters, digits, underscores, or dashes. A filename containing other characters can be ignored even when its contents look correct. Rename it to an accepted name and then recheck the service logs.
Understand the periodic directories
The hourly, daily, weekly, and monthly directories are processed through run-parts. Red Hat documents this mechanism for the corresponding /etc/cron.* directories. A script placed there must satisfy the directory’s filename and execution conventions; a valid script in the wrong directory will run on the wrong cadence, while a rejected filename may never run.
Best Value
- Compatible with Wide Screens - To ensure compatibility with the dual monitor mount, your each monitor must meet three conditions at the same time: First, computer screens size range: 13 to 32 inches. Second, screen weight range: 4.4 to 19.8 lbs. Third, the back of the monitor screen must have VESA mounting holes with a pitch of 75x75mm or 100x100mm.
- Regarding the compatibility with desks - Your desk must meet three conditions at the same time: First, desk material: Only wooden desks are recommended, plastic or glass desks cannot be used. Second, desk thickness range: 0.59" - 3.54". Third, the bottom of the desk should not have any cross beams or panels, as this will interfere with installation. We recommend carefully checking that your desk and monitors meets all above conditions before purchasing.
- Dual C-Clamp Hold - Worried your dual monitors might wobble or slip? Our upgraded base uses a larger platform plus a dual C-clamp structure to lock the dual monitor arm firmly to your desk. Each arm safely keeps your screens steady while you type, click and game—no shaking, no sliding, just a clean and secure setup you can trust every day. It also provides Grommet Mounting installation choice, both options ensure stable and secure fixation for your 0.59" - 3.54" desk.
- Full-Motion Adjustment For Comfortable View - Pull the screen closer when you’re deep in a spreadsheet, push it back to watch videos, or rotate to portrait for coding — moving everything smoothly with just one hand. The monitor stand offers +85°/-50° tilt, ±90° swivel and 360° rotation. Raise your monitor up to 15.75″ to support a healthy sitting posture. Whether you’re working from home, gaming through the night, or switching between video calls and documents, getting the screens to your natural line of sight helps relieve neck, shoulder and back strain so you can stay focused longer with less fatigue.
- Keep Your Desk Organized: By lifting both screens off the desktop, this dual monitor stand opens up valuable space for your keyboard, notebook, docking station or a simple, clutter-free work area. Built-in cable management guides wires along the arms, keeping cords out of sight and out of the way. Enjoy a tidy, modern workstation that looks as good as it feels to use.
Decide how missed runs should behave after downtime
Standard cron does not automatically catch up a job whose scheduled minute passed while the VPS was powered off. If the machine was offline at 02:00, bringing it back at 02:20 does not, by itself, make ordinary cron replay the 02:00 invocation.
Free tools Windows power users keep installed
One-click scans. No signup required.
Choose a catch-up strategy deliberately
- Keep ordinary cron when skipping a missed run is acceptable.
- Use a suitable persistent systemd timer when a missed invocation should be triggered after the host returns.
- Use an anacron-style strategy for workloads designed around periodic completion rather than an exact minute.
Do not add anacron or a systemd-cron implementation beside an existing cron entry without checking behavior. Debian warns that duplicate implementations can execute a job more than once.
Distinguish downtime from a stopped service
A missed run caused by a powered-off VPS is different from a cron service that was stopped while the VPS remained online. Logs and service status tell you which case you have. Changing to a persistent timer will not repair a malformed command or an inactive cron service.
Look for systemd timers that replace or duplicate cron
Some Debian installations using systemd-cron translate crontabs into generated .timer and .service units. Native timers with matching names can override legacy jobs. This can explain why editing a crontab appears to have no effect or why a command runs twice.
List every timer, including inactive ones
systemctl list-timers --allFind timers whose schedule or service name matches the cron job. Inspect the generated units and read their journal entries before creating another schedule. The objective is to identify the single effective owner of the job, not to make both schedulers active.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsResolve replacement and duplication
- If a generated timer is the active implementation, change the source configuration that generates it rather than adding an unrelated cron line.
- If a native timer intentionally replaces a legacy entry, remove or disable the old schedule after verifying the replacement.
- If two units launch the same command, choose one and disable the other; otherwise a successful repair can create duplicate processing, duplicate notifications, or conflicting file writes.
Cron versus a systemd timer: choose one scheduler per job
| Decision factor | Cron | Systemd timer |
|---|---|---|
| Observability | Usually relies on cron and syslog records plus the job’s own redirected output. | Provides unit status and journal entries that can be inspected with systemd tools. |
| Missed-run behavior | Normal schedules do not catch up after the VPS is powered off. | Can provide persistent catch-up when configured as a persistent timer. |
| Dependency ordering | Offers the schedule and command but fewer native service-dependency relationships. | Integrates with service units and system startup ordering. |
| Environment isolation | Requires explicit paths, variables, and working-directory handling in the entry or wrapper. | Encourages explicit unit properties and a separate service definition. |
| Portability | Remains the more portable simple scheduler across Linux distributions. | Is a natural fit on a VPS already managed by systemd. |
| Duplicate risk | Can overlap with anacron or generated timers if both are left enabled. | Can replace a legacy cron job, but an old cron entry must be removed or disabled. |
Choose based on the job’s requirements, not on a belief that one scheduler can repair every failure. For a simple portable command, cron is sufficient when its environment and service state are correct. For journal-based observability, dependency ordering, or persistent handling of downtime, a systemd timer may be easier to operate on a systemd VPS.
An end-to-end repair procedure
Use this sequence when you need a repeatable fix rather than isolated guesses.
- Identify the intended account and inspect its crontab with
crontab -l; usesudo crontab -lonly when the job is intentionally root-owned. - Confirm the five schedule fields, timezone assumption, command boundary, quoting, and any inline comment.
- Replace relative executable, script, configuration, and output paths with absolute paths. Set
PATH, required variables, and an explicit working directory. - Run the exact command as the cron account with
sudo -u APPUSER -- /absolute/path/to/command. - Check
systemctl status cronon Debian/Ubuntu-style systems orsystemctl status crondon Red Hat-style systems. Enable the correct service at boot when necessary. - Add temporary stdout and stderr redirection to a writable diagnostic log, then inspect that log and the matching journal or syslog records.
- If the entry is in a system directory, verify its user field, ownership, mode, executable status where applicable, and filename characters.
- Run
systemctl list-timers --alland inspect generated units for a replacement or duplicate systemd schedule. - If the VPS was offline at the scheduled minute, decide whether ordinary cron’s skip behavior is acceptable or whether one persistent timer or anacron-style strategy should own the job.
- Restore the intended schedule, remove temporary diagnostics, and observe at least one successful run in the final configuration.
Common symptoms and the most likely layer
| Symptom | First layer to inspect | Reason |
|---|---|---|
| The job is absent from the expected list | Crontab owner and file location | You may be viewing another user’s crontab or editing a system file with different conventions. |
| It works in SSH but fails from cron | Absolute paths, variables, shell, and working directory | The interactive environment is not the cron environment. |
| No application output exists | Temporary redirection and scheduler logs | The command may not have started, or its output may be going somewhere you are not checking. |
| Every job stopped after reboot | Service status and boot enablement | The cron service may not be active even though the crontab remains intact. |
A job never runs from /etc/cron.d |
User field, permissions, and filename characters | System-directory parsing and filename rules can reject an otherwise plausible file. |
| A job runs twice | Generated and native systemd timers plus cron/anacron overlap | Two schedulers may own the same command. |
| A run is missing after shutdown | Downtime policy | Normal cron does not replay a missed minute. |
What a successful fix looks like
The final configuration has one clearly identified scheduler and one intended owning account. Its command uses absolute paths, declares the environment it needs, starts in a known directory, and writes diagnostic output somewhere that account can access. The relevant cron or timer service is active and enabled as appropriate for the VPS. A journal or log entry confirms an actual invocation, and the application’s exit result is successful. If downtime catch-up matters, that behavior is provided by the single selected scheduler rather than by overlapping cron, anacron, and systemd entries.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Recommended Free Tools
