I have a backup that I run as a scheduled task every night, then clear out every weekday morning after I check it.
Problem is my server's memory is almost maxed out (can't upgrade with my current host, and still researching others), and the weekend backups are leaving me with no memory by Mon morning.
Is there a way to have Windows Task Scheduler run 6 days a week instead of 7?
if you select weekly you can select which days your task shall run.
Related
I am using an Azure batch account to run sqlpackage.exe in order to move databases from a server to another. A task that has started 6 days ago has suddenly been restarted and started from the beginning after 4 days of running (extremely large databases). The task run uninterruptedly up until then and should have continued to run for about 1-2 days.
The PowerShell script that contains all the logic handles all the exceptions that could occur during the execution. Also, the retry count for the task was set to 0 in case it fails.
Unfortunately, I did not have diagnostics settings configured and I could only look at the metrics and there was a short period when there wasn't any node.
What can be the causes for this behavior? Restarting while the node is still running
Thanks
Unfortunately, there is no way to give a definitive answer to this question. You will need to dig into the compute node (interactively log in) and check system logs to give you details on why the node restarted. There is no guarantee that a compute node will have 100% uptime as there may be hardware faults or other service interruptions.
In general, it's best practice to have long running tasks checkpoint progress combined with a retry policy. Programs that can reload state can pick up at the time of the checkpoint when the Batch service automatically reschedules the task execution. Please see the Batch best practices guide for more information.
I am trying to gather all the info from our scheduled tasks by powershell.
I would like to get not only the name, action and the times but also the full schedule of when its going to run.
E.g Mon 12:00, Tue 13:00, Wed 14:00.
I have run a number of scripts and have the times that the tasks run but not what days they are set to.
Does anyone know how to get what days a task is set to?
Last night was "fall back" time change for most locations in the US. I woke up this morning to find dozens of job failure notifications. Almost all of them though were incorrect: the jobs showed as having completed normally, yet Rundeck sent a failure notification for it.
Interestingly, this happened in two completely separate Rundeck installations (v2.10.8-1 and v3.1.2-20190927). The commonality is that they're both on CentOS 7 (separate servers). They're both using MariaDB, although different versions of MariaDB.
The failure emails for the jobs that finished successfully showed a negative time in the "Scheduled after" line:
#1,811,391
by admin Scheduled after 59m at 1:19 AM
• Scheduled after -33s - View Output »
• Download Output
Execution
User: admin
Time: 59m
Started: in 59m 2019-11-03 01:19:01.0
Finished: 1s ago Sun Nov 03 01:19:28 EDT 2019
Executions Success rate Average duration
100% -45s
That job actually ran in 27s at 01:19 EDT (the first 1am hour, it is now EST). Looking at the email headers, I believe I got the message at 1:19 EST, an hour after the job ran.
So that would seem to imply to me that it's just a notification problem (somehow).
But there were a couple of jobs that were following other job executions that failed as well, apparently because the successfully finished job returned a RC 2. I'm not sure what to make of this.
We've been running Rundeck for a few years now, this is the first I remember seeing this problem. Of course my memory may be faulty--maybe we did see it previously, only there were fewer jobs affected or some such.
The fact that it impacted two different versions of Rundeck on two different servers implies either it's a fundamental issue with Rundeck that's been around for a while or it is something else in the operating system that's somehow causing problems for Rundeck. (Although time change isn't new, so that would seem to be somewhat surprising too.)
Any thoughts about what might have gone on (and how to prevent it next year, short of the obvious run on UTC) would be appreciated.
You can define specific Timezone in Rundeck, check this and this.
I have a stage with two jobs (build and deploy) which is giving me a lot of trouble for the past 2 days.
Yesterday it started to fail about 1 every 4 times I run the stage. The stage is cancelled by itself. First I thought it might be a problem with my code but if I rerun the same execution it failed some of the times.
Today although, I haven't manage to complete a single run (I tried like 20 times in the last 3 hours). Some of the times the build job is cancelled, some others the deploy job.
Anybody facing the same problem? I cannot find where the issue is coming from...
Thanks!
I recently integrated Hangfire in my project and it is working fine. I am having some long running jobs that are actually taking 4-5 days to complete, So what I am trying to do is to Run these jobs on every 8th day means if it triggers on 1st Feb then 9th Feb then 17 Feb like this.
Can any one help me in creating the Cron Expression for this, as CronExpressionBuilder class doesn't have such function to create Cron Expression.
Issue Resolved.
I changed my apporach and using below mentioned cron expression..
RecurringJob.AddOrUpdate(() => Console.Write("Recurring"), "0 10 */8 * *");
And is working like a charm.