net usershare dies for users with "Failed to init messaging context"

David Mulder dmulder at suse.com
Tue Jun 6 20:28:59 UTC 2017


Hmm, problem is the returned error is NT_STATUS_INTERNAL_ERROR, and I
wouldn't think we'd want to blanket allow that error. Looks like it's
coming from messaging_init_internal() where it just returns
NT_STATUS_INTERNAL_ERROR rather than map it from the actual returned error.

On 06/06/2017 09:51 AM, Jeremy Allison wrote:
> On Tue, Jun 06, 2017 at 07:50:43AM -0600, David Mulder wrote:
>> Ugh, didn't mean to encrypt that last message (client did it by default).
>> I pointed out that it looks like we're missing an acceptable NT_STATUS
>> code here. A strace clearly shows that we're being denied because of
>> access issues to the lock dir (which should have taken the 'its ok to
>> fail' case). Instead it's failing because it didn't detect an acceptable
>> messaging init failure.
>> I'll figure out what the status code is and submit a patch.
> Thanks, I'll also take a look if I have time this week.
>
> Can you log a bug for this problem so we can track it ?
>
> Thanks,
>
> Jeremy.
>

-- 
David Mulder
SUSE Labs Software Engineer - Samba
dmulder at suse.com
SUSE Linux GmbH, GF: Felix Imend├Ârffer, Jane Smithard, Graham Norton, HRB 21284 (AG N├╝rnberg)




More information about the samba-technical mailing list