Am I doing something wrong? Here is an example:
$ ldapmodify -c -x -D 'cn=config' -W Enter LDAP Password: <password> dn: olcDatabase={0}config,cn=config changetype: modify delete: olcSizeLimit - modifying entry "olcDatabase={0}config,cn=config" ldap_modify: No such attribute (16) additional info: modify/delete: olcSizeLimit: no such attribute
Ori Bani wrote:
Am I doing something wrong? Here is an example:
$ ldapmodify -c -x -D 'cn=config' -W Enter LDAP Password: <password> dn: olcDatabase={0}config,cn=config changetype: modify delete: olcSizeLimit
modifying entry "olcDatabase={0}config,cn=config" ldap_modify: No such attribute (16) additional info: modify/delete: olcSizeLimit: no such attribute
Option -c does not mean that you can override any server-side checking. It just means that processing the LDIF input is continued.
In your case entry olcDatabase={0}config,cn=config simply does not contain attribute 'olcSizeLimit' which is what the error message says.
Ciao, Michael.
Thanks so much for the reply. Can you please clarify --
Am I doing something wrong? Here is an example:
$ ldapmodify -c -x -D 'cn=config' -W Enter LDAP Password: <password> dn: olcDatabase={0}config,cn=config changetype: modify delete: olcSizeLimit
modifying entry "olcDatabase={0}config,cn=config" ldap_modify: No such attribute (16) additional info: modify/delete: olcSizeLimit: no such attribute
Option -c does not mean that you can override any server-side checking. It just means that processing the LDIF input is continued.
In your case entry olcDatabase={0}config,cn=config simply does not contain attribute 'olcSizeLimit' which is what the error message says.
I'd be fine if that was the case, but I'm not seeing it work as you suggest (processing does NOT continue). Surely I'm doing something wrong. Here is an example of a situation where the subsequest action in the LDIF is ignored after the error:
$ ldapmodify -c -x -D 'cn=config' -W Enter LDAP Password: <password> dn: olcDatabase={0}config,cn=config changetype: modify delete: olcSizeLimit - add: olcSizeLimit olcSizeLimit: 250 - modifying entry "olcDatabase={0}config,cn=config" ldap_modify: No such attribute (16) additional info: modify/delete: olcSizeLimit: no such attribute
$ ldapsearch -x -D 'cn=config' -b 'olcDatabase={0}config,cn=config' -W olcSizeLimit Enter LDAP Password: <password> # extended LDIF # # LDAPv3 # base <olcDatabase={0}config,cn=config> with scope subtree # filter: (objectclass=*) # requesting: olcSizeLimit #
# {0}config, config dn: olcDatabase={0}config,cn=config
# search result search: 2 result: 0 Success
# numResponses: 2 # numEntries: 1
Ori Bani wrote:
Thanks so much for the reply. Can you please clarify --
Am I doing something wrong? Here is an example:
$ ldapmodify -c -x -D 'cn=config' -W Enter LDAP Password: <password> dn: olcDatabase={0}config,cn=config changetype: modify delete: olcSizeLimit
modifying entry "olcDatabase={0}config,cn=config" ldap_modify: No such attribute (16) additional info: modify/delete: olcSizeLimit: no such attribute
Option -c does not mean that you can override any server-side checking. It just means that processing the LDIF input is continued.
In your case entry olcDatabase={0}config,cn=config simply does not contain attribute 'olcSizeLimit' which is what the error message says.
I'd be fine if that was the case, but I'm not seeing it work as you suggest (processing does NOT continue). Surely I'm doing something wrong. Here is an example of a situation where the subsequest action in the LDIF is ignored after the error:
$ ldapmodify -c -x -D 'cn=config' -W Enter LDAP Password: <password> dn: olcDatabase={0}config,cn=config changetype: modify delete: olcSizeLimit
add: olcSizeLimit olcSizeLimit: 250
modifying entry "olcDatabase={0}config,cn=config" ldap_modify: No such attribute (16) additional info: modify/delete: olcSizeLimit: no such attribute
Why don't you just use this if attribute 'olcSizeLimit' is not in the entry yet?
dn: olcDatabase={0}config,cn=config changetype: modify add: olcSizeLimit olcSizeLimit: 250 -
After all -c works as expected: If you have more than one records in your LDIF file it will try to process the next one.
Ciao, Michael.
On Mon, Jan 21, 2013 at 12:42 PM, Michael Ströder michael@stroeder.com wrote:
Ori Bani wrote:
Thanks so much for the reply. Can you please clarify --
Am I doing something wrong? Here is an example:
$ ldapmodify -c -x -D 'cn=config' -W Enter LDAP Password: <password> dn: olcDatabase={0}config,cn=config changetype: modify delete: olcSizeLimit
modifying entry "olcDatabase={0}config,cn=config" ldap_modify: No such attribute (16) additional info: modify/delete: olcSizeLimit: no such attribute
Option -c does not mean that you can override any server-side checking. It just means that processing the LDIF input is continued.
In your case entry olcDatabase={0}config,cn=config simply does not contain attribute 'olcSizeLimit' which is what the error message says.
I'd be fine if that was the case, but I'm not seeing it work as you suggest (processing does NOT continue). Surely I'm doing something wrong. Here is an example of a situation where the subsequest action in the LDIF is ignored after the error:
$ ldapmodify -c -x -D 'cn=config' -W Enter LDAP Password: <password> dn: olcDatabase={0}config,cn=config changetype: modify delete: olcSizeLimit
add: olcSizeLimit olcSizeLimit: 250
modifying entry "olcDatabase={0}config,cn=config" ldap_modify: No such attribute (16) additional info: modify/delete: olcSizeLimit: no such attribute
Why don't you just use this if attribute 'olcSizeLimit' is not in the entry yet?
Part of an automated system. If -c worked as the man page states, this should not be a problem.
dn: olcDatabase={0}config,cn=config changetype: modify add: olcSizeLimit olcSizeLimit: 250
After all -c works as expected: If you have more than one records in your LDIF file it will try to process the next one.
I just showed you that this is not true in my case. Why are you saying this? What am I not understanding?
On Mon, Jan 21, 2013 at 12:45 PM, Ori Bani oribani@gmail.com wrote:
On Mon, Jan 21, 2013 at 12:42 PM, Michael Ströder michael@stroeder.com wrote:
Ori Bani wrote:
Thanks so much for the reply. Can you please clarify --
Am I doing something wrong? Here is an example:
$ ldapmodify -c -x -D 'cn=config' -W Enter LDAP Password: <password> dn: olcDatabase={0}config,cn=config changetype: modify delete: olcSizeLimit
modifying entry "olcDatabase={0}config,cn=config" ldap_modify: No such attribute (16) additional info: modify/delete: olcSizeLimit: no such attribute
Option -c does not mean that you can override any server-side checking. It just means that processing the LDIF input is continued.
In your case entry olcDatabase={0}config,cn=config simply does not contain attribute 'olcSizeLimit' which is what the error message says.
I'd be fine if that was the case, but I'm not seeing it work as you suggest (processing does NOT continue). Surely I'm doing something wrong. Here is an example of a situation where the subsequest action in the LDIF is ignored after the error:
$ ldapmodify -c -x -D 'cn=config' -W Enter LDAP Password: <password> dn: olcDatabase={0}config,cn=config changetype: modify delete: olcSizeLimit
add: olcSizeLimit olcSizeLimit: 250
modifying entry "olcDatabase={0}config,cn=config" ldap_modify: No such attribute (16) additional info: modify/delete: olcSizeLimit: no such attribute
Why don't you just use this if attribute 'olcSizeLimit' is not in the entry yet?
Part of an automated system. If -c worked as the man page states, this should not be a problem.
dn: olcDatabase={0}config,cn=config changetype: modify add: olcSizeLimit olcSizeLimit: 250
After all -c works as expected: If you have more than one records in your LDIF file it will try to process the next one.
I just showed you that this is not true in my case. Why are you saying this? What am I not understanding?
Ah, next *entry* not next line(s).
That was my misunderstanding - I need to separate each modify action into a whole separate entry:
$ ldapmodify -c -x -D 'cn=config' -W Enter LDAP Password: <password> dn: olcDatabase={0}config,cn=config changetype: modify delete: olcSizeLimit
modifying entry "olcDatabase={0}config,cn=config" ldap_modify: No such attribute (16) additional info: modify/delete: olcSizeLimit: no such attribute
dn: olcDatabase={0}config,cn=config changetype: modify add: olcSizeLimit olcSizeLimit: 250
modifying entry "olcDatabase={0}config,cn=config"
Ori Bani wrote:
Ah, next *entry* not next line(s).
That was my misunderstanding - I need to separate each modify action into a whole separate entry:
$ ldapmodify -c -x -D 'cn=config' -W Enter LDAP Password: <password> dn: olcDatabase={0}config,cn=config changetype: modify delete: olcSizeLimit
modifying entry "olcDatabase={0}config,cn=config" ldap_modify: No such attribute (16) additional info: modify/delete: olcSizeLimit: no such attribute
dn: olcDatabase={0}config,cn=config changetype: modify add: olcSizeLimit olcSizeLimit: 250
modifying entry "olcDatabase={0}config,cn=config"
While this works in this case since 'olcSizeLimit' is optional (MAY attribute) in each referencing object class it's not a general solution pattern in case an attribute to be replaced is an mandantory (MUST attribute) in the schema.
This works better:
dn: olcDatabase={0}config,cn=config changetype: modify replace: olcSizeLimit olcSizeLimit: 250 -
Ciao, Michael.
On Mon, Jan 21, 2013 at 1:26 PM, Michael Ströder michael@stroeder.com wrote:
Ori Bani wrote:
Ah, next *entry* not next line(s).
That was my misunderstanding - I need to separate each modify action into a whole separate entry:
$ ldapmodify -c -x -D 'cn=config' -W Enter LDAP Password: <password> dn: olcDatabase={0}config,cn=config changetype: modify delete: olcSizeLimit
modifying entry "olcDatabase={0}config,cn=config" ldap_modify: No such attribute (16) additional info: modify/delete: olcSizeLimit: no such attribute
dn: olcDatabase={0}config,cn=config changetype: modify add: olcSizeLimit olcSizeLimit: 250
modifying entry "olcDatabase={0}config,cn=config"
While this works in this case since 'olcSizeLimit' is optional (MAY attribute) in each referencing object class it's not a general solution pattern in case an attribute to be replaced is an mandantory (MUST attribute) in the schema.
This works better:
dn: olcDatabase={0}config,cn=config changetype: modify replace: olcSizeLimit olcSizeLimit: 250
Newbie mistake, obviously. Of course this is the proper solution. Thank you sincerely.
Ori Bani wrote:
On Mon, Jan 21, 2013 at 12:42 PM, Michael Ströder michael@stroeder.com wrote:
Ori Bani wrote:
Thanks so much for the reply. Can you please clarify --
Am I doing something wrong? Here is an example:
$ ldapmodify -c -x -D 'cn=config' -W Enter LDAP Password: <password> dn: olcDatabase={0}config,cn=config changetype: modify delete: olcSizeLimit
modifying entry "olcDatabase={0}config,cn=config" ldap_modify: No such attribute (16) additional info: modify/delete: olcSizeLimit: no such attribute
Option -c does not mean that you can override any server-side checking. It just means that processing the LDIF input is continued.
In your case entry olcDatabase={0}config,cn=config simply does not contain attribute 'olcSizeLimit' which is what the error message says.
I'd be fine if that was the case, but I'm not seeing it work as you suggest (processing does NOT continue). Surely I'm doing something wrong. Here is an example of a situation where the subsequest action in the LDIF is ignored after the error:
$ ldapmodify -c -x -D 'cn=config' -W Enter LDAP Password: <password> dn: olcDatabase={0}config,cn=config changetype: modify delete: olcSizeLimit
add: olcSizeLimit olcSizeLimit: 250
modifying entry "olcDatabase={0}config,cn=config" ldap_modify: No such attribute (16) additional info: modify/delete: olcSizeLimit: no such attribute
Why don't you just use this if attribute 'olcSizeLimit' is not in the entry yet?
Part of an automated system.
Then fix that system.
If -c worked as the man page states, this should not be a problem.
You misinterpret completely what the man page says about option -c.
dn: olcDatabase={0}config,cn=config changetype: modify add: olcSizeLimit olcSizeLimit: 250
After all -c works as expected: If you have more than one records in your LDIF file it will try to process the next one.
I just showed you that this is not true in my case. Why are you saying this? What am I not understanding?
Read RFC 2849 about how LDIF is structured. And then understand that your LDIF change record leads to a *single* modify request which obviously fails because of 'olcSizeLimit' not existing (which is a feature not a bug).
Ciao, Michael.
On Mon, Jan 21, 2013 at 12:50 PM, Michael Ströder michael@stroeder.com wrote:
Ori Bani wrote:
On Mon, Jan 21, 2013 at 12:42 PM, Michael Ströder michael@stroeder.com wrote:
Ori Bani wrote:
Thanks so much for the reply. Can you please clarify --
Am I doing something wrong? Here is an example:
$ ldapmodify -c -x -D 'cn=config' -W Enter LDAP Password: <password> dn: olcDatabase={0}config,cn=config changetype: modify delete: olcSizeLimit
modifying entry "olcDatabase={0}config,cn=config" ldap_modify: No such attribute (16) additional info: modify/delete: olcSizeLimit: no such attribute
Option -c does not mean that you can override any server-side checking. It just means that processing the LDIF input is continued.
In your case entry olcDatabase={0}config,cn=config simply does not contain attribute 'olcSizeLimit' which is what the error message says.
I'd be fine if that was the case, but I'm not seeing it work as you suggest (processing does NOT continue). Surely I'm doing something wrong. Here is an example of a situation where the subsequest action in the LDIF is ignored after the error:
$ ldapmodify -c -x -D 'cn=config' -W Enter LDAP Password: <password> dn: olcDatabase={0}config,cn=config changetype: modify delete: olcSizeLimit
add: olcSizeLimit olcSizeLimit: 250
modifying entry "olcDatabase={0}config,cn=config" ldap_modify: No such attribute (16) additional info: modify/delete: olcSizeLimit: no such attribute
Why don't you just use this if attribute 'olcSizeLimit' is not in the entry yet?
Part of an automated system.
Then fix that system.
Spare the snide comments.
If -c worked as the man page states, this should not be a problem.
You misinterpret completely what the man page says about option -c.
It's easy to interpret it as I have given the vague quality of the man page.
-c Continuous operation mode. Errors are reported, but ldapmodify will continue with modifications. The default is to exit after reporting an error.
It says nothing about *where* it will continue. Next line, next entry, what? As I've said in my last email, by trial and error, I determined that it continues with the next entry.
dn: olcDatabase={0}config,cn=config changetype: modify add: olcSizeLimit olcSizeLimit: 250
After all -c works as expected: If you have more than one records in your LDIF file it will try to process the next one.
I just showed you that this is not true in my case. Why are you saying this? What am I not understanding?
Read RFC 2849 about how LDIF is structured. And then understand that your LDIF change record leads to a *single* modify request which obviously fails because of 'olcSizeLimit' not existing (which is a feature not a bug).
Is your answer to all OpenLDAP users coming here for assistance really to read the RFC to clarify vague man pages and other misunderstandings? Rather, isn't this community here to help in more productive ways?
Thanks so much for the reply. Can you please clarify --
> Am I doing something wrong? Here is an example: > > $ ldapmodify -c -x -D 'cn=config' -W > Enter LDAP Password: <password> > dn: olcDatabase={0}config,cn=config > changetype: modify > delete: olcSizeLimit > - > modifying entry "olcDatabase={0}config,cn=config" > ldap_modify: No such attribute (16) > additional info: modify/delete: olcSizeLimit: no such attribute
Option -c does not mean that you can override any server-side checking. It just means that processing the LDIF input is continued.
In your case entry olcDatabase={0}config,cn=config simply does not contain attribute 'olcSizeLimit' which is what the error message says.
I'd be fine if that was the case, but I'm not seeing it work as you suggest (processing does NOT continue). Surely I'm doing something wrong. Here is an example of a situation where the subsequest action in the LDIF is ignored after the error:
$ ldapmodify -c -x -D 'cn=config' -W Enter LDAP Password: <password> dn: olcDatabase={0}config,cn=config changetype: modify delete: olcSizeLimit
add: olcSizeLimit olcSizeLimit: 250
modifying entry "olcDatabase={0}config,cn=config" ldap_modify: No such attribute (16) additional info: modify/delete: olcSizeLimit: no such attribute
Why don't you just use this if attribute 'olcSizeLimit' is not in the entry yet?
Part of an automated system.
Then fix that system.
Spare the snide comments.
If -c worked as the man page states, this should not be a problem.
You misinterpret completely what the man page says about option -c.
It's easy to interpret it as I have given the vague quality of the man page.
-c Continuous operation mode. Errors are reported, but ldapmodify will continue with modifications. The default is to exit after reporting an error.
It says nothing about *where* it will continue. Next line, next entry, what? As I've said in my last email, by trial and error, I determined that it continues with the next entry.
dn: olcDatabase={0}config,cn=config changetype: modify add: olcSizeLimit olcSizeLimit: 250
After all -c works as expected: If you have more than one records in your LDIF file it will try to process the next one.
I just showed you that this is not true in my case. Why are you saying this? What am I not understanding?
Read RFC 2849 about how LDIF is structured. And then understand that your LDIF change record leads to a *single* modify request which obviously fails because of 'olcSizeLimit' not existing (which is a feature not a bug).
Is your answer to all OpenLDAP users coming here for assistance really to read the RFC to clarify vague man pages and other misunderstandings? Rather, isn't this community here to help in more productive ways?
BTW, thank you for replying and for the help.
Ori Bani wrote:
On Mon, Jan 21, 2013 at 12:50 PM, Michael Ströder michael@stroeder.com wrote:
Ori Bani wrote:
On Mon, Jan 21, 2013 at 12:42 PM, Michael Ströder michael@stroeder.com wrote:
Ori Bani wrote:
Thanks so much for the reply. Can you please clarify --
> Am I doing something wrong? Here is an example: > > $ ldapmodify -c -x -D 'cn=config' -W > Enter LDAP Password: <password> > dn: olcDatabase={0}config,cn=config > changetype: modify > delete: olcSizeLimit > - > modifying entry "olcDatabase={0}config,cn=config" > ldap_modify: No such attribute (16) > additional info: modify/delete: olcSizeLimit: no such attribute
Option -c does not mean that you can override any server-side checking. It just means that processing the LDIF input is continued.
In your case entry olcDatabase={0}config,cn=config simply does not contain attribute 'olcSizeLimit' which is what the error message says.
I'd be fine if that was the case, but I'm not seeing it work as you suggest (processing does NOT continue). Surely I'm doing something wrong. Here is an example of a situation where the subsequest action in the LDIF is ignored after the error:
$ ldapmodify -c -x -D 'cn=config' -W Enter LDAP Password: <password> dn: olcDatabase={0}config,cn=config changetype: modify delete: olcSizeLimit
add: olcSizeLimit olcSizeLimit: 250
modifying entry "olcDatabase={0}config,cn=config" ldap_modify: No such attribute (16) additional info: modify/delete: olcSizeLimit: no such attribute
Why don't you just use this if attribute 'olcSizeLimit' is not in the entry yet?
Part of an automated system.
Then fix that system.
Spare the snide comments.
This was good advice and not a snide comment.
If -c worked as the man page states, this should not be a problem.
You misinterpret completely what the man page says about option -c.
It's easy to interpret it as I have given the vague quality of the man page.
-c Continuous operation mode. Errors are reported, but ldapmodify will continue with modifications. The default is to exit after reporting an error.
It says nothing about *where* it will continue. Next line, next entry, what? As I've said in my last email, by trial and error, I determined that it continues with the next entry.
Well, because of the LDAP functional model a single LDAP write operation will completely succeed or completely fail. And a single LDIF change record piped to ldapmodify will result in a *single* write operation.
Read RFC 2849 about how LDIF is structured. And then understand that your LDIF change record leads to a *single* modify request which obviously fails because of 'olcSizeLimit' not existing (which is a feature not a bug).
Is your answer to all OpenLDAP users coming here for assistance really to read the RFC to clarify vague man pages and other misunderstandings?
If you're aim is to write an automated system - as you wrote before - you have to understand how LDIF input data is structured and how LDAP operations are processed. Reading RFCs is simply helpful for understanding. So this is simply meant as good advice.
Ciao, Michael.
On Mon, Jan 21, 2013 at 1:09 PM, Michael Ströder michael@stroeder.com wrote:
Ori Bani wrote:
On Mon, Jan 21, 2013 at 12:50 PM, Michael Ströder michael@stroeder.com wrote:
Ori Bani wrote:
On Mon, Jan 21, 2013 at 12:42 PM, Michael Ströder michael@stroeder.com wrote:
Ori Bani wrote:
Thanks so much for the reply. Can you please clarify --
>> Am I doing something wrong? Here is an example: >> >> $ ldapmodify -c -x -D 'cn=config' -W >> Enter LDAP Password: <password> >> dn: olcDatabase={0}config,cn=config >> changetype: modify >> delete: olcSizeLimit >> - >> modifying entry "olcDatabase={0}config,cn=config" >> ldap_modify: No such attribute (16) >> additional info: modify/delete: olcSizeLimit: no such attribute > > Option -c does not mean that you can override any server-side checking. It > just means that processing the LDIF input is continued. > > In your case entry olcDatabase={0}config,cn=config simply does not contain > attribute 'olcSizeLimit' which is what the error message says.
I'd be fine if that was the case, but I'm not seeing it work as you suggest (processing does NOT continue). Surely I'm doing something wrong. Here is an example of a situation where the subsequest action in the LDIF is ignored after the error:
$ ldapmodify -c -x -D 'cn=config' -W Enter LDAP Password: <password> dn: olcDatabase={0}config,cn=config changetype: modify delete: olcSizeLimit
add: olcSizeLimit olcSizeLimit: 250
modifying entry "olcDatabase={0}config,cn=config" ldap_modify: No such attribute (16) additional info: modify/delete: olcSizeLimit: no such attribute
Why don't you just use this if attribute 'olcSizeLimit' is not in the entry yet?
Part of an automated system.
Then fix that system.
Spare the snide comments.
This was good advice and not a snide comment.
OK. But I hope you can see how that can be read both ways. Because I am clearly already trying to create that system in the correct way (i.e., "fix" it), the comment could only be interpreted as snide. I just hope we can interact with common respect here.
If -c worked as the man page states, this should not be a problem.
You misinterpret completely what the man page says about option -c.
It's easy to interpret it as I have given the vague quality of the man page.
-c Continuous operation mode. Errors are reported, but ldapmodify will continue with modifications. The default is to exit after reporting an error.
It says nothing about *where* it will continue. Next line, next entry, what? As I've said in my last email, by trial and error, I determined that it continues with the next entry.
Well, because of the LDAP functional model a single LDAP write operation will completely succeed or completely fail. And a single LDIF change record piped to ldapmodify will result in a *single* write operation.
OK, thank you for the good explanation. I'm not sure if there would be a better way to encapsulate that into the man page or not.
Read RFC 2849 about how LDIF is structured. And then understand that your LDIF change record leads to a *single* modify request which obviously fails because of 'olcSizeLimit' not existing (which is a feature not a bug).
Is your answer to all OpenLDAP users coming here for assistance really to read the RFC to clarify vague man pages and other misunderstandings?
If you're aim is to write an automated system - as you wrote before - you have to understand how LDIF input data is structured and how LDAP operations are processed. Reading RFCs is simply helpful for understanding. So this is simply meant as good advice.
Appreciated. Thanks again for being generous with your time.
openldap-technical@openldap.org
-
Michael Ströder -
Ori Bani