[ https://issues.apache.org/jira/brow...action_12495631 ]

Ole Ersoy commented on DIRSERVER-862:
-------------------------------------

This may be related:

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.

> Installing 1.0.1 with RPM as root forbid the server to be launched
> ------------------------------------------------------------------
>
>                 Key: DIRSERVER-862
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-862
>             Project: Directory ApacheDS
>          Issue Type: Bug
>            Reporter: Emmanuel Lecharny
>         Assigned To: Emmanuel Lecharny
>            Priority: Blocker
>             Fix For: 1.5.1, 1.0.2
>
>
> If one tries to launch the server after having installed it with root, the
 sevrer simply don't start (even if the daemon tells that it's OK).
> The script use the user to launch the server, leading to some Access Denied, as th
e rpm set all the directories to be owned by root.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[ Post a follow-up to this message ]