Hello,
after an update from 6.6 to 6.7 the following error message is logged to /var/log/messages when I login (per ssh):
Aug 11 16:31:21 a1234 automount[1598]: set_tsd_user_vars: failed to get passwd info from getpwuid_r
Checked all log-files of my systems running 6.6 with same configuration -- never got such a message (We use NFS/autofs for home-directories, NIS and tcsh (login shell)).
Everything seems to work -- but before I update all machines to 6.7 I want to know whats going on.
Any comments?
Best regards, Ralf
On Tue, Aug 11, 2015 at 10:55 AM, Ralf Aumüller < Ralf.Aumueller@informatik.uni-stuttgart.de> wrote:
Hello,
after an update from 6.6 to 6.7 the following error message is logged to /var/log/messages when I login (per ssh):
Aug 11 16:31:21 a1234 automount[1598]: set_tsd_user_vars: failed to get passwd info from getpwuid_r
Checked all log-files of my systems running 6.6 with same configuration -- never got such a message (We use NFS/autofs for home-directories, NIS and tcsh (login shell)).
Everything seems to work -- but before I update all machines to 6.7 I want to know whats going on.
Any comments?
Best regards, Ralf _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
I am seeing the same issue.
Any ideas anyone?
On Mon, Aug 17, 2015 at 8:39 AM, Phelps, Matthew mphelps@cfa.harvard.edu wrote:
On Tue, Aug 11, 2015 at 10:55 AM, Ralf Aumüller < Ralf.Aumueller@informatik.uni-stuttgart.de> wrote:
Hello,
after an update from 6.6 to 6.7 the following error message is logged to /var/log/messages when I login (per ssh):
Aug 11 16:31:21 a1234 automount[1598]: set_tsd_user_vars: failed to get passwd info from getpwuid_r
Checked all log-files of my systems running 6.6 with same configuration -- never got such a message (We use NFS/autofs for home-directories, NIS and tcsh (login shell)).
Everything seems to work -- but before I update all machines to 6.7 I want to know whats going on.
Any comments?
Best regards, Ralf _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
I am seeing the same issue.
Any ideas anyone?
To answer the original question, RedHat Engineering is looking into it.
From https://access.redhat.com/solutions/1573693 (subscription required):
"Issue
After an update to RHEL6.7 the following error shows up in logfile /var/log/messages:
automount[60432]: set_tsd_user_vars: failed to get passwd info from getpwuid_r
Environment
Red Hat Enterprise Linux 6.7
Resolution
The issue is currently under investigation by Red Hat Engineering. In case you encounter the problem in your environment, please open a ticket with Red Hat Global Support."
Hello,
after an update from 6.6 to 6.7 the following error message is logged to /var/log/messages when I login (per ssh):
Aug 11 16:31:21 a1234 automount[1598]: set_tsd_user_vars: failed to get passwd info from getpwuid_r
Did some more tests:
Compiled autofs with logging of UID/GID in autofs-function "set_tsd_user_vars". Just before the error is logged, autofs tries to get password info for e.g. UID 409651584 and GID 4294936577 (witch don't exist). Then error message is logged.
A fully updated 6.7 system running latest 6.6 kernel (2.6.32-504.30.3.el6.x86_64) won't print the error message. I checked the changelog of kernel 2.6.32-573.3.1.el6.x86_64 and found some autofs patches since version 504.30.3.
But I can't test an further because the kernel-srpm didn't include single patches anymore.
Maybe someone with deeper kernel knowledge has an idea?
Best regards, Ralf
On Fri, Sep 4, 2015 at 5:28 AM, Ralf Aumüller < Ralf.Aumueller@informatik.uni-stuttgart.de> wrote:
Hello,
after an update from 6.6 to 6.7 the following error message is logged
to
/var/log/messages when I login (per ssh):
Aug 11 16:31:21 a1234 automount[1598]: set_tsd_user_vars: failed to get passwd info from getpwuid_r
Did some more tests:
Compiled autofs with logging of UID/GID in autofs-function "set_tsd_user_vars". Just before the error is logged, autofs tries to get password info for e.g. UID 409651584 and GID 4294936577 (witch don't exist). Then error message is logged.
A fully updated 6.7 system running latest 6.6 kernel (2.6.32-504.30.3.el6.x86_64) won't print the error message. I checked the changelog of kernel 2.6.32-573.3.1.el6.x86_64 and found some autofs patches since version 504.30.3.
But I can't test an further because the kernel-srpm didn't include single patches anymore.
Maybe someone with deeper kernel knowledge has an idea?
Best regards, Ralf
It looks like the latest kernel release fixes this issue:
CentOS pushed the kernel update last night (CEBA-2015:1827 CentOS 6 kernel BugFix Update). I've tested it on a machine that logged the error every time we ran a certain cron job, and so far the errors are no longer appearing.
From the RedHat advisory at https://rhn.redhat.com/errata/RHBA-2015-1827.html :
* When logging in as a user and trying to mount a share using the "cd" command, the UID and GID autofs additional variables previously took incorrect values, taking root UID and GID instead of user's UID and GID. The bug in the assignment of uid and gid mount requests has been fixed, and UID and GID now get the correct values with autofs configuration on Red Hat Enterprise Linux 6.7. (BZ#1258581)
-Matt
Phelps, Matthew <mphelps@...> writes:
On Tue, Aug 11, 2015 at 10:55 AM, Ralf Aumüller < Ralf.Aumueller <at> informatik.uni-stuttgart.de> wrote:
Hello,
after an update from 6.6 to 6.7 the following error message is logged to /var/log/messages when I login (per ssh):
Aug 11 16:31:21 a1234 automount[1598]: set_tsd_user_vars: failed to get passwd info from getpwuid_r
Checked all log-files of my systems running 6.6 with same configuration -- never got such a message (We use NFS/autofs for home-directories, NIS and tcsh (login shell)).
Everything seems to work -- but before I update all machines to 6.7 I want to know whats going on.
Any comments?
Best regards, Ralf _______________________________________________ CentOS mailing list CentOS <at> centos.org http://lists.centos.org/mailman/listinfo/centos
I am seeing the same issue.
Any ideas anyone?
Matthew and Ralf, we were also seeing this. We do variable substitution for some of our mounts (mount server:/export/$OSNAME-$OSREL-$CPU/ on the local machine). In our case, server:/export/$OSNAME-$OSREL-$CPU didn't exist. Once we created it and the mount succeeded, the set_tsd_user_vars errors went away. (At least they have for the past 30 minutes, when we had been seeing them usually every minute or two and no more than every 10 minutes.) YMMV.
Michael Sanderson Manager, Computing Facilities UBC Computer Science