[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Antw: Re: Need information on alock file in data directory of OpenLDAP 2.4.39
Hi!
I'm also using BDB, but I don't have sich problems (SLES11 SP3). You can get
the PID of your slapd with (assuming Linux)
# ps ax |grep slapd
3844 ? Ssl 3:53 /usr/lib/openldap/slapd -h ldap://...
Then you can check for locks with
# grep " 3844 " /proc/locks
6: POSIX ADVISORY WRITE 3844 fd:06:90781 1024 2047
7: POSIX ADVISORY WRITE 3844 fd:06:74093 1024 2047
Then you can check which files are locked
# lsof -p 3844 |egrep ' 90781 | 74093 '
slapd 3844 ldap 10uw REG 253,6 4096 74093
/var/lib/ldap/alock
slapd 3844 ldap 13uw REG 253,6 4096 90781
/var/lib/ldap/audit/alock
You can check for any process that uses an "alock":
# lsof |grep /alock
slapd 3844 ldap 10uw REG 253,6 4096
74093 /var/lib/ldap/alock
slapd 3844 ldap 13uw REG 253,6 4096
90781 /var/lib/ldap/audit/alock
Maybe you can find out what's wong. My slapd is using BDB 4.5 it seems:
# ldd /usr/lib/openldap/slapd
linux-vdso.so.1 => (0x00007fff4a5ff000)
libldap_r-2.4.so.2 => /usr/lib64/libldap_r-2.4.so.2
(0x00007f365844a000)
liblber-2.4.so.2 => /usr/lib64/liblber-2.4.so.2 (0x00007f365823a000)
libltdl.so.7 => /usr/lib64/libltdl.so.7 (0x00007f3658030000)
libdb-4.5.so => /usr/lib64/libdb-4.5.so (0x00007f3657cf8000)
libslp.so.1 => /usr/lib64/libslp.so.1 (0x00007f3657adf000)
libm.so.6 => /lib64/libm.so.6 (0x00007f3657865000)
libnsl.so.1 => /lib64/libnsl.so.1 (0x00007f365764d000)
libsasl2.so.2 => /usr/lib64/libsasl2.so.2 (0x00007f3657432000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f365722d000)
libssl.so.0.9.8 => /usr/lib64/libssl.so.0.9.8 (0x00007f3656fd7000)
libcrypto.so.0.9.8 => /usr/lib64/libcrypto.so.0.9.8
(0x00007f3656c38000)
libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007f36569fc000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f36567e5000)
libwrap.so.0 => /lib64/libwrap.so.0 (0x00007f36565da000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f36563bc000)
libc.so.6 => /lib64/libc.so.6 (0x00007f3656043000)
/lib64/ld-linux-x86-64.so.2 (0x00007f3658958000)
libz.so.1 => /lib64/libz.so.1 (0x00007f3655e2c000)
Regards,
Ulrich
>>> pramod kulkarni <pammu.kulkarni@gmail.com> schrieb am 30.10.2014 um 22:49
in
Nachricht
<CANyT8DkYEh_AQ5cgBKkfm2A_8LBUnmu8opXU2fC3GgPUX7Wx=Q@mail.gmail.com>:
> If I specify slapcat -f slapd.conf -b "dc=example,dc=com" -l backup.ldif
> Then no messages will be displayed in the command window and it will be in
> the same state.
>
> I see somewhere code hangs in the alock.c file I think the slapcat process
> not able to grab the lock,is it correct? or something different.
>
> Regards,
> Pramod
>
> On Thu, Oct 30, 2014 at 10:37 PM, Michael Ströder <michael@stroeder.com>
> wrote:
>
>> pramod kulkarni wrote:
>> > I am runing slapcat command like this, slapcat -f slapd.conf -l
>> backup.ldif
>> > is it wrong ?
>>
>> If you have more than one database you have to use either one of command
>> line
>> options -n or -b.
>>
>> Ciao, Michael.
>>
>>