dirxdumplog
Synopsis
dirxdumplog [ -a ]
[ -c [!] ComponentNameList ]
[ -h]
[ -l NoOfLookAheadEntries ]
[ -m ]
[ -p ]
[ -s [!] SubComponentNameList ]
[ -t [!] ThreadIdentificationList ]
DirectoryLogFileName […]
dirxdumplog -T [*-*TransportInterfaceLoggingOptions ]
TransportInterfaceLogFileName […]
dirxdumplog -V
Purpose
Displays the contents of a binary directory trace log file or a binary transport interface log file.
Arguments
DirectoryLogFileName
-
A string that represents the name of a serviceability log file on which to operate.
TransportInterfaceLogFile
-
A string that represents the name of a transport interface log file name on which to operate.
Options
-a
-
Suppresses display of additional information available in a directory log file entry, for example, the contents of structured function arguments. (To enable the logging of additional information, set debug level 9 for one or more components in the routing specification file.)
-c [!] ComponentNameList
-
If the ! character is specified, displays the directory log file entries that are not associated with the components specified in ComponentNameList, otherwise, displays the directory log file entries associated with the components in ComponentNameList. ComponentNameList is a string that contains one or more component names associated with the log file entries. There are the following component names:
Keyword
Meaning
dba
Data Base Access
dir
Directory
-h
-
Prints a command usage message.
-l NoOfLookAheadEntries
-
Is an integer that represents the number of log file entries to look ahead when searching for function entry/exit log file pairs. Merging between a function entry/exit log file entry is not performed if the corresponding entry cannot be found in the specified range. If this option is not specified, dirxdumplog uses the value 512 as its search range.
-m
-
Suppresses merging of function entry log file entries and function exit log file entries. Invalid or non-existent function input/output and result parameters of a log file entry are represented as a ??? sequence. If this option is specified, dirxdumplog ignores the -l option.
-p
-
Suppresses display of the prolog information for each log file entry.
-s [!] SubComponentNameList
-
If the ! character is specified, displays the directory log file entries that are not associated with the subcomponents specified in SubComponentNameList, otherwise, displays the log file entries associated with the subcomponents in SubComponentNameList. SubComponentNameList is a string that contains a single subcomponent name or a comma-separated list of subcomponent names associated with the log file entries.
The dirxdumplog command recognizes the following subcomponent names for the component dir:
Keyword
Meaning
aci
Access control
adm
Administration
api
Application interface
asn1
ASN1 encoder/decoder interface
attr
Attribute service
audit
Auditing
bth
Bind table handling
conf
Configuration
cref
Continuation references
ctx
Context-specific memory interface
daspp
DAP/DSP processor
disp
DISP initiator and responder
dopi
Operational binding protocol initiator
drv
Deriving - DN creation
frm
Formatting - DN creation
glsch
DSA schema handling
hash
Hashing
icom
Internal thread communication interface
idb
Interface to the database
idbe
Interface to the database (external, for further use)
idbl
Interface to the database (load)
idbm
Interface to the database in memory
idbn
Interface to the database (native)
idbnl
Interface to the database (native lower)
idbr
Interface to the database (rpc)
init
Initialization
ldap_aud
LDAP audit preparation
ldap_cache
LDAP cache operation
ldap_cfg
Configuration of the LDAP server
ldap_conn
LDAP connection handling
ldap_op
LDAP operation handling
ldap_req
LDAP request handling
ldap_ssl
SSL processing in the LDAP server
ldif_ut
LDIF utility functions
load
Database loading with dirxload
match
Matching
nms
Name service
norm
Normalization
opb
Operational binding
opr
DSA operation handling
osi
OSI communication
que3
DirXQue3 search engine
reorg
Database reorganization
ros
Remote operation service
rpc
RPC interface
sch
Schema handling
sec
Security
shr
Shared resources interface
snmp
SNMP functions
sock
Socket interface
sth
Subtree handling
stx
Syntax handling
sys
System call interface
sysadm
DSA administration
tjh
Timed job handler
util
Utility functions
vthr
Virtual thread interface
The dirxdumplog command recognizes the following subcomponent names for the component dba:
Keyword
Meaning
dbam
Database kernel interface
dbambc
Internal database kernel (buffer cache) interface
dsync
Process synchronization interface
-t [!] ThreadIdentificationList
-
If the ! character is specified, displays the log file entries not associated with the threads specified in ThreadIdentificationList. Otherwise, displays log file entries associated with the threads specified in ThreadIdentificationList. ThreadIdentificationList is a single integer or a comma-separated list of integers that represent one or more thread Ids. Alternately, it is a single keyword or a comma-separated list of keywords representing thread types. The dirxdumplog command recognizes the following thread types:
Keyword
Meaning
"abort thread"
Handles aborted connections
MainThread
Initial (main) thread
OperationThread
DAP, DSP, DISP, or DOP operation handling thread
OsiThread
OSI communication handling thread
OsiIComThread
OSI communication handling thread (supports the primary OSI thread during internal event handling)
RpcComThread
RPC communication handling thread
TimedJobThread
Timed job handling thread
-T [-TransportInterfaceLoggingOptions]
-
Displays contents of specified binary transport interface log files instead of directory log files. TransportInterfaceLoggingOptions is a string of one or more alphanumeric characters that represent types of logging information to be output. The dirxdumplog command recognizes the following logging options:
Character
Meaning
c
Displays only transport interface calls associated with attachment, detachment, connection establishment, redirection of connections and disconnection.
d
Displays only transport interface calls associated with data transfer and flow control.
e
Displays only transport interface calls associated with event handling.
t
Displays additional information about error values returned through t_error().
v
Displays transport interface calls with all options and user data.
x
Displays transport interface calls without options and user data.
D
Displays additional information about internal system calls.
-V
-
Displays the DirX Directory product version, in the format:
product_version build_id date time
For example:
DirX Directory V9.0 9.4.428 2023:03:23 20:10 64-Bit
Description
The directory service subcomponents log important information about their activities and state through an internal serviceability interface or, in the case of the transport interface component, through a local logging interface. You specify how directory trace log messages are to be routed with the file dirxlog.cfg. Each log entry is written as a machine-independent binary record of data defined as the contents of a serviceability prolog structure. The dirxdumplog command displays the contents of this binary file in readable text format.
Example
The following examples are based on a DirX Directory DSA log file LOG20861.01. The logging level has been set to 1-5 for the subcomponents sec, idb, idbn, and icom. The DSA has rejected the bind. The examples reduce the content of the output till it focused on the error.
-
Create a readable log file log.all of the whole content:
dirxdumplog LOG20861.01 > log.all
The following output is written to the file log.all:
-------------------------------------------------------------------------------- RpcComAuxThread 0x00000011 dirxdsa dir Fri 02/11/00 09:48:53 -------------------------------------------------------------------------------- -- DEBUG1 sysadm dirxsysadm_svc.c 220 48:53:738 0 dirx_svc_set_dbg_route (Request: ???, Result: ???) -- DEBUG1 sec svc_auth_x511.c 154 48:53:743 1 auth_check_clt_verifier (verifier: 0xee9d15b4, idx: 8) = SUCCESSFUL -- DEBUG1 sec svc_auth_x511.c 158 48:53:745 1 auth_setup_new_verifier (idx: 8, new_verifier: 0xee9d15ac) -- DEBUG1 sysadm dirxsysadm_svc.c 220 48:53:746[001] 0 dirx_svc_set_route (Request: 0xee9d1674, Result: 0xee9d1658) -- DEBUG1 sec svc_auth_x511.c 154 48:53:752 1 auth_check_clt_verifier (verifier: 0xee9d15b4, idx: 8) = SUCCESSFUL -- DEBUG1 sec svc_auth_x511.c 158 48:53:753[001] 1 auth_setup_new_verifier (idx: 8, new_verifier: 0xee9d15ac) -------------------------------------------------------------------------------- OsiThread 0x0000000a dirxdsa dir Fri 02/11/00 09:50:09 -------------------------------------------------------------------------------- -- DEBUG1 icom NetEvent.c 183 50:09:342[018] 0 IComSend (MessageType: ICOM_CLASS_MSG, ReceiverId: ICOM_OPR_CLASS_ID, MessagePriority: ICOM_NORMAL_PRIORITY, MessageSize: 44, MessageRef: 0xee9913dc, DeliveryCount: NULL<-1>) = SUCCESSFUL -------------------------------------------------------------------------------- OperationThread 0x0000000f dirxdsa dir Fri 02/11/00 09:50:09 -------------------------------------------------------------------------------- -- DEBUG1 icom starto.c 298 50:09:362 0 IComReceive (MessageType: ???, SenderId: ???<Classid: ICOM_OSI_CLASS_ID, EntityId: 10>, MessageSize: ???<OUT: 44>, MessageRef: ???, TimeoutMode: ???, MessagePriority: ???<-1>) = SUCCESSFUL -------------------------------------------------------------------------------- OperationThread 0x00000012 dirxdsa dir Fri 02/11/00 09:50:09 -------------------------------------------------------------------------------- -- DEBUG1 icom starto.c 125 50:09:366[002] 0 IComAttach (SubscriberId: 0xee951d38 <ClassId: ICOM_OPR_CLASS_ID, EntityId: 18>) = SUCCESSFUL -- DEBUG1 icom starto.c 298 50:09:369 1 IComReceive (MessageType: ICOM_CLASS_MSG, SenderId: 0xee951cb0<Classid: ???, EntityId: ???>, MessageSize: 0xee951bec<IN: 64>, MessageRef: 0xee951c84, TimeoutMode: ICOM_WAIT, MessagePriority: NULL<???>) = ??? -------------------------------------------------------------------------------- OperationThread 0x0000000f dirxdsa dir Fri 02/11/00 09:50:09 -------------------------------------------------------------------------------- -- DEBUG1 sec proto.c 151 50:09:372[189] 1 auth_dispatch (op_arg: 0xee931c88, op_res: 0xee931ac8) -- DEBUG1 sec auth_dispatch.c 183 50:09:378[181] 2 auth_rec_bind_arg (binding: 0x469528, bind_ctx: 0xee930a98 , auth_world: 0xee9312d8, bind_arg: 0x469728, bind_res: 0x4698d4, bind_err: 0x46bbc8) = SUCCESSFUL -- DEBUG2 sec auth_dispatch.c 445 50:09:380[173] 3 auth_process_bind (incoming_creds: 0x46972c, binding: 0x469528, memctx: 0xee9308fc, auth_world: 0xee9312d8, cred_kind: AUTH_CRED_SP1, initiator_name: 0x4697d4, return_creds: NULL, dsapolicies: NULL) = AUTH_INVALID_CREDS -- DEBUG4 sec dirxauth_s.c 192 50:09:392 4 DN "Initiator_id.dn for bindtable" at address 004697d8 = " RDN (0): 2.5.4.6 = (PRI) <re> RDN (1): 2.5.4.10 = (DirStr-PRT) <sni> RDN (2): 2.5.4.11 = (DirStr-PRT) <asw> RDN (3): 2.5.4.3 = (DirStr-PRT) <hinz und kunz>" -- DEBUG3 sec dirxauth_s.c 346 50:09:393[159] 4 auth_get_policy_simple (mem_ctx: 0x4694a0, cred_kind: AUTH_CRED_SP1, initiator_name: 0x469734, protocol: DACC_ACTX, role: BT_RESPONDER, auth_world: 0xee9312d8, PwList: 0x4699cc, my_name: 0x4699a4, pol_info: 0xee930234, dsaPolicies: NULL) = AUTH_INVALID_CREDS -- DEBUG1 idb auth_policy.c 262 50:09:395[079] 5 idb_open (open_request: 0xee92fe04, DbHandle: 0xee92fe00 <0x4c1b58>) = SUCCESSFUL request: STRUCT IdbOpenRequest { access_mode = IDB_READ_ONLY ; call = IDB_INTERNAL_CALL ; } -- DEBUG1 idbn idb.c 321 50:09:432[041] 6 idbn_open (DbAccessMode: IDB_READ_ONLY, DbHandle: 0x4c1b58) = SUCCESSFUL -- DEBUG5 sec auth_policy.c 384 50:09:475[005] 5 auth_check_user_level (db_hd: 0xee92fe00, cred_kind: AUTH_CRED_SP1, mem_ctx: 0x4694a0. initiator: 0x469734, pol_info: 0xee930234) = SUCCESSFUL -- DEBUG5 sec auth_policy.c 871 50:09:476[002] 6 auth_get_user_policy_data (idb_hd: 0xee92fe00, mem_ctx: 0x4694a0, initiator: 0x469734, pol_info: 0xee930234) = SUCCESSFUL -- DEBUG1 idb auth_policy.c 2202 50:09:477[001] 7 idb_read_dse (Request: 0xee92fb44, Result: 0xee92fb40) = SUCCESSFUL -- DEBUG5 sec auth_policy.c 394 50:09:481[051] 5 auth_get_user_entry (db_hd: 0xee92fe00, cred_kind: AUTH_CRED_SP1, mem_ctx: 0x4694a0, initiator: 0x469734, pw_attrtype: 307390, pw_list: 0x4699cc) = AUTH_INVALID_CREDS -- DEBUG1 idb auth_policy.c 1075 50:09:482[049] 6 idb_read_dse_dn (Request: 0xee92fc28, rdn count: 4, 7 idb_read_dse (Request: 0xee92f9a0, Result: 0xee92f984) = SUCCESSFUL -- DEBUG1 idb idb.c 2372 50:09:485[004] 7 idb_read_dse (Request: 0xee92f9a0, Result: 0xee92f984) = SUCCESSFUL -- DEBUG1 idb idb.c 2372 50:09:490[017] 7 idb_read_dse (Request: 0xee92f9a0, Result: 0xee92f984) = SUCCESSFUL -- DEBUG1 idbn idb.c 519 50:09:496[009] 8 idbn_read_dse (Request: 0xee92f9a0, Result: 0xee92f984) = SUCCESSFUL -- DEBUG1 idb idb.c 2372 50:09:508[012] 7 idb_read_dse (Request: 0xee92f9a0, Result: 0xee92f984) = SUCCESSFUL -- DEBUG1 idbn idb.c 519 50:09:510[009] 8 idbn_read_dse (Request: 0xee92f9a0, Result: 0xee92f984) = SUCCESSFUL -- DEBUG1 idb idb.c 2372 50:09:521[007] 7 idb_read_dse (Request: 0xee92f9a0, Result: 0xee92f984) = IDB_NOT_FOUND -- DEBUG1 idbn idb.c 519 50:09:524[003] 8 idbn_read_dse (Request: 0xee92f9a0, Result: 0xee92f984) = IDB_NOT_FOUND -- DEBUG1 idb auth_policy.c 435 50:09:533[018] 5 idb_close (DbHandle: 0x4c1b58) = SUCCESSFUL -- DEBUG1 idbn idb.c 402 50:09:534[016] 6 idbn_close (DbHandle: 0x4c1b58) = SUCCESSFUL -- DEBUG3 sec auth_dispatch.c 453 50:09:555[001] 3 auth_gen_bind_err (memctx: 0x4694a0, status: AUTH_INVALID_CREDS, bind_err: 0x46bbc8) = SUCCESSFUL -- DEBUG4 sec auth_audit.c 277 50:09:557 4 "DN for audit" : "/re/sni/asw/hinz und kunz" -- DEBUG1 icom proto.c 157 50:09:562[030] 1 IComSend (MessageType: ICOM_CLASS_MSG, ReceiverId: ICOM_OSI_CLASS_ID, MessagePriority: ICOM_NORMAL_PRIORITY, MessageSize: 44, MessageRef: 0xee931ac4, DeliveryCount: NULL<-1>) = SUCCESSFUL -------------------------------------------------------------------------------- OsiIComThread 0x0000000b dirxdsa dir Fri 02/11/00 09:50:09 -------------------------------------------------------------------------------- -- DEBUG1 icom IComEvent.c 101 50:09:564 0 IComReceive (MessageType: ???, SenderId: ???<Classid: ICOM_OPR_CLASS_ID, EntityId: 15>, MessageSize: ???<OUT: 44>, MessageRef: ???, TimeoutMode: ???, MessagePriority: ???<-1>) = SUCCESSFUL -- DEBUG1 icom IComEvent.c 101 50:09:581 0 IComReceive (MessageType: ICOM_ENTITY_MSG | ICOM_CLASS_MSG, SenderId: 0xee971d34<Classid: ???, EntityId: ???>, MessageSize: 0xee971d30<IN: 44>, MessageRef: 0x3cf28c, TimeoutMode: ICOM_WAIT, MessagePriority: NULL<???>) = ??? -------------------------------------------------------------------------------- OperationThread 0x0000000f dirxdsa dir Fri 02/11/00 09:50:09 -------------------------------------------------------------------------------- -- DEBUG1 icom starto.c 298 50:09:594[4:417] 0 IComReceive (MessageType: ICOM_ENTITY_MSG | ICOM_CLASS_MSG, SenderId: 0xee931cb0<Classid: -1, EntityId: -1>, MessageSize: 0xee931bec<IN: 64 OUT: 64>, MessageRef: 0xee931c84, TimeoutMode: 5000, MessagePriority: NULL<-1>) = ICOM_EMPTY -- DEBUG1 icom starto.c 497 50:14:012 1 IComDetach () = SUCCESSFUL -
Create a readable log file log.sec and restrict the content to the subcomponent sec:
dirxdumplog –s sec LOG20861.01 > log.sec
The following output is written to the file log.sec:
-------------------------------------------------------------------------------- RpcComAuxThread 0x00000011 dirxdsa dir Fri 02/11/00 09:48:53 -------------------------------------------------------------------------------- -- DEBUG1 sec svc_auth_x511.c 154 48:53:743 0 auth_check_clt_verifier (verifier: 0xee9d15b4, idx: 8) = SUCCESSFUL -- DEBUG1 sec svc_auth_x511.c 158 48:53:745 0 auth_setup_new_verifier (idx: 8, new_verifier: 0xee9d15ac) -- DEBUG1 sec svc_auth_x511.c 154 48:53:752 0 auth_check_clt_verifier (verifier: 0xee9d15b4, idx: 8) = SUCCESSFUL -- DEBUG1 sec svc_auth_x511.c 158 48:53:753[001] 0 auth_setup_new_verifier (idx: 8, new_verifier: 0xee9d15ac) -- DEBUG1 sec svc_auth_x511.c 154 48:53:761 0 auth_check_clt_verifier (verifier: 0xee9d15b4, idx: 8) = SUCCESSFUL -- DEBUG1 sec svc_auth_x511.c 158 48:53:763 0 auth_setup_new_verifier (idx: 8, new_verifier: 0xee9d15ac) -- DEBUG1 sec svc_auth_x511.c 154 48:53:770 0 auth_check_clt_verifier (verifier: 0xee9d15b4, idx: 8) = SUCCESSFUL -- DEBUG1 sec svc_auth_x511.c 158 48:53:772 0 auth_setup_new_verifier (idx: 8, new_verifier: 0xee9d15ac) -- DEBUG1 sec svc_auth_x511.c 154 48:53:778 0 auth_check_clt_verifier (verifier: 0xee9d15b4, idx: 8) = SUCCESSFUL -- DEBUG1 sec svc_auth_x511.c 158 48:53:781 0 auth_setup_new_verifier (idx: 8, new_verifier: 0xee9d15ac) -------------------------------------------------------------------------------- OperationThread 0x0000000f dirxdsa dir Fri 02/11/00 09:50:09 -------------------------------------------------------------------------------- -- DEBUG1 sec proto.c 151 50:09:372[189] 0 auth_dispatch (op_arg: 0xee931c88, op_res: 0xee931ac8) -- DEBUG1 sec auth_dispatch.c 183 50:09:378[181] 1 auth_rec_bind_arg (binding: 0x469528, bind_ctx: 0xee930a98 , auth_world: 0xee9312d8, bind_arg: 0x469728, bind_res: 0x4698d4, bind_err: 0x46bbc8) = SUCCESSFUL -- DEBUG2 sec auth_dispatch.c 445 50:09:380[173] 2 auth_process_bind (incoming_creds: 0x46972c, binding: 0x469528, memctx: 0xee9308fc, auth_world: 0xee9312d8, cred_kind: AUTH_CRED_SP1, initiator_name: 0x4697d4, return_creds: NULL, dsapolicies: NULL) = AUTH_INVALID_CREDS -- DEBUG4 sec dirxauth_s.c 192 50:09:392 3 DN "Initiator_id.dn for bindtable" at address 004697d8 = " RDN (0): 2.5.4.6 = (PRI) <re> RDN (1): 2.5.4.10 = (DirStr-PRT) <sni> RDN (2): 2.5.4.11 = (DirStr-PRT) <asw> RDN (3): 2.5.4.3 = (DirStr-PRT) <hinz und kunz>" -- DEBUG3 sec dirxauth_s.c 346 50:09:393[159] 3 auth_get_policy_simple (mem_ctx: 0x4694a0, cred_kind: AUTH_CRED_SP1, initiator_name: 0x469734, protocol: DACC_ACTX, role: BT_RESPONDER, auth_world: 0xee9312d8, PwList: 0x4699cc, my_name: 0x4699a4, pol_info: 0xee930234, dsaPolicies: NULL) = AUTH_INVALID_CREDS -- DEBUG5 sec auth_policy.c 384 50:09:475[005] 4 auth_check_user_level (db_hd: 0xee92fe00, cred_kind: AUTH_CRED_SP1, mem_ctx: 0x4694a0. initiator: 0x469734, pol_info: 0xee930234) = SUCCESSFUL -- DEBUG5 sec auth_policy.c 871 50:09:476[002] 5 auth_get_user_policy_data (idb_hd: 0xee92fe00, mem_ctx: 0x4694a0, initiator: 0x469734, pol_info: 0xee930234) = SUCCESSFUL -- DEBUG5 sec auth_policy.c 394 50:09:481[051] 4 auth_get_user_entry (db_hd: 0xee92fe00, cred_kind: AUTH_CRED_SP1, mem_ctx: 0x4694a0, initiator: 0x469734, pw_attrtype: 307390, pw_list: 0x4699cc) = AUTH_INVALID_CREDS -- DEBUG3 sec auth_dispatch.c 453 50:09:555[001] 2 auth_gen_bind_err (memctx: 0x4694a0, status: AUTH_INVALID_CREDS, bind_err: 0x46bbc8) = SUCCESSFUL -- DEBUG4 sec auth_audit.c 277 50:09:55 -
Create a readable log file log_thread15.sec and restrict the content to the subcomponent sec and the thread with threadID 15:
dirxdumplog –s sec -t 0x0f LOG20861.01 > log_thread15.sec
The following output is written to the file log_thread15.sec:
-------------------------------------------------------------------------------- OperationThread 0x0000000f dirxdsa dir Fri 02/11/00 09:50:09 -------------------------------------------------------------------------------- -- DEBUG1 sec proto.c 151 50:09:372[189] 0 auth_dispatch (op_arg: 0xee931c88, op_res: 0xee931ac8) -- DEBUG1 sec auth_dispatch.c 183 50:09:378[181] 1 auth_rec_bind_arg (binding: 0x469528, bind_ctx: 0xee930a98 , auth_world: 0xee9312d8, bind_arg: 0x469728, bind_res: 0x4698d4, bind_err: 0x46bbc8) = SUCCESSFUL -- DEBUG2 sec auth_dispatch.c 445 50:09:380[173] 2 auth_process_bind (incoming_creds: 0x46972c, binding: 0x469528, memctx: 0xee9308fc, auth_world: 0xee9312d8, cred_kind: AUTH_CRED_SP1, initiator_name: 0x4697d4, return_creds: NULL, dsapolicies: NULL) = AUTH_INVALID_CREDS -- DEBUG4 sec dirxauth_s.c 192 50:09:392 3 DN "Initiator_id.dn for bindtable" at address 004697d8 = " RDN (0): 2.5.4.6 = (PRI) <re> RDN (1): 2.5.4.10 = (DirStr-PRT) <sni> RDN (2): 2.5.4.11 = (DirStr-PRT) <asw> RDN (3): 2.5.4.3 = (DirStr-PRT) <hinz und kunz>" -- DEBUG3 sec dirxauth_s.c 346 50:09:393[159] 3 auth_get_policy_simple (mem_ctx: 0x4694a0, cred_kind: AUTH_CRED_SP1, initiator_name: 0x469734, protocol: DACC_ACTX, role: BT_RESPONDER, auth_world: 0xee9312d8, PwList: 0x4699cc, my_name: 0x4699a4, pol_info: 0xee930234, dsaPolicies: NULL) = AUTH_INVALID_CREDS -- DEBUG5 sec auth_policy.c 384 50:09:475[005] 4 auth_check_user_level (db_hd: 0xee92fe00, cred_kind: AUTH_CRED_SP1, mem_ctx: 0x4694a0. initiator: 0x469734, pol_info: 0xee930234) = SUCCESSFUL -- DEBUG5 sec auth_policy.c 871 50:09:476[002] 5 auth_get_user_policy_data (idb_hd: 0xee92fe00, mem_ctx: 0x4694a0, initiator: 0x469734, pol_info: 0xee930234) = SUCCESSFUL -- DEBUG5 sec auth_policy.c 394 50:09:481[051] 4 auth_get_user_entry (db_hd: 0xee92fe00, cred_kind: AUTH_CRED_SP1, mem_ctx: 0x4694a0, initiator: 0x469734, pw_attrtype: 307390, pw_list: 0x4699cc) = AUTH_INVALID_CREDS -- DEBUG3 sec auth_dispatch.c 453 50:09:555[001] 2 auth_gen_bind_err (memctx: 0x4694a0, status: AUTH_INVALID_CREDS, bind_err: 0x46bbc8) = SUCCESSFUL -- DEBUG4 sec auth_audit.c 277 50:09:557 3 "DN for audit" : "/re/sni/asw/hinz und kunz"