Hello All, First post. Just ported Samba4 to a native Android/ARM platform -- quite a bit more work than Samba3. Moved to Samba4 to pick up AD support. The smb and nmb daemons fire up and appear to operate correctly, at least as good as Samba3. However, when trying to use samba-tool to create/list users, etc. I run into the following: ERROR(<type 'exceptions.AttributeError'>): uncaught exception - 'module' object has no attribute 'session_info' Which I interpret to mean that the session_info attribute is not present in samba.dcerpc.auth, but it is. I am a Python and Samba novice, but it appears that samba.auth is overshadowing samba.dcerpc.auth, or vice-versa. When I run python interactively, I can import both modules, but I only see the attributes for the first module imported - i.e. if samba.auth is imported prior to samba.dcerpc.auth, a dir of samba.dcerpc.auth will return samba.auth attributes, which presumably causes the AttributeError. Any help to further debug or resolve this issue would be greatly appreciated. Cheers, -John This e-mail (including any attachments) is confidential and intended only for use by the named addressee(s). It may also be privileged or otherwise protected by work-product immunity or other legal rules. If you are not the intended recipient of this e-mail, you are hereby notified that any use, dissemination, distribution or copying of this e-mail, and any attachments, is strictly prohibited. If you received this e-mail in error, please immediately notify me by return e-mail and permanently delete the original and any copies.
On Thu, Jan 15, 2015 at 10:40:00PM +0000, Kaye, John wrote:> Hello All, > > First post. Just ported Samba4 to a native Android/ARM platform -- quite a bit more work than Samba3. Moved to Samba4 to pick up AD support. > > The smb and nmb daemons fire up and appear to operate correctly, at least as good as Samba3. However, when trying to use samba-tool to create/list users, etc. I run into the following: > > ERROR(<type 'exceptions.AttributeError'>): uncaught exception - 'module' object has no attribute 'session_info' > > Which I interpret to mean that the session_info attribute is not present in samba.dcerpc.auth, but it is. I am a Python and Samba novice, but it appears that samba.auth is overshadowing samba.dcerpc.auth, or vice-versa. When I run python interactively, I can import both modules, but I only see the attributes for the first module imported - i.e. if samba.auth is imported prior to samba.dcerpc.auth, a dir of samba.dcerpc.auth will return samba.auth attributes, which presumably causes the AttributeError. > > Any help to further debug or resolve this issue would be greatly appreciated.Oooh oooh oooh ! Can you post the code changes you needed to do the port please ? I'm excited :-).
Jeremy, I will post the code changes soon, after reading the guidelines on how to do it properly. :-) -John -----Original Message----- From: Jeremy Allison [mailto:jra at samba.org] Sent: Thursday, January 15, 2015 3:00 PM To: Kaye, John Cc: samba at lists.samba.org Subject: Re: [Samba] Samba4 Android port and Python auth modules On Thu, Jan 15, 2015 at 10:40:00PM +0000, Kaye, John wrote:> Hello All, > > First post. Just ported Samba4 to a native Android/ARM platform -- quite a bit more work than Samba3. Moved to Samba4 to pick up AD support. > > The smb and nmb daemons fire up and appear to operate correctly, at least as good as Samba3. However, when trying to use samba-tool to create/list users, etc. I run into the following: > > ERROR(<type 'exceptions.AttributeError'>): uncaught exception - 'module' object has no attribute 'session_info' > > Which I interpret to mean that the session_info attribute is not present in samba.dcerpc.auth, but it is. I am a Python and Samba novice, but it appears that samba.auth is overshadowing samba.dcerpc.auth, or vice-versa. When I run python interactively, I can import both modules, but I only see the attributes for the first module imported - i.e. if samba.auth is imported prior to samba.dcerpc.auth, a dir of samba.dcerpc.auth will return samba.auth attributes, which presumably causes the AttributeError. > > Any help to further debug or resolve this issue would be greatly appreciated.Oooh oooh oooh ! Can you post the code changes you needed to do the port please ? I'm excited :-). This e-mail (including any attachments) is confidential and intended only for use by the named addressee(s). It may also be privileged or otherwise protected by work-product immunity or other legal rules. If you are not the intended recipient of this e-mail, you are hereby notified that any use, dissemination, distribution or copying of this e-mail, and any attachments, is strictly prohibited. If you received this e-mail in error, please immediately notify me by return e-mail and permanently delete the original and any copies.
On 15/01/15 22:40, Kaye, John wrote:> Hello All, > > First post. Just ported Samba4 to a native Android/ARM platform -- quite a bit more work than Samba3. Moved to Samba4 to pick up AD support. > > The smb and nmb daemons fire up and appear to operate correctly, at least as good as Samba3. However, when trying to use samba-tool to create/list users, etc. I run into the following: > > ERROR(<type 'exceptions.AttributeError'>): uncaught exception - 'module' object has no attribute 'session_info'If you are starting and running the smbd & nmbd daemons, then samba-tool wouldn't work, you are still in 'classic' mode, you need to provision samba as an AD DC with samba-tool (full instructions are on the wiki) before samba-tool will create users. Rowland> > Which I interpret to mean that the session_info attribute is not present in samba.dcerpc.auth, but it is. I am a Python and Samba novice, but it appears that samba.auth is overshadowing samba.dcerpc.auth, or vice-versa. When I run python interactively, I can import both modules, but I only see the attributes for the first module imported - i.e. if samba.auth is imported prior to samba.dcerpc.auth, a dir of samba.dcerpc.auth will return samba.auth attributes, which presumably causes the AttributeError. > > Any help to further debug or resolve this issue would be greatly appreciated. > > Cheers, > -John > > This e-mail (including any attachments) is confidential and intended only for use by the named addressee(s). It may also be privileged or otherwise protected by work-product immunity or other legal rules. If you are not the intended recipient of this e-mail, you are hereby notified that any use, dissemination, distribution or copying of this e-mail, and any attachments, is strictly prohibited. If you received this e-mail in error, please immediately notify me by return e-mail and permanently delete the original and any copies.