On Behalf Of Lucian

Check /var/log/audit/audit.log, maybe it's a Selinux related problem. Were you using Selinux on those Centos/Fedora installations previously? Maybe the contexts haven't been migrated over (properly).

Thank you for your reply. I normally disable selinux, but its worth checking out :)

Michael

===================================

Please consider the environment before printing this e-mail

Cleveland Clinic is ranked one of the top hospitals in America by U.S.News & World Report (2010). Visit us online at http://www.clevelandclinic.org for a complete listing of our services, staff and locations.

Confidentiality Note: This message is intended for use only by the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. Thank you.

On Thu, Jan 26, 2012 at 2:28 PM, Tru Huynh tru@centos.org wrote:

no issue here on CentOS-6.2 2.6.32-220.4.1.el6.x86_64 selinux enforced (but I have setsebool -P use_nfs_home_dirs=1)

ibrix:/ibfs1/tru mounted as /home/ibrix (newly created ibrix user)

Tru -

Thank you for your response. When you created the NFS export on the IBRIX system, what options did you use? I am currently using its defaults of RW, NO_ROOT_SQUASH

Thanks Michael

On Fri, Jan 27, 2012 at 3:44 AM, Tru Huynh tru@centos.org wrote:

[root@xxxxxxx ~]# ibrix_version -l  Fusion Manager version: 6.0.326  ===============================  Segment Servers  ===============  HOST_NAME  FILE_SYSTEM         IAD/IAS  IAD/FS   OS         KERNEL_VERSION  ARCH  ---------  ------------------  -------  -------  ---------  --------------  ----  xxxxxxxx1  6.0.326(X9000_6_0)  6.0.326 6.0.326  GNU/Linux  2.6.18-194.el5  x86_64  xxxxxxxx2  6.0.326(X9000_6_0)  6.0.326 6.0.326  GNU/Linux  2.6.18-194.el5  x86_64

...

• l'export et les options que tu as utilisé?

[root@hummer-s2 ~]# ibrix_exportfs -l HOSTNAME   FSNAME  PATH                               OPTIONS ---------  ------  ---------------------------------  ------- xxxxxxxx1  ibfs1   centos6:/ibfs1/tru  rw,no_root_squash xxxxxxxx1  ibfs1   centos5:/ibfs1/tru  rw,no_root_squash xxxxxxxx2  ibfs1   centos6:/ibfs1/tru  rw,no_root_squash xxxxxxxx2  ibfs1   centos5:/ibfs1/tru  rw,no_root_squash

In the CentOS-5 and CentOS-6 machines, mount reports: ibrix:/ibfs1/tru on /home/ibrix type nfs (rw,addr=xxxx)

I would check if your problematic user is created both locally and in your NIS/LDAP/... setup with different uid, restart the gdm daemon (caching? issue), stop nscd (+ flush the local cached data, before restarting it).

Tru -

thank you for the information, here is mine for the same

[root@lri-brix01 ~]# ibrix_version -l Fusion Manager version: 6.0.326 =============================== Segment Servers =============== HOST_NAME FILE_SYSTEM IAD/IAS IAD/FS OS KERNEL_VERSION ARCH ---------- ------------------ ------- ------- --------- -------------- ---- lri-brix01 6.0.326(X9000_6_0) 6.0.326 6.0.326 GNU/Linux 2.6.18-194.el5 x86_64 lri-brix02 6.0.326(X9000_6_0) 6.0.326 6.0.326 GNU/Linux 2.6.18-194.el5 x86_64

and

[root@lri-brix01 ~]# ibrix_exportfs -l HOSTNAME FSNAME PATH OPTIONS ---------- ------ ------------------------------------- ------- lri-brix01 ibrix *:/ibrix/testing rw,no_root_squash ...... <many many exportfs shares>

On workstation, mount shows:

lri-brix:/ibrix/testing on /bme/home type nfs (rw,addr=10.66.200.11)

I even mounted the test share manually, disabling autofs and ypbind, and created a 'local' user with an NFS mounted $HOME directory and it still failed. I dont see what i have done wrong. SSH logins work, and the directory is traversable by the local user but still can not log in via Gnome or KDE.

Michael

On Fri, Jan 27, 2012 at 9:28 AM, Tru Huynh tru@centos.org wrote:

try mounting to /home/username instead of /bme/home/username (and fixing /etc/passwd)

no other idea for the moment.

Tru -

Thank you for the suggestion, i did this, and it still failed with that .dmrc error, even AFTER i changed the RelaxPermissions to be 2 in the gdm default.conf file and restarted the workstation. I am just stumped.

Michael

On Tue, Jan 31, 2012 at 03:10:15PM -0500, Michael Weiner wrote:

On Fri, Jan 27, 2012 at 9:28 AM, Tru Huynh tru@centos.org wrote:

...

no other idea for the moment.

