Trying to delete one entry

02-16-2011, 10:52 AM

Hi, gurus!
We have a 389DS and the following problem deleting an entry.
Our server has multiple databases and the problem only appears in one,
we can remove entries from cn=users but not from other subtree.

All databases are not in read only mode.

ldapdelete shows an ldap_delete: Operations error (1).
In another subtree we can delete any entry without problems.

In the inspect of the ACIs we haven't found anything wrong (same ACI in
both subtrees).

Attached is the modified output of ldapdelete with debug mode 2147483647.

Thanks in advance.

--

[root@ldap ~]# ldapdelete -d 2147483647 -x -D "cn=xxxxxxxx" -w xxxxxxxx "cn=xxxxxxxxx.xxxxxx, ou=xxxxx, ou=xxxxx.es, ou=xxxxx, dc=xxxx, dc=es"
ldap_create
ldap_bind
ldap_simple_bind
ldap_sasl_bind
ldap_send_initial_request
ldap_new_connection 1 1 0
ldap_int_open_connection
ldap_connect_to_host: TCP 127.0.0.1:389
ldap_new_socket: 3
ldap_prepare_socket: 3
ldap_connect_to_host: Trying 127.0.0.1:389
ldap_connect_timeout: fd: 3 tm: -1 async: 0
ldap_open_defconn: successful
ldap_send_server_request
ber_scanf fmt ({it) ber:
ber_dump: buf=0xd4497d0 ptr=0xd4497d0 end=0xd4497f1 len=33
... xx
ber_scanf fmt ({i) ber:
ber_dump: buf=0xd4497d0 ptr=0xd4497d5 end=0xd4497f1 len=28
...
ber_flush: 33 bytes to sd 3
... xx
ldap_write: want=33, written=33
... xxx
ldap_result ld 0xd4405e0 msgid 1
wait4msg ld 0xd4405e0 msgid 1 (infinite timeout)
wait4msg continue ld 0xd4405e0 msgid 1 all 1
** ld 0xd4405e0 Connections:
* host: 127.0.0.1 port: 389 (default)
refcnt: 2 status: Connected
last used: Wed Feb 16 09:52:24 2011

** ld 0xd4405e0 Outstanding Requests:
* msgid 1, origid 1, status InProgress
outstanding referrals 0, parent count 0
** ld 0xd4405e0 Response Queue:
Empty
ldap_chkResponseList ld 0xd4405e0 msgid 1 all 1
ldap_chkResponseList returns ld 0xd4405e0 NULL
ldap_int_select
read1msg: ld 0xd4405e0 msgid 1 all 1
ber_get_next
ldap_read: want=8, got=8
0000: 30 0c 02 01 01 61 07 0a 0....a..
ldap_read: want=6, got=6
0000: 01 00 04 00 04 00 ......
ber_get_next: tag 0x30 len 12 contents:
ber_dump: buf=0xd44aaa0 ptr=0xd44aaa0 end=0xd44aaac len=12
0000: 02 01 01 61 07 0a 01 00 04 00 04 00 ...a........
read1msg: ld 0xd4405e0 msgid 1 message type bind
ber_scanf fmt ({eaa) ber:
ber_dump: buf=0xd44aaa0 ptr=0xd44aaa3 end=0xd44aaac len=9
0000: 61 07 0a 01 00 04 00 04 00 a........
read1msg: ld 0xd4405e0 0 new referrals
read1msg: mark request completed, ld 0xd4405e0 msgid 1
request done: ld 0xd4405e0 msgid 1
res_errno: 0, res_error: <>, res_matched: <>
ldap_free_request (origid 1, msgid 1)
ldap_parse_result
ber_scanf fmt ({iaa) ber:
ber_dump: buf=0xd44aaa0 ptr=0xd44aaa3 end=0xd44aaac len=9
0000: 61 07 0a 01 00 04 00 04 00 a........
ber_scanf fmt (}) ber:
ber_dump: buf=0xd44aaa0 ptr=0xd44aaac end=0xd44aaac len=0

ldap_msgfree
ldap_delete_ext
ldap_send_initial_request
ldap_send_server_request
ber_scanf fmt ({it) ber:
ber_dump: buf=0xd4497d0 ptr=0xd4497d0 end=0xd449826 len=86
...
...
ber_flush: 86 bytes to sd 3
...
...
ldap_write: want=86, written=86
...
...
ldap_result ld 0xd4405e0 msgid -1
wait4msg ld 0xd4405e0 msgid -1 (timeout 100000 usec)
wait4msg continue ld 0xd4405e0 msgid -1 all 1
** ld 0xd4405e0 Connections:
* host: 127.0.0.1 port: 389 (default)
refcnt: 2 status: Connected
last used: Wed Feb 16 09:52:24 2011

** ld 0xd4405e0 Outstanding Requests:
* msgid 2, origid 2, status InProgress
outstanding referrals 0, parent count 0
** ld 0xd4405e0 Response Queue:
Empty
ldap_chkResponseList ld 0xd4405e0 msgid -1 all 1
ldap_chkResponseList returns ld 0xd4405e0 NULL
ldap_int_select
read1msg: ld 0xd4405e0 msgid -1 all 1
ber_get_next
ldap_read: want=8, got=8
0000: 30 0c 02 01 02 6b 07 0a 0....k..
ldap_read: want=6, got=6
0000: 01 01 04 00 04 00 ......
ber_get_next: tag 0x30 len 12 contents:
ber_dump: buf=0xd44aaa0 ptr=0xd44aaa0 end=0xd44aaac len=12
0000: 02 01 02 6b 07 0a 01 01 04 00 04 00 ...k........
read1msg: ld 0xd4405e0 msgid 2 message type delete
ber_scanf fmt ({eaa) ber:
ber_dump: buf=0xd44aaa0 ptr=0xd44aaa3 end=0xd44aaac len=9
0000: 6b 07 0a 01 01 04 00 04 00 k........
read1msg: ld 0xd4405e0 0 new referrals
read1msg: mark request completed, ld 0xd4405e0 msgid 2
request done: ld 0xd4405e0 msgid 2
res_errno: 0, res_error: <>, res_matched: <>
ldap_free_request (origid 2, msgid 2)
ldap_parse_result
ber_scanf fmt ({iaa) ber:
ber_dump: buf=0xd44aaa0 ptr=0xd44aaa3 end=0xd44aaac len=9
0000: 6b 07 0a 01 01 04 00 04 00 k........
ber_scanf fmt (}) ber:
ber_dump: buf=0xd44aaa0 ptr=0xd44aaac end=0xd44aaac len=0

ldap_msgfree
ldap_err2string
ldap_delete: Operations error (1)
ldap_free_connection 1 1
ldap_send_unbind
ber_flush: 7 bytes to sd 3
0000: 30 05 02 01 03 42 00 0....B.
ldap_write: want=7, written=7
0000: 30 05 02 01 03 42 00 0....B.
ldap_free_connection: actually freed
--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users

02-16-2011, 12:05 PM

Hi,

can you see anything in the logs of the DS:
/var/log/dirserv/slapd-<inst>/access
/var/log/dirserv/slapd-<inst>/error

Regards,
Carsten

----- Ursprüngliche Nachricht -----
Von: Rafael Cervillera <rccortes@ujaen.es>
Datum: Mittwoch, 16. Februar 2011, 12:53
Betreff: [389-users] Trying to delete one entry
An: "General discussion list for the 389 Directory server project." <389-users@lists.fedoraproject.org>

> Hi, gurus!
> We have a 389DS and the following problem deleting an entry.
> Our server has multiple databases and the problem only appears
> in one,
> we can remove entries from cn=users but not from other subtree.
> All databases are not in read only mode.
>
> ldapdelete shows an ldap_delete: Operations error (1).
> In another subtree we can delete any entry without problems.
>
> In the inspect of the ACIs we haven't found anything wrong (same
> ACI in
> both subtrees).
>
> Attached is the modified output of ldapdelete with debug mode
> 2147483647.
>
> Thanks in advance.
>
> --
>
>
> > --
> 389 users mailing list
> 389-users@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/389-users
--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users

02-16-2011, 12:23 PM

The only information showed in the access log is

*** conn=2 op=1 DEL dn="cn=xx"

*** conn=2 op=1 RESULT err=1 tag=107 nentries=0 etime=0

In the error and audit log there isn't any information about this
error.

Any idea?

Thanks.

On 16/02/2011 14:05, Carsten Grzemba wrote:

Hi,

can you see anything in the logs of the DS:
/var/log/dirserv/slapd-<inst>/access
/var/log/dirserv/slapd-<inst>/error

Regards,
Carsten

----- Ursprüngliche Nachricht -----
Von: Rafael Cervillera <rccortes@ujaen.es>
Datum: Mittwoch, 16. Februar 2011, 12:53
Betreff: [389-users] Trying to delete one entry
An: "General discussion list for the 389 Directory server project." <389-users@lists.fedoraproject.org>

Hi, gurus!
We have a 389DS and the following problem deleting an entry.
Our server has multiple databases and the problem only appears
in one,
we can remove entries from cn=users but not from other subtree.
All databases are not in read only mode.

ldapdelete shows an ldap_delete: Operations error (1).
In another subtree we can delete any entry without problems.

In the inspect of the ACIs we haven't found anything wrong (same
ACI in
both subtrees).

Attached is the modified output of ldapdelete with debug mode
2147483647.

Thanks in advance.

--

--

389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users

--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users

--
____ __
| _ __ _ / _| __ _
| |_) / _` | |_ / _` |
| _ < (_| | _| (_| |
|_| \_\__,_|_| \__,_|

--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users

02-16-2011, 12:55 PM

works an ldapmodify on this entry?

----- Ursprüngliche Nachricht -----
Von: Rafael Cervillera <rccortes@ujaen.es>
Datum: Mittwoch, 16. Februar 2011, 14:23
Betreff: Re: [389-users] Trying to delete one entry
An: "General discussion list for the 389 Directory server project." <389-users@lists.fedoraproject.org>

>
The only information showed in the access log is
>
*** conn=2 op=1 DEL dn="cn=xx"
>
*** conn=2 op=1 RESULT err=1 tag=107 nentries=0 etime=0

>

>
>
In the error and audit log there isn't any information about this
error.

>
>
Any idea?

>
>
Thanks.

>

>
>
On 16/02/2011 14:05, Carsten Grzemba wrote:

> Hi,
>
> can you see anything in the logs of the DS:
> /var/log/dirserv/slapd-<inst>/access
> /var/log/dirserv/slapd-<inst>/error
>
> Regards,
> Carsten
>
> ----- Ursprüngliche Nachricht -----
> Von: Rafael Cervillera <rccortes@ujaen.es>
> Datum: Mittwoch, 16. Februar 2011, 12:53
> Betreff: [389-users] Trying to delete one entry
> An: "General discussion list for the 389 Directory server project." <389-users@lists.fedoraproject.org>

> Hi, gurus!
> We have a 389DS and the following problem deleting an entry.
> Our server has multiple databases and the problem only appears
> in one,
> we can remove entries from cn=users but not from other subtree.
> All databases are not in read only mode.
>
> ldapdelete shows an ldap_delete: Operations error (1).
> In another subtree we can delete any entry without problems.
>
> In the inspect of the ACIs we haven't found anything wrong (same
> ACI in
> both subtrees).
>
> Attached is the modified output of ldapdelete with debug mode
> 2147483647.
>
> Thanks in advance.
>
> --
>
>
>

> --
>

> 389 users mailing list
> 389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users

>
> --
> 389 users mailing list
> 389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users

>

> --
> ____ __
> | _ __ _ / _| __ _
> | |_) / _` | |_ / _` |
> | _ < (_| | _| (_| |
> |_| \_\__,_|_| \__,_|
>

> --
> 389 users mailing list
> 389-users@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/389-users
--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users

02-16-2011, 03:28 PM

On 02/16/2011 04:52 AM, Rafael Cervillera wrote:
Hi,
gurus!

We have a 389DS and the following problem deleting an entry.

Our server has multiple databases and the problem only appears in
one, we can remove entries from cn=users but not from other
subtree.

All databases are not in read only mode.

What is your 389 ds server platform?* What is your 389-ds-base
version?

ldapdelete shows an ldap_delete: Operations error (1).

In another subtree we can delete any entry without problems.

In the inspect of the ACIs we haven't found anything wrong (same
ACI in both subtrees).

Attached is the modified output of ldapdelete with debug mode
2147483647.

Thanks in advance.

--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users

--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users

02-16-2011, 03:42 PM

> What is your 389 ds server platform? What is your 389-ds-base version?

Hi, I am coworker of Rafael, we updated the server to 389 Directory Server
1.2.7.5 15 days ago on a Centos 5.5 Server.

--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users

02-16-2011, 03:53 PM

On 02/16/2011 09:42 AM, julopez@ujaen.es wrote:
>> What is your 389 ds server platform? What is your 389-ds-base version?
> Hi, I am coworker of Rafael, we updated the server to 389 Directory Server
> 1.2.7.5 15 days ago on a Centos 5.5 Server.
32-bit or 64-bit?
Any chance you could try to reproduce with the 1.2.8 alpha 2?
Try to reproduce the problem with the TRACE error log level - it will be
very verbose and slow the server down, but it should help us pinpoint
the problem - http://directory.fedoraproject.org/wiki/FAQ#Troubleshooting
> --
> 389 users mailing list
> 389-users@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/389-users

--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users

02-16-2011, 04:00 PM

Centos 5.5 64 bits.

Also the system is in production I will do a backup and try with 1.2.8
Alpha 2 with debugging tomorrow at work.

Thanks in advance.

> On 02/16/2011 09:42 AM, julopez@ujaen.es wrote:
>>> What is your 389 ds server platform? What is your 389-ds-base version?
>> Hi, I am coworker of Rafael, we updated the server to 389 Directory
>> Server
>> 1.2.7.5 15 days ago on a Centos 5.5 Server.
> 32-bit or 64-bit?
> Any chance you could try to reproduce with the 1.2.8 alpha 2?
> Try to reproduce the problem with the TRACE error log level - it will be
> very verbose and slow the server down, but it should help us pinpoint
> the problem - http://directory.fedoraproject.org/wiki/FAQ#Troubleshooting
>> --
>> 389 users mailing list
>> 389-users@lists.fedoraproject.org
>> https://admin.fedoraproject.org/mailman/listinfo/389-users
>
>

--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users