[
https://issues.apache.org/jira/browse/DIRSERVER-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny closed DIRSERVER-770.
---
closed
LDIF file import at startup fails
is working fine now...
LDIF file import at startup fails
-
Key: DIRSERVER-770
URL: https://issues.apache.org/jira/browse/DIRSERVER-770
Project: Directory ApacheDS
Issue Type: Bug
Components: ldap
this may work.
I'm sorry, I don't have a W$ box right now, so I can't check your installation.
Anybody ?
LDIF file import at startup fails
-
Key: DIRSERVER-770
URL: http://issues.apache.org/jira/browse/DIRSERVER-770
and apologies for bothering! :-)
LDIF file import at startup fails
-
Key: DIRSERVER-770
URL: http://issues.apache.org/jira/browse/DIRSERVER-770
Project: Directory ApacheDS
Issue Type: Bug
to
figure out what happened, and improve the doco.
What we are going to do is to keep this JIRA opened until we found a W$
computer and try to reproduce the problem.
Is W$ mandatory in yout case ?
LDIF file import at startup fails
-
Key: DIRSERVER-770
to be on Linux. I hope I'll change my platform to Linux soon but I'm
lacking time for transfer. :-)
Thanks!
LDIF file import at startup fails
-
Key: DIRSERVER-770
URL: http://issues.apache.org/jira/browse/DIRSERVER-770
sure you will be able to install and make ADS running
on it.
LDIF file import at startup fails
-
Key: DIRSERVER-770
URL: http://issues.apache.org/jira/browse/DIRSERVER-770
Project: Directory ApacheDS
Issue
LDIF file import at startup fails
-
Key: DIRSERVER-770
URL: http://issues.apache.org/jira/browse/DIRSERVER-770
Project: Directory ApacheDS
Issue Type: Bug
Components: ldap
Affects Versions: 1.0
Issue DIRSERVER-770 created. Test case will follow. Thanks for the link, I am not experienced with Maven so I'll need some time to figure it out.Regards,NGCOn 10/26/06,
Alex Karasulu [EMAIL PROTECTED] wrote:
Sounds like this is a problem with the crap that uses CompoundNameinstead of our
org.apache.directory.server.jndi.ServerContextFactory -
Successful bind of an LDAP Service (10389) is complete.
4732 [main] INFO org.apache.directory.server.Service - server: started in 4731
milliseconds
LDIF file import at startup fails
-
Key: DIRSERVER-770
URL: http
?
LDIF file import at startup fails
-
Key: DIRSERVER-770
URL: http://issues.apache.org/jira/browse/DIRSERVER-770
Project: Directory ApacheDS
Issue Type: Bug
Components: ldap
Affects Versions: 1.0
web site, I tested again
with Goran ldif file and configuration, and everything went fine.
Goran, could you just check that you didn't do the same mistake I did, I mean
using an old version of ADS ?
LDIF file import at startup fails
-
Key
and partitioned) directory? What happens when I try to import LDIF file at startup having already entries in directory? If there is a collision, will import fail after first error or continue to process all entries? Is it configurable?
Regards,NGCOn 10/4/06, Emmanuel Lecharny
[EMAIL PROTECTED]
wrote:Nikola
and there is nothing in log file about it. Only when
the
'version' line is missing, log has an entry saying that the file is
empty.
Another question: should this import be performed only the first time
on a
fresh (not yet created and partitioned) directory? What happens when I
try
to import LDIF file
: should this import be performed only the first time on a fresh (not yet created and partitioned) directory? What happens when I try to import LDIF file at startup having already entries in directory? If
there is a collision, will import fail after first error or continue to process all entries
Nikola Goran Čutura a écrit :
Hi,
Attached is LDIF file generated from JXplorer. I want to import this
file on
DS startup. However, it fails. I also try removing the first entry (com,
example) as it initialy exists but import fails all the same. I also
tried
adding 'changetye: add' but
Also, what error do you get?
Is it a JXplorer error, or a DS error?
cheers,
Chris
Nikola Goran Čutura a écrit :
Hi,
Attached is LDIF file generated from JXplorer. I want to import this file
on
DS startup. However, it fails. I also try removing the first entry (com,
example)
17 matches
Mail list logo