Tru -

I think i *MAY* have this figured out. When you do 'ibrix_fs -i' is compatibility set to no? If so, are you a 64-bit client only shop? I am wondering if our having the 64-bit mode set is causing the problems.

I did my tests on c5/c6 x86_64 only.

[root@lri-brix01 temp]# ibrix_fs -i FileSystem: ibrix ================= Total Segments : 24 STATE : Mounted Mirrored? : No Compatible? : No

[root@xxxxxx2 ~]# ibrix_fs -i FileSystem: ibfs1 ================= Total Segments : 4 STATE : Mounted Mirrored? : No Compatible? : Yes,MaxSegments=63

I don't have account on the ibrix machine.

imho: this should be fixed by HP/ibrix support team. Good luck,

Tru

On Thu, Jan 26, 2012 at 2:22 PM, Thomas Burns tburns@hawaii.edu wrote:

Any relevant messages in /var/log/messages of the server? Is automount able to mount and it is "just" a permissions problem?

I had a vaguely similar problem recently, trying to get OSX to access NIS/NFS, it needs different mount options in the automounter config.

You say you tried with automount turned off, were you able to mount manually but not able to access? Same error message?

What does nsswitch.conf look like?

Generally my trouble shooting goes like this:

1. get NIS to work ('ypcat mymap' works)
2. mount NFS share manually with mount command and access as root
3. access NFS share as ordinary user
4. get automount to mount the share

Thanks for your response Dave! I have been unable to find anything relevant in the server syslogs. But here is what i have tried:

1) ypcat mymap gives me back what i would expect, as does a ypcat -k passwd | grep myusername 2) I can mount the share manually on the workstation (using -o nfsvers=3,rw,hard,intr options) and it mounts and i can traverse it as a root user 3) I can mount the share manually on the workstation and i can traverse it as root and as a local user 4) i can then put the map in place, restart autofs, log in via a NIS account and it maps correctly and i can traverse it properly in a shell (i.e. ssh, etc) 5) i tried mounting manually, creating a $home directory for a new user, giving that user a password and i can ssh in but not Gnome or KDE 6) variations of the above.

And this *IS* working currently on a Sun X4540 system, and the NON-HOME directories that get mapped upon login correctly map on the HP X9320 via NIS authentication just not X.

Thanks for the help and logical thinking. Michael

On Thu, Jan 26, 2012 at 3:40 PM, Thomas Burns tburns@hawaii.edu wrote:

If it was me, I'd try creating a new home directory for that user on a disk local to the machine where you're trying to log in. Presumably the user could then log in. Then I'd check that the user could access the NFS share normally just not as home. If no problem there, I'd be a bit tempted to stop there as a workaround, because I am lazy and most of my users just use one machine.

I have tried this, but of course i did it as the users $HOME directory. The reason we do it this way is because we use that file server to then back up all environmental files and user data. This is currently working, and has been for years, on other hardware ... we just purchased the HP at the end of last year, and silly me thought i would just migrate everything over like i have time and time again :(

Seems possible to me that the dmrc file error message and the instant logout are related but not identical. Gnome just does not like NFS home dirs. (My experience has been, if the same user is logged in to two machines, kablooey!) I used to frequently see a similar problem, after a crash or other odd event, where the user could log in but then would immediately be logged out with an error similar to your second message. I had a magic trick I had to go through to untangle things, if you are desperate enough you could try it:

At this point i supposed i can try anything, this device is not in production yet for this purpose so i have some leeway and can play somewhat.

• delete all files in the user's home dir that start with .gconf

(.gconf and .gconfd).

• delete all files in /tmp.
• reboot to make sure all processes release old corrupted files.
• if feeling paranoid, before having the user try to log in, check

again as root that /tmp is empty and nothing in user's home dir is named .gconf*.

I basically achieved this same thing by doing an 'adduser newuser' and providing it a password which then created the $HOME directory on the NFS mount, and then attempting to login to Gnome or KDE as that user to no avail - same error

One of the symptoms of my problem was, after the user tried to log in and failed, there would be some processes owned by that user alive or in zombie state but still part of ps output, although of course the user was not logged in. These must be killed (or overkilled with reboot) and all traces in /tmp removed. But this would show up in the log of the machine where user is trying to log in (if I recall) as some complaint about gconf. So this may be a goose chase for you, since KDE also fails. I'm not sure what (if anything) they would have in common.

Thanks for the suggestions on some other things to try. Michael

On Thu, Jan 26, 2012 at 3:55 PM, Les Mikesell lesmikesell@gmail.com wrote:

Gnome doesn't like multiple concurrent logins, period.  For example, via the console and freenx as the same user.  I've sometimes wondered if the authors ever saw a multi-headed unix system or used X remotely.  But that doesn't really have much to do with the automount/nfs issue.

No, but it broke up my day, LOL Thanks!