Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of nickfaiz@gmail.com designates
 64.233.162.207 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=RBzd89Q0EmmcZmSkXf1yN8a5SyF8D4rYVQEwH3sg28HaVOudUH7M/RFf1vrW7ylia82KLhBVE7vnY4r+3GI0u7G70ELDFTM2bUlo5oaxrLSmNrAlbih1Dvj6Nh1O7EWCVZsOfOONaKPfUElwTp//QvmtHnGj6kc2GeMRBBmCokA=
Message-ID: <8a8dec4005082815072087fea0@mail.gmail.com>
Date: Mon, 29 Aug 2005 08:07:15 +1000
From: Nick Faiz <nickfaiz@gmail.com>
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: Re: Only 'uid=admin,ou=system' can initiate the first run.
In-Reply-To: <4311F06D.2040800@bellsouth.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <4311D47B.3070408@labeo.de> <4311F06D.2040800@bellsouth.net>

Hi Stefan,

There is a standalone configuration which doesnt require that a
server.xml be passed in on the command line - it defaults to using the
standard one if no argument is present. It can be built using the
standalone maven goal in the main module.

Cheers,
Nick

On 8/29/05, Alex Karasulu <aok123@bellsouth.net> wrote:
> Stefan Zoerner wrote:
>=20
> > Hi all!
> >
> > If I use a current apacheds-main-0.9.2-SNAPSHOT.jar and execute a simpl=
e
> >
> > java -jar apacheds-main-0.9.2-SNAPSHOT.jar
> >
> > in a fresh directory, I get the following exception on the cmdline:
> >
> > Exception in thread "main" javax.naming.NoPermissionException: Only
> > 'uid=3Dadmin,ou=3Dsystem' can initiate the first run.
> >
> This is because without a server.xml saying the user starting the server
> is the admin it defaults to an anonymous user for startup.  This is not
> allowed when starting up the server.  Only the admin has this permission.
>=20
> > After this message, the server starts and after some time clients are
> > able to connect. If I stop the server and restart it the same way (it
> > is not the first run, partition is available on disk), the error does
> > not occur.
> >
> > Has anyone faced this problem as well? Maybe it is not an error at
> > all, but an operating error by me. But if it is always present (I have
> > tested this with J2SE 1.4 and 5.0 on Windows and Solaris, I got it
> > everytime) the message is probably a shock for newbies.
> >
> Well Trustin made some changes after I had experimented with this
> policy.  Perhaps Trustin can help clarify the effects of these changes
> on startup policy.
>=20
> > Should I raise an issue at JIRA for this?
> >
> > Btw.: This does not occur if I use my server.xml within the command
> > line for a first run. Therefore I guess its a problem in the default
> > configuration.
>=20
>=20
> Exactly.
>=20
> Alex
>=20
>