You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by St...@brown.edu on 2005/10/30 16:59:03 UTC
newbie question, getting started
I'm using Mac IS X 10.4, with java 1.5.
I downloaded apacheDS 0.9.2, exploded it, and started it (without
doing anything else to configure it...) .
at the bottom of this note, I've pasted in the console output --
should I be concerned about any of the warnings?
the ldap server seems to be listening on port 389 --
>root# lsof -i -n -P
>COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
>java 28672 root 26u IPv6 0x02f02ba0 0t0 TCP *:389 (LISTEN)
>java 28672 root 28u IPv6 0x02f04820 0t0 TCP
>[::1]:60892->[::1]:60891 (TIME_WAIT)
>iTunes 28943 stc 17u IPv4 0x036bf980 0t0 TCP *:3689 (LISTEN)
also -- I tried using jxplorer to connect to and query the ldap
server (using it from the same machine where apacheds is running),
but it encounters connection errors -- suggestions on how jxplorer
should be configured?
thanks for your patience......
steven-carmodys-imac-g5:/Users/stc/Progs/ApacheDS/apacheds-0.9.2
root# java -jar apacheds-main-0.9.2.jar
SLF4J built for org.slf4j.impl.Log4jLoggerFA
log4j:WARN No appenders could be found for logger
(org.apache.ldap.server.ServerMain).
log4j:WARN Please initialize the log4j system properly.
Exception in thread "main" javax.naming.NoPermissionException: Only
'uid=admin,ou=system' can initiate the first run.
at
org.apache.ldap.server.jndi.DefaultContextFactoryService.checkPermissionToCreateBootstrapEntries(DefaultContextFactoryService.java:578)
at
org.apache.ldap.server.jndi.DefaultContextFactoryService.createBootstrapEntries(DefaultContextFactoryService.java:387)
at
org.apache.ldap.server.jndi.DefaultContextFactoryService.startup(DefaultContextFactoryService.java:197)
at
org.apache.ldap.server.jndi.AbstractContextFactory.getInitialContext(AbstractContextFactory.java:99)
at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at
javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:82)
at org.apache.ldap.server.ServerMain.main(ServerMain.java:76)
Re: newbie question, getting started
Posted by Alex Karasulu <ao...@bellsouth.net>.
Steven_Carmody@brown.edu wrote:
> At 6:08 PM +0100 10/30/05, Emmanuel Lecharny wrote:
>
...
> javax.naming.NamingException: [LDAP: error code 80 - Bind failed:
> org.apache.ldap.common.exception.LdapConfigurationException: Failed to
> bind the LDAP protocol service to the service registry: (SOCKET, ldap,
> 0.0.0.0/0.0.0.0:389) [Root exception is java.net.BindException:
> Address already in use]
...
Looks like you have a server running on 389. Also you need not explode
the jar. You can run it via java -jar ${path-to-jar}. If you want to
run it on any other port try to editing the server.xml and running the
server with the following server.xml option.
java -jar ${path-to-jar} ${path-to-server.xml}
For more info take a look here more for running the server although it
includes how to build it:
http://directory.apache.org/subprojects/apacheds/users/building.html
Look here for info on how to authenticate (bind) as admin or non-superuser:
http://directory.apache.org/subprojects/apacheds/users/authentication.html
Good luck,
Alex
Re: newbie question, getting started
Posted by St...@brown.edu.
At 6:08 PM +0100 10/30/05, Emmanuel Lecharny wrote:
>Hi Steve,
>
>I bet that the first exception is just here to tell that the
>log4j.property file is not present. Nothing to worry about.
>
>Using Jxplorer is a good choice, but you have to use the following
>parameters :
>
>base DN : ou=system
>
>Security level : User + Password
>User DN : uid=admin,ou=system
>Password : secret
>
>Tell us if it does not work !
>
thanks very much!
it does if I specify host=localhost; if I enter the dns name for my
desktop machine, jxplorer displays this error:
javax.naming.NamingException: [LDAP: error code 80 - Bind failed:
org.apache.ldap.common.exception.LdapConfigurationException: Failed
to bind the LDAP protocol service to the service registry: (SOCKET,
ldap, 0.0.0.0/0.0.0.0:389) [Root exception is java.net.BindException:
Address already in use]
at
org.apache.ldap.server.jndi.ServerContextFactory.startLdapProtocol(ServerContextFactory.java:220)
at
org.apache.ldap.server.jndi.ServerContextFactory.afterStartup(ServerContextFactory.java:108)
at
org.apache.ldap.server.jndi.DefaultContextFactoryService.startup(DefaultContextFactoryService.java:204)
at
org.apache.ldap.server.jndi.AbstractContextFactory.getInitialContext(AbstractContextFactory.java:99)
at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
at javax.naming.InitialContext.init(InitialContext.java:223)
at
javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:134)
at
org.apache.ldap.server.protocol.BindHandler.messageReceived(BindHandler.java:131)
at
org.apache.mina.protocol.handler.DemuxingProtocolHandler.messageReceived(DemuxingProtocolHandler.java:70)
at
org.apache.mina.protocol.AbstractProtocolFilterChain$2.messageReceived(AbstractProtocolFilterChain.java:149)
at
org.apache.mina.protocol.AbstractProtocolFilterChain.callNextMessageReceived(AbstractProtocolFilterChain.java:365)
at
org.apache.mina.protocol.AbstractProtocolFilterChain.access$1000(AbstractProtocolFilterChain.java:50)
at
org.apache.mina.protocol.AbstractProtocolFilterChain$Entry$1.messageReceived(AbstractProtocolFilterChain.java:524)
at
org.apache.mina.protocol.AbstractProtocolFilterChain$1.messageReceived(AbstractProtocolFilterChain.java:99)
at
org.apache.mina.protocol.AbstractProtocolFilterChain.callNextMessageReceived(AbstractProtocolFilterChain.java:365)
at
org.apache.mina.protocol.AbstractProtocolFilterChain.messageReceived(AbstractProtocolFilterChain.java:356)
at
org.apache.mina.protocol.ProtocolSessionManagerFilterChain$1.messageReceived(ProtocolSessionManagerFilterChain.java:77)
at
org.apache.mina.protocol.AbstractProtocolFilterChain.callNextMessageReceived(AbstractProtocolFilterChain.java:365)
at
org.apache.mina.protocol.AbstractProtocolFilterChain.access$1000(AbstractProtocolFilterChain.java:50)
at
org.apache.mina.protocol.AbstractProtocolFilterChain$Entry$1.messageReceived(AbstractProtocolFilterChain.java:524)
at
org.apache.mina.protocol.filter.ProtocolThreadPoolFilter.processEvent(ProtocolThreadPoolFilter.java:108)
at
org.apache.mina.util.BaseThreadPool$Worker.processEvents(BaseThreadPool.java:393)
at
org.apache.mina.util.BaseThreadPool$Worker.run(BaseThreadPool.java:333)
Caused by: java.net.BindException: Address already in use
at sun.nio.ch.Net.bind(Native Method)
at
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:119)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
at
org.apache.mina.io.socket.SocketAcceptor.registerNew(SocketAcceptor.java:362)
at
org.apache.mina.io.socket.SocketAcceptor.access$800(SocketAcceptor.java:46)
at
org.apache.mina.io.socket.SocketAcceptor$Worker.run(SocketAcceptor.java:238)
BindRequest =
org.apache.ldap.common.message.BindRequestImpl@79688d]
Re: newbie question, getting started
Posted by Emmanuel Lecharny <el...@apache.org>.
Hi Steve,
I bet that the first exception is just here to tell that the
log4j.property file is not present. Nothing to worry about.
Using Jxplorer is a good choice, but you have to use the following
parameters :
base DN : ou=system
Security level : User + Password
User DN : uid=admin,ou=system
Password : secret
Tell us if it does not work !
-- Emmanuel
On Sun, 2005-10-30 at 11:59 -0400, Steven_Carmody@brown.edu wrote:
> I'm using Mac IS X 10.4, with java 1.5.
>
> I downloaded apacheDS 0.9.2, exploded it, and started it (without
> doing anything else to configure it...) .
>
> at the bottom of this note, I've pasted in the console output --
> should I be concerned about any of the warnings?
>
> the ldap server seems to be listening on port 389 --
>
> >root# lsof -i -n -P
> >COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
> >java 28672 root 26u IPv6 0x02f02ba0 0t0 TCP *:389 (LISTEN)
> >java 28672 root 28u IPv6 0x02f04820 0t0 TCP
> >[::1]:60892->[::1]:60891 (TIME_WAIT)
> >iTunes 28943 stc 17u IPv4 0x036bf980 0t0 TCP *:3689 (LISTEN)
>
> also -- I tried using jxplorer to connect to and query the ldap
> server (using it from the same machine where apacheds is running),
> but it encounters connection errors -- suggestions on how jxplorer
> should be configured?
>
> thanks for your patience......
>
> steven-carmodys-imac-g5:/Users/stc/Progs/ApacheDS/apacheds-0.9.2
> root# java -jar apacheds-main-0.9.2.jar
> SLF4J built for org.slf4j.impl.Log4jLoggerFA
> log4j:WARN No appenders could be found for logger
> (org.apache.ldap.server.ServerMain).
> log4j:WARN Please initialize the log4j system properly.
> Exception in thread "main" javax.naming.NoPermissionException: Only
> 'uid=admin,ou=system' can initiate the first run.
> at
> org.apache.ldap.server.jndi.DefaultContextFactoryService.checkPermissionToCreateBootstrapEntries(DefaultContextFactoryService.java:578)
> at
> org.apache.ldap.server.jndi.DefaultContextFactoryService.createBootstrapEntries(DefaultContextFactoryService.java:387)
> at
> org.apache.ldap.server.jndi.DefaultContextFactoryService.startup(DefaultContextFactoryService.java:197)
> at
> org.apache.ldap.server.jndi.AbstractContextFactory.getInitialContext(AbstractContextFactory.java:99)
> at
> javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
> at
> javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
> at javax.naming.InitialContext.init(InitialContext.java:223)
> at javax.naming.InitialContext.<init>(InitialContext.java:197)
> at
> javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:82)
> at org.apache.ldap.server.ServerMain.main(ServerMain.java:76)
> ---------------------------------------------------------------------------------------
> Wanadoo vous informe que cet e-mail a ete controle par l'anti-virus mail.
> Aucun virus connu a ce jour par nos services n'a ete detecte.
>
>
>