#550892 libpam-mount: mounts/unmounts defined mounts when first mounted

Package:
gnome-keyring
Source:
gnome-keyring
Description:
GNOME keyring services (daemon and tools)
Submitter:
Simon Raven
Date:
2010-12-26 07:55:09 UTC
Severity:
important
#550892#5
Date:
2009-10-13 21:18:24 UTC
From:
To:
hi,

Once one of the defined mounts is mounted, it continually unmounts it,
and mounts it again, in a cycle like that, all the time - literally. Day
or night, whether it's busy or not, it'll unmount it, then re-mount it a
bit later. This has been going on since the last upgrade to the
package.

It's annoying to have it unmount something when you're working on a
file, go to save it, then the program you're using tells you it isn't
there anymore.

(a random bit of venting there, wasn't directed at you the maintainer,
nothing personal at all, ok ? :))

thanks,
simon
#550892#10
Date:
2009-10-26 23:32:55 UTC
From:
To:
Hi,

Am Dienstag, 13. Oktober 2009 23:18:24 schrieb Simon Raven:
There is no code in pam_mount that mounts and unmounts in a cycle.
Please turn on debugging in /etc/security/pam_mount.conf.xml and have a look
in the system log (var/log/syslog for example) to see which process is causing
these mounts.
You should also use 'ps aufwwx' to find which process are running.
Please mail the system log output and the output of the above ps command to
calvin@debian.org if you need more assistance.

Thanks,
  Bastian
#550892#15
Date:
2009-10-26 23:32:55 UTC
From:
To:
Hi,

Am Dienstag, 13. Oktober 2009 23:18:24 schrieb Simon Raven:
There is no code in pam_mount that mounts and unmounts in a cycle.
Please turn on debugging in /etc/security/pam_mount.conf.xml and have a look
in the system log (var/log/syslog for example) to see which process is causing
these mounts.
You should also use 'ps aufwwx' to find which process are running.
Please mail the system log output and the output of the above ps command to
calvin@debian.org if you need more assistance.

Thanks,
  Bastian
#550892#20
Date:
2009-10-27 02:20:39 UTC
From:
To:
2009/10/26 Bastian Kleineidam <calvin@debian.org>:
the client logs about what did it, obviously it would be on the
client, but that's no help, as there's no trace of it in the log. I'll
stick some ps auxw command in my .zlogin so i can see what processes
get run at the time, maybe on a for loop. obviously to get a process
table dump after the fact is pointless.

OK, well, I've done that now, and I'm not seeing anything that could
cause it. pam-mount works fine... what's more relevant is this IMO:

That's me mounting /AAAAA to /DDDDD, then something else unmounting:

=====
Oct 27 02:10:10 pylon mountd[xxxxx]: authenticated mount request from
192.168.yyy.zzz:861 for /AAAAA (/AAAAA)
Oct 27 02:10:11 pylon mountd[xxxxx]: authenticated mount request from
192.168.yyy.zzz:868 for /BBBBB (/BBBBB)
Oct 27 02:10:11 pylon mountd[xxxxx]: authenticated mount request from
192.168.yyy.zzz:787 for /CCCCC (/CCCCC)
Oct 27 02:10:11 pylon mountd[xxxxx]: authenticated mount request from
192.168.yyy.zzz:1002 for /DDDDD (/DDDDD)
Oct 27 02:10:17 pylon mountd[xxxxx]: authenticated unmount request
from 192.168.yyy.zzz:644 for /DDDDD (/DDDDD)
Oct 27 02:10:19 pylon mountd[xxxxx]: authenticated unmount request
from 192.168.yyy.zzz:706 for /CCCCC (/CCCCC)
Oct 27 02:10:31 pylon mountd[xxxxx]: authenticated unmount request
from 192.168.yyy.zzz:779 for /BBBBB (/BBBBB)
Oct 27 02:10:32 pylon mountd[xxxxx]: authenticated unmount request
from 192.168.yyy.zzz:797 for /AAAAA (/AAAAA)
=====

