On 13/11/19 7:19 pm, Emmanuel Lécharny wrote:

On 13/11/2019 09:26, Brian Burch wrote:
On 7/11/19 6:35 pm, Emmanuel Lécharny wrote:
Hi Brian,

Hi yet again Emmanuel!

I'm really up the creek without a paddle (does that have a French equivalent? I'm sure you will understand!)

https://www.urbandictionary.com/define.php?term=up%20a%20creek%20without%20a%20paddle


In french : "A poil dans la pampa" (aka "naked in the desert")



I won't give you too much painful history because I hope to make sense of my re-testing once I understand what is going on.

Basically, I generated a case-sensitive ads-partition definition, along with the appropriate ads-contextentry. When I tried ldapmodify (add) for the new entry, it was rejected because one of its attributes was required to be all-lower-case. (After all, dn's are case-insensitive and so my legacy choice of case should be just "eye candy")


DN aren't case insensitive ! A DN depends on each RDN it contains, and each RDN may use a case sensitive AttributeType.



Next, after deciding to KISS, I re-generated an all-lowercase version, but that failed and crashed the AM25 server! It would not restart and still won't at this moment. The error message says there is a missing index entry, but I innocently assumed I would be able to add those later...

I am wondering whether it is actually worth fighting any more. However, I now have a dead server BUT a lot of external mods I don't want to recreate (systemd definitions and dependencies not part of the deb's init.d script setup).

If I could successfully get back to a vanilla server which is currently stopped (the deb starts it during installation!), I could re-run my setup jobs repeatedly until I have something meaningful to document.

I found this interesting blog post (was it you?):-

http://frenchhack.blogspot.com/2016/02/remove-partition-on-apacheds.html


What you can do is to start a fresh server, and add the partition into it.

OTOH, it's all about getting rid of the directories under the partitions/XXX directory (see http://directory.apache.org/apacheds/advanced-ug/2.2-instance-layout.html). If the configuration is correct, those partitions will be recreated at startup.


I immediately realised this "solution" assumed one was using Studio to delete the partition, but (of course) it would not work for me unless I can start the server!!! (Catch 22)

I had some problems building the AM25 from source, so I was lazy in using the deb. Therefore, I have just unpacked the deb offline and looked at its contents. /var/lib/apacheds-2.0.0.AM25/default/ has an unmigrated config.ldif file and an empty partitions directory, which looks like a good starting place to me!

Do you think I can just replace the whole of /var/lib/apacheds-2.0.0.AM25/default/ to get back to an initial configuration?
Yes.

If yes, then I can go around my testing loop quickly, changing one thing at a time, and arrive at a partition which works for me.

Also, it would be useful to put a "wipe and restart" procedure on the wiki for others in the same catch 22 situation...


That's a good suggestion. Could you create a JIRA under https://issues.apache.org/jira/projects/DIR for that ?

Just a quick note to let you know the re-deployment of the /var/lib directory tree, followed by hacking the example entries in config.ldif worked perfectly.

I will try to find time to create the JIRA and send another more detailed email tomorrow. Of course. I'll be delighted to add the "trick" to the wiki soon.

Thanks for your help,

Brian

p.s. you never answered me about the blogger - was/is it you?
Thanks !



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to