<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Hi Richard</div><div><br></div><div>This is fixed in release 4.2.1, if you cant upgrade now, you can fix this manuallly </div><div><br></div><div><br></div><div>Just do this.</div><div><br></div><div><span style="background-color: rgba(255, 255, 255, 0);">edit file /usr/lpp/mmfs/lib/mmcesmon/SMBService.py<br></span></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Change </span></div><div><br></div><div><span style="background-color: rgba(255, 255, 255, 0);"> if authType == 'ad' and not nodeState.nfsStopped:</span></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br>to</span></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br> nfsEnabled = utils.isProtocolEnabled("NFS", self.logger)<br> if authType == 'ad' and not nodeState.nfsStopped and nfsEnabled:</span></div><div><br><br>You need to stop the gpfs service in each node where you apply the change </div><div><br></div><div><br></div><div>" after change the lines please use tap key"</div><div><br></div><div><br></div><div><br><div>Enviado desde mi iPhone</div></div><div><br>El 27/08/2016, a las 6:00 a.m., <a href="mailto:gpfsug-discuss-request@spectrumscale.org">gpfsug-discuss-request@spectrumscale.org</a> escribió:<br><br></div><blockquote type="cite"><div><span>Send gpfsug-discuss mailing list submissions to</span><br><span> <a href="mailto:gpfsug-discuss@spectrumscale.org">gpfsug-discuss@spectrumscale.org</a></span><br><span></span><br><span>To subscribe or unsubscribe via the World Wide Web, visit</span><br><span> <a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a></span><br><span>or, via email, send a message with subject or body 'help' to</span><br><span> <a href="mailto:gpfsug-discuss-request@spectrumscale.org">gpfsug-discuss-request@spectrumscale.org</a></span><br><span></span><br><span>You can reach the person managing the list at</span><br><span> <a href="mailto:gpfsug-discuss-owner@spectrumscale.org">gpfsug-discuss-owner@spectrumscale.org</a></span><br><span></span><br><span>When replying, please edit your Subject line so it is more specific</span><br><span>than "Re: Contents of gpfsug-discuss digest..."</span><br><span></span><br><span></span><br><span>Today's Topics:</span><br><span></span><br><span> 1. </span><font color="#000000"><span style="background-color: rgba(255, 255, 255, 0);">Re: Cannot stop SMB... stop NFS first?</span></font>(Christof Schmitt)</div></blockquote><blockquote type="cite"><div><span> 2. Re: CES and mmuserauth command (Christof Schmitt)</span><br><span></span><br><span></span><br><span>----------------------------------------------------------------------</span><br><span></span><br><span>Message: 1</span><br><span>Date: Fri, 26 Aug 2016 12:29:31 -0400</span><br><span>From: "Christof Schmitt" <<a href="mailto:christof.schmitt@us.ibm.com">christof.schmitt@us.ibm.com</a>></span><br><span>To: gpfsug main discussion list <<a href="mailto:gpfsug-discuss@spectrumscale.org">gpfsug-discuss@spectrumscale.org</a>></span><br><span>Subject: Re: [gpfsug-discuss] Cannot stop SMB... stop NFS first?</span><br><span>Message-ID:</span><br><span> <<a href="mailto:OF5D32DCFD.74622168-ON8525801B.0057526F-8525801B.005A97BD@notes.na.collabserv.com">OF5D32DCFD.74622168-ON8525801B.0057526F-8525801B.005A97BD@notes.na.collabserv.com</a>></span><br><span> </span><br><span>Content-Type: text/plain; charset="UTF-8"</span><br><span></span><br><span>That would be the case when Active Directory is configured for </span><br><span>authentication. In that case the SMB service includes two aspects: One is </span><br><span>the actual SMB file server, and the second one is the service for the </span><br><span>Active Directory integration. Since NFS depends on authentication and id </span><br><span>mapping services, it requires SMB to be running.</span><br><span></span><br><span>Regards,</span><br><span></span><br><span>Christof Schmitt || IBM || Spectrum Scale Development || Tucson, AZ</span><br><span><a href="mailto:christof.schmitt@us.ibm.com">christof.schmitt@us.ibm.com</a> || +1-520-799-2469 (T/L: 321-2469)</span><br><span></span><br><span></span><br><span></span><br><span>From: "Sobey, Richard A" <<a href="mailto:r.sobey@imperial.ac.uk">r.sobey@imperial.ac.uk</a>></span><br><span>To: "'<a href="mailto:gpfsug-discuss@spectrumscale.org">gpfsug-discuss@spectrumscale.org</a>'" </span><br><span><<a href="mailto:gpfsug-discuss@spectrumscale.org">gpfsug-discuss@spectrumscale.org</a>></span><br><span>Date: 08/26/2016 04:48 AM</span><br><span>Subject: [gpfsug-discuss] Cannot stop SMB... stop NFS first?</span><br><span>Sent by: <a href="mailto:gpfsug-discuss-bounces@spectrumscale.org">gpfsug-discuss-bounces@spectrumscale.org</a></span><br><span></span><br><span></span><br><span></span><br><span>Sorry all, prepare for a deluge of emails like this, hopefully it?ll help </span><br><span>other people implementing CES in the future.</span><br><span></span><br><span>I?m trying to stop SMB on a node, but getting the following output:</span><br><span></span><br><span>[root@cesnode ~]# mmces service stop smb</span><br><span>smb: Request denied. Please stop NFS first</span><br><span></span><br><span>[root@cesnode ~]# mmces service list</span><br><span>Enabled services: SMB</span><br><span>SMB is running</span><br><span></span><br><span>As you can see there is no way to stop NFS when it?s not running but it </span><br><span>seems to be blocking me. It?s happening on all the nodes in the cluster.</span><br><span></span><br><span>SS version is 4.2.0 running on a fully up to date RHEL 7.1 server.</span><br><span></span><br><span>Richard_______________________________________________</span><br><span>gpfsug-discuss mailing list</span><br><span>gpfsug-discuss at <a href="http://spectrumscale.org">spectrumscale.org</a></span><br><span><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a></span><br><span></span><br><span></span><br><span></span><br><span></span><br><span></span><br><span>------------------------------</span><br><span></span><br><span>Message: 2</span><br><span>Date: Fri, 26 Aug 2016 12:29:31 -0400</span><br><span>From: "Christof Schmitt" <<a href="mailto:christof.schmitt@us.ibm.com">christof.schmitt@us.ibm.com</a>></span><br><span>To: gpfsug main discussion list <<a href="mailto:gpfsug-discuss@spectrumscale.org">gpfsug-discuss@spectrumscale.org</a>></span><br><span>Subject: Re: [gpfsug-discuss] CES and mmuserauth command</span><br><span>Message-ID:</span><br><span> <<a href="mailto:OF96C5E3D5.D7802E36-ON8525801B.0057FD62-8525801B.005A980C@notes.na.collabserv.com">OF96C5E3D5.D7802E36-ON8525801B.0057FD62-8525801B.005A980C@notes.na.collabserv.com</a>></span><br><span> </span><br><span>Content-Type: text/plain; charset="ISO-2022-JP"</span><br><span></span><br><span>The --user-name option applies to both, AD and LDAP authentication. In the </span><br><span>LDAP case, this information is correct. I will try to get some </span><br><span>clarification added for the AD case.</span><br><span></span><br><span>The same applies to the information shown in "service list". There is a </span><br><span>common field that holds the information and the parameter from the initial </span><br><span>"service create" is stored there. The meaning is different for AD and </span><br><span>LDAP: For LDAP it is the username being used to access the LDAP server, </span><br><span>while in the AD case it was only the user initially used until the machine </span><br><span>account was created.</span><br><span></span><br><span>Regards,</span><br><span></span><br><span>Christof Schmitt || IBM || Spectrum Scale Development || Tucson, AZ</span><br><span><a href="mailto:christof.schmitt@us.ibm.com">christof.schmitt@us.ibm.com</a> || +1-520-799-2469 (T/L: 321-2469)</span><br><span></span><br><span></span><br><span></span><br><span>From: Jan-Frode Myklebust <<a href="mailto:janfrode@tanso.net">janfrode@tanso.net</a>></span><br><span>To: gpfsug main discussion list <<a href="mailto:gpfsug-discuss@spectrumscale.org">gpfsug-discuss@spectrumscale.org</a>></span><br><span>Date: 08/26/2016 05:59 AM</span><br><span>Subject: Re: [gpfsug-discuss] CES and mmuserauth command</span><br><span>Sent by: <a href="mailto:gpfsug-discuss-bounces@spectrumscale.org">gpfsug-discuss-bounces@spectrumscale.org</a></span><br><span></span><br><span></span><br><span></span><br><span></span><br><span>On Fri, Aug 26, 2016 at 1:49 AM, Christof Schmitt <</span><br><span><a href="mailto:christof.schmitt@us.ibm.com">christof.schmitt@us.ibm.com</a>> wrote:</span><br><span></span><br><span>When joinging the AD domain, --user-name, --password and --server are only</span><br><span>used to initially identify and logon to the AD and to create the machine</span><br><span>account for the cluster. Once that is done, that information is no longer</span><br><span>used, and e.g. the account from --user-name could be deleted, the password</span><br><span>changed or the specified DC could be removed from the domain (as long as</span><br><span>other DCs are remaining).</span><br><span></span><br><span></span><br><span>That was my initial understanding of the --user-name, but when reading the </span><br><span>man-page I get the impression that it's also used to do connect to AD to </span><br><span>do user and group lookups:</span><br><span></span><br><span>------------------------------------------------------------------------------------------------------</span><br><span>??user?name userName</span><br><span> Specifies the user name to be used to perform operations</span><br><span> against the authentication server. The specified user</span><br><span> name must have sufficient permissions to read user and</span><br><span> group attributes from the authentication server. </span><br><span>-------------------------------------------------------------------------------------------------------</span><br><span></span><br><span>Also it's strange that "mmuserauth service list" would list the USER_NAME </span><br><span>if it was only somthing that was used at configuration time..?</span><br><span></span><br><span></span><br><span></span><br><span> -jf_______________________________________________</span><br><span>gpfsug-discuss mailing list</span><br><span>gpfsug-discuss at <a href="http://spectrumscale.org">spectrumscale.org</a></span><br><span><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a></span><br><span></span><br><span></span><br><span></span><br><span></span><br><span></span><br><span></span><br><span>------------------------------</span><br><span></span><br><span>_______________________________________________</span><br><span>gpfsug-discuss mailing list</span><br><span>gpfsug-discuss at <a href="http://spectrumscale.org">spectrumscale.org</a></span><br><span><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a></span><br><span></span><br><span></span><br><span>End of gpfsug-discuss Digest, Vol 55, Issue 44</span><br><span>**********************************************</span><br><span></span><br></div></blockquote><BR>
</body></html>