[Samba] NT_STATUS_OBJECT_NAME_NOT_FOUND after installing the last git version

Garming Sam garming at catalyst.net.nz
Tue Feb 18 16:07:36 MST 2014

On 18/02/14 21:13, Andrew Bartlett wrote:
> Thank you very much for bringing this to our attention.
> This is a (now) know regression that appears to have been introduced
> recently with the change to use wbc_xids_to_sids.  Garming and I were
> able to isolate it down to one of these commits at the end of our work
> day today:
> 6b04558c5e0547a807ac0fcb5eeb1085cfe602ac auth4: Remove unused wbc_context
> f35f88d741f1f896268649238d4ddbda4abb1585 ntvfs_unixuid: No wbc_context required
> 55dd08c4e80827ffc4fe423f3e67aec499af06df ntvfs_posix: No wbc_context required
> 5a4252789b54b6b270b3083f6e0732ba1fdd774b dcesrv_unixinfo: No wbc_context required
> 25e83a9b3e72cdb84c09ef8ada4784efd110f09a unixuid: Use the tevent_context from the ntvfs_context
> 15700a9f6e5393cecf78052f510e015300c5bd85 pvfs: Use the tevent_context from the ntvfs_context
> 5124a9e1183de990ca3146cd355152094495a779 auth4: Do not generate just a temporary wbc_context
> 75d7c4609c1c743f84ca9f2d0666aece9e5200d4 auth4: auth_session_info_fill_unix only needs a tevent_context
> 1de725c2926b526200032c4f46132c17533986c7 auth4: security_token_to_unix_token only needs a tevent_context
> ba5f02739cb454d2312f73f643f2c119e090ac5e libwbclient4: Remove unused composite-based functions
> d0932a1ae089fda0d41be21a9916caeca7c0c233 source4: Use wbc_xids_to_sids
> f275ce4e4367478b488810491c7bcd993c37caf1 libwbclient4: Add wbc_xids_to_sids
> de7122ddc356697777cce95d22b3fab7697b30db source4: Use wbc_sids_to_xids
> fefc59619b58cb0c38bf7e6ac2ebcc25a5ebbd6c libwbclient4: Add wbc_sids_to_xids
> I expect to further diagnose this tomorrow, but in the meantime I've
> CC'ed the patch author and reviewer in case they have any insights.
> In the meantime, you could assist by reverting each of these patches in
> turn, and verifying that it does indeed resolve your issue.
> Sorry,
> Andrew Bartlett

Regarding the cause of the issue, it seems we've identified the problem. 
The issue is the fact that the winbindd socket directory was never set, 
thus it was using /tmp/.winbindd and failing (in winbindd_pipe_sock in 

The reason the tests didn't fail was because it managed to set it 
correctly with the environment variables.

The fix is minor, which is just to add the missing cflags in the 
wscript_build file which include the necessary winbindd socket directory.

Attached is also a patch by Andrew to ensure this doesn't happen again.


Garming Sam
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Define-the-winbindd-socket-directory-when-building-w.patch
Type: text/x-patch
Size: 1044 bytes
Desc: not available
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20140219/a68f2847/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-nsswitch-Remove-fallback-setting-of-WINBINDD_SOCKET_.patch
Type: text/x-patch
Size: 2177 bytes
Desc: not available
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20140219/a68f2847/attachment-0001.bin>

More information about the samba-technical mailing list