Re: [Installer] Possible Bug - apacheds start fails because it cannot create the rolling log - Ole Ersoy - org.apache.directory.dev

9 messages in org.apache.directory.devRe: [Installer] Possible Bug - apache...

From	Sent On	Attachments
Ole Ersoy	May 13, 2007 2:39 pm
Emmanuel Lecharny	May 13, 2007 9:58 pm
Andrew C. Oliver	May 13, 2007 11:20 pm
Emmanuel Lecharny	May 14, 2007 1:54 am
Andrew C. Oliver	May 14, 2007 7:14 am
Ole Ersoy	May 14, 2007 7:27 am
Ole Ersoy	May 14, 2007 7:34 am
Emmanuel Lecharny	May 14, 2007 7:54 am
Ole Ersoy	May 14, 2007 8:17 am

	Permalink for this message Paste this link in email or IM:
	Permalink for this thread Paste this link in email or IM:
	Atom feed for this thread Paste this URL into your reader:

Subject:	Re: [Installer] Possible Bug - apacheds start fails because it cannot create the rolling log	Actions...
From:	Ole Ersoy (ole....@gmail.com)
Date:	May 14, 2007 7:27:47 am
List:	org.apache.directory.dev

Hey Emmanuel,

I think I found the cause. I'll append this message to the JIRA you sent me.

The startup code (Shell script) for the start argument to apacheds looks like this:

$DAEMON_HOME/apacheds \ -user $APACHEDS_USER \ -home $JAVA_HOME \ -Djava.io.tmpdir=$TMP_DIR \ -Dlog4j.configuration=file://$SERVER_HOME/conf/log4j.properties\ -Xms384m -Xmx384m \ -pidfile $PID_FILE \ -outfile $SERVER_HOME/var/log/apacheds-stdout.log \ -errfile $SERVER_HOME/var/log/apacheds-stderr.log \ -cp $CLASSPATH \ org.apache.directory.daemon.JsvcBootstrapper \ $APACHEDS_HOME start

And the debug looks like this:

$JAVA_HOME/bin/java\ -Dlog4j.configuration=file://$SERVER_HOME/conf/log4j.properties\ -Xms384m -Xmx384m \ -Dcom.sun.management.jmxremote \ -Xdebug -Xnoagent -Djava.compiler=NONE\ -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=$DEBUG_PORT\ -jar $DAEMON_HOME/bootstrapper.jar \ $APACHEDS_HOME start ;;

*) echo "Usage apacheds [start|stop|debug]" exit 1;;

I looked in /etc/passwd and I don't have a user called "apacheds". I need to look at the apacheds script in more detail, but I'm assuming $APACHEDS_USER refers to such a user. The RPM spec file should have created this user when ADS was installed. Also, all the files are still owned by root post install, so the rpm spec file needs to change over the ownership in the install section of the spec.

I'll be double checking all this when I finish up the installer work.

Anyways, I removed the -user option from the shell script and now I can start and stop fine.

Cheers, - Ole

Emmanuel Lecharny wrote:

Andy,

I think you have missed something : Ole is starting the server *as root*. There is another issue, and we have to figure out what it is

Ole, I have found a JIRA I filled weeks ago which has been closed : https://issues.apache.org/jira/browse/DIRSERVER-862

Can you check if this is exactly the same problem you have, and if so repoen the issue ?

Thanks !

On 5/14/07, *Andrew C. Oliver* <acol...@apache.org <mailto:acol...@apache.org>> wrote:

this is pretty simply caused by the RPM command running as root and then the dir is owned by root...then if you start it as another user, that user doesn't have permission (and shouldn't) to the dir.

If you install as root (with RPM you have to) you need to run as root or the RPM needs to change permissions to a user which means it pretty much has to create the user.

-Andy

Emmanuel Lecharny wrote: > Hi Ole, > > can you fill a JIRA for this issue? > > Thanks ! > > On 5/13/07, Ole Ersoy <ole....@gmail.com <mailto:ole....@gmail.com>> wrote: >> >> This is interesting. >> >> After installing a fresh RPM (And deleting the old files >> manually) >> if I try to start ADS as root using >> >> /etc/init.d/apacheds start >> I get an OK but the server just exits right >> away. >> >> I think the reason is this: >> >> log4j:ERROR setFile(null,true) call failed. >> java.io.FileNotFoundException: apacheds-rolling.log (Permission denied) >> at java.io.FileOutputStream.openAppend(Native Method) >> >> So somehow it's not able to create the rolling log. I verified >> this by looking in /usr/local/apacheds-1.5.0 / >> and there's no apacheds-rolling.log >> >> However if I start the server like this: >> /etc/init.d/apacheds debug >> >> it starts fine. >> >> I thought this was because it prints the log >> to the screen so that it does not attempt to open it. >> However it's also able to create the rolling log now. >> >> I verified this. /usr/local/apacheds-1.5.0/apacheds-rolling.log >> exists. >> >> I'm surprised that only I'm getting this though. I'm running >> Fedora 6 x86_64. >> >> Cheers, >> - Ole >> >> > >

	Start a set with this search
	Include this search in one of my sets
	Exclude this search from one of my sets
	Permalink to these results Paste this link in email or IM:
	Atom feed for tracking future search results Paste this URL into your reader: