Hello,
I had no problem running openfire on Windows.
I tried to install openfire 3.3.3 from openfire_3_3_3.tar.gz on a Debian system.
I executed the bin/extra/openfire-launchd-wrapper.sh and it unpacked the jar.pack files and it seemed to work (did not test). I guess I needed to set execute permission for this file. You’ll need Sun’s Java installed for it to work (check java -version).
I also found bin/extra/openfired, set executable permission (chmod +x), and created the usual link:
ln -s /opt/openfire/bin/extra/openfired /etc/init.d/openfire
I set export OPENFIRE_HOME and the OPENFIRE_USER environment variables in openfired (I added the openfire user by “adduser openfire” command).
The first weird thing is that is tries to call openfire.sh from the bin directory, but it does not exist!
function execCommand() {
OLD_PWD=pwd
cd $OPENFIRE_HOME/bin
CMD="./openfire.sh $1"
su -c “$CMD” $OPENFIRE_USER &
sleep 1 # allows prompt to return
cd $OLD_PWD
}
So I corrected it to to openfire, which exists.
When I try to execute “/etc/init.d/openfire start” it gives the following error in the nohup.out file:
Critical Error! The home directory has not been configured,
which will prevent the application from working correctly.
ERROR 11926 ():
java.io.FileNotFoundException: XML properties file does not exist: openfire.xml
<…>
I deleted nohup.out before I executed “/etc/init.d/openfire start”.
I checked the source what may be the problem. I learned from the source that this openfire home is passed via the “openfireHome” Java system property to the application.
I checked the openfire script and it sets this property with the “-DopenfireHome=$app_home” option.
Before this line I echo $app_home and it is set correctly to “/opt/openfire” (without the quotes, as always).
So it could as well work.
What’s wrong?