How can I see history of the “at” command in AIX?
I'm experiencing a strange problem where occasionally the at command appears to not be running the command I've configured it to run.
For example:
at -t 201510071042
runsomescript
<Ctrl-D>
runsomescript does not run at 2015/10/07 10:42am, for some reason. Where can I see why at failed to run the command? I'm looking for some kind of log file for the at process.
Also, I am aware at sends mail. Having said that, I'm not getting an email either when at fails to execute the command.
If I run at -lov immediately after submitting the job, I see it in the queue to be ran at the appropriate time.
Additional info as of 2016-02-17
When the at command fails, mail contains the following "Cron Job Failure" message:
Cron: 0481-072 Cannot change to your home directory.
ksh aix at
bumped to the homepage by Community♦ 5 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
|
show 7 more comments
I'm experiencing a strange problem where occasionally the at command appears to not be running the command I've configured it to run.
For example:
at -t 201510071042
runsomescript
<Ctrl-D>
runsomescript does not run at 2015/10/07 10:42am, for some reason. Where can I see why at failed to run the command? I'm looking for some kind of log file for the at process.
Also, I am aware at sends mail. Having said that, I'm not getting an email either when at fails to execute the command.
If I run at -lov immediately after submitting the job, I see it in the queue to be ran at the appropriate time.
Additional info as of 2016-02-17
When the at command fails, mail contains the following "Cron Job Failure" message:
Cron: 0481-072 Cannot change to your home directory.
ksh aix at
bumped to the homepage by Community♦ 5 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
If you can re-test, check the return code from at ($?) as well as the output ofat -l(lower-case ELL) to see if your job made it to the queue. I assume that the contents of at.allow and at.deny are not changing in the interim?
– Jeff Schaller
Oct 9 '15 at 16:12
I suppose I should have added thatat -lovdoes show the job is in the queue, set for the appropriate time. I have no idea what is inat.alloworat.deny; presumably those are global settings? i.e. I'd need root to see them?
– Max Vernon
Oct 9 '15 at 16:20
the at.* files are in /var/adm/cron, which may require root privileges to see. If your jobs are being submitted, though, you're beyond that point. Next thing I wonder about is the shell that it's being run as -- bsh, csh, or ksh.
– Jeff Schaller
Oct 9 '15 at 16:31
KornShell is the shell.
– Max Vernon
Oct 9 '15 at 16:31
1
Problem Management Record (ticket / service request) with IBM - to request help with their software.
– Jeff Schaller
Nov 2 '15 at 20:54
|
show 7 more comments
I'm experiencing a strange problem where occasionally the at command appears to not be running the command I've configured it to run.
For example:
at -t 201510071042
runsomescript
<Ctrl-D>
runsomescript does not run at 2015/10/07 10:42am, for some reason. Where can I see why at failed to run the command? I'm looking for some kind of log file for the at process.
Also, I am aware at sends mail. Having said that, I'm not getting an email either when at fails to execute the command.
If I run at -lov immediately after submitting the job, I see it in the queue to be ran at the appropriate time.
Additional info as of 2016-02-17
When the at command fails, mail contains the following "Cron Job Failure" message:
Cron: 0481-072 Cannot change to your home directory.
ksh aix at
I'm experiencing a strange problem where occasionally the at command appears to not be running the command I've configured it to run.
For example:
at -t 201510071042
runsomescript
<Ctrl-D>
runsomescript does not run at 2015/10/07 10:42am, for some reason. Where can I see why at failed to run the command? I'm looking for some kind of log file for the at process.
Also, I am aware at sends mail. Having said that, I'm not getting an email either when at fails to execute the command.
If I run at -lov immediately after submitting the job, I see it in the queue to be ran at the appropriate time.
Additional info as of 2016-02-17
When the at command fails, mail contains the following "Cron Job Failure" message:
Cron: 0481-072 Cannot change to your home directory.
ksh aix at
ksh aix at
edited Feb 17 '16 at 22:36
Max Vernon
asked Oct 8 '15 at 17:45
Max VernonMax Vernon
324217
324217
bumped to the homepage by Community♦ 5 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 5 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
If you can re-test, check the return code from at ($?) as well as the output ofat -l(lower-case ELL) to see if your job made it to the queue. I assume that the contents of at.allow and at.deny are not changing in the interim?
– Jeff Schaller
Oct 9 '15 at 16:12
I suppose I should have added thatat -lovdoes show the job is in the queue, set for the appropriate time. I have no idea what is inat.alloworat.deny; presumably those are global settings? i.e. I'd need root to see them?
– Max Vernon
Oct 9 '15 at 16:20
the at.* files are in /var/adm/cron, which may require root privileges to see. If your jobs are being submitted, though, you're beyond that point. Next thing I wonder about is the shell that it's being run as -- bsh, csh, or ksh.
– Jeff Schaller
Oct 9 '15 at 16:31
KornShell is the shell.
– Max Vernon
Oct 9 '15 at 16:31
1
Problem Management Record (ticket / service request) with IBM - to request help with their software.
– Jeff Schaller
Nov 2 '15 at 20:54
|
show 7 more comments
If you can re-test, check the return code from at ($?) as well as the output ofat -l(lower-case ELL) to see if your job made it to the queue. I assume that the contents of at.allow and at.deny are not changing in the interim?
– Jeff Schaller
Oct 9 '15 at 16:12
I suppose I should have added thatat -lovdoes show the job is in the queue, set for the appropriate time. I have no idea what is inat.alloworat.deny; presumably those are global settings? i.e. I'd need root to see them?
– Max Vernon
Oct 9 '15 at 16:20
the at.* files are in /var/adm/cron, which may require root privileges to see. If your jobs are being submitted, though, you're beyond that point. Next thing I wonder about is the shell that it's being run as -- bsh, csh, or ksh.
– Jeff Schaller
Oct 9 '15 at 16:31
KornShell is the shell.
– Max Vernon
Oct 9 '15 at 16:31
1
Problem Management Record (ticket / service request) with IBM - to request help with their software.
– Jeff Schaller
Nov 2 '15 at 20:54
If you can re-test, check the return code from at ($?) as well as the output of
at -l (lower-case ELL) to see if your job made it to the queue. I assume that the contents of at.allow and at.deny are not changing in the interim?– Jeff Schaller
Oct 9 '15 at 16:12
If you can re-test, check the return code from at ($?) as well as the output of
at -l (lower-case ELL) to see if your job made it to the queue. I assume that the contents of at.allow and at.deny are not changing in the interim?– Jeff Schaller
Oct 9 '15 at 16:12
I suppose I should have added that
at -lov does show the job is in the queue, set for the appropriate time. I have no idea what is in at.allow or at.deny; presumably those are global settings? i.e. I'd need root to see them?– Max Vernon
Oct 9 '15 at 16:20
I suppose I should have added that
at -lov does show the job is in the queue, set for the appropriate time. I have no idea what is in at.allow or at.deny; presumably those are global settings? i.e. I'd need root to see them?– Max Vernon
Oct 9 '15 at 16:20
the at.* files are in /var/adm/cron, which may require root privileges to see. If your jobs are being submitted, though, you're beyond that point. Next thing I wonder about is the shell that it's being run as -- bsh, csh, or ksh.
– Jeff Schaller
Oct 9 '15 at 16:31
the at.* files are in /var/adm/cron, which may require root privileges to see. If your jobs are being submitted, though, you're beyond that point. Next thing I wonder about is the shell that it's being run as -- bsh, csh, or ksh.
– Jeff Schaller
Oct 9 '15 at 16:31
KornShell is the shell.
– Max Vernon
Oct 9 '15 at 16:31
KornShell is the shell.
– Max Vernon
Oct 9 '15 at 16:31
1
1
Problem Management Record (ticket / service request) with IBM - to request help with their software.
– Jeff Schaller
Nov 2 '15 at 20:54
Problem Management Record (ticket / service request) with IBM - to request help with their software.
– Jeff Schaller
Nov 2 '15 at 20:54
|
show 7 more comments
1 Answer
1
active
oldest
votes
man at
The at command mails you all output from standard output and standard error for the scheduled commands, unless you redirect that output.
So make sure you can send mail using sendmail, and make sure your script doesn't redirect errors (e.g. to /dev/null).
thanks, I should have mentioned in my question that I am awareatsends mail. Having said that, I'm not getting an email either whenatfails to execute the command.
– Max Vernon
Oct 8 '15 at 18:03
As the user that this at job ran under, did you check his local mailfile viamailcommand ?
– doktor5000
Oct 9 '15 at 14:43
yes,mailtypically has output from theatcommand; however not in these particular instances.
– Max Vernon
Oct 9 '15 at 16:33
I've added an error message into my question that I was able to see (finally) in mail.
– Max Vernon
Feb 17 '16 at 22:38
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f234820%2fhow-can-i-see-history-of-the-at-command-in-aix%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
man at
The at command mails you all output from standard output and standard error for the scheduled commands, unless you redirect that output.
So make sure you can send mail using sendmail, and make sure your script doesn't redirect errors (e.g. to /dev/null).
thanks, I should have mentioned in my question that I am awareatsends mail. Having said that, I'm not getting an email either whenatfails to execute the command.
– Max Vernon
Oct 8 '15 at 18:03
As the user that this at job ran under, did you check his local mailfile viamailcommand ?
– doktor5000
Oct 9 '15 at 14:43
yes,mailtypically has output from theatcommand; however not in these particular instances.
– Max Vernon
Oct 9 '15 at 16:33
I've added an error message into my question that I was able to see (finally) in mail.
– Max Vernon
Feb 17 '16 at 22:38
add a comment |
man at
The at command mails you all output from standard output and standard error for the scheduled commands, unless you redirect that output.
So make sure you can send mail using sendmail, and make sure your script doesn't redirect errors (e.g. to /dev/null).
thanks, I should have mentioned in my question that I am awareatsends mail. Having said that, I'm not getting an email either whenatfails to execute the command.
– Max Vernon
Oct 8 '15 at 18:03
As the user that this at job ran under, did you check his local mailfile viamailcommand ?
– doktor5000
Oct 9 '15 at 14:43
yes,mailtypically has output from theatcommand; however not in these particular instances.
– Max Vernon
Oct 9 '15 at 16:33
I've added an error message into my question that I was able to see (finally) in mail.
– Max Vernon
Feb 17 '16 at 22:38
add a comment |
man at
The at command mails you all output from standard output and standard error for the scheduled commands, unless you redirect that output.
So make sure you can send mail using sendmail, and make sure your script doesn't redirect errors (e.g. to /dev/null).
man at
The at command mails you all output from standard output and standard error for the scheduled commands, unless you redirect that output.
So make sure you can send mail using sendmail, and make sure your script doesn't redirect errors (e.g. to /dev/null).
answered Oct 8 '15 at 18:02
MikelMikel
39.3k1099125
39.3k1099125
thanks, I should have mentioned in my question that I am awareatsends mail. Having said that, I'm not getting an email either whenatfails to execute the command.
– Max Vernon
Oct 8 '15 at 18:03
As the user that this at job ran under, did you check his local mailfile viamailcommand ?
– doktor5000
Oct 9 '15 at 14:43
yes,mailtypically has output from theatcommand; however not in these particular instances.
– Max Vernon
Oct 9 '15 at 16:33
I've added an error message into my question that I was able to see (finally) in mail.
– Max Vernon
Feb 17 '16 at 22:38
add a comment |
thanks, I should have mentioned in my question that I am awareatsends mail. Having said that, I'm not getting an email either whenatfails to execute the command.
– Max Vernon
Oct 8 '15 at 18:03
As the user that this at job ran under, did you check his local mailfile viamailcommand ?
– doktor5000
Oct 9 '15 at 14:43
yes,mailtypically has output from theatcommand; however not in these particular instances.
– Max Vernon
Oct 9 '15 at 16:33
I've added an error message into my question that I was able to see (finally) in mail.
– Max Vernon
Feb 17 '16 at 22:38
thanks, I should have mentioned in my question that I am aware
at sends mail. Having said that, I'm not getting an email either when at fails to execute the command.– Max Vernon
Oct 8 '15 at 18:03
thanks, I should have mentioned in my question that I am aware
at sends mail. Having said that, I'm not getting an email either when at fails to execute the command.– Max Vernon
Oct 8 '15 at 18:03
As the user that this at job ran under, did you check his local mailfile via
mail command ?– doktor5000
Oct 9 '15 at 14:43
As the user that this at job ran under, did you check his local mailfile via
mail command ?– doktor5000
Oct 9 '15 at 14:43
yes,
mail typically has output from the at command; however not in these particular instances.– Max Vernon
Oct 9 '15 at 16:33
yes,
mail typically has output from the at command; however not in these particular instances.– Max Vernon
Oct 9 '15 at 16:33
I've added an error message into my question that I was able to see (finally) in mail.
– Max Vernon
Feb 17 '16 at 22:38
I've added an error message into my question that I was able to see (finally) in mail.
– Max Vernon
Feb 17 '16 at 22:38
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f234820%2fhow-can-i-see-history-of-the-at-command-in-aix%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
If you can re-test, check the return code from at ($?) as well as the output of
at -l(lower-case ELL) to see if your job made it to the queue. I assume that the contents of at.allow and at.deny are not changing in the interim?– Jeff Schaller
Oct 9 '15 at 16:12
I suppose I should have added that
at -lovdoes show the job is in the queue, set for the appropriate time. I have no idea what is inat.alloworat.deny; presumably those are global settings? i.e. I'd need root to see them?– Max Vernon
Oct 9 '15 at 16:20
the at.* files are in /var/adm/cron, which may require root privileges to see. If your jobs are being submitted, though, you're beyond that point. Next thing I wonder about is the shell that it's being run as -- bsh, csh, or ksh.
– Jeff Schaller
Oct 9 '15 at 16:31
KornShell is the shell.
– Max Vernon
Oct 9 '15 at 16:31
1
Problem Management Record (ticket / service request) with IBM - to request help with their software.
– Jeff Schaller
Nov 2 '15 at 20:54