Hello William, The slapd was down by itself for some reason. Below is from error file this afternoon. [07/Apr/2016:13:36:33 -0400] - slapd started. Listening on All Interfaces port 389 for LDAP requests [07/Apr/2016:13:36:33 -0400] - Listening on All Interfaces port 636 for LDAPS requests [07/Apr/2016:14:06:12 -0400] - slapd shutting down - signaling operation threads [07/Apr/2016:14:06:12 -0400] - slapd shutting down - waiting for 28 threads to terminate [07/Apr/2016:14:06:12 -0400] - slapd shutting down - closing down internal subsystems and plugins [07/Apr/2016:14:06:12 -0400] - Waiting for 4 database threads to stop [07/Apr/2016:14:06:12 -0400] - All database threads now stopped [07/Apr/2016:14:06:12 -0400] - slapd stopped. So I started it: service dirsrv restart. From the error file again, it shows the process is started: [07/Apr/2016:21:25:49 -0400] - 389-Directory/1.2.11.15 B2016.082.1529 starting up [07/Apr/2016:21:25:49 -0400] - slapd started. Listening on All Interfaces port 389 for LDAP requests [07/Apr/2016:21:25:49 -0400] - Listening on All Interfaces port 636 for LDAPS requests The 'service dirsrv status' shows it is running. However, I still get the same authorization error like before when using 389-console. I can't do ldapsearch either like before: ldapsearch -p389 -hlabd1.christianbook.com -x -bdc=christianbook,dc=com # extended LDIF # # LDAPv3 # base <dc=christianbook,dc=com> with scope subtree # filter: (objectclass=*) # requesting: ALL # # search result search: 2 result: 32 No such object # numResponses: 1 ldapsearch -p636 -hlabd1.christianbook.com -x -bdc=christianbook,dc=com (hanging...) - xinhuan -- 389 users mailing list 389-users@%(host_name)s http://lists.fedoraproject.org/admin/lists/389-users@xxxxxxxxxxxxxxxxxxxxxxx
