[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: port 389 not present while slapd is running
I checked the output of
lsof | grep slapd
nothing related to port and no string LISTEN.
slapd 1367 ldap cwd DIR 3,2 4096 2 /
slapd 1367 ldap rtd DIR 3,2 4096 2 /
slapd 1367 ldap txt REG 3,2 740524 2343702 /usr/local/libexec/slapd
slapd 1367 ldap mem REG 3,2 423136 1213670 /usr/lib/libkrb5.so.3.2
slapd 1367 ldap mem REG 3,2 42252 737324 /lib/libnss_nis-2.3.2.so
slapd 1367 ldap mem REG 3,2 217512 737394 /lib/libssl.so.0.9.7a
slapd 1367 ldap mem REG 3,2 93028 737362 /lib/libnsl-2.3.2.so
slapd 1367 ldap mem REG 3,2 24848 737395 /lib/libcrypt-2.3.2.so
slapd 1367 ldap mem REG 3,2 825138 819910 /usr/local/BerkeleyDB.4.3
/lib/libdb-4.3.so
slapd 1367 ldap mem REG 3,2 107716 737387 /lib/ld-2.3.2.so
slapd 1367 ldap mem REG 3,2 1575400 73060 /lib/tls/libc-2.3.2.so
slapd 1367 ldap mem REG 3,2 16312 737388 /lib/libdl-2.3.2.so
slapd 1367 ldap mem REG 3,2 65928 1213286 /usr/lib/libz.so.1.2.0.7
slapd 1367 ldap mem REG 3,2 99880 73062 /lib/tls/libpthread-0.60.
so
slapd 1367 ldap mem REG 3,2 78048 737390 /lib/libresolv-2.3.2.so
slapd 1367 ldap mem REG 3,2 972464 737393 /lib/libcrypto.so.0.9.7a
slapd 1367 ldap mem REG 3,2 7464 737392 /lib/libcom_err.so.2.1
slapd 1367 ldap mem REG 3,2 139896 1213037 /usr/lib/libk5crypto.so.3
.0
slapd 1367 ldap mem REG 3,2 78628 1213671 /usr/lib/libgssapi_krb5.s
o.2.2
slapd 1367 ldap mem REG 3,2 51152 737319 /lib/libnss_files-2.3.2.s
o
slapd 1367 ldap mem REG 3,2 1980660 737375 /lib/libnss_ldap-2.3.2.so
slapd 1367 ldap mem REG 3,2 24576 2245465 /usr/local/var/openldap-d
ata/__db.001
slapd 1367 ldap 0u CHR 1,3 67073 /dev/null
slapd 1367 ldap 1u CHR 1,3 67073 /dev/null
slapd 1367 ldap 2u CHR 1,3 67073 /dev/null
slapd 1367 ldap 3u unix 0xc045b800 122834 socket
slapd 1367 ldap 4r FIFO 0,5 122835 pipe
slapd 1367 ldap 5w FIFO 0,5 122835 pipe
slapd 1367 ldap 6u sock 0,0 122836 can't identify protocol
matthew sporleder <msporleder@gmail.com> wrote:
>Check for anything that mentions a port number. I use the
>command-line options, so also it's possible to use that. Check your
>ps -auxwww output (on BSD ps), or ps -o args on systemV-style ps (I
>don't know about linux, so check the man page if you're using that)
>
>In lsof, you're looking for the string TCP and an association to the
>PID of your slapd process. For example:
>
>slapd 6104 ldapusr 6u IPv4 0x306618afcf8 1t0 TCP
>*:3891 (LISTEN)
>
>If these don't work, try manually starting your slapd with the
>commands your startup script would use, but make sure you understand
>each one.
>
>/mypath/to/slapd -h ldap://0.0.0.0:389 -f /path/to/config -otherstuff
>-- For this option, I would also add some debugging options.
>
>_Matt
>
>On 8/11/05, nugulus@netscape.net <nugulus@netscape.net> wrote:
>> Could you please elaborate a little, like how do I check out my own config?
>> The slapd.conf file has been used since before the problem occurred. Also, what do I suppose to look for in the lsof output?
>>
>> Thank you.
>>
>> Jun
>>
>
__________________________________________________________________
Switch to Netscape Internet Service.
As low as $9.95 a month -- Sign up today at http://isp.netscape.com/register
Netscape. Just the Net You Need.
New! Netscape Toolbar for Internet Explorer
Search from anywhere on the Web and block those annoying pop-ups.
Download now at http://channels.netscape.com/ns/search/install.jsp