pam_mount home directory (using SSHFS) can't log in

Bug #881408 reported by Joe Collins
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
user-mounts
New
Undecided
Unassigned
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

Hello all - first of all, great work on Ubuntu! Been using it for years and love it!

I'm not sure if this is a bug or a lack of knowledge on my part. The newest documentation that I've been able to find was from 2008 and it was mediocre at best and not ubuntu-specific. On a separate note, it would be helpful if someone knowledgeable on this topic could write a how-to.

Anyway, here it goes:
My user account information is stored on a remote LDAP server host name 'fileserver' running Ubuntu 11.10. I'm using pam_mount on my workstations to auto-mount a directory (also located on 'fileserver') when a user logs in to Ubuntu. User home directories are also on this network directory. Here's the problem. Sometimes it works, sometimes it doesn't.

On previous releases of Ubuntu, after typing my login credentials, I ALWAYS get an error indicating something to the effect that it couldn't access the .ICEAuthority file. If I wait a few seconds, then click close, everything works OK. If I click close immediately, it logs me in but without mounting the network directory (in effect, I get the desktop of a brand new user).

On Ubuntu 11.10, when I get the ICEAuthority error, my only choice is to log out - that brings me back to the login screen. No way to "pass go" it seems.

This sounds to me like some kind of timing issue. I'm guessing that my user account info (home directory, shell, etc) is pulled from LDAP much faster than pam_mount can mount the network directory. Ubuntu is probably expecting my home directory to exist immediately after I log in. Maybe I need some way to insert a delay between logging in and when Ubuntu looks for the existence of my home directory - to give pam_mount time.

Anyone have any ideas here?

Here's my pam_mount.conf.xml file in case it helps:

<!DOCTYPE pam_mount SYSTEM "pam_mount.conf.xml.dtd">
<!--
 See pam_mount.conf(5) for a description.
-->

<pam_mount>

  <!-- debug should come before everything else,
  since this file is still processed in a single pass
  from top-to-bottom -->

<debug enable="1" />

  <!-- Volume definitions -->

  <!-- pam_mount parameters: General tunables -->

<!--
<luserconf name=".pam_mount.conf.xml" />
-->

<!-- Note that commenting out mntoptions will give you the defaults.
     You will need to explicitly initialize it with the empty string
     to reset the defaults to nothing. -->
<mntoptions allow="nosuid,nodev,loop,encryption,fsck,nonempty,allow_root,allow_o
ther" />
<!--
<mntoptions deny="suid,dev" />
<mntoptions allow="*" />
<mntoptions deny="*" />
-->
<mntoptions require="nosuid,nodev" />

<logout wait="0" hup="0" term="0" kill="0" />

<!--<fusemount>mount.fuse %(VOLUME) %(MNTPT) -o %(OPTIONS)</fusemount>-->
<volume fstype="fuse" path="sshfs#%(USER)@fileserver:/data" mountpoint="/data" o
ptions="nonempty,reconnect,idmap=user,password_stdin,allow_other" />

<mkmountpoint enable="1" remove="true" />

</pam_mount>

Revision history for this message
Joe Collins (jgc26) wrote :

I first asked this in the "Questions" section and didn't receive a response (I let it linger for about a week). If I need to provide more information, please let me know what to provide and I'd be happy to!

Changed in ubuntu:
status: New → Invalid
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Marked Invalid Ubuntu tag only, user-mount atill valid
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Revision history for this message
Joe Collins (jgc26) wrote :

Just following up... Has any progress been made on this?

Revision history for this message
g (garic-suess) wrote :

I've got exactly the same issue here.

It seems like GDM is not waiting for PAM Mount to complete before proceeding to use the home directory.

Why was this marked as invalid?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.