a bit more explicit bounds-checking was committed in r8958, and a code cleanup based on the code conventions in r8959
Benjamin Reed March 26, 2008 at 6:17 PM
ok, I've changed the installer to do a copy instead of a symlink in the 1.6-testing branch, r8805
DJ Gregor March 16, 2008 at 11:23 PM
We should fix this, as we do have control over the circumstances that cause this to happen, particularly, whether we use a symlink or not. Making this a blocker for 1.5.91.
Here is a comment I made on the related :
A lot of people seemed to have run into this problem, and it is kind of nasty and hard to debug, especially for new users, so we should probably implement a workaround.
IIRC, changing the symlink to a copy of the file makes it work fine.
Benjamin Reed March 13, 2008 at 1:44 PM
There's not much we can do about this; it's an issue with tomcat erasing files when it shouldn't.
If you symlink the opennms webapp into tomcat's webapps directory, it works, as a workaround, and in the end, this is not an issue with the 1.3.x series, which is going stable Any Day Now.
Opennms 1.2.8 (installed from package)
Java - JDK-1_5_0_07
Tomcat 5.0.28
Solaris 10 ( SunOS murphy 5.10 Generic_118833-17 sun4u sparc SUNW,UltraSPARC-IIi-cEngine )
When tomcat starts the contents of opennms.xml in $OPENNMS_HOME/webapps/ is removed.
ls -last $OPENNMS_HOME/webapps/opennms.xml
0 rrr- 1 opennms staff 0 Aug 10 21:18 /usr/local/opennms/webapps/opennms.xml
file $OPENNMS_HOME/webapps/opennms.xml
/usr/local/opennms/webapps/opennms.xml: empty file
restoring the opennms.xml file allows Tomcat to start again properly but the file is wiped out again.