On Wed, Jul 17, 2013 at 12:06 AM, Nick Duan wrote:
> Thanks! But where could the file name discrepancies be? Is there any
> way to run apacheds in debug mode?
>
check the .ldif files present in
/instances/default/partitions/schema
(I assumed that your instance name is "default" if not replace
Thanks! But where could the file name discrepancies be? Is there any way to
run apacheds in debug mode?
Nick
-Original Message-
From: Emmanuel Lécharny [mailto:elecha...@gmail.com]
Sent: Tuesday, July 16, 2013 11:23 AM
To: users@directory.apache.org
Subject: Re: Redeploying ApacheDS
Yes, we use tar.gz to bundle the entire apacheds directory before moving to
linux.
The version of ApacheDS is M8. I think it may not be related to version
No. but probably related to the file name problem that Emmanuel mentioned in
his response...
Thanks!
Nick
-Original Message-
From
What version of ApacheDS are you using?
Looking at the stacktrace and line numbers, it doesn't seem to be the latest
version.
I presume you used either the zip or tar.gz ApacheDS installer. Is that right ?
Regards,
Pierre-Arnaud
On 16 juil. 2013, at 17:23, Emmanuel Lécharny wrote:
> Le 7/16
Le 7/16/13 4:53 PM, Nick Duan a écrit :
> We created ApacheDS LDAP entries on Mac and running without any problems.
> When I redeployed the same installation on Linux (packaged the entire
> apacheds directory into a tar.gz file), I got the following exception.
> However, the same installatio
We created ApacheDS LDAP entries on Mac and running without any problems.
When I redeployed the same installation on Linux (packaged the entire apacheds
directory into a tar.gz file), I got the following exception. However, the
same installation can be deployed to another Mac without any pro
