[lustre-discuss] putting web pages on lustre mount
Dilger, Andreas
andreas.dilger at intel.com
Thu Jan 26 09:36:30 PST 2017
On Jan 26, 2017, at 09:26, Andrus, Brian Contractor <bdandrus at nps.edu> wrote:
>
> Quick follow-up then.
> Is there a way to tell lustre to ignore uid/gid lookups? Kind of like for gluster, there is a mount option of ‘allow_other’ that seems to do that.
You can set mdt.*.identity_upcall to "NONE" on the MDSes.
Cheers, Andreas
> Brian
>
> From: lustre-discuss [mailto:lustre-discuss-bounces at lists.lustre.org] On Behalf Of Andrus, Brian Contractor
> Sent: Thursday, January 26, 2017 9:07 AM
> To: Patrick Farrell <paf at cray.com>; Dilger, Andreas <andreas.dilger at intel.com>
> Cc: lustre-discuss at lists.lustre.org
> Subject: Re: [lustre-discuss] putting web pages on lustre mount
>
> Hmm. That is the odd part then.
> It is in /etc/passwd (it is the standard apache user: uid/gid 48) on both the MDS and the client. Hmm…
>
> Aha! The apache user was NOT on the second MDS/MDT. Added there and now things seem happier.
>
> Thanks!
>
> Brian Andrus
> ITACS/Research Computing
> Naval Postgraduate School
> Monterey, California
> voice: 831-656-6238
>
>
>
> From: Patrick Farrell [mailto:paf at cray.com]
> Sent: Thursday, January 26, 2017 8:13 AM
> To: Andrus, Brian Contractor <bdandrus at nps.edu>; Dilger, Andreas <andreas.dilger at intel.com>
> Cc: lustre-discuss at lists.lustre.org
> Subject: Re: [lustre-discuss] putting web pages on lustre mount
>
>
> I believe Andreas meant to say etc/passwd.
>
>
> The key thing here is resolving that uid/gid. That output suggests it failed.
>
> It doesn't have to be in passwd if you're using ldap or some other auth setup, but you do have to be able to look up that uid/gid.
> From: lustre-discuss <lustre-discuss-bounces at lists.lustre.org> on behalf of Andrus, Brian Contractor <bdandrus at nps.edu>
> Sent: Thursday, January 26, 2017 9:06:56 AM
> To: Dilger, Andreas
> Cc: lustre-discuss at lists.lustre.org
> Subject: Re: [lustre-discuss] putting web pages on lustre mount
>
> It comes back with:
>
> # L_GETIDENTITY_TEST=true l_getidentity -d 48
> uid=48 gid=48
> permissions:
> nid perm
>
>
> The only thing in /etc/hosts is the localhost. Everything else is via DNS that is all there (forward/reverse/aliases, etc)
>
> Brian Andrus
> ITACS/Research Computing
> Naval Postgraduate School
> Monterey, California
> voice: 831-656-6238
>
>
>
> -----Original Message-----
> From: Dilger, Andreas [mailto:andreas.dilger at intel.com]
> Sent: Wednesday, January 25, 2017 5:25 PM
> To: Andrus, Brian Contractor <bdandrus at nps.edu>
> Cc: lustre-discuss at lists.lustre.org
> Subject: Re: [lustre-discuss] putting web pages on lustre mount
>
> On Jan 25, 2017, at 16:36, Andrus, Brian Contractor <bdandrus at nps.edu> wrote:
> >
> > We’ve been using lustre for some time with great success, but I recently tried moving some hosted web pages from a gluster mount to a lustre mount and suddenly they don’t work, giving an error:
> >
> > [core:error] [pid 8769] (13)Permission denied: [client xxx.xxx.yyy.zzz:56341] AH00035: access to /yum/7/ denied (filesystem path '/opt/yum/7') because search permissions are missing on a component of the path
> >
> > Thing is, the permissions/ownership are exactly the same as the gluster mount. Is there a particular mount setting that needs done so apache can serve pages on a lustre mount?
>
> Is the web server UID/GID in the /etc/hosts file on the MDS so that the l_getidentity upcall can find them? Try running on the MDS as root:
>
> L_GETIDENTITY_TEST=true l_getidentity -d {uid}
>
> and verify that the user can be found.
>
> Cheers, Andreas
> --
> Andreas Dilger
> Lustre Principal Architect
> Intel Corporation
>
>
>
>
>
>
>
> _______________________________________________
> lustre-discuss mailing list
> lustre-discuss at lists.lustre.org
> http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
Cheers, Andreas
--
Andreas Dilger
Lustre Principal Architect
Intel Corporation
More information about the lustre-discuss
mailing list