10.12.2018, 14:13, "Alexander Bokovoy" <[email protected]>:
> On ma, 10 joulu 2018, Николай Савельев via FreeIPA-users wrote:
>> Hello.
>> I try to set up samba with freeipa.
>> I use this article 
>> https://www.freeipa.org/page/Howto/Integrating_a_Samba_File_Server_With_IPA
>>
>> But I have strange error:
>>
>> дек 10 13:48:58 nfs.fs.lan smbd[14242]: [2018/12/10 13:48:58.758419, 0] 
>> ../source3/auth/auth_util.c:1372(make_new_session_info_guest)
>> дек 10 13:48:58 nfs.fs.lan smbd[14242]: create_local_token failed: 
>> NT_STATUS_NO_MEMORY
>> дек 10 13:48:58 nfs.fs.lan smbd[14242]: [2018/12/10 13:48:58.758577, 0] 
>> ../source3/smbd/server.c:1993(main)
>> дек 10 13:48:58 nfs.fs.lan smbd[14242]: ERROR: failed to setup guest info.
>> дек 10 13:48:58 nfs.fs.lan systemd[1]: smb.service: main process exited, 
>> code=exited, status=255/n/a
>> дек 10 13:48:58 nfs.fs.lan systemd[1]: Failed to start Samba SMB Daemon.
>>
>> What does it mean?
>
> There is a plenty reasons for create_local_token() to return
> NT_STATUS_NO_MEMORY:
>
>  - actual memory allocation failed
>  - conversion of SIDs to POSIX IDs failed
>  - copying some internal structures failed
>
> Can you provide an output with 'log level = 10' set with
>   net conf setparm global loglevel 10
> ?
>
> --
> / Alexander Bokovoy
> Sr. Principal Software Engineer
> Security / Identity Management Engineering
> Red Hat Limited, Finland

Sorry, Alexander, I didn't install sssd-libwbclient and it made this error.

But I have another problem.
If I set security = ads, I have 

smbclient -k -L nfs.fs.lan
session setup failed: NT_STATUS_ACCESS_DENIED


 I tried security = user  and samba worked fine.

Why? 

-- 
С уважением, Николай.
_______________________________________________
FreeIPA-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/[email protected]

Reply via email to