Logs directory is not created in the correct location on some systems


Looks like /logs directory on some systems (e.g. on Debian) is created in the root directory.




October 24, 2011, 3:18 PM

Where do I find r12883? I thought this might be referring to the nightly builds and tested openfire_2011-10-22.tar.gz but still had to modify ./lib/log4j.xml to get logs working. On our setup, the account used to run openfire does not have access to / so I can't tell if it's still trying to save logs to /logs or not but I assume it is.

Daryl Herzmann
October 22, 2011, 11:42 AM

r12883 has the suggested patch, thanks

Yu Wang
October 18, 2011, 8:50 PM

I met the same problem when starting openfire by "ant -f build/build.xml run" in the source files.
Seems the property "openfireHome" is not set.
Fix it by changing one line of the build.xml to:
<jvmarg line="${run.debug} -DopenfireHome=${target.openfireHome}"/>

October 18, 2011, 3:21 PM

I modified the "./lib/log4j.xml", removing the "{$openfireHome}" variable and replacing it with the absolute path to my "./logs/<filename>" and now I am getting logs. Seems the Log4J application either receiving the wrong path when it looks up the variable or it isn't getting a response when it looks up the $openfireHome variable and it's defaulting to "/log". Can anyone else having this probably verify this reaction?



Daryl Herzmann