If a user deletes the contents of the OpenNMS logs directory, OpenNMS on restarting will not create the necessary controller, webapps, and daemon directories.
Environment
Operating System: All
Platform: All
Acceptance / Success Criteria
None
Lucidchart Diagrams
Activity
Show:
Seth Leger September 20, 2014 at 10:45 AM
All of the logs are in one directory now that we've moved to log4j2. Marking as fixed.
Tarus Balog May 21, 2007 at 8:07 PM
We should do this. We make directories for rrds, reports, etc. if they don't exist, so if the directory doesn't exist we should create it.
But this may be non-trivial, so I'll change the priority to "enhancement". It is a day one issue, before the logs breakout, so I can't really complain much, can i?
DJ Gregor May 21, 2007 at 6:07 PM
Patient: "Doctor, it hurts when I do this ..." Doctor: "Then stop doing it ..."
We've never created any of the log directories automatically--they were always done as part of the build process. Now that there are sub-directories for each of the parts of OpenNMS that run in a separate JVM, you should either delete the contents of an individual sub-directory of $OPENNMS_HOME/logs or if you delete all of $OPENNMS_HOME/logs, you'll need to recreate the individual log directories manually (and correct the permissions of the webapp logs directory, if Tomcat is running as a non-root user.).
In other words: don't "rm -rf $OPENNMS_HOME/logs/*". If you want to whack a bunch of logs, go after a specific subdirectory, or at least do something like "rm -rf $OPENNMS_HOME/logs//.log*".
If a user deletes the contents of the OpenNMS logs directory, OpenNMS on restarting will not create the necessary controller, webapps, and daemon directories.