that's from the server... so it gets a request to unmount them as soon
as they get mounted. Right now I'm running gnome. Normally I'm running
xfce or openbox. Gonna try in one of my other session types, see if
it's some stupid gui thing causing it or not (I'm think it is). I'll
send an update your way (and the BTS) when I have more info.

Waaah! Now it did it again. pam-mount sees it unmounted, so mounts
them, then whatever sees them mounted, unmounts them. GRR!
#550892#25
Date:
2009-10-27 02:20:39 UTC
From:
To:
2009/10/26 Bastian Kleineidam <calvin@debian.org>:
the client logs about what did it, obviously it would be on the
client, but that's no help, as there's no trace of it in the log. I'll
stick some ps auxw command in my .zlogin so i can see what processes
get run at the time, maybe on a for loop. obviously to get a process
table dump after the fact is pointless.

OK, well, I've done that now, and I'm not seeing anything that could
cause it. pam-mount works fine... what's more relevant is this IMO:

That's me mounting /AAAAA to /DDDDD, then something else unmounting:

=====
Oct 27 02:10:10 pylon mountd[xxxxx]: authenticated mount request from
192.168.yyy.zzz:861 for /AAAAA (/AAAAA)
Oct 27 02:10:11 pylon mountd[xxxxx]: authenticated mount request from
192.168.yyy.zzz:868 for /BBBBB (/BBBBB)
Oct 27 02:10:11 pylon mountd[xxxxx]: authenticated mount request from
192.168.yyy.zzz:787 for /CCCCC (/CCCCC)
Oct 27 02:10:11 pylon mountd[xxxxx]: authenticated mount request from
192.168.yyy.zzz:1002 for /DDDDD (/DDDDD)
Oct 27 02:10:17 pylon mountd[xxxxx]: authenticated unmount request
from 192.168.yyy.zzz:644 for /DDDDD (/DDDDD)
Oct 27 02:10:19 pylon mountd[xxxxx]: authenticated unmount request
from 192.168.yyy.zzz:706 for /CCCCC (/CCCCC)
Oct 27 02:10:31 pylon mountd[xxxxx]: authenticated unmount request
from 192.168.yyy.zzz:779 for /BBBBB (/BBBBB)
Oct 27 02:10:32 pylon mountd[xxxxx]: authenticated unmount request
from 192.168.yyy.zzz:797 for /AAAAA (/AAAAA)
=====

that's from the server... so it gets a request to unmount them as soon
as they get mounted. Right now I'm running gnome. Normally I'm running
xfce or openbox. Gonna try in one of my other session types, see if
it's some stupid gui thing causing it or not (I'm think it is). I'll
send an update your way (and the BTS) when I have more info.

Waaah! Now it did it again. pam-mount sees it unmounted, so mounts
them, then whatever sees them mounted, unmounts them. GRR!
#550892#30
Date:
2009-10-27 06:50:14 UTC
From:
To:
2009/10/26 Bastian Kleineidam <calvin@debian.org>:

=====
Oct 27 02:45:04 acahkos gnome-keyring-daemon[9658]: removing removable
location: /AAAAA
Oct 27 02:45:04 acahkos gnome-keyring-daemon[9658]: no volume
registered at: /AAAAA
Oct 27 02:45:04 acahkos gnome-keyring-daemon[9658]: removing removable
location: /BBBBB
Oct 27 02:45:04 acahkos gnome-keyring-daemon[9658]: no volume
registered at: /BBBBB
=====

Equivalent to the AAAAA and BBBBB from my previous message. So
gnome-keyring-daemon is removing them from being mounted. WHY? Thanks
for your time.

simon
#550892#35
Date:
2009-10-27 06:50:14 UTC
From:
To:
2009/10/26 Bastian Kleineidam <calvin@debian.org>:

