Ever since at-3.1.8-64_FC3 was installed on my machine, at jobs are failing. For each at job that is supposed to run, two messages are placed in /var/log/cron:
Mar 2 14:00:16 waterloo atd[20772]: Authentication service cannot retrieve authentication info. Mar 2 14:00:16 waterloo atd[20771]: Authentication service cannot retrieve authentication info.
This message is coming from PAM, but I don't know how to determine which authentication service is mis-configured or broken.
I tried removing /etc/pam.d/atd (it is a new file in this release of the at RPM), but get the messages in /var/log/cron:
Mar 2 14:02:39 waterloo atd[21063]: User account has expired Mar 2 14:02:39 waterloo atd[21062]: User account has expired
I looked in Bugzilla, but there are not *any* bugs registered to the at component for Fedora Core fc3.
Any pointers or help in trying to determine the cause would be much appreciated.
On Wed, 2 Mar 2005, David L. Crow wrote:
This message is coming from PAM, but I don't know how to determine which authentication service is mis-configured or broken.
Further investigation shows that most, if not all, PAM modules allow a "debug" argument. When I added this to all of the module lines in /etc/pam.d/atd, I see the following syslog messages (/var/log/secure):
Mar 3 22:51:00 waterloo pam_stack[31567]: called for "PAM_ACCOUNT" Mar 3 22:51:00 waterloo pam_stack[31567]: called from "atd" Mar 3 22:51:00 waterloo pam_stack[31567]: initializing Mar 3 22:51:00 waterloo pam_stack[31567]: creating child stack `system-auth' Mar 3 22:51:00 waterloo pam_stack[31567]: creating environment Mar 3 22:51:00 waterloo pam_stack[31567]: NOT passing PAM_AUTHTOK to child: source is NULL Mar 3 22:51:00 waterloo pam_stack[31567]: passing PAM_CONV to child Mar 3 22:51:00 waterloo pam_stack[31567]: NOT passing PAM_FAIL_DELAY to child: source not set Mar 3 22:51:00 waterloo pam_stack[31567]: NOT passing PAM_OLDAUTHTOK to child: source is NULL Mar 3 22:51:00 waterloo pam_stack[31567]: NOT passing PAM_RHOST to child: source is NULL Mar 3 22:51:00 waterloo pam_stack[31567]: NOT passing PAM_RUSER to child: source is NULL Mar 3 22:51:00 waterloo pam_stack[31567]: passing PAM_SERVICE to child Mar 3 22:51:00 waterloo pam_stack[31567]: passing PAM_TTY to child Mar 3 22:51:00 waterloo pam_stack[31567]: passing PAM_USER to child Mar 3 22:51:00 waterloo pam_stack[31567]: NOT passing PAM_USER_PROMPT to child: source is NULL Mar 3 22:51:00 waterloo pam_stack[31567]: passing data to child Mar 3 22:51:00 waterloo pam_stack[31567]: calling substack Mar 3 22:51:00 waterloo pam_stack[31567]: substack returned 9 (Authentication service cannot retrieve authentication info.) Mar 3 22:51:00 waterloo pam_stack[31567]: NOT passing PAM_AUTHTOK to parent: source is NULL Mar 3 22:51:00 waterloo pam_stack[31567]: passing PAM_CONV to parent Mar 3 22:51:00 waterloo pam_stack[31567]: NOT passing PAM_FAIL_DELAY to parent: source not set Mar 3 22:51:00 waterloo pam_stack[31567]: NOT passing PAM_OLDAUTHTOK to parent: source is NULL Mar 3 22:51:00 waterloo pam_stack[31567]: NOT passing PAM_RHOST to parent: source is NULL Mar 3 22:51:00 waterloo pam_stack[31567]: NOT passing PAM_RUSER to parent: source is NULL Mar 3 22:51:00 waterloo pam_stack[31567]: passing PAM_SERVICE to parent Mar 3 22:51:00 waterloo pam_stack[31567]: passing PAM_TTY to parent Mar 3 22:51:00 waterloo pam_stack[31567]: passing PAM_USER to parent Mar 3 22:51:00 waterloo pam_stack[31567]: NOT passing PAM_USER_PROMPT to parent: source is NULL Mar 3 22:51:00 waterloo pam_stack[31567]: passing data back Mar 3 22:51:00 waterloo pam_stack[31567]: passing former back Mar 3 22:51:00 waterloo pam_stack[31567]: returning 9 (Authentication service cannot retrieve authentication info.) Mar 3 22:51:00 waterloo atd[31567]: Authentication service cannot retrieve authentication info. Mar 3 22:51:00 waterloo pam_stack[31567]: freeing stack data for `system-auth' service
Any ideas what this is telling me?
David L. Crow wrote:
Ever since at-3.1.8-64_FC3 was installed on my machine, at jobs are failing. For each at job that is supposed to run, two messages are ...
I do not know, whats going on there: but maybe you will be glad that i can confirm!
I reinstalled the old at-3.1.8-60 and at works again.
There was an update in the authentifikation: * Tue Jan 25 2005 Jason Vas Dias jvdias@redhat.com 3.1.8-64_FC3
- bugs 5160/146132: add PAM authentication control to atd
After breakfast i will have a look at bugzilla ...
David L. Crow wrote:
Ever since at-3.1.8-64_FC3 was installed on my machine, at jobs are failing. For each at job that is supposed to run, two messages are placed in /var/log/cron:
...
There is a bugilla: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=150131