Bug 24811 - samba4-idmap.py: couldn't find ldb
Summary: samba4-idmap.py: couldn't find ldb
Status: RESOLVED WORKSFORME
Alias: None
Product: UCS
Classification: Unclassified
Component: Samba4
Version: UCS 3.0
Hardware: Other Linux
: P5 normal
Target Milestone: UCS 3.x
Assignee: Samba maintainers
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-22 22:03 CET by Stefan Gohmann
Modified: 2013-06-19 12:38 CEST (History)
2 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Customer ID:
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Gohmann univentionstaff 2011-11-22 22:03:10 CET 
Die folgende Meldung erscheint immer in der listener.log:

lpcfg_servicenumber: couldn't find ldb
21.11.11 21:31:02.648  LISTENER    ( PROCESS ) : samba4-idmap: added entry for S-1-5-21-2192183024-2677559174-2030691912-1145
lpcfg_servicenumber: couldn't find ldb
21.11.11 21:31:18.319  LISTENER    ( PROCESS ) : samba4-idmap: removing entry for S-1-5-21-2192183024-2677559174-2030691912-1145
lpcfg_servicenumber: couldn't find ldb
21.11.11 21:31:38.571  LISTENER    ( PROCESS ) : samba4-idmap: added entry for S-1-4-5040
lpcfg_servicenumber: couldn't find ldb
21.11.11 21:31:41.587  LISTENER    ( PROCESS ) : samba4-idmap: renaming entry for S-1-4-5040 to S-1-5-21-2192183024-2677559174-2030691912-1146
Comment 1 Tobias Peters univentionstaff 2013-04-22 17:53:32 CEST 
Diese Meldungen sind nicht mehr im listener.log zu finden.

univention-directory-listener: 7.0.8-1.199.201303011501
univention-samba4: 2.0.45-1.438.201304221741
Comment 2 Arvid Requate univentionstaff 2013-06-19 12:38:28 CEST 
This message appears at debug level 7, e.g. also from samba_dnsupdate and samba_spnupdate. Judging from the source code, I guess it's comming from samba4-4.0.3/lib/ldb-samba/ldb_wrap.c checking for the parameter "ldb:nosync" in smb.conf, so I guess it's harmless.