=====
Oct 27 02:45:04 acahkos gnome-keyring-daemon[9658]: removing removable
location: /AAAAA
Oct 27 02:45:04 acahkos gnome-keyring-daemon[9658]: no volume
registered at: /AAAAA
Oct 27 02:45:04 acahkos gnome-keyring-daemon[9658]: removing removable
location: /BBBBB
Oct 27 02:45:04 acahkos gnome-keyring-daemon[9658]: no volume
registered at: /BBBBB
=====

Equivalent to the AAAAA and BBBBB from my previous message. So
gnome-keyring-daemon is removing them from being mounted. WHY? Thanks
for your time.

simon
#550892#40
Date:
2009-10-27 06:58:53 UTC
From:
To:
2009/10/26 Bastian Kleineidam <calvin@debian.org>:
doing it, probably via pam_session, is my guess.

=====
Oct 27 02:45:04 acahkos CRON[31738]: pam_mount(misc.c:38):
set_myuid<pre>: (uid=0, euid=0, gid=0, egid=0)
Oct 27 02:45:04 acahkos CRON[31738]: pam_mount(misc.c:38):
set_myuid<post>: (uid=0, euid=0, gid=0, egid=0)
Oct 27 02:45:04 acahkos CRON[31577]: pam_mount(mount.c:695): going to unmount
Oct 27 02:45:04 acahkos CRON[31577]: pam_mount(mount.c:196): Mount
info: globalconf, user=root <volume fstype="nfs" server="pylon"
path="/AAAAA" mountpoint="/AAAAA" cipher="(null)" fskeypath="(null)"
fskeycipher="(null)" fskeyhash="(null)"
options="wsize=16384,rsize=16384,bg,retry=10,intr,nfsvers=3,proto=tcp,mountproto=tcp,sec=sys,noauto,user,dev,suid,exec"
/> fstab=0
=====
#550892#45
Date:
2009-10-27 06:58:53 UTC
From:
To:
2009/10/26 Bastian Kleineidam <calvin@debian.org>:
doing it, probably via pam_session, is my guess.

=====
Oct 27 02:45:04 acahkos CRON[31738]: pam_mount(misc.c:38):
set_myuid<pre>: (uid=0, euid=0, gid=0, egid=0)
Oct 27 02:45:04 acahkos CRON[31738]: pam_mount(misc.c:38):
set_myuid<post>: (uid=0, euid=0, gid=0, egid=0)
Oct 27 02:45:04 acahkos CRON[31577]: pam_mount(mount.c:695): going to unmount
Oct 27 02:45:04 acahkos CRON[31577]: pam_mount(mount.c:196): Mount
info: globalconf, user=root <volume fstype="nfs" server="pylon"
path="/AAAAA" mountpoint="/AAAAA" cipher="(null)" fskeypath="(null)"
fskeycipher="(null)" fskeyhash="(null)"
options="wsize=16384,rsize=16384,bg,retry=10,intr,nfsvers=3,proto=tcp,mountproto=tcp,sec=sys,noauto,user,dev,suid,exec"
/> fstab=0
=====
#550892#48
Date:
2009-11-09 15:06:04 UTC
From:
To:
Well then cron seems to be the culprit... and the admin who configured
cron to use pam_mount in session ;-)
#550892#53
Date:
2010-05-24 11:13:57 UTC
From:
To:
Hi,

perhaps you have the gnome-keyring-daemon configured in your cron PAM file at
/etc/pam.d/cron ?
Then whenever a cron daemon finishes, the gnome-keyring-daemon umounts all (or
just some) removable locations.
The solution in this case would be either to fix gnome-keyring-daemon, or
remove it from the cron PAM config.

Regards,
  Bastian
#550892#56
Date:
2010-05-24 11:13:57 UTC
From:
To:
Hi,

perhaps you have the gnome-keyring-daemon configured in your cron PAM file at
/etc/pam.d/cron ?
Then whenever a cron daemon finishes, the gnome-keyring-daemon umounts all (or
just some) removable locations.
The solution in this case would be either to fix gnome-keyring-daemon, or
remove it from the cron PAM config.

Regards,
  Bastian