All users were logged out of Bugzilla on October 13th, 2018

"Could not chdir to home directory : No such file or directory" when connecting to



8 years ago
4 years ago


(Reporter: justdave, Assigned: jabba)



Users of via ssh are greeted with the error "Could not chdir to home directory : No such file or directory" on every connect.  Upon investigation, "getent passwd" shows that all of the users have null home directory entries.  ldap.conf is set to map homeDirectory to the "bzrHome" attribute in LDAP, and all of these users have that attribute set to "/tmp" according to phpla.  I can't figure out why it's showing up null instead of /tmp on the box.
I found several bugs referencing a similar problem with Hg and SVN 4 years ago, all fixed by aravind, but the bugs all only say it got fixed, not what he did to fix it.
Assignee: server-ops → aravind
Group: infra
Changed the map attribute from bzrHome to fakeHome.  Let me know if you still see that message.
I just changed it from fakeHome to bzrHome when this bug was initially filed because half of the users didn't have fakeHome showing up and were getting that message.  Was wondering why it was fakeHome to begin with.  With it set to fakeHome some users get this message and some don't.  Since everyone had the correct values in bzrHome in LDAP already I figured fixing the permissions on bzrHome so it actually worked would be a better course to take.
This is still happening for me.
Assignee: aravind → justdave


8 years ago
Assignee: justdave → jdow

Comment 5

8 years ago
I think this is fixed now. I added an ACL to the ldap server to allow both the fakeHome and the bzrHome attributes to be read. I tested by setting my fakeHome to / , running getent passwd, changing back to /tmp and running it again to make sure that it is being read from ldap and not cached. This seems to work fine now. I'm not sure if we should leave it set to fakeHome or set it back to bzrHome. It probably doesn't matter. I added both to the ACL and it looks like it is consistently /tmp across the board.
Last Resolved: 8 years ago
Resolution: --- → FIXED
Looks like this is still happening for me. I just did a "bzr update" on an old checkout and got greeted with this error message as the first line of output. The update did work, so this is only annoying false error.
Resolution: FIXED → ---

Comment 7

7 years ago
I found the issue with Teemu's account was that the fakeHome attribute was missing altogether:
[root@dm-bzr01 ~]# getent passwd |grep wicked*:1539:100:Teemu Mannermaa::/bin/bash

I added it in ldap, and now I see:

[root@dm-bzr01 ~]# getent passwd |grep wicked*:1539:100:Teemu Mannermaa:/tmp:/bin/bash
Last Resolved: 8 years ago7 years ago
Resolution: --- → FIXED
Blocks: 668975
Product: → Graveyard
You need to log in before you can comment on or make changes to this bug.